02-08-2012, 08:58 AM | #1 |
Connoisseur
Posts: 51
Karma: 10
Join Date: Feb 2012
Device: none
|
Metadata best practices
First off, I'm sorry to barge in like this with post count all-of-1, but I've been in lurk mode for quite some time and I just couldn't restrain myself any longer.
With today's myriad options of obtaining eBooks, discoverability is an obvious boon. As with web properties, metadata may play a key role in this process. Title, author, genre, publisher, language and even subject and description seem logical candidates for enhancement. The subject tag clearly lends itself to keyword stuffing, but how do the different marketplaces respond to this? Do they even process/read/spider the subject tag? Do they penalize obvious mischaracterizations? The description tag can be used for the backcover text, praise, introduction, or a short summary that tells the marketplace exactly who this publication is aimed at. I'd like this thread to be a developing compendium of some of the wisdom on the subject of metadata that is present within this community. By exploring our common wisdom we can help improve the ePub standard while at the same time perhaps selling more books. Moreover, by being aware of the developmental distance between ePub and html proper, we can explore ways in which publishers and creators of eBooks are able to wrest back some control from almighty Amazon and Apple. I would like to invite everyone to share: * current thinking on the OPF metadata tags * ways to tweak individual tag data * experiences with metadata manipulation * our understanding of how metatags influence discovery * possible best practices suggestions Thanks for not tl/dr'ing! |
02-08-2012, 07:18 PM | #2 |
Addict
Posts: 351
Karma: 70000
Join Date: Jul 2010
Location: Australia
Device: ADE, iPad
|
This is a template Metadata info I always replace
Code:
<metadata xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:opf="http://www.idpf.org/2007/opf"> <dc:identifier opf:scheme="ISBN">9781234567890</dc:identifier> <dc:title>Book Title</dc:title> <dc:creator opf:role="aut" opf:file-as="Name, Author">Author Name</dc:creator> <dc:publisher>Insert Publisher</dc:publisher> <dc:rights>Copyright © Author Name 2012</dc:rights> <dc:format /> <dc:date>2012</dc:date> <dc:description>Insert Blurb Here</dc:description> <dc:subject>Humanities; sciences; social sciences; scientific rationalism</dc:subject> <dc:language>en</dc:language> <meta name="cover" content="my-cover-image"/> </metadata> |
Advert | |
|
02-09-2012, 12:06 PM | #3 |
Enthusiast
Posts: 38
Karma: 10
Join Date: Nov 2010
Device: Sony eReader
|
Great post. I think this is worthy of a steady conversation, metadata always seems to be shifting in terms of application in the eBook world.
I have the same questions about keyword/search term metadata. Do online retailers actually recognize this field? I feel like it would be the "webby" way to present BISAC data, but it's unclear if it's worth the effort or not. Obviously, "discoverability" is the goal here, and it seems that custom keywords could lend a much more specific representation of the content than an archaic categorization system. I'd love to hear any/everyone else's experience + expertise on this one!!! |
02-09-2012, 03:34 PM | #4 | ||
Guru
Posts: 968
Karma: 2209358
Join Date: Nov 2011
Location: London, UK
Device: Kobo Aura, Kobo Aura ONE, PocketBook InkPad Color 3
|
Quote:
Does the epub 3 spec have better metadata support than epub 2? Quote:
It doesn't help that readers don't seem to display much of it. Why put it in the books if the readers don't show it? |
||
02-10-2012, 02:55 AM | #5 |
Wizard
Posts: 4,520
Karma: 121692313
Join Date: Oct 2009
Location: Heemskerk, NL
Device: PRS-T1, Kobo Touch, Kobo Aura
|
Actually, the metadata support in ePUB2 is quite good. The only thing that I am really missing is the option for series metadata. I know Calibre uses a custom metadata field, but it is not in the official specs.
The main problem is not the allowable metadata, but the reluctance by publishers to actually use it. The fields that are there, are mostly used by the library programs and not by the readers. The readers usually only support what they think the most useful are. |
Advert | |
|
02-10-2012, 04:03 AM | #6 |
Connoisseur
Posts: 51
Karma: 10
Join Date: Feb 2012
Device: none
|
Metadata are obviously not *completely* neglected by publishers, as marketplaces would have a hard time presenting their customers with content without the <creator> and <title> tags being filled in.
It seems that there might be chances for eBook publishers who DO take advantage of the complete ePub2 metadata possibilities, ie <subject>, <description>. This of course presumes that we as publishers have any idea of how the different marketplaces process these tags, or how this may affect discoverability and ultimately sales. I for one don't know these things, but I'm hoping some of the more seasoned members here do, and don't mind sharing some of their "trade secrets" |
02-10-2012, 01:38 PM | #7 |
Enthusiast
Posts: 38
Karma: 10
Join Date: Nov 2010
Device: Sony eReader
|
Exactly. One can include as much metadata as we want [100s of fields] but ultimately could end up being a arbitrary practice depending on what the retail outlets choose to support. I really, really hold out hope for broad keyword support...and I wonder if some retailers do consider this on their back end, similar to SEO for broader search engines, encouraging easier searching and discoverability of titles. A title could potentially be loaded with tens (or even hundreds) of tags that represent the content.
|
02-11-2012, 02:10 PM | #8 | |
Guru
Posts: 968
Karma: 2209358
Join Date: Nov 2011
Location: London, UK
Device: Kobo Aura, Kobo Aura ONE, PocketBook InkPad Color 3
|
Quote:
Are the reader devices the most important consumers of metadata, or is it the stores? |
|
02-13-2012, 12:46 PM | #9 |
Enthusiast
Posts: 38
Karma: 10
Join Date: Nov 2010
Device: Sony eReader
|
I would say retail/stores/libraries are the more important consumers of metadata, since this is how readers will discover new titles.
It's only assumed that an eBook should represent the same metadata a print edition could offer, no more, no less. |
02-13-2012, 02:02 PM | #10 |
Evangelist
Posts: 416
Karma: 14682
Join Date: May 2008
Location: SF Bay Area
Device: Nook HD, Nook for Windows 8
|
Having a retailer acquire their metadata from inside the ePub is problematic:
So I'd be willing to bet that most retailers are using a separate metadata feed from the files. Last edited by Jim Lester; 02-13-2012 at 02:05 PM. |
02-13-2012, 04:09 PM | #11 |
Guru
Posts: 968
Karma: 2209358
Join Date: Nov 2011
Location: London, UK
Device: Kobo Aura, Kobo Aura ONE, PocketBook InkPad Color 3
|
|
02-14-2012, 09:11 AM | #12 | |
Tweaker
Posts: 102
Karma: 324366
Join Date: Jan 2012
Location: Scotland
Device: Kindle / KOBO / PC
|
Quote:
It is also generally very definitive in comparison to "in-book" metadata, containing all pricing & currency rates, territory & licensing, description, publishing account id info, BISAC code(s), encryption status, and alternative formats & editions, all in addition to the standard/mandatory "in-book" metadata of; title, author & language. None of this extra data is really required for self-publishing. The last three, plus date of publication & ISBN (If required) are all you really need, and is all a retailer will expect, or indeed look at. Unless you are a publisher with a vending agreement/contract with a retailer, you will not be asked for, or be expected to provided, an ONIX file with your titles. Most upload processes for self-publishing usually have a facility to add the description text and other basic info during the upload. Amazon KDP being a prime example. You can add as much "other" metadata as you wish to your e-pub/mobi, what’s not required will be ignored. Tip I’ve noticed Sigil has a fairly extensive metadata headings list (Adv tab) if you want to add additional info for other reasons, such as self retail/distribution, or to credit contributors. Hope that helps |
|
02-14-2012, 06:44 PM | #13 |
Grand Sorcerer
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
|
I built a wiki page on ONIX. I may help distinguish this but for self published books that are sold by someone else this extra data is needed and the description is quite useful inside the ePub itself if the reader supports this option.
Dale |
02-17-2012, 12:05 PM | #14 |
Enthusiast
Posts: 38
Karma: 10
Join Date: Nov 2010
Device: Sony eReader
|
Do you have a link for your ONIX Wiki? I'd love to check that out.....
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Superscript best practices? | DiapDealer | ePub | 19 | 04-14-2012 04:28 PM |
Dialog/Quotation practices | DiapDealer | Writers' Corner | 15 | 12-13-2011 04:32 PM |
ISBN Metadata Best Practices | ccraig13 | Calibre | 2 | 11-03-2011 01:26 PM |
Best practices for margins | Mookiemon | ePub | 8 | 07-24-2011 07:13 PM |
DTBook - best practices | Nate the great | Workshop | 6 | 05-15-2009 04:06 AM |