How do you manage invalid email account?

[Guang Yuan, NTU Singapore]

Hi all,

In my university (NTU), our Dataverse installation authenticates users using Shibboleth log-in.

Once a user leaves NTU, his/her email account will be no longer valid, and thus can't log into our Dataverse system anymore. They also lose access to their datasets, unless we create a non-NTU account for them. 

Our concern is that people who are interested in their datasets can't reach them. Coz the "Contact" button actually goes to invalid account. 

Worse still, we aren't involved in this process. It really causes a bad user experience.

Wondering how do you deal with this issue?

[Philip Durbin]

Hi! Thanks for explaining this situation on the community call the other day. When I sent around the notes for that call, Philipp from DataverseNO replied* with the following:

(Schusie) People leaving NTU, email under "contact" goes to invalid account.

(Philipp) We also have been discussing this issue, and are considering to add by default also the contact address of the repository to all datasets.

That doesn't seem like a bad idea to me.

My understanding of the "Contact" button is that it isn't tied to accounts at all. It's just a metadata field with a bit of validation to make sure a valid email address is entered. That means that it isn't tied to account notifications (the ones in the top right corner). It's more of a "fire and forget" sending of an email. So there's no workflow, if you will, built in to manage messages that have been sent to dataset contacts. There's no tracking that I know of, apart from perhaps a line in a log somewhere. If we really want a better user experience around contacting dataset owners, maybe messages should go into a queue or something. Just some idle thoughts. :)

Thanks,

Phil

p.s. With regard to people leaving your institution, I'd feel remiss if I didn't mention that a self-described Dataverse greenhorn popped into IRC the other day asking about simultaneous use of multiple login systems:

"For now I just want to check how does dataverse login system works in order to try to disign/enable simultanuous use of multiple log-in systems. I'm dataverse greenhorn, but i got a task to do so, so i need to do some research :)"

http://irclog.iq.harvard.edu/dataverse/2020-01-30#i_117329

* https://groups.google.com/d/msg/dataverse-community/jm9hMvJTChU/X6-g6VBfBwAJ

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/adccf8e1-b9de-418b-a083-a72dc76dc5cf%40googlegroups.com.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[Sonia Barbosa]

Hello again!

What we do when someone has moved on to another University etc...is we have them create a new account with their new email and we give them administrative access on the permissions page with their new account. I normally leave the old account on the permissions page as well as sort of a record for us on their previous administrative affiliations.

I suggest this workflow to your group. They will normally contact you if they need further access so you can update both the permissions page and the "contact" box in the metadata of the dataset and dataverse, with their new information.

[Guang Yuan, NTU Singapore]

Thanks Sonia! This sounds like a do-able workflow! We will look into it.

[Guang Yuan, NTU Singapore]

Thanks Philip for bringing up DataverseNO's experience and refreshing my memory. And sharing about discussion on simultaneous use of multiple login systems, which seems can contribute to our team's discussion on building a shared Dataverse platform :D

To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/adccf8e1-b9de-418b-a083-a72dc76dc5cf%40googlegroups.com.

[Philip Durbin]

Sure, regarding simultaneous use of multiple login systems I have even fresher news from just yesterday that just lead me to re-open that "Permit multiple login options to the same Dataverse account" with the following comment: https://github.com/IQSS/dataverse/issues/3487#issuecomment-592441613

There are some screenshots there but I'll attach them here as well. Please note that in the middle screenshot I am offered the choice of HarvardKey, ORCID, and GitHub login but should (in theory) still be able to me "me" in Dataverse.

This is because OIDC, a new feature in Dataverse 4.19 contributed by Oliver Bertuch from FZJ, is being used.

Phil

To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/adccf8e1-b9de-418b-a083-a72dc76dc5cf%40googlegroups.com.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

--

You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.

To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/308eb081-f326-482f-bdeb-2fd3db335b43%40googlegroups.com.