Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
Documentation
Documentation
  • Project
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 2
    • Issues 2
    • List
    • Board
    • Labels
    • Milestones
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • snac
  • DocumentationDocumentation
  • Issues
  • #9

Closed
Open
Opened Oct 19, 2015 by Tom Laudeman@twl8n 
  • Report abuse
  • New issue
Report abuse New issue

policy for data embargo

The technical and policy teams need to discuss data embargo in order to provide guidance to the tech team on one or more likely use cases for embargo and the expectations of how embargoed data will be accessed.

This needs to go on the agenda for the Oct 28 2015 meeting.

Is an embargoed record "locked"? Is the embargo "owned" by a specific user? If the answers to both questions are yes, then embargo fits perfectly as a stage (that is: a workflow stage). Embargo is not permanent, which is one of the primary ways it differs from delete.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
0
Labels
None
Assign labels
  • View project labels
Reference: snac/Documentation#9