It's a workflow preference issue, and for my preference, I always like to know that my images are backed up prior to my working on them, as it provides me with peace of mind. Alternately, some of us looked to programs like IIP as they offered a one-stop solution prior to ingesting that allowed us to ingest and then proceed knowing that we have done what we need to do (backup our image files), but sometimes put off or forget about as we move ahead. Yes, it can be handled outside of LR, but if we want our backups done up front, as I would suspect is a good practice (and my personal preference), we have to leave LR and handle this backup process with other software. The issue I find frustrating is that Adobe offers you a variety of file handling features, like renaming and moving, when ingesting, so, to some of us, it would seem natural that they might offer to place the backups in a similar folder structure so we can proceed ahead knowing that we have taken appropriate precautions about managing and backing up our files before we begin working on them. Well, given the number of comments that I have seen over the years on this issue, I suspect that there are number of people in a number of camps on how they feel about this issue.
I also think it would be a pity if the option was ever removed (which I doubt will happen). Personally, I don't particularly need it to be given any attention (other than to change the date format of the folder name to numeric), though I acknowledge that other users do, and I suspect that there are long-standing feature requests to that effect still lingering on the official Adobe site. That's all I think it was ever intended to be, unfortunately some users wanted to use it as their one and only backup and so were frustrated by the fact that they couldn't control the folder structure that was automatically created. It was always expected that users would indeed take responsibility for backing up their important data (including, but not restricted to, image files), so this "second copy" option was included to protect the card contents while allowing the card to be re-used.
Thus two copies of the card data are created, which allows the card to be reformatted and reused if needed before the next "regular" system-wide backup is run. a copy of the contents of the source card. I do, but only in the context of what I believe was the original thinking, i.e.
0 kommentar(er)
