HomePublishing Workflow › Author

Author

Legacy role: author.php (ROLE_2), with submit.manuscript.class.php / view/submit.manuscript.view.php and the shared manu.view.php detail view. Manuscript-lifecycle role — the corresponding author's portal: submission wizard, dashboard buckets for every in-flight manuscript state, revision, galley proof / required-documents / editorial-corrections responses, payment queue, and co-author invitations.

Page Status Workflow E2E Enhanced Legacy Ref Route Roles
Author Dashboard Full summary-cards author.php /author Author
Submit a New Manuscript Pending Submission author.php?_action=submit /author?_action=submit Author
Incomplete Submissions Full Submission pagination author.php?_action=incomplete /author?_action=incomplete Author
Submissions Sent Back to Author Full Submission pagination author.php?_action=resubmit /author?_action=resubmit Author
Submissions Being Processed Full pagination author.php?_action=processed /author?_action=processed Author
Submissions Contributed as Co-Author Full pagination author.php?_action=co_au /author?_action=co_au Author (co-author)
Submissions Needing Revision Full Revision pagination author.php?_action=need /author?_action=need Author
Revise Manuscript Pending Revision author.php?_action=revise /author?_action=revise&manu_code=... Author
Revisions Being Processed Full pagination author.php?_action=processed_r /author?_action=processed_r Author
Declined Revisions Full Revision pagination author.php?_action=decline_r /author?_action=decline_r Author
Manuscripts Sent for Required Documents Before Publishing Pending Production author.php?_action=ext_abs /author?_action=ext_abs Author
Submit Required Documents Pending Production author.php?_action=ext_abs_manu /author?_action=ext_abs_manu&manu_code=... Author
Manuscripts Sent for Editorial Corrections Pending Production author.php?_action=tedt_to_au /author?_action=tedt_to_au Author
Submit Editorial Corrections Pending Production author.php?_action=tedt_t_au /author?_action=tedt_t_au&manu_code=... Author
Manuscripts Awaiting Payment Full pagination author.php?_action=payment /author?_action=payment Author
Galley Proof Full Production pagination author.php?_action=galley_proof /author?_action=galley_proof Author
Galley Proof Response Pending Production author.php?_action=gl /author?_action=gl&manu_code=... Author
Submissions with a Decision Full Decision pagination author.php?_action=decision /author?_action=decision Author
Manuscript Information Full tabbed-detail author.php?_action=info /author?_action=info&manuscript=... Author (owner or co-author)
Acceptance / Publication Certificate Pending Decision author.php?_action=cert /author?_action=cert&manu=... Author
Withdrawal Request Pending author.php?_action=withdraw /author?_action=withdraw&manu=... Author
Finish Submission Pending Submission author.php?_action=finish /author?_action=finish&manu_code=... Author
Repair Manuscript Files Pending author.php?_action=repair /author?_action=repair&manu_code=... Author (self-service, via a direct dashboard link when already signed in, or the emailed author.php?_al=... auto-login link); also reachable by Journal Admin (Editor-in-Chief / System Admin / Editorial Office) via the same action with &eic=1, which drops the manu_owner ownership check entirely
Manuscript Evaluation Form Pending Review author.php?_action=rvf /author?__au=... Author
Invited Manuscripts Pending Submission author.php?_action=invited /author?_action=invited Author (invitee)
Invited Manuscript Detail Pending Submission author.php?_action=invitedInfo /author?_action=invitedInfo&inv=... Author (invitee)
Decline Invited Manuscript Pending Submission author.php?_action=declineInvite /author?_action=declineInvite Author (invitee)

Features

FeatureStatusE2EDescription
Author sees a dashboard overview of all in-flight manuscripts with per-bucket counts and preview cards Full Landing page shows the 4 attention buckets (incomplete, sent-back, needs-revision, galley-proof) as preview cards with counts, replacing the legacy menu-only author.php landing.
Author can live-search across all their manuscripts from the dashboard New A single dashboard search box finds a manuscript regardless of which lifecycle bucket it is in.
Author can browse each lifecycle bucket as a paginated, searchable list (incomplete, sent-back, in-progress, co-author, needs-revision, revisions-in-progress, declined-revisions, awaiting-payment, galley-proof, with-decision) Full Every legacy author.php bucket screen that survived is served by the shared [bucket] list page.
Author sees revision due dates with overdue highlighting in the needs-revision list Full The revise deadline is a first-class column so an overdue revision is visually obvious.
Author can slice decided manuscripts into accepted / rejected / deleted / withdrawn sub-buckets New Per-outcome sub-lists of the with-decision bucket, with a certificate column only on accepted.
Author can view a read-only tabbed manuscript detail (information, authors, editors & reviewers, files, cover letter & checklist, payments) for owned and co-authored manuscripts Full Replaces the legacy manu.view.php single-scroll detail reached via author?_action=info (with &co_au for co-authored).
Author can submit a new manuscript through the multi-step wizard (manuscript info, authors, files, suggested reviewers, cover letter & checklist) Pending Legacy author.php?_action=submit via submit.manuscript.class.php submitStepsPanel/saveCurrentStep/uploadFile/saveAuthorReviewer; the TenantSidebar 'Submit Manuscript' link is a placeholder and the bucket Submit button uses a provisional legacy URL.
Author can resume a saved incomplete submission where they left off Pending The incomplete-bucket manuscript-ID link intentionally still points at the legacy wizard (author?_action=submit&manu_code=...) via resolveManuscriptIdHref.
Author can delete an incomplete submission Basic The destructive row action exists in the UI but performs nothing yet.
Author can reorder co-authors on a submission Pending Legacy reOrderAu in submit.manuscript.class.php (submission-wizard authors step); no apps/web submission flow exists.
Journal enforces a per-author cap on concurrent submissions Pending Legacy checkAuMaxSubmissions blocks a new submission when the author's open-submission count reaches the journal limit.
Main manuscript file is validated against the journal's word-count limit during submission Pending Legacy checkMainFileWords in submit.manuscript.class.php.
Finishing a submission generates the manuscript PDF and emails the corresponding author and each co-author Pending Legacy finishSubmissionProcess sends 'submit_manu' to the submitter and 'submit_other_authors' to each co-author via EmailManager, and createPDF builds the compiled manuscript PDF; author.php?_action=finish.
Author can pay a pre-submission / fast-track fee as part of submission Pending Legacy fastTrackPayment and checkManuPrePaymentStatus gate the wizard on journals with pre-payment enabled.
Author can submit a revision of a sent-back manuscript Pending Legacy author.php?_action=revise revision form (emails 'revise_manu' on completion); the needs-revision list's continue link still targets the legacy form.
Author can respond to a galley proof (view proof notes, upload/confirm) Pending Legacy author.php?_action=gl via manageGalleyProofManuscript/getGalleyProofNotes/saveGl/checkGlRqFiles (manu_status 6); only the galley-proof queue list is ported.
Author can submit required documents requested before publishing Pending Legacy author.php?_action=ext_abs queue + ?_action=ext_abs_manu form (manageGalleyProofManuscript, manu_status 45); neither the queue bucket nor the form exists in apps/web.
Author can submit editorial corrections Pending Legacy author.php?_action=tedt_to_au queue + ?_action=tedt_t_au form (manageGalleyProofManuscript, manu_status 60); neither ported.
Author can pay a publication fee / upload a payment receipt for an awaiting-payment manuscript Pending The awaiting-payment list is ported but its pay-now link targets legacy response.php?manupm=... (sibling Response module, itself flagged as apparently dead in its own inventory).
Author can download an acceptance or publication certificate for an accepted manuscript Pending The accepted bucket surfaces certificate links (AuthorManuscriptsTable certificate column) but buildAuthorActionUrls points them at legacy author?_action=cert&ac / &pb; no apps/web certificate renderer.
Author can request withdrawal of a manuscript with an explanatory note Pending Legacy manuscriptWithdrawRequest sets manu_wait_for_response=1 / l1=100, records a status-55 tracking entry with the author's note; the apps/web row-menu withdraw item links to the legacy form.
Co-author can email the Editor-in-Chief about a manuscript from the list Basic The button is present but inert; legacy provided the email link from the co-author bucket.
Author can download a manuscript's main file from the row actions Basic The menu entry exists but has no href/mutation yet.
Author can repair rejected/broken manuscript files self-service, including via an emailed auto-login link; journal admins can repair any manuscript with the eic=1 override Pending Legacy author.php?_action=repair, reachable via the encrypted author.php?_al=... auto-login link (getAuthorDirectLink); &eic=1 drops the manu_owner ownership check for Editor-in-Chief/System Admin/Editorial Office.
Author can complete a reviewer evaluation form sent to them by encrypted email token Pending Legacy author.php?__au=... (internally _action=rvf) renders the manuscript evaluation form keyed on an encrypted manuscript+reviewer-assignment token.
Invited author can view invited manuscripts, see invitation detail, accept (start a submission tied to the invitation) or decline with a reason Pending Legacy author.php?_action=invited / invitedInfo / inviteaction / declineInvite via getInvitedManuscripts/getInvitedManuscriptInfo/manageInvite/declineInvieteManuscript; accepting redirects into the submission wizard with &inv=.
Manuscript access is enforced server-side to the owning author or listed co-author Full An author cannot open another author's manuscript detail; failures are indistinguishable from not-found.
Legacy 'waiting for approval', 'in-house evaluation', 'incomplete revisions' buckets and the saveSimple submission action Dropped Dead-in-legacy capabilities deliberately excluded from the port.
author.index.php is a same-prefix false friend — it is the public, unauthenticated "Browse by Author" A-Z index (journal/author-index.md / browse-by-author.md), not part of this role portal. It is inventoried under the Journal segment's browse module, not here.
Excluded as non-rows: ?_action=guide sets a page title (MENU_GUIDE_FOR_AUTHORS) but has no matching branch in the content switch, so it silently falls through to the same Author Dashboard markup — not a materially different screen (the real "Guide for Authors" link on the dashboard footer points to journal/authors.note, a separate public page outside this module). ?_action=waiting, waiting_r, in_house, and incomplete_r are still handled in author.php's switch but are not linked from the current menu (__author_pmenu) or dashboard view, and are not documented as live buckets in author-manuscript-list.md — leftover dead code from a superseded menu, not reachable via any in-app link. ?_action=saveSimple calls saveSimpleSubmission(), which is not defined anywhere in the codebase (fatal error if hit).
Manuscripts Awaiting Payment
only lists the manuscripts; clicking a Manuscript ID does not stay in author.php — it links to response.php?manupm=<manu_code> (the actual "pay now / upload receipt" screen), which belongs to the sibling Response module. This is a live caller into response.php, worth flagging since that module's own inventory describes it as apparently dead/unused.
Submissions Being Processed
and Revisions Being Processed are tagged Workflow "—" rather than one lifecycle stage: both buckets are a numeric-range/exclusion filter (manu_status >= 3 minus a decided-status set) that can span triage, assignment, and review simultaneously from the author's point of view — there is no single stage name that fits.
Galley Proof Response
, Submit Required Documents, and Submit Editorial Corrections all render through the same manageGalleyProofManuscript view function, distinguished only by the loaded manuscript's manu_status (6, 45, or 60). They are kept as three rows because each is reached from a distinct dashboard bucket with a distinct step label (galley note / required-documents note / technical note) and a distinct next status.