Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User preferences #1046

Closed
chouseknecht opened this issue Aug 9, 2018 · 0 comments
Closed

User preferences #1046

chouseknecht opened this issue Aug 9, 2018 · 0 comments

Comments

@chouseknecht
Copy link
Contributor

With the addition of community surveys, we'll be adding more users to Galaxy, because in order to complete a survey, one has to be authenticated. We also need to add features to Galaxy that entice users to visit the Galaxy site more frequently, authenticate, and provide feedback in the form of surveys. In anticipation of this, we need to start working on pages that enable users to manage their preferences. This was always in the backlog of things to do, but now there's more urgency to get this started.

Here are some of the preferences we know we'll need:

Email management

Every user should have a verified email address marked as their primary email address where Galaxy can send notifications. To support this, create a page that let's the user do the following:

  1. Add, remove email addresses
  2. Verify an email address
  3. Mark a verified email as primary

Notification preferences

As a Galaxy user, I want to enable/disable notifications. Example notifications might include the following:

  • Notify me when there is a new community survey for my content
  • Notify me when a new release is available for content that I'm following
  • Notify me when a contributor I'm following adds new content
  • Notify me when an import fails
  • Send me a summary of

API key management

Content creators will need a Galaxy API key in order to run mazer galaxy publish. As a content creator, I should be able to log into Galaxy, and in preferences view my API key and copy it to my local clipboard.

Each user will only have a single API key. The user should be able to generate a new key, which replaces and invalidates the old key.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants