Preservation

Preservation on The Sunil Abraham Project (TSAP) refers to the long-term protection, continuity, accessibility, and survivability of the project’s content, metadata, and research materials. As a static, Git-based digital archive, TSAP follows a preservation-oriented architecture built around open formats, distributed storage, version control, redundancy, and public accessibility. The project incorporates principles from digital archiving, scholarly preservation, and library science, including concepts such as the 3-2-1 backup rule, LOCKSS (“Lots Of Copies Keep Stuff Safe”), versioned preservation through Git, and the use of external archival services such as GitHub, Zenodo, the Internet Archive, and Archive.today. The goal is not only to prevent data loss, but also to ensure that the material remains readable, portable, verifiable, and accessible over long periods of time across changing technologies and platforms.

Last reviewed: May 2026

Status guide: Active Implemented and regularly used Experimental Implemented but still evolving Planned Proposed or under consideration Not Started Identified but not yet implemented

Web Archiving

Active

TSAP maintains ongoing public web archival workflows using external archival services including the Internet Archive Wayback Machine and Archive.today. Archival snapshots are created both manually and through browser-based tools. Rather than relying solely on infrequent bulk exports, TSAP follows a continuous preservation approach in which pages are archived incrementally over time. A small number of pages may be archived daily, while larger archival sessions are periodically conducted to preserve batches of pages together.

Current tools and services used include the Wayback Machine browser extension (Chrome, Firefox) and the Archive Page browser extension (Chrome, Firefox). Similar archival and preservation-oriented browser extensions and tools are also available for other browsers and platforms.

These workflows help reduce link rot risk, preserve historical page states, improve public survivability, maintain independent external copies, and provide resilience against accidental deletion or hosting failure. Because TSAP is a continuously evolving project, archival snapshots taken at different points in time also function as historical records documenting the evolution of the archive itself.

TSAP also includes direct archival links in the footer of every page, allowing readers to immediately access preserved versions of the current page through both the Internet Archive Wayback Machine and Archive.today. These links are generated dynamically using the page URL and form part of the project’s broader commitment to transparency, public preservation, and long-term accessibility.

Zenodo Preservation

Experimental

TSAP has begun publishing selected curated materials and archival collections through the Zenodo Archives portal. Zenodo provides DOI-backed scholarly preservation infrastructure, helping ensure long-term citability, archival stability, and independent preservation outside the primary website infrastructure.

Zenodo deposits may include curated datasets, archival compilations, preserved research publications, structured metadata collections, and static exports of historically significant materials. The use of DOI-backed archival infrastructure complements the project’s broader preservation strategy based on redundancy, distributed storage, and open formats.

Repository Preservation

Not Started

TSAP is intended to eventually incorporate repository-level preservation workflows based on Git and distributed version control. Such workflows may support long-term preservation, historical version tracking, offline backup creation, distributed cloning, and independent repository mirroring across multiple systems and hosting environments.

Because the project is built primarily using static files and open formats, repository-level preservation is expected to form an important part of the long-term archival strategy of TSAP. As of May 2026, these repository preservation workflows remain in the planning stage and have not yet been formally implemented.

Planned steps and workflows

Initial repository preservation workflows are expected to begin with manually downloading complete repository snapshots from GitHub using the repository’s “Download ZIP” export option available through the green “Code” button on the repository page. These downloaded ZIP archives may later be renamed using milestone or date-based naming conventions such as tsap-backup-2026-05.zip or tsap-1000-pages-archive.zip.

Planned preservation workflows may also include creating additional repository snapshots before major restructuring, large-scale editing, permalink modifications, CSS overhauls, automation experiments, or infrastructure changes. These snapshots may function as recovery checkpoints before significant modifications to the project.

Future repository preservation plans may additionally involve storing archival copies across multiple environments including local systems, portable storage devices, external storage media, and secondary computers in order to improve redundancy and disaster recovery capability.

Long-term plans may also include experimentation with distributed repository mirrors, Git-based preservation workflows, offline archival exports, and independent preservation redundancy across multiple hosting environments.

Offline TSAP

Planned

As part of its broader preservation and accessibility strategy, TSAP is also exploring approaches for offline access and low-connectivity distribution. This includes the long-term possibility of creating portable offline editions of selected TSAP content that can be stored, shared, and accessed without a continuous internet connection.

The project is particularly interested in lightweight, static, and preservation-friendly offline approaches that may support use in environments with limited connectivity, intermittent mobile data access, institutional restrictions, archival requirements, or disaster recovery scenarios. Possible future directions include downloadable static archives, compressed offline snapshots, portable HTML editions, local “internet-in-a-box” style distributions, and offline institutional mirrors.

TSAP is also exploring the idea of periodically creating milestone-based physical archival editions of the project, including portable storage device copies and optical disc editions such as CD or DVD archives. These may potentially be created after major milestones such as every 1,000 pages, at fixed time intervals such as once per year, or during historically significant stages in the development of the project. Such offline editions may function both as preservation snapshots and as portable archival records documenting the evolution of TSAP over time.

As of May 2026, these offline archival workflows remain in the planning and exploratory stage and have not yet been formally implemented.

Because TSAP is built primarily using static HTML, Markdown, YAML, and other open formats, much of the site’s content is inherently suitable for long-term offline preservation and portable archival distribution.

Redundancy and Mirror Infrastructure

Experimental

As part of its broader preservation strategy, TSAP also experiments with redundant deployment and mirror infrastructure across multiple hosting environments. This includes parallel static deployments intended to improve resilience, continuity, survivability, and disaster recovery capability in the event of hosting failures or service disruption.

Some secondary deployments are intentionally treated as infrastructure-level preservation mirrors rather than primary public access points. These mirrors primarily exist to support redundancy, preservation testing, continuity planning, and long-term archival resilience.

Future Plans

Planned

As TSAP continues to expand, additional preservation-oriented workflows, standards, and documentation systems may gradually be introduced over time. These future directions are intended to strengthen long-term accessibility, archival durability, metadata quality, portability, and historical continuity across the project.

Accessibility as Preservation

TSAP treats accessibility as an important part of long-term preservation. Future work may include broader accessibility audits, improved semantic structure, enhanced screen reader support, reduced-motion compatibility, improved colour contrast, and other measures intended to ensure that archived knowledge remains usable and accessible across different devices, abilities, and technological environments.

Open Formats

TSAP strongly prefers open and preservation-friendly formats such as HTML, Markdown, YAML, TXT, CSV, JPEG, and PDF wherever practical. Future preservation planning may further strengthen format standardisation, portability, export workflows, and compatibility with long-term archival systems and offline distribution methods.

Metadata Preservation

Future preservation work may place additional emphasis on the long-term preservation of metadata including publication dates, authorship information, categories, citations, structured data, archival references, and URL stability. Metadata preservation is considered important because contextual and descriptive information often becomes historically valuable over time.

Long-Term Link Stability

TSAP aims to minimise link rot and maintain stable long-term URLs wherever possible. Future work may include improved redirect systems, permalink audits, archival link expansion, canonical URL maintenance, and additional preservation-oriented approaches intended to support durable citation and long-term discoverability.