Metadata Accuracy
Article, journal, book, chapter and proceedings metadata should accurately reflect the published scholarly record, including title, authorship, affiliation, abstract, identifiers, dates, licensing and publication status.
Scholarly Metadata Policy
XML, JATS and Metadata Deposit Policy
UnivColl Publications maintains this policy to support accurate scholarly metadata, DOI-ready publication records, structured article information, XML/JATS readiness and long-term discoverability of journals, articles, books, chapters and conference proceedings.
XML
Structured content readiness
JATS
Journal article tagging vision
DOI
Persistent identifier metadata
SEO
Search and discovery support
Policy Purpose
Reliable Metadata for a Responsible Scholarly Record
Metadata is the public and machine-readable identity of a scholarly work. It allows published research to be discovered, cited, verified, linked, preserved and updated. This policy explains how UnivColl Publications approaches article metadata, XML/JATS readiness, DOI metadata deposit, landing page metadata and post-publication metadata maintenance.
The policy applies at publisher level and supports journal articles, issue records, books, chapters, edited volumes, conference proceedings and future academic publishing programs managed under the UnivColl Publications platform.
Policy Snapshot
- Policy Owner UnivColl Publications
- Applies To Journals, Articles, Books, Chapters, Proceedings
- Primary Focus XML, JATS, DOI and Metadata Quality
- Last Updated 28 July 2026
Core Principles
Metadata Practice Built on Accuracy, Transparency and Continuity
UnivColl Publications treats metadata as part of the scholarly record, not as a decoration. It must be accurate, consistent, traceable and responsibly maintained.
Persistent Discoverability
Published records should remain discoverable through stable landing pages, canonical URLs, search-friendly metadata, DOI records where applicable and responsible long-term record maintenance.
XML and JATS Readiness
The publisher supports progressive development of structured XML and JATS-compatible workflows for article interchange, archiving, indexing readiness and future scholarly platform integration.
Transparent Limitations
The publisher does not claim XML, JATS, Crossref, DOAJ or indexing services for any article or journal unless the relevant service, deposit, record or workflow is actually active and verifiable.
Scope of Metadata
What This Policy Covers
The policy covers visible article information, machine-readable website metadata, DOI-ready deposit data, XML/JATS-ready editorial fields and post-publication status updates needed to protect the scholarly record.
✓
Journal article records, article landing pages, article PDFs and supplementary files where applicable
✓
Journal title records, ISSN information, publisher information, issue/volume records and archive pages
✓
Academic books, edited volumes, book chapters, conference proceedings and research monographs where published by the publisher
✓
Bibliographic metadata including title, subtitle, abstract, keywords, author names, affiliations, ORCID iDs, corresponding author details and publication dates
✓
Persistent identifiers including DOI, ISSN, ISBN, article ID, issue ID, URL, canonical URL and related identifiers where applicable
✓
Rights metadata including open access status, copyright statement, license information, repository/self-archiving information and publication permissions
✓
Research integrity metadata including funding, conflicts of interest, ethics approval, data availability, corrections, retractions, withdrawals and expressions of concern
✓
Machine-readable metadata formats used on publisher pages, including Highwire tags, Dublin Core, Open Graph, JSON-LD/Schema.org and future XML/JATS outputs
Core Metadata Fields
Essential Fields for Scholarly Discovery and Verification
The following metadata fields support article landing pages, citation tags, DOI deposit, indexing readiness, XML/JATS preparation and long-term publication record maintenance.
| Metadata Field | Purpose and Use |
|---|---|
| Title and Subtitle | Identifies the scholarly work clearly for readers, search engines, repositories and citation systems. |
| Author and Contributor Data | Records names, affiliations, author order, ORCID iDs where provided, correspondence details and contributor roles where applicable. |
| Abstract and Keywords | Improves discoverability, indexing readiness, search relevance and reader understanding of the article scope. |
| Journal / Book Context | Connects the item with journal title, ISSN, volume, issue, year, page range, article number, book title or proceedings record. |
| Publication Dates | Records received, revised, accepted, online published, issue publication and metadata update dates where available. |
| DOI and Persistent URLs | Provides persistent identification and supports durable linking between the publication record and external scholarly systems. |
| References | Supports citation linking, scholarly verification and responsible bibliographic transparency when references are prepared and deposited. |
| Licensing and Copyright | Clarifies open access permissions, copyright holder, license terms and reuse conditions. |
| Integrity Statements | Records declarations such as funding, conflict of interest, data availability, ethics approval, consent and corrections where applicable. |
| File and Format Links | Links readers and systems to PDF, HTML, XML, supplementary files, notices, datasets or related files where available. |
| Version and Status | Identifies whether the record is the version of record, corrected version, retracted article, withdrawn manuscript or updated publication record. |
| Publisher Contact | Provides a responsible communication route for metadata corrections, DOI issues, XML concerns and record maintenance requests. |
XML and JATS Readiness
Preparing Content for Structured Scholarly Exchange
JATS-oriented production depends on clean source documents, complete metadata, structured article sections, citation integrity and careful production review.
Article Front Matter
The publisher aims to keep article title, authorship, affiliations, abstracts, keywords, article type, dates, journal title, ISSN, DOI and license information ready for structured XML representation.
Body Content Structure
Research articles should be prepared with logical headings, paragraphs, tables, figures, citations and acknowledgements so that conversion into structured XML becomes technically manageable.
Back Matter and Declarations
References, funding, conflicts of interest, ethics approval, consent, data availability, author contributions and supplementary information should be recorded consistently.
Tables, Figures and Captions
Tables, images and captions should be prepared with clear numbering, descriptive titles, source information and file references to support future XML tagging.
References and Citation Links
References should be checked for completeness, DOI accuracy where available, consistent style and alignment between the article file and metadata record.
Progressive Implementation
Where full XML/JATS files are not yet published, the publisher may still maintain structured page metadata and improve XML readiness as part of ongoing production development.
Transparent implementation note: XML/JATS readiness does not automatically mean that every
published article currently has a downloadable full-text XML file. UnivColl Publications will
describe XML/JATS availability honestly on the relevant journal, article or production page when
such files are active, available and verified.
Metadata Deposit Workflow
From Submission Metadata to Long-Term Record Maintenance
A reliable metadata workflow connects author-provided information, editorial verification, production preparation, landing page publication, DOI-ready deposit and post-publication updates.
Metadata Capture at Submission
Basic metadata is collected from the submitted manuscript and author-provided information, including article title, author details, affiliation, abstract, keywords and corresponding author contact.
Editorial Verification
Editorial checks help confirm article type, journal scope, author order, declarations, ethics statements, conflict of interest disclosure and completeness of required publication information.
Production Metadata Preparation
After acceptance, production metadata is prepared for article landing pages, citation tags, PDF records, issue records, DOI assignment where applicable and future XML/JATS conversion.
Landing Page Publication
The publisher creates or updates the official article page with title, authors, abstract, issue details, DOI, PDF, citations, license, declarations and structured metadata.
DOI and Metadata Deposit
Where DOI registration is applicable, metadata is prepared for deposit or update through the appropriate registration workflow, with the landing page URL serving as the official resolution destination.
Quality Review and Correction
The metadata record may be reviewed for spelling, author order, DOI format, dates, issue data, file links, license information, references and correction notices.
Long-Term Maintenance
If article URLs, journal title information, corrections, retractions, licensing, files or metadata fields change, the publisher should update the website and applicable external metadata records.
DOI and External Metadata Records
DOI Metadata Must Remain Accurate After Publication
Where a DOI is assigned, the publisher should maintain the article landing page, bibliographic fields, publication dates, authorship data, identifiers, references, license information and status notices with care. DOI metadata should not be treated as a one-time entry; it may require correction, enrichment or URL updates over time.
Crossref-Style Metadata Discipline
Registration, Linking and Maintenance
The publisher supports the principle that scholarly metadata should identify the work, connect it to the official landing page and remain maintainable if a page, journal, issue, correction notice, file location or publication status changes.
Metadata Quality Control
Checks Before and After Public Release
Metadata quality is an editorial, production and technical responsibility. The following checks help reduce citation errors, indexing problems, broken DOI links and misleading records.
✓
Title, abstract and keyword fields match the final published article
✓
Author names, sequence, affiliations, ORCID iDs and corresponding author information are checked carefully
✓
DOI syntax, DOI URL and article landing page URL are reviewed before public communication
✓
Journal title, short title, ISSN, volume, issue, year, page range and article ID are consistent across page, PDF and metadata
✓
Published date, accepted date and issue period are checked for internal consistency
✓
References listed in metadata are present in the article and are not artificially added or manipulated
✓
Funding, conflict of interest, ethics, consent, data availability and author contribution statements are included where applicable
✓
License, copyright holder and open access status are visible on the article page or PDF where applicable
✓
Correction, retraction, withdrawal or expression of concern notices are linked to the relevant article record
✓
Sitemap, canonical URL, page title, meta description and structured data are reviewed for public discoverability
Corrections, Retractions and Metadata Updates
Metadata Must Reflect the Current Publication Status
When a publication record changes, the metadata should not remain misleading. Article pages, DOI metadata, XML/JATS records and notices should be reviewed so that readers can identify the correct version and status of the scholarly work.
Correction / Erratum
The article page and related metadata should identify the correction notice, corrected fields and relationship between the original record and the notice.
Retraction
The article status, public notice, DOI landing page and metadata should clearly show the retracted status while preserving the scholarly record.
Withdrawal
If a record is withdrawn before final publication, the publisher may keep an internal or public notice depending on publication stage, policy and ethical need.
Expression of Concern
Where an investigation is ongoing, a linked notice may be used to inform readers without making a final determination prematurely.
Metadata Correction
Minor errors such as spelling, affiliation, page range, PDF link or DOI display issues should be corrected promptly after verification.
Platform Migration
If content moves to a new system or URL, the publisher should update canonical links, DOI targets, sitemap entries and public landing pages.
Responsibility Matrix
Metadata Quality Requires Shared Responsibility
Accurate metadata begins with authors and continues through editors, production, publisher administration, technical maintenance and reader feedback. This shared responsibility helps protect the reliability of the scholarly record.
| Role | Responsibility |
|---|---|
| Authors | Provide accurate title, author order, affiliations, ORCID information, references, funding details, declarations, ethics approval and data availability statements. |
| Editors | Check that essential article information is complete, ethical declarations are present and any post-publication concern is routed for responsible handling. |
| Production Team | Prepare article pages, PDFs, issue records, citation metadata, DOI fields, XML readiness data and correction updates with careful attention to accuracy. |
| Publisher Office | Maintain publisher-level policies, metadata deposit workflows, DOI landing page continuity, website records and communication with authors or service providers. |
| Readers and Institutions | Report suspected metadata errors, broken links, DOI issues, file mismatches or status inaccuracies through the official publisher contact route. |
Machine-Readable Page Metadata
Article Pages Should Support Readers and Machines
UnivColl Publications supports structured public pages with clean titles, canonical URLs, descriptive meta tags, citation metadata, article identifiers, open access information and schema-ready information where applicable.
This helps human readers understand the article and helps discovery systems interpret the publication record more reliably.
Recommended article-page metadata layers: 1. Human-readable title, authors, abstract and citation 2. Highwire citation tags for scholarly search systems 3. Dublin Core metadata for bibliographic description 4. Open Graph and Twitter metadata for sharing 5. JSON-LD / Schema.org ScholarlyArticle data 6. Canonical URL and sitemap inclusion 7. DOI, PDF, license and version-of-record indicators 8. Correction, retraction or update notices where applicable
Transparent Limitations
No False XML, Indexing or Deposit Claims
UnivColl Publications will not state that a journal or article has JATS XML, Crossref registration, DOAJ metadata upload, indexing coverage, archiving deposit or any third-party service unless that activity is active, accurate and verifiable for the relevant record.
Responsible Communication
Claims Must Match the Actual Record
Metadata policy pages are not marketing promises. They are transparency tools. If a feature is planned but not yet active, it should be described as planned, progressive, under development or applicable only where verified.
Metadata Correction Request
How to Report XML, DOI or Metadata Errors
Authors, readers, librarians, institutions and indexing services may report metadata issues through the official publisher email. Please include clear information so the publisher can verify the issue and correct the record where appropriate.
Suggested metadata correction email format: Subject: Metadata Correction Request - [Journal / Article Title] 1. Name of reporting person: 2. Role: Author / Reader / Editor / Librarian / Institution / Other 3. Journal or publication title: 4. Article / chapter / book title: 5. DOI or article URL: 6. Metadata field needing correction: 7. Current incorrect information: 8. Correct information requested: 9. Supporting evidence or explanation: 10. Contact email for follow-up:
Related Publisher Policies
Connected Policies for Publication Integrity
These related pages support metadata accuracy, publication continuity, proof correction, security and responsible reporting of publication concerns.
Digital Preservation and Continuity Plan
View PolicyProof Correction Guidelines
View PolicyPublication Malpractice Report
View PolicyWebsite Security and Content Integrity Statement
View Policy
Frequently Asked Questions
XML, JATS and Metadata Deposit FAQ
Clear answers for authors, editors, reviewers, institutions, librarians and readers.
Does this policy mean every article is already available in full JATS XML?
No. This policy describes the publisher's metadata and XML/JATS readiness approach. Full XML/JATS publication may be implemented progressively according to journal workflow, technical capacity, article type and production stage.
Why is metadata important for journals and articles?
Reliable metadata helps readers, libraries, search engines, DOI systems, indexing services and citation tools identify, link, cite and verify the correct scholarly record.
Can metadata be corrected after publication?
Yes. Verified metadata errors may be corrected on the publisher website and, where applicable, in external metadata records. Substantive publication changes should follow the appropriate correction, retraction or update policy.
Are DOI records permanent?
A DOI should remain connected with the scholarly work, while its associated metadata and resolution URL may need long-term maintenance if the content moves or is updated.
How should authors submit metadata corrections?
Authors should email the publisher with the article title, journal name, DOI or article URL, the exact metadata field to correct, the correct information and supporting evidence where needed.
Does the publisher add references to metadata that are not in the article?
No. Reference metadata should correspond to references actually present in the published article. Artificial, manipulated or hidden reference metadata is not permitted.
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.