Hard-coded Identifier Keys
DaltonST,
Thank you for the excellent plugin. As I am trying to organize my library, both ebooks and paper-books, I have found your plugin a huge help. Most especially, as I try add and correct metadata, your plugin has been great. I am not completely Python fluent, but I have looked at your code, and I see you have put a lot of work into this tool.
Is there a reason that you hard coded the keys for the Calibre 'Identifiers' field / dictionary? When I try to correct or check the ids for my books, I often get confused between the lccn, loc_lccn, and the lc_authority_name. The lccn is the id for the author and the loc_lccn is the one for the book. The oclc and oclc-owi fields are more intuitive. Even so, I get tripped up trying to remember to use a dash for the oclc-owi identifier, but an underscore the the #oclc_owi composite column I have. In any case, I can pick the names for the #ddc and #lcc custom columns, but I can not pick any of the identifier keys. Why?
I am interested in hacking at, ... err, I mean editing, ... the plugin code to see if I could get the ids to take configurable parameters, but before I took a bunch of time at it, I thought I should ask. Is there some reason that I should not parameterize the id keys? Also, if I do get this working, are you interested in merging in a branch off the current 1.0.34 baseline code, or would this project just be a one off thing for my own use?
In any case, thanks for a great plugin.
cbedgar
|