Discussed in #71
Originally posted by hoganwr June 25, 2025
It appears as though the dron-chebi-mapping.csv file is not used in the build process. We should verify it. We should also verify then that all the mappings in the file are now contained in the obsolete.tsv template file. Should both things check out, then we could archive the mapping file. It's too much work to manually keep it up to date if it's not used for anything. Alternatively, we could add an automatic sync to the build process, but I am not sure that would be worth it.
Verified that no scripts, sparql, or Makefiles use the file.
This issue is to attempt a build after renaming the file, then reviewing the build and ensuring nothing breaks or even changes.
Discussed in #71
Originally posted by hoganwr June 25, 2025
It appears as though the dron-chebi-mapping.csv file is not used in the build process. We should verify it. We should also verify then that all the mappings in the file are now contained in the obsolete.tsv template file. Should both things check out, then we could archive the mapping file. It's too much work to manually keep it up to date if it's not used for anything. Alternatively, we could add an automatic sync to the build process, but I am not sure that would be worth it.
Verified that no scripts, sparql, or Makefiles use the file.
This issue is to attempt a build after renaming the file, then reviewing the build and ensuring nothing breaks or even changes.