Public publishing
Journal Website
Own domain, journal identity, policies, editorial boards, announcements, issues, article pages, archives and scholarly metadata.
DijiderScholarly journal management and publishing system
The enterprise-grade operating system for scholarly journals.
Dijider connects the journal website, editorial management panel, automation robot and Core administration in one publishing ecosystem—from migration and submission to peer review, production, publication and reporting.
10+years of domain experience
10integrated product modules
16representative workflow states
4coordinated product surfaces
Four connected product surfaces
One publishing ecosystem, from public journal to central administration.
Website, Management Panel, Robot and Core work on the same governed publishing operation. Institutions gain central control while each journal preserves its own identity, archive and policies.
Editorial operation
Management Panel
Submission, files, author records, role-based assignments, reviewer pool, invitations, custom evaluation forms, revision rounds, decisions, issue preparation and reporting.
Automation
Dijider Robot
Scheduled checks, reviewer invitation follow-up, review and revision reminders, timeout monitoring, process alerts and auditable automated tasks.
Central administration
Dijider Core
Create and configure journals, manage independent data environments, roles, permissions, connections and portfolio-level operational controls from one centre.
Planned migration
Bring the existing archive without leaving the journal's history behind.
Accessible volume, issue, article, author, institution, date, page, DOI, metadata and full-text file records are mapped, transferred and checked according to the source system's technical structure.
System architecture
One product. Five coordinated layers.
Dijider separates the journal’s public identity from editorial operations while keeping metadata, files, automation and reporting connected to one governed record.
Journal-branded public portal
Own domain, policies, archives, articles and discovery metadata
Role-aware editorial application
Submission, review, decisions, production and communication
Shared publishing services
Business rules, metadata, files, identity and integrations
Automation & monitoring
Scheduled tasks, reminders, robots, operational alerts and audit events
SQL Server data foundation
Separated journal data, transaction integrity, indexing and controlled access
Product scope
The complete operation of a scholarly journal.
Ten connected modules carry a manuscript from first submission to permanent publication—without scattering the editorial record across unrelated tools.
01
Submission & author portal
Guide complete, policy-compliant submissions from first login to final files.
- Configurable submission steps
- Declarations, files and metadata
- Author-controlled revisions
02
Editorial screening & decisions
Turn journal policy into visible controls, assignments and accountable decisions.
- Initial and technical checks
- Editor and field-editor assignment
- Decision history and rationale
03
Reviewer discovery & peer review
Find relevant expertise, manage invitations and protect blinded evaluation.
- Topic-similarity suggestions
- Workload and history signals
- Custom evaluation forms
04
Revision & version control
Keep every file, response, request and decision connected to the manuscript record.
- Revision rounds
- Response-to-reviewer files
- Complete event history
05
Specialist editorial production
Coordinate technical, language, copy, layout and biostatistics work after acceptance.
- Role-specific queues
- Production file hand-offs
- Final publication control
06
Journal website & publication
Publish each journal through its own domain, visual identity, archive and policies.
- Issue, volume and archive management
- Stable article pages
- Journal-specific navigation and policies
07
Metadata, DOI & discovery
Produce structured, reusable metadata for scholarly indexes and library systems.
- Crossref-ready DOI deposits
- OAI-PMH and DOAJ XML
- RIS, BibTeX and preservation outputs
08
Communication & automation
Protect deadlines with governed templates, reminders and task automation.
- Journal-specific message templates
- Reviewer and revision reminders
- Automated operational alerts
09
Dashboards & reporting
See throughput, workload, delays and quality signals at journal and portfolio level.
- Nine operational views
- Role and stage performance
- Exportable management insight
10
Multi-journal administration
Operate a portfolio centrally while preserving journal-level identity, data and authority.
- Separated journal environments
- Central policy and service oversight
- Portfolio-wide reporting
Editorial lifecycle
Every transition stays visible and accountable.
The 16 states below show a representative lifecycle. Stages, permissions, forms and decisions can be configured according to each journal’s policy.
Draft
Author workspace
Submission received
Record and files created
Declarations & files
Completeness control
Initial screening
Scope and policy review
Editor assignment
Clear case ownership
Field evaluation
Specialist editorial review
Reviewer selection
Expertise and workload signals
Invitations
Acceptance and deadline control
In peer review
Blinded evaluation record
Reviews complete
Forms and recommendations
Editorial decision
Reasoned and traceable outcome
Revision
Author response and new version
Re-evaluation
Editor or reviewer follow-up
Accepted
Production package prepared
Production
Language, copy, layout and final checks
Published & archived
Public record and discovery outputs
Role-aware workspaces
The right context for every specialist.
Each participant sees the files, decisions, deadlines and actions relevant to their responsibility while the journal retains one continuous history.
Author
Submission, declarations, files and revisions
Reviewer
Invitation, blinded files and evaluation forms
Editor
Governance, assignments and final decisions
Field editor
Subject evaluation and reviewer coordination
Technical editor
File, metadata and publication readiness
Copy editor
Style, consistency and textual quality
Language editor
Language quality and terminology control
Layout editor
Typesetting, proofs and final publication files
Biostatistics editor
Method and analysis review where required
Journal manager
Configuration, teams, reporting and continuity
Operational intelligence
Less chasing. Earlier intervention.
Automation protects routine deadlines; reporting shows where editorial capacity, reviewer availability or production flow needs attention.
07
Task types
Governed automation
- Submission completeness checks
- Reviewer invitation follow-up
- Review deadline reminders
- Revision deadline follow-up
- Production hand-off tasks
- Metadata and DOI preparation
- Operational exception alerts
09
Management views
Operational reporting
Submission volume
Status distribution
Decision time
Reviewer performance
Reviewer workload
Editor workload
Stage turnaround
Publication output
Portfolio comparison
Publication & discovery
Your journal builds authority under its own name.
Every journal can publish through its own domain, visual identity, policies and archive. Article pages, structured metadata and index outputs strengthen the journal—not a generic umbrella portal.
See own-domain publishingHTTPSjournal.orgJournal-owned digital identity
OAI-PMH
Crossref DOI XML
DOAJ XML
RIS
BibTeX
LOCKSS
Copernicus
Google Scholar metadata
Machine-readable metadata supports search engines, indexes and library discovery services.
Frequently asked
Three questions institutions ask first.
Can every journal use its own domain?
Yes. The public journal identity, domain, navigation, policies and archive can remain journal-specific while the infrastructure is managed centrally.
Does Dijider support specialist editorial roles?
Yes. Author, reviewer, editor, field editor, technical editor, copy editor, language editor, layout editor, biostatistics editor and manager workspaces are supported.
Can institutions manage multiple journals?
Yes. Portfolio-level administration and reporting are combined with separated journal environments, permissions and identities.