openlibhums / openlibhums/janeway
Make issue field optional rather than required
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.
Many of our journals only use volume numbers, but the current system requires both a volume and issue number for a new set of content.
Describe the solution you'd like
It would be great if the issue number field could be optional rather than required, even if this is assessed on a journal-by-journal basis
Describe alternatives you've considered
As a workaround, we've been entering "0" into the issue field for journals that only use volume numbers, but this means that on the journal's page, the volume is listed as "Volume 15, Issue 0" for instance.
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. Start by tracing validation for new journal content and how volume and issue numbers are displayed, then check whether optional issue numbers can be configured per journal. Done means volume-only journals no longer require a placeholder and their pages display the volume without “Issue 0”.
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