Consider ways to collect users' emails

[jpmckinney]

So that we can follow up with them to help promote effective use.

Ideas:

• Subscribe to new publications and/or major updates to the data registry as a whole (can be implemented using Mailchimp or Substack). We can then message the list once a year to ask how they used the registry (via a simple form). We can otherwise aim to send quarterly updates.
• Subscribe to individual publications, e.g. to be alerted about major improvements, newly identified quality issues, etc. This would require handling subscriptions in the app itself. If a user subscribes to multiple datasets, we'd want to send them one combined email, not several. When updating a publication, we can maybe have a form asking if it's a major update, and if so prompt the admin to fill in a bullet-form description. These bullets would then be aggregated into weekly emails. We would add the registry to our GDPR registry of systems.

In both cases, our existing terms of use cover the collection and use of personal information.

[jpmckinney]

@sebasdocp When you have a moment, let me know if you have any ideas for this issue.

[jpmckinney]

https://www.figma.com/slides/0JPBZRvX3V1hh1MKMggbEE/Email-subscr-placement-ideas-in-Data-Registry?node-id=1-55&node-type=slide&t=Ohsy7PUpnoQqiq1d-0