Versions not handled by the contentStore selector ?

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.

jservajean

Hi all,

I have set a new store in order to stream some selected content to a specfic hard drive, by means of the contentStoreSelector.
Using the "cm:storeSelector" aspect and "cm:storeName" works really fine for the main document (content is moved to the new drive), but all the older versions of the document (cm:versionnable) remains in the older content store.

Is there a way (by configuration/tweaking) to have the versions moved along with the current version during the operation ?

Thanks

afaust

Hello,

the store selector aspect only works on those nodes that have the aspect applied. Every version is a "frozen" node with the metadata/aspects the document had at the point the version was created. If you add the aspect to the document later on, the existing versions will not be modified and thus not have their content moved to the alternative store.

I currently see no way using pure configuration / tweaking to get your requirement to work. But I can think of an implementation option: code a behaviour logic that modifies the "frozen" version nodes (in violation of their "frozen" state) and applies the selector aspect to them as well whenn applied to the actual document. A potential problem here might be that some internals handling the versioning may get in your way and enforce the "frozen" logic for the content move (i.e. throw an exception) even if you can get the aspect applied.

Regards
Axel