openlibhums / openlibhums/janeway
ORCID Redirect URI should be at Press level
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 238
- Forks
- 97
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 8
Description
Is your feature request related to a problem? Please describe.
As as Janeway Press Administrator whose Press supports multiple journals and repositories, I want to reduce the burden of updating my ORCID API client's Redirect URIs every time we add a new journal/repository or changes its URL.
Describe the solution you'd like
Create an "ORCID processing" page at the Janeway Press level to serve as the Press-wide Redirect URI.
Include in the ORCID OAuth link a param which indicates the journal or repository the account holder should be directed to after they return to Janeway from ORCID.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing ORCID OAuth link and its return/redirect handling for journal and repository flows. Define the Press-level ORCID processing page and the parameter that identifies the destination. Done means one Press-wide redirect URI supports multiple journals and repositories and returns account holders to the indicated destination.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100