Jupyter notebook metadata
-
Concerns the metadata schema -
Existing metadata key -
New metadata key required
Describe the problem or requirement
We need a way to identify the presence of jupyter notebooks in an OSSR record.
Do you have a proposal already?
The proposal being experimented at the moment is to use the keyword jupyter-notebook
.
Another (more appropriate?) way would be to indicate Jupyter Notebook
as a ProgrammingLanguage
.
However, there is no equivalent to ProgrammingLanguage
in zenodo metadata, so the crosswalk would probably fall back to using keywords again.
Discussion
We need to identify the actual need here and what is expected.
- In what context and why ESAP need to identify records with jupyter notebooks?
- Shall we identify records including jupyter notebooks or records that are only a jupyter notebook (+ a running environment)?
- Would a list of files in the record be enough?
- If included in the metadata, shall this be a wide searchable metadata? Or something that can be checked record by record? (--> is it needed in the zenodo metadata or not?)