You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been manually editing the prefix.csv files in my semsql installation to handle prefixes that are not already defined for ontologies we are currently developing. However, I'm uncertain how best to handle the KEGG prefixes given their shared resolution.
Any suggestions or guidance on a robust solution for this issue would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
KEGG Ontology Prefix Handling
We are currently using two KEGG prefixes:
Both of these prefixes resolve to the same base URL:
https://www.kegg.jp/entry
. For example:I have been manually editing the
prefix.csv
files in my semsql installation to handle prefixes that are not already defined for ontologies we are currently developing. However, I'm uncertain how best to handle the KEGG prefixes given their shared resolution.Any suggestions or guidance on a robust solution for this issue would be greatly appreciated.
The text was updated successfully, but these errors were encountered: