Navigation: Policies > Preservation, Privacy & Inclusive Access > Archiving, Preservation & Platform Continuity Policy
This policy sets out CorayNova Academic Press's standards for archiving, preservation, platform continuity, metadata maintenance, DOI linking, article landing pages, journal transfer, journal closure, merger, cooperation changes, and limitations of long-term access claims.
• Scope
This policy applies to journal pages, article landing pages, article records, metadata, DOI links, full text, supplementary materials, post-publication notices, preservation arrangements, platform continuity planning, journal transfer, closure, merger, and cooperation changes involving CorayNova journals.
• Who This Policy Applies To
This policy applies to authors, readers, editors, institutions, libraries, repositories, societies, partners, journal owners, technical support, and CorayNova publisher-level offices.
• Policy Statement
CorayNova seeks to preserve the scholarly record, maintain reliable article landing pages, support metadata continuity, and protect access information through responsible platform and preservation practices. CorayNova has enabled the PKP Preservation Network for eligible journals/content where supported by platform and journal configuration.
Long-term preservation and platform continuity involve best efforts, technical capacity, preservation service eligibility, journal configuration, metadata maintenance, agreements, and operational constraints. Preservation activity does not guarantee permanent availability of any third-party database, indexing service, institutional repository, external website, or discovery platform.
• Procedures and Standards
|
Area |
Policy standard |
|
PKP Preservation Network |
CorayNova has enabled PKP Preservation Network participation for eligible journals/content where supported by platform and journal configuration. |
|
Additional services |
LOCKSS, CLOCKSS, Portico, institutional repositories, or other preservation services may be adopted by individual journals or future agreements, but are not stated as active unless actually enabled. |
|
DOI and landing pages |
Published articles should use persistent DOI-based linking where assigned and maintain article landing pages where feasible. |
|
Metadata maintenance |
Article metadata, license information, publication status, correction/retraction links, and access information should be maintained where operationally feasible. |
|
Operational backups |
Operational backups support platform recovery and continuity but are not the same as independent long-term preservation. |
|
Journal closure, transfer, merger, or cooperation ending |
CorayNova will seek to preserve the scholarly record, metadata, DOI links, and access information according to obligations, platform capacity, preservation arrangements, and agreements. |
|
Limitations |
CorayNova does not guarantee permanent availability of third-party databases, indexes, repositories, discovery tools, external websites, or services outside CorayNova's control. |
Where journal-level preservation, transfer, closure, or platform continuity arrangements differ because of partner agreements or technical configuration, the relevant journal page should provide transparent information.
• Contact Route
Questions about preservation, article landing pages, metadata, DOI links, platform continuity, or technical access should be sent to support@coraynova.com. Questions about article record integrity, corrections, retractions, or publication notices should be sent to editorial@coraynova.com. Serious institutional-level matters may be sent to executive@coraynova.com.
• Related Resources
This policy should be read with For Institutions & Libraries, Metadata and Discoverability, Library and Repository Support, Corrections, Retractions, Expressions of Concern & Article Removal Policy, and Copyright, Licensing, Permissions, Reuse & Self-Archiving Policy.
• Policy Administration
|
Field |
Policy information |
|
Effective date |
August 15, 2026 |
|
Last reviewed |
August 15, 2026 |
|
Review schedule |
At least every 12 months, and earlier when legal, platform, publishing standard, operational, or business changes require review. |
|
Policy owner |
Technical Support, with Editorial Office responsibility for scholarly record integrity |
|
Version |
Version 1.0 |