openlibhums / openlibhums/janeway

When submitting, author cannot return to first page of process

Open
#4,458 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

User Story

As an author, when I am submitting an article, I have to navigate a multipage process. I am guided through this by a chart at the top, which allows me to move back to previously completed pages, except for the first page.
image

As I'm entering information on a later page, I may realise I've made a mistake and want to check back on the first page, particularly as there is a rich text entry option on the first page, so it wasn't just a case of ticking some boxes which if not ticked I'd not be able to proceed.

Further the text the user enters on that first page under 'Competing Interests' shows up on the final page for checking, but there is no way to go back and edit it.

Solution I'd like

either:
Include the start page in the map, but make the tick boxes non-editable.

or:

Move the 'competing interest' text entry to a different page / new page.
make the tick boxes for the start of the submission separate from the rest of this process, and don't include it in the visual map.


note:
first page URL: /submit/start
subsequent pages: /submit/[article_id]/info, /submit/[article_id]/authors etc.

If there first page is just tick boxes, without agreeing to which one cannot proceed, then there is some sense in it not be editable later, but I think it should be distinguished from the rest of the pages, not part of the same map.

Currently the first page also has a rich text box for competing interest information, this should be editable during the process. Perhaps it should move to a different page?

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 submission flow from /submit/start through /submit/[article_id]/info and /submit/[article_id]/authors, including the chart that links completed pages. Decide how the first-page competing-interest text can remain editable while preserving the required initial tick-box agreements, then verify that authors can return to it and review the value on the final page.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.