Document info update without creating a new release

[GoogleCodeExporter]

What steps will reproduce the problem?
1. After the creation of a new document release, is not possible to update the 
relevant fields (e.g.: the description) without creating another release

What is the expected output? What do you see instead?
1. Now we create the new revision, inserting the required modifications, saving 
 and than deleting the previous version. 
Will be helpful the capability to update the additional fields (title, 
description, comment, file name, workflow) without creating a new release (in 
some way like is already possible for folders)

Original issue reported on code.google.com by pia.alg...@gmail.com on 23 Jun 2011 at 9:51

[GoogleCodeExporter]

It is key feature of document and its metadata versioning: keep all versions of 
content and metadata.
It is not required to upload new content and increase version of document 
between revisions.
May be I adjust revision view to group revisions for one document version

Original comment by vit.jo...@gmail.com on 23 Jun 2011 at 5:11

• Added labels: Type-Enhancement, Usability
• Removed labels: Type-Defect

[GoogleCodeExporter]

Sure it's a key feature to keep versions of content. 
But the metadata regarding a version need to stay changeable at any time. 
There might appear new or changed metadata when the workflow is going on. These 
data need to be documented related to that version of content. 

Proposal: Use of a history page of metatdata regarding each version of original 
data. Here we can write down (and read) the steps of the workflow as well.

Original comment by Dieter.E...@dest.de on 13 Feb 2012 at 2:29