Task #7966 (closed)
Opened 8 years ago
Closed 7 years ago
Resolve namespace table
| Reported by: | ajpatterson | Owned by: | ajpatterson |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | Specification | Version: | n.a. |
| Keywords: | dbmodelcompare, schema | Cc: | jburel, jamoore |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
namespace is a distinct table in DB but in the Model is just an attribute on annotation nodes. In the DB it is linked to the annotation table.
Change History (5)
comment:1 Changed 7 years ago by ajpatterson
comment:2 Changed 7 years ago by ajpatterson
- Milestone changed from OMERO-Beta4.4 to Unscheduled
- Sprint 2012-02-14 (8) deleted
comment:3 Changed 7 years ago by jburel
- Cc jburel jmoore added
Currently the table is only used for roi. This should be available for anything to allow creation of smart folders from name space.
Note that the FLIM work and the keywords associated is no longer used.
comment:4 Changed 7 years ago by jburel
See #4789 for various tickets related to name space and keywords possible usage
comment:5 Changed 7 years ago by ajpatterson
- Resolution set to fixed
- Status changed from new to closed
Following ROI discussion namespaces will be changed to namespace in roi table and no longer be a list, just one item. Work on Story #8084
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Namespace table is not heavly used. It is mostly used by Donald's FLIM code. It is not the same as the namespace in the model on attributes. A general re-think is needed. Not a priority for 4.4