You are here

Integration of databases in NILDE

Software technologies Insight Librarians Experts OpenURL

Thanks to the OpenURL technology, it is possible to link to NILDE the most used bibliographic and citation databases, with a great benefit for both users and librarians.
For the user, it will be much easier to request an item to their library, as the request form will be pre-compiled from the database with the bibliographic data of the article itself. Spelling mistakes will be avoided and all the fields required to find the item will be filled. This will prevent the library from tiring operations of completing/verifying the information entered by the user, and the module will be forwarded to the library found for the supply more quickly.

1. Introduction to OpenURL technology
2. NILDE as target and the OpenURL link resolver of NILDE
3. Instructions for configuring NILDE as target for a Database or a Link Resolver

Introduction to OpenURL technology

The integration of NILDE with a database takes place through AN internationally-used linking technology, which uses a standard protocol (ANSI/NISO Z.39.88-2004 OpenURL Framework for Context-Sensitive Services), for simplicity also called OpenURL protocol. The OpenURL standardizes the information useful for retrieving an article (title, author, issn).

An OpenURL is composed of two parts: a fixed one corresponding to the service, also referred to as "OpenURL Solver", and a variable one which contains the article's data.
An OpenURL always has a source and a target.

In this case, the database acts as an OpenURL source, because it crates the OpenURL containing the bibliographic metadata of the document and sends them to the service that the user has chosen for that document. For example, from a bibliographic reference of an article you can activate the link that directs you to the full-text of that article, or request it by the document delivery service of your library. In the first case, the OpenURL target is the platform of the electronic resources from which the full-text can be accessed, in the second case, the request through the document delivery service, the target can be NILDE.
More generally, some libraries or some of the University's library sistems prefer to configure a Link Resolver (examples of commercial softwares are SFX TM (tradeMarck symbol), Link Source TM, etc.) so that the OpenURL linking services can be used by all the databases subscribed to by the library or the University.

NILDE as target and the OpenURL link resolver of NILDE

NILDE is target of an OpenURL because it receives the bibliographic metadatas of the document (journal article, book chapter, ...) and it can resolve them by automatically inserting them in the NILDE request form (if it's the user that clicked on the service from a database) o in a new borrowing request form (if it's a library).

The NILDE OpenURL service is and it's compatible with the last version of the standard OpenURL 1.0 (and also retro-compatible with the 0.1 version). It accepts OpenURLs sent through the HTTP GET (obviously URL-Encoded) protocol with KEV encoded parameters.

Below there is a list of some of the parameters (specified in the standard 1.0 syntax) accepted by NILDE. For a complete discussion of the parameters (both for the 1.0 and 0.1 version) refer to the NISO OpenURL standard.

Required parameters:
url_ver:          Z39.88-2004
url_ctx_fmt:   info:ofi/fmt:kev:mtx:ctx

Genre definition:
rft_val_fmt:    info:ofi/fmt:kev:mtx:journal  (for articles only)
rft_val_fmt:    info:ofi/fmt:kev:mtx:book  (for books only)

rft_issn:         international standard serial number
rft_isbn :        international standard book number

rtf.jtitle:         title of the journal
rft.btitle:        title of the book
rft.atitle:        title of the article/preprint/proceeding/chapter

rft.aufirst:      name of the first author
rft.aulast:      surname of the first author

Other datat:
rtf.volume:     indication of the volume           editor
rft.issue:        indication of the dossier
rft.spage:       first page
rtf.epage:       last page         date of publication in the format YYYY-MM-DD or YYYY-MM or YYYY

rtf_id:             multiple choice field (it can be repeated indicating "rft_id[]="), and may contain identifiers such as DOI, PUBMEDID, SID

Exemple of OpenURL for an article (already URL-Encoded):[]=Awasthi%2C+Aashees&rft_id[]=info%3Adoi%2F10.1016%2Fj.jct.2012.04.024

Exemple of OpenURL for a book part (already URL-Encoded):[]=Rudd%2C+Pauline+M.&rft_id[]=info%3Adoi%2F10.1111%2Fj.1749-6632.2011.06420.x

Instructions for configuring NILDE as target for a Database or a Link Resolver

There is no unique way to configure the NILDE OpenURL Solver on a database or for a Link Resolver.

Some databases allow you to do it autonomously through the administration panel (see the articles in the following sections: PubMed, SciFinder Scholar, Scopus and ScienceDirect, Proquest, Ovid, RefWorks, ADS, and DoGi).*

NILDE's configuration with SFX Link Resolver can be easily done within a University or institution from the SFX Manager (NILDE Configuration as SFX Target).*
For other databases, and for other Link Resolvers, you need to make a specific request to the manufacturer/service provider by notifying the NILDE OpenURL Solver you want to configure it.

If you wish you can also specify the NILDE icon that you want to appear in the database; depending on your favorite size, you can link one of these images: (size 48x15 px)

Scopus /Science Direct button   (size 101x15 px) (size 120x26 px)

If the database (or link resolver) allows it, it should be possible to only specify the NILDE's solver openurl without having to manually enter the parameters of the OpenURL as the way in which these are specified in the OpenUrl depend on the type of resources (article, book, conference etc ...) and should therefore be automatically "calculated" by the database itself.