BiblioShare Quick Start Guide
Welcome to BNC BiblioShare! This guide will help get you started.
Information on how to access data from BiblioShare can be found at booknetcanada.ca/bibliographic-data-distribution.
- 1 BiblioShare Basics
- 1.1 Deliver:
- 1.2 Process:
- 1.3 Zip Files:
- 1.4 ONIX:
- 1.5 Images:
- 1.5.1 Covers
- 1.5.2 Back Cover
- 1.5.3 Interior images
- 1.5.4 Author photos
- 1.5.5 BooksoniX Clients
- 1.6 Samples:
- 1.7 FTP Structure
- 1.7.1 FTP
- 1.7.2 BiblioShare.ca
- 1.8 Reports
- 1.8.1 Import Reports
- 1.8.1.1 Import Failed
- 1.8.1.2 Import Success
- 1.8.2 Biblio Update Report
- 1.8.3 BiblioShare.ca Reports
- 1.8.1 Import Reports
- 2 APPENDIX ONE: What is BiblioShare?
- 3 APPENDIX TWO: Manuals, Documentation and Resources
- 4 APPENDIX THREE: XML Validation
- 5 APPENDIX FOUR: BooksoniX Image Processing
- 6 APPENDIX Five: Coresource Image Processing
- 7 Contact: biblioshare@booknetcanada.ca
BiblioShare Basics
Deliver:
Deliver files to our FTP:
Ideally, the same file that is being supplied to a Canadian trade retailer, and at the same frequency. At a minimum every record should have a cover image.
Both BNC Webform and BNC BiblioShare's Account Admin offer options to load files to BiblioShare but these actually move files to our FTP as described below. In the case of Webform, image files are named appropriately with the product's ISBN as part of the service. If you are submitting files using BiblioShare's Account Admin you should follow the naming conventions described below.
Process:
Files are automatically processed when delivered taking into consideration the options for naming and file type:
All files must be left in the appropriate sub-directory. No files are automatically processed from the top directory.
All files must carry an appropriate extension for it's sub-directory if it is to process (detailed below), here's an overview:
"onix" sub-directory: onix files carrying an .xml extension
"image" sub-directory (and it's sub-directories: "interior" or "author"): web enabled images – generally .jpg extension
'sample" sub-directory: text based files as either .pdf or EPUB files
The sub-sub-directories below "image" directory support simplified naming options giving you more flexibility (detailed below).
The following is true for all 'image' and 'sample' files loaded to our FTP:
All files loaded MUST begin with a valid ISBN. We prefer and recommend ISBN-13 but we will also accept ISBN-10. (Webform automatically provides this.)
We prefer and recommend ISBNs without dashes, but hyphens are ignored if included. If the first 10 or 13 numbers are a valid ISBN-10 or 13 it can be processed.
See the heading FTP Structure below for a detailed explanation of our FTP site.
Zip Files:
Our automation will open zip files and process their contents. Zip files are recommended for supplying multiple images files but are otherwise optional. There's no recommendation on their naming convention other than uniquely named files that contain a company name are always recommended.
ONIX:
ONIX files are loaded to 'onix' sub-directory
All ONIX files must be loaded to the sub-directory 'onix' and carry an extension of .xml
Recommended naming: publishername_delta_yyyymmdd.xml
We automatically apply a unique name to every file for processing, but submitting files with identical names will affect our archiving and ability to troubleshoot problems. We strongly recommend that all ONIX files arrive with a unique name.
BiblioShare archives the original ONIX files for several months and has special processing rules for archiving "FULL" and "DELTA" files.
You should only supply a file name with "_full_" in it if represents ALL records associated with this account
Submitting multiple files at the same time with "_full_" in them may result in processing problems. The last submitted file with "_full_" can bump the previous files out of the processing queue as it's assumed to represent all available records.
Submitting files with "_delta_" in the name shows that it is an update file.
Files with neither "_delta_" or "_full_" are assumed to be update files.
Images:
Images are loaded to 'image' directory
Image files are front cover images, back cover images, interiors spreads and author photos. The image folder sub-directories 'interior', 'back' and 'author' allow looser naming conventions detailed below.
All files loaded to the 'image' directory or it's three sub-directories must be named by ISBN as detailed above and detailed in each section. The following defines what can be processed in these directories.
JPG, TIF, PNG, and GIF formats are accepted
Image files must carry their extensions.
RGB colour space (No CMYK)
All files are converted and stored in the JPG format.
Our primary image is maintained in the same size as you provide
We want images up to 2500 pixels on the long side, but at a minimum they should be at least 500 pixels wide.
EDItEUR's current recommendation (based on retailer requests) is:
Short side: Minimum 1000 pixels
Long side: Maximum 2500 pixels
All images must start with a valid ISBN-13 or ISBN-10 as below in the file name in order to be processed. Our processing will assume an image is a cover if it's not processed as an Interior or Author type as below.
If your file naming convention is ISBN based but does not follow the model described below, see the instructions for the sub-subdirectories \image\interior, \image\author & \image\back as they process any ISBN named files to the type of the directory name. If you're still unsure or your automation can accommodate multiple directories, ask.
Covers
All cover images must be named by a valid ISBN 10 or 13.
Example: 9781234567890.jpg
In general, you should be sending BiblioShare the same images you send to Amazon, Indigo, etc.
There is no need to submit thumbnails as we will create a standard one.
Back Cover
All back cover images must
start with a valid ISBN-13 or ISBN-10,
follow that by the characters "back"
and can include other characters after
Example: 9781234567890_back.jpg
Using the image\back directory
Back cover images may be loaded to the sub-directory 'image\back'. The same naming convention applies, except you do NOT need to use "back" in the file name as any ISBN based file loaded to the directory 'back' is assumed to be a back cover image.
We do NOT currently offer access to this directory from the File Upload page in your BiblioShare.ca admin account.
Clients using BooksoniX should NOT use the image\back directory as the processing detailed in Appendix 4 below applies only to the "image" directory.