Tools ecosystem processes

[hmenager]

This table is meant to document the various processes (workflows) taking place in this repository:

Source name	Import	Validation	Cross-link	Report	Publish
bio.tools	biotools-import.yaml	biotools-testrunregistry.yml	doi-load.yaml	biotools-pullrequest-analyzer.yml	bioschemas-build.yml bioschemas-build-dump.yml
bioconda	bioconda-import.yaml
biocontainers	push from biocontainers
OpenEBench metrics	openebench-git-populous
Debian Med	debianmed-import.yml	debian-yaml-validator.yaml	doi-load.yaml
BIII	biii-import.yaml				biii-import.yaml
Global				report.yaml

[hmenager]

@OlegZharkov @bgruening can you provide the bioconda + biocontainers information?

[hmenager]

@redmitry from what I understand openebench-git-populous only sends the metrics data. Do you have another script to send the openebench data themselves?

[redmitry]

@redmitry from what I understand openebench-git-populous only sends the metrics data. Do you have another script to send the openebench data themselves?
No. The reason is that OpenEBench tools collected from bio.tools, bioconda and some time ago galaxy. That would be a duplication (?).
I have a code to import bio.tool -> git:
https://gitlab.bsc.es/inb/elixir/tools-platform/biotools-git-populous

There is no problem to push OpenEBench tools to the github, but its update supposed to be done on the over direction (from conda/biotools files).

Cheers,

D.

[hmenager]

Thanks for the clarification @redmitry. Indeed, if you have no other source for metadata than bio.tools and bioconda, then there is probably no need to document what is probably a "one-time" import.