QC: test mapping files for expected databases

bridgedb / BridgeDb

The BridgeDb Library source code

https://bridgedb.org/

Apache License 2.0

28 stars 21 forks source link

QC: test mapping files for expected databases #218

Open DeniseSl22 opened 1 year ago

DeniseSl22 commented 1 year ago

Based on the expected databases in a mapping file (which are different for GeneProtein/Metabolite/Etc.), there should be an output which databases should be present in the mapping files. @egonw @tabbassidaloii @DeniseSl22

egonw commented 1 year ago

expected databases in a mapping file

What do you mean with "expected" here? Expected by whom? Right now, the QC tool expects the same databases in the next release as the previous release. That is in the output.

You mean the BridgeDb Derby schema version, right?

DeniseSl22 commented 1 year ago

Well, apparently that is not a "foolproof" technique (as the issues with the GeneProtein Mapping files have shown). We know which databases we want to have represented in the mapping files, right? So, I think there should be a warning if one of those isn't there.... vs checking the content per database which is being done now.

egonw commented 1 year ago

When you compare with a previous database it already does report which databases are added or removed. That is separate from the differences.

What it does not do, is look at the attributes in both files.