Using Alfresco Share:

  1. Upload new document
  2. Change “description” property to “Description 1.0”
  3. Upload new version (1.1)
  4. Change “description” property to “Description 1.1”
  5. Upload new version (1.2)

Modifications on description metadata are stored according to this figure.

alfresco-versioning-metadata

In my opinion, this logic seems incoherent: version 1.0 must not store “Description 1.0” value or both versions 1.1 and 1.2 must store “Description 1.1”.

New issue has been created (https://issues.alfresco.com/jira/browse/ALF-19860) in order to clarify Alfresco criteria on this subject.

Final considerations

Once Alfresco resolved the issue, I understood that my thoughts on this were tricky. Real scenario works according to this figure.

alfresco-versioning-metadata-2

Alfresco advice, based on the use of cm:autoVersionOnUpdateProps property, may provide a huge number of versions to the user (one on every property value change). So, maybe the best approach is to version automatically on file upload in order to build a consistent version history for the user.

Alfresco · Metadata versioning analysis

Responder

Introduce tus datos o haz clic en un icono para iniciar sesión:

Logo de WordPress.com

Estás comentando usando tu cuenta de WordPress.com. Cerrar sesión / Cambiar )

Imagen de Twitter

Estás comentando usando tu cuenta de Twitter. Cerrar sesión / Cambiar )

Foto de Facebook

Estás comentando usando tu cuenta de Facebook. Cerrar sesión / Cambiar )

Google+ photo

Estás comentando usando tu cuenta de Google+. Cerrar sesión / Cambiar )

Conectando a %s