PURE (Lancaster’s Research Information Management System) is being migrated from an on-site installation to the Elsevier (Developer of PURE) cloud hosting platform.

This will affect the PURE system and also the Lancaster University Research Directory (https://www.research.lancs.ac.uk/portal/) which will be replaced by a new hosted portal.

Why is this happening?

Performance, safety, security and access to future releases of PURE are key drivers for migration and will provide the following benefits:

• Enhanced Security: Secure hosting and application of security updates will be performed by Elsevier without the need for ISS intervention.
• Improve Performance: Users will benefit from faster, more reliable access.
• Reduced operational overhead: System maintenance and infrastructure monitoring burden will be removed from ISS.
• Enable Future upgrades: The currently operational PURE version is the last that is supported on the Lancaster University IT infrastructure. Moving to the cloud will enable us to take advantage of future upgrades and functionality.

When will the migration happen?

Migration is scheduled for the week commencing 15th September. There will be some scheduled downtime during the preparation and migration window.

Further updates will be posted here.

What do I need to do before the migration?

Pure users do not need to do anything specific in order to prepare for the migration and access to the new site will be via the same URL as the existing system.

It is good practice to keep your PURE profile and information up to date. Your publicly visible profile is a vital tool for showcasing your research, expertise, and impact. Take the time now to refresh your profile to help maximise the benefits of Pure’s new cloud-based platform and ensure your research is presented effectively.

What do I need to do after the migration?

Once the migration is complete you should check your personal profile and publications/activities/projects etc to ensure that all your information has migrated successfully

Any issues should be reported to RSO Systems