Count the issues. Check the route. Verify the record.
DergiPark DOI service: can your journal apply yet?
Readiness for DergiPark's DOI service needs more than an issue count. Separate journal eligibility, service approval and each article's DOI verification.
AcademicFix Editorial Team · Sources checked
A total can hide a missing prerequisite
Nine articles. Two issues. One unresolved check.
The invented 5-and-4 example below shows why an issue count is only one part of a readiness check.
Does the total hide a shortfall?
Keep the two counts separate before deciding what to do next.
Work through the example 02 / Separate the stages3 checksEligible, approved or registered?
These are three editorial checkpoints, not interchangeable status labels.
Build an audit trail 03 / Read the identifierİZ ≠ DOIWhich identifier are you seeing?
A submission-stage İZ does not establish that an article has a registered Crossref DOI.
Distinguish the recordsFor journal editors and publishers using DergiPark, and authors asking about an article's identifier. This is a dated reading of platform rules and a practical verification workflow. DergiPark decides service applications. The guide does not assess a particular journal, register an identifier or promise approval.
1. Check prerequisites before choosing a route
DergiPark describes its qualifying DOI service as free through Crossref sponsorship. That is this programme's arrangement; Crossref says sponsors set their own criteria and may charge for services. Do not generalise one programme's terms to every sponsor. [2] [3]
| Check | Requirement |
|---|---|
| Shared prerequisites | DergiPark hosting; a current, regular archive; at least five articles per issue; journal-specific mandatory pages. |
| Index route | Listing in TR Dizin, DOAJ, Web of Science or Scopus. |
| Process route | Editorial processes run in DergiPark; at least two issues for issue-based publication, or one year for continuous publication. |
| Applicant | The Baş Editör (Editor-in-Chief) appointed by the Bilimsel Yayın Koordinatörü (Scientific Publication Coordinator). |
The process route also examines meaningful reviews, two reviewer decisions, major-revision follow-up, review durations and reviewer/author diversity. [1]
Editorial recommendation: label unresolved evidence explicitly. “We think the journal is indexed” is not the same as a current record identifying the correct title and ISSN. Keep the supporting record beside the route decision.
2. Test a two-issue claim without inventing a research result
| Issue | Illustrative count | Shortfall against 5 |
|---|---|---|
| Issue A | 5 | 0 |
| Issue B | 4 | 1 |
| Total | 9 | 1 |
The calculation is 5 + 4 = 9; the second issue is one below five. Adding the counts together does not remove that per-issue gap. This checks one prerequisite, not the review process or the application outcome. [1]
The useful decision: record the gap and review the legitimate publication plan before claiming readiness. Do not manufacture an article, bypass review or add irrelevant material to reach a quota. Even a hypothetical 5-and-5 pair would leave the other checks unresolved.
3. Keep eligibility, approval and registration in separate rows
After acceptance, complete DergiPark's Crossref onboarding. Approved service covers qualifying original, unpublished articles prospectively, not backdating or cover/editorial material. Rejected applicants can reapply after six months. [1]
Crossref's sponsored application uses a dedicated link from the sponsor. Agree who will register and maintain records; avoid creating an unrelated membership application while the sponsored process is underway. Generic Crossref onboarding estimates are not a promise about DergiPark's entire review. [3]
An editor's working log can contain three separate rows: evidence supporting the chosen route; the service decision and its date; and each article's registration result. Add an owner and next action to every unresolved row. These are our suggested audit fields, not claimed DergiPark button names.
DergiPark's policy requires correct, complete metadata consistent with the full text. For a practical cross-check, compare the title, author list, journal, date and landing page against the final article. Preserve the exact error or support response if a record fails. [2] [4]
4. İZ and DOI can coexist without meaning the same thing
DergiPark's February 2026 announcement says İZ is assigned at submission and complements DOI workflows. İZLİK describes early identification and lifecycle tracking, including integration with the DergiPark archive. An İZ can therefore exist before a publication decision. It is not evidence of acceptance or a substitute for checking whether a Crossref DOI was actually registered. [6] [7]
When a journal rejects a submission and a new evaluation begins at another journal, DergiPark's announcement describes a new, independent İZ. Record the identifier shown for the relevant process rather than assuming every stage shares one code. [6]
A useful author enquiry: “Which identifier is shown on the article record, and has its DOI registration completed?” Include the article's public URL when contacting the journal. Keep unpublished manuscript contents and account credentials out of a public enquiry.
5. Check the destination and the metadata, not just the string
DOIs are registered through registration-agency services; the DOI Foundation does not require you to join the Foundation to use an agency. The restrictions of this journal programme are not a universal ban on identifiers for other communities or kinds of object. [8]
For a DOI supplied by the journal, open its https://doi.org/ link and compare the resulting article record with the final publication. Keep an existing DOI if the content moves; update its associated metadata and destination through the responsible workflow. Do not mint a second DOI as a workaround for an existing record. [4]
When a link fails: capture the link, error and check time; ask the journal which registration or metadata issue remains. A fixed 24–72-hour waiting rule cannot diagnose every failure. This guide makes no promise that waiting alone will resolve it.
6. Leave a checkable handover
This checklist is our editorial workflow, applying the linked rules without replacing the platform's decision.
- Keep a dated copy or link to the current official rule and identify the route you intend to use.
- Record each prerequisite as met, not met or unresolved, with a link to the supporting journal record.
- Have the authorised journal account review the application; do not share passwords or submit through an unrelated role.
- After service approval, keep a separate article-level log of registration results, DOI links and metadata corrections.
- Check the published landing page against the final article, then repeat the check after a platform move or correction.
Two questions to settle before proceeding
Does meeting the issue count guarantee a successful application?
No. The route, shared prerequisites, process evidence and authorised applicant still matter. Use the matrix as a readiness check, not an approval certificate. [1]
Sources and verification
Relevant source sections were read on 15 October 2026. The service rules and policy are in Turkish; the İZ announcement also has an official English version. The worked counts are invented and were recomputed. Panel menu paths and guaranteed processing times are intentionally not asserted.
- 1DergiPark: DOI service
Current Turkish service rules: shared prerequisites, two eligibility routes, applicant role, approval and permitted use.
- 2DergiPark policy, version 1.0
Policy dated 5 May 2026: sponsored DOI service, journal information and accurate metadata responsibilities.
- 3Crossref: Working with a sponsor
Sponsor-specific eligibility, dedicated application links and allocation of registration responsibilities.
- 4Crossref: Constructing your DOIs
Persistent, unique identifiers; maintain metadata and continue using an existing DOI when content moves.
- 5Crossref: Integrity of the scholarly record
Metadata supplies context; a DOI record alone is not a quality signal.
- 6DergiPark: Integration of the IZ identification system
English announcement dated 13 February 2026: submission-stage identifiers complement DOI workflows.
- 7İZLİK: Academic identification infrastructure
Official platform description of early identification, lifecycle tracking and DergiPark integration.
- 8DOI Foundation: Frequently asked questions
Registration agencies, services, different identifier communities and DOI resolution.
Follow the record into the reference list
- Handle a reference when an article has no DOI
- Check the journal's current author instructions
- Draft an APA reference from a verified DOI — inspect the returned metadata before using it.