Digital Preservation and Journal Continuity

JGTSS participates in the PKP Preservation Network for eligible published material and requires a separate operational recovery programme. Effective 15 September 2026, this policy assigns responsibility for preservation coverage, deposit failures, system recovery and continuity of the social-science record.

Independent preservation service and deposit coverage

The PKP Preservation Network, also called PKP PN or PKP PLN, independently preserves eligible released content. The Preservation Coordinator must check the participating journal identity, service terms, package status and updated notices. Pending and failed transfers remain distinct from completed deposits; participation alone is not a statement that every item has finished preservation.

The publisher must keep a dated coverage ledger by issue, investigate gaps and reconcile it with provider holdings where a public record exists. Technical Support can explain the recorded coverage of a requested article or issue. DOI registration, a working journal website and an author’s repository copy serve different functions from independent preservation.

Published material and deposit boundaries

The public preservation package covers released article files, issue contents, bibliographic and licence metadata, authorised public supplements and linked corrections or retractions. Survey instruments and appendices are included when the journal has the necessary rights. Participant contact lists, raw identifying field notes, reviewer identities and fee-reduction evidence are excluded from public archive packages.

For social-media studies, ethnography and qualitative research, the managing editor checks whether a supplement inadvertently exposes participants or restricted source material. A citation to an external dataset is not a promise that JGTSS can preserve the dataset. Rights limitations and a durable source reference are recorded where direct deposit is unavailable.

Deposit checks and failure handling

The managing editor checks completeness after an issue is released or changed. The preservation coordinator reviews deposits after such changes and at least monthly, using the compatible OJS/PKP PN workflow and recording package IDs, status, covered items and unresolved errors. Transmission alone is not completion; the relevant provider confirmation is retained. Backlog failures receive an owner and a follow-up date.

The publisher appoints a continuity owner to review prolonged failures. During an outage the office investigates, protects the latest usable copies and gives an appropriate access update. A PKP PN dark archive is opened under its actual trigger procedure; it is not the source for ordinary server restoration.

Transfer cessation and access reports

A platform move or cessation must preserve original dates, identifiers, author rights, open licences and notice relationships. The publisher informs active authors, stops new solicitation if publication ends, arranges an authorised successor or applicable preservation route and updates DOI destinations and redirects. An unchanged work is not assigned a false new publication history.

Readers should report an inaccessible article, missing supplement or incorrect archive claim to jgtsssupport@jandoopress.com with the journal, issue and DOI or link. The office checks the relevant record and communicates the recovery position. Public preservation statements are revised as evidence changes.

Hosting and operational accountability

Amazon Web Services hosts the journal website. The Technical Support Officer must configure the OJS application, permissions, backups and restore procedures within the selected services. The required programme creates a consistent encrypted database-and-file copy daily, keeps 30 daily and 12 monthly versions in storage with separated access, performs monthly sample restores and exercises a full restore quarterly. The officer documents the configuration and actual test results; cloud infrastructure protection does not complete these application-level duties.

The recovery objectives are no more than 24 hours of lost updates and restoration of essential service within 72 hours. These are operating targets against which tests and incidents are measured, not guaranteed outcomes. Failed jobs or exercises require an assigned corrective action. Routine backup rotation must preserve the independent scholarly record. Report an unavailable issue or missing supplementary file to jgtsssupport@jandoopress.com.

Last updated: 16 September 2026