As such, CDFs are created with care and consideration, and your institutions (and user) need, and possibilities will be balanced with the limitations and technical considerations associated with CDFs. These have been quite tricky to report on, as it isn't clear where to find the necessary information: is it on the person, or is it on the research output? With this release, we've introduced a new way of reporting on this type of information.Ĭustom-defined fields: Custom-defined fields (CDFs) are an extremely powerful way for your institution to extend your coverage of content without the need to wait for Pure updates.
#OMNIPRESENCE THESAURUS DOWNLOAD#
While the actual scanning of the files is performed outside Pure, you can now decide to show the status of files as a badge, and to block the download of infected and/or unscanned files.Complex relation reporting: In Pure we have a lot of information on the relationship between types. To increase the security within Pure, we are now scanning files for viruses. Security: antivirus scan, status badges and download blocker For projects, this applies both to the external organizations affiliated to the project as well as any collaborative partners. For research outputs, this means showing the external organizations affiliated to authors on the output. We will start displaying external organization relationships for both research outputs and projects on the Portal.
#OMNIPRESENCE THESAURUS HOW TO#
In this release, we have made the new improved way of reporting on metrics available for: Research Outputs, Journals, and Publishers. This is the first iteration of the improvement, and we are working on how to make the user experience even smoother and more efficient. The data is now stored in a format optimized for reporting. In previous versions, metrics were selected as part of the details of the content, now this have been changed into a relation to the content.
We have redesigned the way of reporting on metrics in order to improve the performance of the reporting module. The users can also get an easy overview of whether a particular dataset is OpenAIRE-compliant through the newly added OpenAIRE compliance check. To facilitate the enrichment, monitoring and management of datasets for OA compliance, including all mandatory OpenAIRE fields, it is now possible for users to add License information at the record and file level. The model for dataset records in Pure is expanded to align with OpenAIRE guidelines for dataset interoperability ( ). The DOI and source links for research output (where provided) are now also available in the top right corner of the metadata section of the editor to provide easier and faster access to the source of record for checking and validation purposes.
#OMNIPRESENCE THESAURUS UPGRADE#
On the 26th of October, we upgrade Pure to 5.25.0ĭOI and source links at top of research output editor
0 kommentar(er)
