openlibhums / openlibhums/janeway
Allow Coauthor Confirmation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 238
- Forks
- 97
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 8
Description
If enabled, coauthors are asked to confirm the submission is ok and that they are indeed co-authors (or not).
This is now closely linked with the ORCID work that CDL are undertaking (including https://github.com/BirkbeckCTP/janeway/issues/3351 and https://github.com/BirkbeckCTP/janeway/issues/2655)
I have drafted a rough co-author confirmation wireframe (yes its not great) but it will give a rough idea of what is intended here. This "wireframe" constitutes the content section of a standard Janeway backend page.
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 coauthor confirmation wireframe and the linked ORCID issues #3351 and #2655 to understand the intended workflow. Done means an enabled confirmation flow lets coauthors confirm both that the submission is acceptable and that they are coauthors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100