5.14.05.14.0

1. Web accessibility

It is now easier for keyboard and screen reader users to navigate the new Reporting Module. We have updated our Drop Downs and Tap Panels to only have a single tab stop and better screen reader compatibility.

Another action towards making the Portal fully WCAG 2.1 AA compliant by February 2021, this improvement adds an underline to menu items and changes their color when you hover the mouse over them.

2. Pure Core: Administration

The new Personal User Overview is a significant improvement to how personal users access, work, explore and add content within Pure. The new overview has a cleaner, simplified style, with improvements to fonts and color selection for accessibility. It continues the design changes we've already begun in Pure. Very importantly, users will not lose access to any functionality or utility.

The new overview is tightly integrated with the personal user’s Pure and PlumX data at the research output, project and researcher level. This includes coverage of content added by the user and institution, and PlumX mentions, usage, captures, social media and citation data for each research output where available. The new overview is aimed at encouraging productive and meaningful engagement between the personal user and their content in Pure.

The new overview includes new and improved views of:

• Researcher profiles
• Research output inventories
• Project timelines
• Supervision and teaching overviews
• Assessment snapshots
• Collaboration maps

The new personal user overview is disabled by default.

Click here for more details...

The new and improved Personal User Overview expands the capabilities of Pure to assist and encourage researchers to add and improve their content. It also presents aggregated data and metrics in an easy-to-digest format. To enable PlumX metrics on the personal user overview, please enable the PlumX integrations job, and instructions can be found further in the relevant release notes section.

Important information

• The new overview is available only to the personal user and users with viewing rights.
• It is not publicly visible and is not the Portal profile for the personal user.
• The new overview is by default OFF.

Grace period for old overview

The old overview will be retired in version 5.15.0.

Edit: October 2019

Please note, due the number of improvement suggestions to the new overview, we will not be retiring the old overview until a large portion of those improvements are implemented.

 

 

Getting started:

Personal user guide for the new overview

A guide, written from the perspective of an administrator for their personal users, can be found in a separate wiki page. The guide is designed to supplement any training material provided to personal users. A .pdf version is provided as well as image files in .png format.

 

Enabling new overview by Administrator

Personal user access to the new personal overview is granted via: Administrator > Persons > Personal overview configuration > Personal overview then toggle on or off 'Show new personal user overview page'.

Note: Configuration settings between staging and production are not carried over. After testing the feature in staging, please be aware that any changes made when either enabling or disabling the new personal user overview will not be carried over to production.

Welcome message

Users landing on the new overview page for the first time are greeted by a welcome message along with simple instructions on how to get started. This welcome message will only be shown once to the user.

Administrators can add links to their institution’s own guide or help documents via: Administrator > Persons > Personal overview configuration > New personal overview page welcome message link then toggle on 'Add information link to the welcome message'. The screenshot below shows the relevant section.

Layout of new personal user overview
The new overview is differentiated by the following sections, highlighted in the image: Researcher profile information Overview toggle PlumX researcher-level metrics Content inventory Projects overview Add new content Tasks and notifications Assessment overview Teaching and supervision overview Research relation and collaboration overview Each of the sections of the new overview are described in detail below.
Researcher profile information
A personal user’s primary information is presented in this section. This includes access (where granted by administrators) to: (1) Public profile (Pure Portal Profile or custom equivalent) (2) CVs created, and option to create a CV (3) FAAR report, downloadable in .docx or .pdf format (4) ORCID ID and option to authenticate their ID (5) Researchers, where allowed, can edit their profile. Access rights to edit profile can be set via: Administrator > Persons > Personal overview configuration > Edit profile then toggle on or off 'Show edit profile button'. For custom profile links: Edit profile then toggle on or off 'Show custom edit profile link' and add link text and URL.
Overview toggle
In both the new and old overview, users can toggle between the two styles of overview page. The toggle is only shown if access to view the new overview is granted by administrators. Access rights can be granted via: Administrator > Persons > Personal overview configuration > Personal overview then toggle on or off 'Show new personal user overview page'.
PlumX researcher level metrics
This section shows summaries for all research outputs that have associated PlumX metrics. If there are changes in the metrics between this time and the time the user previously logged into Pure, the changes will be shown above the total for each metric. For more information on each of the PlumX metrics, the user can click on the (1) PlumX link which will direct them to https://plumanalytics.com/learn/about-metrics/. In the screenshot, for the (2) 127 research outputs with associated PlumX metrics (out of a total of (3) 167 for the researcher), since the last login, the usage metric total has increased by 21 to a new total of 102. There have also been 7 new citations to one or more of the 127 research outputs, with a new total count of citations of 66. The user can isolate the research output with associated PlumX metrics or their total research output corpus by clicking on the count links (2 & 3). Important note: PlumX metrics must be enabled first. Instructions on how to do so can be found further in the release notes here. Metrics from Plum are currently limited to what is indexed in Plum. As more content is indexed by Plum, coverage will increase. Updates to most metrics are processed by Plum on a weekly basis. Thus if users log in more than once in a week, changes will not be shown until they log in the following week. For more information on indexing and coverage, see: https://plumanalytics.com/learn/about-metrics/citation-metrics/
New PlumX filter in editor: There is also a new filter for research output with PlumX metrics in the overview editor as shown here.
Metrics in research output editor: Users can also examine metric counts per research output in the Research output editor window > Metrics tab as shown in the screenshot.
Content inventory
The content inventory is a summary of all content a user has in their Pure. Content types are ordered by the count of each sub-type. When clicked, each type and sub-type will be opened in content list view with the appropriate filter activated.
Project overview
The project overview is a visual summary that allows you to explore projects and associated outputs. Users can quickly determine if the projects and their associated content are complete and correct. The project overview displays output related to a project within its timeline (3) for easier estimations of output volume and publication year. Users can select the (1) time range they would like to view, (2) click though to specific project overviews (more details on the Individual project overview screens can be found below), with PlumX metrics shown for the project and individual research outputs. Projects are sorted by their start date, with the earliest projects at the top. Projects that have no end dates are shown with an ellipsis ( … ), and (4) projects with no start or end date only display the project title. Project-related metrics such as count of ongoing projects, and applications and awards counts and amounts are shown in the project inventory (5). Clicking on any of the metrics will open the appropriate editor window. A scroll bar will appear within the project timeline window when there are 7 or more projects. Note: Only customers on the Unified Project Model (UPM) will have access to the new project overview. If an institution is on the old project model, users will still be able to access their project data, but it will not be visualised in the project timeline. To convert to the new UPM, free of charge, please contact the Pure Support team.
Individual project overview When a user clicks on an individual project in the project overview, more information about this project is shown in a dialog box containing: (1) the title of the project,    (2) the period the project is active,    (3) an option to edit the project via the project editor    (4) the PlumX metric(s) associated with the research output of the project    (5) the project timeline including a time range selection option, and the individual research outputs related to the project, oriented by publication date on the timeline, and distinguished by type icon. The individual outputs are grouped if they have very close publication dates, with counts displayed below the icon if there are more than one output. Outputs with updated PlumX data are shown with (6) an orange ring icon on the timeline and a circular orange badge on the icon. Users may click on the icon to bring up the list of research output(s). The (7) title link opens the research output editor window. If available, the (8) associated PlumX metrics are shown below the output. A circular orange badge indicates an updated metric, and the 'See details’ link leads to view Plum’s summary page for that specific research output.
Adding new content
The Add new content button will open the standard window to use a template to create new content types.
Tasks and notifications
Tasks and notifications have undergone slight design changes, but overall functionality remains the same. Users are still notified of potential research output matches, workflow push requests, and general notifications. Userscan click on links within tasks and notifications to access the appropriate content.
Assessment overview
For UK customers, a REF-specific overview is available for personal users. Users are provided with an overview of their ranked research output selected for submission and may (when allowed) (1) propose new research outputs or modify existing selections. The list includes outputs proposed by either the personal user (and/or on behalf of the personal user) and/or co-authors.
Teaching and supervision overview
Personal users are provided with a summary of their (1) current and former students, with information such as (2) student name, (3) project title, (4) the user’s percentage share of supervision, and the (5) supervision period. Output, submissions and courses related to teaching and supervision are presented in the (6) inventory at the bottom of the section and the user may click through to the appropriate overview via the links in the inventory.
Research relation and collaboration overview
The new overview features an improved research relation and collaboration network map. Users can (1) switch between showing all content relations in their network or their co-authorships, (2) set themselves as the focus point within the network, (3) arrange the network map for optimal viewing and zoom in or out of the network. If an entity has been selected in the network, it is shown (4) at the top of the network, with the option to (5) set the entity as focus point or (6) examine the details of the entity via the appropriate editor window. To optimize render performance of the network map, a maximum of (7) 50 top linked relations (and 100 top collaborations) are shown. Users may show more content using the link , but this may have a detrimental effect on performance. Relation types can be filtered using the (8) drop down filter tool bar. The map will be re-rendered if new relation types are removed or added. The network inventory highlights the (9) top collaborating individuals with the personal user, and (10) the most frequent affiliations listed in the research outputs. When clicking on either metric, the user is presented with the overview editor of all their publications related to those collaborators or institutions. Important note: The circular diagram option has been removed in this update.

 

 

As of Pure 5.14 the Handle.net plug-in for Pure will work with the new Web Service API, instead of the old legacy Web Service API.   
In order to retain the Handle.net functionality, you need to update the Handle.net plug-in and your Handle.net configuration.

In addition, administrators can now manually add handles to content (research output, student thesis, and student projects) in the editor, if the handle.net integration has been enabled (System settings > HANDLE.NET).

We have updated the Research Output Import Wizard with a new feature which allows you to overwrite the content in Pure with updates from the Import file.   
Previously, manual changes could not be overwritten by the Import Wizard.

Property logic and behavior rules for the 'Available updates from online sources' job have been updated and refined, to enable users to be more selective of data received from different online import sources and to changes made to metadata fields.

Click here for more details...

Administrator users can now define rules that determine how Pure automatically handles updates to the metadata fields of a research output.

If the 'Available updates from online sources' job is enabled, and no rules are set, by default any available updates are highlighted in the Research output editor window > Available updates tab, and the user must manually select/merge the preferred option(s) and save any changes.

Please note:

General logic: Rules follow an 'if-this-then-that' logic - a user selects a metadata field, an action to perform on this field, and the import source(s) the action must take into account.

Where in configuration: Rules can be set in Administrator > Research outputs > Import and Available Updates configuration > Property logic and behavior rules for 'Available updates from online source' section.

Import sources: The import sources that are available for the rules to function are determined by what is enabled in the 'Available updates from online sources' section (available via the same path as above).

Instructions for use:

Adding a new rule:
1. To add a new rule, click 'Add new rule'.
2. Select a field to be acted on in the 'Metadata field' drop down menu.
3. Choose either: 'All current and future sources' - updated data from all current and future import sources will be considered. 'Only apply for specific source(s)' - specify exact source(s) to apply this rule for.
4. Select an action: Automatically accept when blank – If the metadata field is empty, then the new value is automatically applied. The user does not see options to manually select/merge values. Automatically accept and overwrite – The current metadata field value is overwritten with the new value. The user does not see options to manually select/merge values. Ignore if only property – If no other metadata field has changed on this research output, the change is not applied and user is not prompted to review the new value for this field until other fields also require review. Ignore always – No updates are applied to this metadata field. Pre-configured rules: To avoid overwhelming users with initially high counts of potential candidates, two rules have been created by default - keywords and URLs are set to 'ignore if only property' from 'any source'.

Editing or removing a current rule
A rule can be edited by clicking on the 'Edit' button next to each rule.	When a user is modifying a current rule, the rule in question is highlighted in the list, and only the Source(s) and Desired action options are allowed to be changed.
A rule can be removed by clicking on the '-' button next to each rule.

Filtering research outputs affected by Available Updates from Online Sources job

Filters	Screenshots
Users can filter research outputs that have available updates by import source, and by metadata field. Using these filters, users can pre-select and inspect records before processing them either manually or via rules. Users can select one or more source or metadata field. Important note: After enabling the job, it may take up to a week for all data to be scanned and potential updates identified.

Important notes:

Conflicts between rules

Care should be taken when using these rules to avoid creating conflicts between multiple actions and sources. If a new rule conflicts with other rule(s), one or more of the following conflict messages will be displayed, and the suggested courses of action are explained below.

 

Conflict error message	Suggested course of action
Required fields are missing.	Fill all fields to create a rule.
Rule is configured for both all and specific sources.	Only select 'All current and future sources' or specific source(s)
Automatically accept actions can only be set for one specific source.	Use Automatically accept actions for only one source in case there are different data between sources
An action is already configured for '{field}' for this source: {source}.	Check current rules and modify if necessary so that only one action per metadata field and source combination exists.
An action is already configured for '{field}' for the sources: {source}.	Check current rules and modify if necessary so that only one action per metadata field and source combination exists.
A rule is already configured for '{field}' using an Automatically accept action. A metadata field can only be configured to Automatically accept for one source.	Check current rules and modify if necessary so that only one source is used for an Automatically accept action.
A rule is already configured for '{field}' using the same action but a different range of sources. A metadata field can only be configured to use either all sources or specific source(s).	Check current rules and modify if necessary so that only one action per metadata field and source combination exists.

Import sources and rules

Disabling sources

If a source is disabled in the section 'Available updates from online sources', an warning message will is shown indicating which rules will be affected by disabling the source. A user may save this configuration if they wish but the source will be shown as disabled in any rules affected.

 

Disabling sources
When a source is disabled and this affects a rule, a warning message is shown, specifying which rules it affects.	All sources enabled: Source disabled, with effect on rule(s):
If the settings are saved, a 'disabled' tag will appear in the rule(s) next to the source(s) affected. The rule will no longer function as intended as the source will be excluded from the logic of the rule. Note: If a source has been disabled but a rule uses the 'any source' option, no error or 'disabled' message will be shown.

Rule processing delay

Once rules are added or modified and the configuration page has been saved, the rules (and actions specified in these rules) are set to work on the current data. To avoid conflicts between current rules and rules being modified and added, a user cannot add or modify rules until the current set of rules have completed their processing of the current data. A warning message will be shown (see below).

Once the processing has been completed, rules may once again be added or modified.

 

 

 

The corresponding author of a publication is a key enabler of how the publication is disseminated to a wider audience, and a signal of author contribution to a research output. The corresponding author is often likened/equivalent to the first author in that any further communications regarding the research under study passes through the corresponding author. It is a key author characteristic that Pure now supports.

Corresponding author is disabled by default.

To improve readability and rankings in author listing, it is now possible to set the default position of author collaborations in the author listings.

Pure has expanded support for pre- and post-nominal titles. It is now possible to set the title based on position relative to the person name.

We have aligned the manner in which active affiliations are added when adding a person to content. Previously, when adding person(s) to research output, only the primary affiliation, if noted, would be added. However, for all other content types, all affiliations would be added.

All content editors are now unified and when adding persons to content, all active affiliations are added unless a primary affiliation is specified, wherein only the primary is added.

With Pure 5.14.0, the Old Web Service API has been removed. For all customers who have been using the Old Web Service API to extract highlighted content from Highlighted Content CVs, there will be a temporary loss of highlighted content. Additionally, the new Web Service API will not expose highlighted content from Highlighted Content CVs but will expose highlighted content from a new unified location in the personal user profile.

Customers using the Pure Portal will now already be able to use the unified location. For customers without a Pure Portal, this unified location will only be available in 5.14.1. Therefore, if you use highlighted content from Highlighted Content CVs, please consider postponing updating your system until the release of 5.14.1.

We have added a set of awards filters that reflect the start and end dates of the award.

Click here for more details...

The new filter, Award progress, has three progress states: Not started Running Finished
The Award status filter now only displays the actual award statuses that can be found on the award: No status set (Award Management module only) Internally approved (Award Management module only) Curtailed Declined (Award Management module only)

This update is also reflected in the overview screen for the Awards Management module:

 

 

3. Pure Core: 3rd party import sources

We have extended our integration with SSRN introduced with Pure 5.11.0 - with this release imports from SSRN also include the abstract information where available on SSRN.

As part of the new Personal user overview screen we have added an import of metrics from PlumX. PlumX Metrics provide insights into the ways people interact with individual pieces of research output (articles, conference proceedings, book chapters, and many more) in the online environment. Examples include, when research is mentioned in the news or is tweeted about. Collectively known as PlumX Metrics, these metrics are divided into five categories to help make sense of the huge amounts of data involved and to enable analysis by comparing like with like.

4. Pure Core: Web services

With Pure 5.9.0 we introduced the new Web Service API and with this release the new Web Service API will replace the old Web Service API previously available.   
As a consequence, the old Web Service API is removed and is no longer available.

If you are still using the old Web Service API for any purpose, we strongly encourage you to switch to the new Web Service API.   
Please find additional information about the new Web Service API:

• in the Pure 5.9.0 Release Notes
• in the Pure Academy Masterclass
• by contacting Pure Support

The removal of the old Web Service API will affect operations of other features. These are highlighted in more detail in other sections of these release notes, specifically:

• Highlighted Content availability
• Pure Portal

We are very happy to announce that we have added a new OAI-PMH endpoint that will expose your data in CERIF XML. You can find the specification for the mapping and additional information here.

This mapping was done in collaboration with euroCRIS and Pure users. A special thanks to everybody involved, Anna, Nykhola, Patricia, Federica, Kara, Anne, Jan and Bill.

To enable CERIF XML via OAI-PMH please do so under Administrator > Web services > OAI configuration.

We added a filter to the POST call for equipment and enables filtering based on its loaning policy.

We have aligned the XML and JSON response structure. Previously, lists in the XML response were exposed as a flat list instead of being wrapped correctly.   
We have improved and aligned the format to achieve a more consistent and aligned structure between the two formats. Please click expand to view an example of before and after the change.

5. Reporting

Following the release of the technology preview of the new Reporting module in 5.9.0, and updates to this preview in subsequent releases (5.9.2, 5.9.3, 5.10.0, 5.10.1, 5.11.1, and 5.12.0) we are continuing to develop the new Reporting module in order to deliver a comprehensive, flexible, and intuitive reporting tool that continues to meet users' evolving reporting needs.

In this release, we are moving the new Reporting module out of the 'Technology Preview' phase, into Beta. With this update, the module will now only be available to Pure 5 customers with access to the reporting module. We strongly encourage users to start using the new module and provide us with feedback on your experiences via JIRA. New features in this release include:

• New content and content types
• Expand functionality
• Enhanced user support

6. Pure Portal

As part of this release we will be updating the version of Elasticsearch powering the Pure Portal search engine. This is essential due to Elasticsearch discontinuing support for our current version. In order to complete this upgrade, all Pure data must be re-indexed, which will necessitate pausing the connection between the Pure Portal and Pure. This must be done on a region-by-region basis, and the Portal will not update with new content during this time. We expect this to take roughly 24 hours.

The aforementioned upgrade to the latest Elasticsearch version has also afforded us the opportunity to tweak our 'profile similarity' algorithm. As a result of these changes you should (generally speaking) see more results per person as well as slight changes in the ordering when sorting by relevance.   

In line with earlier communication, with the release of Pure version 5.14.0, we will be completing the switch over for Pure Portals to use a newer version of our web service API. Depending on your configuration, some action may be required from your side for your Pure Portal to continue to update. Most affected clients should also have been notified by email. The information presented here is the same.

We are very pleased to announce the addition of download statistics to the Pure Portal. Download counts of files attached to research outputs will now be displayed on the research output pages and in search results.

We've added a degree of control over our search algorithm. You now have two options for the default protocol used for Portal searches.

In response to client feedback, we have added a configuration option for our Collaboration Map on Pure Portals, so they can be disabled for any particular person's profile.

With 5.14 we have made it possible to use a Portal "Sort name" within Pure Portals. This allows users to specify a different name to use when displaying alphabetically sorted lists of researchers. This is useful if, for instance, the Last Name includes a prefix. So for the name "Ludwig van Beethoven", even though the Last Name is set as "van Beethoven", it can be sorted by "B", not "V". This functionality was previously only available in custom Portals.

During this release we have fixed a bug pertaining to our "Willingness to talk to media" option. In some cases, this bug caused made the option to signal willingness to talk to media available to personal users even if the feature was disabled on an admin level.

It's now possible to configure on Pure Portal Dataset pages whether the suggested citation includes all contributors to the dataset, or only those with the role 'Creator'.

7. Country-specific features

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

• Introduction of 'Submission approach' property on the Unit of Assessment.
• Complete re-design of the REF2 Research Output framework to align with the updated REF2021 submission requirements and the partial de-coupling of outputs from staff. This is a significant change in the REF module, with wide-ranging implications.

With this release you can now capture Datasets in the SEP D3b: Main categories of research output and KUOZ C: Research output tables.

Further information is available in the SEP wiki.

8. Additional features of this release

Previously, actions and activity by cron jobs in audit logs were shown with generic names. The 5.14 release marks a transition to naming jobs in the audit log using the title of the job and the user name. This improves the ability for administrators to identify changes made by specific jobs. This is a continuous process, and we expect this transition to occur over the next year.

Following a review of the text that corresponds to country codes in Pure, several corrections were made, as listed below. These codes in Pure correspond with the https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 list of country codes.

Due to underlying infrastructure changes within Pure, markup is no longer possible in pinned system messages.

The mods format has been improved to expose additional information for events on content. This can potentially effect custom stylesheets (xslt).