View Single Post
Old 04-16-2011, 10:04 AM   #90
kiwidude
Calibre Plugins Developer
kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.
 
Posts: 4,731
Karma: 2197770
Join Date: Oct 2010
Location: Australia
Device: Kindle Oasis
Quote:
Originally Posted by ldolse View Post
Right - not sure how much more complicated that makes things. Anyway I think for this type of author search I don't think you need to worry about special handling for books being deleted/merged. While a user could certainly do it while those results are being displayed, a merge/delete isn't the goal in this case, just changing the metadata. Not sure if that helps any.
Its not a major deal but it is something I need to consider.

In fact I think there is another bigger issue and that is duplicate exemptions, which again are book based. If the purpose of a duplicate group for resolution purposes is to show all books for authors that have duplicates, then you won't want other books by those authors exempted out of it (or the groups partitioned because of it).

This all just confirms my thoughts that author based duplicate searching has to be considered "separately" in terms of the impact it has and perhaps how it should be presented.
kiwidude is offline   Reply With Quote