The data.bridgedb.org catalogue of mapping databases (gene.json, other.json and their build configs), which both people and the BridgeDb image build download from.
Last 90 days
No data yet.
What we check
gene.json is valid JSON listing at least 36 organism databases with the required fields, at least 34 webservice-tested, and no date defects beyond the known one.
other.json lists the six shared databases (complexes, genes, interactions, metabolites, pathways, publications), each with a DOI and download link.
The metabolite database listed in other.json is the one the webservice serves.
gene.json.config, which the image build reads, lists exactly the species in gene.json.
gene.json.config names exactly the database files listed in gene.json.
other.json.config names exactly the six shared database files listed in other.json.
The coronavirus catalogue and its build config, also read by the image build, are published and agree on the file.
Mapping files download through the figshare download host the image build uses; the catalogue's own links answering with a bot challenge shows amber.
Every Zenodo and figshare record the catalogue cites is published and still holds its mapping database file.
The bridgedb/data workflow that generates the catalogue web pages last completed successfully.
