This presentation was given at ALA 2017 during the 11th NISO-BISG Forum, Delivering the Integrated Information Experience, by Brian O'Leary of the Book Industry Study Group (BISG)

1. Metadata Challenges in the
Publishing Supply Chain
© 2017, Book Industry Study Group, Inc.
June 23, 2017

2. Book Industry Study Group (BISG)
2
Mission Vision Values Objectives
To create a
more informed,
empowered and
efficient book
industry
To be
recognized as
publishing’s
primary
resource for
solving
problems
affecting more
than one part of
the supply chain
• Focus
• Shared
Solutions
• Results
Orientation
• Best in Class
• Collaborative
• Information
• Standards
• Research
• Community

3. BISG Objectives
Objective Detail
Information Establish BISG as the ‘information hub’ for the book industry
supply chain.
Standards Foster the development, refinement and use of standards that
improve revenue, promote product visibility, reduce costs
and ensure transparency across the book industry supply
chain in the U.S. and across global markets.
Research Shape the conversation about the current state and future of
book publishing by studying and communicating about
emerging topics, issues and trends that affect the book
industry.
Community Maintain relevance by growing a diverse membership base
that reflects the various segments and participants of the book
industry supply chain.
3

4. BISG efforts …
p Solve problems that increase costs, lower
revenues or block development of new models
p Ensure widely available, transparent information
that can shape decisions
p Improve the timeliness and accuracy of supply-
chain data (both provided and derived)
p Give everyone a voice in standards and best
practices
p Deliver recommendations that meet the needs of
most or all supply-chain participants
4

5. Challenges to supply-chain efficiency
p Mixed use of standards (ONIX 2.1, 3.0)
p Inconsistent use of standards
n Failure to apply best practices
n Multiple interpretations of ‘best practice’
p Customized feeds for data recipients
n Standards are not ‘standard’
n Requires every data provider to create custom
versions
p Lack a reliable metadata repository
5

6. Example: The ONIX 3 timeline …
2008 2009 2010 2011
2012
2013 2014
2015 2016 2017
2018
ONIX 3
development
starts
ONIX 3
released
(April 2010)
ONIX 3 update after
‘proofof concept’
implementation
Steering committee agreement
on 3-year sunset timetable
(Oct 2011)
ONIX 3 update
(Jan 2012)
ONIX 3 update
(Jan 2014)
ONIX 3 update
(Apr 2016)
Public announcementof
sunset plans
Supportfor ONIX 2.1
‘sunsets’;code list updates
continue for another year
End of ‘twilight’ supportfor 2.1
code lists; continued supportfor
codes shared with ONIX 3
ONIX 2.1 code lists frozen
with issue 36 (still usable;no
longer updated)
‘Making the business case
for ONIX 3’

7. For more information
p Brian@bisg.org
p Kim@bisg.org
p www.bisg.org
n Especially, “Committees”, “Resources” and “Events”
p (646) 336-7141
7