Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
eossr eossr
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 26
    • Issues 26
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Docker-in-Docker (DinD) capabilities of public runners deactivated. More info

  • ESCAPE2020
  • WP3
  • eossreossr
  • Issues
  • #71

Closed
Open
Created Jan 14, 2022 by Vuillaume@vuillaumeOwner

CodeMeta checker / validator

Describe the feature you would like to see in eossr

It has been discussed during WP3 calls that a CodeMeta validator for the OSSR would be useful.

Pinging @tacke @kettenis @garcia for discussion - I'd love to have your feedback.

In what context do you need this feature?

  • CodeMeta to Zenodo crosswalk
  • uploading record (TBD)
  • OSSR curation process (automatize and thus simplify part of the curation)

Expected behaviour?

Checks that the mandatory metadata are provided as well as the validity of their value

Possible way(s) to implement

CodeMeta has an online validator at: https://codemeta.github.io/codemeta-generator/
code implementation in javascript: https://github.com/codemeta/codemeta-generator/

It would be best to leverage it. By order of personal preference, I see:

  • implement a light python checker, still relying on providers to have done their job (using the generator and/or the online official validator)
  • using the code from the codemeta generator by calling it directly
  • submodule the generator and tweak it if needed
  • import the codemeta validator in python with a javascript wrapper
  • reimplement the all thing in python in the eOSSR

Note also that this is useful only if it simplifies our life and actually saves us time. A visual inspection of the codemeta file during the curation takes 20s at most, so implementation of a checker should stay rather simple and fast.

MetaData CodeMeta checker discussion

Assignee
Assign to
Sprint: Codemeta checker
Milestone
Sprint: Codemeta checker (Past due)
Assign milestone
Time tracking