5.19.05.19.0

CORE (https://core.ac.uk/) is an aggregator of OA repositories, harvesting research papers from data providers from all over the world, including institutional and subject repositories, Open Access and hybrid journal publishers. It contains over 186 million OA articles from tens of thousands of journals, collected from 9,980 data providers around the world. The full list of data providers can be found at CORE's provider listing. CORE will supply data for the UK REF 2021 Open Access Policy Audit to Research England, and the integration with CORE will make OA articles more easily accessible and more useful to researchers, and will allow institutions to monitor their OA output. 

Click here for more details...

To enable CORE integration you will need to provide an API key, which can be requested at https://core.ac.uk/services/api/.

Instructions on how to enable, add and search for content from CORE are shown below.

Instructions	Screenshot
To enable CORE 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 ‘CORE’.
Search for content using the search bar. It is possible to search by author names, DOI and title. It is then possible to import or remove import candidates.

 

 

bioRxiv (https://www.biorxiv.org/about-biorxiv) is a free online archive and distribution service for unpublished preprints in the life sciences, containing over 80,000 papers by more than 348,000 authors.

The integration with bioRxiv provides researchers and institutions with content in biological sciences, especially relevant when following latest COVID-related studies and results.  

Click here for more details...

Instructions on how to enable, add and search for content from bioRxiv are shown below.

Instructions	Screenshot
To enable bioRxiv 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 ‘bioRxiv’.
Search for content using the search bar. It is possible to search by author names, DOI and title. You can define the time frame and subject category in which you want to perform the search. It is then possible to import or remove import candidates.

 

 

In this release, we have enriched the data of Research Outputs imported from Scopus and CrossRef by retrieving additional Open Access information. 

Records imported from Scopus will now contain additional information on:

• Open Access status flag

Records imported from CrossRef will now contain additional information on:

• Open Access status flag
• License

Information on the Open Access status of a document is associated to the DOI, electronic version, or to a specific version (file) of the document.

4. Pure Core: Administration

Pure customers use metrics to support research-based assessment and evaluations. As the number of metrics available to institution administrators is increasing rapidly, we are working hard to ensure that these new or newly-derived metrics are supported in Pure, and are easy to access and maintain. This release includes the following additions to the metrics suite.

Top percentile metrics are an article-level metric based on SciVal’s field-weighted version of the Outputs in Top Citation Percentiles metric. The top percentile is calculated based on the comparison of citation counts between articles within similar fields. Top percentiles are currently only available to SciVal customers. 

We are happy to announce that with release 5.19, Pure users will be provided with new Citescore and category journal metrics from Scopus. In addition to the existing job providing journal Citescore, SNIP, and SJR, new journal and category metrics are being imported through the integration with the CAFE service.

Click here to expand...

To import Scopus journal metrics go to Admin > Cron job scheduling, and select the job Scopus: Update/Create Journals and Metrics. Once you have selected this, it is possible to schedule the frequency at which the job runs and the roles who can manage it. 

The new metrics from Scopus are displayed together with other journal-related metrics in Journal > Metrics.

Citescore metrics	New journal-level metrics imported through CAFÉ include: number of publications total citations total citations (excluding self-cites) number of documents with zero citations percentage of articles cited Metrics are shown per year.
Citescore category metrics	New subject category metrics imported through CAFE include: journal rank quartile percentile

It is possible to add or edit category metrics by clicking Edit and updating the desired fields.

 

 

We are happy to announce that the Field-Weighted Citation Impact (FWCI) is now freely available to all customers. FWCI is the ratio of the total citations received by a publication, and the total citations that would be expected based on the average of the subject field.

Fractional counts on Research Outputs provide a more nuanced view on contributions of individual authors to a publication. The calculation is simplified and assumes that each author contributes equally. 

A new global role has been added to allow user accounts with no linked persons/affiliations to access the web service (WS).  Users with this specific role will be able to use the WS via basic authentication in the API call but will require additional roles in order to access the Pure content backend.

The Community Module helps effectively manage multi-institutional research projects, providing a shared reporting engine and a multi-institution portal that makes it easy to collate and aggregate the data, showcase the research assets and understand the contributions of each institution. As data is gathered from

several underlying Pure instances, a lot of effort has gone into improving data quality and transparency in this release.

In the following sections, the term Institution refers to a single Pure instance that is part of a Community. Community refers to the aggregating Pure instance running the Community Module with two or more Institutions.

Note: Some of the changes made in this release require a Pure Harvester upgrade. Pure Harvester is a service that makes data from the participating Pure Institutions available to the Community. Over time, we will migrate every Community to the new Harvester, but you can also reach out to us if you want to be migrated earlier. To be eligible for migration to the new Pure Harvester, all Pure instances in a Community must be upgraded to Pure 5.19.0 or higher.

Pure's rich data model allows for multiple dependencies between content types to unlock the research potential of an institution. When data from several Pure instances is combined in a Community, the network of relations becomes even more complex. This allows the Community to gain valuable insights, and showcase connections and collaborations.

However, removing pieces of such a complex dependency graph can be challenging. In previous versions of the Community Module, the content removed by one of the Institutions was not always removed from the Community. Instead, its visibility was set to 'Backend' to prevent it from showing on the Community Portal.

In 5.19, we have introduced support for a number of known scenarios, and we will also closely monitor the removal of data to ensure that the Community instance is always up-to-date.

Note: Some of the data retention improvements will only work with the new version of the Pure Harvester (see above).

Until now, automatic deduplication was only supported for Journals and Research Outputs. In this release, we expand the list with the following content types: Person, Event, Publisher, External Organization and External Person.

The deduplication jobs are available regardless of whether the Pure Harvester has been upgraded, but are automatically scheduled only with the new Pure Harvester.

With 5.19, content origin information is easy to see as it is included in the short render format used in content listings and search. For some content types, information about content origin is also available in the editor.

Note: This upgrade is only available when switching to the new Pure Harvester (see above).

Click here for more details...

Information	Screenshot
The following content types now have origin information in the short render: Prizes Activities Press / Media Facilities / Equipment External Person External Organization Person Organization Research output Applications Awards / Grants Projects Journal   Example: The red box contains the name of the Institution where the data originated from. If the content has been merged, it will be the name the primary contributor.
For Persons, Organisations and Research outputs this information is also visible in the editor. If content has been merged, you can see what Institution it originates from. This information includes source ID, with which you can either access the original content (if permitted), or reach out to the Institution that owns it to report data quality issues, or make other data-related queries. Example: The red box in the 'Publication import ID' section contains the primary ID. The red boxes in the 'Additional source IDs' section contain the secondary IDs. Contributor rank can be changed by switching the order of Institution IDs. As this is a manual task, it needs to be done with extreme caution so as not to corrupt the data.

 

 

5. Pure Core: Web services

The early access Pure API now supports the management of Journal, Publisher, and Event in addition to Internal and External Organizations. As part of the implementation of the thee new models, we reviewed the previously released models, which has led to the following breaking changes in the API in version 5.19.0 

Breaking change:

• Organization and External Organization field family has been renamed to systemName to reflect the meaning of the field.
• KeywordGroupConfiguration field targetFamily have been renamed  to targetSystemName.

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 have made several changes to how the Web Service endpoints are structured and to the format of the managed entities in the new API.

• The endpoints for an entity are structured so that 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 regard 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 do not 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. 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 Administrator>Pure API>User API Access. 

In contrast to the current Web Service API keys, the new Pure API requires a user that the system using the API key acts on their behalf.

 

 

 

5.2. OAI-PMH improvements: Ability to configure exposure of internal keywords

We have improved our OAI-PMH integration by adding new configurations. It is now possible to configure the visibility of individual keyword groups in the Web Service and OAI, and to select whether a keyword is exposed in the WS and in OAI.

Click here for more details...

In 5.19, Keyword Group Configurations will have a new toggle: Show in WS.

The toggle is enabled by default, which means that keywords will be visible in the Web Service and OAI.

This toggle can be switched to OFF if a keyword contains internal information that should not be exposed through the WS. 'Hidden' keywords will remain visible to administrator API keys, which are able to bypass this configuration.

 

 

5.3. Person Expertise added to Web Service 

In this release, we have added the option to expose information on a Person's area of expertise through the Web Service. In order to make use of this functionality the Person Expertise module must be enabled.

Click here for more details...

An example of how the Person's Expertise is displayed on a personal profile is shown below:

An (XML) example of how these areas of expertise are exposed through the Web Service is shown below:

Person Expertise WS example

<person pureId="18472" uuid="65c28253-a8a5-4a07-815e-d0378e811bad">     [...]         <personExpertise pureId="18484">     <areasOfExpertise>       <areaOfExpertise>Biology</areaOfExpertise>       <areaOfExpertise>Chemistry</areaOfExpertise></areasOfExpertise>     <areaOfExpertiseClassifications>       <areaOfExpertiseClassification pureId="18478" uri="/dk/atira/pure/person/personexpertise/maths">         <term formatted="false">           <text locale="en_GB">Maths</text>         </term>       </areaOfExpertiseClassification>       <areaOfExpertiseClassification pureId="18480" uri="/dk/atira/pure/person/personexpertise/physics">         <term formatted="false">           <text locale="en_GB">Physics</text>         </term>       </areaOfExpertiseClassification>     </areaOfExpertiseClassifications>     <willingnessToMedia>true</willingnessToMedia>     <moderatedWillingnessToMedia>true</moderatedWillingnessToMedia>     <type pureId="2361" uri="/dk/atira/pure/personexpertise/personexpertisetypes/personexpertise/personexpertise">       <term formatted="false">         <text locale="en_GB">Person Expertise</text>       </term>     </type>   </personExpertise>     [...]   </person>

 

 

5.4. Funding value changed to string 

Until now, currency values related to funding of awards were not human-readable after they reached a certain threshold.

In this release, the element types of the values have been changed to strings in order to improve value visibility. This means the value 3.45e8 will now be rendered as 345000000.

Click here for more details...

Example:

<awardedAmount>1E7</awardedAmount>
<institutionalPart>1E7</institutionalPart>

becomes:

<awardedAmount>10000000.00</awardedAmount>
<institutionalPart>10000000.00</institutionalPart>

The changes are:

ComplexType wsAward:

 ComplexContent:
 Extension:
 Sequence:
 Element totalAwardedAmount:
 The type of element 'totalAwardedAmount' changed from xs:double to xs:string.
 Element totalSpendAmount:
 The type of element 'totalSpendAmount' changed from xs:double to xs:string.
ComplexType wsAwardFundingAssociation:
 ComplexContent:
 Extension:
 Sequence:
 Element estimatedValue:
 The type of element 'estimatedValue' changed from xs:double to xs:string.
 Element awardedAmountInAwardedCurrency:
 The type of element 'awardedAmountInAwardedCurrency' changed from xs:double to xs:string.
 Element awardedAmount:
 The type of element 'awardedAmount' changed from xs:double to xs:string.
 Element institutionalPart:
 The type of element 'institutionalPart' changed from xs:double to xs:string.
 Element institutionalContribution:
 The type of element 'institutionalContribution' changed from xs:double to xs:string.
 Element institutionalFEC:
 The type of element 'institutionalFEC' changed from xs:double to xs:string.

 

 

6. Integrations 

In this release we have enriched the data of Research Output imported from Scopus by retrieving information for two additional metadata fields.

We have improved the integration with Data Monitor by making it possible for Pure users to edit the metadata of imported datasets. A new configuration has been added to the Data Monitor configuration page, giving users the option to run Data Monitor as a synchronization or import candidates manually.

We have improved the 'Match Scopus IDs For Publications' job so that false or incorrect matches will no longer be created. With this improvement, incorrect Scopus IDs will no longer be assigned to publications.

In release 5.19 we have revisited the existing Scival integrations in Pure and switched to SciVal's new API, as the current API will be deprecated.

Other than a change in endpoints, this has no implications for existing integrations. Functionality will remain the same. The affected integrations are the following:

• SciVal External Organisation Synchronisation
• SciVal Scopus Author ID Import
• SciVal Metrics Synchronisation
• Export organisations to Scival

More information on the new API can be found at SciVal's partner API description.

In release 5.19,  Spanish customers can import their Research Output directly from their CVN. In order to import content from CVN, the FECyT module must be enabled (see release note 5.17 for details).

In this release, the field groupAuthor has been replaced by the field authorCollaboration, as the groupAuthor field is being deprecated.

Although the new field authorCollaboration should be used going forward, groupAuthor will still be supported for some time.

If both fields are present, the field authorCollaboration will be used and a warning will be displayed in the job log.

A new configuration has been added to the Master List data import, making it possible to select whether to export your current master list with or without former Organisations and Persons.

To make use of the Master List to export your data from Pure, a Master List needs to have been previously uploaded in Pure. The new configuration can be found in Administrator > Bulk Import > Masterlist.

Note: the Master List data import is only available for customers with the Author Profile module.

7. Pure Portal

In the previous major release (5.18), we introduced large hero images on Portal homepages. With this release, we have enabled hero images on Research Unit (Organisation) pages to help you better showcase organisations within your institution.

We have taken our first steps towards supporting video content on the Pure Portal. To begin with, you can embed media content on Research Output and Research Units. YouTube and Vimeo are currently the two supported media platforms. We will be rolling out this functionality to cover other Portal pages types and other media platforms over the course of future releases.

Click here for more details...

Getting the URL - YouTube

To embed a video hosted on YouTube, find the video on YouTube.com. From that page you can use one of these options:

• Copy the browser URL.
• Right click the video, and select "Copy video URL".
• Use the "Share"-button and click "Copy" in the dialog being opened.

Getting the URL - Vimeo

To embed a video hosted on YouTube, find the video on Vimeo.com. From that page you can use one of these options:

• Copy the browser URL.
• Click the "Share" button (or icon), and then click the link on the dialog to copy the address.

Adding media content to Pure

Once you have the URL, embedding a video in either a Research Unit or Research Output is very simple. 
Just open the record you want to add the video to, paste the video link in the Web address (URL) field, add an (optional) description, select 'Portals multimedia' from the dropdown menu, and click Save.

The content should then publish to the Portal within a few seconds.

Note on URL shorteners

Shortened URLs are not supported by the embedded media feature on the Pure Portal. If you need to include a video where the URL has been shortened, please access the link in your browser, and then use the Share functionality on the video platform site to get the full-length link.

 

 

Due to the impending discontinuation of support for Adobe's Flash Player, the Flash-powered Graph of Relations feature on all remaining Custom Portals has been updated to instead use a combination of HTML5 and Javascript. The functionality remains unchanged. There are no other Portal elements still using Flash Player.

In order to comply with local regulations, we have  added two new sets of fields to Pure for our clients hosted in Mainland China to add their governmental website registration numbers (Commercial ICP number and ICP Beian License).

8. Reporting module 

Pure 5.19.0 comes with a brand new feature: reporting on the hierarchy of an organisation. This means that you are now able to report not only on a single organisational unit, but also on the organisational hierarchy above or below.

You now can:

• do a roll-up of information in a hierarchy
• drill down into a hierarchy
• summarise on each level of a hierarchy

Similarly, when filtering, you can now choose to filter on the selected organisational unit itself, or on the entire organisational hierarchy below.

You can access this feature where you normally choose your organisational values and filters in a report.

As part of improving what can be reported on in the new Reporting Module, we have updated reporting on Journal metrics for this release. We have added the options to report on CiteScore metrics and Journal Impact Factor metrics. 

We are happy to introduce an additional preview option: the wide preview. In columns where multiple values are listed in a cell, you can now choose to see all the data in list view, and select one of three separators (double slash, comma, pipe). 

You can easily switch between the Default preview and the Wide preview (see below). The currently applied preview mode will be used when exporting data as Excel or CSV.

Click here for more details...

In 5.19, wide preview is possible for up to 100 items. Cells with more than 100 records can only be viewed in the default mode (parentheses). 

 

 

 

9. Country-specific features

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

10. Additional features of this release

We are excited to announce the introduction of Pendo.io to Pure. Pendo will allow us to provide additional help and gather user feedback without having to wait for a new release. With Pendo, we will be able to create new, more dynamic feature guides and tooltips to improve the product and new feature onboarding experience. We will gradually start using Pendo with the new Reporting Module, with the aim to use Pendo throughout Pure. The guides and tooltips will be used as an addition to the standard help texts in Pure.