Quote:
Originally Posted by Sunlite
Custom columns are mainlya way for you to store information for your books not fitting the standard columns. When they are created, they are empty. You can then fill them with your info.
"Column built from other columns" is a way to combine existing informations and make it available in searches and templates.
Too many columns of this kind can slow down your library, because the information is always calculated on the fly.
To use author_sort you do not need a custom column, that is already a lookup name
Edit: Maybe you could tell us what goal you want to reach? There might be a way there, you are not seeing right now.
|
Thank you. My goal is/was to create a custom column where I could use "Author sort" field as author's name. For that I wanted to use "author_sort" lookup name, similar to how Author(s) column "uses" "authors" one. But, now I see that's not possible, because these lookup-names are defensively not what I initially thought them to be.
Just to clarify. So, is it true that there's no way for me to have a column in Calibre which would use "Author sort" field instead of "Author(s)" one? Or it can be done applying some Python magic somewhere at least?