Registering for an account needs explanation

Open
#162 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
javascript
Domain
authentication

Research direction

Start at the InterlexNext homepage's Register and Login entry points and reproduce the reported ORCiD flow, including the blank window and sandbox credential error. Review the registration and authentication behavior to determine whether ORCiD is required and how it relates to username/password accounts; done means the requirements are explicit before registration and the resulting login flow is consistent.

Written by the indexing model from the issue text.

Description

Issue: I'm not sure if ORCiD is required, it's not clear up front that ORCiD is helpful/needed.

  1. Click Register on InterlexNext homepage. [I registered for an account today, under the username stappan, I filled in the requested fields],
  2. Click "register", 2 new windows opened up.
    first was blank, second was a request to sign into ORCiD.
    [Sandbox ORCiD doesn't accept my actual ORCiD credentials. receive error message]
  3. return to InterlexNext homepage
  4. select login
  5. type in credentials.
  6. successful. login accepted.

Issues and questions:

  1. if ORCiD is needed and used by Interlex,
  • the initial login should provide that information upfront.
  • do we need the username/password method of creating an account? (i.e., would we select to use ORCiD -or- email / username pair)?
  • is it important that the username and email is linked to the ORCiD ?
  • should i be able to login even if i don't have my ORCiD added to my account?
  1. if ORCiD is not needed, i'm not sure why upon selecting register that it calls up ORCiD login.
Image
Dominant language
JavaScript
Stars
3
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MetaCell/interlex

All issues in MetaCell/interlex

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.