Suggestion: Update the CodeMeta Metadata Block to add some more structure for machine actionability

[doigl]

Overview of the Suggestion

Actually, the fields MemoryRequirements and ProcessorRequirements and StorageRequirements are just free text fields, what makes it difficult to use them in an automated process to provide the right resources for running a jupyter notebook or a container. Adding subfields to these fields with controlled vocabularies would it make it easier to differentiate between different types and identify the right amount of resources like memory.

Also, as @poikilotherm mentioned, the CodeMeta Scheme is now available in version 3 and it could be worth a look, if we want to also add some of the new fields (code reviews) in the metadata block.

What kind of user is the suggestion intended for?

(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
User, Sysadmin

What inspired this idea?

Two different things:

• We have a dataset, where a user tried to add two different types of memory requirements to a research software (RAM and GPU memory) and we expect this to happen more often in the future
• We want to connect our dataverse instance to a Jupyter Hub as an external tool to allow for an interactive exploration of published Jupyter Notebooks. In this process, we have to decide, which ressources the machine should provide, that will run the notebook.

What existing behavior do you want changed?

Adding structured subfields and controlled vocabularies at least for the fields memoryRequirements, processorRequirements and storageRequirements. Make the memoryRequirements field multiple to allow different types of memory. We are open to discuss changes also for other fields and think about adding new version 3 fields to the block (do we need software reviews?).

Any brand new behavior do you want to add to Dataverse?

Also interesting would be a CodeMeta-Export that then puts the structured fields again together to be compatible with the CodeMeta standard. And we would have to adjust our GitHub-Action to import the information from codemeta files in Git-Repos into Dataverse datasets.