Another Keyword question

Status
Not open for further replies.

dwphoto

Member
Joined
Aug 18, 2008
Messages
29
I have been struggling with some issues to do with keywords which you can see in some of my other posts.

My question - if I edit a keyword tag eg tick export but untick the other boxes - how do I get this info to stay with the keyword when I export the keywords to a text file?

I have found that when I export them, they default to being all ticked - which I don not want.

Anyone know this one ?

Thanks, Dean
 
Dean, I'm not entirely sure I understand your last sentence, but when you export the keywords as a text file the 'Don't Export' keywords should be enclosed in square brackets. [Don't Export Me]. I don't believe the other two options, Export Synonyms and Export Containing are tracked by the keyword text export process, (although I stand ready to be corrected if so.)

I'm assuming your last sentence means 'when I export them, (and then reimport) they default ....'
 
Dean, I'm not entirely sure I understand your last sentence, but when you export the keywords as a text file the 'Don't Export' keywords should be enclosed in square brackets. [Don't Export Me]. I don't believe the other two options, Export Synonyms and Export Containing are tracked by the keyword text export process, (although I stand ready to be corrected if so.)

I'm assuming your last sentence means 'when I export them, (and then reimport) they default ....'


Yes Brad, when I reimport the text file to another computer/laptop, the changes I made to the Export Synonyms and Export Containing Keywords have not been retained. The square bracket [dont export] is maintained.

Any ideas if there is a solution for this?
Thanks, Dean
 
No, not to my knowledge. I assume any reasonable SQL programmer could write something to extract / reload that data for you.

Time for a feature request I guess. Now that you mention it, it seems a glaring omission. My keyword strategy isn't that sophisticated, the [Don't Export] is enough for me. I never really noticed until you pointed it out.

Several folks here have done a lot more work with keywords than I have, maybe they'll have an idea....
 
That does seem like a strange omission doesn't it?

Unfortunately the only way I can avoid hierarchical keywords writing to my dng files when I update the preview and metadata, is if I untick the Export Synonyms and Export Containing Keywords boxes.
Although annoying, it is a work around solution. However this issue compounds the problem when I work between my desktop and laptop ie now I have to manually edit every single keyword...twice ! - ouch

If any keyword experts out there could help me I would appreciate it. Even just the ability to edit the keywords in bulk instead of individually would be a huge benefit.
Thanks, Dean
 
Dean, do you always uncheck Export Synonyms and Export Parents for all your keywords? If so, you can try running a couple of quick sqlite3 statements to set those flags to OFF in your database by running the following at the command line:

sqlite3 Lightroom\ 2\ Catalog.lrcat 'update AgLibraryKeyword set includeParents = '; update AgLibraryKeyword set includeSynonyms = ';'

What's happening on the command line:

* sqlite3: you'll need to download this;
* Lightroom\ 2\ Catalog.lrcat: The name of the Lightroom catalog, with spaces escaped via backslash;
* 'update AgLibraryKeyword: here we're telling sqlite3 to modify a field found in the table AgLibraryKeyword;
* set includeParents = ';': set the column includeParents to '
* ... and the final update statement does the same for includeSynonyms.

The syntax should be just about the same on XP as on OS X, so this might give you some luck. It is possible to more selectively set those values based on keyword, but it's not as clean. I have the sense that this is a global edit for you -- but if it's not, and this is something you want to sort out, it should be doable for specified keywords as well.

And, of course, any time you're mucking around with the database, work from a backup!

_Edit_: I should add that the above is specific to LR 2.x. The flags to include synonyms and parents are stored very differently in LR 1.x -- in 1.x there's a column called flattenedParams in table AgLibraryTag. This single field holds all three values, and I'm not sure if editing those values are as straightforward.
 
Thanks, Alan, that's the white knight I was hoping would contribute. My SQl's just about good enuf to fool around in one of my catalogs(with precautions), but not someone else's.
 
_Edit_: I should add that the above is specific to LR 2.2. The flags to include synonyms and parents are stored very differently in LR 2.1 -- in 2.1 there's a column called flattenedParams in table AgLibraryTag. This single field holds all three values, and I'm not sure if editing those values are as straightforward.
So, the upgrade from 2.1 to 2.2 DID some database structure changes! :!:
This make me wonder if it is a good idea to continue to suggest to some users having troubles to downgrade from 2.2 to 2.1 :roll:

Thinking twice, this may not be a problem after all as 2.1 is not aware of 2.2 changes, there will probably just be both datasets present in the database, one not being used.

Opinions?
 
Nope, Mark and Denis, you're right -- the DB structure between 2.1 and 2.2 are the same. I was of course describing differences between 1.x and 2.x, and I have no idea why I ascribed the old structure to 2.1. A typo, and a substantial one at that!

I've edited the original (again) to clarify.
 
schussman;351'4 said:
Nope, Mark and Denis, you're right -- the DB structure between 2.1 and 2.2 are the same. I was of course describing differences between 1.x and 2.x, and I have no idea why I ascribed the old structure to 2.1. A typo, and a substantial one at that!

I've edited the original (again) to clarify.
AH! Ooof! :o
Thanks for the update. 8)
 
Status
Not open for further replies.
Back
Top