An institutional repository (IR) in which the institution's research output is captured by storing a record / version of each article or chapter written by its researchers, and/or
Current research information system (CRIS) that tracks an institution's research performance by, amongst others, capturing each article or chapter written by its researchers, and/or
A local VIVO installation (http://vivoweb.org/ about, http://vivo.sourceforge.net/) in which an institute's researchers are profiled. These researcher profiles often need to be complemented with their publication
Other internal reporting systems that track research output, similar to the above
Elsevier supports institutions who want to enhance their institutional repository (IR), current research information system (CRIS) or local VIVO installation (http://vivoweb.org/ about, http://vivo.sourceforge.net/) with Scopus APIs, ScienceDirect APIs or a combination of the two.
The table below indicates the repository objectives for IR/CRIS/VIVO client applications using Scopus APIs, ScienceDirect APIs or a combination of both.
Repository objectives & use cases
Scopus API use case only
ScienceDirect API use case only
Scopus & ScienceDirect APIs combined use case
SciVal API use case
To retrieve metadata of a comprehensive overview of the world's research output across publishers
X
X
To enable users to assess article impact by displaying Cited-by counts
X
X
To retrieve metadata and abstracts of articles and chapters of affiliated authors published with Elsevier
X
X (optional)
To enable users to identify the best available version and indicate whether users have access to the full-text on ScienceDirect
X
X
To enable users to read ScienceDirect content on the institutional repository pages
X (optional)
X (optional)
To enhance your compliance with funding body and publisher policies by automatic ingestion of embargo end dates
X (optional)
X (optional)
To retrieve a rich basket of metrics for Institutions
X
To retrieve a rich basket of metrics for authors
X
To retrieve a rich basket of metrics for documents
X
Detailed policy for Scopus:
Scopus data in institutional repositories, research information systems, VIVO
Definition: the client application is:
An institutional repository (IR) in which the institution's research output is captured by storing a record / version of each paper written by its researchers, and/or
Current research information system (CRIS) that tracks an institution's research performance by, amongst others, capturing each paper written by its researchers, and/or
A local VIVO installation (http://vivoweb.org/ about, http://vivo.sourceforge.net/) in which an institute's researchers are profiled. These researcher profiles often need to be complemented with their publication
Other internal reporting systems that track research output, similar to the above
A common challenge for managers of these applications is to identify every paper written by the institution's researchers,
and abstracting and indexing services like Scopus make that task easier by profiling researchers and their affiliations and publications,
and making them accessible through APIs. We allow this use case under the following conditions:
The application needs to be operated by, or on behalf of an academic institution that has a subscription for Scopus. If the developer and/or operator of the application is a third party contracted by the institution, this third party needs to have a separate agreement with Elsevier to use the APIs.
If the application is developed and/or operated by a third party, the third party is not allowed to differentiate the fees for the use of the application based on Scopus data being in- or excluded by the application
For as long as the institution has the Scopus license, the application is allowed to query the APIs to identify publications written by its researchers (also those published prior to a researcher's affiliation with the institute), and to retrieve the following metadata for these publications from the APIs:
The record IDs (Scopus ID and/or eid)
DOI
PubMed ID
the Scopus author IDs of the authors of the document (this includes the IDs for co-authors of the document not affiliated with the institute)
authors' names
authors' countries of residence
authors' affiliations
document title
document publication year
source (journal) title
ISSN
source type (journal, conference proceeding, etc.)
volume/issue/pages/article number
document type (e.g. research article, review article, etc.
Publisher
Subject category (per ASJC)
citation count (number of times cited by other articles)
Author Metrics
H-Index
Doc Number
Citation count
Cited by
Source/Journal Metrics
CiteScore (forthcoming)
SNIP
SJR
The following Scopus items may not be displayed publicly:
abstracts
CAS registration numbers
author email addresses
non-English language tags
chemical names
controlled vocabulary
The institution is allowed to store this metadata in its IR/CRIS in perpetuity even after it has cancelled its Scopus license (in which case it is not allowed to continue to retrieve new records through the APIs)
The metadata in the IR retrieved from Scopus through the APIs can be shown to any IR/CRIS user, regardless of this user being affiliated with the institution or not
Cited-by counts can be aggregated for use in internal bibliometric analysis, but not be aggregated for external display.
Scopus should be identified as a source and a link to the Scopus record and cited-by results list should be displayed as described in the Scopus Attribution Guide.
Please note that this policy is also reflected by a clause in standard Scopus license agreements.
Detailed policy for ScienceDirect:
Using ScienceDirect APIs to enhance your institutional repository
We allow this use case under the following conditions:
The metadata fields that can be retrieved and displayed are those listed for the ScienceDirect Search API (definition) and the Article Hosting Permission API (example).
Search results/records need to be clearly marked as leading to the final published version and need to link back to the article or chapter on ScienceDirect.
Along with each link to an article or chapter on ScienceDirect, an indicator needs to be displayed that informs the user if (s)he has access to this article/chapter on ScienceDirect, based on the user’s IP address.
In case more than one instance of the article or chapter is available in the system, the ScienceDirect version should show up higher on the page in at least the same font size as the other links.
The system may, but is not required to, embed the final version of a ScienceDirect article/chapter within its web pages, subject to the user’s IP address being authorized for access to that article/chapter on ScienceDirect.
The system is allowed to store this metadata in perpetuity even after it has discontinued its use of the ScienceDirect API to retrieve publication metadata.
The ScienceDirect API services as described in the IR/CRIS/VIVO use case, are available to all IRs free of charge upon acceptance of a click-through agreement when registering for an API key. If your institution cannot accept a click-through agreement, you can contact your local sales representative for a ScienceDirect Amendment or an Agreement for non-ScienceDirect customers.
To start with the ScienceDirect API services program for your institutional repository, please follow this three step approach:
Register for the institutional repository program here and submit your API key: https://www.elsevier.com/solutions/sciencedirect/forms/institutional-repository-managers?rURL=Direct. The Elsevier integration support team will add the ScienceDirect IR settings to your API key, and confirm back. If your institution already has a Scopus API key, you can submit this API key to have the settings for the SD IR services added.
Develop your IR software. Detailed technical documentation on the ScienceDirect API integration can be found here.
Detailed policy for SciVal:
SciVal metrics in institutional repositories, research information systems, VIVO
Definition: the client application is:
An institutional repository (IR) in which the institution's research output is captured by storing a record / version of each paper written by its researchers, and/or
Current research information system (CRIS) that tracks an institution's research performance by, amongst others, capturing each paper written by its researchers, and/or
A local VIVO installation (http://vivoweb.org/ about, http://vivo.sourceforge.net/) in which an institute's researchers are profiled. These researcher profiles often need to be complemented with their publication
Other internal reporting systems that track research output, similar to the above.
By utilizing the SciVal API, the managers of these applications can download the most common metrics for institutions and researchers. It allows them to automate repetitive tasks, thus saving time and effort.
We allow this use case under the following conditions:
The client application needs to be free of use and non-commercial. This also means that it should be free of advertising.
The client application needs to obtain an API key by registering here.
The owner/operator of the client application needs to have a SciVal license, or operate the application on behalf on an institution that has a SciVal license.
The client application needs to run within, and execute the API calls, from the user's browser and not proxy the calls through a server-side component.
The client application needs to link back to SciVal records as described in the SciVal Attribution Guide.
