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
Each API will have their own mechanisms for restricting search results. It makes sense for us to develop a flexible template type string that would allow us to embed (and easily update) search scaffolding as part of the model/database that the frontend can use with standard text-substitution mechanisms to build the appropriate query string.
I can imagine that we may also end up needing to capture additional details that only apply to certain types of searches. For instance, if you only want to include terms that fall under a particular node inside a hierarchically oriented terminology.
The text was updated successfully, but these errors were encountered:
Each API will have their own mechanisms for restricting search results. It makes sense for us to develop a flexible template type string that would allow us to embed (and easily update) search scaffolding as part of the model/database that the frontend can use with standard text-substitution mechanisms to build the appropriate query string.
I can imagine that we may also end up needing to capture additional details that only apply to certain types of searches. For instance, if you only want to include terms that fall under a particular node inside a hierarchically oriented terminology.
The text was updated successfully, but these errors were encountered: