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

Feature Request/Idea: Improve Contact Form Email #9185

Closed
qqmyers opened this issue Nov 23, 2022 · 1 comment · Fixed by #9186 or #9643
Closed

Feature Request/Idea: Improve Contact Form Email #9185

qqmyers opened this issue Nov 23, 2022 · 1 comment · Fixed by #9186 or #9643

Comments

@qqmyers
Copy link
Member

qqmyers commented Nov 23, 2022

Overview of the Feature Request The current contact form mechanism has some limitations that QDR and others are interested in removing. These include:

  • Each contact is sent a separate email, so none of them know who else received a request and there is no single group email where a 'reply all' can be done
  • When contacts for a collection or dataset exists, the repository does not receive (via to or cc) an email. For curated repositories, this means administrators are not aware when requests come in
  • When the form emails the repository, it uses the :SystemEmail address. For some repositories, there is interest in making the SystemEmail a no-reply address which would not be useful for support emails
  • In determining the form of the name in a greeting, the current code assumes that any comma in the name string implies a person with a <last name>,<first name> order and it reverses the two parts. This is not correct for names such as 'IBM, Inc.'
  • while there is a Feedback API call, it doesn't work and isn't documented.

QDR will submit a PR with changes addressing these issues. As usual the PR can be adjusted/split as desired.

@pdurbin
Copy link
Member

pdurbin commented Nov 23, 2022

Hmm, overall sounds fine but at a high level I'll just say that if we're changing behavior and we're not sure if people like some of the old behavior, we should probably add new settings as needed.

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