5.12.15.12.1

Prior to this release, for SEP and KUOZ, 'Not eligible' covered three things:

• the content type does not exist in the mapping file, so is not eligible for SEP / KUOZ counting
• the content type has been specifically mapped to 'Not eligible' in the SEP output mapping file
• the individual item of content has been manually selected as 'Not eligible' (for various reasons)

When updating a mapping file, Pure would re-visit all mappings and make the necessary changes to the records. But this also meant that all 'Not eligible' items were updated as well - whether they were not eligible because they didn't previously have a mapping, or they were manually selected as not eligible. This was problematic for those items manually selected as Not eligible - these should not automatically update.

With this release, we have introduced two new elements to better handle ineligible content:

• A new classification for 'Not eligible (manual selection)'. This value is never automatically updated - even if the specific mapping for that item's type is updated.
• A new classification name - 'Not eligible (mapped value)' - for those items that are not eligible because they don't exist in the mapping file or have been specifically mapped to not eligible in the SEP output mapping file.

Notes:

• Along with this enhancement, we have improved the robustness of how SEP / KUOZ types are selected upon changes to the relevant properties of the item (e.g. category, role). You may therefore see slightly different behaviour in the SEP / KUOZ type fields from this release. This includes the SEP or KUOZ type being shown as 'Not eligible (mapped value)' until all relevant fields (category, peer-reviewed, person role, etc.) are populated.
• The 'Not eligible (mapped value)' type should never be manually selected - it is only to be used by Pure automatically as per the mapping rules in the xml file. If it manually selected, upon saving, the field will revert back to the default value

JIRAs resolved by these improvements include:

• PURESUPPORT-38868 - Re-emerged issue Inconsistent Use of 'Not Set' and 'Not Eligible' CLOSED
• PURESUPPORT-44427 - Manually Set SEP & KUOZ Research Output 'Not Eligible' overwritten by job CLOSED
• PURESUPPORT-44132 - Concerns regarding note in KUOZ - Update Activity type mapping CLOSED
• PURESUPPORT-45073 - Saving changed KUOZ activity type status with Activities, Prizes and Press/Media doesn't work CLOSED

Upon the release of KUOZ Table D: Research activities in 5.11.2, a discrepancy was discovered between Table D and the existing KUOZ Table C: Research outputs. Table C made use of the 'Scientific' category, whereas Table D used the 'Academic' category. In this release, we have updated KUOZ Table C to employ the 'Academic' category, as agreed by the User Group.

Prior to upgrading to 5.12.1, it is recommended that you create and export a report for all Research Outputs, including the following fields. This will give you a 'before' picture that you can compare against post-upgrade to confirm all values have migrated as expected.

• Pure ID / UUID
• Output type
• Peer review
• Publication category
• SEP Output type
• KUOZ Output type

Upon upgrade to 5.12.1, where the publication category 'Scientific' is employed for Research Outputs, the classification will automatically be updated to 'Academic'. Additionally, if any of your SEP or KUOZ Output mapping files previously made employed mappings that included the 'Scientific' publication category, these will be automatically updated to use the new 'Academic' classification.

The default SEP Output mapping file and KUOZ Output mapping file have been updated in the SEP/KUOZ wiki.

Guidance on how to bulk update categories for Activities, Prizes, and Press/Media is available here.

JIRAs resolved by these improvements include:

• PURESUPPORT-44302 - Incorrect display of category types Scientific and Other in KUOZ D: Research Activities CLOSED