Task #10947 (closed)
Enable per-dataset search in OMERO.searcher
| Reported by: | spli | Owned by: | spli |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | Web | Version: | 4.4.9 |
| Keywords: | searcher | Cc: | analysis@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Most of the OMERO.searcher PySLID functions already support a dataset parameter to allow search to be restricted to a single dataset. This should be implemented in the UI.
Change History (2)
comment:1 Changed 11 years ago by spli
- Resolution set to wontfix
- Status changed from new to closed
comment:2 Changed 11 years ago by spli
- Keywords searcher added
- Version set to 4.4.9
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
I don't think dataset filtering should be handled at the level of separate ContentDBs. It means searching a subset of datasets requires loading multiple ContentDBs, and it also means features have to be stored in at least two ContentDBs (the global/group one, and the dataset one, also remembering that images can belong to multiple datasets).
The downside to implementing it at the group/global level is that it's significantly less efficient since the list of datasets associated with an image has to be queries for every potential image in the results. This should be good enough for a demo though, see #11134.
Reopen/comment if you have other thoughts.