Versioning of directories

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

hbf

Dear all,

I would be very glad to receive some clarifications concerning directories and versioning:

1. Versioning for directories is implemented, right?  I just have to apply "cm:versionable" to them, correct?

2. "cm:versionable" in case of a directory means that the directory's list is versioned. So one version may have children {A,B,C} and the next version might have children {B,C,D}. Right? I took this from here but hope it's still valid?

3. Where can I find additional information about how versioning of child-associations (that's what cm:folder's cm:contains is) works in detail? For instance, if a versioned directoy (one in the version history, not the current one) has children {A,B} and A is not versioned and B is versioned, then the reference to A is just a link and the reference to B is a link to a particular version of B (namely the version of B that was the current one when the directory was archived). For the latest version of the directory (the current one), *both* A and B are references that automatically point to the *latest* versions of A and B, respectively. Is this true?

4. How can I see the version history of a directoy in the Alfresco Web Client? How can I revert it to a previous version? The Web Client shows the version history only for files and not for spaces.

5. How do versioned directories relate to "cm:versionable"? Is this going to be an *additional* feature or is it going to replace the current behaviour of "cm:versionable"?

Many thanks,
Kaspar

rwetherall

Hi,

1) Yes versioning of directories is implemented (in the repo at least) BUT this only versions the folder object itself, not all of its contents.  This feature of inherited or banded versioning is to come.

2) Yes I believe this to be correct

3) When a node is versioned all associations emanating from that node will be versioned.  The versioned associations will point to the most recent version of the destination node as you state.

4) At the moment you can't see the version history information for a folder in the web client.  Although the repository supports the notion of a folder being versioned the web client does not provide UI to support this.

5) Here you are making reference to the WCM repository which works differently from the DM repository.  Over the coming months we will be working on closer integrations of these two worlds and I'm sure this will have a positive impact on how we version folders.

Cheers,
Roy