Versioning

[sacco]

Is there any way in the Web Client to  see the detailed metadata of a previous version
of an asset or (as the is in WCM) to roll-back to a previous version?  I can see only a link to
'view' (in which case I suppose roll-back can be approximated by copying the older version
over the newer, albeit this isn't quite the same thing).

If not, is the older metadat, etc. still available in the repository (but just not exposed
through the Web Client), or has it been over-written?

Finally, is it possible to create a link to a specific version of a document:
a)  in the Web Client;
b)  programatically in the repository.

The motivation behind these questions is that when there is a library of technical
references whaich is maintained to keep the documents up-to-date, there will be
some projects that need to refer to the latest updated version, whereas other will
require to be based upon a specific (fixed) version of a standard.

[protenus]

I would argue that it should not be created a new version for each update of metadata.

Reason is that it would possibly create an insane number of versions. Metadata is not only usable for classifying and retrieving documents, but also to track status, or be the link of a document to an external system, or whatever you come up with. So if each of those edits creates a new version, there will be many version. But the content is still the same.

Instead, this can be taken care of with auditing if you need to retrieve before values. New version should only be used when content has changed.

/Peter Löfgren

We have a need for metadata changes to create new versions. Here is our scenario.

We have a spaces which have custom metadata, this metadata stores information about the the company whos documents are stored in sub-spaces within this space. (for example metadata is company inv. phase, etc.)

We need to be able to report on changes to this information (how long was a company in a particular phase, etc). Auditing (as we have used it) does not give us access to this specific data.

If the space would create a version on update of metadate, we could get the information from the version history.

It is very difficult to extract this information from the audit system.

Any ideas? ANy way to have those spaces make new versions with a script or rule?

Thanks,

M