openlibhums / openlibhums/janeway
ROR in repository system
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 238
- Forks
- 97
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 8
Description
User story
When submitting a preprint, I am prompted to create affiliations using ROR data.
Proposed solution
Amend the current preprint submission workflow to include manual affiliation entry as a step. Perhaps make it optional once we have ROR data coming through ORCiD more reliably. This would depend on how heavily Janeway repositories encourage people to log in with ORCiD.
Hook into the same or similar affiliation management views as for article affiliations, with a return URL back to the repository submission path.
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 tracing the preprint submission workflow and comparing it with the existing article affiliation management views. Confirm how ROR and ORCiD data currently enter the workflow, then define the manual affiliation step, its optional behavior, and the return URL back to repository submission; done means the flow supports manual entry without losing submission context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100