openlibhums / openlibhums/janeway
Repository: Comment moderation link to preprint title should resolve to preprint
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 239
- Forks
- 97
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 8
Description
Describe the bug
When reviewing the Repository Comment Moderation queue, the link of a submission's title resolves to the comment moderation queue for that preprint. It should resolve to the preprint itself -- the moderator is already on the moderation page.
Janeway version
1.9 RC1
To Reproduce
Steps to reproduce the behavior:
- Using an author or other account, submit a comment on a Janeway Repository object.
- Log in on a Moderator account, go to the Repository Comment Moderation queue
Screenshots
Expected behavior
The title Repository Object (eg Preprint) should link to the Preprint's moderator page view /repository/manager/[ID] and have some other method to filter all pending comments for a single Preprint, or it should at least have some method for getting to the Preprint's page (eg an additional column/link).
Compare with the UI for new version moderation, which gives heaps of info:
Would be nice: The link would go to the /repository/view/[ID] and have the pending comment(s) in line, in preview mode.
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 reproducing the Repository Comment Moderation queue behavior described in the issue and inspect the submission title link and its destination. Compare the link with the expected moderator or preprint view URLs; done means the title reaches the intended preprint page while moderators retain a way to filter pending comments for that preprint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100