How Can We Help?
5.7.0 Upgrade Notes5.7.0 Upgrade Notes
Please follow the general Upgrading Pure documentation as well as the 5.7.0 (4.26.0) specific instructions below.
PARTICULAR ITEMS TO NOTE WITH THIS RELEASE
Duration of upgrade:
- Depending on the number of activities in your installation, migration (and hence the upgrade) will likely take longer than usual (potentially hours)
- Given the scale of the migration of content within this release, we strongly advise that Integrated customers upgrade their TEST server prior to updating Pure in their PRODUCTION environment, as well as securing a data dump prior to upgrading
Portals:
- Custom portals (i.e. Advanced portals) and Standard portals will see changes due to the changes to the data models in Pure. While we tested a significant number of Custom and Standard portals, we could not test them all. We therefore advise that you review your Portal in your TEST environment prior to upgrading Pure in PRODUCTION.
- The Pure portal (i.e. Pure Experts portal) has been updated to reflect the changes to data models included in this release, as part of our ongoing development of the Pure portal.
- Google's updated Terms of Use mean that from 5.7.0 (4.26.0), maps will no longer be displayed in the Pure Portal (i.e. Experts Portal) or Custom Portals (i.e. Advanced Portals) unless an API key has been set up as per the instructions available in the Release notes. Further, it will take time for the Pure job to run through all existing geolocations and re-plot them, therefore there will be a delay before all map markers are available again in Portals.
Web services:
- This release includes changes to web services for Activities, Press / Media, and Prizes. Further details are available from the Release notes.
File Storage configurations relating to workflow updates
Due to the changes made in 5.6 to workflow functionality (see the 5.6.0 release notes), the storage setup in Pure is now more simple and easier to understand. The changes to the workflow configuration in the Storage settings mean that when you select a workflow step, all later workflow steps are also included automatically. For example, if in the future you change the workflow configuration for research outputs from a 3-step to a 4-step, content in the last step is automatically included in the content that is being sent, without needing to return to the Storage configuration.
If you have setup internal or external file storage (DSpace, Eprints, Fedora, Equella etc.), you need to check that the configuration adheres to the new rules described below before applying the upgrade, otherwise storage will be disabled, and the following error is logged:
Permanent store '<store name>' has been DISABLED. Contact support@atira.dk for more information
|
The settings are located under “Administrator” > “Storage”, and it applies for both “Internal File Storage” and “External File Storage” sub-menus. Here you can setup conditions for the storage; if you have set up a workflow condition, you need to check the following:
| OLD configuration option | NEW configuration option |
|---|---|
|
If you had selected e.g. 'For validation', then you also had to select all subsequent workflow steps
|
Therefore, we have updated this functionality such that you now only select which step is the first you want to include, and then all subsequent steps are also included
This change has been implemented to ensure that if you change the workflow configuration from a 3-step to a 4-step, content in the last step is included among the content that is being sent. |
|
If your configuration is set up like the following, then e.g. 'Validated' is not included in the content being transferred.
|
Previously announced changes that affect Pure 5.7
Oracle 11g will not be supported as the Pure database from version 5.7 and forward:
From version 5.7/4.26, Pure will no longer support Oracle 11g for the Pure database.
SQL Server 2005 will not be supported as the Pure database from version 5.7 and forward:
From version 5.7/4.26, Pure will no longer support SQL Server 2005 for the Pure database.
IE 9 and IE 10 will not be supported from version 5.6 and forward:
Since Pure 5.6.0 (released June 2016), Pure no longer supports Internet Explorer 9 and Internet Explorer 10. This does NOT mean that Pure no longer works in IE 9 or IE 10, but we no longer test against these browsers, and we will not fix bugs specifically related to these two browsers. If you are using Internet Explorer, you should therefore upgrade your browser to the latest version of Internet Explorer in order to get the best experience with Pure.
We are following the line from Microsoft whom ended this support on January 12 (see e.g., https://www.microsoft.com/en-us/WindowsForBusiness/End-of-IE-support)
Deprecation / End of support for DSpace 1.8.x or earlier from version 5.6 and forward
Since Pure 5.6.0 (released June 2016), support for DSpace 1.8.x and earlier has been deprecated. The functionality still works and will be supported, but customers are strongly advised to migrate to more recent versions of DSpace. All new customers will need a more recent DSpace version.
From version 5.8/4.27 of Pure (February 2017), Pure will no longer support and bug fix the integration to DSpace versions 1.8.x or earlier.
Our decision to do this is to better align with the versions that are supported from the DSpace community as well as keeping the number of supported releases we need to test and maintain at a reasonable level.
The DSpace Committers Group officially ended support of 1.8.x as of January 2015 (see https://wiki.duraspace.org/display/DSPACE/Releases for details, and https://wiki.duraspace.org/display/DSPACE/DSpace+Software+Support+Policy for the groups established support policy).
In future versions of Pure, we will support integration to DSpace versions two years after the DSpace Committers Group end their support, which should provide sufficient time to plan and execute an upgrade of DSpace. For example, support for DSpace 3.x integrations in Pure will end in February 2018.
For customers wishing to migrate to more recent releases of DSpace, please check https://wiki.atira.dk/display/PUREDOCS/Supported+Platforms for supported versions. Since Pure release 5.6, support for DSpace 5.x has been added.
Deprecation / End of support for Equella from version 5.6 and forward
Since Pure 5.6.0 (released June 2016), support for Equella has been removed from the list of officially supported repositories. Existing customers will continue to receive support for the currently-supported Equella version, but we will not implement integration to more recent versions of Equella.
Our decision to drop this is the very low number of customers we have that integrate to Equella.
SQL Server testing
Since Pure 5.6.0 (released June 2016), we only test with SQL Server 2014. SQL Server 2008 and newer will still be supported by Pure.
See the End of Support Announcements for Pure page for all end of support announcements.
Updated at July 27, 2024