While the typical use case is to use an ontology or vocabulary in which AC is easily available as a service (OLS, Monarch, GO), there are various occasions where we need to be able to AC based on a local file. This is either if the vocabulary isn't published, or if local modifications are to be made.
With DeskPhenote this was done by having the config point at either a local obo file or one bundled with phenote.
Here the format is obographs json (it's very straightforward to turn an obo or owl file into this format). This could be directly loaded in memory. @balhoff - what was the name of the pure-js lucene engine?
While this could be used to support microvocabularies I think this is a separate concern. These would be small subset lists in the config file.
balhoff
commented
7 years ago
While the typical use case is to use an ontology or vocabulary in which AC is easily available as a service (OLS, Monarch, GO), there are various occasions where we need to be able to AC based on a local file. This is either if the vocabulary isn't published, or if local modifications are to be made.
With DeskPhenote this was done by having the config point at either a local obo file or one bundled with phenote.
Here the format is obographs json (it's very straightforward to turn an obo or owl file into this format). This could be directly loaded in memory. @balhoff - what was the name of the pure-js lucene engine?
While this could be used to support microvocabularies I think this is a separate concern. These would be small subset lists in the config file.