We'll remember your contact info. for this session.

History of Dataverse Account II - Converted Account Info

  • 4 years ago (), Comment by Michael:
    It is mocked up this way because in one of the meetings, it was decided that First Name and Last Name would be able to be delivered from Shibboleth.
  • 4 years ago (), Comment by Philip:
    AuthenticatedUsers don't have separate first and last names. They only have a field called "name" in the database. You can think of it as "display name". So I'd prefer to just show "Name" here rather than trying to parse it apart.

    See also https://github.com/IQSS/dataverse/issues/457#issuecomment-66558549
  • 4 years ago (), Comment by Philip:
    Yep. Sounds fine.
  • 4 years ago (), Comment by Michael:
    I am reusing that screen for both workflows. We can easily conditionally render a different message.
  • 4 years ago (), Comment by Philip:
    You can get to this mockup by clicking the "doesn't not have a matching email" but in this case it does not make sense to say we are converting the account. What we are really doing is creating an account. Imagine a new user from Harvard who is creating an account for the first time and is choosing to do so via Shibboleth.
  • 4 years ago (), Update by Michael: Rerendering to satisfy referential integrity constraint.
    Dataverse Account III - Agree Terms of Use Login Dataverse Account III - Agree Terms of Use
  • 4 years ago (), Minor update by Michael
  • 4 years ago (), Update by Michael: Rerendering to satisfy referential integrity constraint.
  • 4 years ago (), Minor update by Michael
  • 4 years ago (), Update by Michael: Rerendering to satisfy referential integrity constraint.

Load more...

Please click OK to reload the page and continue using myBalsamiq