primo-explore-unpaywall

primo-explore-unpaywall

Add 'Open Access available via unpaywall' link to search-result-avaliability-line-after in Primo New U

Background

Purpose

• We created this add-on to increase open access to online records for our patrons.
• This helps to increase overall access to our user whether or not they're logged in or we subscribe to the content in the results (WorldCat search)
• At BU, this results in around 50,000 additional open access links a week added exclusively to items that are not marked as oa

unpaywall API usage

• This functionality is made possible by a call to unpaywall.org's API (e.g. https://api.oadoi.org/v2/{doi}?email={email}").
• Its rate limits are extremely leniant (100,000 calls a day), and we never hit them (we do around half of that), but your mileage may vary (depending on how many of your results have DOIs [see 'How it Works' below]).
• If you do hit the limit, set showOnResultsPage to false. [see 'Additional Customization']

primo-explore-oadoi-link

• This customization was inspired by and originally developed on top of alliance-pcsg's primo-explore-oadoi-link customization, and owes very much to their great work.
• While we did seek to recontribute our changes to that repository (and not create our own 'fork' of it) and did end up creating a pull request.
• We decided to publish our's independently for the following reasons:
  • increased flexibility/control: having our own npm package allows us to make changes more quickly
  • sufficient distinction: our package uses the same API with a similar approach, but...
    • has entirely different templates/displays
    • is loaded into a different component/location on different pages (full-view-service-container-after vs search-result-availability-line-after)
    • has additional logging functionality and customizations
    • shares very little code and required an entirely new app.module anyway.
    • can be used indepently
  • maintenance and versioning: having our own project ensures we don't affecting existing users and can version our work as we go

How it Works

Wherever a <prm-search-result-availability-after> tag appears (/primo-explore/search, /primo-explore/fulldisplay), we...

1. look in its parentController (prmSearchResultAvailability) for the item info contained in it's result variable
2. if there's a doi (doi) in there and it's not already marked as open access (oa) use it to make a call to the afore-mentioned unpaywall api.
3. if that call ends up being successful, look for an open access download link (successResponse.data.best_oa_location)
4. if it has that, grab the url for it and place it right beneath the other "Online Access Available" link.

Usage

Adding the Package to your view in primo-explore

run the following command from within your view's main directory to add it as a dependency.

$ npm install --save primo-explore-unpaywall

this should add the following line to your package.json file...

"primo-explore-unpaywall": "^0.9.1"

and add the contents of this repository (at that npm version) into a node_modules/primo-explore-unpaywall directory for your current view. the presence of this package should mean that the package was successfully installed and added to your project.

Configuring via unpaywallConfiguration

to afford you with as much control as possible (and since we needed you to add your email for the unpaywall API call to work anyway), we've added some configuration options that you'll need to set up before the package runs.

our package attempts to read its options as variables within a constant object attached to the primo angular app, so all you have to do is add something that will be added to your custom.js file once it's built (either by created a unpaywall.config.js file or adding to an existing js file you use for other configuration options).

// unpaywall.config.js
app.constant('unpaywallConfig', {
  "email":"<your_username>@<your_institution>.edu"
});

note: only email is required, since unpaywall uses it to track requests and manage rate limits

Additional Customization

the following table describes describes some additional configuration options that are currently afforded to you by the package. an example implementation of this section can be found within this repo at src/custom.module.js:

name	default	description
logEvent	[see src/custom.module.js]	here's an opportunity to hook in whatever event tracking you have, (we use google analytics)
showOnResultsPage	true	determine whether the link is added to each item in the list of results
showVersionLabel	true	sometimes the unpaywall OA response qualifies the stage of publication the work was OA-available in (Submitted, Published, Accepted)
logToConsole	true	controls whether or not messages about what's going on in the component are console.log()-ed (visible in inspector)
showDebugTable	false	the debug table is a quick way to see unpaywall response data for the record in context a really ugly way (used to help troubleshoot, not meant for end users)
publishEvents	false	we use this variable within our sample implementation to ensure only real traffic is tracked (not us debugging/developing/testing)

note: the default for logEvent can be found within this repo at src/custom.module.js. it assumes you're using google analytics and calls it via window.ga