5.23.05.23.0

This release brings extensive updates to the design and functionality of the Data Quality interface. The major updates and improvements include filtering groups by organization type, as well as source IDs and matching rationale now provided for each entity. You can find detailed instructions on how to use the Data Quality interface in the 5.22.0 release notes.

You can now narrow down the list of duplicate groups by applying the external organization type filter.

Synchronization source name and IDs are now shown when hovering over the sync symbol in the entity list.

The candidate-to-target match score rationale has been updated to provide more context to the match score. Details are provided for the name (including alternative names), address and and associated IDs. Users can click on the match score to view the per field rationale.

This functionality was introduced in a minor release (5.22.2).

Clients who use the login screen as an alternative or supplement to single sign-on, can now allow users to reset their password if they have forgotten it. Previously, only a logged-in user could request a password reset for another user from within Pure. The same option can now be made available to unauthenticated users on the login screen.

Note: If you are using a single sign-on system to authenticate your users against your Pure instance, it is not recommended to enable this feature, as it does not support externally authenticated users.

Click here for more details…

Information	Screenshot
Enabling password policy To enable this feature, you first need to enable password policy for your Pure instance in Administrator > Security > Password policy. We recommend setting up a policy in line with your security standards. See 5.10.0 Password Policy & Password Reset to find out more about the password policy feature.
Enabling password reset ('Forgot password?')  Once the password policy is enabled, you will see the option to enable the 'Forgot password' feature at the bottom of the 'Policy enforcement' section.  Enable the feature and save your settings.
Accessing the feature When the feature is enabled, the users logging into Pure via the login screen can see a Forgot Password? hyperlink.
How it works When the user selects the option, they are taken to the next screen, where they are asked to enter either their username or email. They then receive an email with further instructions. This email and following flow is the same as the original feature described in 5.10.0 Password Policy & Password Reset.

 

 

As part of the 5.22.0 release, we implemented deduplication as a feature on many more content types (see 5.22.0 release notes section: Deduplication available on more content types).

Following a period of customer testing, we are now pleased to also make this extended deduplication feature available as scheduled cron jobs per content type.

This feature was originally defined to support the needs of our Pure Community Customers and is a powerful means to:

• process and merge content without a need for manual intervention and
• resolve duplicate issues in bulk.

The automatic deduplication process is applied based on a set of rules that identify and validate candidates prior to deduplication and merging. The rules are listed on the Automated Deduplication Job page.

2. Pure Core: Pure Web Service and Pure API 

2.1. Pure API: Upcoming breaking changes

This functionality was introduced in a minor release (5.22.2).

Pure API now supports the management of Users. CRUD operations on the User content type are now available.

Use cases catered for in the current release:

• Synchronize externally managed user data with Pure so that end-users can use existing single sign-on infrastructure to sign in to Pure. In this case, users are externally authenticated.
• Synchronize externally managed user data with Pure so that end-users can sign in to Pure without requiring single sign-on infrastructure. In this case, users are authenticated by Pure.

Note: It is possible to combine the User and Person endpoints to grant Persons the personal user role.

Assigned roles cannot be managed yet, but we are planning to make that possible in the upcoming release (5.24.0).             

A password reset feature ('Forgot password?') was also added in this release. For further details, refer to Password reset available on login screen and Pure API: Reset user password via API.

You can get more information the API (supported fields and more) by upgrading Pure and accessing the Swagger UI available at:

Shortly, you will also be able to experiment with the user endpoint using the Pure API sandbox.

To expand on the use cases supported by the API, it is now possible to reset password for users through the API.

Note: The underlying functionality and limitations are the same as described in Forgot password available on login screen.

This functionality was introduced in a minor release (5.22.2).

Pure API now supports the management of Research outputs. CRUD operations on the Research output content type are now available.

All metadata fields on Research outputs have been introduced, except for relations to other editorial content types.

Use cases catered for in the current release:

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

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

This functionality was introduced in a minor release (5.22.2).

We have added a new generic concept to the API called disciplines. 

Disciplines is a generic concept which is available as an option on all endpoints. It can be used to retrieve additional information about different discipline schemes and content associated to these disciplines.

The API now supports the following disciplines (ANZSRC module needs to be enabled):

• Fields of Research (for)
• Socio-Economic Objectives (seo)
• Types of Activity (toa)

The intention is to add more disciplines over time and perhaps also support for managing your own disciplines. 

The External organization model was updated as part of the 5.20.0 release to include information on hierarchy and organization takeover ('Taken over by'). See 5.20.0 release notes for more details.

This information is now exposed in the Pure API for External organizations and can also be updated through the API.

3. Integrations

In order to be able to provide better filtering and search for import candidates in the future, the underlying model/framework for import candidate management has been redesigned. Previously, import candidates were stored on the file system. With this release, the data has been moved to the database to provide more flexibility and better performance.

The Data Monitor integration has been upgraded from version 2 to version 3. The new version contains new information for some datasets:

• Geolocation
• Rights
• Date of data production
• Date made available

4. Unified Project Model and Award Management

Work continues on changes needed to support our new workflow management implementation and on underlying changes required to enable Milestone implementation on award management content types (for AMM customers only). This substantial package of changes is at an advanced stage but is still mostly 'under the hood' at this point in the development cycle. We will continue to refine these together with with our award management community in the coming months ahead of our proposed launch in version 5.24. Please feel free to contact the AMM product manager (James Toon) for further information or to provide feedback into user testing.

In addition to the underlying development described above, we continue to work on system stability and to resolve defects as they arise. Please review the Resolved Issues section of the release notes for further information.

As a continuation of our work to extend and improve the use of milestones, we have made a few updates to the milestone overview screen by making a clear distinction between milestones that have been allocated a responsible user and those that are allocated based on their responsible role type alone. 

(a) The addition of a new column titled 'assigned to' that includes the name of the user given responsibility for any given milestone.  (b) The addition of a new column title 'milestone role permissions' that indicates the role that the milestone is associated with

We have also included a further two filter options into the overview, so that it is possible to narrow down the list either based on the existence of responsible users, or by individual awards. 

Option to filter on milestones that do/do not have a responsible user
Option to filter based on award title

5. Pure Portal

It is now possible to set up an integration with SFX so that an SFX link to the full text will be added to all publications with the status of 'E-pub ahead of print' or 'Published'.

The SFX link resolver is a linking service and a collection management tool. It provides a direct route to electronic full-text records through an OpenURL. The SFX link also provides further resource discovery with access to journals and much more. The SFX can be launched as an Ex Libris-hosted, or a locally hosted system. Linking capabilities can be easily embedded into any OpenURL-compliant source. This could be discovery platforms, a library portal, or Google Scholar, just to name a few.

In other words, the SFX link provides the information on the electronic availability of an item. It can be used to link directly to a full-text, to find journals, and to take advantage of other library services.

Click here for more details…

Information	Screenshot
Enabling the SFX link resolver Go to Administrator > Pure Portal > Configuration > Content types. Edit Research output configuration. Search for 'SFX link resolver' setting. Specify the base URL for SFX. Save your settings. Note: As mentioned in the help text, research outputs will be republished when a URL is first entered or updated.
Accessing the feature Users visiting the Portal will see an SFX link together with other links for the research output. This will be shown for all research outputs with the status of 'E-pub ahead of print' or 'Published'.

 

 

It is now possible to allow visitors to your Portal to export a search result to a file containing a list of UUIDs. The list is formatted in such a way that it can be used as a filter in the reporting module. See this section for further details

This feature is disabled by default.

Note: We have also added the option to disable the existing export functionality, so that now both Excel and UUID list exports can be either enabled or disabled.       

Pure and Elsevier teams continue to work on enhancing the Fingerprint engine. From June 2022, the technology behind the fingerprint is changing, making the terms used clearer and the fingerprint itself more compact and easy to use. As a result of this, we expect the existing fingerprints to change noticeably and would like to make sure that our customers are comfortable with this change.

In view of the above, we are calling on customers currently using the Fingerprint functionality to participate in the new fingerprint testing. Customers who wish to take part will be able to view the updated fingerprint for their research outputs, persons and organisations and compare it to the current one. Your feedback will be instrumental in ensuring the necessary level of quality of the updated service.

Please contact Irina Bischof (i.bischof@elsevier.com) if you would like to participate in the testing or have any questions about the forthcoming changes.

6. Reporting

7. Country-specific features