5.18.05.18.0

1. Web accessibility news

During this release, the Portal team continued our work towards making the Pure Portal fully WCAG 2.1 AA compliant. This time we focused mostly on improving the keyboard accessibility of the Portal.

While the development work was mostly completed, we were unfortunately unable to get these changes fully tested and verified in time to merge with this release, owing in part to the challenges presented by the current global situation. These improvements will therefore be held over until our next major release (5.19.0, coming October 2020).

2. Privacy and personal data 

3. Pure Core: Administration

Funding opportunity eligibility classifications were previously static and limited. Users with relevant roles can now extend and/or disable eligibility requirement classifications to cater for a broader range of criteria. This applies to both general eligibility requirements and academic degree eligibility requirements.

Pure will now use any Web of Science (WoS) ResearcherIDs attached to a person profile for automated search. Support for using WoS' ResearcherID to search for content when importing from WoS as an online import source was introduced in 5.17.0 (see 5.17.0 release notes). We have now extended functionality such that the ResearcherID is now part of the automated search feature. Automated search using ResearcherID is only available with the premium WoS, not WoS Lite.

Click here for more details...

To add a ResearcherID, enable automated search on that ID and view import candidates resulting from this search follow the instructions below.

Instructions	Screenshot
Enable Automated import via ResearcherID To enable, go to Administrator > Research output > Import sources > Web of Science then Enable automated ResearcherId search
Adding ResearcherID to person profile To add a ResearcherID to a person profile, within the Metadata menu tab of a person profile editor, select 'ResearcherID' from the ID Type drop down in the ID section. Enter the ID, click Create and save the person profile.
To enable automated search on ResearcherID From the Automated search menu tab of person profile editor, enable Web of Science.
Viewing import candidates The cron job, Search for Import Candidates, will use the supplied ResearcherID to query Web of Science and add any results as import candidates in the Persons with import candidates filter under Research outputs on the main Editor tab.

 

 

We have introduced a job to clean journals that have had incorrect ISSNs/eISSNs erroneously added via import or automated means. The job will search for all ISSN/eISSNs on a journal record and check via Scopus that the identifiers are correct for that journal. Any incorrect assignments will be corrected and any related content will be checked via their original record and assigned to the correct journal. This job will not correct manually merged journals.

Pure data export has always been requested on an ad-hoc basis for a specific issue or feature. To make it easier for customers, and for us to be able to deliver a better service and product, it is now possible to enable data export as a continuous export. For full transparency, we have expanded on the options of filtering out sensitive data, which are excluded by default. Customers will always have the ability to opt-out of continuous data export if they no longer want to send data to us.

Click here for more details...

The feature is still located under Administrator > Support > Database export. For a more thorough description of how we manage customer data, refer to the wiki page Customer Data Management .

If a customer opts in for the continuous export functionality:

• Each month an export of the customer's data will be sent to the Elsevier Pure team, where the customer is in control of what we are allowed to use the data for.
• The export will be sent at the end of the month and will be retained for 35 days, and then automatically deleted.

Instructions	Screenshot
Data Usage The following data usage options are available. Customers must select at least one option. An explanation of each option is provided below: General development and bug fixing Make your data available for the Elsevier Pure team to use it during the development of new features. You are welcome to write an additional note if you would like to be contacted regarding new feature development. You are not guaranteed to be involved, but if we are using your data to develop a new feature, we might reach out to you for feedback. Feature testing A feature has been developed and requires testing on a production data set, to help us identify and fix potential errors in the new features. Bug fixing on issues created by my institution Helps detect and fix your specific reported defects We will only use the data dump when fixing issues which have been reported by your institution. Migration testing To test that a Pure upgrade can continue successfully without any interruptions or migration errors. Provides peace of mind that your next Pure version will not encounter errors due to your data. You are more than welcome to only tick this option, as this also helps us deliver a more stable product to you and your peers.
Sensitive data Customers can clearly specify whether sensitive data should be included in a data export. By default no fields are included. Note: your institution may have more options, depending on your modules.
WebDAV share   Note, WebDav is deprecated from primo April 2024. Data dumps are now stored in Amazon Web Services (AWS)      Customers need to specify access to our WebDAV share, where the dump will be upload, and later removed as soon as it is in our internal systems. If you need help in completing this, please reach out to Pure-Support@elsevier.com. Once configured and saved: A job will be scheduled to send the data between the 20-25th each month. It will be exported at a random hour between 8-12PM on the randomly selected day. We will inform you if the data export was not successful. This could be if you are running out of storage. Before the job runs, it always checks if there is sufficient storage, if not, the job will stop and send a notification email, to this configured e-mail address. The date of the next extraction is shown on the job configuration page You have the option to stop this schedule and no longer send data continuously Data will automatically be deleted 35 days after we have received it. One time data extraction Customers still have the option to send data as a one-time export. The same configuration options regarding data access, and sensitive data can still be specified in the WebDAV share configuration.  One time exports with different data restrictions can be made even if you have continuous export configured.

 

 

4. Pure Core: Web services

To simplify querying using publishedBeforeDate and publishedAfterDate we have changed its type from a datetime to a date. Going forward you now query without time, as this is redundant in regards to the field itself in Pure. 

Old query example:

New query example:

New type injects attribute 'formatted' into the XML elements hostedPublicationTitle, hostedPublicationSubTitle, and publicationSeries.name.

New result example:

If you have configured the Pure research output model to have book series as journals you can now query for them using a POST query.

New POST example:

The early access Pure API now supports the management of organizations in addition to external organizations.

Click here for more details...

The Pure API is an evolution of the existing REST web services, to support a backwards-compatible read and write REST JSON endpoint for using and managing research information data in Pure.

In order to achieve these objectives, we've made several changes to how the web service endpoints are structured and the format of the managed entities in the new API.

• The endpoints for an entity are structured so it is clear where you can expect REST or RPC semantics - this should make it easy for developers to interact with the API with a minimal upfront time investment
• The entity format is optimized in regards to JSON data modelling best practices and with an expectation of the model evolving in a backwards-compatible manner in the future
• The API specification is defined and published as an OpenAPI 3 specification enabling service users to quickly generate a client while at the same time providing developers with useful documentation on the API and its semantics
• The entity API includes several helper operations that return the allowed values for the different parts of the entity model where this is relevant - this should make it easy for developers to submit valid changes to the write portions of the API
• All modification requests are made on behalf of a specified Pure user and clearly audit logged with both user and API key details
• As we expect the API to be able to support older clients updating against a newer version of the API all PUT requests have JSON merge patch semantics - this ensures that older clients do not inadvertently clear new properties that they don't know about

When the module has been successfully enabled a Swagger UI representation of the OpenAPI 3 specification will be available at https://{your Pure hostname}/ws/api/api-docs/index.html?url=/ws/api/openapi.yaml . Alternatively the latest API on the development community sandbox server can be found in this Swagger UI. A sample Java client that can be used as a starting point for developing a client can be found on the GitHub page.

Information	Screenshot
The early access Pure API can be enabled in the Pure administrator section. Please note that enabling or disabling the Pure API module requires a restart of Pure in order to take effect.

All use of the new endpoints requires an API key that is generated in the "User API Access" section of the "Pure API" administrator pages.

The main difference from the existing web service API keys is that the new Pure API requires a user that the system using the API key will act on behalf of.

 

 

 

5. Integrations

In this release we have made a number of updates to the ORCID integration:

In this release we have added the integration to the DBLP computer science bibliography, a comprehensive database containing open bibliographic information on more than 5 million scientific publications.

Click here for more details...

Instructions on how to enable, add and search for content from DBLP are shown below:

Instructions	Screenshot
To enable DBLP as an import source, go to Administrator > Research Output > Import Sources
To search and import content, go to ‘Add content’ and in Research Output > Import from online sources select ‘dblp’.
Search for content using the search bar. It is then possible to import or remove import candidates. Note: if an import candidate is removed, it will not be included in future searches.

 

 

The Scientific Electronic Library SCIELO is an open bibliographic database covering a selection of scientific journals. Initially covering scientific literature from Brazil, it now indexes research from 16 countries in South America and South Africa. In this release we have improved the integration with SCIELO by introducing additional fields to search for content.

In addition to searching for content by using words from the Title, Abstract, Author Names, Organizational Unit, and DOI, the following fields have been introduced:

• Publication date (by year range)
• Keywords

Click here for more details...

Instructions on how to enable, add and search for content from SCIELO are shown below:

Instructions	Screenshot
To enable SCIELO as an import source, go to Administrator > Research Output > Import Sources
To search and import content, go to ‘Add content’ and in Research Output > Import from online sources select ‘SCIELO’.

 

 

In this release we have added integration to the Jisc Publication Router. The Jisc Publications Router provides a way for Pure customers to receive notifications from publishers whenever a publication with their affiliation has been added or updated. By bypassing indexing services such as Scopus or WoS, the Jisc router speeds up the import of relevant content into Pure. 

In addition to reducing your Institution's administrative effort and maximising discovery and distribution of content, The Jisc Publications Router helps institutions comply cost-effectively with the Open Access policies of research funding bodies, currently valuable to UK customers considering the upcoming REF.

Access to the Jisc Publications Router is currently limited to UK customers. Before using the router integration in Pure, your institution will need to have an account set up and an agreement in place with Jisc – details available at https://pubrouter.jisc.ac.uk/about/start-up-guide-for-institutions/

Click here for more details...

Setup instructions

Instructions	Screenshot
To enable the integration with Jisc Publications Router, in Administrator > Research Output > Import Sources set the 'Jisc Publications Router integration' to ON.
In the 'Configuration' tab insert Account ID and API Key:
By default 'Notification retrieval and processing' is turned ON, meaning that if a pdf version of a record is found this will automatically be imported. It is possible to toggle this option OFF; in this case when a new import canddate is found it will still be possible to select the attached pdf file, when available. Once the integration has been setup, the job will run in the background and find import candidates. This job is configured to run once per day, between 06:00 and 08:00 (the exact time is randomized as to stop all Pure instances to begin querying the Jisc API at the same time). The job can also be triggered manually by selecting 'Run Job now'

Import and Update Candidates

Once the integration has been enabled, import candidates can be found in Research Output > Organizations with import candidates. Records will be shown for the default managing organization. 

Update candidates are created if a match is made on either DOI or PubMed ID. It is then possible to import or reject candidates. Once candidates have been rejected, they will not be shown when the synchronization runs again.

Rejected candidates can be cleared by clicking "Clear rejected candidates" on the Jisc Router job configuration.

 

 

In this release, the NIH grant feed for the synchronization of and Institution's awards and projects has been replaced by the Elsevier Funding Database (previously known as FROS Awards Service). In addition to awards and projects funded by the NIH, the Elsevier Funding Database comprises a number of different funders, and the service will be expanded in future releases of PURE to include data from additional funders such as the Federal Reporter and the NSF.

The jobs related to the Elsevier Funding Database can be found in Administrator > Jobs > Cron job scheduling, under 'Award Synchronization' and 'Project Synchronization (New)'.

In this release we have completed the integration with CAFE, a cloud-based process which provides notifications when content has been added to, updated, or deleted from ScienceDirect and/or Scopus.

Through the CAFE feed it is possible to import a number of journal-level metrics, such as:

• Number of publications
• Citations
• Citescore

The CAFE feed can be found in Administrator > Jobs > Cron job scheduling, under 'Scopus: Update/Create journals and metrics'.

We are pleased to announce that in release 5.18 we have included improvements to the PRS/QABO publication import job. While this job previously only matched internal persons that were profiled, this has now been changed to match non-profiled internal persons on Scopus IDs. As a result this will stop

• the creation of external persons where the person was actually internal
• the creation of external person records for internal persons that were profiled

There are still a few edge cases where a duplicate person might get created if the person is formerly profiled. The duplicate will in most cases be deleted by Master Data clean up job, which is a part of the QABO/PRS sequence of jobs.

We will continue to work on this job in the next releases to further improve matching on persons and to make this overall service more robust. For more information and updates on the QABO , see PRS/QABO related issues.

6. Unified Project Model and Award Management

7. Pure Portal

With our ongoing redesign of the Pure Portal, we aim to increase the visual impact of key landing pages while also allowing for a stronger integration of your insitutional brand.

In this release we are happy to announce the first major feature of this redesign, our bold new 'hero image' that will be displayed on the front and center of the homepage of your Portal. With this, you can now ensure your Portal stands out from the crowd while showcasing what makes your institution special:

This is not only key to the new look of the homepage, but also lays the foundations for an improved visual display throughout the Portal and how we will be introducing more space for images and other multimedia elements such as video.

In order to get the most from the new 'hero image' homepage design, we made some changes to the search field on the homepage. These simplify the existing design, making searching more intuitive and less complex for new users.

In the 5.17.3 minor Pure release, we delivered our brand new homepage banner feature. We designed this with highlighting coronavirus-related material in mind, but it can be used to highlight any key content, either on your portal or elesewhere.

To find out more on how to maximize showcasing of key content via this banner, check out the Pure version 5.17.3 release notes.

We have also now in this release encoded the banner search query in a more compact form to ensure compliancy with all browsers. This resolves a reported bug that occured when search strings were too long.

By redesigning our Pure Portal search filter interface we have made the search process faster and more intuitive, allowing Pure users to narrow down content and surface the most relevant results. 

To achieve this, all the search filters have been moved from their previous position (below the search bar) to a column on the lefthand side of the page:

Adding the ability to export search results from the Portal has been a highly requested feature for some time. With the 5.18.0 release, we are making this a reality, meaning you can now more easily share your search findings with others.

In the last major release (5.17.0), we updated the layout of the Pure Portal pages for equipment and project pages to display links to the content related to those pages in a more structured way. In this release, the same changes have been rolled out to the Research Output and Dataset content types:

A new tab has been added to the Pure Portal profile pages, in order to separately display the work that a person has supervised from their own work. 

To indicate a person's research output over time, a small bar graph is shown on their profile.

While typically a quick indicator of a researcher's activity, we recognise that it in some circumstances this data can be misleading, or unflattering. We have therefore added a configuration allowing your institution to choose to hide this bar graph.

8. Reporting

With this release, we have introduced global reporter roles for all content types. These new roles will grant access to the new reporting module, and it will be possible to report on the selected content types, e.g. Global reporter of Research Output. This means that it is now possible to open the new reporting module up for more users so they can start using the new reporting module. Combine these roles to give access to the new reporting module for more users without having to provide editorial rights to users. If the global reporter roles are the only role that a user has, then the user can only see the new reporting tab, and use the new reporting module without being able to see the rest of Pure. 

This is part of the ongoing development of the new reporting module and we are planning for more changes around the roles in the new reporting module to enable even more fine-tuned access and usage of the new reporting module.

As part of ongoing interviews and feedback from users, we have introduced Tips and Tricks to the home page of the reporting module.

These Tips and Tricks will:

• Highlight various features of the new reporting module
• Help with on-boarding
• Help discover the multitude of features and possibilities in the new reporting module
• Help users in their daily tasks

The reporting home page will be updated with more Tips and Tricks with each release of Pure.

It is now possible to disable the ability to schedule reports in the classic reporting module via Administrator > Reporting.

Click here for more details...

When disabled the ability to set up new scheduled reports will be removed from the classic reporting module

It is possible to cancel any already scheduled reports, by clicking 'Show scheduled reports' button on the Report configuration page, see screen shot above. There is possible to cancel selected ones, or all at once.

Cancelling all of the scheduled reports will remove the scheduling and it will have to be set up again on all of the reports if they are needed once more.

 

 

 

9. Country-specific features

In this release we have made a number of updates to the REF module:

10. Additional features and notes of this release

Pure now supplement session cookies with a 'SameSite' attribute to satisfy requirements set by current and soon to be released browsers when using single sign-on and other functionality that relies on non-GET HTTP methods, and to better protect end-users against attacks. Its value is set to 'None' for anonymous sessions and 'Lax' for fully authenticated sessions by default. The default value can be changed individually via Administrator > System settings > Cookies (SameSite). This includes disabling addition of the attribute entirely.

Please notice that the Pure Security Guide now strongly recommends to use HTTPS for all Pure web applications and recommends that the 'secure' attribute is set on Tomcat connectors. That is especially important when a 'SameSite' attribute is added to cookies as browsers can now or in the future require such cookies to also have the 'Secure' cookie attribute.

Sherpa Romeo is deprecating their current 'color' service for journal OA policies and permissions. Based on current information found at http://sherpa.ac.uk/romeo/index.php, and confirmed by Jisc, the providers of Sherpa Romeo data, the following dates are confirmed:

• Launch of new service: April 14th 2020
• Decommission of current service: July 31st 2020

The updated web access can be found here: https://v2.sherpa.ac.uk/romeo/

Significant changes have been made to Sherpa Romeo, with multiple options for Open Access routes per publication state. Interviews with customers are underway to determine what is the best information to surface at the research output and the journal content level.

Service to Sherpa Romeo will continue to be available until the API shutdown, upon when Pure will switch off access to the old API to prevent system errors.

In 5.18.1 users will be shown a link to Sherpa Romeo to access the latest journal OA routes, and once customer interviews are complete, the updated information will be surfaced in full on the research output and journal editors. The transition to the new Sherpa Romeo will be complete on release of 5.19.

We highly recommend administrators and other relevant roles review the new OA access routes information.