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
I need some metadata (gene, reagent, labels for controls, etc.) associated with a well that I couldn't find in the REST API. To get this extra metadata, I usually merge the data from the REST API that describes the layout and the annotations from the data provider (CSV format).
For instance, I can't find the gene, reagent or whether this is a control or not in this query. Could you give me an example of where to find this information using only the API?
Thanks!
The text was updated successfully, but these errors were encountered:
NB: If you load annotations for more than 1 object at a time (e.g. 2 wells in that example) then you'll need to use the link.parent.id data to know which annotation is on which object. If just a single object (e.g. well=67070 then you know all the annotations are on that object.
These /webclient/api/ URLs are not well documented since we've generally treated these as for 'internal' usage by the webclient. But you can find them using the developer tools in your browser (look in Network tab under XHR). E.g. when you click on a Well at http://idr.openmicroscopy.org/webclient/?show=well-67070 you'll see the above URL being loaded.
I don't know if you have a "JSON" plugin/extension for your browser, but the formatting of JSON in the browser makes it much easier to inspect what you're getting from those URLs.
Hi,
I need some metadata (gene, reagent, labels for controls, etc.) associated with a well that I couldn't find in the REST API. To get this extra metadata, I usually merge the data from the REST API that describes the layout and the annotations from the data provider (CSV format).
For instance, I can't find the gene, reagent or whether this is a control or not in this query. Could you give me an example of where to find this information using only the API?
Thanks!
The text was updated successfully, but these errors were encountered: