Add form

[tinykite]

What this does

Duplicates a portion of the form Perma provides to create an archive of a single link, as a portion of ENG-771. Some pertinent notes:

• This does not attempt to duplicate the behavior of the folder input. This will be handled in the future. For now, all perma archives will be created with the assumption that there is no organization-specific folder chosen for the newly-created capture.
• There is error handling that will show an error has happened if, for example, you try to upload a capture without supplying a link. But the error will generally be generic.
• Additionally, the perma browser tools link has not yet been added.
• For the time being, instead of updating the appearance of the submit button to include a loading spinner and a progress bar, the capture state and upload progress percentage are logged directly to the screen. The capture progress info will not show up until the archive is actively being captured, which should match existing behavior.
  • This will be updated in a future PR
  • The submit button is not disabled by design, per advice from Adam Silver's blog post "The Problem with Disabled Buttons and What To Do Instead" and other sources on form design. Submitting the form should surface an error, although right now it will not be a helpful error just yet.

Screenshots

Ready to handle single url archive requests

Waiting for a response from the /archives endpoint

After the archives API returns a GUID for a link, the state of the archive process will switch to "isQueing"

When a capture is in progress, the page will display the status of the overall archiving process and the progress percent of the capture job specifically

A capture failure

Redirecting to the archive after a successful capture

Testing notes

• I tested this by adding the following to my settings.py:

  from .deployments.settings_dev import *
  CELERY_TASK_ALWAYS_EAGER = False

• To make all captures fail, I added poll_data['status'] = 'failure' above line 314 of the capture job code so that everything looks like failure.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 70.48%. Comparing base (a2fed03) to head (077d758). Report is 30 commits behind head on develop.

:exclamation: Current head 077d758 differs from pull request most recent head efd4405. Consider uploading reports for the commit efd4405 to get more accurate results

Additional details and impacted files

```diff @@ Coverage Diff @@ ## develop #3489 +/- ## =========================================== - Coverage 71.22% 70.48% -0.74% =========================================== Files 48 48 Lines 6512 6594 +82 =========================================== + Hits 4638 4648 +10 - Misses 1874 1946 +72 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[tinykite]

@rebeccacremona can you take another look? Made a handful of fixes, based on feedback.

Additionally — regarding the cookie utility function — let me know if you want to revert that, that's an easy fix too!