View Single Post
Old 09-21-2014, 12:06 AM   #43
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
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.
DaltonST is offline