Renaming Document on Checkin?

[cthompson]

We have established naming conventions. For example, a document might be named "DMSTestPlan_v0.1_20090116_Draft.doc".

The version number, date, and version name must be modified each time a change is input to a document. For example, the previous file would be named "DMSTestPlan_v0.2_20090117_Draft" or "DMSTestPlan_v1.0_20090122_Final" upon update. Each time the document is edited, the name must change.

Each time a document is checked into Alfresco, the name I apply is automatically reset to the name of the checked out document. This is not an acceptable method of versioning. Although I can still review the old versions as long as I have versioning turned on, the names never change.

Has anyone found a way around this? Or, is there any plans to change this process?

Carrie

[cthompson]

It appears that this isn't a very active forum for basic use questions.

This issue has been resolved for my company's process.

While documents may be created at the Alfresco Portal or from the mapped network drive, all check in procedures should take place from the network drive if you wish to retain previously named versions with their names intact.

Basically:

• Check out a document from the portal or from the network drive.


• Perform necessary editing and rename the document according to your established naming policy (eg v0.1 to v0.2 or v1.0).


• From the network drive, drag and drop the newly edited and named document into the same folder it was checked out of.
The previous version remains as does a copy of the previous version named (working copy). The newly named version is also in the folder.

• Delete the (working copy) version.
This leaves you with the original (correctly named) and the edited version (correctly named).

This can be considered a plus as the original document will remain as a read only version and cannot be modified. This is because no "check in" took place to actually replace this document. Any company whose process requires that versioning be a part of the process, and that all historical documents be saved with that versioning clearly identified, can use Alfresco as described above to ensure your process is followed. All of your Draft and Final versions can be easily identified in their respective folders.

[zaizi]

Can I ask why you have to name the files as "DMSTestPlan_v0.1_20090116_Draft.doc"? What is the thinking behind it?