Long-term continuity

Digital Preservation and Archiving

Digital preservation protects journal content from platform failure, organizational change, broken links, and ordinary technology loss. The journal should name only preservation services covered by active arrangements and should maintain its own tested backup, recovery, and content-transfer procedures.

Editorial illustration representing Long-term preservation, backups, and content continuity journal digital archiving policy
1Preservation2Backups3DOI continuity4Content transfer
Overview of the key elements involved in Long-term preservation, backups, and content continuity
01

More Than a Routine Backup

Operational backups help restore a working system after an incident. Independent preservation services support long-term access when the journal platform or publisher can no longer provide content.

Persistent identifiers remain useful only when their metadata and destination URLs are maintained. Article, issue, correction, license, and relationship metadata should be updated when the site changes.

Key routes

Use the Journal With Confidence

Each route connects to the record or policy needed for the next decision.

1

Platform resilience

Use tested backups, restricted administrative access, recovery procedures, and documented responsibilities.

Open related resource

2

Scholarly preservation

Deposit content and metadata only with services covered by current, verifiable arrangements.

Open related resource

3

Identifier maintenance

Keep DOI and other persistent-record metadata accurate across moves, corrections, and version changes.

Open related resource

Editorial standards and transparent records for Long-term preservation, backups, and content continuity
02

A Practical Continuity Plan

The journal should know what is backed up, how often, where copies are stored, who can restore them, and how recovery is tested. It should also plan for domain renewal, platform migration, credential transfer, and publisher transition.

A content-transfer plan identifies the files, metadata, licenses, notices, and technical documentation needed to move the journal without losing issue structure or article routes.

  • Maintain tested backups in more than one controlled location.
  • Document recovery roles and platform dependencies.
  • Keep issue, article, license, and notice metadata exportable.
  • Update persistent-identifier destinations after a move.
  • Publish only verified preservation claims.

Common questions

Questions Readers and Contributors Ask

Is a cloud backup the same as digital preservation?

No. A backup supports recovery of the operating system, while preservation addresses durable access and continuity of the scholarly record.

Should the journal display preservation logos?

Only when an active agreement or verified participation supports the claim.

What happens if the platform changes?

The journal should migrate content, metadata, notices, and links while maintaining persistent identifiers and redirects.

Sources

Standards and Further Reading

These external resources provide additional policy or practice context. The journal’s own published policies govern its workflow.

Preserve the Record Before a Crisis

Stable routes, exportable metadata, tested recovery, and verified preservation arrangements work together.