2) What we preserve

Datasets and code are typically housed in external repositories under the authors’ control. We preserve stable links and descriptive metadata and encourage the use of dataset DOIs for durable citation.

3) Layers of preservation

Resilience depends on redundancy at multiple levels. CJNCP applies the following complementary layers:

4) Integrity, fixity, and audit

We use cryptographic checksums and controlled workflows to protect against corruption and unauthorized changes.

• Checksums: A SHA-256 checksum is computed for canonical artifacts (PDF, XML, images, media) at ingest and stored with the preservation package.
• Scheduled verification: Fixity checks run on a rolling schedule (e.g., monthly for recent content, quarterly for backfiles) and after any storage migration.
• Variance handling: Any mismatch triggers immediate re-validation from alternate replicas; if a file is corrupted, the intact replica is restored and the incident documented.
• Change control: Editorial updates (e.g., corrections) use versioned assets; replaced files are assigned new checksums and linked notices.

5) File formats and sustainability

Long-term readability depends on open, well-documented formats. CJNCP selects formats widely supported across platforms and archivally favored when practical.

6) Metadata, identifiers, and discovery

Persistent identifiers and rich metadata are central to preservation and reuse.

• DOIs for articles and components: Each article receives a DOI with structured metadata; supplementary files are exposed via the article landing and internal anchors.
• People and places: We support author identifiers (e.g., ORCID iDs) and institutional identifiers where feasible. Funding and award numbers are recorded when provided.
• Machine access: Sitemaps and metadata feeds surface titles, abstracts, licenses, and update statuses to crawlers and discovery systems.
• Citation continuity: If URLs change (e.g., platform move), HTTP 301 redirects preserve inbound links from indexes, repositories, and citations.

Where authors link to external datasets or code, we encourage persistent identifiers (dataset DOIs, software archive DOIs) and bidirectional links between the article and the repository records.

7) Trigger events and access continuity

We plan for unusual scenarios that could affect access, from temporary outages to long-term platform changes. The following table outlines typical triggers and how continuity is maintained.

8) Corrections, retractions, replacements, and withdrawals

The integrity of the record requires that changes are transparent and durable.

• Corrections: Minor errors that do not invalidate conclusions are fixed with a linked notice; both HTML and PDF are updated with a stamp or note and the change log is preserved.
• Retractions: For unreliable results or ethical breaches, a retraction notice replaces the article landing with clear reasoning; the PDF may be watermarked “Retracted”.
• Replacements: When a corrected version is validated, the prior version is clearly marked and linked to the replacement; the DOI continues to resolve to the current VoR.
• Withdrawals (pre-publication): If a DOI had been reserved publicly, its landing page is updated to state that the manuscript was withdrawn prior to publication.

9) Roles, responsibilities, and governance

CJNCP conducts periodic reviews of preservation controls. Findings inform improvements to storage choices, verification cadence, and documentation.

10) Ethical, privacy, and legal considerations

• Privacy by design: Article files and supplementary materials must not disclose protected health information unless explicit permission allows public release.
• Takedowns: When legally required or where privacy is at risk, we remove or restrict access to specific files and provide a tombstone page explaining the reason, as permitted by law.
• Licensing: Open licenses travel with preserved copies. Replacement or correction does not revoke earlier license grants but updates the authoritative version.

11) Responsibilities of authors

• Use repositories that provide persistent identifiers for datasets, instruments, and code; include those identifiers in the manuscript and supplementary files.
• Ensure third-party materials (images, scales, questionnaires) have clearance for open access reuse compatible with the article’s license.
• Update external repository records when the article is corrected, retracted, or replaced to prevent out-of-date guidance in clinical practice.

12) Responsibilities of readers and reusers

• Cite the version of record DOI in clinical guidelines, protocols, educational materials, and policy documents.
• Check the article landing for update notices (corrections/retractions) before relying on findings in patient care.
• Respect the license terms when reusing text, tables, figures, and multimedia.

13) Service levels, monitoring, and reporting

While no digital system can guarantee absolute permanence, CJNCP strives for robust continuity.

• Monitoring: Platform uptime, error rates, and storage health are continuously monitored; alerts trigger operator response.
• Testing: Periodic restoration tests confirm that backups and replicas are usable; anomalies are remediated and documented.
• Transparency: In significant incidents affecting access or integrity, we aim to publish a brief statement summarizing the cause and corrective steps.

14) Frequently asked questions (FAQ)

15) Governance, updates, and contact

• Versioning: This policy is versioned; the date modified above indicates the current version.
• Review cycle: CJNCP periodically reviews preservation controls, with changes documented in the policy and, where relevant, announced to contributors.
• Contact: For questions about preservation, archiving deposits, or continuity, contact the editorial office via the journal’s official contact page. Include your article title, DOI, and a concise description of your query.