Use cases
JournTech gives every unit that works on publishing at a university its own workflow. This page walks through four typical uses.
University press and publishing committee
A book proposal reaches the press as an online submission. The editor does the initial check and picks reviewers from the pool. Reviews are collected in a double-anonymous process, and the publishing board records its decision in the system.
Once the book moves to production, typesetting, cover and imprint steps are tracked on the task list. An ISBN request is prepared and goes to the publishing board for approval. The authorised person applies with their own e-Devlet login. A browser extension, in pilot, carries the approved request into the Ministry's form. The assigned number is checked against the check digit and the International ISBN Agency's range file.
Entering the print date starts the 15-day legal deposit deadline. Copies, the EYDeS e-copy and the bandrol are tracked, and a reminder arrives before the deadline. Finally the book is published in the open-access catalogue with its cover, imprint, licence and citation formats.
Journal editing
A journal can work in two ways. With full management, submissions, review, decisions and issues all run in JournTech. In DergiPark mode the journal stays on DergiPark. Published issues and articles are synced to the institution's site over OAI-PMH, and the “Submit an article” button opens DergiPark's submission page.
The TR Dizin readiness checklist shows the criteria for each journal and links every gap to the screen that fixes it. When an issue is published, the files to upload to ODİS are prepared in one package. Articles are registered with Crossref for DOIs together with their reference lists.
The system reminds editors of the reviewer rules. It warns when fewer reviewers are chosen than the journal requires per round or when a reviewer is from the author's institution, and it suggests a third reviewer when reviews disagree.
Library
The library presents the institution's publications in one open-access catalogue. Every record has a permanent link, a Turkish and an English page, and a licence. Readers search by field, by year range and with synonyms.
Harvesters collect the records over OAI-PMH. Theses in the institution's open repository are imported over OAI-PMH too and synced every day. On the Institutional Archive's Theses page they can be filtered by type, institute, department and advisor. The original record stays in the repository, and corrections are made there.
An existing catalogue is imported in bulk from Excel or CSV files, and rejected rows are reported. Legal deposit copies of books are tracked as well.
IT department
IT manages users, roles and permissions. There are eleven built-in roles and permissions can be fine-tuned. If the institution's identity provider supports OpenID Connect, staff sign in with their institutional account. Two-step verification can be required for privileged roles.
Every important action is written to the audit log, which the auditor role can only read. Every uploaded file is scanned for viruses. Serious errors and security events are reported to the technical team at once.
The installation is prepared for the institution. Hosting and backup locations are set in the contract.
Last updated:
Let's plan a demo for your institution.
Tell us how you publish, and we'll show JournTech with your own examples.
Write to usinfo@hbtech.com.tr
Explore the live demo