openlibhums / openlibhums/janeway
ORCID functionality should be managed at the 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 a Janeway Press administrator, I would like the ability to both a) add and update Janeway's ORCID credentials at the press level, as well as b) manage ORCID functionality for each journal or repository at the press level (related feature request: https://github.com/openlibhums/janeway/issues/2655 ).
In addition, to reduce the burden on the Janeway Press Admin of needing to update our ORCID credentials each time we add a new Journal or Repository, Janeway's ORCID integration should redirect to a Press-level page which then auto-directs them to the relevant journal or repository. (See related feature request: https://github.com/BirkbeckCTP/janeway/issues/3335 .)
Describe the solution you'd like
Add a new section to the Janeway Press Manager: ORCID Manager
The ORCID Manager should be a separate page which allows the Press Administrator to add or update the listed ORCID API Credentials, as well as enable functionality for each journal or repository under the press.
There should be clear instruction to the Press Administrator on what Redirect URI to register with their ORCID API credentials, along with a note that ORCID requires HTTPS Redirect URIs.
For each journal or repository, there should be an option to:
- Enable ORCID (users can sign in/register with ORCID or connect their ORCID iDs to their accounts)
- Require ORCID iD from submitting author (submitting author must have an authenticated ORCID iD connected to their Janeway account) (related: https://github.com/openlibhums/janeway/issues/2655 )
- Request ORCID iDs from co-authors (when an article is accepted for publication, an email is automatically sent to all listed co-authors requesting that they connect their ORCID iD to Janeway) (related: https://github.com/openlibhums/janeway/issues/2655#issuecomment-1263450625)
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 reviewing the existing Press Manager and ORCID integration, then read related issues 2655 and 3335 to understand the surrounding requirements. Done means a press-level ORCID Manager supports credential updates, journal and repository settings, clear HTTPS redirect-URI guidance, and redirects users to the relevant journal or repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100