Problem Importing Keywords with jpg photos into Library

  • Thread starter Thread starter JMC
  • Start date Start date
Status
Not open for further replies.
J

JMC

Guest
I am a new and enthusiastic LR user working to migrate from iMatch, where I have kept my ~8',''' photos organized for the last several years. However, my last roadblock to being able to do that is the import of keyword information (or as iMatch calls them, Categories). Obviously it's critical that these transfer across seemlessly as they represent untold number of hours in sorting and managing the database.

The situation: Via an iMatch script I can successfully write the associated categories, including hierarchy, into an IPTC field of my choosing that is then included with the jpg file itself. I have done this into the "Keywords" field, with various combinations of special characters and/or spaces to denote hierarchy relationships or separate keywords.

Upon LR import: LR recognizes the presence of the keywords and pulls them into the metadata, but refuses to see them as anything except part of one continuous hierarchy.

Example: A picture in iMatch has two Categories associated with it, both of which are organized under a parent-->child hierarchy:
Trips --> Switzerland2''6 and Special --> Family --> Daughter

When written via script into the IPTC Keyword field of the jpg file, it looks like this: Trips.Switzerland2''6; Special.Family.Daughter
(note -- I can make the semicolon separating the keywords anything, such as a comma, space, etc. I have tried all.)

When imported into LR, it ends up looking like this under the left panel Keyword Tags area: Trips --> Switzerland2''6; Special --> Family --> Daughter
In the righthand panel under "Keyword Tags", I only see "Daughter" as this is at the bottom of the single stack hierarchy that was interpreted.

In other words: I have found no possible way for LR to recognize that there is in fact MORE THAN ONE keyword coming in, rather than always a single hierarchy stack or very long words with spaces, semicolons, whatever included in between.

I have tried every setting under Preferences-->File Handling, but those only give me options about when to tell LR to recognize a hierarchy step, not about what character to see as a separation between keywords themselves.

Final note: If I first open one of my picture files in Adobe Bridge and look at the IPTC field Keyword there, it looks perfect. And if I go into that field and mess around a bit -- add a space, take away a space -- with in the end no change, then resave the file, THEN bring into LR, it works fine! I believe what is happening in this case is that Bridge is correctly interpreting the Keyword data from the file, but then is writing it into an XMP area that I can't see. LR must then read the XMP area in preference over the IPTC are upon import.... But -- if Bridge can read the original IPTC line correctly, why not Lightroom?!

Bottom line question: What format or special character or special trick must be used for multiple keywords in the IPTC Keyword field so that Lightroom will correctly recognize the multiple keywords upon import?

Thank you!

JMC
 
LR imports and exports hierarchical keywords using tabs. If you want the hierarchy Trips --> Switzerland2''6 and Special --> Family --> Daughter then the input file should look like this:

Trips
->Switzerland2''6 and Special
->->Family
->->->Daughter


where each -> is represented by a tab character. I don't know if that holds true for keywords embedded in an image file but for a straight import of keywords this is how you get hierarchy in. I hope that helps! :)
 
I am able to see multiple keyword trees in LR 1.3 after importing from IMatch 3.6 (latest update). E.g. in right panel I would see: Switzerland2''6, Daughter. In left panel, I see both hierarchies checkmarked for the image.

I do use DNG so can't say if this works for jpg.

In LR, under Edit > Preferences > File Handling, I've checked Treat '.' as keyword separator. In Imatch, I use the Copy categories/keywords to IPTC script to copy IMatch keywords to IPTC. Also I tell IMatch to enable dot notation.

Hope this helps.
 
Follow up to earlier reply. I've discovered that LR seems to import keywords ok on initiial import because it seems to read from the XMP fields used by IMatch which have values such as xxx.yyy.zzz, but LR writes back values of zzz to those fields. LR uses a different area to store its keyword hierarchy which isn't used by IMatch.

If you (or anyone else) has been able to successfully sync keywords between the 2 programs, I'd like to hear how.
 
JMC:

I suggest you look at one of your files w/ a tool such as exiftool to see what's actually happening. Compare the files before and after making the changes in Bridge and you should be able to see what changes Bridge has made to the file to make it import correctly in LR. If it's not simply a character substitution, you should also be able to use exiftool to make the changes in a batch mode. Exiftool is a bit tricky to learn, but well worth the investment, IMHO.

Would be interested in a report back as to what the changes are. Cheers,
 
If you don't want to dive too deeply into exiftool's command line interface, a couple of similar GUI oriented tools are:

XnView
PhotoME

I believe they're both freeware. I can't testify to their completeness vs. exiftool (as Bruce says, that is the gold standard) but they're typically enough for my purposes.


....brad s
 
Status
Not open for further replies.
Back
Top