How Can We Help?
5.31.0 5.31.0
We are pleased to announce that version 5.31.0 (4.50.0) of Pure is now released
Always read through the details of the release - including the Upgrade Notes - before installing or upgrading to a new version of Pure.
Release date: 4th October, 2024
Hosted customers:
- Staging environments (including hosted Pure Portal) will be updated 9th of October (APAC + Europe) and 10th of October (North / South America)
- Production environments (including hosted Pure Portal) will be updated 23rd of October (APAC + Europe) and 24th of October (North / South America)
Advance notice - Discontinuation of Dspace versions 4-6
We previously announced that we would be discontinuing support for older versions of Dspace (v4-v6) from version 5.31.
We have postponed this discontinuation until version 5.32.0. Therefore, Dspace v4-v6 will still be supported until February 2025.
New backup schedule
We're updating the schedule and availability of backups; this change means that we will have more frequent backups available for the most recent week at any given time, while having fewer backups in storage beyond the age of one week. The new backup schedule will go into effect from 4th November 2024.
For more information, please consult our backup schedule change note.
Reminder: Upcoming deprecations previously announced
-
Potential all clients:
- DB sync will be retired in June 2026 (5.36.0). We will continue to fully support sync into Pure through XML and the API. (Ref1)
-
On-premises installations only:
- Only supporting PostgreSQL as the underlying Pure database from THIS release. See On-premises installation upgrade notes.
- Last on-premises feature release of Pure, February 2026 (5.35). (Ref1)
-
Sunsetting of Classic reporting
- The classic reporting module is scheduled to be sunset in June 2025, see Sunsetting classic reporting for more information.
- The classic reporting module is scheduled to be sunset in June 2025, see Sunsetting classic reporting for more information.
5.31.0 New and noteworthy
Core
New standard header
The new and improved header is now the standard header. The standard header provides improved efficiency, accessibility, and user experience. It offers the following benefits:
- WCAG 2.1 AA compliance.
- Modern, intuitive layout.
- Streamlined access to all global actions through enhanced navigation.
- Improved orientation through distinctly organized tasks, notifications, and system messages.
New standard header in 5.31.0
The new standard header is now the default in 5.31.0 and it is not possible to switch back to the old header.
For more information on the new standard header:
- Early access introduction of new header in 5.29.2 release notes
- New header updates in 5.30.0 release notes
Classification maximum size default value
After feedback from customers and analysis of average classification sizes, we have updated the default classification size value to 8000.
For (very) large classifications we now allow:
- Creation of new classification schemes with less than, or equal to, 8000 values (old maximum value was 500) in the classification scheme
OR
- If the classification scheme already exceeds 8000 values, then we only allow modifications which do not increase the number of values
5.29.0 release notes where a maximum classification size was first implemented
Reporting
Updates for sharing of snapshots
With this latest release, you now have the ability to share snapshots with any user within the Pure platform. This significant enhancement maximizes the impact and utility of the reporting module, allowing for broader dissemination and collaboration on key insights. Furthermore, you can share snapshots with yourself, providing a convenient way to keep track of your own reports and analyses. This new feature ensures that everyone, including you, can easily access and benefit from the valuable data and insights generated within Pure.
Since it is now possible to share data snapshots with all users in Pure, we have removed the live data option and the go to workspace button, for all recipients except the owner of the workspace. This is to ensure that the data snapshot is indeed a snapshot as seen by the creator of the workspace and not the recipient.
The share workspace option is available for when you want to offer a live data refresh to the recipients. As this is being shared with users that have a reporting role, you also don't have to worry about setting up filters for organizations, etc., as the data will be loaded with the recipients' roles and rights.
REF
Contributions to knowledge and understanding (REF2)
In 5.30.3 we released an initial REF2 model. With this model it is now possible to start creating the REF2s. The initial model contains the following fields:
- Research output relation
- Total numbers of authors override
- Unit of Assessment
- Output type (this uses the same mapping from REF2021)
- Narrative statement
Volume contributing staff
To start gathering an overview of the volume needed for REF, we have added an FTE of volume contribution staff to the Unit of assessment. This is a manually inputted field and no automatic calculation of needed content has been added. The field is available in reporting. It is possible to bulk upload FTE of volume contributing staff using a spreadsheet.
Pure Award Management
Contract Management
We have introduced a new control within the Contracts configuration in administration->award management. This feature enables institutions to determine whether participants listed on contracts are permitted to modify or delete those contracts.
Review content type
New role for Ethical Reviews
We have now added a new user role for review editors on Ethical Reviews (called Review Editor of Ethical Reviews). This role follows on from the introduction of role-based review editors, previously described in https://helpcenter.pure.elsevier.com/en_US/release-notes-pure-5280-4470#343-the-role-editor-of-reviews-is-now-based-on-content-type-17.
List view filters
We have fixed an issue relating to the filters on the review content type. In doing so, we have renamed the filter ‘persons’ to ‘reviewers’
Clickable links on reviews
In 5.31 we have made the items under review available as a link for the reviewer so they are able to open the item being reviewed (subject to reviewer permissions to access the linked item).
Clicking on the link will now open a pop-up option as follows;
No-cost extensions on awards
In this version we have introduced a new configuration in the award management settings to configure the use of the new ‘no-cost’ extension option on awards.
Pure API: Student Thesis support
Full endpoints to support the existing content type ‘Student Thesis’ have been added to the API.
NOTE: This is the common Student Thesis model available to all clients, if the module is enabled.
The Student Thesis endpoints support the same design principles as other content-related endpoints.
For further documentation of the Pure API, refer to the official guides or your local version, available at <your server url>/ws/api/documentation/index.html or the interactive <your server url>/ws/api/rapidoc.html.
To get an overview of remaining content types, refer to Pure API roadmap and remember to vote on the linked idea exchange tickets to help us prioritize the upcoming endpoints.
Known issues fixed in this release
KI-# |
Title |
---|---|
Error "413 request entity too large" occurring when trying to upload files in Pure |
Updated at October 14, 2024