Context-sensitive linking: CISTI's experience with WebBridge

(1)

Questions? Contact the NRC Publications Archive team at

[email protected]. If you wish to email the authors directly, please see the first page of the publication for their contact information.

https://publications-cnrc.canada.ca/fra/droits

L’accès à ce site Web et l’utilisation de son contenu sont assujettis aux conditions présentées dans le site LISEZ CES CONDITIONS ATTENTIVEMENT AVANT D’UTILISER CE SITE WEB.

READ THESE TERMS AND CONDITIONS CAREFULLY BEFORE USING THIS WEBSITE.

https://nrc-publications.canada.ca/eng/copyright

NRC Publications Archive Record / Notice des Archives des publications du CNRC :

https://nrc-publications.canada.ca/eng/view/object/?id=ae6b7646-3ef1-4a25-a9ed-b802a6b44b3c https://publications-cnrc.canada.ca/fra/voir/objet/?id=ae6b7646-3ef1-4a25-a9ed-b802a6b44b3c

NRC Publications Archive

Archives des publications du CNRC

Access and use of this website and the material on it are subject to the Terms and Conditions set forth at

Context-sensitive linking: CISTI's experience with WebBridge

(2)

Context-Sensitive Linking

CISTI’s Experience with WebBridge

Presented by:

Sophie Roy, Systems Librarian, IRM, CISTI

(3)

Presentation Overview

• OpenURL Linking Architecture

– Metadata & Identifiers

– Why Use an OpenURL Resolver?

• WebBridge

– Configuring WebBridge – Lessons Learned

(4)

OpenURL

• National Information Standards Organization

(NISO)

• Standardizes:

– Data used to identify or describe an object – Syntax used to package the data

(5)

OpenURL: Data & Field Names

Meta-Tag Description genre book - a book

journal - a journal, volume of a journal, issue of a journal article - a journal article

proceeding - a conference proceeding

aulast A string with the first author's last name

aufirst A string with the first author's first name

issn An ISSN number

eissn An electronic ISSN number

sici A SICI of a journal article, volume or issue. Compliant with ANSI/NISO Z39.56-1996 Version 2 (see http://sunsite.berkeley.edu/SICI/)

bici A BICI for a section of a book, to which an ISBN has been assigned. Compliant with http://www.niso.org/bici.html

title The title of a bundle (journal, book, conference)

atitle The title of an individual item (article, preprint, conference proceeding, part of a book)

volume The volume of a bundle

(6)

Metadata

• Metadata

– Many bits of data needed to identify an object

– Information about information – Descriptive

(7)

Origin  Resolver  Targets

ORIGIN  RESOLVER (OpenURL)

• http://cat.cisti.nrc.ca:4550/resserv?

issn=0302-9743&volume=2301

RESOLVER generates links to TARGETS

• FULL TEXT:

http://springerlink.metapress.com/openurl.asp? genre=issue&issn=0302-9743&volume=2301 • SEARCH:

http://cat.cisti.nrc.ca/search/i? SEARCH=0302-9743

(8)

Linking Architecture

ORIGIN sends OpenURL OpenURL resolver TARGETS WebBridge ORIGIN sends OpenURL  Full text  Order from CISTI  Find in CISTI Catalogue

(9)

Origin

OpenURL link

to resolver _{List generated} by resolver

(10)

Identifiers

• Identifiers

– Code uniquely identifying an object – Ex.: Digital Object Identifier (DOI):

(11)

RP Article via DOI Handle System

(12)

Why Use An OpenURL Resolver?

• FOR USERS

– Broader scope – Consistent services – Appropriate resources

• FOR LIBRARY

– Change in Workflow

(13)

Current Situation

IBIDS CSA EBSCO PubMed Check Library Holdings Order Full Text Protein Data Bank

(14)

Consistent Services

ORIGINS Research Press CISTI Source Expertise Database CISTI Signal CISTI Catalogue IBIDS SilverPlatter Business Source Elite

Protein Data Bank Cambridge Scientific Abstracts OpenURL Resolver TARGETS Full text Abstracts Pay-per-view

Order from CISTI Library Catalogues Book Reviews

(15)

Appropriate Resources

• Offer a relevant resource to the user

– Who is requesting what?

– What are we licensed to offer to that user?

• Example: Article Request

– From NRC  full text of article

(16)

Architecture for Appropriate Resources

Link from OpenURL ORIGIN Local OpenURL resolver List of links to TARGETS

License & holdings information

User authentication and recognition

(17)

Change of Workflow

BEFORE

Citation Database

•Providers & syntax •User affiliation

•Affiliations’ holdings •Linking mechanism

Library

•Input holdings into many systems

AFTER

Citation Database

•OpenURL metadata •User affiliation &

resolver URL

•Linking mechanism

Library

•Resolver

(18)

Resolver Configuration

• LIBRARY owns resolver & decides what

services resolver will generate

– What origins to accept – How to handle metadata – What targets to offer

– How to display links

(19)

(20)

WebBridge: Administration

• Origins

• Filters

• Categories

• Field Selectors

• Data Tests

Resource

Definitions

(21)

(22)

WebBridge: Field Selectors

• How to handle incoming metadata? • ISSN

– OpenURL field: issn – MARC field: 022|a

• YEAR

– OpenURL field: date – Format: yyyymmdd

• VOLUME

– MARC field: 440|v

(23)

(24)

WebBridge: Field Selectors and Data Tests

http://cat.cisti.nrc.ca/search/i?SEARCH=#@ISSN# #@EISSN##@ISBN#

Display link only if origin has sent ISSN or ISBN in the OpenURL.

(25)

WebBridge: Data Tests

• Object described using specified data type

– Has ISSN

– Has ISSN, volume, issue and spage – Has spage or atitle or aulast

• Data type has specified value

– 260 has “Springer”

• Data value matches against local holdings

(26)

WebBridge: Coverage Data

• Holdings data loaded into Innovative database

Springer|Journal of Molecular Evolution|0022-2844|

|1432-1432|19960101|20021231|||Restrictions may apply

• Holdings data used to:

– Check availability (appropriate copy) – Display library’s holdings

(27)

WebBridge: Resource Definitions

•Resource definition for each link to display

•Requires syntax that is based on data transferred in OpenURL

•Difficult to generate link using this syntax:

http://scitation.aip.org/getabs/servlet/GetabsServlet?prog=no rmal&id=PHFLE6000015000011003318000001&idtype=cvip s&gifs=yes •Easier syntax http://stork.cisti.nrc.ca/util/rplink_e?issn=0829-8211&volume=78&issue=1&spage=1

(28)

WebBridge: Resource Definitions

• Definition for each target syntax

Article

openurl.ingenta.com/content?genre=article… Journal

openurl.ingenta.com/content?genre=journal…

• Definition with non-OpenURL data

– http://link.aip.org/link?PHF/15/3318/html

– http://link.aip.org/link?#@JOURNALCODE#/#@V OLUME#/#@SPAGE#/html

(29)

WebBridge: Resource Definitions

• In what category

• Order within category

• Where to display

– Catalogue -- browse or full record; within page or link to panel

– External -- panel

• What link text

– Library holdings

(30)

(31)

(32)

(33)

Lessons Learned: Field Selectors

• Origin and target use different metadata

– EISSN vs. ISSN with hyphen – LC subject vs. MeSH subject

– Subject with vs. without brackets

• Internal origin data not in MARC record

– Bibliographic record number not in MARC record.

• Data in MARC is concatenated.

(34)

Lessons Learned: User Interface

• Common Look and Feel

– Bilingual display

– New window vs. frame

– “Opening in new window” message

• Displaying object-specific information

– WebBridge definition is at provider level. One link text for all objects available from provider. – Object-level information maintained in

(35)

Lessons Learned: Data Tests and Filters

• Data tests are limited to options created by

Innovative.

– Cannot create data test “item location=x”. Solution: use “bib location=x”

– Cannot use negative logic (field does not exist)

• Match on date assumes date is sent by origin.

No date sent, no match, no link.

(36)

Lessons Learned: Targets

• Resources not available online

• Provider does not have predictable URL syntax

• Provider registers objects with CrossRef

– Create CrossRef definition & coverage data

– Use only if you have access to publisher site.

CrossRef links to publisher, not to every possible provider. If library does not have license with

(37)

Lessons Learned: Targets

• Problem: BioMed Central has multiple

syntax

1. http://www.biomedcentral.com/#@ISSN#/# @VOLUME#/#@SPAGE# 2. http://genomebiology.com/#@ISSN#/#@VO LUME#/#@SPAGE# 3. http://<sitename>/content/#@VOLUME#/#@ ISSUE#/#@SPAGE#

• Solution: Create coverage data for each

syntax group.

(38)

Lessons Learned: Targets

• Data needed to generate link is not passed in

OpenURL

– http://link.aip.org/link?PHF/15/3318/html – Need journal code

• Solution: Secondary Lookup

– Keep journal codes in coverage data – Extract journal code based on ISSN

– http://link.aip.org/link?$#@ISSN##@JOURNALCO DE#$/#@VOLUME#/#@SPAGE#/html

(39)

Lessons Learned: Targets

• Maintaining accurate holdings when dates are

regularly changing (EMBARGO)

• Different OpenURL data in same field in target

syntax

• http://www.blackwell-synergy.com/openurl? issn=#@ISSN#&volume=#@VOLUME#

&issue=#@PART#&spage=#@SPAGE#

• http://www.blackwell-synergy.com/openurl? issn=#@ISSN#&volume=#@VOLUME#

(40)

Lessons Learned: Targets

• Problem: Multiple syntaxes for same resource

– http://openurl.ingenta.com/content?genre=article&issn=#@ISSN#& volume=#@VOLUME#&issue=#@ISSUE#

• &spage=#@SPAGE# • &aulast=#@AULAST# • &atitle=#@ATITLE#

– With 3 definitions, 3 links are generated when origin sends all data.

• Solution: Create one ‘combination’ definition with data test “spage or atitle or aulast”

– http://openurl.ingenta.com/content?genre=article&issn=#@ISSN#&

volume=#@VOLUME#&issue=#@ISSUE#&spage=#@SPAG

(41)

Lessons Learned: Targets

• Problem

: Same metadata but different URL for

supplement

– Origin sends:

issn=0284-186X&date=2004&volume=43&issue=15&spage=5

– Target URL for supplement:

issn=0284-186X&volume=43&issue=0&supp=15&spage=5

– OpenURL from Origin does not convey

‘supplement’. Link to regular article is also generated.

(42)

Handling Identifiers

• Origin sends identifier only (no metadata)

• Few targets recognize DOI

• Not enough information for providing

appropriate copy

– Need ISSN and Date

• Pass directly to site that recognizes identifier

– Handle system (DOI Server) DOI  Full Text

(43)

Handling Identifiers

• Use identifier resolution system

– CrossRef reference database

DOI  CrossRef  Metadata

– With metadata, resolver can check against local holdings and offer appropriate copy

(44)

Handling Identifiers: Linking Architecture

OpenURL with DOI OpenURL resolver TARGETS CrossRef

License & holdings information

User authentication & recognition

(45)