5.25.05.25.0

1. Web accessibility

The Pure Voluntary Product Accessibility Template (VPAT) report has been updated. The Pure Portal underwent accessibility testing on the 25th of July, 2022. You can access full results of this assessment through a link included in the 'About web accessibility' section found in the footer of the Portal.               
The analysis and results showed:

• Portal accessibility fully supports 43 items and partially supports the remaining 7.
• Partially supported areas are primarily due to external dependencies like Altmetric and PlumX widgets, which the Pure team is not in control of.
• The UN Sustainable Development Goals (SDG) official logos do not have high enough color contrast. Although a black and white alternative is available, in this particular case a decision was made to promote recognizability over accessibility.

All of the partially compliant areas were reviewed by our accessibility experts. While most areas cannot be fully fixed in the current setup (primarily due to external dependencies), we managed to make one of these areas (1.3.1 Info and Relationships) fully compliant.

2. Pure Core: Administration

To increase the security within Pure, we are now scanning files for viruses. While the actual scanning of the files is performed outside Pure, you can now decide to show the status of files as a badge, and to block the download of infected and/or unscanned files. This feature will be enabled by default for all Elsevier-hosted customers. Self-hosted customers will need to follow a dedicated guide on our Antivirus integration confluence page to take advantage of the feature.

In line with Pure's 5Cs data quality framework, we have expanded the model for dataset records in Pure to align with OpenAIRE guidelines for dataset interoperability (https://guidelines.openaire.eu/en/latest/data/index.html). To facilitate the enrichment, monitoring and management of datasets for OA compliance, including all mandatory OpenAIRE fields, it is now possible for users to add License information at the record and file level. The users can also get an easy overview of whether a particular dataset is OpenAIRE-compliant through the newly added OpenAIRE compliance check.

Click here for more details...

License information on a record

Users can specify a data-specific license on the dataset, with values provided in the modifiable classification 'Datasets: Document licenses' (/dk/atira/pure/dataset/documentlicenses).

Example:

License information is available in:

• Dataset editor
• Reporting
• OAI-PMH via CERIF XML. If there is a license set on the dataset, this will now be exposed as part of product set (see CERIF XML mapping for more details).               
  

License information can now be added via:

• Synchronization/import
  • The configurable dataset synchronization now supports synchronizing the license information if data is provided for it in the XML.
  • The dataset bulk import functionality now supports importing in the license information if data is provided for it in the XML.
• Data Monitor
  • If datasets are imported from Data Monitor, license information is added directly to the new license field at the record level and the access is set based on the license provided.

OpenAIRE compliance check

To help users identify which fields are required, an OpenAIRE compliance check can be displayed on the dataset editor in the Access and Compliance section.

Enabling the check You can enable the check in Administrator > Open Access > Configuration > OpenAIRE compliance check.                The check is disabled by default.
Updating values in some fields will not trigger immediate updates to the compliance check, but users can click the Update button to trigger an update.

Filters and availability of compliance status in reporting

The OpenAIRE compliance status can be used elsewhere in Pure to help identify records that need enrichment.

OpenAIRE status filter When the compliance check is enabled, a corresponding filter in the dataset overview will become active, and each compliant record will be tagged with an OpenAIRE icon.
OpenAIRE status as column value in reporting The compliance status can be used as a column value in reporting. It can be found under the Access section.
OpenAIRE status as filter in reporting Compliance status can also be used as a filter in reporting.

 

 

Deduplicating journals is now possible in the Data Quality interface. You can merge and set journals as distinct from each other using the same functionalities as for external organizations. See the Data Quality interface instructions for more details. 

The DOI and Scopus source links for research output (where provided) are now also available in the top right corner of the metadata section of the editor to provide easier and faster access to the source of record for checking and validation purposes.

3. Pure Core: Pure Web Service and Pure API

From 5.25.0 we consider the Pure API stable, and no longer in early access. While the Pure API is not fully featured yet, we are confident that the implemented endpoints are ready for production use. This means that backwards compatibility of the contract will be guaranteed for the implemented endpoints intended for management of resources. The only exception is the /search endpoint which is a carry-over from Pure Web Service, and will likely be changed when we define how the query model for the Pure API.

Pure API now supports the management of Application, Award/Grant, and Project outputs. CRUD (Create, Read, Update, Delete) operations on these content types are now available.

Most metadata fields are supported, except for milestones and budget/expenditure.

Use cases catered for in the current release:

• Legacy import as an alternative to the current bulk upload functionality
• Enrichment of existing entities with additional metadata
• Full extraction of all entities in a Pure installation, including confidential content, using Access Definitions introduced in 5.22.0

If your use case is not covered by this implementation, we would like to hear from you and add it to Use cases.

As mentioned in the 5.24.0 release notes, some breaking changes have been introduced.

• The contributors field on research output will support three types instead of just one. This is to make it clear for the API user what fields are available/required, based on what type of contributor they are adding, i.e. internal person, external person, or an author collaboration.
• Organizations are sometimes spelled with an 's', both in the field and in the documentation. We updated this to be consistently spelled with a 'z'. This is to be compliant with Elsevier API standards.

In addition, we have made the decision to not include derived properties in the Pure API models, as these are not editable. This means that the following properties have been removed:

• The openAccessPermission and openAccessEmbargoDate properties on research output have been removed, as they're derived from the values on the associated electronic versions.

4. Integrations 

We have used the API migration as an opportunity to optimize how requests to WoS are made and to better handle request quota limits. The improvements to the integration with the WoS Starter and Expanded APIs aim to facilitate their usage and to ensure that the number of requests that are sent from Pure is kept to a minimum. While the functionality of the integration remains unchanged for the end-users, the structural changes in Pure result in a smarter usage of API quotas. Additionally, it is now easier for the administrators to control settings for the two APIs as the source configuration is available on a single page. 

To provide you and your institution with a complete coverage of your data, we are continuously adding integrations and import sources that range over several content types and often have different data structures and requirements. We know that monitoring the usage of different sources and the performance of different import jobs is not always straightforward, which sometimes makes optimizing import processes (or identifying problems) challenging.

This is why we have started working on new set of tracking pages for integrations in Pure. These pages will be a space where research administrators can easily get an overview of the usage of import sources (both for requests made from Pure and for imported content), APIs and import jobs used by their institution and researchers.

We are happy to release the first pages that will make up this new tracking space, and we will continue working on adding functionality and additional APIs and sources over the next releases, so stay tuned! 

It is now possible to run an automated search based on the researcher's profile ID in researchmap, and configure the integration to either list records as import candidates, or automatically save the content in Pure. A number of configuration options let you determine the rules used for matching and enrichment of content in Pure.

Click here to expand...

Background

researchmap was first added to Pure in 5.21 as an import source, allowing researchers to manually search for and bring content into Pure. With this release, we have expanded this integration and added functionality to automatically import research outputs related to researchers at their institution.          
The current configuration options for the automatic import of research outputs from researchmap are described below. The work to improve the automatic import configuration is ongoing and we are adding more configuration options and matching rules. Our goal is to optimize the automatic import configuration by making it possible to customize rules per import source.

Feature details

Instructions	Screenshot
Enabling automatic import To enable the automatic import of research outputs from researchmap: Go to Administrator > Research output > researchmap Select the 'Automatic Import Configuration'.
Setting deduplication rules It is possible to set rules for the deduplication of content. A description is shown when a rule is selected from the menu.
Setting import rules You can decide if you want to list records as import candidates or, based on configurable rules for the creation of content, automatically save the records in Pure.
Setting matching and data enrichment rules In the 'Matching rules' section, you can set the conditions under which content is matched in Pure.  In the 'Data enrichment rules' section, you can set the rules (and data) with which you want to enrich the new content imported to Pure.
Setting workflow step for imported content You can also set the workflow step the imported content should be saved in to allow for a check on content that was imported directly.
Importing content in bulk mode If you are enabling researchmap as an import source for the first time, you can select to import content in bulk mode. The job will check the import source for all content related to an organization, and all matched content will be imported into Pure in line with the configured import rules.            This will import all publications from researchmap that belong to researchers at your institution. After the import has run in bulk mode, it goes back to its regular

 

 

The JISC integration in Pure has been updated to the new v4 version of the API with no change to functionality. For more details on the integration see the 5.18.0 JISC integration release notes.

5. Unified Project Model and Award Management

While previously milestones could be added to awards and applications, they can now be added to the project and ethical review content types as well. This allows for better support of task management across the award management life cycle. Milestones on projects and ethical reviews work similarly to milestones on awards and applications: you can create and specify details for custom milestones, or choose to create templates.

Milestone overview screens show what content family milestones are associated with, and milestone reporting includes support for all milestones types.

Click here for more details...

Instructions	Screenshot
Adding milestone templates To add milestone templates for ethical review and projects: Go to the 'Milestone templates' section in the left-hand menu of Award Management. Select 'Add template'.  From the drop-down menu, select the content family the template should be created for.
Adding milestones to content To add milestones on ethical reviews and projects: Open the related content record and scroll to section called 'Milestones'. Select from the available milestone templates, or choose to add a custom milestone from the editor.
Notifying users User notification options, including task and email settings, are in common with the existing milestone model.
Milestones overview Milestone overview screens include an indicator of the content family the Milestones are associated with. You can also search by content family, and/or by content title.
Reporting The Identification option lets you report on milestones by content type they are assigned to.

 

 

6. Pure Portal

In addition to the new OmniScience thesaurus added in 5.24, based on client requests, we have added support for the International Nuclear Information System (INIS) Thesaurus. Maintained by the International Atomic Energy Agency, the INIS Thesaurus provides a classification scheme for institutions specialising in nuclear research. It can be used as the sole thesaurus applied to your content or combined with the OmniScience vocabulary, allowing for content to be fingerprinted against both vocabularies.

You can now enable the display of external organization relationships for both research outputs and projects on the Portal. For research outputs, this means showing the external organizations affiliated to authors on the output. For projects, this applies both to the external organizations affiliated to the project as well as any collaborative partners.

With this release, you will have a number of new configuration options available on how the portal is rendered. These include choosing:

• which impact description fields should be displayed
• whether the status of the impact should be displayed
• what job information to show on a person's affiliation (e.g. job title or job description)

Until now, the organization hierarchy listing page of the Portal showed full hierarchy, which could become unwieldy for institutions with many organizational units. From this release on, institutions with more than 100 organizational units to be displayed in their hierarchy will not automatically expand beyond the first level. The hierarchy can be further expanded manually.

As part of this release there are a number of small changes that have been made to support special use cases or to improve stability. To see more details of these expand the relevant section below.

7. Reporting

We have redesigned the way of reporting on metrics in order to improve the performance of the reporting module. In previous versions, metrics were selected as part of the details of the content, now this have been changed into a relation to the content. The data is now stored in a format optimized for reporting.

In this release, we have made the new improved way of reporting on metrics available for: Research Outputs, Journals, and Publishers. This is the first iteration of the improvement, and we are working on how to make the user experience even smoother and more efficient.

You can now control the grouping of columns in the data table widget in the data story. Before, the table widget always grouped columns in order from left to right; from now on, you can define which columns, if any, should be used for grouping.

Available resources

Pure Manual > Reporting Module (Beta) > Data story

 

Click here for more details…

Instructions	Screenshot
Selecting columns To select which columns should be used for grouping in the table widget select Arrange columns
Grouping by column To group by a column, simple drag and drop the column to the area.  You can create multiple groupings in one table. Any columns that can be used for grouping are marked with a (G) next to them.
Any columns that can be used for grouping are marked with a (G) next to the name.