Implementing LinkFinder Plus at the University of Connecticut

1
Implementing LinkFinder Plus at the University of
Connecticut

• Steven K. Wieda and Melissa A. Wisner

2
What We Will Discuss

• eJournal subscriptions at UCL
• In-house solutions for eJournal management
• What LinkFinder Plus does out of the box
• How UCL has enhanced LinkFinder Plus
• Q A about UCL implementation of LinkFinder Plus

3
eJournals at UCL

• A full report from Serials Solutions lists apprx.
  23,000 titles
• High-use/demand of full text online from users
• of our budget

4
In-House Solutions for eJournal Management

• eCompass 1999 MS Access/Cold Fusion database of
  eJournal holdings from subscription aggregators
  as well as specific licensed full text content
• Pros easy to use, fast searching
• Cons cumbersome for staff to maintain, mostly
  stand-alone

5
(No Transcript)
6
(No Transcript)
7
In-House Solutions for eJournal Management

• Serials Solutions license with vendor to
  maintain a track record of our eJournal
  subscriptions
• CSV report is reviewed than loaded/updated to
  eCompass
• Using XML report from Serials Solutions to
  activate titles in LFP Knowledge Base
• Updated frequency of receipt of XML report to
  monthly to keep LFP KB as accurate as possible

8
(No Transcript)
9
What LinkFinder Plus Does Out of The Box

• OpenURL Link resolver
• Knowledge Base with 1654 sites
• Can batch activate Serials Solutions data
• Will locate the full text or abstract online if
  library has access to it

10
What LinkFinder Plus Does Out of The Box

• Knowledge Base Oracle database of pre-populated
  targets and sites, governing where and how to
  locate the full text
• Extended Services Value-added services to
  supplement user searches

11
Limitations of LinkFinder Plus Out of The Box

• Reliant on restrictive LFP Administrator Client
• 3.0 limitation of 3 OpenURL parameters per
  extended service via client
• Limited to default queries when editing XSL
  Templates
• System interconnect dependent upon OpenURL
• Lack of ER diagrams, documentation on XML queries

12
(No Transcript)
13
(No Transcript)
14
(No Transcript)
15
(No Transcript)
16
(No Transcript)
17
(No Transcript)
18
(No Transcript)
19
(No Transcript)
20
Top Priority of LinkFinder Plus
21
(No Transcript)
22
Knowledge Base
23
Extended Services
24
General (HTML) modifications to LFPDisplay.xsl
25
How UCL Has Enhanced LinkFinder Plus

• Whats in Knowledge Base vs. what eJournals UCL
  actually licenses
• What is typical user behavior when looking for
  full text?
• DD/ILL is part of accessing full text

26
How UCL Has Enhanced LinkFinder Plus

• Extended Services Desired by UCL, but not
  provided within the Admin Client
• Homegrown ILL Application
• Homegrown eJournal Locator

27
How UCL Has Enhanced LinkFinder Plus

• General Interface Wishlist
• Context Sensitive
• SFX-like Interface
• Pulldowns instead of link lists
• Verbiage changes

28
How UCL Has Enhanced LinkFinder Plus

• Moral of the story
• To fully customize and enhance LinkFinder Plus,
  you must break away from the Admin Client and
  modify the LFPDisplay.xsl template.

29
XSL primer

• HTML-like structure
• Extremely strict
• Queries called, filtered inline with HTML
• Testing for data in a query ltxslwhen
  testquerygt
• Outputting a query ltxslfor-each
  selectquerygt
• Scoping a query to a single record
  ltxslfunction selecttest"querynamename"gt
  

30
Default Queries in LFPDisplay.xsl

• lfp-display/fulltext List fulltext resources
• lfp-display/metadata/element List metadata for
  record
• lfp-display/ext-service List extended services
  available

31
Connecting to Homegrown ILL

• OpenURL-enabling the ILL web application
• Rewriting the add item component
• Allowing both login and non-login options
• Connecting LFP to the OpenURL-enabled application
• Context Sensitive

32
Open URL search of eCompass
Metadata from citation passed via Open URL to
DD/ILL web form
33
(No Transcript)
34
Connecting to eJournal Locator

• OpenURL-enabling the eJournal Locator
• Creating a search from an OpenURL
• Connecting LFP to the OpenURL-enabled eJournal
  Locator
• XSL modifications
• Context Sensitive how and whys

35
(No Transcript)
36
(No Transcript)
37
Where UCL Wants to Go Next with LFP

• From about 60 representation of UCL
  subscriptions in KB to as close to 100
• Still maintaining services such as Silver Linker
  and Hooks to Holdings with third party vendors
• Separate file maintenance of eCompass and LFP KB
  (one CSV, one XML)
• Getting LFP to work in ERA

38
Where UCL Wants to Go Next with LFP

• Building Open URLs from OPAC to LFP KB or
  eCompass
• More flexibility and influence with vendors over
  placement of UConn Full Text graphic
• Monitor any /- impact of LFP on DD/ILL
• Integrating LFP with University Courseware
  Management System

39
Questions

• LFP product?
• UCL Implementation of LFP?
• Staff resources?
• Skills for maintenance and growth of LFP?