MobileRead Forums - View Single Post - What Features or Tools does Sigil Still Need Yet?

KevinH · 02-09-2021, 11:06 AM

I need help with understanding the most common way to assign a dc:identifier when it is an Amazon/Mobi ASIN under both epub2 and epub3.

So how does one properly set metadata when using an Amazon asin as an identifier:

Epub2

Code:

<dc:identifier opf:scheme="MOBI-ASIN">B005IEGK5C</dc:identifier>

Is that correct? Or is the opf:scheme set to "ASIN" or "mobi-asin", "asin" or something else?

And for epub3, which of these is most commonly used (and with "MOBI-ASIN", "ASIN", "asin" or "mobi-asin"?

Code:

<dc:identifier id="myid">B005IEGK5C</dc:identifier>
<meta refines="#myid" property="identifier-type">MOBI-ASIN</meta>

Or

Code:

<dc:identifier id="myid">"urn:asin:B005IEGK5C</dc:identifier>

or

Code:

<dc:identifier>"urn:mobi-asin:B005IEGK5C</dc:identifier>

or something else?

I would very very much like to keep this in sync with what Calibre uses when faced with this task under both epub2 and epub3.

So any help or guidance here would be greatly appreciated. As this is xml, case definitely matters so please be specific.

Thanks to anyone who has epub2 and epub3 versions of mobis in their calibre library who can check on this for me or from book developers on what they typically used when faced with the same thing.

02-09-2021, 11:06 AM	#147
KevinH Sigil Developer Posts: 9,268 Karma: 6565382 Join Date: Nov 2009 Device: many	Need Help on how to use ASIN as dc:identifier I need help with understanding the most common way to assign a dc:identifier when it is an Amazon/Mobi ASIN under both epub2 and epub3. So how does one properly set metadata when using an Amazon asin as an identifier: Epub2 Code: <dc:identifier opf:scheme="MOBI-ASIN">B005IEGK5C</dc:identifier> Is that correct? Or is the opf:scheme set to "ASIN" or "mobi-asin", "asin" or something else? And for epub3, which of these is most commonly used (and with "MOBI-ASIN", "ASIN", "asin" or "mobi-asin"? Code: <dc:identifier id="myid">B005IEGK5C</dc:identifier> <meta refines="#myid" property="identifier-type">MOBI-ASIN</meta> Or Code: <dc:identifier id="myid">"urn:asin:B005IEGK5C</dc:identifier> or Code: <dc:identifier>"urn:mobi-asin:B005IEGK5C</dc:identifier> or something else? I would very very much like to keep this in sync with what Calibre uses when faced with this task under both epub2 and epub3. So any help or guidance here would be greatly appreciated. As this is xml, case definitely matters so please be specific. Thanks to anyone who has epub2 and epub3 versions of mobis in their calibre library who can check on this for me or from book developers on what they typically used when faced with the same thing. Last edited by KevinH; 02-09-2021 at 11:47 AM.