Instead of #3716

Build a feature for Curators to input specific AAR text for users to see, and be required to fix, while editing their submission.

As prep for this I had a meeting with Laura and Molly to observe how they work and send things back into AAR. My first idea was to create a checklist for problems in the Dryad system and automatically create an email and a case in salesforce based on those. However, curators are very used to the generation of the email in Salesforce, using quick texts in Salesforce, and it's much easier for the curation team to create and modify those quick texts for new issues, so working in the other way—starting a case and an email in Salesforce, then having curators copy text from Salesforce back into Dryad—is recommended.

• Create a more streamlined process to send submissions to AAR (creating a Salesforce case, using this new tool, and changing the status to AAR, all in one workflow) from the activity page
• Curators should be able to add specific text for each section of the submission editor (probably copied from salesforce)
• Users should see this text, as error text, in the submission editor when creating a new version after AAR
• Users should not be able to submit a new version without editing each section that is marked as having an error