openlibhums / openlibhums/janeway
Popup to warn author on new article submission not to submit manuscript revisions for pre-existing article
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.
Authors are occasionally prone to bypassing article revision tasks in the review stage of Janeway to instead submit their revised manuscript as an entirely new article with new article ID. This situation can lead to redundant articles in the workflow, and more worryingly can mess up peer review processes, as the PR tasks can get split between two article IDs.
Describe the solution you'd like
On the submission of an article, this feature would check to see if the author already has an unpublished article in Janeway under their account, and if there is an article, a popup could warn them not to upload any article revisions through the main submissions process. If this does not apply to them, they might be able to proceed, but the hope is this would force them to consider what they are doing first.
Describe alternatives you've considered
The difficulty is in the term 'resubmit' – we will need to look through our email templates and documentation to see if this is used for revision tasks, but it stands to reason that some authors will still do this regardless.
Additional context
N/A
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 with Janeway’s main submissions process and compare it with the existing revision-task workflow. Review email templates and documentation for uses of “resubmit”; done means the submission flow clearly warns authors who have an unpublished article without disrupting authors for whom the warning does not apply.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100