View Single Post
Old 05-03-2011, 09:38 AM   #183
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 aznime View Post
I'm not sure how calibre comes up with the published year '2007'. However, from going through the whole log, I think the earliest publication year is '2009' from HarperCollins. Please see attached pic below.
The answer from my previous emails with Kovid on this is that Calibre now does a lookup to find the earliest publication date using the XISBN service, as part of the merging of results. This lookup is independent of the publication date values you see being displayed in the log. It does mean that the value you got from Goodreads for instance in this case is ignored and the date from XISBN is used instead.

Normally it isn't a problem as you would hope they all have the same result but sometimes I have found that you do get some weird results back from XISBN unfortunately. There is no way to turn off this behaviour AFAIK.

It does raise the question as to whether there is any point to the plugins retrieving a published date if it is being ignored. The one circumstance I can think where the pugin's publication date would get used is if the book has no ISBN but that would be relatively rare.
kiwidude is offline   Reply With Quote