Task #1767 (closed)
Opened 14 years ago
Closed 14 years ago
Permissions : Enumerations should be global objects
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | major | Milestone: | OMERO-Beta4.2 |
| Component: | Security | Version: | 4.1 |
| Keywords: | n.a. | Cc: | atarkowska, jburel, cxallan |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
This is a part of ticket:1434
Since #1434 restricts which objects can be loaded into a particular group, enumerations would either:
- need special handling
- need to be global, system types
- need to be hard-coded (not with tables)
Special handling is, in general, a bad idea. Hard-coding, though the appropriate long-term solution, requires a significant rework and therefore can't be achieved for 4.2. Instead, all enumerations will be made global for this release.
Change History (3)
comment:1 Changed 14 years ago by jmoore
- r6024 Global enumerations (no DB upgrade yet)
comment:2 Changed 14 years ago by jmoore
comment:3 Changed 14 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
Done, but will still needs work as a part of #1750 (db upgrade)
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
