weezintrumpete Offline Upload & Sell: On
|
melcat wrote:
I doubt my scheme would scale to your shooting volume, but there are probably a couple of ideas you could take from it.
First, I extensively use the “select folder” feature in my cameras. If I'm shooting two different kinds of things, or I'm going on different trips, the images go in different folders, and I will if appropriate switch the camera back to using an earlier folder. Then, everything in one folder stays on the card (and nowhere else, not backed up) until I'm ready to postprocess it. This corresponds to your steps 1 to 4. Note that I have less to keep track of than you, because I probably remember which body I used for what, when.
Next, when I copy the files onto my computer (“ingest” it) all the files are renamed, and their file names are unique across my entire archive and have a “batch code” which corresponds to the folder. Once a file gets this name, it never changes. This file name looks like 202212_BATCH_007.CR3, where BATCH is a mnemonic batch code. Note that it starts with the year, month and batch code so that whatever folder the file ends up in it will be sorted that way when displayed sorted by file name. Two camera folders from the same month never have the same batch code.
On ingestion, I archive 800px thumbnails of every frame but after that am fairly ruthless in deleting crap. The thumbnails are useful to jog my memory about the sequence of events when captioning, or to get a different view of a bird or animal for identification purposes.
Once every folder on a card has been ingested, I can format the card in the camera. If it’s really important, I will wait until a macOS backup has run.
I use Capture One for my archive. Images are organised in folders on my drive; I drag them from the ingestion folder to the appropriate folder using Capture One (but if Capture One were to disappear, the folder hierarchy is still there, visible in macOS Finder). Folders are named by subject, not date; the date is redundant because of EXIF metadata and the file names. Notice that within a folder the images are sorted by month and then batch code, because of the form of the file names. A few images could be classified multiple ways, and for those I make an arbitrary choice for what will determine the folder, and place them in Capture One collections for the other attributes.
I think Lightroom, like Capture One, uses the SQLite database for its catalogue. I have no problem trusting SQLite, as it has been validated for avionics use and is super-reliable. It should have no problem handling records for millions of images, so I see nothing wrong with your decision to use a single Lightroom catalogue. I do run two for Capture One: one for bird photography, and one for the rest, but this is really for convenience....Show more →
---------------------------------------------
schlotz wrote:
One thing I find interesting is that there is no mention of using keywords in Lightroom. Very powerful option when implemented correctly. Unfortunately having gone down your current workflow path for as long as you have, just about any modification is going to require some significant work to restructure.
In your 'specific spot example': if you had added a keyword to those photos (that represented this spot) you could easily click on that keyword in the right panel and only those photos would be displayed. You could use the Library Metadata filter to then further refine that display list. EX) assuming you had added a keyword for night, clicking on it in the metadata at the top would show that spot where photos at night were taken. Lots of options in the metadata to choose from.
Keywords can be setup with a substructure as well. EX)Animals then a keyword can be placed within Animals for the type like dog, cat, eagles etc... ...Show more →
---------------------------------------------
melcat wrote:
Hierarchical keywords use Adobe’s proprietary XMP metadata extension. I think these days most other programs can read that, and write it through to the IPTC keywords, but I know for a fact DxO used to get that wrong.
The IPTC keywords field, which e.g. Flickr probably uses, is limited to 64 bytes, not even characters. (If you use diacritics, curly quotes or kanji, it will be fewer than 64 characters.) This will very quickly fill up when every level of the hierarchy is dumped in there:
Hierarchical keywords: Birds/Australian/Australian Magpie
IPTC: Birds, Birds | Australian, Australian, Birds | Australian Magpie
That’s already 60 bytes and heading for truncation with a longer bird name. As you can see, it also adds noise keywords.
This is why, when/if I move to keywords, I’ll avoid hierarchical keywords and instead use a controlled vocabulary, where the keywords are stylised or chosen from a supplied list. I might decide, for example, that "acn=" denotes an Australian common name for the bird and use the keyword "acn=Australian Magpie". Or I might use just two keywords: "Australian Birds" and "Australian Magpie".
I’ve put off designing such controlled vocabularies both because I don’t yet have enough images to need to, and because I might want to adopt someone else’s. This is one reason why birds are in their own Capture One catalogue – I can imagine adopting a controlled vocabulary from a bird observing society, but wanting to use a different one for everything else.
In the meantime, I just put the bird name in the Description (also known as “caption” in some software) and use Capture One to search/filter on descriptions containing that. It’s pretty fast, which makes me think it’s using full text indexing. I’d be surprised if Lightroom doesn’t too. Quite long descriptions are possible, they don’t require the XMP metadata extensions, and pretty much all software understands them.
OP may be better sticking with keywords, unless he has (like me) the scripting skills to create the keywords from the descriptions later. Just be aware of the interchange problems and keep the scheme as simple as possible....Show more →
Thanks to both of you.
@melcat - I really appreciate you outlining your workflow for me. While I think you're correct that some (much) of this doesn't necessarily apply to me, I did get some ideas, and your information about tagging is really helpful.
Just to make sure I understand about tagging - if I use the hierarchical way of tagging within Lightroom, it is not the most compatible going forward outside of lightroom, correct? Or at the least, I will lost the hierarchy? I *think* tagging is the right way to go for me, along with smart collections to assemble those photos into different easily-viewable buckets.
@schlotz - as it turns out, I did a half assed job of doing tagging back several years ago and abandoned it. I think it's the right way for me to handle this. I need to get more proactive about my library if I want it to be useable for retrieval, and this seems like the right way.
|