Preservation and Backup Transparency
This page provides transparent information about IJAICET's current backup, restoration, and long-term preservation readiness.
Purpose
The purpose of backup and preservation work is to protect published scholarly content, support website recovery, and maintain access to article metadata, article files, and issue records.
What Is Backed Up
- OJS database content, including journal settings, static pages, article metadata, issue metadata, and workflow records.
- Important public website files such as sitemap, AI-readable information files, stylesheets, issue images, and author resources where relevant.
- Deployment-related backups before major website or policy updates.
Backup Timing
Backups are created before major deployment changes, policy updates, public-page updates, and metadata changes that affect the live journal website. The editorial and technical team may also create manual backups before sensitive operational changes.
Restoration Approach
If a technical issue affects journal availability or public content, the technical team may restore the most recent known-good database or public file backup, clear OJS cache, restart required services, and verify public URLs after restoration.
Limitations
Operational backups support service restoration but are not the same as formal third-party preservation. IJAICET will not claim participation in LOCKSS, CLOCKSS, Portico, PKP Preservation Network, or another preservation network unless active participation is confirmed.
Future Preservation Plan
IJAICET intends to strengthen long-term preservation by evaluating recognised preservation services, improving DOI and metadata completeness, keeping stable article landing pages, and maintaining complete issue archives.
Contact
Preservation and backup questions may be sent to editor.ijaicet@gmail.com.