Research Output Management in PS Higher Education: FAIR Metadata Principles

 
Metadata for research outputs management
Part 2
 
Susanna Mornati – 4Science
ORCiD
 0000-0001-9931-3637
 
Basic Training Workshop
/ 6-8 
September 2017
 
 
FAIR metadata: the origins
 
Data management is not a goal in itself, but a means to foster  the
advancement of knowledge.
The existing digital ecosystem surrounding scholarly output publication has
many barriers preventing optimal discovery and reuse:
variety of approaches,
fragmentation of repositories,
different access policies,
uncertain license conditions,
lack of machine interfaces,
lack of metadata standardization…
To overcome these obstacles, a workshop was held in the Netherlands in
2014, bringing together a wide group of academic and private stakeholders,
setting foundational principles that all research objects should be 
FAIR
:
Findable, Accessible, Interoperable, Reusable
 
2
 
FAIR metadata: the principles
 
F
 
= Findable
A
 
= Accessibile
I
 = Interoperable
R
 = Reusable
 
3
 
FAIR metadata: materials
 
The FAIR Guiding 
Principles for scientific data management and
stewardship - 
https://www.nature.com/articles/sdata201618
 
 
FAIR DATA PRINCIPLES -
https://www.force11.org/group/fairgroup/fairprinciples
 -
https://www.force11.org/fairprinciples
 
 
Guidelines on FAIR Data Management in Horizon 2020 -
http://ec.europa.eu/research/participants/data/ref/h2020/gr
ants_manual/hi/oa_pilot/h2020-hi-oa-data-mgt_en.pdf
 (DMP,
Data Management Plan)
 
 
 
 
4
 
FAIR metadata: Findable
 
TO BE FINDABLE:
 
F1. (meta)data are assigned a globally unique and eternally
persistent identifier.
 
F2. data are described with rich metadata.
 
F3. (meta)data are registered or indexed in a searchable resource.
 
F4. metadata specify the data identifier.
 
 
5
 
FAIR metadata: Accessible
 
TO BE ACCESSIBLE:
 
A1  (meta)data are retrievable by their identifier using a
standardized communications protocol.
 
A1.1 the protocol is open, free, and universally implementable.
 
A1.2 the protocol allows for an authentication and authorization
procedure, where necessary.
 
A2 metadata are accessible, even when the data are no longer
available.
 
6
 
FAIR metadata: Interoperable
 
TO BE INTEROPERABLE:
 
I1. (meta)data use a formal, accessible, shared, and broadly
applicable language for knowledge representation.
 
I2. (meta)data use vocabularies that follow FAIR principles.
 
I3. (meta)data include qualified references to other (meta)data.
 
7
 
FAIR metadata: Reusable
 
TO BE RE-USABLE:
 
R1. meta(data) have a plurality of accurate and relevant
attributes.
 
R1.1. (meta)data are released with a clear and accessible data
usage license.
 
R1.2. (meta)data are associated with their provenance.
 
R1.3. (meta)data meet domain-relevant community standards.
 
8
 
OpenAIRE guidelines
for Literature Repositories
 
https://guidelines.openaire.eu/en/latest/literature/index.html
 
OpenAIRE uses the OAI-PMH v2.0 protocol for harvesting
publication metadata
 
OpenAIRE expects metadata to be encoded in the Dublin Core
metadata format (metadataPrefix oai_dc)
 
OpenAIRE relies on a specific syntax used in the values of
standard Dublin Core metadata fields to identify
projects, funders, referenced publications, and datasets.
   This syntax takes the form of URIs and is defined as the
info:eu-repo namespace.
 
9
 
10
 
OpenAIRE guidelines
for Literature Repositories
 
Application profile overview:
 
https://guidelines.openaire.eu/en/latest/literature/application
_profile.html
 
 
11
 
OpenAIRE guidelines
for Data Archives
 
https://guidelines.openaire.eu/en/latest/data/index.html
 
OpenAIRE uses the OAI-PMH v2.0 protocol for harvesting
dataset metadata.
 
OpenAIRE expects metadata to be encoded in the DataCite
metadata format (metadataPrefix oai_datacite).
 
OpenAIRE shares the goal of the DataCite Metadata Schema - to
provide a domain-agnostic metadata schema and
provide interoperability through a small number of properties -
making interoperability possible in the simplest manner
possible and as a result keep the technical barriers for
implementation as low as possible.
 
 
12
 
13
 
OpenAIRE guidelines
for Data Archives
 
Application profile overview:
https://guidelines.openaire.eu/en/latest/data/application_pro
file.html
 
DataCite:
http://schema.datacite.org/meta/kernel-3/doc/DataCite-
MetadataKernel_v3.1.pdf
 
 
Example:
https://purr.purdue.edu/publications/1118/2
 
http://schema.datacite.org/meta/kernel-3/example/datacite-
example-dataset-v3.0.xml
 
 
 
 
 
 
 
14
 
OpenAIRE Guidelines for CRIS Managers
based on CERIF-XML
 
https://guidelines.openaire.eu/en/latest/cris/index.html
https://zenodo.org/record/17065
https://zenodo.org/record/17065/files/OpenAIRE_Guidelines
_for_CRIS_Managers_v.1.0.pdf
 
The Guidelines provide orientation for CRIS managers to expose their
metadata in a way that is compatible with the OpenAIRE
infrastructure.
 
CERIF (Common European Research Information Format) is a standard
data model for research information and a recommendation by the
European Union to Member States.
 
The OpenAIRE data model is CERIF-compliant and CERIF XML has
been adopted by OpenAIRE as the basis for harvesting and importing
metadata from CRIS systems.
 
15
 
CERIF subset for OpenAIRE
 
16
 
OpenAIRE Guidelines for CRIS Managers
based on CERIF-XML
 
 
The model comprises of the following CERIF Research Entities:
 
• Publication: cfResultPublication (cfResPubl);
• Product/Dataset: cfResultProduct (cfResProd);
• Person: cfPerson (cfPers);
• Organisation: cfOrganisationUnit (cfOrgUnit);
• Project: cfProject (cfProj);
• Funding: cfFunding (cfFund);
• Equipment: cfEquipment (cfEquip);
• Service: cfService (cfSrv).
 
17
 
OpenAIRE Guidelines for CRIS Managers
based on CERIF-XML
 
 
The following tables define the CERIF data elements to be
utilised for the exchange of data between individual CRIS
systems and the OpenAIRE infrastructure.
 
Example: The CERIF entity cfProject (cfProj) in the context of
OpenAIRE is used to represent funded projects.
 
 
18
 
CERIF for OpenAIRE
: e.g. Projects
 
Internal Identifier cfProj.cfProjId
Start Date cfProj.cfStartDate
End Date cfProj.cfEndDate
Acronym cfProj.cfAcro
Title cfProj.cfTitle
Abstract cfProj.cfAbstr
Subject cfProj.cfKeyw; cfProj.cfProj_Class
Open Access Requirements cfProj.cfProj_Class
(at the moment: OA mandated, OA not mandated)
Federated Identifiers cfProj.cfFedId.cfFedId
(type of identifier is given through cfProj.cfFedId.cfFedId_Class)
Relations (e.g.):
Product / Dataset cfProj.cfProj_ResProd
Person cfProj.Proj_Pers
Organisation cfProj.cfProj_OrgUnit
 
19
 
CERIF for OpenAIRE
: e.g. Projects
 
Example:
https://zenodo.org/record/17065/files/openaire_cerif_xml_e
xample_projects.xml
 
 
20
 
Tool to implement guidelines automatically
 
DSpace-CRIS:
 
https://wiki.duraspace.org/display/DSPACECRIS/DSpace-
CRIS+Home
 
DSpace-CRIS is the 
open-source
 extension of DSpace for the
Research Data and Information Management.
 
Examples:
http://ira.lib.polyu.edu.hk/cris/rp/rp00068
http://ktisis.cut.ac.cy/handle/10488/7613
http://dspacecris.eurocris.org/
https://portalrecerca.csuc.cat/
 
21
 
Practical e
xercise – small groups - 30
minutes
 
1.
Choose a publication here:
https://www.openaire.eu/search/find
 and describe it
according to the OpenAIRE Guidelines for Literature
Repositories:
https://guidelines.openaire.eu/en/latest/literature/index.h
tml
 
 
2.
Choose a dataset here: 
http://www.re3data.org/
 and
describe it according to the OpenAIRE Guidelines for Data
Archives:
https://guidelines.openaire.eu/en/latest/data/index.html
 
22
Slide Note
Embed
Share

Research output management in higher education focuses on making scholarly output findable, accessible, interoperable, and reusable through the implementation of FAIR metadata principles. The digital ecosystem surrounding scholarly publications faces barriers like fragmented repositories, varied approaches, and lack of standardization. A workshop in the Netherlands in 2014 set foundational principles for FAIR data, emphasizing the importance of addressing these obstacles for advancing knowledge in academia.

  • Research
  • Higher Education
  • FAIR
  • Metadata Principles
  • Scholarly Publications

Uploaded on Sep 30, 2024 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

E N D

Presentation Transcript


  1. Metadata for research outputs management Part 2 Susanna Mornati 4Science ORCiD 0000-0001-9931-3637 Basic Training Workshop/ 6-8 September 2017 Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP This project has been co-funded with support from the European Commission. The European Commission support for the production of this publication does not constitute endorsement of the contents which reflects the views only of the authors, and the Commission cannot be held responsiblefor any use which may be made of the information contained therein.

  2. Research Output Management in PS Higher Education FAIR metadata: the origins Data management is not a goal in itself, but a means to foster the advancement of knowledge. The existing digital ecosystem surrounding scholarly output publication has many barriers preventing optimal discovery and reuse: variety of approaches, fragmentation of repositories, different access policies, uncertain license conditions, lack of machine interfaces, lack of metadata standardization To overcome these obstacles, a workshop was held in the Netherlands in 2014, bringing together a wide group of academic and private stakeholders, setting foundational principles that all research objects should be FAIR: Findable, Accessible, Interoperable, Reusable Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 2

  3. Research Output Management in PS Higher Education FAIR metadata: the principles F= Findable A= Accessibile I = Interoperable R = Reusable Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 3

  4. Research Output Management in PS Higher Education FAIR metadata: materials The FAIR Guiding Principles for scientific data management and stewardship - https://www.nature.com/articles/sdata201618 FAIR DATA PRINCIPLES - https://www.force11.org/group/fairgroup/fairprinciples - https://www.force11.org/fairprinciples Guidelines on FAIR Data Management in Horizon 2020 - http://ec.europa.eu/research/participants/data/ref/h2020/gr ants_manual/hi/oa_pilot/h2020-hi-oa-data-mgt_en.pdf (DMP, Data Management Plan) Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 4

  5. Research Output Management in PS Higher Education FAIR metadata: Findable TO BE FINDABLE: F1. (meta)data are assigned a globally unique and eternally persistent identifier. F2. data are described with rich metadata. F3. (meta)data are registered or indexed in a searchable resource. F4. metadata specify the data identifier. Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 5

  6. Research Output Management in PS Higher Education FAIR metadata: Accessible TO BE ACCESSIBLE: A1 (meta)data are retrievable by their identifier using a standardized communications protocol. A1.1 the protocol is open, free, and universally implementable. A1.2 the protocol allows for an authentication and authorization procedure, where necessary. A2 metadata are accessible, even when the data are no longer available. Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 6

  7. Research Output Management in PS Higher Education FAIR metadata: Interoperable TO BE INTEROPERABLE: I1. (meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation. I2. (meta)data use vocabularies that follow FAIR principles. I3. (meta)data include qualified references to other (meta)data. Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 7

  8. Research Output Management in PS Higher Education FAIR metadata: Reusable TO BE RE-USABLE: R1. meta(data) have a plurality of accurate and relevant attributes. R1.1. (meta)data are released with a clear and accessible data usage license. R1.2. (meta)data are associated with their provenance. R1.3. (meta)data meet domain-relevant community standards. Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 8

  9. Research Output Management in PS Higher Education OpenAIRE guidelines for Literature Repositories https://guidelines.openaire.eu/en/latest/literature/index.html OpenAIRE uses the OAI-PMH v2.0 protocol for harvesting publication metadata OpenAIRE expects metadata to be encoded in the Dublin Core metadata format (metadataPrefix oai_dc) OpenAIRE relies on a specific syntax used in the values of standard Dublin Core metadata fields to identify projects, funders, referenced publications, and datasets. This syntax takes the form of URIs and is defined as the info:eu-repo namespace. Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 9

  10. Research Output Management in PS Higher Education Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 10

  11. Research Output Management in PS Higher Education OpenAIRE guidelines for Literature Repositories Application profile overview: https://guidelines.openaire.eu/en/latest/literature/application _profile.html Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 11

  12. Research Output Management in PS Higher Education OpenAIRE guidelines for Data Archives https://guidelines.openaire.eu/en/latest/data/index.html OpenAIRE uses the OAI-PMH v2.0 protocol for harvesting dataset metadata. OpenAIRE expects metadata to be encoded in the DataCite metadata format (metadataPrefix oai_datacite). OpenAIRE shares the goal of the DataCite Metadata Schema - to provide a domain-agnostic metadata schema and provide interoperability through a small number of properties - making interoperability possible in the simplest manner possible and as a result keep the technical barriers for implementation as low as possible. Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 12

  13. Research Output Management in PS Higher Education Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 13

  14. Research Output Management in PS Higher Education OpenAIRE guidelines for Data Archives Application profile overview: https://guidelines.openaire.eu/en/latest/data/application_pro file.html DataCite: http://schema.datacite.org/meta/kernel-3/doc/DataCite- MetadataKernel_v3.1.pdf Example: https://purr.purdue.edu/publications/1118/2 http://schema.datacite.org/meta/kernel-3/example/datacite- example-dataset-v3.0.xml Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 14

  15. Research Output Management in PS Higher Education OpenAIRE Guidelines for CRIS Managers based on CERIF-XML https://guidelines.openaire.eu/en/latest/cris/index.html https://zenodo.org/record/17065 https://zenodo.org/record/17065/files/OpenAIRE_Guidelines _for_CRIS_Managers_v.1.0.pdf The Guidelines provide orientation for CRIS managers to expose their metadata in a way that is compatible with the OpenAIRE infrastructure. CERIF (Common European Research Information Format) is a standard data model for research information and a recommendation by the European Union to Member States. The OpenAIRE data model is CERIF-compliant and CERIF XML has been adopted by OpenAIRE as the basis for harvesting and importing metadata from CRIS systems. Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 15

  16. Research Output Management in PS Higher Education CERIF subset for OpenAIRE Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 16

  17. Research Output Management in PS Higher Education OpenAIRE Guidelines for CRIS Managers based on CERIF-XML The model comprises of the following CERIF Research Entities: Publication: cfResultPublication (cfResPubl); Product/Dataset: cfResultProduct (cfResProd); Person: cfPerson (cfPers); Organisation: cfOrganisationUnit (cfOrgUnit); Project: cfProject (cfProj); Funding: cfFunding (cfFund); Equipment: cfEquipment (cfEquip); Service: cfService (cfSrv). Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 17

  18. Research Output Management in PS Higher Education OpenAIRE Guidelines for CRIS Managers based on CERIF-XML The following tables define the CERIF data elements to be utilised for the exchange of data between individual CRIS systems and the OpenAIRE infrastructure. Example: The CERIF entity cfProject (cfProj) in the context of OpenAIRE is used to represent funded projects. Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 18

  19. Research Output Management in PS Higher Education CERIF for OpenAIRE: e.g. Projects Internal Identifier cfProj.cfProjId Start Date cfProj.cfStartDate End Date cfProj.cfEndDate Acronym cfProj.cfAcro Title cfProj.cfTitle Abstract cfProj.cfAbstr Subject cfProj.cfKeyw; cfProj.cfProj_Class Open Access Requirements cfProj.cfProj_Class (at the moment: OA mandated, OA not mandated) Federated Identifiers cfProj.cfFedId.cfFedId (type of identifier is given through cfProj.cfFedId.cfFedId_Class) Relations (e.g.): Product / Dataset cfProj.cfProj_ResProd Person cfProj.Proj_Pers Organisation cfProj.cfProj_OrgUnit Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 19

  20. Research Output Management in PS Higher Education CERIF for OpenAIRE: e.g. Projects Example: https://zenodo.org/record/17065/files/openaire_cerif_xml_e xample_projects.xml Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 20

  21. Research Output Management in PS Higher Education Tool to implement guidelines automatically DSpace-CRIS: https://wiki.duraspace.org/display/DSPACECRIS/DSpace- CRIS+Home DSpace-CRIS is the open-source extension of DSpace for the Research Data and Information Management. Examples: http://ira.lib.polyu.edu.hk/cris/rp/rp00068 http://ktisis.cut.ac.cy/handle/10488/7613 http://dspacecris.eurocris.org/ https://portalrecerca.csuc.cat/ Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 21

  22. Research Output Management in PS Higher Education Practical exercise small groups - 30 minutes 1. Choose a publication here: https://www.openaire.eu/search/find and describe it according to the OpenAIRE Guidelines for Literature Repositories: https://guidelines.openaire.eu/en/latest/literature/index.h tml 2. Choose a dataset here: http://www.re3data.org/ and describe it according to the OpenAIRE Guidelines for Data Archives: https://guidelines.openaire.eu/en/latest/data/index.html Project number: 573700-EPP-1-2016-1-PS-EPPKA2-CBHE-JP 22

More Related Content

giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#