-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
create a codemeta examples dataset with examples from representative communities
- identify candidate set from each registry / repository
- generate codemeta or pull existing codemeta
- "grade" codemeta (manually?)
- include alternative representations (e.g., datacite.json?)
- include context in the README.md file
- organize examples in an
examplesdirectory, with a directory per registry / repository e.g.,
examples
├── all.csv
├── ascl
├── comses
│ └── artificial-anasazi
│ ├── README.md
│ └── codemeta.json
├── csdms
├── rsd
└── zenodo
provide guidance on how to consistently map somewhat unclear terms:
- peer reviewed -> Review / reviewBody / reviewPart
- dependencies / softwareRequirements
- related publications
- preferred citation
- narrative documentation
- others?
should we recommend including fields with no corresponding codemeta term in a schema.org additionalProperty?
examples from CSDMS:
- https://github.com/CUAHSI/FAIRRS-Evaluation/blob/develop/crosswalks/codemeta_csdms.md
- https://github.com/CUAHSI/FAIRRS-Evaluation/tree/develop/schemas/csdms/codemeta
examples from Caltech:
- https://zenodo.org/records/15428136/export/codemeta
- https://github.com/caltechlibrary/iga/blob/develop/codemeta.json
Examples from OSSci Innovation Sprint:
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels