Embed Size (px)
Citation preview
Standards and CertificationTom Richardson
April 1, 2016
Three things to work on in standards
ONIX 3.0 is being used
BiblioShare has 46,856 ONIX 3.0 records from:• House of Anansi• Heritage House• Scholastic• Hachette• HarperCollins• and many more Canadian publishers
All eBOUND Canada clients data arrives as both ONIX 3.0 and 2.1 files.
Retailers can support ONIX 3.0
All major US retailers and support companies can accept ONIX 3.0 nowbut within North America prefer ONIX 2.1 unless there is additional data in the 3.0 feed.
Indigo plans to have support for ONIX 3.0 in place by early summer.
2.1 to 3.0 transition conundrums:
• Digital and Print data is handled differently
• ONIX 3.0 is more typically used to support the international digital supply chain.
For North American print products:
• Not much ONIX 3.0 data available
• What is available typically offers no advantage to the existing 2.1 feed
ONIX 2.1 is no longer a supported standard
• Code Lists unique to 2.1 are not updated
• Code Lists shared by 2.1 and 3.0 are updated for 3.0 needs only
• EDItEUR makes no provision to accommodate ONIX 2.1 logic in it’s planning
• Development designed to answer new needs can happen only in 3.0
ONIX 3.0 has structural differences in • Mapping
• Changes to data structure
• New data values to support
ONIX 3.0 supports change by supporting• Higher accuracy and less ambiguity
• Which has to be met through changing data practices.
Retailers using international data from multiple sources need accuracy and cannot tolerate ambiguity in their metadata feeds.
Mapping data
• A term used for when you take a piece of data from your database or dataset and transfer or “map” it to another system or standard.
• Mapping often includes conversion where a code value in your system is converted to be a different code with identical meaning in another system.
In the transition from 2.1 to 3.0 a shared code list usually means a mapping change, but not necessarily that the structure remains the same.
ONIX 2.1 Subjects
• List 26 – Main Subjects (P.13 Main Subject Composite)
• List 27 – Additional Subjects (P.13 Subject Composite)
• BISAC element (PR.13.1 BISAC subject category)
• BIC element (PR.13.2 BIC main subject category)
ONIX 3.0 Subjects
• List 27 Subject (P.12 Subject composite)
• Main subject flag (P.12.1 Main subject flag)
Work Identifier
• ONIX 2.1 puts the Work Identifier following the PR.7 Title information.
• ONIX 3.0 puts the Work Identifier in a new section within P.22 Related Materials
New data point required
• P.22.1 Work relation code (List 164) to describe the relationship the product and the work identified.
ONIX 3.0
is designed to solve
known problems
in ONIX 2.1
ONIX 3.0 is designed to support
international metadata by
removing ambiguity.
Series and Sets have migrated to
Title or Collections
Changes to the Title composite allow:
• Indexing Series name
• Indexing of Brand names
• ONIX 3.0’s integrated title block is supported by sequence numbers that control display.
• Title Statement, a separate element can support HTML.
Series and Sets have migrated to
Title or Collections
If the Series name isn’t integrated in the book title then use the Collections composite. It can handle complex layered entries.
No duplication of series entries
is required in ONIX 3.0 metadata.
Sales rights and market territory statements
Small changes to
• improve accuracy
• and remove ambiguity
A new value:
• P.21.10 Rest of World sales rights type code
• List 47 “ROW” code is not to be used in 3.0
Contributor Place
• 8 code values to describe Contributors– Citizen of
– Currently resides in
– Flourished in
– born / died / educated / formerly resided in
• And geographical coding for– Country
– Region
– Location Name
A Canadian author is defined in ONIX 3.0’s
Contributor Place as
• Code 08 “Citizen of”
• Country Code of “CA”
“Citizen of” should only be associated with a country code. You can repeat the Contributor Place composite and define other code values with their own geographical coding
International Standards Organization (ISO) meetings
• Work on an updated definition of ISBN continues
– Completion in a year?
• International Standard Text Code (ISTC)
– Can we change it to something we can use?
– A proposal for change has gone to ISO...
• ISTC has not been adopted because publishers don't really want it
• Retailers want it but make the links they need anyway.
– So maybe it's time to say what you do want –Watch for a call for use cases.
ISNI International Standard Name Identifiers
Most established (eg multi-book) authors have them now. You can just look them up.
This librarian site has an easy look up:
https://viaf.org/
Charis Cotter: 0000000074234353Maria Tippett: 0000000110849049Cheryl MacDonald: 0000000073846438
Erin Knight did not have an ISNI but did have a VIAF ID
List 44 option for 3.0’s Name Identifier
New BISAC Young Adult Subject Headers
Amazon and Indigo are ready to take them now
Start using them now, but regularly include them in feeds for a while.
Thema
Use has increased in BiblioShare 5 fold within the past few months with over 63,000 books in BilblioShare supporting a Thema main subject.
Indigo will be accepting them by July but will not display them.
BISAC to THEMA Converter
BISG is released a new mapping this week and BookNet will update our software next week.
Bibliographic Committee
Dates in Canadian metadata
Guidelines for enhance content
– HTML in ONIX
– Links in ONIX
– Marketing materials not in ONIX
Certification
BiblioShare Quality Reports
