Rongmei Hymnal

Background

Preserving songs without separating them from their community context

Rongmei Hymnal is a digital reading and preservation project. Its purpose is to bring multiple Rongmei and community song collections into one searchable space while accounting for readers who may have inconsistent connectivity. The project is more than an interface: the long-term value depends on the accuracy of text, collection provenance, numbering, attribution, and the ability to correct records without losing their source context.

The point is to make the collections easier to search without stripping away their source, numbering, or community context. The app is deployed, but editorial review is still ongoing; a working interface is not proof that every text has been checked or approved.

Collection overview

Three registered collections; 1,271 records in the documented snapshot

The project’s recorded validation snapshot lists three collection counts: 305, 930, and 36 songs, for a total of 1,271. Counts can change as collection metadata or records are corrected, so re-check the live registry and repository before quoting these numbers in another publication.

A combined search interface improves discovery, but it should not erase differences between source books, editions, numbering systems, or attribution. Each collection needs to retain its identity and enough provenance for a reviewer to trace a questionable record.

Architecture

Separate the application shell from the song data

The project uses a static web application and progressive web app approach. The interface, collection registry, collection metadata, song records, local preferences, service-worker cache, and explicit full-library downloads have separate roles. That separation makes it possible to update the application without treating all content as one opaque bundle.

• The registry identifies each collection and points to its metadata and data.
• Structured JSON records make collections easier to validate and regenerate than manually copied text embedded in interface code.
• Local preferences can support favourites, history, or reading choices without requiring an application account.
• The service worker supports the application shell, while the in-app download workflow stores the song collections for offline reading.
• Validation checks structure and expected counts; it cannot prove that every word, title, attribution, or translation is editorially correct.

Practical guide

Run the project locally

Prerequisites

• A current browser.
• Git and Python 3 (or another static HTTP server).
• Access to the repository and appropriate source material for any editorial correction.

Steps

git clone https://github.com/Guang84/RongmeiHymnal.git
cd RongmeiHymnal
python3 -m http.server 8000

1. Open http://localhost:8000 and check that the registered collections load.
2. Search several terms across collections and open individual records.
3. Test reading controls, favourites, history, and local preferences.
4. For offline testing, use the application’s own download action and wait for completion before disconnecting.
5. Reconnect and inspect how application or collection version changes are detected.

Use HTTP for local testing; opening files directly through file:// does not reproduce service-worker and offline behaviour reliably.

Editorial workflow

Correct text from a source, not from assumption

1. Identify the collection, record identifier, title, number, and current text.
2. Find the best available source scan, printed edition, or approved reference.
3. Compare the proposed change carefully, including punctuation, spelling, line breaks, and alternate numbering.
4. Preserve enough provenance and notes to explain an uncertain correction.
5. Run JSON/schema and count validation, then test search and reading behaviour.
6. Ask an appropriate community reviewer to resolve cultural or linguistic uncertainties when needed.

Do not silently “correct” unfamiliar wording just because a spellchecker or language model suggests a more familiar phrase. A structurally valid record can still contain a transcription or rights error.

Offline use and rights

Offline availability does not grant redistribution rights

Readers may need access without a stable connection, but publishing software under an open-source licence does not automatically make every included song text, translation, arrangement, recording, or illustration free to redistribute. Keep software licensing separate from content permissions and attribution.

Test the installed application after a full library download, then test what happens when storage is limited, a download is interrupted, or a later collection version is available. Keep a visible path for users to report mistakes and rights concerns.

Validation snapshot

Technical checks and editorial checks answer different questions

The recorded snapshot dated 20 September 2026 documents three registry entries resolving to 305, 930, and 36 records, with core JavaScript syntax and public JSON parsing checks. Those checks support consistency of the data shape and counts. They do not certify the spelling, wording, attribution, or rights status of each hymn.

For current status, source and contribution details, use the Rongmei Hymnal repository and the deployed application linked from the repository. The project remains a living digital edition rather than a claim that every record is a final authoritative edition.

Source and current status

Explore the project

Active · deployed · editorial review ongoing. This page documents the public record of the project. For the current code, dependencies, licence, issues, and setup steps, check the linked repository before using it.

For corrections, contact GLab Ent. or raise it in the linked repository.