This session will discuss the knowledge base metadata lifecycle, current and upcoming metadata standards, and the effect that knowledge bases have on discovery and e-resource management. The presenters will look at ways knowledge bases can be leveraged to create downstream tools for resource management and discovery. The session will also provide different perspectives on knowledge bases, including from librarians and product managers, as well as a discussion of the NISO's KBART Automation recommended practice and what this could mean for knowledge bases in the future. The session will also include a conversation regarding how leveraging knowledge bases can aid librarians in improving resource discovery within their own libraries and ultimately decrease the amount of time spent on metadata workflows. Through this presentation, we also aim to improve communication between the library community and metadata providers and creators.
Elizabeth Levkoff Derouchie, Metadata Librarian for Serials & Electronic Resources, Samford University Library
Beth Ashmore, Associate Head, Acquisitions & Discovery (Serials), North Carolina State University
Eric Van Gorden, Product Manager, EBSCO
2. What are knowledge bases?
Why is this important?
Where are the gaps?
How does KBART help?
What's next?
3. What is a knowledge base?
A knowledge base is a vendor’s grouping of title-level metadata
organized by the collection in which the title can be acquired.
A knowledge base brings together publisher title lists with the
goal of further grouping together identical or related resources to
aid in the identification of the appropriate copy.
A knowledge base supports discovery.
4. The Knowledge
Base & the ILS
Traditional ILS use a bibliographic
databases and the patron database as
the backbone the system.
Image from https://blogs.library.duke.edu/bitstreams/2018/04/12/the-backbone-of-the-library-the-library-catalog/
5. The Knowledge Base & the ILS
Next gen ILS
make knowledge
bases more
central to their
structure.
6. Organization of Information:
The Record of Everything-ish
Business
Collection
The Journal of
Finance
Quarterly
Journal of
Economics
Journal of
Accounting
Research
Science
Collection
Nature
Science
Journal of
Biological
Chemistry
Book
Collection
AWrinkle in
Time
The Secret of
the Old Clock
Charlie and
the Chocolate
Factory
Journal
Publisher
Business
Collection
Science
Collection
Book
Publisher
Book
Collection
7. • Business CollectionTitle List
• Science CollectionTitle List
Journal
Publisher
• Book CollectionTitle List
Book
Publisher
Knowledge Base
Library/Patrons
Product/Discovery
Layer
8. Organization of Information:
The Library’s Record of Everything
Business
Collection
The Journal of
Finance
Quarterly
Journal of
Economics
Journal of
Accounting
Research
Science
Collection
Nature
Science
Journal of
Biological
Chemistry
Book
Collection
AWrinkle in
Time
The Secret of
the Old Clock
Charlie and
the Chocolate
Factory
Journal
Publisher
Business
Collection
Science
Collection
Book
Publisher
Book
Collection
9. Key Concepts
• Complete title lists and KBART (Knowledge Bases and
RelatedTools)
• Uniqueness of copy
• Appropriate copy
• Changing access
Photo by Kimberly Farmer on Unsplash
10. Appropriate Copy
Derivative works
• Pride and Prejudice vs Pride and Prejudice:
The Graphic Novel
Similarly named works
• Homer’s Odyssey by Gwen Cooper vs
Homer’s Odyssey by Homer (maybe)
• The Indianapolis Recorder vsThe Recorder
(Ontario Music Educators'Association)
UpdatedVersions
• Current Diagnosis &Treatment Pediatrics,
25th edition vs Current Diagnosis &Treatment
Pediatrics, 24th edition Photo by Brett Jordan on Unsplash.
11. KBARTTimeline
KBART Phase I: NISO RP-9-2010, KBART:
Knowledge Bases and RelatedTools
Recommended Practice (January 2010)
2010
KBART Phase II: NISO RP-9-2014, KBART:
Knowledge Bases and RelatedTools
Recommended Practice (March 2014)
2014
KBART Automation: NISO RP-26-2019,
KBART Automation: Automated Retrieval
of Customer Electronic Holdings (June
2019)
2019
KBART Phase III: Initiated in December 2019
2019
13. Why does this matter?
We significantly influence or control the
selection, organization, preservation, and
dissemination of information.
CODE OF ETHICS OFTHE AMERICAN LIBRARY ASSOCIATION
17. Let us know on the
chat board.
What frustrates you the
most about knowledge
bases?
Inaccurate metadata
Missing titles
Requires too much customization
Not enough collaboration between
publishers and vendors
Anything else?
18. Gaps in Knowledge
Bases
• Lack of trust in publisher metadata
• Lack of communication between
librarians, publishers, and vendors
• Appropriate copy
• Rights management
• Not specific to any institution
• Duplication of efforts
Photo by Elijah Ekdahl on Unsplash
19. Reconciliation & AccessVerification
• Package management at NCSU to address the lack of trust in publisher metadata
• Reconciliation for entitlements
• Reconcile orders to publisher title lists
• Reconcile orders to knowledgebase title lists
• Access verification for metadata accuracy
• Identify collections that require extra scrutiny
• Fix at failure or disruption for more reliable collections
20. Future of Knowledge
Bases
• KBART Automation
• Centralized resource management well-
integrated
• Integrated with ILS system
• Usage and Cost data integrated with key
decision points
• Extending the KB to include license rights
and limitations
• Impacting analytics
Photo by ErolAhmed on Unsplash
21. KBART Automation
What problems could KBART
Automation solve?
Reduce duplication of efforts
Faster delivery of metadata across our systems
More accurate holdings information
What problems could KBART
Automation create?
Problems in metadata are less visible
Less awareness of when updates are made
Fewer opportunities for customization
22. What issues could
KBART Automation
Solve?
• Lack of trust in publisher metadata
• Lack of communication between
librarians, publishers, and vendors
• Rights management
• Not specific to any institution
• Duplication of efforts
Photo by Shot by L.M. Martín on Unsplash
23. What’s ahead and other
thoughts
• Improve communication across stakeholders (within
the library, across publishers, etc.)
• Improve resource discovery and ultimately decrease
the amount of time spent on metadata workflows.
• Usage statistics: COUNTER has released
“Incorporating KBart files with Release 5 reports”
Photo by chuttersnap on Unsplash
24. Let us know on the
chat board.
What would you like to
have in future
knowledge bases?
More robust, institution specific KBART
files sent from my publisher to my
knowledge base
More robust, institution specific KBART
files sent from my publisher to me
An ILS centered on the knowledge base
25. THANKS FOR WATCHING!
Questions? Contact us at
• Beth Ashmore – beashmor@ncsu.edu
• Elizabeth Levkoff Derouchie – elizabeth.derouchie@samford.edu
• EricVan Gorden – evangorden@ebsco.com
Hinweis der Redaktion
Everyone
Photo by chuttersnap on Unsplash
So, what does this all mean? We need to focus on improving communication across our stakeholders, not only externally, but internally as well. If we aren’t working with our reference librarians to help us report problems that are actively getting in the way of discovery, then we can’t actively report those problems. Personally, I have found that many vendors are receptive to changing or fixing a problem, but they have to know about it. I’ve found that to be true in a lot of different instances. And the goal here is to work together, so when problems in metadata arise, we aren’t recreating the wheel. You saw Eric’s slide before showing the numbers – and those are just for EBSCO.
And many libraries, if they haven’t already, are moving towards using KBART data, or KB data, in their workflows right now, and we continue to find new ways to use that information. One example is how COUNTER has released a PDF which details how to use KBART files with Release 5 reports to better examine, I believe, zero usage. I’d really like to hear your thoughts on some of this Eric--
**The bridge between what the vendor is trying to accomplish and what the librarian can accomplish; flow of information and data quality**