Objective

To implement support for some sort of "embargo" period for requests.

Context

One feature that was added on top of the original fork was an embargo period. As noted in the website's FAQ:

Yes, we recognize that reporters and others may have an interest in not immediately disclosing a request and any documents received in response to that request. You control whether a request and any government response is released publicly for up to 1 year after the request. When making the request, uncheck the box stating “This request is public.” If you do not uncheck the box when making the request, your request will be publicly disclosed on the Internet as soon as it is made.

We should investigate whether or not this feature is something we want to reimplement (basically does the above reasoning still apply), and whether or not we want to take a more granular approach (embargo requests for 1 week, 1 month, ...etc).

Tasks

• Figure out the granularity of embargo periods we should support
• Implement support for the embargoing of requests

Success Criteria

Requests can be successfully embargoed.

Related Items

Parent Epic: #50

• Where the Celery tasks are defined: https://github.com/CodeWithAloha/uipa/blob/73cc661c80d87fd9640d92ce35370ad98fa354eb/uipa_org/celery.py