Task #3751 (new)
Opened 9 years ago
Last modified 7 years ago
Data Permissions: Viewing
| Reported by: | ajpatterson | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | Specification | Version: | n.a. |
| Keywords: | schema | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Moved from http://www.ome-xml.org/ticket/86
The schema should store information that helps administrate permissions:
- Workplace preferences -minor
- For OME-XML, what should be recorded is probably a just a choice between Public or Restricted, with Restricted requiring specific user ids.
- Management can be made a lot easier by the software, which could overlay options like: Anyone, Anyone in my institution, Anyone in my lab, Only me, or Custom group. You should probably be able to manage and reuse groups you have created, and so one.
- For OME-XML, what should be recorded is probably a just a choice between Public or Restricted, with Restricted requiring specific user ids.
- Legal requirements -trivial
- Embargoes from Journals
- Dates of embargo
- Authority that requires it
- It would be great if the software could automatically adjust the permissions on this when the embargo ends.
- Dates of embargo
- HIPPA
- Government Classification Status
- Court-Sealed Docs
- Encryption is legally required for some of these things, as well. Software would need to support appropriate encryption options for files and file transfer, etc.
- Embargoes from Journals
Changed by andrew
Restriction is information not control.
Change History (3)
comment:1 Changed 8 years ago by ajpatterson
- Keywords schema added
comment:2 Changed 7 years ago by ajpatterson
- Component changed from Model to Specification
- Owner set to ajpatterson
comment:3 Changed 7 years ago by ajpatterson
- Owner ajpatterson deleted
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.