Nasirus V2 is here: what's new in this release

The second major release of Nasirus is live. If V2 had to be summed up in one sentence: it brings a publisher’s entire working day — from the submissions desk to the accounting ledger — under one roof, making it the most comprehensive release we have shipped to date.

This post is not a feature-list dump; it is a summary of the problems we were looking at while building the release and what has changed as a result. For any topic you want to dig into, the Modules page has the more technical breakdown.

Four work types, one system

The backbone of V2 rests on a single decision: books, journals, articles, and edited-volume chapters are not jobs for separate programs — they are four faces of the same system. All four are managed under one identity, and every stage a work passes through, from submission to sale, appears on a single timeline.

What this means in practice: when an editor sits down in the morning, there is no “one program for the journal, another for the book files, a third for sales figures.” Which task is sitting with whom, and for how long, is visible in one list. Switching tools, reconciling spreadsheets by hand, digging through email attachments to find “which version was the latest” — none of that is a work step in V2.

Release highlights

Forms are designed in the dashboard. Submission and review forms are now built from the institution’s own dashboard. Required fields, conditional questions, different forms per work type — all of it is configuration, not a code change. Updating a live form is safe, too: in-flight submissions keep living on their own form version, and no submission is ever lost.

External review works without accounts. Sending a review request to someone outside your reviewer pool no longer means telling them to “register first.” The external reviewer sees the file through a secure link of their own, writes the review, and is done. No sign-up burden; full traceability.

Documents are generated from the institution’s own templates. Acceptance letters, rejection letters, publishing contracts, and receipts are auto-filled from the institution’s own Word templates and rendered to PDF. Every generated document carries a QR code, so its authenticity can be confirmed in seconds on a public verification page.

The storefront has been rebuilt. A published work goes on sale in a store running on the institution’s own domain: print, digital, or both together. Guest checkout, a digital library, free delivery of open-access titles, and search-engine-friendly multilingual pages all arrive with this release. There are three ready-made themes to choose from; logo, colors, and menus are managed from the dashboard.

Sales and accounting go hand in hand. When an order is paid, the invoice, the accounting record, the stock adjustment, and the author’s royalty accrual all fall into place on their own; nobody keys the same sale into four different places by hand. Returns close out with the same discipline.

Principles that did not change

V2 is defined as much by what we deliberately left alone as by what we added.

Decisions stay with people. The system drafts the acceptance letter, but the editor makes the acceptance decision; it prepares the print job, but the institution signs off on printing. Automation’s job is not to decide — it is to eliminate the drudgery around the decision.

Double-blind review is in the system’s safekeeping. Keeping reviewer and author identities hidden from each other is not a courtesy left to people’s vigilance; it is a rule the system takes ownership of.

And every step is on the record. Who made which decision, and when — the immutable audit trail has been a cornerstone of the product since V1, and it remains one in V2.

The story of three requests from the field

We set V2’s agenda in the field, not at a desk; three examples tell that story well.

“We can’t get external reviewers to open accounts.” This was the complaint we heard most often in the V1 era: you want to send a review request to a respected name outside your circle, and everything stalls at the “please register” step. Account-free review over a secure link was born directly from that complaint.

“What if we come across a forged document?” Fake acceptance letters dressed up in institutional letterhead are, sadly, one of publishing’s known afflictions. That reality is what put document security at the top of our agenda: thanks to sealed document generation with QR verification and a public verification page, you can confirm the authenticity of the letter in your hands in short order, without phoning the institution.

“The issue went out, and we forgot to update the store.” The manual steps of publication day — the archive page, article statuses, the storefront — are the tasks most prone to slipping through the cracks. In V2 we handed the tracking of those steps to the system; forgetting is no longer a work step.

Our ear is still to the ground today: the best feature of the next release will most likely be the solution to some publishing house’s everyday headache.

Migration and onboarding

We handle the entire setup; a new institution is up and running in short order. For institutions on V1, migration is planned and unhurried — no “everything changed over the weekend” surprises.

Nor do you have to switch on every module from day one; we decide together where it makes sense for you to start.

Questions and suggestions are always welcome: info@nasirus.com. If you would like to see the product through the lens of your own workflows, book a demo — in the demo, your workflow drives the screens, not us.