How to avoid use of filenames for versioning

[whispering]

Hi

We are an IT company using Alfresco Share sites as project sites to manage internally project documents.

During documents migration from our old system, we found the use of filenames to implement versioning common.

Example:
ProjectPlan_CustomerA_20110711.mpp
ProjectPlan_CustomerA_20110622.mpp
ProjectPlan_CustomerA_20110503.mpp

We can migrate the above by using Alfresco Upload New Version  function to consolidate the above three files into one file (where versioning is done by Alfresco)

However, if we do so, when our customer calls and refers to a file sent to them, they will refer to it by the filename.

How can we implement Alfresco so that the customer reference to a specific file is met and yet at the same avoid the multiple files from the old way of doing things?

We do not want to open our Alfresco repository to our customers.

thanks

[mrogers]

Can your customers say "ProjectPlan_CustomerA Version 123."    Or do you have to remain doing version control through filename mangling?

[whispering]

Not quite sure what you meant by your question.

Could you please clarify?

The customer receive a file and because they cannot see the version metadata (since they are not Alfresco users) - there is no way they can say a certain version. They can only refer back to the filename.