5.10.0 Upgrade Notes5.10.0 Upgrade Notes

Upgrade to 5.9.x required prior to upgrade to 5.10

In order to install the 5.10 release, you must first upgrade to a version of 5.9 (i.e. 5.9.0, 5.9.1, 5.9.2, 5.9.3, or 5.9.4)

We have had to introduce this requirement to ensure the successful migration of content to the new unified Research Output data model

The upgrade to 5.10 will fail before any Research Output migration starts if 5.9.x has not already been installed

Re-index after upgrading

• After upgrading to 5.10 it is important to run a re-index. To do this, navigate to the Administration tab → System setting → Search and indexing. Here select all content and "Start indexing". Depending on the content in your Pure this might take some time. It is okay to work in Pure while indexing, but you might experience problems in regards to searching and matching in import.

Potential loss of attached files due to consecutive 'change template' actions

When changing templates multiple times without running the "Preserved Content Update Job" in between, the information about where attached files are stored is lost. Put differently, changing template twice (or more) on a piece of content before the “Preserved Content Update” job has a chance to copy files into their final storage causes Pure to forget the reference to the file. With the reference lost, the file is deleted.

All content types where files can be added are affected. However, given the particular set of circumstances required to trigger this bug, we expect the number of affected records to be very small.

Further information is available here

Unification of Research Outputs : Implications for Portals

• Custom portals (i.e. Advanced portals) and Standard portals should generally not see any major changes resulting from the unification of the Research Output content type. However, we advise that you review your Portal in your TEST environment prior to upgrading Pure in PRODUCTION.
• The Pure portal does not have any changes due to the unified research output model.

Unification of Research Outputs : Implications for External storage (DSpace, Eprints, Fedora)

• If you have setup an external storage where one of the conditions is a limitation on the type, the external storage connection will be disabled if the type is no longer available. The type limitation needs to be updated manually in Pure, and then the external storage enabled again. Note this is only relevant for clients NOT on the common base. Further details can be found here.

SciVal switching to HTTPS

• The SciVal integrations will switch to an encrypted connection using HTTPS instead of using HTTP on the 10th of October 2017. This is reflected in Pure from version 5.8.3 on for SciVal. Customers running on earlier versions may need to address this. Click here for more info...

NETHERLANDS : SEP / KUOZ : Actions required prior to upgrade

• Before upgrading to 5.10.0, you MUST apply the new SEP / KUOZ staff mapping (which will automatically run the "SEP / KUOZ : Update Mapping of SEP / KUOZ Staff Types" cron job). Click here for more info...