Open will-moore opened 3 years ago
See https://forum.image.sc/t/using-omero-parade-on-dataset-level-and-image-level-omero-tables/50180/7
When loading data for filtering, don't just check for csv or OMERO.tables on the parent Project. Also check on the child Datasets.
The returned JSON would have to indicate which Datasets the filters were coming from. E.g.
/parade/filters/?project=152
"data": [ "ROI_count", "Rating", "Comment", "Tag", "Key_Value", "Table", "idr0021_merged_results.csv", "Batch_ROI_Export.csv", "roi_intensities.csv" "Dataset 123: dataset_values.csv" ]
These would have to be shown in a list that indicates which Dataset they're coming from. And when we load a filter, the URL would also need to indicate which Dataset the table came from (as it would if the Dataset were an orphan)
This issue has been mentioned on Image.sc Forum. There might be relevant details there:
https://forum.image.sc/t/using-omero-parade-on-dataset-level-and-image-level-omero-tables/50180/8
See https://forum.image.sc/t/using-omero-parade-on-dataset-level-and-image-level-omero-tables/50180/7
When loading data for filtering, don't just check for csv or OMERO.tables on the parent Project. Also check on the child Datasets.
The returned JSON would have to indicate which Datasets the filters were coming from. E.g.
/parade/filters/?project=152
These would have to be shown in a list that indicates which Dataset they're coming from. And when we load a filter, the URL would also need to indicate which Dataset the table came from (as it would if the Dataset were an orphan)