The first step in publishing your eBooks and other resources with CloudPublish is to upload the source files. These take two forms:
- The actual item to be published, such as an eBook or eJournal issue
- Metadata, i.e. data describing the item
These correspond to the following files:
- An ePDF plus a JPG or PNG cover file
- An ONIX XML file (for eBooks) or CSV file (for eJournal Issues and eJournal Articles)
Multiple items can be described in a single ONIX or CSV file.
Note that eChapters are not listed above. These are derived from eBooks, and are created within CloudPublish using the API. The cover will be the same as that of the eBook from which the eChapter is extracted. Additional metadata is supplied either through the API or by uploading CSV files (please contact your account manager for example CSV files).
Note also that eJournals do not have a source file; these are described in CSV metadata only. An eJournal is a container for eJournal Issues and eJournal Articles, both of which must have source files. An eJournal Article can relate to (i.e. be part of) an eJournal Issue and/or an eJournal. In order for the relationship to be described, you must create the eJournal first (which will generate an eJournal ID), then create the eJournal Issue, supplying the eJournal ID to create the link. Finally you can create eJournal Articles, supplying both the eJournal Issue ID and the eJournal ID that were generated in the preceding steps.
Cover files can be in JPG or PNG format, of high resolution (e.g. print resolution) and should ideally be in a consistent aspect ratio. Do not include crop marks etc, as the file will be displayed as uploaded. The only modification made by CloudPublish is to produce "thumbnail" and mid-size versions suitable for web display.
Covers are required because the first page of your PDF may not be the cover of the eBook. It is best if the first page of the eBook is the first printed page of your printed book, and not the cover. In this way, page numbering in the online version can line up correctly with page numbering in the print version. This is achieved by supplying (in metadata) the number of pages of introductory / front matter (ExtentType 03 in the Extent element, in ONIX). These pages will be listed using Roman numerals, and then the next page will be listed as page 1. If no front matter extent is given, then the first page will be page 1. If this is not also page 1 in your printed edition, then page numbers shown on-screen may not line up with the page numbers in your book. This could present a problem for someone following up a reference to the print edition, but will not present a problem for the Table Of Contents generated by CloudPublish.
Your PDF should essentially be the same as for print, but without crop-marks. Fonts should be embedded but text should not be turned into graphics, and the PDF should comply with the standard Adobe 1.4 specification.
Importantly, you should include PDF bookmarks / links within the file to mark the document structure. These will be read by CloudPublish and used to generate the Table Of Contents. These bookmarks can be nested to produce a multi-level Table Of Contents. The inclusion of such bookmarks is the main aspect of what are called "ePDF" documents. No other interactive / extended content (for example forms) will be read by CloudPublish, and the inclusion of any of this kind of additional content may delay or prevent conversion.
The PDF and cover files should be named according to the main identifier used in your metadata. For eBooks, this should be the ISBN, for example:
Do not include any spaces or dashes.
Metadata files can be given any name, but each new file should be uniquely named to avoid any confusion if we need to inspect a file for errors. You might therefore consider adding a timestamp to the filename. The file suffix will either be .csv for CSV files or .xml for ONIX files.
Your files should be uploaded by SFTP to the server "upload.cloudpublish.co.uk" using the credentials given in your Settings page on http://admin.cloudpublish.co.uk. All files should be placed in the "incoming" directory, and no additional directories should be created.
For more information about metadata, please see these pages: