Codemeta to SSHOC Open Marketplace
This is a converter to transform data from codemeta (as used by https://tools.clariah.nl) for ingestion into the SSHOC Open Marketplace by communicating via their API.
Installation
Run (preferably in a Python virtual environment):
pip install codemeta2mp
Usage
If you already have a codemeta.json file, just run codemeta2mp --baseurl http://localhost:8080 --username Administrator --password q1w2e3r4t5 codemeta.json to upload it to the SSHOC marketplace (the default credentials and URL are for a local development instance):
- Find the tool you want to convert on https://tools.clariah.nl/ (e.g. https://tools.clariah.nl/frog
- Run this on on it:
curl --header 'Accept: application/json' https://tools.clariah.nl/frog/ | codemeta2mp --baseurl http://localhost:8080 --username Administrator --password q1w2e3r4t5 -
Considerations & Discussion
A conversion from one vocabulary to another always presents some challenges, as terms do not always map exactly one to one. Some decisions and assumptions have to be made by the converter.
The following were made for the conversion from codemeta (as used by the CLARIAH-NL Tools) to the sshoc open marketplace. If any of the SSHOC/EOSC SKOS terms are used directly in the codemeta, then they will of course be preserved as-is.
- SSHOC Invocation Type does not cover all we have in our Software Types, some mappings are sub-optimal.
- EOSC Resource Technology readiness levels go from 1-9, CLARIAH's go from 0-9. We map both our 0 and 1 to their 1.
- EOSC Lifecycle status values we derive from our use of Repostatus for
codemeta:developmentStatus(to indicate maintenance status) and TRL. codemeta:issueTrackergets mapped to SSHOC Marketplace'shelpdesk-url- Software as a Service by definition has at least two
accessible_atURLs after conversion. One pointing to the source code, and one to the service. The marketplace doesn't really have the mechanism for fine-grained control to distinguish the two yet keep the strong relation. - We both use Tadirah for
schema:applicationCategoryakaactivity. This maps one-to-one. - Marketplace has an Austrian bias and uses ÖFOS 2012. Österreichische Version der 'Fields of Science and Technology (FOS) Classification' for
disciplinewhereas CLARIAH-NL has a dutch bias and uses NWO's classification (inschema:applicationCategory. A conversion for this still needs to be established.
Metadata
Release files for codemeta2mp 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| codemeta2mp-0.4.0.tar.gz | 24.2 kB | Without provenance | Details for codemeta2mp-0.4.0.tar.gz |
Release files / codemeta2mp-0.4.0.tar.gz
| Download URL | codemeta2mp-0.4.0.tar.gz |
|---|---|
| Size | 24.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eaddd1ef5a668402b07fba32ec67b5f362a8b47d461081663287defaaf6d58df
|
|
BLAKE2b-256 checksum How to use checksums |
dd8db1c3823d745422a236d8d65edc657f208ec9f44d21d0bb02e1acb25284e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for codemeta2mp 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.