How Can We Help?
5.13.0 Upgrade Notes5.13.0 Upgrade Notes
Please follow the general Upgrading Pure documentation as well as the 5.13.0 (4.32.0) specific instructions below.
PARTICULAR ITEMS TO NOTE WITH THIS RELEASE
Old Pure web service API will be deprecated in 5.13.0 (October 2018) and removed with 5.14.0 (February 2019)
We announced in the Pure 5.9.0 release (June 2017) our plans to remove the old web service API upon the Pure 5.13.0 release in October 2018. Over the past few months, we have received feedback that our users would like us to extend the overlap period of the old web service API. As such we will not be removing the old web service API with the release of Pure 5.13.0, but we will deprecate* it with the 5.13.0 release and remove it in the 5.14.0 release in February 2019.
*Deprecation means that we will no longer fix or improve the old web service API, but you can continue using it until its removal in 5.14.0.
We encourage everyone to make sure you have adapted your applications to use the new web service API. Details of the new web service API can be found here.
Please also be aware that the new web service API only supports the Unified Project Model. Content in the old Project model will not be available on the new web service API. If you implemented Pure from 4.13 or later (this includes all of Pure 5), you are already are using the Unified Project Model. If you are in doubt, you can check the Administrator tab > Unified Project Model tab. If this tab with the Unified Project Model settings is available, you are using the Unified Project Model. Please contact the Pure Support team for assistance in migrating to the Unified Project Model.
Removal of the 5.9 web service API endpoint
Pure 5.13.0 is the first release where a new web service endpoint (the 5.9 API) will be removed. If you are currently using the 5.9 endpoint, you will need to update your queries to use one of the supported web service endpoints. For this 5.13.0 version these are:
- 5.10 API
- 5.11 API
- 5.12 API
- newly introduced 5.13 API
You can find more information about the web service delivery module in the Pure 5.9.0 release notes. We will continuously inform you about removed web service endpoints in the individual Upgrade Notes of the release.
Faculty and Academic Activity Reporting (FAAR)
We recently discovered an issue with FAAR functionality such that, under certain conditions, when a batch download of FAAR reports was actioned, Parent organisations were removed from Organisational units in the database, leading to orphaned Organisational units in the hierarchy (if you synchronise your Organisational unit content, Parents would be re-instated upon the next synchronisation). This issue has been resolved in both 5.12.4 and 5.13.0, and a job to resolve the Organisational hierarchy issues caused is expected in the 5.13.0-1 release.
We have been in touch with all customers who have enabled FAAR with more detail on this issue and work being undertaken to fix the Organisational hierarchy issues caused. If you have not heard from us but think you have been affected, please contact the Pure Support team directly).
Espacenet: New API requires access credentials
Espacenet has released a new version of their API, which now requires the use of access credentials. All customers using Espacenet as an import source must upgrade their Pure to at least version 5.12.2. Further details are available from the 5.12.2 release notes.
Funding Discovery
Customers using the Funding Discovery module are requested to upgrade their Java 1.8 version to version 1.8.0_162-b12 or newer. Older versions cause SSL errors (SSL handshake failure from the secure HTTPS connection made from Pure to the Pure funding service).
In order to upgrade to 5.13.0 (4.32.0), you must be upgrading from at least 5.9.x (4.28.x). We strongly recommend that you do not attempt to skip any more than three major releases when upgrading as to do so increases the risk of migration errors.
Content validation
You are generally encouraged to check all content in the re-validation workflow step prior to upgrade as changes to the underlying data model may not be reflected in the re-validation overview screen (see example)
Further, you are encouraged to check if all content can validate prior to an upgrade of Pure. This check is done by running the Check content and files job and resolving any data validation issues that are flagged by the job
Pure Portals
Backwards compatibility for Pure Portals
As previously communicated, we provide support for only the three most recent major releases of the Pure Portal. This means that as of the launch of Pure 5.13.0, versions 5.10.0 and earlier will not be officially supported by the Pure team.
If you continue to run an earlier version, new features and bug-fixes will not be available. We are also unable to make any commitment as to the performance and stability of your Portal. We therefore strongly recommend you regularly upgrade Pure to ensure Pure Portal compatibility.
NOTE : this issue is only relevant for customers who have the Pure Portal AND are responsible for managing their own upgrades
Custom and Advanced Portals
Phasing out Custom and Advanced Portals
As previously communicated, we will be phasing out our support for Custom and Advanced Portals.
Current clients will continue to receive support (new enhancements and bug fixing) through 2021, however please bear in mind that we will be reallocating development resources during this period, so the volume of enhancement work we can take on will be limited.
As of January 2022 only critical bug fixing will be supported.
In the meantime, Pure Portals are being enhanced with key features found in Advanced and Custom Portals as part of our continuous, ongoing product development. This work is being undertaken on a product level, and in direct collaboration with current customers.
We are committed to supporting the migration of current clients and would be very glad to discuss your additional needs and requirements in facilitating a smooth migration as soon as possible - should you be interested in going down this route. This conversation will help us better prioritise our development plans. Please feel free to reach out to us with any questions or requests for consultation via our Pure Support team.
Browser support
Internet Explorer will no longer be supported by Pure from 5.15.0 (June 2019)
From 5.13.0, Pure will show the following notification to users that access Pure using Internet Explorer 11 or older:
Removing support for Internet Explorer in Pure 5.15.0 enables the team to focus even more time on delivering great user experiences that run smoothly in modern browsers such as Chrome, Firefox, Safari, and Edge.
User documentation
Retiring old Pure tutorial videos
To promote use of up-to-date Pure Academy content, we are concluding the removal of old Pure-related videos from the Pure YouTube channel.
The information explained in the most popular videos (How to use reporting, Set up scan for publications in online sources) are available in the Pure Academy and users will be redirected to these locations.
We will then conclude by deleting the channel completely in December 2018.
If you are still maintaining local resources that link to this content, please update your links to point to the Pure Academy.
Changes that affect Pure 5.13
Suggested change to Tomcat AJP connector in server.xml
Due to a bugfix in Tomcat 8.5.31 the handling of a specific set of characters in the URL has changed. This may impact any existing service users of the Pure REST web services. In order to allow the previous character semantics the following attribute should be added to the AJP connector element in the Tomcat server.xml:
relaxedQueryChars="^{}[]|"" |
See the End of Support Announcements for Pure page for all end of support announcements.
Updated at July 27, 2024