Expired
Milestone expired on Feb 6, 2022

Sprint: Codemeta checker

Goal

  • Create a checker for codemeta entries

Here from D3.7 the meta data to check:

Required

  • Title
  • Authors: list of authors
    • Contact (maintainer):
    • name: could be a person or an entity
    • email or other contact channel (not anymore)
  • Short description of the software/service
  • License
  • Version

Recommended

  • Provide a persistent identifier (such as a Digital Object Identifier (doi), if already available)
  • Publication date (if already published elsewhere)
  • URL to the (live) development repository
  • Type of publication: source code, compiled binaries, container, image
  • Grant/funding
  • Contributors
  • References
  • Programming language
  • External dependencies (including matching versions)
  • Operating system
  • Compilation environment
  • Hardware requirements
    • General use case (HPC, server, local desktop)
    • CPU, RAM, HDD/SSD requirements
    • GPU requirements
    • FPGA
  • Data Type (inputs/outputs)
  • Access
    • Open
    • Closed
    • Restricted
    • Embargoed
  • Documentation language
  • Keywords: to be selected in a defined list of keywords, see below

Current keywords list

  • CTA
  • LSST
  • LOFAR
  • SKA
  • EGO-Virgo
  • KM3NeT
  • ELT
  • EST
  • HL-LHC
  • FAIR

Minimal information for Zenodo

  • publication date
  • title
  • authors
  • description
  • access right: open-access or embargoed or restricted
    • raise a warning for embargoed and restricted to ask for justification
  • license --> open-source SPDX: https://spdx.org/licenses/

Minimal information for the OSSR

  • maintainer
  • funding (ESCAPE)
  • keywords

Team

Working plan

Plan:

  • start with validator:

    • check if required metadata has a value
    • warning if recommended metadata has no value

  • dev in the eossr

    • command-line tool to output errors and warnings

  • use validator in the curation process

  • provide an online generator