The UK Research Data Discovery Service
metadata schema
Dom Fripp (Senior curation metadata developer, JISC)
19/05/2016
1
UKRDDS metadata schema - aims
To produce a draft of a metadata schema to fulfil the following
criteria:
› Meet user requirements (based on the evidence provided by user cases
and correlation with common fields in use across the research data
domain).
› Simple enough (in core form) to map onto the CKAN instance that
underpins the portal.
› Based on existing schemas (and good practice) in use across the
research data domain.
› Flexible enough to develop along with the service and user needs.
19/05/2016 2
Fields matching user requirements
19/05/2016 3
Admin Harvest / Ingest Browse Search Reporting Usability Policy
Existing services & schemas
19/05/2016 4
Rationale
»What is mandatory?
19/05/2016 5
»What is common?
UK Research Data Discovery Service
»Findable
› Persistent identifiers accommodated
»Accessible
› Persistent identifiers accommodated
› Access information / protocols harvested
»Interoperable
› Crosswalks to other schemas
› Vocabularies & standards used where possible
»Reusable
› License information harvested
› Rich descriptive metadata also harvested
19/05/2016 6
Schema cardinality
»Mandatory
› Creator
› Title
› Unique resource
identifier
› Date
› Contact
19/05/2016 7
»Recommended
› Keywords
› Publisher
› Project
› Rights
»Optional
› Description
› Subject
› Geolocation
› Format
› ResourceType
› Language
› Related Resource
Mapping OAI-PMH formats
ADS
19/05/2016 8
Dublin Core
MODS
DDI 2.5
GEMINI 2.2
Latest processes
»Formalise schema
development process
»Additional user requirements
(e.g. metadata licenses)
»Richer mappings from schemas
in use at repositories
»OAI-PMH format options
19/05/2016 9

UK Research Data Discovery Service metadata schema

  • 1.
    The UK ResearchData Discovery Service metadata schema Dom Fripp (Senior curation metadata developer, JISC) 19/05/2016 1
  • 2.
    UKRDDS metadata schema- aims To produce a draft of a metadata schema to fulfil the following criteria: › Meet user requirements (based on the evidence provided by user cases and correlation with common fields in use across the research data domain). › Simple enough (in core form) to map onto the CKAN instance that underpins the portal. › Based on existing schemas (and good practice) in use across the research data domain. › Flexible enough to develop along with the service and user needs. 19/05/2016 2
  • 3.
    Fields matching userrequirements 19/05/2016 3 Admin Harvest / Ingest Browse Search Reporting Usability Policy
  • 4.
    Existing services &schemas 19/05/2016 4
  • 5.
  • 6.
    UK Research DataDiscovery Service »Findable › Persistent identifiers accommodated »Accessible › Persistent identifiers accommodated › Access information / protocols harvested »Interoperable › Crosswalks to other schemas › Vocabularies & standards used where possible »Reusable › License information harvested › Rich descriptive metadata also harvested 19/05/2016 6
  • 7.
    Schema cardinality »Mandatory › Creator ›Title › Unique resource identifier › Date › Contact 19/05/2016 7 »Recommended › Keywords › Publisher › Project › Rights »Optional › Description › Subject › Geolocation › Format › ResourceType › Language › Related Resource
  • 8.
    Mapping OAI-PMH formats ADS 19/05/20168 Dublin Core MODS DDI 2.5 GEMINI 2.2
  • 9.
    Latest processes »Formalise schema developmentprocess »Additional user requirements (e.g. metadata licenses) »Richer mappings from schemas in use at repositories »OAI-PMH format options 19/05/2016 9