openlibhums / openlibhums/janeway
Help copyeditors know whether to replace file or upload new file
Open
Nobody has claimed this yet.
enhancement
Size M
- Dominant language
- Python
- Stars
- 238
- Forks
- 97
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 8
Description
User Story
As a copyeditor, I am unsure whether I am meant to upload a new file or replace an existing file when turning in copyedits. Version control of manuscript files is very central to my job and I often feel anxiety about communicating versions with project editors and authors.
I would like
- a bit of text explaining the difference, and
- a way to see all previous versions of the file, demonstrating to me that if I upload a new version of an existing file, I won't wipe out old versions.
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
No files, tests, or entry points are named in the issue; start by locating the copyeditor file-upload workflow and its existing version handling. Done means the workflow explains replacing versus uploading, and users can view previous file versions without losing them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100