(research) Email form definition json file on submission from new content registration UI
Background
The new content registration UI will use the synchronous deposit API.
The synchronous deposit API has emails disabled.
If users want to save/edit a submission in the content registration UI, they must do so on their local machine. This takes the form of a json file that contains both the form definition (what the form fields are) and the form contents (as entered by the user). The user can save the json file locally and upload to the Content Registration UI to edit/redeposit in the future.
It is desirable to email the json file to the user on submission, much like we email the submission record to users when they submit via the Web Deposit Form. Is this feasible? How could this be accomplished? Are there better solutions?
Observed behavior
Expected behavior
How urgent
Definition of ready
-
Product owner: @SaraBowman -
Tech lead: @afandian -
Service:: or C:: label applied -
Definition of done updated -
Acceptance testing plan: -
Weight applied
Definition of done
-
Unit tests identified, implemented, and passing -
Code reviewed -
Available for acceptance testing via a staging URL, or otherwise -
Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed -
Knowledge base reviewed and updated -
Public documentation reviewed and updated -
Acceptance criteria met -
Assessment of feasibility and outline of steps needed to implement (if feasible), or alternative solutions (if not feasible)
-
-
Acceptance testing passed -
Deployed to production
Notes
Edited by Sara Bowman