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
If include=all is done on the /submission endpoint, then the data shall be grabed from the links and put in the outpiut explicilty.
This policy can also be generalized to any "links" that does not return too much data (basically that are about metadata) : metrics, reviews, notes, groups, categories, projects, analytics.
I would keep out the links that can possibly return too much data: submissions, properties, classes, roots, schemes, collections, instances, views
The text was updated successfully, but these errors were encountered:
This is about implementing agents also as links to stay consistent with what was done for other complex objects in the models.
E.g., https://data.agroportal.lirmm.fr/ontologies/AGRO/metrics
For the moment links contains:

And agents are directly included in the submission like this

So a call like this does not work :
https://data.agroportal.lirmm.fr/ontologies/AGRO/agents
If include=all is done on the /submission endpoint, then the data shall be grabed from the links and put in the outpiut explicilty.
This policy can also be generalized to any "links" that does not return too much data (basically that are about metadata) : metrics, reviews, notes, groups, categories, projects, analytics.
I would keep out the links that can possibly return too much data: submissions, properties, classes, roots, schemes, collections, instances, views
The text was updated successfully, but these errors were encountered: