HMC Community Wiki

Introduction

HMC Vision and Mission

Recommendation Tree

• 0. Basic Recommendations and Assumptions
  • B0 Which data to we want to harmonize
  • M0 Use PID Metadata
    • M1.0 use ORCID
      • M1.1 Centers encourage
      • M1.2 Employees maintain
      • M1.3 Data infrastructures implement
    • M2.0 Use ROR
      • M2.1 Centers maintain ROR
      • M2.2 Repos refer to ROR
    • M3.0 Use PIDInst
      • M3.1 Techs Maintain PIDInst
      • M3.2 Researchers refer to PIDInst
      • M3.3 Repos refer to PIDInst
    • M4.0 Use IGSN
      • M4.1 Sample Curators register IGSN
      • M4.2 Repos refer to IGSN
    • M5.0 Use Crossref DOI
      • M5.1 Publication Repos register Crossref DOI
      • M5.2 Repos refer to Crossref DOI
    • M6.0 Use DataCite DOI
      • M6.1 Repos register and refer to DataCite DOI
      • M6.2 Publisher and Authors refer to DataCite DOI
  • I0 Providing of Interfaces and Excange Formats
    • I1.0 Agree on Protocol
      • I1.1 Define REST Interface
      • I1.2 Define OAI-PMH Interface
      • I1.3 Define CSW Interface
    • I2.0 Define Exchange Format
      • I2.1 Use DataCite Metadata Format for Exchange
      • I2.2 Use ISO 19115 Metadata Format for Exchange
      • I2.3 Use schema.org Metadata Format for Exchange
      • I2.4 Use DCAT v3 Metadata Format for Exchange
  • S0 Use of Semantic Resources
    • S1.0 Use Schema.org compliant code with datasets
      • S1.1 Repos implement Schema.org compliant code with datasets
  • C0 Define Data Containers
  • L0 Use Licenses
  • Q0 Implement Quality Information
  • P0 Track Provenance
  • R0 Define Stakeholder Roles
  • V0 Value Data Publications

—-

• Template for recommendations

—-

* Stakeholder Instructions

• for center management
  • for technicians (lab / experiments)
  • for center administration
• for researchers (data producers)
• for data stewards / managers / repositories
• for librarians

* Instructions for Re-using data

Schema.org