Now that you’ve been getting your ebook ONIX flowing to BiblioShare, you’ve no doubt noticed the data quality reports that BiblioShare sends back to you. While BookNet is your first line of support for BiblioShare, we’re going to break down how you can interpret those BiblioShare reports as they relate to your ebooks on CoreSource.
First, you should know that BiblioShare Quality reports have a flaw in that they cannot currently separate digital and print products and therefore will cite digital products for “print only” metadata problems. The good news is that these citations are easily identified. For example, digital files have no weight, dimensions or barcode location, so when you receive errors of this type you can ignore them.
The current best practice is to leave physical product description fields blank for ebook metadata files. It is important to note that while the balance of the citations represent best practices in North America for metadata, not all of these are currently supported by CoreSource and some best practices for the digital supply chain at large remain undefined. In light of this, our recommendations in this tutorial are real world compromises for using the BiblioShare Quality report in conjunction with CoreSource metadata for ebooks.
BiblioShare report snapshot: Aggregation Processing Thresholds
| Threshold | Target | % of Records | Pass |
|---|---|---|---|
| Canadian Contributors (Datapoint) |
>0.10 |
>98% |
Y |
| Canadian Product Availability (Datapoint) |
>90% |
>0% |
N |
| Canadian Price (Datapoint) |
>90% |
>100% |
Y |
The Canadian Contributor status ensures that your ebooks are loaded onto 49th Shelf, a free sales and marketing initiative that contains buy links to etailers where your ebooks are for sale. If you have 100% Canadian authored books and want to take advantage of the 49th Shelf opportunity, you’ll want to ensure that the Canadian Contributors datapoint shows this in the BiblioShare Aggregation Processing Thresholds.
To identify which books are missing Canadian authorship, please log on to your BiblioShare account to get access to the data. To retrieve your login information and for assistance running or interpreting your BiblioShare reports, please contact BiblioShare. For assistance specifying Canadian Contributor metadata in the CoreSource User Interface or metadata template, please contact our Digital Services Coordinator.
The Canadian Product Availability threshold is looking for a Product Availability Code, which CoreSource supports through incoming ONIX, but not yet in the metadata template. Canadian Price is important data to include in all of your ebooks as well.
Let’s look at some common errors and warnings from the BiblioShare Quality report in relation to CoreSource’s handling of ebook ONIX. The text below each error describes the actions you need to take to correct the BiblioShare errors and warnings.
BiblioShare report snapshot: Errors & Warnings
| Field Name | Type | Rule |
|---|---|---|
| PR.2.7: ISBN-13 | Warning | Continuing to supply an ISBN-10 in data feeds is recommended when a product has a 978- 13-digit ISBN. |
Please disregard this warning. CoreSource does not support ISBN-10 at this time. The 13-digit ISBN is widely used and preferred by all retailers/ distributors. The 10-digit ISBN will eventually be phased out and no longer used or accepted.
| Field Name | Type | Rule |
|---|---|---|
| PR.2.10: Barcode indicator | Warning | Barcode is required. |
Please disregard this warning. CoreSource currently does not support barcode metadata.
| Field Name | Type | Rule |
|---|---|---|
| PR.19.4: Name code value | Warning | Amazon currently requires the Publisher composite to include the NameCodeValue tag if the Imprint composite is not present or does not include this. |
NameCodeValue is optional and only needed if you have a blank imprint field. Imprints are set up at an account level, if you have new imprints to add, please contact our Technology Specialist to get them set up. Please note, not having an imprint set up at account level will result in ingestion failure when attempting to ingest a file under that imprint.
| Field Name | Type | Rule |
|---|---|---|
| PR.24.22: Product Availability – Supplier | Warning | Avoid using AvailabilityStatus — PR.24.22 Product Availability should be used, in conjunction with Publishing Status, instead of PR.24.21 Availability status code. |
CoreSource supports Product Availability only via incoming ONIX, but not yet in the metadata template. If you are using the metadata template, you can support Availability status code (which is required for specific etailers) and Publishing Status. If you send ONIX, please also include Product Availability.
| Field Name | Type | Rule |
|---|---|---|
| PR.13.1: BISAC Main Subject category | Warning | A BISAC main subject code is required in all records. |
It is essential to declare a Main BISAC Code in your metadata, so you’ll need to add this to your metadata To learn how to include main BISAC code in your metadata, click here to read our tutorial on the subject.
| Field Name | Type | Rule |
|---|---|---|
| PR.24.18: Returns conditions code type – Supplier | Warning | BISAC coded returns information is expected on every product. |
Please disregard this warning. CoreSource does not support this element, and it is not required in ONIX.
| Field Name | Type | Rule |
|---|---|---|
| Discount Code Composite | Warning | Discount information is expected by trading partners and should be conveyed using codes which a trading partner will look up alongside a list they are provided. If discount information is not relevant disregard. |
DiscountCoded is supplied by CoreSource, as well as DiscountCodeType and DiscountCodeValue. Please use these fields only if they apply, if not, disregard the warning.
| Field Name | Type | Rule |
|---|---|---|
| PR.14.1: Audience Code | Warning | An ONIX or BISG Audience Code is required on all Active and Forthcoming titles. |
CoreSource supports Audience Code, so please include this for all titles. You can add Audience Code metadata in your metadata template, or via the CoreSource User Interface. If you require assistance, please contact our Technology Specialist.
| Field Name | Type | Rule |
|---|---|---|
| PR.22.2: HEIGHT Measure | Warning | A full set of measures is required on every available product. This file is missing MeasureTypeCode 01 for Height |
Please disregard this warning. Since ebooks are not physical products with fixed dimensions, it is best practice to leave this field blank.
| Field Name | Type | Rule |
|---|---|---|
| PR.22.2: WIDTH Measure | Warning | A full set of measures is required on every available product. This file is missing MeasureTypeCode 02 for Width. |
Please disregard this warning. Since ebooks are not physical products with fixed dimensions, it is best practice to leave this field blank.
| Field Name | Type | Rule |
|---|---|---|
| PR.22.2: THICKNESS (Depth) Measure | Warning | A full set of measures is required on every available product. This file is missing MeasureTypeCode 03 for Depth (Thickness) |
Please disregard this warning. Since ebooks are not physical products with fixed dimensions, it is best practice to leave this field blank.
Please disregard this warning. Since ebooks are not physical products with fixed dimensions, it is best practice to leave this field blank.Please disregard this warning. PackQuantity is a print field that is not currently supported by CoreSource.Please disregard this warning. CoreSource supports the following : 01 (Proprietary Product Identifier), 04 (UPC), 06 (DOI), 13 (LCCN), 14 (GTIN), and 15 (ISBN). Normally, publishers use 15 (International Standard Book Number, unhyphenated, 13-digits starting 978 or 9791-9799). Other codes are ignored at this time.Please disregard this warning. Media File Composite is not currently supported by CoreSource. However, this field will be added in the future. As of May 15, 2013, the release date has not been announced. We will circulate new information as it becomes available.How to find and fix missing metadata elementsTo take a look at your metadata for missing elements, you can run a report in CoreSource called the Metadata Extract report. This report is available in the Reports section of CoreSource. When you run the the report, select “All” dates, or filter results by a set time period. We recommend exporting to Excel, so that you can filter your metadata.
When you’re in Excel, click on the header row in the left-hand margin to select it. Select Data from the menu, then Filter > Auto Filter. This gives you drop down menus on each of the header columns, where you can filter your data based on a specific value, such as a misspelled publisher name or a blank field. With filtering, you can quickly take stock of your data, pinpoint issues to correct, or find missing elements.Metadata, Metadata, MetadataUpdating your book metadata is not just about fixing typos, it can lead to more sales! Remember, you can enhance, improve, and elaborate your metadata by adding reviews, awards, and fine tuning descriptions.If you have questions about digital product best practices, ONIX, or how CoreSource exports ONIX, please get in touch with our Technology Manager. For CoreSource support with the metadata template or the User Interface, please contact our Technology Specialist.
| Field Name | Type | Rule |
|---|---|---|
| PR.22.2: WEIGHT Measure | Warning | A full set of measures is required on every available product. This file is missing MeasureTypeCode 08 for Weight |
| Field Name | Type | Rule |
| PR.24.44: Pack or carton quantity – Supplier | Warning | PackQuantity is required on all current products. If it is unknown, a default value of “1” can be entered until it is known. |
| Field Name | Type | Rule |
| PR.2.7 EAN | Warning | Field is mandatory for Silver |
| Field Name | Type | Rule |
| Media File Composite | Warning | PR.16 Media File Composite is required for all active titles, and recommended for all titles. |