kbart update ala midwinter 2010
Post on 21-Oct-2014
351 Views
Preview:
DESCRIPTION
TRANSCRIPT
KNOWLEDGE BASES AND RELATED TOOLS:
A NISO/UKSG RECOMMENDED PRACTICE
Jason Price, PhD Claremont Colleges/SCELCKBART Working Group Member
ALA Midwinter Jan 16 2010Boston, MA
K ?Xok ?X KBART
KBART: An Introduction
Knowledge Bases And Related Tools UKSG and NISO collaborative project Get better data for everyone –
Those who provide data (publishers, aggregators) Those who process data (link resolvers, ERMs, etc.) Those who present data (libraries, consortia)
All for THOSE WHO USE DATA – library patrons Ensuring timely transfer of accurate title access
list data to knowledgebases, ERMs, etc.
the Recommended Practice: Unveiled! Hot off the press: posted thursday, TBA
Monday http://bit.ly/kbartRP
What’s inside: Data supply chain description - from
producer to user Detailed examination of KB data problems Specific solutions as best practices that will
help avoid these problems Aiding adoption & Next steps
Inaccurate Data – The problem
ErrorLevel
False (+) including links to inaccessible
content
False (-)lacking links to accessible
content
TitleAccess not activated by publisher
Accessible title not listed in KB/Catalog
Date Range
Part of access not activated by publisher OR Years of access over-represented in KB/Catalog
Years of access under-representedin KB/Catalog
Inaccurate Data – Our current responses
REACTIVE – correcting data for individual articles that patrons report as inaccessible But what about the (large) majority that go
unreported (esp. the false negatives that prove that “Google has
lots of content ’not available through the library’”) PROACTIVE – before we get (or don’t get)
complaints title by title or package by package extremely labor intensive An example
Proactive reconciliation of an ejournal package list General Process – library, consortium or KB
vendor (Re-)Request updated access list from publisher Sample publisher list for accuracy Translate publisher list to match KB list
Number of titles never matches Perform ISSN match with MS Access Watch for & integrate title changes, mergers, acquisitions
and losses Watch for publisher-reuse of ISSNs/title combinations Identify date discrepancies manually (inconsistent formats
& granularity) Decide when its ‘good enough’ and go live/distribute
new list Lather, Rinse, Repeat
Correcting Inaccurate Data – the hard way
Correcting Inaccurate Data – the hard way
226 titles = 16%
Knowledge bases
Date coverage
Title relations
Licensing
Data & transfer
Supply chain
Compliance
accuracy
format
vol/issue vs date
date granularity (day, month, season, year)
title changes
title mapping
abbreviations
ISSN/ISBN variations
re-use of ISSN effect on
licensing
genericism/granularity
misrepresentation
package variations
accuracy
free content
format
ownership
contacts/feedback mechanisms
incentive
informal structure
unclear responsibilities
duplication of effort
file format
format definitions;
shoe-horning
age of data
accuracy
frequency
link syntax and
granularity
Problem Overview
Problems identified and addressed 4.2.1 Identifier Inconsistencies 4.2.2 Title Inconsistencies 4.2.3 Incorrect Date Coverage 4.2.4 Inconsistent Date Formatting 4.2.5 Inconsistencies in Content Coverage
Description 4.2.6 Embargo Inconsistencies 4.2.7 Data Format and Exchange 4.2.8 Outdated Holdings Data 4.2.9 Lack of Customization
Inaccurate Data – The KBART Solutions Standardize transfer of data within
and among supply chain participants Best practices recommendations specify:
means of data transfer frequency of updates file structure Data elements – Mandatory and
Optional e.g. Start and end date format & granularity
Desired impact on our work
An end to our role as translators No more badgering publishers to send complete
access lists(List of necessary elements is standardized) No more teasing out title changes to make the #’s
match(Best practice is to include former titles & issns) No more waiting for the KB data team to translate
data (Standardized format leads to automated ingest) No more out-of-date access lists (Regular updates direct from publisher to knowledge
base)
Supporting adoption: The web hub Guidelines, FAQ, Quick Guides & Video demonstrations Case studies
http://www.uksg.org/kbart
Next steps
Definitions for global vs. local updates Consortia-specific metadata transfer Institution-specific metadata transfer Documentation of guidelines for non-text
content metadata transfer Review of metadata transfer for e-books Monitoring and enforcing compliance
with KBART recommendations Exchange of ERM data
How can you help?
Send the report or web hub link to the publishers you work with and ask them to adopt the practices
Tell your colleagues about them so they can do the same (particularly consortia representatives)
Consider reference to KBART in ejournal package license terms
Join the monitoring group to stay up to date and help us continue to improve KBART
Thanks!
http://www.uksg.org/kbart http://www.niso.org/workrooms/kbart
Peter McCracken (NISO (ex) co-chair) Co-founder & Director for Research, Serials Solutions
Charlie Rapple (UKSG co-chair) charlie.rapple@tbicommunications.com
Head of Marketing Development, TBI Communications Jason Price (Working group member)
jason.price@libraries.claremont.edu Head of Collections @ Claremont; SCELC ejournal
package analyst
Who’s in KBART?
Core working group Link resolver/ERM suppliers – Ex Libris, Serials
Solutions Publishers – British Medical Journal Group, Taylor &
Francis Subscription agents/aggregators – Credo, EBSCO,
Swets Consortia – California Digital Library, SCELC Libraries – Claremont, Cornell, Edinburgh, Leicester,
Princeton, Pacific Northwest Technical Lab Monitoring group
More of these plus other related groups e.g. NASIG Anyone can join monitoring group sign up for updates: kbart_interest-subscribe@list.niso.org
top related