Show request to claim certificate when not the owner.
Email should definitely be sent async

Otherwise timeouts on the smtp server can bubble up to the user.
Save record to database and use id as parameter for queue

This is less data to serialize and there is now a record of who took the transfer.
Put the owner changing responsibility on the dataset model
Use active support method for non-nil check
In development log email to stdout from jobs worker
Test the actual exploit the code is trying to protect from
Create claim model
Add certificate claim model

I didn’t do this as an extension of transfer as the switching of
logic would’ve lost clarity and there is no reason to limit claims to
a one to one relationship like there is with owner initiated transfers
Render modal content outside most of the DOM

To remove interference from other css styling. As it’s absolutely positioned it doesn’t matter where in the DOM it is.
A factory to build a complete claim model
Display outstanding claims and approve/deny them

If user is admin then they can see all claims not just
ones against datasets they own.
Send emails for notifying of claims

Currently only certificate@theodi.org will be notified of claims. Unset Claim::DELIVERY_ADMIN_OVERRIDE to change this
Undo enviornment changes in test
This phrases weren’t used.
Don’t imply success on something that is just a request
Add a translation for claim this certificate button

Hopefully with the tone that leads the user to follow it if it applies to them.
Spell trasnfer correctly
Change copy for claiming

Trying to be consistent about what the user owns and what the certificate is.

The dataset could be theirs. The certificate is ODI’s but applies to their data and they get to control the outcome of it by answering questions about the dataset.
Transfer is already loaded so use class

The object is already loaded and in the background worker, so attempting to optimise by only passing the id around is pointless.