Credo Reference will need metadata and data from you to publish your multimedia collection in Credo's Core Collection platform. This document provides guidelines on what Credo will need. For our purposes, “Multimedia Collections” refer to a group of images, videos, or audio which we are publishing independently of “book” format text. If you are looking for our standards which refer to images or video which are part of a book which is also being published by Credo (including supplemental CD-Roms or DVDs) – see our Credo Metadata and Data Standards: For Books and Textual Materials page.
Credo’s Editorial Department will be your contact for all data/metadata issues. Please contact This email address is being protected from spambots. You need JavaScript enabled to view it. with any questions or issues regarding data or metadata.
We need contact details for the person in your organization who will provide metadata/data.
Credo Reference’s FTP site is ftp://ftp2.credoreference.com. Please contact This email address is being protected from spambots. You need JavaScript enabled to view it. for your username/password.
All data should be put in the \incoming directory and an email should be sent to This email address is being protected from spambots. You need JavaScript enabled to view it. with the book titles and corresponding file name(s) when the data is there.
Credo requests that you provide metadata for each collection. Please provide metadata in spreadsheet form. See here for a template spreadsheet. For further information, please contact This email address is being protected from spambots. You need JavaScript enabled to view it. .
Credo converts all source data to DocBook 5 XML using a subset of elements available in all of DocBook 5. If you can provide DocBook 5 XML, please contact This email address is being protected from spambots. You need JavaScript enabled to view it. for exact specifications.
If you cannot provide DocBook 5, we prefer XML. If you send XML, please send the DTD or schema. If you also have ePub or PDF, please send that as well; we use it for QA and Support.
If you do not have XML available, we may be able to accept ePub, PDF, Quark, print or other data formats. Please provide all documentation about the data.
Please provide a jacket image for each collection if available. Credo uses a PNG with 166-pixel-width.
If your data is a collection of images, each file will need the following descriptive information delivered separately from the image file: Unique Title, File Name, Transcript (if available), Short Description or other accompanying text, and copyright information (if different for each image). This can be delivered either in XML or spreadsheet format. Please ensure that the file name given in the descriptive information is the exact same as the delivered file Including case, underscores, punctuation, and any other formatting).
When images are provided separately (for XML data, for example), they should be consistent with the RGB color standard. Images with any photographic content should be delivered as .jpg. Graphic images should be delivered as .gif.
Unless the media is embedded within the text in the delivered data, calls to media should contain the media file name. For example, a call to a video file with the name might look like this: video_1.webm
<mediaobject><videobject><videodata filref=”video_1.webm” format=”webm”/></videoobject><caption>This is the caption text.</caption></mediaobject>
If your data is a collection of videos, each file will need the following descriptive information delivered separately from the video file: Unique Title, File Name, Transcript (if available), Short Description or other accompanying text, and copyright information (if different for each video). This can be delivered either in XML or spreadsheet format. Please ensure that the file name given in the descriptive information is the exact same as the delivered file Including case, underscores, punctuation, and any other formatting).
Please deliver 2 versions of each video: a WEBM and an M4V, and a VTT file as defined below. All should use the same base file name with the only difference in file names being the extension (.webm /.m4v / .vtt). To comply with accessibility standards, we also require an accompanying WebVTT file which contains the captions. For more details on this format, please consult the W3C website on the standard. If you’re delivering XML along with videos, the XML should look something like this:
<mediaobject><imageobject><imagedata fileref=”aabb.m4v”/></imageobject></mediaobject>
And the file names should be:
aabb.webm
aabb.m4v
aabb.vtt
Credo works with a number of conversion vendors and would be happy to provide you with recommendations on vendors who can help you convert your data to Credo’s DocBook 5. Please contact us at This email address is being protected from spambots. You need JavaScript enabled to view it. for recommendations.