openlibhums / openlibhums/janeway

Janeway upgrade guide for editors, repo managers, and press managers

Open
#4,628 1 comment 0 reactions 1 assignee View on GitHub

@joemull is already working on this.

Since Feb 20, 2025.

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

Description

User story

As an editor, repo manager, or press manager, I know that Janeway has so many useful features, and that they are often introduced as optional settings which are by default off until I find them and turn them on, since the Janeway team do not want to change more than they have to for people who want their workflow to stay the same. The CRediT contributor role standard is one example.

Proposed feature

Notify each press manager and each journal manager unobtrusively about major new optional features when installation is upgraded.

  • Prominent but dismissable banner that says something like "Choose new settings in Janeway vX.X"

    • Button to open step-by-step series of new settings
    • Button to snooze all for one week (for this journal or repo or press)
    • Button to snooze all for one month (for this journal or repo or press)
    • Button to dismiss all permanently (for this journal or repo or press)
  • A page for making a decision about each setting

    • The name and description of the setting and information about whether you're setting it for the press or journal (i.e. the same info as on the settings edit page)
    • An explanation of what the setting does (link to docs?)
    • An option to snooze a decision for a week
  • Not all new settings would be put in this guide, only important ones that we think a significant number of people would want

  • Important settings introduced in the last 2-3 years that are under-utilized can be put in the first iteration of this guide, since some editors may still not know about them

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.