Naming files in translation projects
Copyright © ProZ.com, 1999-2019. All rights reserved.
Surely, the subject might have been already addressed on proz.com, nevertheless as some of my ideas may be individual, I dare to present them here to share them with others in hope of suggestions which might help improve my system.
Looking for things in a jungle of files may be a frustrating job.
In spite of computer system search devices, any successful search is only possible when you know what you are looking for. Proper naming of directories and files in translation projects might proof to be very rewarding.
With a time, there is always a temptation of improving your present system. Any changes should be only introduced if they seem to be more logical. Good criterion of new introductions is the thought of “What name I might be looking for in this particular case?”
1. Naming directories
My tree of directories could take the following shape:
Translation memories by name of outsourcer [mem_by_name]
Translation memories by subject [mem_by_subject]
Outsourcer's name 1:
Source Directory [Source]
Working Dir [Working]
Target Dir [Target]
Proofread Dir [Proof]
Outsourcer's name 2.
And so on.
It is good idea to make the template, empty directory named “New Name” with all its subdirectories properly named according to the above, or your own order of names.
Each time new project comes, you may want to decompress it (if necessary) directly to “Source” subdirectory of "New_Name” folder template and rename it with new Project Name or Project Manager’s name. Personally, I find it much easier to remember PM names then Project Names. On the other hand, with a time, PM may change and any successor may refer only to the Project Name only, while asking for copies or something.
2. Naming Files
Alternative system might be adopted with only one folder used for any outsourcer: "New Name," which you rename according to received project. This time you may prefer rename particular files in this folder adding to their original names, working languages code letters. For example, NamePL.doc, NameWK.doc or NameEN.doc respectively to the above system.
The later system allows you to keep only one directory for each project, saving, at the same time, disk space and the necessity of handling more files.
When the project is ready for sending, you may easily rename the files by deleting previously added characters, or your PM may be happy with new names – easily distinguishable from source files by language code letters.
I believe, some of you might have developed even more interesting systems and I hope to trigger some kind of discussion on the subject.
Thank you for reading.
Will appreciate comments.
Profile at: http://www.proz.com/pro/64759