Frequently asked questions
Answers to the questions people ask most about what JournTech does, how it is installed and which systems it works with.
What is JournTech?
JournTech is an academic publishing platform built for university presses, journal editors and libraries in Turkey. It runs book and journal publishing in one place, from submission to the open-access catalogue. It is developed by HB Tech.
Who develops JournTech?
JournTech is developed, installed and supported by HB Tech. The contact address is info@hbtech.com.tr.
Which institutions is JournTech for?
JournTech suits universities that publish books and journals. Presses, publishing committees, journal editors, libraries and IT departments work on the same platform.
Our journals are on DergiPark. Do we have to leave?
No. In DergiPark mode the journal stays on DergiPark; JournTech syncs published issues and articles to your institution's site with the journal's consent and sends “Submit an article” to DergiPark.
Our theses are in our institutional repository. Can JournTech show them too?
Yes. JournTech imports theses from your institution's open repository (DSpace, for example) over OAI-PMH and syncs them every day. On the Institutional Archive's Theses page they can be filtered by type, institute, department and advisor. The record itself stays in your repository, and corrections are made there.
Does JournTech apply for the ISBN?
No. Your institution's authorised person always applies in the Ministry's system with their own e-Devlet login. JournTech prepares the request, gets the publishing board's approval, fills in the form through the extension, checks the assigned number and reminds you of the next deadlines.
Can we bring our existing catalogue?
Yes. Records are imported in bulk from Excel or CSV files and rejected rows are reported. Journals on DergiPark are synced over OAI-PMH.
Can people sign in with institutional accounts?
Yes. If your identity provider supports OpenID Connect, institutional sign-in can be turned on; ORCID sign-in is available too. Two-step verification can be required for privileged roles.
How is personal data protected?
Privacy notices, consent texts, erasure requests and retention periods are built in. Permissions are limited by role and every important action is written to the audit log. Hosting and backup locations are set in the contract.
What does an installation need?
JournTech runs in the browser; nothing is installed on users' computers. Each institution gets its own installation with its domain, logo and colours.
How is it priced?
We prepare an offer for your institution's publishing volume and needs. Write to us and we will look at it together.
Will our publications appear in Google Scholar?
JournTech puts the citation_* tags and the PDF link that Google Scholar reads on every publication page and keeps the sitemap up to date. Whether a publication is indexed is Google's decision.
Can it register DOIs?
Yes. Articles with their reference lists, as well as issues, books, chapters and proceedings papers, are registered with Crossref. This needs the institution's Crossref membership. Automatic registration starts in a test mode.
Does JournTech apply to TR Dizin?
No. The journal applies. JournTech offers a readiness checklist that follows the TR Dizin criteria for each journal and an export that prepares the files to upload to ODİS.
Which languages does it support?
The public site and the admin panel are in Turkish and English. Visitors switch the language at the top of the page.
Does it meet accessibility standards?
JournTech is designed to WCAG 2.2 AA. Public pages and panel views go through automated accessibility checks on every change.
Can we try JournTech?
Yes. The live demo shows the public site with sample content. For a presentation tailored to your institution, write to info@hbtech.com.tr.
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