A Double-Blind Peer-Review System for a Saudi University

Double-blind review is an integrity mechanism: authors and reviewers must never see each other's identities, while editors see everything. Encoding that into software means the permission model is the product — one leak in a query breaks the blindness. On top of that: submissions, scoring, issue assembly, payments and official acceptance certificates.

• Double-blind anonymity enforced by the data model itself
• Four roles — Admin, Editor, Reviewer, Researcher — with strict boundaries
• Automated evaluation scoring
• Official documents that must be verifiable

I built it in an Nx monorepo — React frontend, NestJS with TypeORM on PostgreSQL — with JWT authentication and advanced role-based permission handling designed around the blindness requirement. Research moves through submission, assignment, review and automated scoring; accepted papers get PDF previews, QR codes and generated acceptance certificates.

• Nx monorepo: React + NestJS + TypeORM + PostgreSQL
• Permission model built around double-blind anonymity
• Submission-to-scoring automated workflow
• PDF preview, QR generation, automated certificates

The journal's complete editorial machine, from submission to published issue.

• Double-blind peer-review workflows
• Research submission with automated evaluation scoring
• Issue management and online payments
• QR-verified acceptance certificates

The system is live at upafa-edu.net running the journal's editorial process for a Saudi university — academic-grade integrity requirements delivered as working software.

• Live at upafa-edu.net
• Editorial lifecycle fully digitized
• Review integrity enforced by design

Technology Stack