View Single Post
Old 06-09-2019, 09:07 PM   #11
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,780
Karma: 30237628
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by Soap-dodger View Post
Thanks for your suggestion. However, I prefer to maintain all book-related information within Calibre, without recourse to external facilities and tools.
I was always a strong advocate for Open Systems, so having interoperating applications is second nature to me. I just don't get today's closed-shop/eggs-in-one-basket/walled-garden/ mentality. But I appreciate that's what most folks prefer.

Quote:
Originally Posted by Soap-dodger View Post
I understand that Calibre already separates author-related information into its own table, as is proper under standard database design. It's just that the permitted author information is so sparse. There ought to be a way to extend author-related information via custom columns, just as there is for book-related information.
Calibre is open source. It shouldn't be too hard to to create a private fork that had the specific Author columns you want, along with attendant maintenance functionality etc.

BR

Last edited by BetterRed; 06-09-2019 at 10:29 PM.
BetterRed is online now   Reply With Quote