openlibhums / openlibhums/janeway

As a typesetter, I need to track an article's progress after completing the typesetting assignment

Open
#3,338 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

new feature Size M
Dominant language
Python
Stars
238
Forks
97
Avg merge
9d 1h
Merged PRs (30d)
8

Description

User Story
As a large typesetting service provider, we track jobs independently of Janeway. When we use Janeway to send a proof to the editor for author review, we set its status in our system as "waiting for return of proofs from author". However, sometimes the editor publishes the article, without returning it to us, because no corrections were made to the proof. We aren't notified when that happens, so soon our records get out of sync with the journal's records. We have to email the journal outside of Janeway to ask about lingering articles, and this is cumbersome

Proposed solution
We'd like to be notified in two ways:

  • When an editor moves an article out of typesetting, we'd like to be notified by email.
  • We'd like to see an overview of articles we previously worked on with indications of current status. This would allow us to compare Janeway to our own records from time to time to check for discrepancies, clearing articles that have been moved to pre-publication.

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 tracing the article typesetting workflow and the status transition that moves an article out of typesetting. Then identify how Janeway currently sends email notifications and presents article status. Done should provide an email notification for that transition and an overview of previously typeset articles with their current status.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.