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
For /catalog endpoint. The spec for disease and disorder filter have been defined by OntologyRequestArrayFilter, that only uses id property. However, in order to be capable of detecting disease information from SPARQL, its mandatory to use AlphanumericRequestFilter like the rest of filters.
The table from documentation defines this AlphanumericRequestFilter structure, but later, the exemplar request/response is described by OntologyRequestArrayFilter
The text was updated successfully, but these errors were encountered:
Dear Pablo, I've taken a close look at the documentation you referenced, both the table and the example, and it seems that both of them describe the use of an Ontology Filter for Disease or Disorder.
For your convenience, I've also included a snippet from the specification that outlines the structure for /catalogs requests:
The CatalogRequestFilter can be either a CatalogAlphanumericRequest or OntologyRequestArrayFilter. Furthermore, when we delve into the details, it becomes apparent that the OntologyRequestArrayFilter can encompass either a string value or an array of string values:
To address the issue of distinguishing between a correct filter for Disease and a potential false positive filter, we have the filtering_terms informational endpoint, which provides valuable insights into filter usage.
For /catalog endpoint. The spec for disease and disorder filter have been defined by
OntologyRequestArrayFilter
, that only usesid
property. However, in order to be capable of detecting disease information from SPARQL, its mandatory to useAlphanumericRequestFilter
like the rest of filters.The table from documentation defines this
AlphanumericRequestFilter
structure, but later, the exemplar request/response is described byOntologyRequestArrayFilter
The text was updated successfully, but these errors were encountered: