I have a mostly managed Aperture 2 library (running OSX 10.6.8) and am in the process of moving to totally Managed. (The plan is to update to Aperture 3 and Lion so that I can move from MobileMe to iCloud. Joseph outlined a plan back in Oct. 11! I am finally tackling.)
Starting with ref projects stored in Folders on external drive, I am Consolidating Masters, project by project, copying, not Moving. (Safer, right?) These files have custom names that I added on import (as outlined in 10 Tips on File Mgt.) What I just discovered is that the versions are all the Original File name, not the Custom Version name. Is there a way to correct that as I am consolidating? Or do I have to copy and paste each one to correct. And how do I make certain that future versions use the custom name?
I am wondering if I missed something when I initially imported. Is this an issue with referenced files?
I have searched the forums and don't see the answer. I apologize in advance if I missed it!
You are here
Custom file name for referenced orig files, but version name does not reflect?
#1
On further investigation, I have realized that the files in Projects that I initially imported as Referenced DO include the custom file import name as the Version name. The projects that I discovered today when consolidating to Managed were ones that had been originally imported as Managed BEFORE I started using custom import naming, then were moved to Referenced when I started using Joseph’s system of Custom file names. Somehow I must have missed a step in the process as they have Versions that don’t include Custom name (that is now on Master.) So, how do I fix these Version names? And how do I correct in the future. I have stopped Consolidating until I get some advise. Thanks!
Susan S
Susan,
Thanks for the follow-up, that helps.
What likely happened is that when you chose to relocate the masters (going from managed to referenced), you also chose to rename the masters based on the new naming scheme/preset. This however does not rename the versions at the time of moving.
What you can do now is select them all, and open the Batch Change menu, then rename all versions as the Master File Name. You will need to create a new preset; I’ve outlined the steps in this [screenshot].
The only caveat is that your version names will also include the .CR2 or .JPG or whatever extension the masters have, which means when you export new versions to the desktop, you will have a double file extension. This won’t affect the file but could be confusing. Unfortunately there’s no way to batch remove the extension on the version name.
@PhotoJoseph
— Have you signed up for the mailing list?
Thanks Joseph. A few more questions about this.
1. For the future, is there a way to change the version name automatically when changing to a custom Master File name? (Did I miss a step before?) I am now using your system of naming on import, but these were older and if I someday I wanted to go back and rename more old Master files, can the version names also be changed automatically?
2. There are only ten small projects to be dealt with. (The ones I had moved to Referenced and at the same time made this custom name change to Master Files.) A total of 558 files have the “wrong” (old file names) for Version names. I am now ready to consolidate, project by project as I move to total Managed Library for now.
Would it make any sense to change them one at a time so that they would not have the CR2 extension included? If I change the version name, what will future versions (of the same Master) reflect? I am a bit confused about how version names are set up for future versions. Does your batch change solution set it up so that the change is reflected in future versions? (And does it matter when I make the change?) Am I making sense?
Susan S