Keywords to collections and vice versa.

Status
Not open for further replies.

someothername

Active Member
Joined
Apr 3, 2008
Messages
272
Location
Missouri
Lightroom Experience
Advanced
I find that I'm often putting things in collection set structures that mirror my keyword hierarchy, for example, Plants > Flowers > Roses is in my keyword list as an hierarchy. I also have a collection set named Plants with a subset called Flowers and a collection called Roses. Within the collection I don't distinquish between the different kinds or colors of roses, while in the keywords I might easily add red or orange or climbing or some other descriptive term.

What I'd like to be able to do is work starting on either side of the Library module and transfer that work to the other side. For example, at the last earth day, I imported 674 photos that night. For the next one, what I would like to do is keyword all of them into an hiearchy that looks like this Festivals > Earthday > earthday 2''9. Then I'd go through and add more specific keywords to the images that contain acrobats, jugglers, singers, etc. When I'm done, it would make my life so much easier if I could right click on the keyword "Earthday 2''9" and have a pair of drop down menu choices available:

Add or create collection and collection sets from here up.

Add or create collection for this keyword only.

The first choice would look for the top keyword, Festivals, and add or create a collection set "earthday" under it and under that find or create a collection called earthday2''9 and put the keyworded images in that collection.

The second choice would look for a collection by that name and put the keyworded images there, and if such a collection didn't exist, would give me the opportunity to select a set to put it under.

This is important because it greatly improve the ability to organize both keywords and collections for later work.

What do you think? I put it in the Adobe list, but didn't have enough room to say that I'd want to be able to go both ways except through the title.
 
Can you explain why it's helpful to mirror the keyword structure in Collections, or vice-versa? What workflow problem does this solve for you?

Not the whole structure, just the top parts of the keyword hierarchies.

Thank you for the challenge, it made me open Lightroom and play around a bit. Both collections and keywords do essentially the same thing to the content of the Library grid, slideshow, web, and so forth. So in terms of workflow as a series of tasks carried out on images, it makes little difference whether I use a collection or a keyword to select the images.

One of the two things that led to my feature request was the statement I came across elsewhere on this forum that keywords are stored with the XML and in the database, but collections are stored only in the database. So if I lose the database, this feature would enable me to quickly rebuild collections.

The other factor is that I currently have a backlog of some 4',''' images that I've imported into Lightroom that are not yet keyworded or sorted out into collections. And I'm looking forward to the many thousands of film images I plan to scan in over the next few years.

My thinking was something like this: If I keyword this group of images as Festivals>earthday>earthday2''6 then I can go on to provide additional keywords like belly dancers, tie die, jewelry, candid and so forth as the image dictates. This level of detail is not something I'd want in a collection, because I was thinking of a collection as a higher level working group.

On the other hand, there are collection names I wouldn't want turning up as keywords in my exported files, such as "my family" or "8x1' prints". Perhaps more options ought to go in the drop down going from collection to keywords, "do not export" which would used the [my family] to keep it there for me but not export it.

So now that I'm thinking more about it, I'm wondering if there is any practical difference between them other than that keywords can be exported. I'm starting to think that maybe there shouldn't even be collections, just hidden and "smart" keywords.

In terms of workflow, what I'm struggling with at base is techniques for dealing with large numbers of images that are currently only organized by dates and some slightly descriptive folder name. Plus working out how to best identify my images for searchers and potential buyers. The single column keyword component is not very friendly to deal with when you are trying to shift things around, the scrolling goes out of control at the ends, and when expanded it gets unweildy to say the least.

I'm open to comments.
 
Keywords are basically enough for me. I use collections for much more ad hoc / temporary purposes.

I know John Beardsworth, a frequent contributor and guru here, has a very strong preference for collections for image management, particularly smart collections.

I'm interested in what he may have to say in this thread.
 
I'm a bit out on a limb here, but I find hierarchical keywords to be an utter pain, and keep getting into a mess with them. No matter how much I try, I always end up with the child keywords also appearing again at root level, eg when I re-import an exported file. Or the same child keyword will find itself in more than one hierarchy, usually because I've changed the hierarchy at some point, or on another machine.

The trouble is that I think we’re trying to make HKs do two things, boost keyword data entry, and speed up finding. Deep down I’m not convinced data entry and what is a reporting function belong together. So I've gone back to a flat structure, and make keyword entry as efficient as I can by having many more keywords sets and metadata presets - in 2 the latter also include keywords so I can target all sorts of IPTC fields in one hit.

As far as finding is concerned, I don’t see a hierarchy as helpful enough to overcome the inconsistencies I described earlier, so I do focus on smart collections.

For example, I might have a Collection Set for weddings, which contains a two line SC for &#822';keywords contains weddings” and &#822';keywords contains candid”, and similar ones for other aspects of the wedding. My flat &#822';candid” keyword therefore exists once in my catalogue and independently of the HK parent (in this case &#822';weddings”) which first caused me to add it to the catalogue - if I subsequently add &#822';candid” to a bit of street photography, that picture won’t find itself grouped with weddings and I won’t need &#822';candid” under two HK parents.

It’s worth saying I only build these SCs this for groupings when I actually need them, but I find this a better use of time than building a hierarchical structure in anticipation of needing the grouping. I also build SCs rather than using the Filter Panel because I feel that if something has caused me to look up a particular combination of keywords and other metadata, there’s a fair chance I’ll want to look them up again. So I may as well save the query as an SC and save myself time in future, and I can group SCs with dumb collections)

Another aspect is that your catalogue is rarely keyworded perfectly. In my own catalogue for example, older pictures of the Castlerigg stone circle in the Lake District might just have a single keyword &#822';Lake District” and other info in the caption or title, while more recent pictures of the same subject would have many more keywords. Let’s say I then have a need to find these pictures. Searching in keywords for &#822';Castlerigg stone circle” doesn’t give me all the pictures, while &#822';Lake District” gives me too many. Using a SC means I can look for &#822';keywords contains Castlerigg stone circle” or &#822';caption contains Castlerigg” or &#822';title contains Castlerigg”. So a SC returns more accurate results in many real world situations.

John

PS. As an aside, once I’ve made such a SC, I’ll then tidy up the keywords and make them more consistent.
PPS. I won’t say this is a black and white issue – eg I’d probably take a slightly different view if I shot species and could import a listing of Latin and common keywords
 
Very well put John. I relate to this logic very well.
Thanks for your post!:cheesy::cheesy:
 
John, I think you have nailed a way to go for Keywords vs Hierarchal Keywords in Lightroom, using this method. You should do a Video Tutorial to help others struggling with this, if you have not already!

Don
 
I'm a bit out on a limb here, but I find hierarchical keywords to be an utter pain, and keep getting into a mess with them. No matter how much I try, I always end up with the child keywords also appearing again at root level, eg when I re-import an exported file. Or the same child keyword will find itself in more than one hierarchy, usually because I've changed the hierarchy at some point, or on another machine.
I certainly agree with you here. I'm finding the same kinds of problems, not to mention that I often just type the keywords in the keyword entry place, not realizing I already have it in the list somewhere. But the idea of controlled vocabulary or standardized taxonomy of photo keywords strongly appeals to me.

Three feature requests:
1. On the "Click here to add keywords" box, make it less sensitive and allow use of the mouse to select, or require selection by pressing enter (esc to abandon). I find the behavior a bit too quick for me. I type a letter or two and a list appears with what I'm looking for somewhere in it. In order to select it, I have to very carefully move to the arrow keys and go down the list using the arrow keys, not something done elsewhere in the interface. I often end up with the wrong one.

2. On the search for keywords box, "filter keywords": After you type your basic search term, e.g. "bird" and in my current state of keyword list, what shows up is Animal>wild>bird and the singleton bird. But what I really want to do is see if ostrich is already there or not; or maybe I'm hoping the list of species I have under bird in the hierarchy will jog my memory as to what kind of bird is in the photo. But at this point I'm locked into the choices displayed. There's a triangle next to bird, but I can't click it to see what's under it, if anything. The new feature I'd like is to set up the results from a keyword filter so that I can drill down from the results shown after a search. Perhaps some visual indicator that more exists under a keyword.

3. Ability to select a proposed set of keywords prior to applying them. When in the keyword list, allow me to pick which which keywords or which parts of an hierarchy I'm going to apply. I have a photo of an eagle, I want to apply wild>bird>eagle, but I don't want to apply animal in this case because it's a sculpture. So, when I click on eagle, checkboxes show up for animal>bird>wild>eagle, but I can uncheck the animal one, and then scroll down and find (or filter and find) "sculpture" and click it, too. Now I can right click and apply selected keywords. Probably need a new box somewhere, perhaps just above the keyword list, that shows my proposed keyword additions. Definately need a way to cancel.

The trouble is that I think we’re trying to make HKs do two things, boost keyword data entry, and speed up finding. Deep down I’m not convinced data entry and what is a reporting function belong together.
I very much agree that there is confusion in this part of the user interface. The keyword tags, suggestions and sets are pretty clearly data entry, but the keyword list is a mixture, with reporting on both edges (check marks, minus signs on the left, triangles on the right) and a variety of input functions in the right click drop down box. I guess export is a report function.

I tried to suggest a way to make the keyword list a more powerful data entry tool in
http://www.lightroomqueen.com/community/showthread.php?t=3311
Basically, what I'm looking for is a technique I've often used in my own programming and is found in many computer programs where a many-to-many relationship needs to defined as the data input. Mostly you see this when you have a fixed list of things or attributes and you want the user to select one or more of them. One method is put checkboxes, and the user selects the ones wanted, just like you can go through and select photos by control-clicking on photos you want to select in the library grid. Another method is to display two list boxes and you select items from the left box and click an arrow to copy them to the right box or a different arrow to move them back. When you have everything you want in the right side box (for most western languages, the from box will be the left side, the to box will be the right), you click the done button.

In lightroom, since we're dealing with images as well as words, I want to see some kind of dual grid where I can pick and choose from the left hand grid of photos and verify that is what I want in the right hand grid before I say do it. Since words are also involved, I want a list of only the keywords associated with the images in the left hand grid displayed along side it and the keywords associated or to be associated with the selected images (with visual clues as to which is which) displayed alongside the right hand grid. When I click the do it button, I would still have to choose whether I want to add the new keywords to the selected images or if I wanted to change from the keywording set up on the left to the new keywording set up on the right.

The keyword list associated with the grid on the left would be unalterable -- just a display of the keywords that exist for one or more of the images, using the check mark and minus sign convention. The keyword list on the right hand side could in fact be the current keyword list, but needs to be set up with an additional visual marker that indicates which ones I'm about to apply once I click done.


So I've gone back to a flat structure, and make keyword entry as efficient as I can by having many more keywords sets and metadata presets - in 2 the latter also include keywords so I can target all sorts of IPTC fields in one hit.

As far as finding is concerned, I don’t see a hierarchy as helpful enough to overcome the inconsistencies I described earlier, so I do focus on smart collections.

For example, I might have a Collection Set for weddings, which contains a two line SC for “keywords contains weddings” and “keywords contains candid”, and similar ones for other aspects of the wedding. My flat “candid” keyword therefore exists once in my catalogue and independently of the HK parent (in this case “weddings”) which first caused me to add it to the catalogue - if I subsequently add “candid” to a bit of street photography, that picture won’t find itself grouped with weddings and I won’t need “candid” under two HK parents.

It’s worth saying I only build these SCs this for groupings when I actually need them, but I find this a better use of time than building a hierarchical structure in anticipation of needing the grouping. I also build SCs rather than using the Filter Panel because I feel that if something has caused me to look up a particular combination of keywords and other metadata, there’s a fair chance I’ll want to look them up again. So I may as well save the query as an SC and save myself time in future, and I can group SCs with dumb collections)
I like how you are using collections and smart collections and it appears to be a workable way to deal with the current lightroom keywording system. Thanks a bunch for explaining how you do it.

Another aspect is that your catalogue is rarely keyworded perfectly. In my own catalogue for example, older pictures of the Castlerigg stone circle in the Lake District might just have a single keyword “Lake District” and other info in the caption or title, while more recent pictures of the same subject would have many more keywords. Let’s say I then have a need to find these pictures. Searching in keywords for “Castlerigg stone circle” doesn’t give me all the pictures, while “Lake District” gives me too many. Using a SC means I can look for “keywords contains Castlerigg stone circle” or “caption contains Castlerigg” or “title contains Castlerigg”. So a SC returns more accurate results in many real world situations.

John

PS. As an aside, once I’ve made such a SC, I’ll then tidy up the keywords and make them more consistent.
PPS. I won’t say this is a black and white issue – eg I’d probably take a slightly different view if I shot species and could import a listing of Latin and common keywords
If all I shot were one kind of photo, say landscapes, then I certainly don't need very many keywords, and a flat list will work fine. But as I look toward making photos available to stock or art buyers, I want to be able to drop 2' or 3' "relevant" keywords on each image, and this is where I like the notion of an hierarchy that inlcudes the higher level things I might not think of at first glance. However, the way the hierarchy functions in lightroom at present is cumbersome at best, so for now I think I'll stick mainly to a flat list myself.
 
Last edited by a moderator:
Status
Not open for further replies.
Back
Top