Codemeta server

[ewan-escience]

CodeMeta server

Changes proposed in this pull request:

• Add CodeMeta server that can serve for each public software page the CodeMeta data

How to test:

• docker compose down --volumes && docker compose build --parallel && docker compose up --scale data-generation=1
• Browse http://localhost/software to collect some slugs
• Visit http://localhost/codemeta/some-slug and check that the CodeMeta data corresponds to the software page
• Check for missing data that is crucial for this first version
• Check the README.txt
• The actions can only be tested when merged into main 🙁, but read the files to see if they seem reasonable

Closes #1128

PR Checklist:

• [ ] Increase version numbers in docker-compose.yml
• [x] Link to a GitHub issue
• [x] Update documentation
• [ ] Tests

[cmeessen]

Works as described :+1: Will codemeta be the only metadata format that the RSD will offer in the future? If not, would it make sense to use a more generic route route, e.g. /api/metadata and use arguments to specify the desired metadata format? This could make it easier and more stable to use in case there will be support for other formats in the future.

[ewan-escience]

Works as described 👍 Will codemeta be the only metadata format that the RSD will offer in the future? If not, would it make sense to use a more generic route route, e.g. /api/metadata and use arguments to specify the desired metadata format? This could make it easier and more stable to use in case there will be support for other formats in the future.

Nothing concrete planned, but who knows. I don't think this is part of the API, so how about /metadata/codemeta or /metadata/codemeta/v3, since we use V3 of the spec?

[sonarcloud[bot]]

Quality Gate passed for 'rsd-codemeta'

Issues
3 New issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[ewan-escience]

I changed the path to metadata/codemeta/v3.