5.27.05.27.0

1.1. Copyright management and improved accessibility on images

1.2. Image support on additional content types 

Image upload on additional content types is enabled through System settings > Image upload, and is default DISABLED.

Upload via the Pure API is limited to the specific content type endpoints that are currently available. Copyright information including copyright guidelines and upload and usage confirmation apply to all images uploaded across all content types. 

Recommended order of operations for related settings: With the addition of more content types supporting image upload, if you do plan on enabling the Copyright-related confirmation of upload and usage rights checkbox, please enable the checkbox first before enabling the additional content type image upload.

Please note that there will be no change in the content types for which images are shown on the current Pure Portal. New Pure Portal look and feel will allow showcasing the images on all content types.

1.3. UI updates to licensing section in Administrator overview

1.4. Multiple and exclusively external affiliations allowed on Activities

2.1. Metrics support

3.1. Dspace: update to v7 and collections

As part of the OA requirements around Institutional Repositories (IRs) and, in particular, the need for IRs to provide long term preservation and storage of Research outputs and digital content, Pure maintains an integration (connector) to Dspace, allowing Pure customers to export and save their content from Pure to their Dspace repository, where it can be stored. 

In this release we have updated the existing Dspace connector to support Dspace v7. There are no changes to the existing functionality to the Dspace connector. The content types that can be exported to Dspace are Research output, Datasets and Student theses. When these content types are exported from Pure to Dspace the main thing that is pushed is the metadata, but there is also the possibility to export associated files, that are then saved in Dspace. 

The update to Dspace 7 also (re)introduces the possibility to export and save content in 'collections', that group the exported content based on keywords or organizations. 

Description	Screenshot
It is now possible to define a collection in Pure based on organization.
The organization ID related to a specific collection must be included on the record in Pure
It is also possible to define a collection in Pure based on keywords.
Once a collection is defined and a record is exported from Pure, it will be saved in Dspace as part of that collection
All collections related to a given record are visible on that record in Dspace

Requirements

There are no additional requirements for this update.

 

4.1.  Introducing the Pure Review Content Type

The Pure Review Content Type allows enables institutions to collect, review and approve data from a wide range of stakeholders as part of the pre-award management process.

The use of the review type supports the development of many question set templates and allows the option of distributing review/protocol questions to one or more reviewers as required. Research administrators can use the review responses to further guide decision making and for the process of managing compliance.

As part of our strategy to streamline operational processes and improve service options, the review content type allows institutions to acquire structured information and review/feedback on applications and therefore make informed decisions about what will ensure a greater chance of success. 

As part of the process management workflow, we have now made it easy for administrative users to create approver/checker roles that can be applied as required across the breadth of the internal approvals routing. 

Note: Customisable roles are available once only if the process manager is enabled for award management

Example of the 'manage roles' config screen, available via Administrator > Applications > External workflow configuration > Manage roles

When clicking to 'add role' the user is presented with the following config screen. The uri required for the the role will be automatically populated when adding role titles, but may be amended prior to saving. 

Having added new roles, they are made available as users in Masterdata > Users for selection as per normal user management. 

Once new roles have been established - they may be used when adding responsible Pure roles to the BPMN file configurations by using the URI details (as per the following examples)

To prevent editors and/or administrators of applications from updating the funder reply status outside the confines of the application workflow, we have added an option to disable editing of the funder reply status as displayed in the application user interface. 

The configuration to prevent editors from updating the funder reply status on applications is available in Administrator > Award Management 

Updating this setting 'disable' ensures that the following section is locked and will only be updated as and when the status is triggered by changes in the workflow. 

Following the introduction of the upload an usage rights confirmation checkbox and the possibility to add the copyright information for images in Pure, Pure Portal will also see the corresponding changes.

• If you chose to enable the upload and usage rights confirmation checkbox in Pure, Pure Portal will only show images where the box has been checked
• The copyright information (if available) will appear on hover over the © icon found at the upper right corner of the image
• Alt-text will now also be available for images in the Portal

Please note that if you have not enabled the setting, all images will appear on the Portal (where possible).

Here is an example of copyright shown on a portrait photo (text appears on hover):

Here is an example of the gallery: both images have copyright information, user is hovering over one making the text appear:

As mentioned in the section 3.1 of these release notes, it is now possible to manage images that are shown on the Portal to ensure there is no copyright infringement.

• If you choose to activate the upload an usage rights confirmation checkbox in Pure, Pure Portal will only show images where the box has been checked
• When enabling this feature for the first time you have a choice on how to treat images that are already in Pure and are displayed in the Portal. You can
  • Accept all: if you select this, the copyright confirmation checkboxes will be checked for all the existing images and they will continue to be shown on the Portal
  • Accept only the portraits of persons and hero/profile images for organisations: only the accepted images will be shown, while any images appearing on the galleries (i.e. Person gallery, equipment gallery) will not be displayed. Once the user goes in and checks the usage rights confirmation checkbox, the approved images will be shown in the gallery again.
  • Reject all: if you select this, the copyright confirmation checkboxes for all the existing images will remain unchecked, leading to images being NOT shown on the Portal

Due to the Direct2Experts initiative being no longer active, this functionality and the corresponding setting has been removed from the Portal. You do not need to take any actions.

As part of preparing for the updates to roles for reporting, we needed to do some cleanup of the reporting roles. Currently, some editor roles, content administrator roles, and validators could do reporting if they also had a reporting role. This has now been removed such only a reporting role will be able to do reporting. We do not anticipate many users to be affected by this, but know that some will be. The affected users will experience that they no longer can report on certain content types, only the content types where they have a reporting role. We have also made sure that only Administrators can report on confidential content. We're not removing any roles from the system, only which roles are allowed to do reporting. This is only for the reporting module, the classic reporting module will not be affected by this change.

Example

Alice have the following roles: Global reporter of organizational units and Administrator of Research output. Alice would be able to do reporting on Organizational units and Research outputs in 5.26, but from 5.27.0 she will no longer be able to report on Research output since she doesn't have an explicit reporting role on research output. By adding a Global report of Research output, she will have the same level of reporting rights as she had prior to 5.27.0

Pure can contain a lot of links to 3rd party resources, such as DOI, link to full texts etc. Previously, these were not clickable link in the reporting module, meaning that you would need to copy-and-paste the link into the browser. With this release we have made these types of links on research outputs full clickable. This means that when creating workspaces and datastories the DOIs, fulltext files link, and other links are clickable, no more copy-and-paste. When exporting to Excel, the links are exported as link there also, so you can open them from within Excel.

In order to provide at better experience with the reporting module we have updated the layout of the home page for reporting. Your favourite and recent workspaces now have their own place making it much esiear to access them from the home page. We have also reworked the menu when creating a new workspace to also provide easier access to all of your favourite workspaces.

To make the reporting on metrics even better, we have improved the flow for reporting on metrics. Previously, you would have to create the relation to metrics, for instance person metrics, then you would have to apply a filter to only show the relevant metric, for instance h-index. With this update, we have added new relations, such that you can select the h-index when you are creating the relation from person to metrics. This will enable users to get an overview of which metrics is availble and an really easy way of selecting the correct metric.

Another big update for metrics, is the addtion of the ability to select journal metrics right from the Research outputs. The journal metrics that you're getting this way, is the journal metrics that corresponds to the year the publication was publised. This makes is possible to create a report with for instance SNIP, Citescore or any other journal metric, equal to the publication year. It is no longer needed to create a relation to the journal, then to the journal metrics, which then should be split on metrics year to get the relation journal metric for the year the publication was published.

What we also have done, is to remove all the old ways of adding metrics to a report, now this must happen using the metric relations. The reason behind this is for performance improvements. Previously, some of the metrics would be so slow that they wouldn't appear in the report, or after minutes. With the new relations, these will be adding within seconds. This mean that any exsting report that were using metrics needs to be updated, if they are using the metrics that were adding under the content type, and not as a relation.

As part of adding new WOS metrics to Pure, these have now been made available in the reporting module. You can now create reports on the various WOS metrics that Pure supports. You can find the new values were you add values to a workspace. 

7.1. UK:REF - Review type for continuous assessment