Scholarly Record Protection
Published records should remain stable, accessible and traceable so authors, readers, institutions and citation systems can rely on them over time.
UnivColl Publications supports responsible preservation of journals, articles, books, book chapters, conference proceedings, PDFs, metadata, policy pages and publication records for long-term academic access and record integrity.
Publication is not complete when a paper, book or proceedings volume goes online. The scholarly record must remain reachable, understandable, citable and connected with its metadata, policies, corrections and access routes.
This policy describes the internal archiving and digital preservation approach of UnivColl Publications for journals, issues, articles, books, chapters, proceedings, proceedings papers, PDFs, metadata and publisher policy pages.
Connecting University & College Research Worldwide
Stable URLs, archived issues, publication PDFs, metadata, citations and policy-connected updates.
Preservation should protect publication records, metadata, files, links and post-publication notices in a transparent and responsible way.
Published records should remain stable, accessible and traceable so authors, readers, institutions and citation systems can rely on them over time.
Title, authors, affiliations, abstract, keywords, DOI, ISBN, issue details, pages, dates, PDF links and citation details should be preserved with the publication record.
The version of record should remain identifiable, while corrections, retractions, updates and notices should be connected transparently.
Where publication policy permits, article PDFs, book files, chapters and proceedings records should remain reachable through stable URLs.
Website files, database records, publication PDFs, covers, images and metadata should be backed up and monitored to reduce loss risk.
UnivColl Publications should not claim membership in any external archive or preservation service unless that relationship is confirmed.
The policy covers the publisher’s core scholarly outputs and supporting pages across journals, books, chapters and proceedings.
Article pages, PDFs, abstracts, keywords, author metadata, DOI fields, references, citation metadata, view/download counts and issue connections.
Current issues, archived issues, volume/issue metadata, publication period, issue cover, table of contents and issue-level URLs.
Book title, subtitle, author/editor, ISBN, DOI where applicable, year, cover, abstract, keywords, PDF/access route, chapters and citation data.
Chapter title, author, abstract, keywords, parent book, page range, chapter DOI where applicable, PDF/access route and chapter citation.
Proceedings title, event identity, editors, organizer, venue, date, paper list, ISBN/DOI fields, PDF/access route and citation.
Ethics, peer review, open access, copyright, corrections, privacy, complaints, author guidance and other publisher policy pages.
Digital preservation is a continuous process involving metadata, files, links, sitemaps, backups and policy-connected updates.
A stable publication page is created with title, author/editor details, abstract, keywords, dates, pages, DOI/ISBN fields and access links.
PDF files, covers, images, article data, issue details, book data and proceedings metadata are stored in the website and CMS structure.
Records are connected through journal pages, archives, issue pages, book pages, chapter pages, proceedings pages and policy pages.
Published records may be included in relevant XML sitemaps to support discovery and long-term navigation.
Files, database records and metadata should be backed up and periodically reviewed for broken links, missing PDFs or incomplete metadata.
Corrections, retractions, withdrawals or notices should be linked with the original record according to policy.
Good preservation keeps scholarly metadata, access routes and post-publication notices connected in one reliable record.
Stable public URL
Canonical URL
Publication title
Author or editor names
Affiliation details where applicable
Abstract and keywords
Journal, book or proceedings title
Volume, issue, year or event details
Page range
DOI or ISBN where applicable
PDF or access link where policy allows
Citation format
Publication date
License or copyright statement
Correction or retraction links where applicable
Sitemap inclusion status
Preservation includes public pages, PDFs, metadata, covers, database records and publication policies.
Published article PDFs, chapter PDFs, book PDFs, proceedings PDFs and supplementary files where allowed.
Journal issue covers, book covers, proceedings covers and official publication graphics.
Public article pages, book detail pages, chapter pages, proceedings pages, policy pages and journal archive pages.
Publication metadata stored in CMS tables such as articles, issues, books, chapters and proceedings records.
Highwire, Dublin Core, JSON-LD, DOI metadata and other citation-oriented information where applicable.
Publisher policy pages, author guidance, editor guidance, reviewer guidance and public notices.
Regular backup and monitoring reduce the risk of file loss, broken records, incomplete metadata and access interruptions.
Backup website files and uploads regularly
Backup database tables containing publication records
Preserve article PDFs and issue cover files
Preserve book covers, book PDFs and chapter files
Preserve proceedings files and paper PDFs where applicable
Keep exported metadata where possible
Monitor broken internal links and missing files
Maintain clean folder structure for uploads
Avoid deleting publication files without policy review
Document correction, withdrawal or retraction actions
Check sitemap and robots configuration after major updates
Protect admin access and backup storage credentials
Long-term preservation requires stable URLs, readable metadata, archive navigation and clear notices when records change.
Published pages should avoid unnecessary URL changes. If a URL changes, a redirect should be used where possible.
PDF files should remain connected to their publication records where publication policy permits access.
Readers should be able to browse by journal, volume, issue, article, book, chapter, proceedings and paper records.
Important metadata should appear in readable HTML, not only inside PDF files.
Corrections, retractions and withdrawal notices should remain connected with the scholarly record.
A clear contact route should exist for reporting broken links, missing files or record errors.
Clear status labels help users understand whether a record is active, archived, corrected, retracted, withdrawn or under review.
| Status Label | Meaning | Responsible Use |
|---|---|---|
| Active Record | The record is published and available on the official website. | Normal published articles, books, chapters, proceedings and policy pages. |
| Archived Record | The record is no longer current but remains part of the permanent scholarly archive. | Past issues, older volumes, previous proceedings or older policy versions. |
| Corrected Record | The record has been updated or linked with a correction notice. | Use when a correction was issued according to policy. |
| Retracted Record | The record remains visible with a clear retraction notice where required. | Use only after formal retraction decision. |
| Withdrawn Record | A submitted or in-process item was withdrawn before final publication or according to policy. | Use according to withdrawal policy. |
| File Under Review | A file, link or metadata issue is being checked. | Temporary internal or public clarification when a record problem is reported. |
Preservation requires coordination between publisher, editors, authors, technical administrators and users who report access problems.
| Role | Responsibility |
|---|---|
| Publisher | Maintains website, publication records, policy pages, metadata, archives, backups and public communication. |
| Editors | Support accurate final records, issue integrity, correction awareness and metadata quality. |
| Authors | Provide accurate metadata, correct names, affiliations, references, permissions and final proof review. |
| Technical Administrator | Maintains hosting, database backups, uploads, sitemaps, redirects, file paths and technical availability. |
| Readers / Users | May report broken links, missing files, metadata errors or access problems through official contact routes. |
Preservation requires transparency. Silent deletion, broken archives and false preservation claims can harm authors, readers and publisher credibility.
Delete published article records without policy documentation
Remove retracted articles silently without a notice
Change publication URLs frequently after indexing or citation
Replace PDFs without version or correction awareness
Break article-to-issue or chapter-to-book links
Claim participation in external preservation services without confirmation
Leave dummy pages, placeholder records or test PDFs in public sitemap
Keep missing PDFs, broken links or incomplete records unaddressed
Hide serious corrections or retractions
Display outdated policy text without review where policies have changed
Archiving policy works together with ethics, correction, withdrawal, access, copyright and privacy policies.
Ethical responsibilities and scholarly record integrity.
Read PolicyPost-publication corrections, retractions and record updates.
Read PolicyWithdrawal of submitted or in-process records before final publication.
Read PolicyAccess, reuse and public availability of scholarly records.
Read PolicyRights, permissions and long-term reuse information.
Read PolicyProtection of personal data and responsible information handling.
Read PolicyLater the publisher CMS can track archive status, PDF availability, metadata completeness, sitemap status, broken links, DOI status and backup status for every article, book, chapter and proceedings record.
UnivColl Publications should claim participation in any external preservation service, archive, database or repository only after formal confirmation and accurate public documentation.
A serious publisher should protect publication records through clean archives, metadata, backups, stable URLs, correction links and responsible user support.
Basic questions about digital preservation, article archives, PDFs, corrections, retractions, broken links and long-term access.
It explains how published records, metadata, PDFs, covers, journal issues, books, chapters, proceedings and policy pages are maintained for long-term access and scholarly record integrity.
Published article records should remain accessible through stable public pages, archive pages and PDF links where publication policy allows.
Yes. Corrections should be handled transparently and connected with the original publication record according to the corrections and retractions policy.
Normally, retracted records should not be silently deleted. They should remain linked with a clear retraction notice where required.
No. This policy describes internal archiving and preservation practices. External archive membership should be claimed only when formally confirmed.
Users may contact the publisher with the publication title, URL and problem details so the record can be checked.
Yes. The policy covers journals, articles, books, book chapters, proceedings, proceedings papers and related metadata.
Published URLs should remain stable where possible. If a URL must change, a redirect should be used when feasible.
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.
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.
Editorial and publication decisions should remain evidence-based, policy-led and independent.
Acceptance depends on scope, originality, review suitability, ethical compliance and editorial decision.
Published records may be supported with structured metadata, DOI references and correction workflows where applicable.
Queries should include manuscript ID, DOI, transaction reference or policy concern details where available.