User Story #1636 (new)
Opened 14 years ago
Permissions and rights management
| Reported by: | omero | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | General | Keywords: | n.a. |
| Cc: | Story Points: | n.a. | |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
Permissions and rights management would expand the potential audience for Omero and its usefulness to current users. It's critical for libraries and repositories, for instance, but also for anyone managing clinical or otherwise restricted data. Even ordinary labs still handle copyright and licensing, and I'm sure they would welcome the ability to do that in Omero.
Increased granularity in permissions management is needed to handle:
- The restrictions in between simply public or private
- Managing legal copyrights retained or licenses
- Managing handling restrictions such as gov classification (Top Secret) or HIPPA
- Encryption needed in some cases
- I don’t have a great handle on where the encryption needs to happen—to the file, to the entire software installation, to the transmission of the data…
I have a proposed permissions and rights additions to the data model in OME tickets, and I've attached here some mocked-up examples of what a management interface for the software might look like. Changes can be added incrementally--it doesn't all need to get done at once.
Attachments (4)
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
A copyright management screen