View Single Post
Old 10-26-2014, 03:12 PM   #7
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
You can do a search for
Code:
identifiers:"=mobi-asin:"
The mobi-asin identifier is created by calibre when it imports an AZW3/MOBI (this only happens during the Add books process, using the first Add option*) with a non-null exth 113 field (the asin identifier). It is not saved as asin because asin creates a link to the product page on amazon.com, but the exth 113 field may be for a book from the UK or other foreign storefronts.

This is important because metadata fetching will download asin metadata but it will never import calibre's custom mobi-asin field.


tl;dr
If a book has a mobi-asin identifier, it is pretty much guaranteed that it came from Amazon, and certainly implies that the original format was either MOBI or AZW3.


* -- The second Add option is traditionally used when adding from another library folder, it imports the metadata from the metadata.opf which overrides fetching metadata from inside the book file itself.

Last edited by eschwartz; 10-26-2014 at 03:15 PM.
eschwartz is offline   Reply With Quote