corpus-archive

Experimental Dataset Architecture: The repository structure, metadata tiers, category taxonomies, and catalog indexing formats are currently under active design and evaluation. All specifications, metadata keys, and JSON schemas detailed below represent representational examples and intended targets.

This repository serves as a structured digital textual archive preserving Hmar literature, historical accounts, school textbooks, dictionaries, parallel Bible corpora, and academic research repositories through high-resolution document scans and a 3-tier registry index.

This dataset is not final. It is actively maintained and updated at a deliberate, gradual pace as physical materials are digitized and documented. It is intended to serve multiple purposes beyond traditional static archival preservation and is not designed or suitable as a reliable off-the-shelf machine learning training dataset in its current state.

Maintained by the Hmar Heritage Foundation (https://hmarheritage.pages.dev) as part of the Hmar Heritage Archival Project.

---

Intended 3-Tier Maintainer-Centric Architecture

This dataset layout represents the intended target structure designed specifically for maintainer sanity to ensure physical format assets (data/pdf/, data/json/, data/repo/) are strictly organized, auditable, and isolated while maintaining lightweight registry pointers:

corpus-archive/
├── data/
│   ├── pdfs/                         # PDF Document Scan Directory (Active - 4 Items)
│   │   ├── metadata.jsonl            # TIER 2: Format Catalog Index
│   │   ├── 0001/ ... 0004/
│   │
│   ├── json/                         # Structured JSON Format Directory (Active - 7 Items)
│   │   ├── metadata.jsonl            # TIER 2: Format Catalog Index
│   │   ├── 0005/ ... 0011/
│   │
│   └── repo/                         # Multi-File Academic Research Repositories (Active - 1 Item)
│       ├── metadata.jsonl            # TIER 2: Format Catalog Index
│       └── 0012/                     # PMST-Hmar: Person Marking in Hmar (University of Bern)
│           ├── metadata.json         # Tier 3 Item Metadata Record
│           ├── readme.md             # Dataset documentation
│           ├── metadata.yml          # Original PARALEX manifest
│           ├── pmst-hmar_cells.csv   # Relational paradigm cells table
│           ├── pmst-hmar_forms.csv   # Inflected verbal forms & pronouns
│           ├── pmst-hmar_morphs.csv  # Tokenized IPA morphemes table
│           └── docs/
│               └── data_sheet.md     # Research data sheet
│
├── metadata.jsonl                    # TIER 1: Root Registry Pointer Index
├── viewer.jsonl                      # Dedicated Viewer Preview Catalog (6 Universal Fields)
└── README.md                         # Dataset card & documentation

---

Metadata Tier Definitions & Specifications

1. Tier 1 Metadata (Root Registry Pointer Index)

• File Location: metadata.jsonl (at repository root)
• Role: A simple, unbloated pointer registry that lists file paths for active Tier 2 format registries.
• Schema Example:

  {"format": "pdf", "count": 4, "path": "data/pdf/metadata.jsonl"}
  {"format": "json", "count": 7, "path": "data/json/metadata.jsonl"}
  {"format": "repo", "count": 1, "path": "data/repo/metadata.jsonl"}
  

2. Tier 2 Metadata (Format Catalog Index)

• File Location: data/{format}/metadata.jsonl (e.g. data/pdf/metadata.jsonl, data/json/metadata.jsonl, data/repo/metadata.jsonl)
• Role: A flat JSONL catalog indexing all items of that format. All Tier 2 metadata files share the exact same uniform schema structure across all formats (id, title, authors, category, language, file_path).

3. Tier 3 Metadata (Detailed Item Metadata Record: Format Dependent)

• File Location: data/{format}/{id}/metadata.json (inside each item directory)
• Role: Full authoritative metadata record for that single work. Tier 3 metadata is format-dependent.

Repository Tier 3 Schema Example:

{
  "id": "0012",
  "title": "PMST-Hmar: Person Marking in Hmar",
  "authors": ["Sandra Auderset", "Hunter L. Brown", "Jonathan Reich", "Pascal Gerber", "Muhammad Zakaria", "Linda Konnerth", "Lalbieklien Infimate"],
  "institution": "Institute of Linguistics, University of Bern",
  "category": "Linguistics & Dictionaries",
  "language": "hmr",
  "format": "repo",
  "file_path": "data/repo/0012/pmst-hmar_forms.csv",
  "source_repo": "https://github.com/isw-unibe-ch/PMST-Hmar",
  "license": "CC-BY-SA 4.0",
  "year": 2026,
  "description": "Linguistic database of Hmar person markers, verbal inflection paradigms, pronouns, tokenized IPA morphs, and phonetic sound mappings from the University of Bern.",
  "entry_count": 281
}

---

Catalog Table

ID	Title	Authors	Category	Target Language	Format	Direct File Link
0001	Hmar Grammar (1996)	P. N. Dutta Baruah, V. L. T. Bapui	Linguistics & Dictionaries	en	PDF	View PDF
0002	Hmar Tawng Inchukna (2012)	Vanlal Tluonga Bapui	Linguistics & Dictionaries	en	PDF	View PDF
0003	Nunrobu-8 (2020)	Hmar Literature Society	School Textbooks & MIL	hmr	PDF	View PDF
0004	Hmar Chanchin (1987)	H.B. Hrangchhuana	History & Ethnography	lus	PDF	View PDF
0005	Hmar Tawng Inchukna (2012)	Vanlal Tluonga Bapui	Linguistics & Dictionaries	hmr	JSON	View JSON
0006	Pherzawl Hmar-English Lexicon	Dr. John H. Pulamte	Glossary	hmr	JSON	View JSON
0007	English-Hmar Dictionary	Upa J. Lungawi	Glossary	en	JSON	View JSON
0008	English-Hmar Vocabulary	Dr. Thanglung	Glossary	en	JSON	View JSON
0009	Foundation Primer Wordlist	Hmar Heritage Foundation	Glossary	en	JSON	View JSON
0010	Pathien Lekhabu Inthieng (Hmar CLB)	Bible Society of India, HCLF	Religion & Theology	hmr	JSON	View JSON
0011	Pathien Lekhabu Inthieng (Hmar OV)	Bible Society of India	Religion & Theology	hmr	JSON	View JSON
0012	PMST-Hmar: Person Marking in Hmar	University of Bern (S. Auderset et al.)	Linguistics & Dictionaries	hmr	Repo	View Repo

---

Rights & Usage

This archive is provided for non-commercial research, linguistic study, and cultural preservation.

Copyright remains with the original authors, societies, and publishers (e.g., HLS, HSA, AIRTSC, CIIL, University of Bern). Rights holders may request removal or modification of materials through the repository discussion channel.