Email report

[sethlbrown]

User can email the report

• When users view the report, they will be able to email themselves a link to the report by clicking on the email report link/icon
• When the email report link/icon is clicked, a modal will appear allowing the user to input multiple email addresses. The modal will also inform the user that the link isn't entirely private.
• The form will have email validation so if the user doesn't input the email address in the correct format, it will throw an error
• Once the user clicks send, a confirmation message will appear in the modal.


[johnwildspring]

Proposed approach:

Given that we chose not to build a back-end system, we can't do link sharing because that requires a back-end system that holds all the data for a session. Instead, we opted for a "savefile". Sharing that file is really easy on the user's part, they simply need to download it, and email it to their colleagues (i.e. this issue is closed). Sharing that file on behalf of the user is harder, because we don't have access to that savefile because we don't have a back-end.

My suggestion is that we continue to use the savefile methodology, unless users feedback says that it's hard to use... then we may consider if its worth building out a back-end system. There are certain benefits to have a back-end system, like being able to see all the data in the big picture and seeing trends in that data. Something that academics might find useful.

Estimate hours (assuming we stick with using the savefile): 0-5 if we want to play around with some extra copy, or add some content that walk users through how to share the file.

Esimate hours (assuming we build out a back-end): TBD