View Single Post
Old 09-07-2022, 07:39 AM   #32
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,861
Karma: 30277270
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by chaley View Post
@un_pogaz's method doesn't use the algorithm to generate the sort. The template constructs an author_sort string using the sort values in the author table, then compares that to the author_sort for the book. In other words, it is checking that the book's author_sort is what the author table says it should be.
@chaley: that raises two questions:
  1. If the authors table has the 'definitive' author_sort value (assuming that's the one that gets altered in Manage Authors) why the need for an author_sort column in the books table - the definitive value(s) is/are available via the books-author-link table?
  2. But, how is it possible that the books table author_sort column can even acquire the 'wrong' value (other than by poking it into the db itself). If I fire up the MDE for one of Maddy St John's books I see my "St John, Madeleine" in the Author sort box on a green ground.
BR
BetterRed is offline   Reply With Quote