keyword import format

[someothername]

Is there someplace where I can find out what the format is to import a text file with an hierarchical keyword list in it that will go into LR2?

Is there a (free) source of such keyword lists? I can build my own, but I understand there are some pretty extensive ones already compiled. I found two, one was for business organizational stuff and the other was for some obscure medical research area.

I've been pretty hit or miss on my keyword usage. Like a photo that has a dog and a couple cats in it gets dog and cat, but should probably have animal, domestic dog and cat. Which goes back to my first question, what is the syntax for showing an hierarchical key word entry? Animal/domestic/dog?

Thanks,
brandon

 

[Sean McCormack]

Use Tabs
Each tab indicates a child keyword.

Landscape
             Beach
                     Spiddle
             Woods
                     Roscahil

If in doubt use Export Keywords to see.

 

[someothername]

Use Tabs
Each tab indicates a child keyword.

Landscape
             Beach
                     Spiddle
             Woods
                     Roscahil

If in doubt use Export Keywords to see.

Thank you! I hadn't realized that was there. So, if I prepare a file like that, I can import it?

What happens if I have something like

Animal
    cat
    cats and dogs
    Dog
[...]
dog
    sad
dogs

and I want to replace it with

Animal
    domestic
         cat
         dog
         ferret
    wild
         coyote
         fox
         bird
            robin
            eagle

Would I lose "dogs and cats"? Would "dog" replace "Dog"? Is there anyway to automatically move the ones currently keworded with "dog" into Animal/domestic/dog?

 

[Brad Snyder]

Yes, you can import a prepared text file. And it will sync, as opposed to overwrite.

Here's an example of a commercial file for sale. (This snippet included as a 'fair use' to illustrate the idea). Credit: www.controlledvocabulary.com

[_CVKC v3.']
[©2''3-2''7 David Riecks/ControlledVocabulary.com]
[4/4/2''7]
[ACTIVITIES/ACTION]
<tab> [ACTION MOTION]
<tab><tab> action
<tab><tab> aim
<tab><tab><tab> {aiming}

There is no leading whitespace except <tab> characters.
[...] are excluded category headers, will set the Export keyword flag to false
{...}are synonyms

Be extremely careful of extraneous whitespace and or blank lines. (.e.g. carriage return with no content). That will crash the import.


I don't know how this will turn out when entered as a post. Edit, the tabbing turned out OK, readable.


As far as exporting synonyms, etc. I sent you to a reference site, in another thread on a similar topic.

 

[someothername]

Thank you!
Do I type <tab> or do I press the tab key? The export file I extracted has just tabs in those spots, with the keyword starting right after.

I'm on the controlled vocabulary yahoo list and while the price is not bad, I am thinking I want to create my own vocabulary.

I read that other reference you mentioned, and find it kinda disturbing that top level keywords would be dropped like that. However, I also am not sure that someone searching for a photo is likely to use a top level word like that. Is there a requirement that top level words be all caps is some kind of context? I see that in my own keyword list export that they are not. Is lightroom going to treat them differently because they are not all caps?

Yes, you can import a prepared text file. And it will sync, as opposed to overwrite.

Here's an example of a commercial file for sale. (This snippet included as a 'fair use' to illustrate the idea). Credit: www.controlledvocabulary.com

[_CVKC v3.']
[©2''3-2''7 David Riecks/ControlledVocabulary.com]
[4/4/2''7]
[ACTIVITIES/ACTION]
<tab> [ACTION MOTION]
<tab><tab> action
<tab><tab> aim
<tab><tab><tab> {aiming}

There is no leading whitespace except <tab> characters.
[...] are excluded category headers, will set the Export keyword flag to false
{...}are synonyms

Be extremely careful of extraneous whitespace and or blank lines. (.e.g. carriage return with no content). That will crash the import.


I don't know how this will turn out when entered as a post. Edit, the tabbing turned out OK, readable.


As far as exporting synonyms, etc. I sent you to a reference site, in another thread on a similar topic.

 

[Brad Snyder]

Thank you!
Do I type <tab> or do I press the tab key? The export file I extracted has just tabs in those spots, with the keyword starting right after.


Just press the tab key, (it's just so hard to format a post to show that)

I'm on the controlled vocabulary yahoo list and while the price is not bad, I am thinking I want to create my own vocabulary.

I read that other reference you mentioned, and find it kinda disturbing that top level keywords would be dropped like that.

[COLOR=#''''ff]Well that's why it's selectable. In [] it's not exported. Without the [] it is exported. For instance, I have top levels of

[LOCATION]
people

I don't want Location exported, I'll already know it's a location, by the context. I do want 'people' exported, because even if I know it's a specific person, a can also sort by people / no people. Note, I enter the excluded category headers [IN ALL CAPS] as a shorthand visible reminder that they're excluded from export.[/COLOR]

However, I also am not sure that someone searching for a photo is likely to use a top level word like that. Is there a requirement that top level words be all caps is some kind of context? I see that in my own keyword list export that they are not. Is lightroom going to treat them differently because they are not all caps?

[COLOR=#''''ff]No, see above, where I answered in the wrong place, but it's late and I'm not fixing it. The all caps is just a reminder. The thing LR looks at is the [...], that's what set's the no export flag.

In general I enter all keywords by default lower case. The non-exporting Category Headers (which are used only to organize the hierarchy) in all upper case, and proper names(People, Places, some things) with initial caps.
[/COLOR]

It's past my bedtime, if I'm spouting nonsense, sorry, just ask again.