openlibhums / openlibhums/janeway
Inconsistent identification of files with no labels
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 238
- Forks
- 97
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 8
Description
When a file has been added without a label - in some places the label is then missing, leaving the file with no identifier, in others 'no label' is specifically stated, and in yet others, the filename is used so there is an identifier, but it is not obvious the label is missing.
Files should be consistently identified.
This within the spirit of WCAG 3.2.4 which is about consistently identifying functions. While files aren't functions, it is equally unhelpful having files identified differently in different places when we are handling workflows with multiple files.
Article In Review
Left has label, right has no label
Document Management
Review Assignment
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
The issue names no source files or tests; begin by comparing the Article In Review, Document Management, and Review Assignment views shown in the screenshots. Trace how files without labels are identified in each view, then make the treatment consistent and verify all three workflows display an explicit identifier.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100