HomePublishing Workflow › Specialist Editor

Specialist Editor

Legacy entry point sp_editor.php (dispatch view view/index.sp_editor.view.php, shared list/detail rendering in class/editor.class.php + view/editor.view.php) — role 9's manuscript-handling workspace, labeled "Editor" in the legacy UI itself (renamed "Specialist Editor" here per the Phase B taxonomy to avoid confusion with the separate Editor-in-Chief module). A set of work-queue lists scoped to manuscripts personally assigned to the logged-in specialist editor, plus a shared manuscript detail/decision panel, search, and guide.

Page Status Workflow E2E Enhanced Legacy Ref Route Roles
Specialist Editor Home Pending sp_editor.php /sp_editor Specialist Editor
New Manuscripts Pending Assignment sp_editor.php?_action=assign /sp_editor?_action=assign Specialist Editor
Manuscripts Assigned to Reviewers Pending Review sp_editor.php?_action=assigned /sp_editor?_action=assigned Specialist Editor
Reviewers Not Reviewed Manuscript in Review Due Date Pending Review sp_editor.php?_action=not_respond_due /sp_editor?_action=not_respond_due Specialist Editor
Manuscripts Agreed by Reviewers Pending Review sp_editor.php?_action=accept /sp_editor?_action=accept Specialist Editor
Manuscripts Not Responded by Reviewers Pending Review sp_editor.php?_action=not_respond /sp_editor?_action=not_respond Specialist Editor
Manuscripts Requiring Additional Reviewers Pending Review sp_editor.php?_action=need_adt_rv /sp_editor?_action=need_adt_rv Specialist Editor
Manuscripts Reviewed by Reviewers Pending Review sp_editor.php?_action=all_reviewed /sp_editor?_action=all_reviewed Specialist Editor
Manuscripts Reviewed by All Reviewers Pending Review sp_editor.php?_action=reviewed_cmpl /sp_editor?_action=reviewed_cmpl Specialist Editor
Manuscripts Recommended by Reviewers to be Revised Pending Review sp_editor.php?_action=need_revise /sp_editor?_action=need_revise Specialist Editor
Manuscripts Accepted by Reviewers Pending Review sp_editor.php?_action=reviewer_accept /sp_editor?_action=reviewer_accept Specialist Editor
Manuscripts Rejected by Reviewers Pending Review sp_editor.php?_action=reviewer_decline /sp_editor?_action=reviewer_decline Specialist Editor
Manuscripts Declined by Reviewers Pending Review sp_editor.php?_action=reject /sp_editor?_action=reject Specialist Editor
Manuscripts with Editor's Decision Pending Decision sp_editor.php?_action=assignedd /sp_editor?_action=assignedd Specialist Editor
Closed Assignments Pending sp_editor.php?_action=closed /sp_editor?_action=closed Specialist Editor
Manuscript Detail — Assign Reviewers & Record Decision Pending Review request/editor.ajax.php?task=showManusriptDetails POST /request/editor.ajax?task=showManusriptDetails&manu_code=... Specialist Editor
Search Manuscripts Pending sp_editor.php?_action=search /sp_editor?_action=search Specialist Editor
Guide for Editor Pending sp_editor.php?_action=guide /sp_editor?_action=guide Specialist Editor
Pending Manuscripts Pending Review sp_editor.php?_action=sassign /sp_editor?_action=sassign Specialist Editor
Submission History Pending sp_editor.php?_action=track /sp_editor?_action=track&manu=manuCode Specialist Editor
Reviewers / Editors Report Pending sp_editor.php?_action=revTrack /sp_editor?_action=revTrack Specialist Editor

Features

FeatureStatusE2EDescription
Specialist Editor can open a home dashboard listing every work queue with a live per-queue count badge Pending sp_editor default view renders an 'Editor Options' panel where each queue link carries the current record count (view/index.sp_editor.view.php lines 88-235).
Dashboard queue set adapts to the journal's workflow mode: reviewer-managing mode (spAction=1) shows the reviewer queues, direct-decision mode hides them Pending getSpAction() gates the assigned/agreed/declined/not-responded/overdue block; in direct-decision journals the specialist editor evaluates manuscripts personally instead of managing reviewers.
Reviewer response-breakdown queues (Agreed / Declined / Not Responded) appear only when the journal's rv_details setting is 2 Pending A journal-level setting decides whether the editor sees reviewer accept/decline/no-response splits or only the aggregate assigned queue.
Specialist Editor can view a queue of newly assigned manuscripts (New Manuscripts) Pending sp_editor?_action=assign lists manu_status=23 manuscripts personally assigned to the logged-in role-9 editor.
Specialist Editor can view manuscripts currently assigned to reviewers Pending sp_editor?_action=assigned lists manu_status 4/30/49 with any reviewer response state.
Specialist Editor can view manuscripts whose reviewers have agreed, declined, or not responded to the review invitation (three separate queues) Pending sp_editor?_action=accept / reject / not_respond split the assigned pool by reviewer accept_reject state.
Specialist Editor can view reviewers who have passed the review due date without reviewing Pending sp_editor?_action=not_respond_due uses getReviewersAssignments with a due-date filter to surface overdue reviewer assignments.
Specialist Editor is alerted to manuscripts needing additional reviewers, via a red-badged queue link shown only when the count is non-zero Pending sp_editor?_action=need_adt_rv (cmpl=2 filter); the home panel conditionally injects the link with a badge-red count (view/index.sp_editor.view.php lines 148-153).
Specialist Editor can view manuscripts reviewed by at least one reviewer, and separately those reviewed by all reviewers Pending sp_editor?_action=all_reviewed and reviewed_cmpl (cmpl=1) via manuscriptReviewWorkFlow.
Specialist Editor can view manuscripts by reviewer recommendation: recommended to revise, accepted, or rejected (hidden queues in this portal) Pending sp_editor?_action=need_revise / reviewer_accept / reviewer_decline (rev_recommend 2/1/4) render if visited directly; their menu links are commented out here but the identical screens are live in the sibling EIC and Section Editor portals.
Specialist Editor can view a hidden Pending Manuscripts queue (manu_status=30) Pending sp_editor?_action=sassign still renders when hand-typed although its links are commented out of both themes' menus; the same action is a live menu item in the Executive Director portal.
Specialist Editor can view manuscripts on which they have already recorded an editor decision (Decision-stage queue) Pending sp_editor?_action=assignedd lists spCompleted=1 manuscripts, respecting the journal's spAction mode.
Specialist Editor can view their closed assignments Pending sp_editor?_action=closed lists assignments closed out of the editor's active workload.
Specialist Editor can open a manuscript's detail panel in-page from any queue row without leaving the list Pending Clicking a manuscript ID fires POST request/editor.ajax.php?task=showManusriptDetails rendered by the shared EditorManager::preAssignReviewers() into the current page; no separate URL exists.
Specialist Editor can assign reviewers to a manuscript, picking from a subject-filtered reviewer list, and reviewers are emailed invitations Pending 'Assign Manuscript to Reviewers' panel (reviewer-managing mode): selectReviewers builds a subject-tree-filtered role-3 list, saveReviewers/getEmailTo tasks assign and send templated invitation emails.
Specialist Editor can manage active reviewer assignments: unassign a reviewer, extend the review due date, and send author files to reviewers Pending editor.ajax.php tasks unassignRev, extendDueForm, sendAuthorFilesToReviewers operate from the shared detail panel.
Specialist Editor can read reviewer recommendations and review comments for a manuscript Pending getReviewersRecommend / getReviewersRecommentation surface each reviewer's recommendation and evaluation inside the detail panel.
Specialist Editor can record their editorial evaluation: send an evaluation result to the Editor-in-Chief, or make the decision directly in direct-decision journals Pending The detail panel's second mode ('Send Evaluation Result to Editor-in-Chief' / 'Make Decision'); in direct-decision mode showEditorActionForm has the editor fill the evaluation form personally (editor treated as an assign_status=5 reviewer, one submission then locked), via sendFinalRecommend/saveDecision tasks.
Specialist Editor can save private editor notes on a manuscript Pending saveEditorNote task; note_for_editor / manu_editor_note fields are loaded with the detail panel.
Opening a manuscript that is awaiting the editor's response clears its unread/awaiting flag Pending preAssignReviewers calls checkManuUnread when manu_wait_for_response=1 (class/editor.class.php:902-904) — a background side-effect of viewing the detail.
Specialist Editor can search their manuscripts with a criteria form and browse the result list Pending sp_editor?_action=search renders manuSearchForm; on submit getSubmissionList feeds the shared list renderer scoped to the editor's assignments.
Specialist Editor can read a static role guide page Pending sp_editor?_action=guide renders getSpEditorsGuide(), linked from the home panel footer.
Specialist Editor can view a manuscript's full submission tracking history (undiscoverable route) Pending sp_editor?_action=track&manu=<code> renders showManuscriptTracking but no menu or footer link exists in index.sp_editor.view.php — reachable only by hand-typed URL as role 9.
Specialist Editor can view a reviewers/editors assignment report (undiscoverable route) Pending sp_editor?_action=revTrack renders getReviewersAssignments; unlike sibling portals no footer link exists here — hand-typed URL only.
Specialist Editor can log in with one click from a notification email deep-link Pending sp_editor?_ad=<encrypted> bypasses the session gate: the _ad payload is decrypted (EncDec keyed on the journal abbreviation) and loginEditorsA signs the editor in, with a bot-user-agent guard.
Author identities can be hidden from Specialist Editors journal-wide (blind handling) Pending When the hide_au_sp_edt journal setting is 1, every list/detail call receives hide_au=1 so the editor never sees author names (sp_editor.php:229-232).
Every Specialist Editor page is gated to role 9; users without the role are redirected home, unauthenticated users to login with return-to-page Pending sp_editor.php:19-40 checks ju_contact_role._role=9 for the session contact on every action, with pLoc capture for post-login return; no role widening anywhere in the file.
Hidden/dead route — Pending Manuscripts.
_action=sassign is commented out of both the classic "Editor Options" panel and the primary-menu builder in template/rules.php — it has no live link anywhere in the current UI. The dispatch switch, page-title mapping, and underlying query (manu_status = 30) are all still intact, so the URL still renders a distinct list if visited directly. Included per the row-identification rule for hidden-but-rendering actions; flagged here as dead/unreachable navigation, in the same spirit as the segment's response.php.
Hidden/dead routes — Recommended to Revise / Accepted by Reviewers / Rejected by Reviewers.
_action=need_revise, reviewer_accept, and reviewer_decline follow the same pattern as sassign above: each has an intact page-title mapping (sp_editor.php lines 110-118) and an intact action-switch branch calling manuscriptReviewWorkFlow($_PARAMS) with a distinct rev_recommend filter (2, 1, and 4 respectively; class/editor.class.php ~line 1466), but their only links are commented out of the classic "Editor Options" panel (view/index.sp_editor.view.php lines 183-204) and never added to the Modern-theme menu builder (__speditor_pmenu(), template/rules.php). The identical actions are live, uncommented menu items in the sibling Editor-in-Chief (editor.php, __editor_pmenu()) and Section Editor (sec_editor.php) portals, confirming these are working screens rather than abandoned template code.
Undiscoverable utility routes — Submission History / Reviewers & Editors Report.
_action=track and _action=revTrack are wired into sp_editor.php's dispatch switch and page-title mapping, but — unlike the sibling editor.php / jexpert.php / sec_editor.php portals, whose own views link "Reviewers / Editors Report" from their footer — index.sp_editor.view.php exposes no menu or footer link to either action (the one "Submission History" link in the codebase, in view/manu.view.php, is commented out and hardcoded to editor.php, not sp_editor.php). apps/legacy/spec/editor/editor-role-dashboard-menu.md's _role IN (1, 4, 9, 14) broader-role claim (line 64) names exactly the three actions editor.php widens for — manuscript tracking history, print view, impersonation entry (track/print/imps, editor.php:69-72) — not sp_editor.php's own gate, which is hardcoded to _role = 9 for every _action with no widening anywhere in the file (verified: sp_editor.php:19-40 is the only _role check in the file). revTrack is not even among the three actions editor.php widens, and jexpert.php:46 / sec_editor.php:50 show the same single-role, no-widening pattern for their own track/revTrack. So for the Specialist Editor these two routes remain reachable only as role 9, and only via a hand-typed URL since no menu/footer link exists in index.sp_editor.view.php (confirmed absent, unlike index.editor.view.php:570, index.jexpert.view.php:310, and index.sec_editor.view.php:357, which all do link _action=revTrack).
Manuscript Detail is not a distinct _action.
Clicking any manuscript ID in the lists above fires an in-page AJAX POST (inc/js/editor.jsrequest/editor.ajax.php, task=showManusriptDetails) that a shared, cross-role class method (EditorManager::preAssignReviewers()) renders into the current list page — there is no separate browser-navigable URL. It combines two conditionally-shown panels — "Assign Manuscript to Reviewers" (reviewer-managing mode, journal setting spAction = 1) and "Send Evaluation Result to Editor-in-Chief" / "Make Decision" (direct-decision mode) — modeled here as a single Review-stage row since the underlying screen and endpoint are one and the same.
Vestigial actions omitted as rows.
sp_editor.php's action switch also defines resubmit (manu_status = 3), edt (duplicate of assign, manu_status = 23) and redt (manu_status = 24) branches. None have a page title, a menu entry, or corroboration in spec — they read as leftover code carried over from a shared controller template rather than reachable pages, so they are omitted here rather than counted as rows. The mirror-image mismatch also exists and is likewise omitted: the page-title switch defines 16 further titles with no corresponding action-switch branch (pending_revise, pending_revise_due, revised, revise_declined, galley_proof, tech_editor, tech_editor_p, final_accept, published, final_reject, deleted, rejected, pending, invite/save_invite sharing one title, invited, in_housesp_editor.php lines 98-155). Visiting any of these _action values falls through to the switch's default: branch and renders the ordinary home screen with only a different <title>, so none render a materially different screen and none are counted as rows here either.