How Can We Help?
5.33.15.33.1
We are pleased to announce that version 5.33.1 (4.52.1) of Pure is now released
Always read through the details of the release - including the 5.33.1 On-premises installation upgrade notes - before installing or upgrading to a new version of Pure
Release date: 7. July 2025
Hosted customers:
-
Staging environments (including hosted Pure Portal) will be updated:
- 9. July 2025 (APAC + Europe)
- 10. July 2025 (North/South America).
-
Production environments (including hosted Pure Portal) will be updated:
- 9. July 2025 (APAC + Europe)
- 10. July 2025 (North/South America).
Pure Core: Administration
Introducing OAuth to Pure Mail for Microsoft 365
As Microsoft has announced that they no longer will support basic authentication (basic auth) as SMTP Auth (to connect to their SMTP Server) we have introduced OAuth for Microsoft 365.
Please note that Microsoft have moved the original deadline from September 2025 to March 2026.
To help you getting started, we have made a guide which can help you moving from basic auth to using OAuth on Microsoft 365.
Enable new features
We have introduced a New features toggle for Pure administrators to allow their users to test and use new features at their convenience.
All new features listed are disabled by default. Administrators can choose to deploy the new feature at their convenience, with some features incorporating secondary toggles to allow users to switch between classic and new features, or make the new feature the default.
Read more about this toggle and the other new User Interface feature changes here.
Reordering custom filters on content types
[July 14 update]
Due to an error in the release notes, reordering is not available until 5.33.2 - check Release calendar for release dates.
The new filter functionality can only be accessed if the new Left side menu is enabled. See Enable new features above.
See User Interface changes > Custom filters, for more information.
Author collaboration content type filter
Learn more about unused content filter here, and Author collaboration content type here.
Course content type updates
The course content type has been updated to include the following additional fields.
- Instruction language
- Course credits and course credit type
- Related files and links
Read more about Courses here.
Pure API
Author collaboration
Important Notes:
- Access Definition: To utilize the new Author collaboration endpoints, ensure that author collaboration is included in your access definition. This step is vital for making the endpoints selectable by the API key.
- Design Consistency: The Author collaboration endpoints adhere to the same design principles established for other related endpoints, ensuring a consistent user experience across the API.
Documentation: For detailed information on the Pure API, please refer to the official documentation available at:
- API Documentation Getting started: Pure API user guide or your local version: (<your server url>/ws/api/documentation/index.html)
- Interactive API Documentation: (<your server url>/ws/api/rapidoc.html)
Future Enhancements: To stay informed about remaining content types and upcoming features, please refer to the Pure API roadmap. We encourage users to participate in the idea exchange by voting on linked tickets to help prioritize future endpoint developments.
Pure Portal
Robots.txt file control
Following customer demand, we have introduced greater flexibility and control into how portal robots.txt files are managed.
A robots.txt file acts as a set of instructions for web crawlers (bots) visiting a website. When a bot makes a request to a website, it first checks the robots.txt file to understand which pages it can and can't crawl, which links it should and shouldn't follow, and other requirements for bot behavior. Robots.txt files manage bot activity for the entire site, while the meta robots tags apply to individual web pages (for example, person profile sub-pages are marked as not to be indexed on the Portal). Robots.txt file cannot enforce these rules, but good bots are programmed to look for the file and follow the rules before they do anything else.
What is the current setting:
- Robots.txt does not disallow any bots. This means that all verified bots that have been allowed through by the general Cloudflare protective rule are able to access your Portal.
- To review your Robots.txt file go to your Portal homepage and add /robots.txt to the URL.
- Robots.txt text is a vendor-only setting. To make a change to it, please reach out to Support.
You can find out more about Robots.txt as well as other tools we have available for managing bot activity on your Portal here.
Integrations
DataCite Updates
Limit search based on repositories
In this release, we have introduced the ability to import Datasets only from certain repositories, such as your institution’s local repository like Zenodo or Figshare. In order to do that you need to locate a Repository code.
A guide to filling in the Repository information can be found in Limiting search results by repository
Improved Name-Based Matching in Automated Search Profiles
In this release, we improved the accuracy of automated dataset searches for Persons. Previously, mismatches between first and last names could result in excessive false candidates. This issue is now resolved, ensuring both names match the same person.
When upgrading to version 5.33.1, all existing import candidates will be removed. The next run of the “Search for import candidates” job will generate a new, more precise set of candidates.
Improved handling of versioning
In DataCite, each version of a record receives a new DOI and a new record, which has led to many duplicate records being imported into Pure and made it difficult to identify and store only the latest version. Starting with this release, we’ve implemented logic to import only the most current version.
Updates to “Data made available”
In version 5.33.0, we initially imported the “Published Year” from DataCite into the “Date Made Available” field. We have now updated the logic to default to importing the “Available Date” from DataCite. Since this field is not mandatory in DataCite, the system will fall back to using the “Published Year” when the “Available Date” is missing.
Read more about DataCite integration from here
Updates to XML import on Project/Application/Award
We have updated our XML to also support import of internal collaborators on Project, Application and Award. Additionally, we have expanded the Project XML to include support for relations to Prizes and Datasets
Documentation has been updated accordingly.
Application:
Applications synchronisation (Views)
Award:
Project:
Project synchronisation (Views)
Institutional CV templates
With this release, we're updating our CV module with a new capability, namely the option to create CV templates. We have updated the interface for managing CV templates. With this update, it is also possible to see usage of each template. All existing CV templates will be denoted as classic.
As a part of updating the UI for CVs, we have also removed some of the classic cv templates, namely: NiH biosketch and Europass. The Nih recommends using SciENcv which can import from ORCiD. And the Europass format is no longer supported.

Read more about how to create and use the institutional templates here:
Bug fixes
This release contains a number of bug fixes, including the following from Known issues:
Issue Number | Title |
---|---|
KI-000191 | Missing 'open' view for confidential related projects on application and awards |
KI-000217 | Missing link to Data Privacy Policy |
KI-000221 | Some publications appear blank on the portal |
KI-000218 | Error when enabling DataCite in Production |
KI-000215 | Incorrect Total Number of Persons per Organisation |
KI-000200 | Visibility Issues with Search Bar in Dark Mode in Pure |
Published at July 14, 2025