View Single Post
Old 10-26-2013, 03:34 AM   #9
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
Quote:
Originally Posted by st_albert View Post
Our experience is precisely as Hitch described.

AFAIK, no aggregator or distributor digs into the epub metadata for anything.

That said, if I really really wanted to include BISAC codes, or their human-readable equivalents, in the metadata, I would simply put it within the <dc:subject> tags like any other keywords.

We do use the <dc:subject> tags, although I am unaware of any software that makes use of them at the moment. Maybe Calibre? Kind of like the Voyager project; we send it out there, not knowing who is listening....

Albert
Hey, Albert:

Ditto, we use the subject tags, also, and the description tag; but like you we don't kluge the BISAC codes themselves in there. No point to it, as humans generally don't search that way. We use them for the theoretical Deep Web and because we think that it's likely that libraries my send out searchbots someday through the DB's looking for keywords, rather than BISACs which they can pick up from the actual metadata/ONIX input.

Best,
Hitch
Hitch is offline   Reply With Quote