We need three new RESTful endpoint methods to support the ontology search widget.
We need a method each to search for Codes, Concepts, and Terms (a.k.a Item) each of which returns a list of items each containing a code, concept, tty (term type), term and optionally (may be missing or blank in a response) rel (relationship type, like isa or part_of). Additional, optional parameters to constrain the query are 1) relationship types (e.g, isa, or part_of), and/or 2) terminology sets (e.g, UBERON, FMA, CCF). Terms come in two flavors, attached to a code or attached to a concept via pref_term relationship, which for the later case there will be no code information returned (blank code_id, code_sab, code).
The three WS methods are defined as:
{{ontology_url}}/codes/<code>/terms?code_sab=sab1,sab2,sab3&relationship=*[sabA],rel2[sabB],rel3[*]
Example response:
We need three new RESTful endpoint methods to support the ontology search widget.
We need a method each to search for Codes, Concepts, and Terms (a.k.a Item) each of which returns a list of items each containing a code, concept, tty (term type), term and optionally (may be missing or blank in a response) rel (relationship type, like isa or part_of). Additional, optional parameters to constrain the query are 1) relationship types (e.g, isa, or part_of), and/or 2) terminology sets (e.g, UBERON, FMA, CCF). Terms come in two flavors, attached to a code or attached to a concept via pref_term relationship, which for the later case there will be no code information returned (blank code_id, code_sab, code).
The three WS methods are defined as:
{{ontology_url}}/codes/<code>/terms?code_sab=sab1,sab2,sab3&relationship=*[sabA],rel2[sabB],rel3[*]
Example response:{{ontology_url}}/concepts/<concept>/terms?code_sab=sab1,sab2,sab3&relationship=*[sabA],rel2[sabB],rel3[*]
Example response:{{ontology_url}}/terms/<term>/terms?code_sab=sab1,sab2,sab3&relationship=*[sabA],rel2[sabB],rel3[*]
Example response: