New editor should require submitter email addresses

[jagoldstein]

how are we to write back to submitter's if we don't have his/her email address? this field should be required for at least one personnel or organization

[dmullen17]

This would be really great to have, I've spent 30 minutes looking for an email address before.

[jagoldstein]

I agree with @dmullen17 . I easily spent a half hour trying to track down a submitter's email address yesterday so that I could add it as a "Requestor" in RT. I am still not confident I even obtained a good address to contact the submitter.

Often submitter's enter very sparse metadata, occasionally omitting all email addresses. Additionally, many people intentionally hide their email address from being listed publicly. Even some private universities' websites do not publish students' email addresses (only those with university login credentials can access student directories).

At least one contact email should be required by the editor. Otherwise, submissions may sit as private indefinitely as we cannot contact the submitter. It would be great to prioritize this.

[jeanetteclark]

I'll add a plus one to this...it is MUCH harder to retrieve submitter email addresses than you would think since ORCID doesn't expose them. Most of the time a page like this is all we have to go off of:

It is definitely not uncommon for us to spend 20 minutes trying to track down the best email address for a submitter.

[mbjones]

We have a need to switch from using the ORCID public API for authenticating to using the ORCID member API. This switch would allow some new features, one of which is that we could ask the user for permission to view their email from their ORCID profile as a condition of logging in, so we would always have an email for them. I think that would solve this immediate request. This is a DataONE authentication change, described here: https://redmine.dataone.org/issues/8746

[laurenwalker]

Removing the 'blocker' label since this isn't truly blocking any work - will replace with a priority label.

[laijasmine]

We would love to see this feature up soon. It is an issue that still comes up on a regular basis.

[jeanetteclark]

Yup I agree. The team has wasted untold hours over the years trying to figure out how to contact people.

[laurenwalker]

That's not good! Ok, I will figure out a way to require this that makes the most sense and get it in soon.

[jeanetteclark]

bump for this issue. A user just had a failed submission, and I cannot figure out how to contact them. If the email address field were required I would have already emailed them - instead I'm going to keep looking and/or hope they email us. Either way, I'm not having a good time, and I'm sure the user on the other end isn't either.

[laurenwalker]

Ok, thanks for letting me know. I will take a look at this.

[mbjones]

Reiterating my earlier comment (#545 (comment)), this might be really easy and require almost no UI changes on our part if we switch to using an ORCID login with a member account where we can require the email and name attributes.

[jeanetteclark]

Hi @laurenwalker - just giving this another bump!

[laurenwalker]

I've implemented this feature in MetacatUI by adding the ability to require the Contact email in the editor. (other EMLParty fields can be required, too). I created an issue in the d1_portal_servlet repo to get the email from the ORCID API when users login: DataONEorg/d1_portal_servlet#3

[laurenwalker]

It is my understanding from the ORCID API documentation that we can request the email from users when they login via ORCID, but we cannot require it since it is part of the ORCID Trusted Data. So we cannot rely on the ORCID API implementation as a way to require email addresses for each submission. However, I still think it will be useful to try to get that info upon login anyway.