260 likes | 379 Vues
This document, presented by Lisa Goddard, explores the implementation of OpenURL for full-text linking in libraries, detailing its purpose, benefits, and operational mechanics. It also covers the ASIN Resource Discovery and Management Service (RDMS) and its components, highlighting the RFP process initiated in September 2003. The MUN Portal is showcased, including its library channel development and how it enhances user experience with integrated searches, authentication, and resource access. This overview aims to inform about emerging technology and services in library systems.
E N D
New Technology Overview Lisa Goddard Emerging Services Librarian Memorial University Libraries November 3, 2003
Outline I. OpenURL – Full Text Linking • Purpose • Benefits • How does it work? II. ASIN Resource Discovery and Management Service • The RFP process • Major components of ASIN RDMS
Outline Cont’d III. The MUN Portal (my.mun.ca) • Purpose? • Demonstration of interface • Developing a Library Channel
What is OpenURL? • OpenURL is a NISO standard • Link Resolver software uses the OpenURL standard e.g. SFX, Godot, V-link, Article Linker • Unified interface to the diverse collections that a library hosts locally or has rights to externally • Creates links from citations to full text resources based on your library’s holdings
Closed Linking Currently we have closed linking • Links to FT resources controlled by citation provider • We provide profiles of our electronic holdings to individual index publishers (e.g. Silver Linker) • Requires constant updating & duplication of work for each vendor profile • Prone to errors and inconsistencies • Doesn’t scale well
Benefits of Open Linking • One master list of all available resources and institutional holdings. • Puts link resolution into the hands of the library, not the vendors. • Presents links based on our preferred resources and services.
Elements of Open Linking Open linking has three key elements: • Referrer/Source = Citation provider (Electronic Index) • Link Resolver = Performs the comparison between cited article and library holdings, displays the results as links to appropriate resources • Target = article level link
Referring Resource – Citation Provider Link button contains citation information encoded into an URL.
OpenURL Syntax URL carries citation metadata: Server name and domain ? Indicates beginning of parameters = Divides field name from value & Indicates start of new field http://resolver.mun.ca/resolve?issn=1468-4527&title=Online Information Application or file to process data Name of field Value of field
OpenURL Query Statement http://server.mun.ca/resolver/ ?sid=ukoln:ariadne (vendor ID : database ID) &genre=article &atitle=Information%20gateways:%20collaboration%20on%20content &title=Online%20Information%20Review &issn=1468-4527&volume=24 &spage=40&epage=45 &artnum=1 &aulast=Heery&aufirst=Rachel
Link Resolver • Citation information is passed to the library’s link resolver server • Citation information from referrer is checked against master list of all available resources and institutional holdings • Creates custom link for each appropriate resource/ service using metadata from referrer
Link Resolver • Will create multiple links if the article is available through more than one vendor. • Library applies rules about “appropriate copy” and user permissions • Library indicates which links to other services should also display in results • e.g. OPAC search link, Google search link, document delivery request button, Cisti Source search link
Open Linking: Overview Target Link to FT article from aggregator Citation Provider MUN Link Resolver Link Citation Metadata Carried in URL Target Local Holdings & Appropriate Copy Link Link to Google Search Link Target Link to send request to Relais
ASIN RDMS – Where are we now? • Resource Discovery and Management Service • Request for proposal (RFP) released September, 2003 http://interuniversity.ns.ca/tenders/ASIN_RFP.pdf • RFP closed on October 27th, 2003. • Vendors required to submit point by point response to requirement list. • Vendors also required to provide a working demo of their solution.
ASIN RDMS – Major Components Authentication • Single sign in to authenticate against proxy, catalogue, Relais • Login information carried through entire session • Integrate login with MUN LDAP server Pathfinder Model • Subject as main point of entry • Ability to customize metasearch targets based on subject area chosen • Ability to add customization to searches from a given page (e.g. indicate terms that should always be included)
ASIN RDMS – Major Components Metasearching • Simultaneous searching of multiple library catalogues, indexes and full text resources • Ability to return integrated/deduped list of search results. • Simple and advanced search interfaces w/ Boolean support • Must also provide access to native vendor interfaces Full text linking (OpenURL) • Portal must act as the referrer and resolver of full text links. • Links to Full text resources, predefined web searches, Relais requests must appear beside integrated result lists
ASIN RDMS – Major Components Customization • Every subject area can have a completely customized look and feel (e.g. news feeds, images, forms, predefined searches, thumbnails, page layout) • Users can save personalized metasearch preferences, search strategies, register for alerting services • Uses login information to present users only with collections and resources that they have the right to search and retrieve. Direct requests to Relais • Button to request any resource through Document Delivery • Carries citation information and user login information
ASIN RDMS – The Selection Process • Received responses from 8 vendors. • A sub-committee will filter and shortlist products based on vendor responses. • Short listed vendors willbe invited to Halifax for demonstrations. • Final choice will be made based on those presentations. • Decision anticipated by December 2003.
ASIN RDMS – Implementation Process Stage 1 • Steering committee formed to oversee implementation. • Software installed in a usable, initial version by June 2004. Stage 2 • Steering committee creates a development working group to shape ongoing development and governance of RDMS
MUN Portal – my.mun.ca • The MUN portal is a collection of separate data sources integrated into a personalized, customizable web page. • Each of these sources is called a “channel” • Channels are organized into three major categories: • Courses – Academic services • News – Information and Events • Student Life – Classifieds, personal bookmarks, surveys, email • Offers users a single login to most services.
MUN Portal – User customization • Content is pushed out to end-users based on their personal profile & relationship to the university • User chooses what content is displayed on his/her web portal layout. • Can add/remove channels according to need or interest • Can subscribe to specific news feeds & services
MUN Portal – Demo http://my.mun.ca/ Login with plato username/password
MUN Portal – Library Channel According to student surveys, the library is the most requested channel. Possible content: 1) Unicorn Information • Reserve Lists (by course & section) • Overdues & Other Notices • Request Status e.g. The item you have on hold is now available for pick-up
MUN Portal – Library Channel 2) Website Information • News streaming • Info/Services to Distance Users • Course Instruction Materials (by course and section) e.g. Your psych 101 class has a tutorial this Friday at 1pm e.g. There is research material available for Geo 400 • Branch Specific Information e.g. Health Sciences users can request custom online searches e.g. Marine users may be interested in our new marine dynamics database • Ask a librarian/Virtual Reference