Populate tool source registry

[proycon]

The CLARIAH tool source registry is the input for the harvester. It merely lists endpoints (git source repositories) and service endpoints to search for metadata. The registry is a simple set of configuration files maintained in this git repository: https://github.com/CLARIAH/tool-discovery

Adding new tools is done using a pull request (or direct push) as per the contribution guidelines. Tools from all institutes and work packages should be represented eventually. Currently, however, we're still in the early stages of development.

The below list tracks the progress:

• [x] Add CLARIAH WP3 tools from RUN (including those that moved to KNAW-HuC now)
• [ ] Add CLARIAH WP2 tools from KNAW-HuC
• [x] Add CLARIAH WP3 tools from KNAW-HuC
• [x] Add CLARIAH WP3 tools from Utrecht
• [x] Add CLARIAH WP3 tools from INT
• [x] Add CLARIAH WP3 tools from RUG
• [x] Add CLARIAH WP3 tools from Fryske Akademy
• [ ] Add CLARIAH WP3 tools from DANS
• [ ] Add CLARIAH WP3 tools from MPI
• [x] Add CLARIAH WP4 tools from VU
• [ ] Add CLARIAH WP5 tools from B&G
• [ ] Add CLARIAH WP6 tools from KNAW-HuC / DANS

[proycon]

A few tools have already been added by others; this is a request to all partners to just add their tools to the tool source registry now and check if the already existing metadata descriptions of yours tools (i.e. in files like setup.py, README.md, github descriptions, package.json etc) are accurate and up to date. At this stage, you do not need to bother to add a custom codemeta.json yet (but you may if you want to experiment with it already).

We want to see to what extent the automatic harvesting already suffices. In the next stage, partners will be requested to add CLARIAH-specific metadata.

The result of all harvesting can be seen on https://tools.dev.clariah.nl/ . Eventually all CLARIAH tools must be in this registry.