5.8.05.8.0

Before	5.8 improvement

It is also possible for Administrators to edit the order that content types appear in the content type header. By default, the order is as follows:

• Persons (Profiles)
• Organizational units (Research Units)
• Research Outputs
• Equipment
• Projects
• Datasets
• Prizes
• Activities
• Courses
• Press / Media
• Impacts
• Student Theses

To edit the order of content types in the Portal:

• go to Administrator > Portal > Configuration
• scroll down to 'Families'
• to change the order in which content types are displayed in the content type header, use the up or down arrow next to the desired content type to change where it resides
• to add or remove a content type, please contact Pure Support via Client community

Student Theses will be displayed for both profiled Persons who have authored a Student Thesis, as well as Student Theses that are supervised by profiled Persons in the Portal. This content is not displayed by default.

Notes:

• Student Theses is an independent content type - Research Outputs of type 'Thesis' will continue to be listed in the Portal as Research Outputs
• Student Theses are disabled by default

The purpose of this feature is to enable Portal visitors to request a copy of a full text document (e.g. Author's Accepted Manuscript) when the document cannot be made available for download via the Portal due to embargo restrictions.

Once the Request for Copy functionality is enabled, all Research Outputs with status embargoed will have a Request for Copy e-mail link available. When the embargo passes, the Portal page will automatically update to make the file available directly in the Portal.

From 5.8, the Pure Portal now displays titles from the Person record. Where multiple titles have been input, they will appear in the Portal in the order they appear in the Person editor.

When importing content from WoS, multiple organisations in the address tag would result in a single organisation with all the organisation names concatenated into one string (e.g. "Fac Chem, Dept Biochem, Univ Belgrade, University of Belgrade"):

This has been improved such that Pure interprets these as multiple organisation affiliations rather than one, indirectly improving name matching during the import process.

• Fac Chem
• Dept Biochem
• Univ Belgrade
• University of Belgrade

Roles affected: Editors of Research output, Validator of Research output, Administrators, Technical administrators

This early access to the new Web service is intended to provide you with:

• a better understanding of how the Web service will work from 5.9.0
• a look at the updated user interface
• a preview of the Web service content access control, which is set in the Pure backend

As we are providing early access to the new Web services prior to completion of the update, you should note that changes may occur prior to the full release in 5.9. It is not intended that Web service users will start programming using this early access version as a firm foundation.

We welcome any feedback you may have; please contact the Pure support pure-support@atira.dk

The early access is limited to include 2 endpoints:

• Organisational units
• Persons (limited to listing all Persons and details for a specific Person)

You can preview the new GUI designed for the Web Service. This new graphical interface is designed using Swagger.io and allows the developer to get an easy overview of the endpoints, the filters available, as well as the possible parameters that apply for every endpoint. An example is that it is possible to switch between the new XML and JSON output formats. Additionally, this graphical interface provides both "Request URL" and "Curl" when making a query.

In order to view the new graphical interface you need to go to this link https://your-path/ws/api/59-ea/apidoc/index.html

A key addition to this early access is the user access control that determines which endpoints a given Web service user is able to use. The setup of the access control is performed in the backend of Pure using API keys. An API key can be generated and setup to show all (admin), or one or more content types (check box), and it can also be temporarily disabled. Additionally, an API key can tagged with an expiration date.

Each API key has a description field allowing the Pure administrator full overview of the Web service users. Before the Web service can be used, the API key needs to be entered in the GUI shown above. This is done be clicking the green "Authorize" button.

Go to Administrator > Security > Api keys in order to create the API keys for web service. Click on the button "+ Add new API key".

A new window will appear, in which the new API key is auto-generated, and where it is possible to set the individual rights for a given API key. For each API key a description can be added, along with the selection of which content end points should be visible. An API key can be temporarily locked if necessary or an end date can be set. Finally it is possible to create an API key with administrative rights which will have access to all end points.

Publication channel identification

The BFI-system has reverted the means of identifying publication channels (Journals, Publishers and Conference proceedings) to use BFI-number for identification, whereby Pure is not forced to have a version of the publication channel for each year it has appeared on a BFI authority list. In addition to changing the approach for identification, all duplicate BFI-publication channels will be merged upon an upgrade to 5.8.

Upon upgrade, there should only be one version of a publication channel independent of which years it has appeared on a BFI authority list.

Publication channel merge

The BFI-system has added a new feature whereby they can merge duplicate publication channels in the BFI-system. Consequently, the synchronisation of BFI publication channels in Pure will automatically update and merge Journals in Pure in accordance with a merge of publication channels conducted in the BFI-system. Pure will therefore reflect merging conducted in the BFI-system.

Merging of publication channels uses the regular merge functionality in Pure. This means that for Journals, any related content will maintain Journal title and ISSN since existing Journal title and ISSNs will be added as Title or ISSN variants. For Publishers and Conference series, the Publisher or Conference series name will be changed on all related content.

BFI-level on BFI-publications

From 5.8 BFI-level will be synchronised to the publication in Pure when the level is available in the BFI-system. Hereby, each publication from current or last year will automatically have level added when new information is synchronised with Pure from the BFI-system. If BFI level is needed for publications from previous BFI-years you will have to run the job 'BFI Legacy Points Import Job (2013 ->)' which will re-import BFI-point for publications from the specified year. The setting 'Force run' should be enabled to update all publications even though no changes have appeared. NOTE : BFI-data will be updated for all publications, including BFI-points per person.

Latest version of MXD

Pure has been updated to support DDF-MXD version 1.4.0, which includes the following:

• Roles for persons on publications. MXD now holds a person role of 'Other'. If roles are added to the classification scheme for roles on publications, these will all be mapped to the 'Other' role which does not qualify for BFI-points.
• The 'Other' publication type in MXD has been updated with a field for Year. Pure will add current year to this field. The benefit of this new field is that the BFI-system is now able to process publication years for all publications, and hence you should see a big change in the number of publications that in the BFI-system marks as errornous due to an invalid publication year.

The new DDF-MXD format is available here: http://mx.forskningsdatabasen.dk/mxd/1.4.0/

To enter the setup page go to Administrator > Publications > Edit (next to Bibliotek.dk).

The following page will then appear. Check the "Enabled" box to activate the source and then press "Save"

When making a search from bibliotek.dk the window now looks like this:

We have expanded the number of bulk actions available for REF1a/c content to include:

• Eligibility status
• Submission status
• UoA assignment
• Workflow (already available)
• Delete content (already available)

Roles affected: Administrator

Notes:

• As there is a relationship between Eligibility and Submission statuses, there is some logic in place that impacts on the bulk actions:
  • If a group of REF1a/c records that are currently flagged as Not Eligible are selected to be bulk moved to Submission status = Yes OR Pending, this will not be actioned (because, if a REF1a/c is flagged as Not eligible, it cannot be submitted, therefore it will always have the Submission status = No)
  • If a group of REF1a/c records are bulk moved to Eligibility status = No, the REF1a/c records will automatically also be moved to Submission status = No

When the function to enable affiliating PhD Theses to the Promoter(s)' Organisational Unit(s), rather than that of the PhD Candidate, was delivered in the 5.6.0 release, this significantly complicated the ability to report SEP content by organisation, such that we were unable to enable the function to filter by ‘selected and all underlying organisations’. This was resolved in the 5.7.3 (4.26.3) release and is now available both in the SEP Outputs table, and in the SEP Staff tables. 

The JUFO metric is now available for Journals and Publishers:

• For Journals, the metric will be matched based on ISSN and subsequently added
• For Publishers, all Publishers available from the source are added in Pure with the corresponding metrics. If there is a 100% name match between a Publisher from the source and Pure, then only the metric is added and the Publisher is not created. Since it is the name alone that is being used for matching, then there is a possibility for Publisher duplicates after the job has run

The feature will be available as a cron job and set to OFF as default. In order to switch it to ON go to Administrator > Jobs and locate the job called "Import metrics from julkaisufoorumi (JUFO)"

Set the desired schedule (it is recommended to run the job once per month) by clicking the "Change schedule" button. Click the "Update" button. and then the "Start Job now" to run the job.

The job will then run as described. Below is an example of a publisher with JUFO metrics added.

For journals the added metrics are displayed as shown below:

Configuration for Pure Portal URLs to ORCID

The existing configuration for sending Pure Portal URLs to ORCID has been updated such that when disabled, not only will individuals' Pure Portal profile URLs be removed from ORCID, but also the Pure Portal output URLs. When enabled, the individuals' and outputs' Pure Portal URLs will be visible as hyperlinks in the individuals' ORCID page, thereby giving ORCID readers the opportunity to navigate to the Pure Portal for further information on the researcher and the output. This configuration should be disabled if a Pure Portal (whether a Custom Portal or the Pure Portal) is not available from the internet.

Student affiliations

The ORCID integration has been updated to more accurately capture Student affiliations. Where a Person in Pure only has a Student affiliation(s), Pure now sends basic affiliation information across into the Education section, rather than the Employment section. Where a Person in Pure has both staff and student affiliations, no change has been made to the integration; the affiliations will continue to be captured as Employment in ORCID.

Externally authored publications

The export to ORCID now includes all publications on a Person's record, including those wholly externally authored. Notes: where workflow is disabled on external publications, Pure will export all external publications to ORCID, regardless of the 'Effective workflow step' configuration in the Export to ORCID configuration screen      where workflow is enabled on external publications, Pure will follow the same 'Effective workflow step' as internal publications

Pure ORCID documentation has been updated to reflect these updates:

• ORCID : Admin Configuration 
• ORCID : Functionality for Administrators and Editors 
• ORCID : Functionality for Personal Users 

Roles affected: Administrator and Personal user

The Metrics tab on Research Outputs now contains the number of downloads per year, where available. Details are as follows:

• the number of downloads includes downloads of Electronic version files from outside Pure's backend (e.g. from a Pure Portal)
• the number of downloads are filtered to generally omit downloads from robots as well as double downloads from one user (within 10 seconds)
• this option is by default enabled, but can be disabled in the 'Filter download information' job

Roles affected: Personal users, Editors of Research output, Validator of Research output, Administrators, Technical administrators

As the matching of Pure Research Outputs with Scopus publications is done algorithmically (via the 'Match Scopus IDs for Publications' job), in very few cases an incorrect Scopus ID can be assigned to a Research Output in Pure. If the Scopus ID is manually removed from the Output in Pure, it will simply be re-added the next time the job is run.

To avoid this scenario, it is now possible to configure the job to exclude such Research Outputs and make no further matching attempts. In the job configuration, there is a new field for 'Excluded publications' where Outputs can be added using a search field. If it is subsequently needed to remove an Output from the excluded list, it can be removed individually or it is possible to clear the list in full.

Note that the job does not remove Scopus IDs from the Research Output records of excluded Outputs; it simply un-syncs the content with Scopus. As such, following the addition of an Output to the excluded list, the Administrator should manually remove the incorrectly matched Scopus ID.

Roles affected: Administrators, Technical administrators