Charlie Rapple
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Charlie Rapple

  • 7,912 views
Uploaded on

Explanation of OpenURL linking, the problems within its supply chain, and the KBART working group set up by UKSG and NISO to address these problems.

Explanation of OpenURL linking, the problems within its supply chain, and the KBART working group set up by UKSG and NISO to address these problems.

More in: Education , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
7,912
On Slideshare
7,597
From Embeds
315
Number of Embeds
9

Actions

Shares
Downloads
22
Comments
0
Likes
1

Embeds 315

http://allmyeye.blogspot.com 305
http://allmyeye.blogspot.co.uk 2
http://allmyeye.blogspot.ru 2
http://www.blogger.com 1
http://64.233.179.104 1
http://66.102.9.104 1
http://allmyeye.blogspot.in 1
http://allmyeye.blogspot.ca 1
http://feeds.feedburner.com 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Hallo everyone. I’m here to give you an overview of the UKSG-sponsored KBART working group. KBART’s goal is to improve the supply of data to link resolvers and knowledge bases, in order to improve the efficiency and effectiveness of OpenURL linking. So I’ll also be going back to basics to explain the OpenURL since this is still an area that many in our community don’t feel comfortable that they understand.

Transcript

  • 1. KBART: improving the supply of data to link resolvers and knowledge bases Charlie Rapple KBART co-chair UKSG Annual Conference 5-7 April 2008
  • 2. Today’s agenda
    • OpenURL recap – why? how?
    • Stakeholder overview – who does what
    • What is a knowledge base, and why it matters
    • Some examples of problems that occur
    • KBART – what? why? who? how? when?
  • 3. OpenURL origins
    • Appropriate copy (“Harvard problem”)
    • Binary/hard-coded reference linking
    • Creation and standardisation of OpenURL
  • 4.  institution     repository publisher website database print collections gateways article citation article title = … first author = … journal name = … metadata string OpenURL query (base URL + metadata string) resolver.institution.edu base URL of link resolver link resolver’s knowledge base publisher/provider holdings data library holdings data content licence target (cited) article predictable link
  • 5.
    • Make their content OpenURL compliant by:
      • Creating outbound OpenURL links
    • Make their content KB compliant by:
      • Telling the knowledge base what content they have and how to link to it
    Which bits do publishers do?
    • Together: link-resolver compliance
    OpenURL query (base URL + metadata string) publisher/provider holdings data link resolver’s knowledge base
  • 6. What bits do libraries do?
    • Have a link resolver! And register it with providers
    • Customise its knowledge base with their own holdings data
    institution resolver.institution.edu base URL of link resolver library holdings data link resolver’s knowledge base
  • 7. What does the link resolver do?
    • Takes an OpenURL and extracts the article metadata
      • http://baseurl.institution.edu/content?genre=article&issn=1234-5679&volume=53&issue=3&page=14
    • Compares article metadata to knowledge base
      • where is the article available?
      • which version is preferred by the library?
    • Puts together a predictable link to this version
    http://baseurl.institution.edu/content?genre= article&issn=1234-5679&volume=53&issue=3&page=14 target (cited) article predictable link
  • 8. Hang on. What is a knowledge base?
    • A database
    • Contains information about web resources
      • e.g. what journals are available in JSTOR
      • and how would you link to articles in them
    • Contains information about the resources a library has licensed/owns
      • may also include offline holdings
  • 9. So why is it so important?
    • It knows where all the content is
    • It knows which versions the library is able to access
    • So – it’s the only place that can get a user to an “appropriate copy”
  • 10. article citation query (base URL + metadata string) link resolver/ knowledge base target (cited) article publisher website database print collections gateways publisher/provider holdings data repository
  • 11. Where the chain breaks
    • Wrong data
      • Publisher gives wrong metadata for title to the KB
      • Link resolver uses bad metadata to make link
      • Link does not resolve to correct target
      • Dead end 
  • 12.
    • Outdated data
      • Publisher said it has a particular issue
      • Link resolver links to an article from it
      • Issue has been removed
      • Dead end 
      • Or, provider doesn’t notify that issue is now live
      • So no traffic from link resolvers to that issue!
    Where the chain breaks That’s not good!
  • 13.
    • K nowledge B ases A nd R elated T ools
    • UKSG and NISO collaborative project
    • To improve navigation of the e-resource supply chain by
    • Ensuring timely transfer of accurate data to knowledge bases, ERMs etc.
    Right. So. What is KBART?
  • 14. Why was KBart established?
    • UKSG 2007 research report, “ Link Resolvers and the Serials Supply Chain ”
      • lack of awareness of OpenURL's capabilities
      • impacting the quality and timeliness of data provided to knowledge bases
      • undermining the potential of this sophisticated technology
    • NISO partnership to help reach US audience
  • 15. Who’s in KBart?
    • Core working group chaired by me (Publishing Technology – Ingenta) and Serials Solutions’ Peter McCracken
      • Link resolver/ERM suppliers – Ex Libris, Openly/OCLC, SerialsSoln
      • Publishers – Taylor & Francis, Sage
      • Subscription agents/aggregators – Swets, EBSCO, Ingenta, Credo
      • Libraries – Edinburgh, Leicester, Cornell, Hanford Technical
      • Consortia – Claremont, CDL
    • Monitoring group
      • More of these plus other related groups e.g. NASIG
  • 16.
    • Guidelines
    • Education
    • Information hub
    What is KBart’s mission?
  • 17. How are you going to do it?
    • Terminology
    • Problems
    • Solutions
    • Advocacy
  • 18. Terminology link-to syntax aggregator appropriate copy content provider DOI embargo ERM knowledge base localisation metadata OPAC OpenURL SFX source link resolver federated search gateway Open Access target
  • 19. Problems?
  • 20. When are you going to finish?
    • This time next year
    • May go on to create a standard
    • Phase II e.g. non-text content
  • 21. Questions?
    • www.uksg.org/kbart
    • Charlie Rapple (UKSG co-chair)
      • [email_address]
    • Peter McCracken (NISO co-chair)
      • [email_address]