Reporting Corrections
Once you have reviewed the galley and noted every error, the next step is to communicate those corrections clearly to the Layout Editor (and any other relevant team members) so they can be fixed before publication. OJS provides a built-in discussion thread for this purpose.
Using OJS Discussion Threadsβ
All communication about a submission should happen inside OJS rather than via personal email β this keeps a complete audit trail attached to the submission record.
Opening the Production Discussions Panelβ
- Open the submission from your Dashboard β My Queue.
- Click the Production stage tab.
- Scroll down to the Production Discussions section.
- Click Add Discussion.
Creating a New Discussionβ
| Field | What to enter |
|---|---|
| Subject | A clear, brief subject, e.g. "Proofreading corrections β PDF galley" |
| Message | Your formatted corrections list (see below) |
| Participants | Add the Layout Editor and, if instructed, the Editor |
Click OK to post the discussion. All listed participants receive an email notification automatically.
You can reply to an existing discussion thread if one has already been started for proofreading. Avoid opening multiple separate threads for the same submission β keep all corrections in one thread to make it easy to track what has and has not been addressed.
Formatting a Clear Corrections Listβ
A well-structured corrections list saves the Layout Editor time and reduces the risk of corrections being missed or misunderstood. Use the following format for each item.
Recommended Table Formatβ
| # | Format | Page / Location | Element | Error | Suggested Fix |
|---|---|---|---|---|---|
| 1 | Page 2, para 3 | Body text | "recieve" | Change to "receive" | |
| 2 | Page 5, Table 2 | Column header | Missing bold formatting | Apply bold to header row | |
| 3 | HTML | Section 3.1 heading | Heading level | Rendered as <h4> | Should be <h3> |
| 4 | Page 8, Figure 3 caption | Caption text | "Figure 2" | Change to "Figure 3" |
Column Explanationsβ
| Column | Guidance |
|---|---|
| # | Sequential number so each correction can be referenced in follow-up messages |
| Format | PDF, HTML, XML β specify which galley has the error |
| Page / Location | Page number (PDF) or section heading / paragraph (HTML/XML) |
| Element | What type of content contains the error (body text, heading, table cell, caption) |
| Error | Describe the error exactly β quote the erroneous text in quotation marks where possible |
| Suggested Fix | What the corrected version should say or look like |
OJS discussion messages accept plain text. Format your table using Markdown (pipes and dashes) β it renders as readable columns in most email clients and browsers.
Attaching Annotated Galley Filesβ
In addition to the text corrections list, attaching the annotated PDF helps the Layout Editor locate each issue visually.
- In the Add Discussion (or Reply) window, click Upload File.
- Select your annotated PDF from your computer.
- In the Article Component dropdown, select Proofreading Notes (or the closest available option such as Other).
- Click Continue, confirm the file details, and click Complete.
- The file appears as an attachment in the discussion message.
Not all OJS installations enable file uploads in discussion threads. If the Upload File option is not visible, paste your full corrections list as formatted text in the message body and note that you can email the annotated PDF directly if needed.
Communicating Clearly with the Layout Editorβ
Be Specific, Not Vagueβ
β "There are some font issues on page 4."
β
"Page 4, paragraph 2: The word 'Introduction' in the body text is in Times New Roman, while the rest of the paragraph uses Cambria. Please standardise to Cambria."
Quote the Erroneous Textβ
Always quote the current (incorrect) text alongside the correct version:
Error: "The results shows a significantβ¦"
Fix: Change "shows" to "show"
This allows the Layout Editor to search the file for the exact text rather than scanning manually.
Use Neutral, Professional Languageβ
Proofreading is a collaborative process. Frame corrections as observations rather than criticisms:
- "This appears to be a typo β 'teh' should be 'the'."
- "The figure caption reads 'Figure 3' but this is the fourth figure in the article."
Prioritising Correctionsβ
Not all corrections carry the same weight. Flag the severity of each correction so the Layout Editor can triage efficiently.
| Priority | Type | Examples |
|---|---|---|
| Critical | Errors that affect meaning, accuracy, or metadata | Wrong author name, incorrect DOI, missing figure, factual error introduced in typesetting |
| Major | Errors that significantly affect readability or layout | Broken table, missing section heading, garbled special characters |
| Minor | Small typographic or stylistic inconsistencies | Single space vs double space, inconsistent capitalisation, minor alignment issue |
Add a Priority column to your corrections table, or group corrections under ### Critical, ### Major, and ### Minor headings in the discussion message.
Critical Corrections β Act Promptlyβ
If you discover a critical error (such as an incorrect author affiliation or a missing figure), notify the Layout Editor immediately via the discussion thread rather than waiting until you have finished the full review. Use "CRITICAL" in the message subject or at the top of your message so it stands out.
After Posting Your Correctionsβ
- Make a note of the discussion thread URL (copy it from your browser address bar) for your own records.
- Check back in OJS after one or two business days to see if the Layout Editor has replied.
- If you have not received a response within a reasonable time, send a follow-up reply in the same discussion thread β avoid starting a new one.
Further Readingβ
- Learning OJS β Production & Publication β How production discussions work
- PKP Community Forum β Community Q&A for OJS users