CASE FILE: Sakya Research Center

role: Maintainer
period: 2021–ongoing
stack: Ruby on Rails, PostgreSQL, legacy infrastructure
about: maintenance of a long-running research platform
url: sakyaresearch.org

Summary

The Sakya Research Centre is an academic platform for Tibetan historical and literary research. It catalogues persons, places, sources, images, and electronic texts related to the Sakya tradition — thousands of records spanning centuries, cross-referenced and filterable by affiliation, period, and topic. It’s been live since 2012.

I took over maintenance in 2021. The application is an older Rails system backed by PostgreSQL, with a traditional server-rendered frontend. The work is not glamorous: keeping dependencies updated, fixing bugs, making small improvements, ensuring the hosting stays stable, and occasionally adding features.

Sakya Research Centre persons index showing a filterable list of historical Tibetan figures with affiliations and dates — The persons index — a filterable catalogue of historical figures with affiliations, dates, and cross-references to related records.

The platform indexes over 3,000 persons, hundreds of places and monastic sites, source texts, and a visual archive of photographs and manuscript images — each record interlinked with related entities across the database.

Sakya Research Centre image detail page showing a photograph of Dingpoche Monastery with metadata, topics, and place references — An image detail record — a photograph of Dingpoche Monastery with structured metadata, topic tags, and linked place units.

The maintenance work touches the full stack in miniature: Rails upgrades, dependency patches, server administration, data backups, occasional schema changes, and the kind of careful refactoring you do when the codebase is old enough that you cannot just rewrite it without losing institutional knowledge encoded in the code itself. The system continues to operate and evolve without pretending a rewrite is automatically the answer.