Skip to content
This repository was archived by the owner on Feb 11, 2026. It is now read-only.
This repository was archived by the owner on Feb 11, 2026. It is now read-only.

Improve visibility of proofed files when assigning typesetting corrections #166

Description

@joemull

Problem reported

When creating round 2 typesetting assignments, editors report confusion about whether files that have been uploaded by proofreaders will be available to typesetters. The trouble arises on the assignment creation page when they are trying to manage and distinguish between three different places where files are specified:

  1. Which file to typeset -- usually a manuscript file in Word format. In rounds after the first, the requirement to check such a file again causes some consternation, since it seems that by doing so one is designating a new file, when the file they want to highlight as containing new information is actually the proofed file (below).

  2. The proofreader-uploaded files. These files are hidden at first, so it's not immediately clear that this file will even be included (see screenshot).

Screenshot from 2022-07-25 10-57-33

  1. The previously uploaded typeset files. These are listed under "Corrections". They are automatically selected, in contrast to the files to typeset.

Suggested changes

To the assignment page

  • List any proofreader-uploaded files on the main assignment creation page--that is, the user does not have click "View proofreader feedback" to see them.
  • Automatically check the file to typeset that has already been sent to the typesetter. In other words, the form should remember what files were sent in the previous typesetting round, as it does for the typeset files at the bottom of the page. This is important because it helps the user understand that this file has already been sent and they can leave it alone.
  • While you're at it, standardize the styling of these three file lists so that they are the same (they all use different Foundation CSS elements at the moment)

To the typesetter view

  • Add a "Modified" column to the "Files to Typeset" list so typesetters can tell when a file is old or new.

Metadata

Metadata

Assignees

Type

No type

Fields

No fields configured for issues without a type.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions