1 KBART: improving the supply of data to link resolvers and knowledge bases Jason Price, SCELC Ejournal Package AnalystKBART Consortia RepresentativeNISO/BISG ALA Annual Anaheim27 June 2008Credit for (most) slides: Charlie Rapple (KBART UKSG co-chair)
2 Outline Retrieval using a link resolver and its knowledge base What is a knowledge base, and why it mattersSome examples of problems that occurKBART – what? why? who? how? when?
3 How does a link resolver allow retrieval? Takes an OpenURL and extracts the article metadataCompares article metadata to knowledge basewhere is the article available?which version is preferred by the library?Puts together a direct link to this versiontarget (cited) articlepredictable link
8 Hang on. What is a knowledge base? A databaseContains information about web resourcese.g. what journal holdings are available in JSTORand how would you link to articles in themContains information about the resources a library has licensed/ownsMay contain electronic and print holdings (in addition to a number of other services)
9 So why is it so important? It ‘knows’ where all the content isIt ‘knows’ which versions the library is able to accessSo – it’s the only comprehensive source of links to a library’s full complement of electronic full text contenti.e. It solves the “appropriate copy” problem
11 Where the chain breaks Wrong data Publisher gives wrong metadata for title to the KBLink resolver uses bad metadata to make linkLink does not resolve to correct targetDead end
12 Where the chain breaks Outdated data Publisher said it has a particular issueLink resolver links to an article from itIssue has been removedDead end Or, provider doesn’t notify that issue is now liveSo no traffic from link resolvers to that issue!That’s not good!
13 Right. So. What is KBART? Knowledge Bases And Related Tools UKSG and NISO collaborative projectTo improve navigation of the e-resource supply chain byEnsuring timely transfer of accurate data to knowledge bases, ERMs etc.
14 Why was KBart established? UKSG 2007 research report, “Link Resolvers and the Serials Supply Chain”lack of awareness of OpenURL's capabilitiesimpacting the quality and timeliness of data provided to knowledge basesundermining the potential of this sophisticated technologyNISO partnership to help reach US audience
15 Who’s in KBart?Core working group chaired by Charlie Rapple (Publishing Technology – Ingenta) and Serials Solutions’ Peter McCrackenLink resolver/ERM suppliers – Ex Libris, Openly/OCLC, SerialsSolnsPublishers – Taylor & Francis, SageSubscription agents/aggregators – Swets, EBSCO, Ingenta, CredoLibraries – Edinburgh, Leicester, Cornell, Hanford TechnicalConsortia – SCELC, CDLMonitoring groupMore of these plus other related groups e.g. NASIG
16 What is KBart’s mission? GuidelinesEducationInformation hubClarify who, mostly, needs educating – did the research report suggest one group is getting it more than another? (probably the publishers – sorry publishers!)
17 How are you going to do it? TerminologyProblemsSolutions (to come)Advocacy (to follow!)
18 Terminology Open Access ERM embargo target link-to syntax OPAC source link resolvercontent providerlocalisationappropriate copyaggregatorSFXDOIfederated searchgatewayknowledge basemetadataOpenURL
19 Problemsaccuracyformatvol/issue vs datedate granularity (day, month, season, year)title changestitle mappingabbreviationsISSN/ISBN variationsre-use of ISSNeffect on licensinggenericism/granularitymisrepresentationpackage variationsfree contentownershipcontacts/feedback mechanismsincentiveinformal structureunclear responsibilitiesduplication of effortfile formatformat definitions; shoe-horningage of datafrequencylink syntax and granularityData & transferDate coverageKnowledge basesSupply chainTitle relationsComplianceLicensinghaving articulated the issues affecting the efficiency of OpenURL linking, we’re now proposing and honing solutions.Hopefully some will be relatively simple – a case of finally having the right people in a room together discussing itOthers may need compromise between different stakeholders
20 When are you going to finish? This time next yearMay go on to create a standardPhase II?e.g. exploring options for a centralized knowledge baseInclude wider range of resources (e.g. non-text content)?
21 Questions? www.uksg.org/kbart Charlie Rapple (UKSG co-chair) Peter McCracken (NISO co-chair)Jason Price (Working Committee Member)