This presentation was provided by Michael Roberts of Emerald Group Publishing during the NISO event, Enabling Discovery, Part One: Publishers and Libraries Talk Metadata & Monographs, held on January 14, 2019.

1. Data-driven Discovery to Delivery:
A Publisher’s Perspective
Michael Roberts
14th January 2019

2. What are the
gaps affecting
the User
Experience?

3. Context: Publishing Ecosystem Data Flows
Funding
bodies
Researchers
Institution
Grants
Office
Institutional
Information
Management
Research
Management
Third party providers
PID providers
Citation
Management
Abstracting &
Indexing
Analytics
Content
Preservation
Submission
Management
Publishers
Editors &
Reviewers
Discovery
Services
Web & Library
Catalogues
Adapted from work done by Metadata2020 participants
http://www.metadata2020.org/projects/mappings/

4. Context: Publisher Data Flows
PID provider
Product
Data Store
Submission
System
Publication
Management
System
Sales
Data Store
CRM
Data
Warehouse
Reporting
System
Submission &
Publication
Management
Typesetters
XML
Data Store
Bookstore
Web platform
Standard
3rd Party
Data Feeds
Bespoke
3rd Party
Data Feeds
Data Stores
User-facing Systems
External services
Data feeds
Key

5. How are we
finding the
gaps?

6. Emerald Methodology
• Monitoring
•Auditing
•Reporting

7. Monitoring

8. Auditing

9. Reporting

10. Follow the User

11. What’s going wrong?
Image: Public Domain

12. How do we fix the gaps?
Image: Public Domain

13. Case Study 1: Background
Single site, part of a larger national body.
Manage their own subscriptions, but use a discovery layer provided for
them.
Usage drop was noticed, which led to a site visit.

14. Case Study 1: Issues found
Content was indexed in the discovery layer
Direct linking wasn’t reliable
Authentication failed when transferring from discovery layer to
platform

15. Case Study 1: Resolutions
Discussion with provider of discovery layer to resolve linking issues
Discussion with authentication provider to work out how to enable the
‘handshake’ when transferring users to our platform
Resolving bug on our platform when logging in

16. Case Study 2: Background
National Consortium
A consortium-wide change of Library Management System and
Discovery Layer led to a drop in usage

17. Case Study 2: Issues found
Discovery layer is from one of the main providers, so we already know
from our auditing that the content is indexed; however, it’s not
appearing in search results
LMS & LDS centrally managed for most sites, so individual institutions
may not have the ability to configure the systems to reflect their
subscriptions

18. Case Study 2: Resolutions
This is one we’ve not been able to make much headway on.
The problems have been flagged up to the consortium, but the
complexities of setting up multiple sites with the correct subscription
packages mean little progress.
LDS provider’s position is that ranking of resources is at the customer’s
discretion, and they can’t focus on improving the ranking of a single
publisher.

19. What next?

20. Internal developments
Image: By Leaflet - Own work, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=11770851

21. More automation!
https://www.niso.org/standards-committees/kbart/kbart-automation
Image: https://flic.kr/p/cp5WgS Spencer Cooper CC-BY-ND

22. More collaboration!

23. Thank you
mroberts@emeraldgroup.com