I’m hopeful

Lightroom: Mark a photo as the FINAL version

Mark a photo as the FINAL version.
A way to differentiate a photo as the final version which is being used in a project.
206 people like
this idea
+1
Reply
  • EMPLOYEE
    I’m happy
    Jeffrey Tranberry (Chief Customer Advocate) April 05, 2011 21:13
    Pat, can't you use a custom color or keyword as metadata to do this?
    • view 3 more comments
    • Jeff,

      Merging would be useful.
    • Merging is a possibility but note that the OP just asked for a way of flagging final versions. He didn't imply locking. I use colour labels for recording the status and that works fine because I don't have a locking requirement.

      So strictly speaking, the two threads had different motivations. If this thread's OP (pat d) agrees that locking would address his feature request (in which case locked photos need to stand out somehow) then merging makes sense.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited sad, anxious, confused, frustrated

  • 8
    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.
    • view 2 more comments
    • Jack, that's PRECISELY how I would use this!! I do different finishing and effect techniques on various images, both in my fine art and portrait work. I don't want these edits to clutter everything, and I don't want them thrown away. And I already have specific uses for all star and color ratings/categories. This would DEFINITELY be a tremendously helpful tool, and it should be tremendously simple to implement.

      HOWEVER, I disagree that "final" means "you can't edit it anymore". I would just want it to require a confirmation that I do want to edit it further before allowing me to do so. Sometimes I need to go back to do "one more" edit, but I don't want to need to remove the "final" label in order to do so because I know myself well enough to know that I would forget to re-apply it at least half the time. :)
    • Kevin - Can you offer any odds that this feature will make it into Lr4-final, or are we more likely talking Lr5 for this one?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • 1
    If locking is what's being called for, then forget the rest of this reply.

    But, if marking a photo as the final within a group is what's being requested, I'd like to suggest the alternative feature request for enhanced photo group handling (aka stack replacement technology) - please read down aways since the topic evolved quite a bit... In a nutshell - any set of photos could be defined as some kind of group, and one photo in the group is always elected as "representative". I would think this "representative" would be the same as "final" in this case.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • 2
    Maybe a way to MARK, LOCK and TAG it with the project that this final photo version was used in?
    Then if you tried to open it Lightroom could offer to make a virtual copy of the final file as a version 2 to edit that way you always have the FINAL file in the state it was used in that project but could still go on from there to edit for another use.
    • view 2 more comments
    • I mean that I use photos outside of Lightroom in design projects but I would like to know when I am in Lightroom which photos were the Final versions used in a certain design project. Using a TAG would differentiate from Lightroom workflow.
    • Well, from the first response given, it seems like Adobe may be thinking of this more like the "lock" idea. I mean if all you want to do is tag a photo as final for a project you can easily use a free IPTC field or custom metadata if you don't want to bastardize IPTC. I mean, you could easily define a custom metadata field, called "project", then just enter the name of the project for each final version to be included. Then you can filter all finals used in a project... Would this fall short of your desires? (you could also define project status as custom metadata...) I use custom metadata all the time to associate photos in various ways or record notes about them, without polluting the keyword space or consuming color labels...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • 1
    Jeffrey Tranberry said: "Do you guys think it should be merged with this topic? http://feedback.photoshop.com/photosh..."

    I say: "Yes, most definitely"!

    There is considerable confusion about whether "marking as final" implies locking. And, there being 2 Ideas about it makes it even more subject to question. My sense is that any-ol' metadata item can be used to "mark" any photo for any reason (hopefully custom metadata will be supported in Lr4 for this sort of thing...).

    Without the "locking" aspect, what would be the value added in marking "as final" over a simple metadata assignment?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • I’m stoked about native locking, but also a bit worried about losing features I've come to love in ChangeManager.
    1
    I'd like to request some other options besides "Create a Virtual Copy" if user tries to edit a locked file:

    - Accept change, but remain locked (allows single edits in case you just want to add one keyword, or increment temperature or exposure by .1... - I find this *very* convenient when keeping files locked via ChangeManager - avoids having to unlock, adjust one thing, then re-lock).
    - Unlock - self explanatory (I almost never explicitly unlock files anymore in ChangeManager - just start editing then approve the unlock prompt).
    - Revert after a few seconds (allows one to freely experiment temporarily, with the knowledge that it will return to its locked state immediately thereafter - I use this all the time in ChangeManager (via the 'Ignore' function) - also my display driver works this way ;-).

    PS - Another option I like is to create a snapshot when a file is locked, so in case its unlocked for editing or whatever, one can still compare to or return to previous locked state or whatever. If a snapshot is associated with a locked photo, there should also be an option to update the snapshot if change accepted (see above), and date changed to reflect update.

    PS - Please display snapshot and/or lock date-time.

    Summary:
    =======
    The goal is to eliminate inadvertent changes, *without* impeding the ability to continue to make changes on purpose - or even to play (er, I meant "experiment").
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Another related topic:

    New way to handle related groups of photos in Lightroom. Hint: read down a ways - this 'Idea' evolved considerably after initial conception.

    In case ya didn't catch the connection:
    --------------------------------------------------
    One photo is always the "elected representative" in a defined group of photos (for the purpose of collapsed viewing...), so if one defined a group of photos as being "potentially final for a project" then which ever one was the elected representative would also serve to "mark" it as final in this case.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • I think a snapshot is best for this kind of thing. As final as we might think an image is there's always more that you might want to do to an image later. Saving snapshots that indicate what you may have delivered to a client at the time, for example, is very useful for reprinting purposes without limiting future image development.
    • I agree Scott - I use snapshots without exception as part of "marking-as-final" - its part of the next best thing work-around-wise to not having a true lock, IMO. However, that does not solve the problem of inadvertent edits.

      However, if Lightroom used a simplified/unified targeting scheme, *and* there was some clear difference, even if subtle, when adjustments are being targeted at multiple photos versus just one, I would not make the mistake of inadvertent edits nearly so often, making locking far less necessary.

      Reminder: locking does not limit future development, it just means you have to click "unlock" first, or answer a prompt if you don't unlock first. I mean, I suspect the steadiest handed and consistent brained users may never lock - more trouble than its worth, but for the more oopsidaisical of us...

      Another idea that can be used in conjunction with snapshots, instead of or along with locking, is photo comparison. For example instead of locking, just take a "final" snapshot, then have a feature that can compare the present state of photos to their final snapshots.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • While I could see how locking an image might be useful to some I can't help from thinking that the idea of finality is a misnomer. I can't tell you how many times I've seen my clients name Photoshop files "[image name] final.psd" "[image name] final 2.psd" "[image name] final 3.psd". At least we can now have it parametrically! IE, Snapshots named "Final 1" "Final 2", etc. LOL.

    Question: If we get rid of the word "final", how could we convey the same meaning?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Poor man's "ChangeManager":

    - Create a develop preset with any settings (does not matter), and name it something like "Finished".
    - Load into text editor and replace the settings with:
    settings = {
    NoEdit = true,
    },
    - Save the file & restart Lightroom.

    What you have now is a way to tag a photo as "final" by using a develop preset, instead of metadata.

    You can search for photos that have this preset applied (or that dont) in library filters or in smart collections.

    Options for taking this idea further:
    - Create a no-edit develop preset named "Clear Edit History" and use it to clear the top of the edit history list without changing anything.
    - Create a no-edit develop preset named "Finish Editing Later" and use it to mark photos as "Not Final"...

    Summary:
    ========
    Since Lightroom has "Develop Preset (applied)" as metadata, one can apply null/no-op/no-edit presets to clear the edit history list, and for recording end-of-present-editing-session status.

    PS - this won't help with non-develop-settings changes, but hey...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • That's pretty clever. Is it better than a snapshot? I suppose you can apply it using Quick Develop, which could be handy...
    • Snapshots are stored in xmp, so they can weather catalog anomalies. But, you can't search for photos with "thus and such" a snapshot taken, so they don't help with finding photos that have been changed since snapshotted, or those that still need work done...

      In addition to the obvious of being able to clear the edit history list (or even just for serving as a visual separator between editing sessions), the NoEdit presets can be used in library filters and smart collections - snapshots can't.
    • SnapAndMark - Snapshotting and annotating the edit history list, on steroids...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • i like the idea of being able to "lock" an image to prevent editing.

    pat d, as far as marking "final", wouldn't this work.

    1) Create a metadata tag called 'my projects'
    2) Under 'my projects' create a 'project name' metadata tag for each project.
    3) For each image in a project, add the appropriate 'project name' tag during import.

    I have two tags that I use to mark "final" : 'Client Pick' and 'Final Pick'

    With these tags, I can now:

    1) Find all images for a given project.
    2) Within a project, identify images that are either my 'final' set and/or the set that the client picked.
    3) Find all 'final' images across all projects (or any subset of projects).

    This is an example of the power of metadata.

    I also have metadata tags 'On Flickr', 'On my site', 'On Facebook', etc. With these, I can find all images for a given project and see where I have published them.

    hope this helps.
    • When you say "metadata tag", I assume you mean "keyword"(?)

      Some people shy away from using keywords for such stuff, forgetting that they can be made non-exportable if they are only to be used for such "internal" purposes.

      Others use custom-metadata for such stuff instead of (or along with) keywords...

      Anyway, because its already so easy to mark things with metadata like this, I have also assumed that the primary thrust of this Idea is really the "lock" aspect.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Rob,

    Yes. Sorry for mixing it up. I wanted to say Keyword rather than metadata tag.
    • OK. I think pat d's primary objection was just that "project final" keywords kinda get lost when mixed in with the rest. He wanted something more specifically purposed, I think.

      I'd also like to see the notion of groups of related photos extended, e.g. (read down aways): http://feedback.photoshop.com/photosh...

      This would allow photos to be associated for projects or other purposes without requiring additional metadata assignment or additional collections..., and one could stack all photos in a group, any group, or expand them, which is something you can't really do now using keywords or collections.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • It would be useful if a given image in Lightroom could be "locked" - the effect would be that no further edits could be made to that image without first unlocking the image.

    The idea is that once you have completed editing an image, you could "lock" it to prevent any inadvertent further changes - essentially marking it as a final image. You would make a virtual copy of that locked image in order to create a new, further edited version, while still ensuring that the "final" for a given purpose was protected from further changes.

    This reply was created from a merged topic originally titled
    Lock edits to prevent further changes in Lightroom.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Eric Chan (Camera Raw Engineer) September 26, 2011 16:03
    Snapshots effectively do the same thing, so that you always have a way to "get back to" where your stated "final edit" was.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Agreed, I think Snapshots are the key and the idea of anything as being "final" is a lost cause/ false notion.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Its not just about having a way back, its about preventing the need to go back, and/or knowing when/if you need to go back...

    The notion of "final" (for now) is a *very* useful one - after marking/locking, attempts to edit in the future require approval.

    Summary: Right now a photo has only one state:
    - Anybody can do anything they want to it, on purpose or by accident, and although there are a multitude of ways to go back, there is no way to detect the need to go back - no way to distinguish inadvertent edits from intended edits.

    This proposal is to add another state:
    - I'm done for now. In which case you know it hasn't changed. If you want to edit it again, then do - but you'll have to answer a prompt first, that's all.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • The path leads to many destinations but who can say which is home.

    Relatively few of my images ever reach a singularly "final" state.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • 1
    I would use a feature like that. Select and Reject are not enough. Finished should be added. Maybe even one more that is user adjustable such as uploaded, printed, etc.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Yes Final version tag with lock would be ideal. I have too many times accidentally edited a file that was already final and part of a collection and it no longer matches the set.

    This could be set also (if user wants) automatically to any images that have been exported, have been part of a web gallery etc. It would warn user that the photo is part of collections so and so and exported yy-mm-dd and force user to make new virtual copy,
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • 3
    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",
    2) "Apply"
    3) "Apply to a copy" (hard or virtual?)

    ..and with the additional option :
    A) "Re-look after"
    B) "Discard look".

    with option
    "Just this one"
    "All"

    (or of course other combinations of the above ideas)

    Of course with ability to use "locked files" as a filter.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • My thought was something similar but not exactly the same as outlined. I would like to go beyond just locking down a single image. I would like to mark as folder as processed/done/complete/final with all of its sub-images.
    The 'pick' and color coding of individual images is part of my work flow as generally finalizing which photos were the delivered versions.. it is just looking through my huge library that I would like a library management function and have the folder denote it being marked processed / complete / locked in the library explorer view.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Regarding the locking aspect of this idea, I'd like exports to be locked if photo not locked. Or at least a prompt must be answered to do so.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • I mark my photos as "Final" versions by placing them into collections. I also tag those photos with the word "delivered".
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Benjamin, what we desire is those pics to be protected from accidental further editing...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Benjamin, what we desire is those pics to be protected from accidental further editing...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Work-arownd idea:

    Convert 'final versions' into DNG (with or without boxed-in original raw) + make a snapshot called 'Final1' + a reminder that there IS a snapshot (with keyword or colour or star..etc).

    That way you know where to come back to (to the snapshot) and are shure it's in the file (versus external XML or/and in catalog only or only as a fragile virtual copy only). (Unless I have things wrong. of course if you have all pics in DNG they will stand out less but this proceedure seems doing the trick, no?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • The work around suggested so far though are a little bit cumbersome and not sure would fit everyone's need. One of the wonderful things about Lightroom that the Adobe team has done is build in features that people can use their own way.

    It sounds like people want to accomplish a couple of specific things:

    1) Be able to lock / protect an image file from modification (perhaps invoking the native OS's 'file lock' property.

    2) Be able to mark a photo processing complete and have it natively filterable across the library and have a single clear cut method to be able to differentiate a folder or files processing status. Unprocessed/Draft/Complete-Final-Delivered to really be able to look at ones library and say.. "Ok.. what is done and what do I still need to work on."
    The work arounds so far include...
    -Snapshots aren't filterable and are not visible outside of the develop module.
    -Key wording is a work around but not quickly filterable like star, pick, stars, and colors.
    -Images can be dragged and dropped or built using smart collections but users dont want to have a collection for every shoot.
    -Pick / Unpick I think people have built into their workflows.. though for some it is at the beginning to slim down images, some is cleared after purging rejects, and for some it is used at the end of their processing.
    -Generating an additional 'final' copy of an edited image is not in most works flow and not something people want to do.
    ... though none of them accomplish #1.
    3) Have a way to track what was actually delivered to a client.
    ... this can be accomplished through
    -Key wording (messy)
    -Dedicating a color to it (workable)
    -utilizing a combination of stars, colors, and picks (workable)
    ... though this does not facilitate #1 nor #2
    4) Be able to have another piece of quickly available and editable meta data that can be used through the library and utilize all of the features of Lightroom.. and not be a combination of many things to accomplish a single thing.
    Having to use multiple work arounds and methods to accomplish things simply increase complexity for trying to accomplish a single task, and make the library less manageable overall; and do not accomplish 1, nor 2-3 efficiently.

    So why not just implement an additional set of flags that can be put on images to account for 3-5 different processing status.
    Such as : New, In Process, In Review, Distributed, Complete
    or Unprocessed, Draft-InProcess, Complete-Final-Delivered

    Christopher
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • 1
    Protection-feature is missing ! That's the issue.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • They're a few ways to do part of this request but they are not simply!
    I would love a quick key that did a final flag. It could be highlighted maybe with a multi-colored box (Red and Black) around it in thumb view.

    Robe Cole comments below I think head in the right direction
    - Accept change, but remain locked (allows single edits in case you just want to add one keyword, or increment temperature or exposure by .1... - I find this *very* convenient when keeping files locked via ChangeManager - avoids having to unlock, adjust one thing, then re-lock).
    - Unlock - self explanatory
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Good idea, instead of having to compare time stamps, and file sizes. Suprised I didn't think of this tbh.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • YES!! I think you can make a custom label "Final" but it would be nice to have a flag like symbol all in place.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Yet another shortcoming of snapshots as work-around, this happens:

    * edit to satisfaction
    * snapshot
    (time goes by)
    * edit some more (on purpose, not realizing it's "final")
    (time goes by)
    * make an inadvertent or test edit, or just decide this round of edits not good.
    * notice and return to snapshot, thus *losing* previous round of on-purpose edits.

    In case the point still isn't clear: having a snapshot doesn't do any good unless you know:
    * whether changes have been made since the "final" snapshot, and
    * whether those changes were on purpose, or inadvertent.
    and often "we" *don't* know those things.

    Rob
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • 1
    I don't want to beat a dead horse, but I would really appreciate this feature...

    Marking as Final - And more importantly "Locking" from further edits preventing accidental edits without "unlocking" MAKES GOOD SENSE. It's a good idea!

    Of course there are alternate methods that are sort of substitutes, but they don't Lock the image.

    Like Rob said: ""Snapshots DO NOT protect from accidental further editing (nor does any other method of marking a photo as final). - you can accidentally edit, further, any snapshotted (or marked) photo, and never know you did it, export it, send it to client, and *maybe* one day in the future, realize you did it, but maybe not. That's not "protection", in my book.""
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • What if users could create new custom metadata tags, one of which could be "FINAL".

    Users could then use this specially-made custom metadata tag for only the images they want to deem as final.
    • SImply tagging files as "FINAL" is the easy part. e.g. a simple (possibly non-exporting) keyword will do it.

      So, it seems to me, it's the locking part that is the biggest subject here.

      PS - I use a label for "FINAL", instead of a keyword, so it's visible in the thumb.

      Don't get me wrong - I'm a big-time supporter of custom-metadata, since one may want to add a to-do note if *not* final, or add some finale notes if *is* final..., which is also easy enough to do with CustomMetadata, *but* that metadata needs to be promoted to first-class citizen in order to be a thoroughly satisfying solution - e.g. saved/read from xmp.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • I was recently shocked to find a bunch of photos missing (I know I inadvertently deleted them when I was working on something). Thankfully, they were in the recycle bin. But it made me realize another aspect of locking that is needed, along with the ability to protect from inadvertent changes to existing images, we need:

    * Protection from inadvertent deletion, especially of locked images.

    I realize that Lightroom can't stop you from doing whatever you want to files in the OS, when Lightroom isn't running..., but it should be able to detect "missing" files (fairly promptly) - and there should be a distinction between missing, and offline:

    * Missing: drive is online, but photos are gone.
    * Offline: Drive is not mounted, that's why photos not present.

    This help would be appreciated by all fallible humans, but would have even more value to users who don't understand that Lightroom doesn't suck images into itself when importing. I've helped more than one user recover, who deleted all their image files after importing, thinking that Lightroom had them already...

    Rob
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • I haven't read back through the whole thread today, so apologies if this has already been posted, but to avoid accidentally deleting images, you may be interested in the PhotoSafe plug-in http://regex.info/blog/lightroom-good...
    • I am familiar with PhotoSafe - it protects from catalog removal, but not disk deletion. Worthwhile to be sure, and I use it, but hopefully Adobe will take it all the way, since a photo in the catalog but not on disk is a photo you can't edit or export - which is about as much fun as a dead puppy... Likewise, for corrupted files: having them on the disk isn't much fun if they can't be read...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • 1
    I think it would also be nice to see a feature where after export there was a little flag or something of the sort to show you have now exported the image. I work on series of photos over time which I export to lots of different locations and it is often a bit of a job to remember what i exported when and where. To have a feature where you could quickly glance to see the last date and location if you have previously exported the image before would be very useful
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • 1
    Locking (from editing, not just deletion, and at the virtual copy level) would definitely be a good idea that would complement the feature under discussion nicely.

    With LR's batch processing abilities, it';s all too easy to accidentally make adjustments to images where you want to preserve the current edits.

    It would also be useful to be able to search for 'finished' photos -- and I've already used up all my colour labels for other things
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • 1
    I think most of the groundwork for this is already in Lightroom. There are virtual copies, softproof copies... all's missing is a final copy.

    A final copy could be locked for editing similar to the way softproof copies work. If you want to make a change, you get prompted.

    There is already the ability to filter by virtual copies, so similarly you could filter by final copies.

    Can we hope for this in Lightroom 5 Final, pretty please?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • I’m Sad, but hopeful.
    1
    This reply was created from a merged topic originally titled
    Lightroom: Ability to "Lock" Final Versions of Images.


    Feature Request: Ability to "Lock" Final Versions of Images
    I know this is not new (people have been asking for years), but LR5 is so feature-rich that the lack of locking capability is now my biggest frustration.
    Lightroom is now like a vast library in which the mis-shelving of a book effectively means that it will never be found, so it's as good as gone forever. There are so many ways to "lose" an image in LR. I can accidentally change its flag status, or its color/star rating. I can accidentally remove it from a collection. I can accidentally delete a snapshot or virtual copy. In the most extreme case, I can even accidentally remove it from the catalog. Admittedly, some of these things are hard to do, but they still can be done (for example, you think you're removing a reject image from the catalog, but you've accidentally selected an image you want to keep). It's even more worrisome for the many things that can be done with a single keystroke or mouse click (such as changing the star rating). And to reiterate a key point, no amount of backing-up my catalog and image files to multiple external drives will save me if a carefully selected and edited "pick" accidentally gets identified as a "reject." Once the erroneous attribute is set, I'll never see that image again. It's as good as gone.
    Please, Adobe, help save us from our own inadvertent keystrokes/mouse clicks.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • It's funny to see that this feature has been requested over three years ago, and it seems to have a lot of votes in its favour.

    Is it gonna be under consideration for another three? Just wondering...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • A simple toggle "lock" to prevent any edits or deletion plus the ability to "unlock" would be a good start.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • 1
    This reply was created from a merged topic originally titled
    Facility to "lock" an image preventing further edits or deletion.


    Recently started using lightroom and would like the facility to "lock" an image so that no met edits can be done nor can it be delete. Objective is to stop me doing stupid things to a finished image e.g. include whilst syncing a group of images or including in a mass delete. I've asked on the forum and been given workarounds but it does seem a feature that many would like.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • Reminder: the problem is -

    How to keep finalized photos from being inadvertently edited.

    Snapshots don't solve that problem - granted, they can help recover from the problem, once it's been detected..

    Cheers,
    Rob
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • A snapshot does not "help recover from the problem", it restores the image with a single click. Also, if the image has been violated the snapshot will no longer be highlighted.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

  • 1
    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.

    Rob
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned