Skip to main content
Favorite
Add To List
Ben Johnson

Ben Johnson

Provider Relations Engagement Manager - Ex Libris, a ProQuest Company
Ben has been working with content in the ProQuest/Serials Solutions products for over a decade, and Ex Libris products since their acquisition by ProQuest in late 2015. He has participated in all things KBART since 2012, including two years as former co-chair of the KBART Standing Committee. He received his library degree from the University of Washington in 2006, and lives in Seattle with his partner, son, a small zoo’s worth of animals, and a perpetually full cup of coffee.

Matching Videos

2 Matching Videos
Education

KBART Open Hour Webinar

01:01:07
Do you work for a publisher, aggregator, or content provider and have questions about how to implement KBART for your content? Need to know how to format a particular KBART field, or what it is used for? Want to learn about resources you can use in developing your KBART files, or how to get feedback on your files? On October 8, 2019, at 11 a.m. Eastern, join the KBART Standing Committee for a FREE, 60-minute "open hour" question-and-answer format webinar hosted by NISO and get information about KBART straight from the group. We will begin the webinar with a brief presentation on the KBART endorsement process, followed by answers to frequently asked questions and discussion of questions posted by attendees. To submit a question ahead of time, please email kbart@niso.org with the subject "Webinar Question". Attendees will also be able to submit questions during the webinar via chat. KBART (Knowledge Bases and Related Tools) is a NISO Recommended Practice that describes how to transmit data about serials and books/monographs to knowledge bases maintained by link resolver, resource management, and discovery system vendors.
NISO KBART Validator App 
How can we enhance trust in the quality of KBART files? Endorsement process is one way. Automated validation could be another way.

Content providers can have their KBART files endorsed by NISO. But the endorsement process consists of manual checks and thus can be a long process, with multiple file revisions and much back-and-forth communication required. The KBART Standing Committee aims to formalize and speed up its endorsement process by automating a number of validation tasks, thus providing more time to analyze parts of the files that are trickier to check automatically. Automated validation could also occur upstream, by content providers checking their KBART files post-production, or downstream, by knowledge bases checking KBART files before ingestion. What if all these scenarios relied on a shared tool?

The NISO KBART Validator app has two goals:
* Short term : ease NISO’s endorsement process by automating file checks that can be automated
* Long term : provide the community with a common validator app

The NISO KBART Validator app is currently under development. This session will provide a demo of the tool and insights about its roadmap. We want this app to be community powered: we’ll take time in this session to discuss where you and your organization could help, with or without developers.""

The Package ID: Seeking Sanity through Standards
Content providers often bundle offerings into pre-set collections by subject, year, or some other scope so libraries can select packages that best fit their needs. Publishers also sell individual journals and books, allowing libraries to select content title-by-title. These options provide an effective approach to selling content. However, they produce a confusing, ever-changing tangle in knowledgebases.

Currently, package names are used identifiers, which introduces challenges for knowledgebase providers and librarians. Marketing pages, access platforms, licenses, invoices, and knowledgebases may all use different names for the same packages. Additionally, package names change, differ on various systems, and different bundles often have very similar names.

Knowledgebase providers load the content bundles to serve as the basis for discovery, linking, and ERM processes. Using package names as the identifier complicates always uniquely identify collections. The problem also affects automatic updates to the knowledgebase, in general, or within a specific library’s holdings. Likewise, librarians have a difficult time determining which of the many similar-sounding packages matches their licensed content.

Ultimately, all parties want to ensure that the licensed content is represented and enabled in knowledgebases for discovery and linking. Consistent unique identifiers may offer a way to improve efficiency and reduce confusion.

We are NISO, the National Information Standards Organization. We’re the place where information professionals turn for industry standards that enable them to work together. Let us help keep you informed about what’s happening at NISO and in the wider information community by signing up for emails in your area(s) of interest.