ojs-production-preparation

Prepares OJS article and issue metadata for publication from source documents.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/thathman/OJS-Production-Preparation-Skill --skill ojs-production-preparation-thathman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ojs-production-preparation
Source: https://github.com/thathman/OJS-Production-Preparation-Skill/tree/main/ojs-production-preparation
Command: npx skills add https://github.com/thathman/OJS-Production-Preparation-Skill --skill ojs-production-preparation-thathman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Preparing accepted manuscripts for publication in Open Journal Systems (OJS) requires manually extracting metadata, parsing titles and authors, formatting references, and configuring issue records, which is slow and error-prone. This Skill automates that post-acceptance production workflow by inspecting journal sources first and generating only the fields needed for the selected task. ## Core Features & Use Cases - Source-first journal detection: Inspects journal websites, published PDFs, and policy documents to detect ISSN, DOI prefixes, URL path conventions, licence policies, and Publisher ID usage before asking configuration questions. - Article publication preparation: Produces a fixed six-step response (Title & Abstract, Contributors, Metadata, References, Galleys, Issue) with correct OJS field semantics, including Prefix/Title/Subtitle splitting and concise semantic article URL Paths. - Issue preparation and QA: Builds Issue Data, Issue Galley, and Identifiers scopes, generates authorised issue descriptions, and runs production readiness checks returning ready, ready_with_warnings, or not_ready. - Use Case: An editor uploads a final accepted manuscript PDF and the journal website URL; the Skill detects the journal profile, extracts authors, affiliations, references, and metadata, and returns a copy-ready OJS publication record with validation warnings. ## Quick Start Prepare this accepted manuscript PDF for publication in OJS using the journal website I provide, and return the full six-step publication record.

Frequently Asked Questions about ojs-production-preparation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare an accepted manuscript for publication in OJS?

Provide the final manuscript PDF and optionally the journal website URL. The Skill detects the journal configuration, extracts title, abstract, authors, affiliations, references, and metadata, then returns a six-step publication record covering Title & Abstract, Contributors, Metadata, References, Galleys, and Issue.

How do I prepare an OJS issue for publication?

Supply the issue's articles and any cover or galley files. The Skill organizes output into Issue Data (Date Published, Volume, Number, Year, Title, Description, URL Path), Issue Galley, and Identifiers scopes, and can generate an authorised whole-issue description after inspecting every assigned article.

What is the difference between DOI, Source, and Publisher ID in OJS metadata?

The DOI identifies the submission itself, Source identifies another work the submission is derived from, and Publisher ID is an optional external database or deposit identifier. The Skill never places the submission's own DOI in Source or Publisher ID and detects each journal's Publisher ID conventions before use.

Does the Skill support QuickSubmit article entry in OJS?

Yes, it prepares QuickSubmit metadata including Section, Prefix, Title, Subtitle, Abstract, Keywords, References, and optional Dublin Core fields like Coverage, Type, Source, and Rights. Disabled or ignored fields are excluded, and the same metadata definitions used for article publication apply.

What are the limitations of automated OJS metadata extraction?

The Skill does not invent missing DOIs, ORCIDs, funding, ethics approvals, or data availability statements, and it flags ambiguous author name parsing instead of guessing. Scientific discrepancies such as inconsistent doses or units are reported for editorial review rather than corrected automatically.