Page History
...
All of the above features can of course be enabled or disabled easily, to ensure only the relevant features are displayed.
API keys can be obtained from integrationsupport@elsevier.com after acceptance of the terms and conditions of the program (no cost applicable).
...
Registering a Developer API key
The functionality will send requests to ScienceDirect APIs to retrieve metadata. These APIs are protected with user accounts and keys to avoid abuse by robots and malicious users.
To register an API key, go to: https://dev.elsevier.com/apikey/create
Further support for the API key registration process is available from integrationsupport@elsevier.com
Adding the functionality to your DSpace codebase
| Info | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Elsevier and Atmire are working together with the DSpace community to add this functionality to the DSpace 6 codebase. As of Oct 28th 2016, this is still work in progress. The latest information can be retrieved on:
|
Because the functionality is currently not part of the standard DSpace codebase, the code changes currently have to be added as a customization. To keep these cleanly separated from standard DSpace code, Atmire's patch files are adding these changes in the /dspace/modules/additions directory.
Patching DSpace 5
The code changes have been compiled into a patch file that has been tested against DSpace 5.4 and is already in use in production.
| View file | ||||
|---|---|---|---|---|
|
Installation instructions:
- Download this patch file onto the machine where you are executing your DSpace maven builds (mvn clean package)
- Put the patch file in the root of your DSpace SOURCE directory. So NOT the installation directory where dspace is installed/deployed
- OPTIONAL: check if the patch can be applied to your codebase by running "git apply --check --verbose ./elsevier5.4-updated.patch"
- Use git-apply to apply the patch to your codebase. "git apply ./elsevier5.4-updated.patch"
After applying these changes to the codebase, follow the standard procedures for building the code with maven and deploying it on your Tomcat. These can be found at Upgrading DSpace#UpgradeSteps from step 4 "building DSpace" and onwards.
Configuration: Enabling or Disabling the features
The following steps assume that you have successfully patched your DSpace or that you are running a version of DSpace in which the ScienceDirect Live import code has already been merged.
Live import
The live import should be enabled in the dspace/config/item-submission.xml. The step below should be included prior to the Describe metadata steps:
...
Overview
Content Tools