Another non-official fix for LR2's non-exporting keywords

Question

Just as Zak Beck's fix, this is NOT an official fix!<br /><br />I'm sure Adobe's fix will be out soon, but for those who don't want to wait and are a bit adventurous, here's my fix :)<br /><br />You will need a copy of your old LR1 catalog and your new LR2 catalog. This utility will read each keyword from the old catalog and apply the same setting to Include On Export, Include Parents and Include Synonyms in the new catalog.<br /><br />FAIR WARNING!!! This is not tested rigorously!!! I did this for my own catalogs, and it works on them. It passes LR's integrity check, opens fine in LR2 and I have checked around 30 (of 9000) keywords and they all seem to be correct now. However, PLEASE MAKE A BACKUP of your LR2 catalog prior to running this. You never know... Needless to say, this comes with no warranty whatsoever, use at your own risk!<br /><br />For the diligent, the source code is included, so feel free to make sure it does what I say it does :)<br /><br />If your still interested, here's what you need to do:<br /><br />1) If not already installed, install Java 1.6 or later.<br /><br />2) Download LRKeywordFix.zip from here: http://www.box.net/shared/tyylegbccg<br /><br />3) Unzip LRKeywordFix.zip<br /><br />4a) If you are on a Mac, move the file macosx/libsqlitejdbc.jnilib one directory up<br /><br />4b) If you are on Windows, move the file win\sqlitejdbc.dll one directory up <br /><br />5) run the command "java -jar LRKeywordFix.jar <path to LR1 catalog> <path to LR2 catalog>"<br /><br />For example: "java -jar LRKeywordFix.jar c:\backups\LR1Cats\mylr1cat.lrcat c:\LR2Cats\mylr2cat.lrcat"<br /><br />Let me know how it goes!<br /><br />Regards,<br />Kris

Answer 1

OK, so I've updated the tool now. This is what's different:
-Separate packages for Win32 and OSX
-Output is more informative now. Note the levels: INFO, WARNING and ERROR. INFO is just FYI, nothing went wrong. WARNING means something non-critical happened and the tool should continue to process. ERROR usually means a critical error happened and the tool will quit. Also, if a keyword from LR1 was not found in LR2, it will tell you so.
-I actually check that the LR2 keyword is the same by complete name, case sensitive. So, e.g., if LR1 keyword was 'Los Angeles^California^USA', the LR2 keyword must be exactly the same, not e.g. 'los angeles^california^usa' or 'Los Angeles^USA', etc. This may be a nuisance for some but I felt it was better to be strict here. If really needed, I can add an option to let the user choose how strict the tool will be.
Win32 package:
http://www.box.net/shared/54yyp6zuq4
OSX package:
http://www.box.net/shared/un61qc2gfg
/Kris