[Feature Request] Support Scopus API
Posted: Wed Apr 19, 2017 5:36 am
Hi, I'm not sure if this could be solved using an Import filter (though I don't think it supports REST?) or somehow hacking the OpenURL commands (though I can't see how to keep my WOS URI and search arguments and add the URI and different GET arguemnt for Scopus), but I would like some way to integrate Scopus search into Bookends.
Elsevier has created some very clear API documentation:
https://api.elsevier.com/documentation/ ... chAPI.wadl
including nice interactive API testers:
https://dev.elsevier.com/scopus.html#!/ ... opusSearch
The simplest route would be to just allow us to trigger a Scopus search using a selected references DOI, this would require a query and then parsing the response for a URL to open in a browser, so for example:
returns JSON including the links to the scopus page, and the link to the wonderful cited by summary:
I know not all institutions have access to Scopus, but that is true of Web of Science and JSTOR which you have integrated into Bookends. Scopus is owned by Elsevier, and is therefore a major reference indexing system. Citation searching seems better in Scopus than any other system.
Elsevier has created some very clear API documentation:
https://api.elsevier.com/documentation/ ... chAPI.wadl
including nice interactive API testers:
https://dev.elsevier.com/scopus.html#!/ ... opusSearch
The simplest route would be to just allow us to trigger a Scopus search using a selected references DOI, this would require a query and then parsing the response for a URL to open in a browser, so for example:
Code: Select all
https://api.elsevier.com/content/search/scopus?query=doi(10.1093%2Fcercor%2Fbhl020)&apiKey=XXXCode: Select all
{
"@_fa": "true",
"@ref": "scopus",
"@href": "https://www.scopus.com/inward/record.uri?partnerID=HzOxMe3b&scp=34247111185&origin=inward"
},
{
"@_fa": "true",
"@ref": "scopus-citedby",
"@href": "https://www.scopus.com/inward/citedby.uri?partnerID=HzOxMe3b&scp=34247111185&origin=inward"
}
Damn that is a shame (as Scopus is actually very good), and I understand your position entirely. This is the sort of thing where a some kind of plugin interface for Bookends would help. You would provide a generic way to trigger a URI request from Bookends and a way to read some data back. A plugin (nothing more than a python/bash/ruby etc. script) would then do the actual request and parsing. As long as the returned data was in a format you could handle (similar to the Pubmed browser for example), then you could show the results. In this case the plugin would simply need a user's personal API key thus Bookends would not be liable to any costs. 