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
In our scenario, the API will be shared across the organization and not specific to our project. Consequently, when using the endpoints /artefacts and /records it would provide results from every semantic artefact (SA) defined in the organization. This is fine, but a typical use case would be that a user only wants to retrieve results tied to a specific project in the organization.
It would be great if it was possible filter the results based on some grouping of the SAs, for example by using an additional query parameter in the call to these endpoints. How would this affect the compliance with the MOD-API standard?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
In our scenario, the API will be shared across the organization and not specific to our project. Consequently, when using the endpoints /artefacts and /records it would provide results from every semantic artefact (SA) defined in the organization. This is fine, but a typical use case would be that a user only wants to retrieve results tied to a specific project in the organization.
It would be great if it was possible filter the results based on some grouping of the SAs, for example by using an additional query parameter in the call to these endpoints. How would this affect the compliance with the MOD-API standard?
Beta Was this translation helpful? Give feedback.
All reactions