Persistent Scholarly Identification
A DOI should support long-term identification of a publication record and should resolve to a stable landing page controlled by the publisher or authorized platform.
DOI and Metadata Policy
Persistent DOI Identification and High-Quality Scholarly Metadata
UnivColl Publications supports reliable DOI assignment, accurate publication metadata, stable landing pages, citation-ready records, Google Scholar readiness, structured data, correction tracking and long-term scholarly discoverability.
DOI Prefix and Metadata Integrity
A DOI Is Valuable Only When the Metadata and Landing Page Are Accurate
DOI assignment helps identify a scholarly work, but the strength of the record depends on accurate metadata, stable URLs, correct author details, reliable dates, clear issue placement, valid PDF links, transparent license information and post-publication maintenance.
This policy explains how UnivColl Publications approaches DOI status, DOI assignment, citation metadata, Google Scholar readiness, book/chapter/proceedings metadata, stable URLs, metadata corrections and long-term record integrity.
Publisher DOI Prefix: 10.65919 | Connecting University & College Research Worldwide
DOI + Metadata
Identify. Link. Preserve.
Stable DOI, citation tags, schema, canonical URL, sitemap, PDF, license and corrections.
UnivColl Publications
Connecting University & College Research Worldwide
Core Principles
Principles Behind DOI and Metadata Management
DOI and metadata management should protect accuracy, citation, discoverability and long-term scholarly record integrity.
Metadata Accuracy
DOI and publication metadata should accurately describe the title, authors, affiliations, journal or book title, issue, pages, dates, license, references and publication status.
No False DOI Claims
A work should not be shown as DOI registered unless the DOI is actually assigned and intended to resolve to the correct public record.
Stable Landing Page
The DOI landing page should remain accessible, citable and updated with corrections, retractions, license statements, PDF links and metadata changes.
Discoverability Readiness
Metadata should support Google Scholar visibility, search engine indexing, citation parsing, sitemap inclusion and structured data readiness.
Correction Without Erasure
If metadata errors occur, the publisher should correct records transparently rather than deleting or hiding the scholarly record.
DOI Scope
Publish With Us
Publication Records That May Use DOI and Metadata Workflows
DOI and metadata principles apply across journals, books, chapters, proceedings and notices where applicable.
Journal Articles
Research papers, review articles, case studies, short communications and other article-level records may receive article-level DOI where applicable.
Book Chapters
Individual chapters may receive chapter-level DOI where the publication workflow, metadata quality and publisher policy support it.
Academic Books
Books, edited volumes, monographs and textbooks may receive book-level DOI or metadata records where applicable.
Conference Papers
Proceedings papers may receive DOI when the event, paper, author metadata and public record are suitable for persistent identification.
Special Issue Papers
Special issue articles should follow the same DOI and metadata rules as regular journal articles.
Corrections and Notices
Corrections, retractions or editorial notices may require clear linkage to the affected record and may have their own metadata where needed.
DOI Status Labels
Clear Language for DOI Status
DOI status should be transparent and should not mislead authors, readers or indexing systems.
| Status Label | Meaning | Responsible Use |
|---|---|---|
| DOI Pending | The record is published or prepared but DOI assignment, registration or activation is not yet completed. | Use when DOI is planned but not yet final. |
| DOI Assigned | The DOI string has been assigned to the record and should be checked for accuracy before final public display. | Use when DOI exists but final resolution or metadata update may still be under processing. |
| DOI Registered | The DOI is intended to resolve to the correct landing page with appropriate metadata. | Use only when the DOI record and landing page are ready. |
| DOI Not Applicable | The publication type, policy or stage does not require DOI assignment. | Use for content where DOI is not planned or not suitable. |
| Metadata Update Required | The record exists but title, author, issue, page, license, DOI URL or other metadata requires correction. | Use internally when metadata needs editorial or technical review. |
| Record Corrected | A metadata correction has been made and the public record should reflect the updated information. | Use when corrections have been completed and documented. |
Core Metadata
Metadata Elements That Support a Strong Scholarly Record
Complete metadata improves citation, discoverability, indexing readiness, author identification and long-term record management.
Publication title
Subtitle where applicable
Author names
Author affiliations
Corresponding author
ORCID IDs where provided
Abstract
Keywords
Journal/book/proceedings title
ISSN or ISBN where applicable
Volume and issue where applicable
Article/chapter/page range
Publication date
Received/revised/accepted dates where applicable
DOI status and DOI URL
License and copyright statement
Funding statement
Conflict of interest statement
Ethics and consent statement where applicable
Research data statement where applicable
References
PDF URL
Canonical URL
Article Metadata
Metadata Standards for Journal Articles
Article metadata should match article page, PDF, DOI, citation tags and archive record.
Citation Title
The public title should match article page, PDF, DOI metadata, citation tags and sitemap record.
Citation Authors
Author names should be consistent across article page, PDF, DOI record, Highwire tags and structured data.
Journal Identity
Journal title, short name, ISSN, volume, issue, period and publisher identity should be accurate.
Date Metadata
Published date, accepted date and received date should be formatted consistently where used.
PDF and Landing Page
The article should have a stable landing page and PDF link where applicable; DOI should point to the landing page, not only a file.
References and Citations
References should be visible, complete and suitable for citation parsing where possible.
Book and Chapter Metadata
Metadata Standards for Books and Chapters
Book and chapter metadata should connect parent records, contributors, ISBN, DOI status and publication details.
Book Title and Subtitle
Book metadata should clearly identify the title, subtitle, edition, series and academic category where applicable.
Editor or Author Details
Book records should identify authors, editors, contributors and affiliations accurately.
ISBN and DOI Status
ISBN and DOI information should be clearly separated and accurately displayed where applicable.
Chapter Linkage
Chapters should link to the parent book record and book metadata should link to chapter records where available.
Publication Details
Publisher name, place, year, edition, pages and license should be clear.
Indexing Readiness
Book metadata should support cataloguing, search visibility, schema and citation discovery.
Proceedings Metadata
Metadata Standards for Conference Proceedings
Proceedings records should clearly connect event identity, paper metadata and publication record.
Event Identity
Proceedings records should identify the conference, seminar, organizer, date, location or mode where relevant.
Paper-Level Metadata
Each proceedings paper should have title, authors, abstract, keywords, pages and DOI status where applicable.
Organizer and Sponsor Clarity
Organizer, sponsor or institutional roles should be disclosed without affecting editorial decision-making.
Proceedings Title
The proceedings title should be consistent across cover, PDF, contents page, website and metadata.
Publication Linkage
Proceedings papers should link to the parent proceedings record and relevant event record where available.
Review Statement
Review or selection process information should be clear and not misleading.
DOI Workflow
Track Manuscript
From Record Preparation to DOI Maintenance
DOI workflow should begin with a stable public record and continue after publication.
01
Publication Record Prepared
A stable landing page is prepared with title, authors, abstract, journal/book/proceedings identity, publication date and PDF link where applicable.
02
Metadata Verification
Editorial or production team verifies author order, issue placement, page range, dates, license, declarations, references and canonical URL.
03
DOI String Assignment
A DOI string may be assigned according to publisher format, publication type, year, journal/book identity and internal record number.
04
Landing Page Resolution Check
The DOI should resolve to the stable public landing page rather than an unstable file, temporary page or incorrect record.
05
Public Display
DOI is displayed on the article, chapter, book or proceedings page and in the PDF where applicable.
06
Post-Publication Metadata Maintenance
If author details, title, issue, pages, references, license or correction status changes, the metadata and public record should be updated.
DOI Format Guidance
DOI String Should Be Stable, Unique and Consistent
DOI construction should support internal clarity and long-term record identity.
| Element | Guidance |
|---|---|
| Prefix | Use the publisher DOI prefix accurately. Current publisher prefix: 10.65919. |
| Journal or Program Code | Use a consistent short identifier for the journal, book, chapter or proceedings program. |
| Year | Use the publication year or approved DOI year consistently according to publisher workflow. |
| Volume and Issue | For journal articles, volume and issue elements should match the official issue record. |
| Article or Chapter Number | Use stable internal numbering that will not change after publication. |
| No Reuse | A DOI string should not be reused for a different article, chapter, book or proceedings paper. |
Google Scholar Readiness
DOI Alone Does Not Guarantee Search or Scholar Visibility
Google Scholar and search visibility depend on crawlability, metadata, PDF access, citation tags, references and stable article structure.
✓
Stable article landing page
✓
Accessible PDF link
✓
Clear article title
✓
Visible author names
✓
Author affiliations where available
✓
Journal or book title
✓
Publication year
✓
Volume and issue where applicable
✓
Page range where applicable
✓
Abstract and keywords
✓
Highwire citation meta tags
✓
Dublin Core metadata where applicable
✓
ScholarlyArticle schema where applicable
✓
Canonical URL
✓
References section
✓
No blocked PDF or metadata by robots
✓
Clean URL structure
✓
Sitemap inclusion
Technical Metadata
Metadata Layers for Search, Citation and Structured Data
Strong pages use multiple metadata layers to help machines and humans understand the record.
Highwire Citation Tags
Article pages should include citation_title, citation_author, citation_publication_date, citation_journal_title, citation_pdf_url and related tags where applicable.
Dublin Core
Dublin Core metadata may support academic description, creator, date, publisher, identifier and rights information.
JSON-LD Schema
Structured data may describe articles, books, chapters, organization, breadcrumbs and FAQ where appropriate.
Open Graph and Twitter Cards
Social preview metadata should use correct title, description, image and URL.
Canonical Tags
Canonical URLs should prevent duplicate content confusion and point to the preferred public record.
Sitemap and Robots
Important public records should be discoverable through sitemap and not accidentally blocked from crawlers.
Metadata Corrections
How Metadata Errors May Be Handled
Metadata corrections should improve accuracy while preserving record transparency.
| Correction Type | Example | Handling |
|---|---|---|
| Minor Metadata Correction | Typo in affiliation, ORCID, keyword, page range or date formatting. | Correct public record and internal metadata where appropriate. |
| Author Name Correction | Spelling correction, initials, order mismatch or missing author component. | Verify with author and correct article page, PDF and metadata where needed. |
| DOI Link Correction | DOI points to wrong landing page or old URL. | Update DOI resolution and public record link. |
| Issue Placement Correction | Article placed in wrong volume, issue, month or year. | Correct issue metadata and update page, PDF and archive links. |
| License Correction | Wrong Creative Commons license or missing copyright statement. | Update public record and PDF where required. |
| Serious Record Correction | Wrong article title, author list, duplicated DOI or retraction status issue. | Handle under corrections and retractions policy with visible notice where appropriate. |
Stable URL Rules
Stable Landing Pages Protect Citations and DOI Resolution
Broken links damage reader trust, search visibility, DOI resolution and citation access.
✓
Avoid changing published article URLs after indexing
✓
Use redirects if a URL must change
✓
DOI should resolve to a landing page, not only a PDF file
✓
Article PDF URL should remain stable where possible
✓
Journal issue URLs should remain accessible
✓
Archive pages should link to published records
✓
Retraction or correction status should not break the DOI link
✓
Old links should not return blank pages
✓
Duplicate URLs should use canonical tags
✓
Public records should not be deleted casually after publication
Metadata Quality Control
Pre-Publication and Post-Publication Metadata Checklist
A final metadata check prevents many DOI, indexing and citation errors.
Title matches PDF and webpage
Author order matches PDF and webpage
DOI format checked
DOI URL checked
Volume and issue checked
Page range checked
Published date checked
License checked
Abstract checked
Keywords checked
References checked
PDF link checked
Canonical checked
Schema checked
Highwire tags checked
Sitemap checked
DOI and Metadata Decision Matrix
Possible Handling of DOI and Metadata Situations
Editorial and technical response depends on seriousness, publication stage and record impact.
| Situation | Risk | Possible Action |
|---|---|---|
| DOI planned but not yet active | Low if transparent | Display DOI Pending or keep DOI field blank until confirmed. |
| DOI assigned to wrong article | High | Stop display if needed, correct DOI resolution and update metadata. |
| Author metadata mismatch | Medium | Verify with authors and correct article page, PDF and metadata. |
| Article URL changed after publication | Medium to high | Add redirect, update canonical, sitemap and DOI landing page. |
| Google Scholar not detecting article | Discoverability issue | Check PDF access, Highwire tags, title, author display, references, robots and sitemap. |
| Wrong issue or volume metadata | Medium | Correct issue placement, archive links, PDF cover/page and DOI metadata where applicable. |
| Retraction or correction issued | High record integrity issue | Update public record, metadata, notice links, PDF status and DOI landing page. |
| Duplicate DOI used | Very high | Investigate immediately and correct according to DOI and publication ethics workflow. |
Not Supported
DOI and Metadata Practices UnivColl Publications Should Not Support
Misleading DOI or metadata practices damage citation trust, search visibility and the scholarly record.
!
Displaying fake DOI
!
Reusing one DOI for multiple different records
!
Showing DOI Registered when DOI is not actually ready
!
Changing published URLs without redirects
!
Deleting published landing pages after DOI assignment
!
Pointing DOI to the wrong article or file
!
Hiding correction or retraction status from the DOI landing page
!
Publishing with intentionally false metadata
!
Using misleading indexing claims in metadata
!
Changing author order without proper confirmation
!
Publishing metadata that conflicts with the PDF
!
Blocking article PDF or landing pages from crawlers by mistake
Metadata by Program
Minimum Metadata Expectations by Publication Type
Each program requires slightly different metadata, but accuracy and stability remain common.
| Publication Program | Minimum Metadata Expectation |
|---|---|
| Journal Article | Title, authors, affiliations, abstract, keywords, journal title, ISSN, volume, issue, pages, DOI status, PDF, references and declarations. |
| Book | Book title, author/editor, ISBN, DOI status where applicable, publisher, year, edition, pages, license and description. |
| Book Chapter | Chapter title, chapter authors, parent book title, editors, pages, DOI status, abstract/keywords where applicable and references. |
| Proceedings Paper | Paper title, authors, event/proceedings title, organizer, date, pages, DOI status, abstract, keywords and PDF link. |
| Special Issue Article | Standard article metadata plus collection/special issue title and guest-editor context where applicable. |
| Correction Notice | Notice title, affected article, date, correction type, clear link to original record and updated metadata. |
Related Policies
Policies Connected with DOI and Metadata Integrity
DOI and metadata management connects with discoverability, editorial workflow, corrections, archiving, repository and licensing policies.
Indexing and Discoverability
Metadata, schema, sitemap, Google Scholar readiness and search visibility.
Read PolicyEditorial Process
Workflow from submission to production, DOI status and final publication record.
Read PolicyCorrections and Retractions
Metadata corrections, DOI landing page updates and record notices.
Read PolicyArchiving Policy
Long-term access, stable records and preservation of published content.
Read PolicyRepository Policy
Self-archiving, repository links and version-of-record clarity.
Read PolicyCopyright and Licensing
License metadata, copyright statements and reuse information.
Read Policy
Future CMS Plan
Ready for DOI and Metadata Automation in CMS
Later the publisher CMS can track DOI prefix, suffix, DOI URL, canonical URL, Highwire tags, schema status, sitemap status, metadata review status and correction notes for every publication record.
metadata_id
record_type
record_id
paper_id
doi_prefix
doi_suffix
doi_url
doi_status
canonical_url
landing_page_url
pdf_url
citation_title
citation_authors
publication_date
volume_number
issue_number
page_range
license_type
schema_status
highwire_status
sitemap_status
metadata_review_status
metadata_correction_note
created_at
updated_at
Important DOI Notice
DOI Does Not Automatically Mean Indexing
DOI assignment supports persistent identification, but it does not guarantee Google Scholar inclusion, Scopus indexing, Web of Science indexing, citation, ranking or impact factor. Discoverability requires accurate metadata, crawlable pages, stable PDFs and external indexing decisions.
Metadata Excellence
Strong Metadata Makes a Publisher Look Serious and Search-Ready
Clean DOI, citation tags, structured data, canonical URLs and stable records help authors, readers, libraries and search systems trust the publication.
DOI and Metadata FAQ
Frequently Asked Questions
Basic questions about DOI, pending DOI, metadata correction, Google Scholar readiness, stable landing pages and duplicate DOI prevention.
What is a DOI?
A DOI is a persistent digital identifier used to identify and link to a scholarly record such as an article, chapter, book or proceedings paper.
Does every publication automatically receive a DOI?
No. DOI assignment depends on publication type, publisher workflow, metadata readiness and policy. Some records may show DOI Pending or DOI Not Applicable.
What does DOI Pending mean?
DOI Pending means DOI assignment or activation is planned or under process but not yet final for public confirmed display.
Where should a DOI point?
A DOI should generally resolve to the stable publication landing page where title, authors, abstract, PDF, metadata and correction status can be viewed.
Why is metadata important?
Metadata helps readers, libraries, search engines, citation systems and indexing services understand, cite and discover the publication record.
Can metadata be corrected after publication?
Yes. Metadata errors may be corrected. Serious corrections may require visible notices according to corrections and retractions policy.
Does a DOI guarantee Google Scholar indexing?
No. A DOI helps identification, but Google Scholar visibility depends on crawlability, metadata, PDF access, citation tags, references and many external factors.
Can the same DOI be used for two different papers?
No. A DOI should identify one specific scholarly record and should not be reused for a different publication.
Policy Pathway
Related Policies, Author Actions and Trust Pages
This policy is connected with UnivColl Publications' wider publishing ecosystem, including author guidance, editorial independence, publication ethics, metadata readiness and official support routes. Use the related links to move to the next practical step without relying on disconnected or informal information.
Author Guidelines
Open related page
Authorship Change Request
Open related page
Conflict of Interest
Open related page
Submit Manuscript
Open related page
Policies and Guidelines
Open related page
Publication Ethics
Open related page
Peer Review Policy
Open related page
Contact Publisher
Open related page
Transparency and Responsible Publishing
Policy Use Does Not Create Publication or Indexing Guarantees
UnivColl Publications uses policy pages to support transparent communication, fair editorial handling, author awareness and scholarly record integrity. Submission, payment, policy compliance or support communication must not be treated as a promise of acceptance, indexing, citation, ranking or any third-party database outcome.
Publication Ethics
Editorial and publication decisions should remain evidence-based, policy-led and independent.
No Guaranteed Acceptance
Acceptance depends on scope, originality, review suitability, ethical compliance and editorial decision.
Metadata Ready
Published records may be supported with structured metadata, DOI references and correction workflows where applicable.
Documented Support
Queries should include manuscript ID, DOI, transaction reference or policy concern details where available.