Feature Description
We wish to get filtered taxonomies (e.g. data_taxonomy ) by API calls.
Problem Statement
Currently, RESTful APE always returns the full data_taxonomy which also includes plain inputs and outputs, e.g. Over-Representation Data_p which is a direct substructure of Over-Representation Data. However, the frontend does not use the plain variant and we currently have to filter those out manually which definitely reduces the performance on the frontend side.
Proposed Solution
The best solution would be to implement additional filter parameters e.g. for the data_taxonomy like for the attributes id and/or label such as:
id neq <string>id endswith|beginswith <string>id !endswith|!beginswith <string>
Alternatives Considered
Alternatively, to tackle pathological cases, we could just add boolean switches to the API calls such as include_plain being true by default.
Use Cases
One use-case arose in Workflomics-Frontend and the issue was solved rather by a workaround, i.e. filtering there.
Additional Context
Feature Description
We wish to get filtered taxonomies (e.g.
data_taxonomy) by API calls.Problem Statement
Currently, RESTful APE always returns the full
data_taxonomywhich also includesplaininputs and outputs, e.g.Over-Representation Data_pwhich is a direct substructure ofOver-Representation Data. However, the frontend does not use theplainvariant and we currently have to filter those out manually which definitely reduces the performance on the frontend side.Proposed Solution
The best solution would be to implement additional filter parameters e.g. for the
data_taxonomylike for the attributesidand/orlabelsuch as:idneq<string>idendswith|beginswith<string>id!endswith|!beginswith<string>Alternatives Considered
Alternatively, to tackle pathological cases, we could just add boolean switches to the API calls such as
include_plainbeingtrueby default.Use Cases
One use-case arose in Workflomics-Frontend and the issue was solved rather by a workaround, i.e. filtering there.
Additional Context