Nasirus · Publishing management platform
A publisher’s processes in one system
Books, journals, articles and edited chapters are handled as four forms of the same publishing process rather than as the work of four separate programs. Nasirus manages all four under one identity and shows every stage a work passes through, from submission to sale, on a single timeline.
The starting point
In publishing, much of the work begins after the acceptance decision
In many publishing offices the working environment looks like this: one program for the journal, another location for book files, a separate spreadsheet for sales figures. Which task is waiting with whom, and for how long, does not appear in any single list. Identifying the final version of a file means searching through email attachments.
The consequence is a workload that is difficult to see: a storefront update overlooked on publication day, a reviewer delay noticed late, the same sales record entered by hand more than once. These are not individual errors; they follow from the absence of a shared system.
Nasirus brings this chain into one data model. Switching between programs, reconciling spreadsheets by hand and searching for file versions are no longer part of the daily work.
Lifecycle
The lifecycle of a work
Submission
By the author or the institution.
Review
Assignment, deadline tracking, board decision.
Acceptance and contract
Acceptance letter and publishing contract.
Production
Copy-editing, typesetting, cover, translation, illustration, print job.
Publication
Assigned to an issue, or published as a book.
Storefront and sales
A shop on the institution’s own domain; print and digital.
Accounting
Invoice, record, stock and royalty accrual handled together.
Who it is for
Intended institutions
An institution does not have to use the whole system. It is possible to start with the journal side only, with book production only, or with the storefront only.
| Primary | University presses and publication offices. Academic journals and journal groups. Publishing units of institutes, research centres and public research bodies. Publishing units of public institutions, local authorities, chambers and professional bodies. |
|---|---|
| Secondary | Commercial and independent publishers. The publishing arms of associations, foundations and learned societies. Educational publishers. |
Scope
What the system covers
One data model · one audit trail.
| Module | Scope |
|---|---|
| Works and metadata | Shared work and metadata management for books, journals, articles and edited chapters. |
| Submissions and calls | Work submissions and calls for edited volumes. |
| Review and board | Peer review and board decision processes. |
| Journals and issues | Journal, issue and article management; the journal’s own storefront. |
| Production and suppliers | Production operations from copy-editing to print, and supplier tracking. |
| Forms | Submission and review forms designed by the institution from its own panel. |
| Document generation and verification | Documents generated from institutional templates, with public verification. |
| Storefront and sales | Print and digital sales on the institution’s own domain. |
| Finance and accounting | Sales, invoices, stock and royalty records managed together. |
| Access and audit | Role-based access and an immutable audit trail. |
Module details and current features are published on the product site: nasirus.com
Deployment
Each institution has its own installation
In Nasirus the data model is not shared between institutions. Each institution has its own installation, which can be hosted on our infrastructure or run on the institution’s own server.
| Hosted | On-premises | |
|---|---|---|
| Data model | Dedicated installation | Dedicated installation |
| Where the data is kept | CND infrastructure | The institution’s own server; data remains there |
| Updates | Carried out by CND | Planned and carried out together |
| Suited to | Institutions that want to go live quickly | Public bodies and European institutions with data residency requirements |
On-premises deployment is a standard option, not an additional service.
Migration
What happens to existing data
We carry out the entire installation. A new institution can begin working within a short time. For institutions moving from an existing system, the migration is planned and carried out in stages rather than in a single cut-over.
Not every module has to be activated on the first day. The appropriate starting point is agreed together.
Multilingual operation: the management interface is available in Turkish, English and German. Storefront languages are set in the institution’s own settings, and further languages are tracked on the product roadmap.
See the system with your own workflow
A demo call follows your own process. Describe how your institution works today and we will show how the system handles that work.