openlibhums / openlibhums/janeway

Separate email/letter template for desk rejection VS review stage rejection

Open
#3,964 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

dev-ready good first issue new feature Priority high Size M
Dominant language
Python
Stars
238
Forks
97
Avg merge
9d 1h
Merged PRs (30d)
8

Description

Currently, there is one email template for rejections (review_decision_decline). It would meet editors' needs better to have two separate templates for desk rejections VS rejections at the review stage.

Having two templates (review_decision_decline + submission_decision_decline perhaps?) means editors can set up two standard responses, limiting how much they may need to edit these templates. Currently, at least one journal has two letters in the current template from which they delete one. This does however introduce more margin for error and issues, if editors need to edit this email every time it is being send.

(Additional note: based on FD ticket 7813. Requested to be put in 1.6 + 'Good first issue' potentially?)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the existing review_decision_decline template and the code paths that send rejection emails. Trace how desk rejections differ from review-stage rejections, then add and wire a separate template so editors can configure each response independently; verify both rejection flows use the intended template.

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
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.