Jump to Content

UCeLinks Glossary

Linking terms

CrossRef

  • a collaborative reference linking service
  • in this context CrossRef is used to discover the Digital Object Identifiers (DOI) using article metadata supplied by the participating publishers
  • For more information see the CrossRef web site

DOI

  • Digital Object Identifier
  • stable identifier (URL)
  • DOIs provide a framework for linking to electronic content (among other things)
  • For more information see the Digital Object Identifier web site

Link Resolver

  • a generic term for products which support linking between databases and services such as linking to full text. SFX is a Link Resolver.

Metadata

  • According to the W3C metadata is machine understandable information for the web.
  • In this context the information includes the author, article title, journal title, volume, issue, date, start page, etc.

OpenURL

  • draft NISO standard which defines how to transport metadata between two systems using http
  • In this context the two systems are an A&I database and UC-eLinks.
  • For more information on the draft standard see the NISO AX committee web site

Terms specifically related to UC-eLinks

UC-eLinks

  • The name of the SFX server managed by the CDL

Knowledge database

  • a MySQL database provided by SFX which contains e-journal and e-book information
  • a journal title needs to be in this database and activated before UC-eLinks can offer the option for electronic text

Linking

  • some database like Gale's Expanded Academic ASAP which contain citation records and fulltext offer two verions of linking generally refered to as inbound and outbound
  • outbound links are OpenURLs associated with a citation record which are sent to a Link Resolver (UC-eLinks)
  • inbound links are generated by a Link Resolver (UC-eLinks) and resolved to full text at the vendor's site

Parser

  • software routines within UC-eLinks which process the OpenURL and build links (URLs) to services offered in the UC-eLinks menu window

Services

  • options which can appear in the UC-eLinks menu window
  • some services are getFullTxt, getHoldings, getDocumentDelivery, getWebServices

Source

  • vendor sending OpenURLs to UC-eLinks
  • at this time most of UC-eLinks sources are A&I database vendors

Target

  • vendor receiving URLs from UC-eLinks
  • at this time most of UC-eLinks targets are full text providers
  • Melvyl® and Request are also targets for UC-eLinks

Threshold

  • list of metadata which needs to be included in an OpenURL in order for a service to appear in the UC-eLinks menu
  • in some cases, such as dates, a value for the metadata can also be included in the threshold
Last updated: December 14, 2012
Document owner: UC-eLinks Team