Thread: [GUI Plugin] Derive Genres
View Single Post
Old 09-21-2014, 01:23 AM   #44
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by DaltonST View Post
The field name must be #genre. That is what is defined in the custom-columns table in metadata.db. Calibre knows it by that name and no other. The label that appears as the column name that you actually see can be anything that you wish. You can label the #genre column 'Title' or 'Tags' if you wish. The label is just that; a mere word that appears at the top of the column and in the embedded metadata of a book.

Historical Calibre design decisions regarding custom columns should be investigated in the Development forum. Plugins merely work within the existing design parameters of Calibre. Plugins are the tail; Calibre wags it. The Development forum is where you might seek answers about your generic issues with custom columns.
Calibre doesn't define the names of any custom column. And doesn't define a column called "genre" or "#genre". The only reference to "#genre" the calibre code is where it is used as example in a template function description. There are some instructions somewhere about how to handle genre in calibre. Those instructions probably suggest "#genre" as the lookup name for the custom column needed.

Because of the above, you can set the name used by the plugin for the custom column. Or, you can do like most plugins that us custom columns and allow the user to call it whatever they want and then set it in the plugin configuration.
davidfor is offline