Mark a photo as the FINAL version.
A way to differentiate a photo as the final version which is being used in a project.
Note: the problem is rarely due to inadvertently editing a single photo whilst in develop module.
The problem is inadvertently editing multiple photos due to auto-sync remaining enabled, or snafu in library module (especially whilst in grid view), or via keyboard/menus...
Snapshots don't keep that from happening, nor do they help you detect that it has happened.
Indeed *IF* you know you've goofed, then you can go through each potentially goofed up photo, and restore (develop settings only) via snapshot - but you have to do each photo individually, and they don't help to restore non-develop metadata.
Also, there is always some uncertainty as to which snapshot to use, and/or whether there were some "on purpose" edits which weren't snap-shotted - if such is the case, you will lose adjustments by restoring the most recent snapshot...
PS - Ratings and keywords also need to be lockable - not just develop settings.
Bottom line: snapshots are not a panacea, and are no substitute for a locking feature.
Lock images (prevent from any new changes unless un-locked) whenever you feel, would indeed be a fantastic added feature to LR.
But then also, when you include such locked files within a multiple selection
(images to witch you intend to apply a batch alteration),
LR should then warn you with
"Your selection also includes "somany" locked files"
And if you then choose to proceed nevertheless, LR should go ahead to proceed changes to all un-loocked files(as is per default), but hold and
let you see one by one each of those locked files, and let you confirm first
1) "Skip/Dont apply",
3) "Apply to a copy" (hard or virtual?)
..and with the additional option :
A) "Re-look after"
B) "Discard look".
"Just this one"
(or of course other combinations of the above ideas)
Of course with ability to use "locked files" as a filter.
That would be cool, to "lock" the photo down. If you tried to make any more edits, it could offer to make a virtual copy.
I like it.
How do I find all the images in my 100,000 database that have snapshots called say"finished".
How do I prevent changing a flag or a keyword, so they disappear from collections of "finished" images.
A finished image may spawn multiple children such as small jpg for web, full size tiff for printing, with different colour spaces depending on ultimate destination. I wish to be able to easily find the finished image I am looking for and / or its children. Despite the fact that Lr is built around a database, I cannot run a query in Lr to select such a set of candidates.
The snapshot feature is very useful, but I cannot search for specific snapshots.
There are flaws also with using Virtual Images to do something similar. The main flaw is that there is no separate xml file for each virtual image. That is the reason I have stopped using virtual images and probably should be the subject for a different thread..
Rikk, that is a great idea.
But is that not just the same as publish. When an image is published the location, date and time are added to the history similar to a snapshot.
Where both might suffer is there in no way of minimising deletion by accident. A lock could warn the user to click a box before deletion or further editing.
Between snapshots, virtual copies, flags, color labels, stars, keywords and collection, yes, one can establish a system for marking photos as final version. But that's not the point.
Because this process can vary so much from person to person and also from shoot to shoot, the point is to have something consistent that doesn't include jumping through 10 hoops to mark a photo as final.
Once i know I finished working on an image, I shouldn't have to add a snapshot, create a virtual copy, flag it as pick, add 5 stars, mark it with the green label, add the keyword FINAL and add it to KEEP IT DO NOT TOUCH collection.
And even if I did, which of these criteria would I use to filter my catalog to find only the final versions of the image? And what if I happened to skip a step in the above elaborated process?
And what if after I decide to do something else to the same image? I create a(nother) virtual copy and undo everything? Unmark it as pick, remove the green label, remove the snapshot, lower the star rating, ensure to remove it from the final collection, etc. Do you see how it can get crazy really fast?
The (many) benefits of having this feature have been detailed by many so far. The original idea was posted over 4 years ago! That's basically an eternity. Back then, the iPhone 4 was the hot new thing and Photoshop CS5 was the current version.
By now, this should either start to be implemented or this thread should be deleted to spare people some considerable frustration.
Now that Adobe have spent 2 years working on improving what is under the bonnet, they need to seriously work on Usability. This is a simple example of a small feature having major usability benefits.
I have a whole bunch of good suggestions to make, but I am not going to put the energy or effort into documenting or describing them, if I like this one it takes 4 years and still no progress.
If Adobe are serious about usability then I am happy to share my ideas. The usability of the entire Creative Suite is seriously below par.