Task #10741 (closed)
Opened 11 years ago
Closed 8 years ago
Storage of content database
| Reported by: | spli | Owned by: | spli |
|---|---|---|---|
| Priority: | minor | Milestone: | Partner |
| Component: | General | 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
The OMERO.searcher ContentDB is currently stored outside the OMERO data-store so is not subject to the permissions model. On the other hand this is not necessarily a bad thing as far as searching other people's data is concerned, since if you're alowed to read someone's data there's no point in recalculating features for the same image. This could get complicated.
The other question is whether to use the current ContentDB Python pickle file, or OMERO.tables (though this will mean you can only save features to your own feature table even though you can read other users').
Change History (4)
comment:1 Changed 11 years ago by spli
- Milestone changed from Unscheduled to 5.0.0
- Version set to 4.4.9
comment:2 Changed 11 years ago by spli
- Keywords searcher added
comment:3 Changed 10 years ago by spli
- Milestone changed from 5.0.0 to Partner
comment:4 Changed 8 years ago by jamoore
- Resolution set to wontfix
- Status changed from new to closed
Cleaning up searcher backlog.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
This should eventually be handled by OMERO.features.