View Single Post
Old 04-24-2018, 07:16 PM   #7
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,829
Karma: 30277270
Join Date: Mar 2012
Location: Sydney Australia
Device: none
@dwig - I have tried using the IDs column as you suggest, but because it operates at the book level I found it too much of a contrivance for my purposes. At the individual book level I prefer to use long text (header on the side) columns to hold the link.

Basically I would like the ability to click on an entity value (Publisher, Series, Location, Illustrator, AdminTag etc) in book details and go to its website, or a page in one of my OneNote or Evernote notebooks, or simply open a file; like I do for the Authors values in Book Details -- assuming I have the appropriate URI in the Manage Authors Link column

But I suspect that would require an additional column (Link) to be added to all the relevant database tables, which is why I assume its a big ask. Kovid has avoided the need to change the database schema for a very long time (maybe never). I've been down the path of changing users' managed databases, there be dragons down there

But thanks for the suggestion. It may help someone else.

BR
BetterRed is online now   Reply With Quote