Only a limited amount of metadata from the File Info makes it into epub metadata.
I don't have the list handy for CS5.5 but for CS6 we use the following under the "Description" Tab:
"title", "creator", "subject", "description", "publisher", "date", "source", "relation", "coverage", "rights"
I think your complaint from EPUBCheck is that you don't have a <title> element defined. which is required.
We've made a lot of important changes in EPUB since 5.5, you might considering downloading CC trial to see if it makes your workflow better.
As you're viewing this thread: Do you know if there's a way to script
additional XMP properties such that they will be added to ePub export?
Obviously it is possible to add XMP with scripting, but (in another
thread) I was unable to add it in such as way that it will appear in the
Do you happen to know offhand if this is actually possible?
If not, would you know if creating a custom XMP panel with the XMP SDK
would solve the problem?
Thanks (and sorry for diverting the thread somewhat),
No. We only generate a limited amount of metadata for EPUB2 and we grab that in a very simplistic way from the XMP. This did not change in CC.
The EPUB2 spec does allow more metadata to be added but I find it rather complicated to understand how to do this in a way that is effective, that is, whoever is going to read the metadata needs to know how you've coded it, right? There is a lot of stuff in the XMP and it is not clear how much of it should end up in the EPUB.
I'm interested in provding more flexibility in this area for CC.next but I'm not sure the XMP is necessarily the way to go.
Ah, good to get a confirmation of something I was beginning to suspect
-- that the ePub export metadata is not hardwired to XMP, rather
selected info is carried over.
I'll tell you what we need it for -- it's simply that when an ePub is
submitted to the iBookstore (this is still, for us, the target vendor)
iBookstore asks for a bunch of info, including BISAC codes, and quite a
lot of other stuff, and it would be nice if all this information could
be part of the InDesign file so that if any changes or edits are made
and an ePub re-exported, it doesn't all have to be keyed-in from scratch
when submitting the file to them.
Right now I'm finding that it's actually possible to create an InDesign
file that does not need any editing of the ePub file produced by
InDesign in an external editor (especially since we can attach a custom
CSS file) -- the only thing that prevents this being completely
self-contained is the metadata.
I would very much like to understand what your final metadata looks like after you've added it.
This is an area that I think should be improved but there is a range of options with a range of costs and I'd appreciate your input.
Can you contact me off-list at email@example.com at your convenience?
Oooh, now I'm getting skeptical. Can you copy/paste the top part of your .OPF file so we can see it?
It will look something like this:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<package xmlns="http://www.idpf.org/2007/opf" unique-identifier="bookid" version="3.0">
<meta name="generator" content="Adobe InDesign 9.1 Build 10" />
<meta name="cover" content="x203.png" />
You are selecting the optiion "Include Document Metadata" under the EPUB Export Dialog Advanced Tab, right?
I'm not sure what the problem is. The OPF has no metadata in it, and I've checked the "include document metadata" option. Does it have something to do with the fact that I've put this ebook together from an InDesign Book?
<metadata> <meta name="generator" content="Adobe InDesign"/> <meta name="cover" content="x191.png"/> <dc:title></dc:title> <dc:creator></dc:creator> <dc:subject></dc:subject> <dc:description></dc:description> <dc:publisher>PulpWork Press</dc:publisher> <dc:date>2013-06-27</dc:date> <dc:source></dc:source> <dc:relation></dc:relation> <dc:coverage></dc:coverage> <dc:rights></dc:rights> <dc:language>en-GB</dc:language> <dc:language>en-US</dc:language> <dc:identifier id="bookid">datvoo</dc:identifier> </metadata>