Email notifications documentation
UPDATED by @lathrops1 20211024
USER STORY
Per diagrams for each epic / features and other Documentation, supported Phase 1 users (Bookshelf staff, Org Admin, Editors, PDF2XML taggers) need to be notified the status of their actions through the flow of their content from submission to release to public access on Bookshelf so they can track and manage it in a timely fashion, and those notifications should provide enough details to understand what content the notification refers to, its status, what they need to do about that content, and how / where to easily find information how to do that.
TECHNICAL PROPOSALS
If text changes to the email itself are required, please add the text to the linked Google document in the correct section, using tracked changes (suggesting mode)
Email notifications dev tracker
ACCEPTANCE CRITERIA
-
Notifications are sent to the correct user(s) who need to know the status / do something per the provided user / email details -
Notifications have clear subjects that include details about what the content is and its status and any action needed -
Notifications have clear descriptions in the email body of what has / needs to be done -
Notifications provide sufficient details to easily find the content, including IDs to easily search for it and direct links to directly access the content / details