gammapy: Missing Zenodo community and Codemeta informations for ESCAPE

In order to complete the on-boarding of gammapy on the ESCAPE platform several actions are required :

edit the Zenodo entry to add it on ESCAPE 2020 community see https://escape2020.pages.in2p3.fr/wp3/ossr-pages/page/contribute/publish_overview/ : “Edit your project on Zenodo. Under “Communities” search for “ESCAPE 2020” and add it. Save the record. This will trigger the curation process to the OSSR.” Who can do this ? @Bultako, @adonath, @registerrier, @bkhelifi
on zenodo the codemeta.json should be also uploaded outside of the zip file as in this example: https://zenodo.org/record/5972794#.YinUQhPMI6h
the codemeta.jon should include informations about funder and funding grant as in the example below (from https://zenodo.org/record/5972794#.YinUQhPMI6h)

  "funder":[
    {
      "@type": "Organization",
      "name": "European Commission",
      "@id": "https://doi.org/10.13039/501100000780"
    }
  ],
  "funding": "824064",

could this be also included to the CITATION.cff or have to be added after conversion to codemeta.json ?

the validity of the .json file should be verified with the eossr codemeta validator: https://escape2020.pages.in2p3.fr/wp3/eossr/docstring_sources/eossr_cli/eossr-metadata-validator.html could this be added to the workflow of #3833 ?

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 1
Comments: 23 (22 by maintainers)

Most upvoted comments

gammapy is now fully onboarded

vuillaut on Jun 27, 2022

In order to complete the on-boarding of gammapy on the ESCAPE platform several actions are required :

on zenodo the codemeta.json should be also uploaded outside of the zip file as in this example: https://zenodo.org/record/5972794#.YinUQhPMI6h

This is not necessary anymore. Just add a codemeta.json to your repository and continue with the GitHub-Zenodo integration as usual.

vuillaut on Mar 15, 2022

I have modified https://github.com/gammapy/gammapy/pull/3833 so to comply with requirements on the codemeta.json from the ESCAPE community.

It uses eossr tools to validate codemeta.json and convert into .zenodo.json

The final workflow is now: CITATION.cff -> cffconvert -> fix codemeta.json -> eossr validator -> eossr converter -> .zenodo.json

Bultako on Mar 18, 2022

@vuillaut

I tried to produce a .zenodo.json file with eossr from this codemeta.json file produced with cffconvert. I have the following error trace log

$ eossr-codemeta2zenodo -i codemeta.json 
Traceback (most recent call last):
  File "/opt/miniconda3/envs/gammapy-dev/bin/eossr-codemeta2zenodo", line 33, in <module>
    sys.exit(load_entry_point('eossr', 'console_scripts', 'eossr-codemeta2zenodo')())
  File "/Users/jer/git/eossr/eossr/scripts/eossr_codemeta2zenodo.py", line 66, in main
    codemeta_file, outdir=directory_codemeta, overwrite=args.overwrite
  File "/Users/jer/git/eossr/eossr/metadata/codemeta2zenodo.py", line 311, in parse_codemeta_and_write_zenodo_metadata_file
    meta_converter.convert()
  File "/Users/jer/git/eossr/eossr/metadata/codemeta2zenodo.py", line 254, in convert
    self.zenodo_data = find_matching_metadata(self.codemeta_data)
  File "/Users/jer/git/eossr/eossr/metadata/codemeta2zenodo.py", line 200, in find_matching_metadata
    add_author_metadata(metadata_zenodo, codemeta_json[person_type], person_field=person_type)
  File "/Users/jer/git/eossr/eossr/metadata/codemeta2zenodo.py", line 83, in add_author_metadata
    zenodo_person = parse_person_schema_property(person_property, person_field)
  File "/Users/jer/git/eossr/eossr/metadata/codemeta2zenodo.py", line 47, in parse_person_schema_property
    zenodo_person['affiliation'] = person_property['affiliation']['name']
KeyError: 'name'
`` `

Bultako on Mar 16, 2022