topic Re: Alfresco Share VS metadata versioning in Alfresco Archive

Alfresco Share VS metadata versioning

michalwrobel — Fri, 16 Mar 2012 13:04:45 GMT

I've a question regarding versioning of metadata in Share. As I can see by default metadata is versioned but only as a 'snapshot' in the moment of uploading new content version. I would like to force alfresco to store a new minor version at EVERY metadata change.I've found this topic:https://forums.

Re: Alfresco Share VS metadata versioning

billerby — Fri, 16 Mar 2012 15:32:03 GMT

Michal,

If you add content in Share and then add the aspect Versionable to it through the "Manage Aspects" action, your content will get this aspect with its default properties which includes the "cm:autoVersionOnUpdateProps" set to true ie, you will get exactly what you want.

However If you just upload some content and then uses the Share action "Upload New Version" the REST API that Share uses seems to set the cm:autoVersionOnUpdateProps to false after adding the Versionable aspect.

I guess that if you create a rule on the document library that automatically adds the Versionable aspect to all you content (or a preferred subset) directly upon upload you will have the behaviour you are asking for.

Have a nice weekend!
/Erik

Re: Alfresco Share VS metadata versioning

michalwrobel — Mon, 19 Mar 2012 09:50:16 GMT

Hi,

thanks for you answer!

You were.. partially right
Yes indeed if I
1. upload new content,
2. then manually add versionable aspect,
3. and afterwards modify metadata everything is versioned properly (every metadata change treated as minor change).
4. But.. if the next step is uploading new version of this content it goes astray again, metadata changes pass unobserved.
Even after manually removing versionable aspect and adding it again the problem still occurs.

So Alfresco Guys, don't you think this behaviour should be considered as bug?

(Tested on Alfresco 4.0d community)

Re: Alfresco Share VS metadata versioning

billerby — Mon, 19 Mar 2012 10:12:47 GMT

http://wiki.alfresco.com/wiki/Versioning_Behaviour#Configuring_the_Auto-Version_Behaviour_for_Property-Only_Updates_.283.2.29

They state "although it should be noted that Alfresco Share currently disables this feature (by explicitly setting autoVersionOnUpdateProps=false for upload and checkout)."

I also notice the behaviour you are explaining, what I find really strange is that the autoVersionOnUpdateProps stays true all the time but no new versions are created upon a property change.

So to sum up:

1. Upload a document in Share.
2. Add the versionable aspect. The autoVersionInUpdateProps is true by default
3. All property changes from now on are reflected with new minor versions.
4. Upload a new version of the document. The autoVersionInUpdateProps stays true.
5. After this no property changes is reflected with new versions.

I would recommend you to file an issue in Jira. http://issues.alfresco.com

/Erik

Re: Alfresco Share VS metadata versioning

michalwrobel — Mon, 19 Mar 2012 10:48:01 GMT

Yeah, I've also just pulled versionable aspect properties to the share GUI and tried to turn autoVersionOnUpdateProps on/off but it also doesn't change anything after the node is 'broken' by uploading content. Really strange ;/

JIRA issue here: https://issues.alfresco.com/jira/browse/ALF-13353

Re: Alfresco Share VS metadata versioning

billerby — Mon, 19 Mar 2012 14:06:55 GMT

Found an open related jira issue:

https://issues.alfresco.com/jira/browse/ALF-2685

/Erik