How Can We Help?
5.5.25.5.2
We are pleased to announce that version 5.5.2 (4.24.) of Pure is now released.
Always read through the release notes before installing or upgrading to a new version of Pure.
Pay attention to the Upgrade Notes - failing to adhere to these may result in loss of functionality.
Released date: 1st of April 2016
Installation and downloading
See the Request Pure distribution file page for information about how to request a new version of Pure.
Other Resources and Links
If you have problems with this release please contact Pure Support to get help.
Pure hosting requirements
See the Pure Requirements page for more information
Administration module
1. Open Access improvements and unification
The 5.4.1 / 4.23.1 Release notes had indicated that the logic for the Open Access Status had been updated to fully capture the implications of the record Visibility (i.e. Public / Campus / Backend / Confidential), and whether a DOI or Link electronic version has been added (as the OA Status of outputs accessible via external DOIs or Links is not impacted by the visibility of the Pure record). Unfortunately, this was not the case; this issue has now been resolved in this release.
The description of the logic behind deriving the Open Access status of the record is available here
CV module
2. Weill Cornell Medical College (WCMC) CV Template
We have delivered the following bug fixes:
- Section B : (1) Academic degree(s) : Ensure ‘Professional qualifications’ are not available for selection in this section
- Section I : Extramural Professional Responsibilities : Ensure that only those Activity types specified in the mapping are available for selection, and add ‘Conference participation’ to those available for selection in the ‘Invited Presentations’ sub-section
- Download the CV to Letter (8.5” x 11”)
We will endeavour to deliver additional changes and mapping improvements for the 5.6 release in June.
Country-specific functionality
3. UK : REF2020 Module
With regards to REF OA Compliance monitoring, we have fixed the issue that was resulting in Access dates not being populated for some uploaded electronic versions. Upon upgrade, you must run the 'Generate OA compliance status' job, and this will resolve the issue of missing 'Earliest access date' (and resulting erroneous REF OA Compliance status) for affected records.
Note that there are still some known issues relating to how DOIs are incorporated into the REF OA Compliance status. We hope to have these issues resolved in an upcoming 5.5. bug-fix release. Further details are available at Open Access compliance - Notes and issues CLOSED.
Updated at July 27, 2024