← Publishing Policies & Trust CentreRecord continuity

Article Versions, Metadata & Digital Preservation

Digital preservation is more than routine backup. A responsible publisher plans for continuity of the scholarly record across system failure, platform migration, organisational change, transfer or closure.

BMU VenturesPublisher framework · Version 1.0Draft for formal adoption
Status and scope

This page states BMU-wide publishing principles. It does not replace journal-specific author guidelines, peer-review descriptions, fee schedules or discipline-specific ethical requirements. Operational claims apply only where implemented by the relevant journal or publisher system.

Version of Record

The Version of Record is the final formally published and citable version identified by the journal. Material changes to this version should be documented rather than silently overwritten.

Earlier versions

Preprints, accepted manuscripts, proofs and other earlier versions should be distinguishable from the Version of Record. Journal and repository links should allow readers to identify which version they are viewing.

Metadata

Core metadata may include title, authorship, affiliations, identifiers, dates, abstract, licence, funding, references, publication status and links to post-publication notices. Metadata should be maintained accurately because it supports discovery, citation and continuity.

DOIs and persistent identifiers

Where a DOI or other persistent identifier is assigned, the publisher should maintain the associated metadata and destination links as far as reasonably possible during platform changes or migrations.

Preservation versus backup

Backups are designed mainly for operational recovery. Preservation is a longer-term strategy intended to keep scholarly content accessible, authentic and interpretable despite technological or organisational change.

Verified preservation claims

BMU and its journals should name preservation services only where participation or deposit is verified. Installation of a preservation plugin or intention to join a service is not equivalent to successful preservation.

Transfer, suspension and closure

Transfer or closure should not be used as a reason to delete published articles, notices or metadata. Continuity planning should address DOI resolution, licences, correction history and access to the Version of Record.

Post-publication status

Corrections, expressions of concern and retractions should remain connected to article metadata and display. Preservation should maintain not only the original article but also the subsequent information needed to understand its current status.

Policy basis and interpretation

Adapted principally from JHWCR Policy 31. The BMU version generalises journal-specific material into a publisher framework and removes details that should remain title-specific. Where a journal publishes a more specific requirement that is consistent with these principles, the journal-specific rule governs that journal's submissions.

Questions about this framework may be sent to info@bmuventures.com.