openlibhums / openlibhums/janeway
Article number and link to article needed on all notifications
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 239
- Forks
- 97
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 8
Description
Describe the bug
At present, some of the notification emails don't contain either the article number or link to the article, so it can take a while to find the article manually in the system. This is quite a time-consuming issue, particularly for bigger journals with lots of notifications and actions required on papers.
Janeway version
1.3.9 (I think!)
To Reproduce
I got an article notification stating [personal details redacted]:
'[author] has completed revisions for [paper title]
Actions:'
There were no suggested actions here, and no link to the article
Expected behavior
A link to the article and a list of actions (as suggested by the email text) would be useful. In particular, in the [journal name] that appears in the title it would be good to pull in the article number as standard here so that every email on a specific article starts with the name of the article number as well as the journal (ie, [olh 4647]. Then a link to the article in the system in each email would be useful, ie, at the end of the email - something like:
'Click here to go to this article in the system: [link url]'
Desktop (please complete the following information):
Using windows 10 firefox (laptop)
Additional context
Githubbed as requested by AJRB - thanks for your help
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 files, tests, or entry points. Start by locating the notification email templates and the code that generates article notifications, then review each notification variant; done means every email includes the article number, a link to the article, and any promised action list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100