## 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](https://gitlab.in2p3.fr/escape2020/wp3/ossr-curation) (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