Use this structure whenever a new PDF, court order, hearing notice, report, or missing source is added. The goal is to keep every entry searchable, source-linked, and auditable.
1. Minimum fields for every document
- Date: ISO format, for example
2025-06-03.
- Document number: notification/order/memo/case number exactly as printed.
- Document type: notification, order, corrigendum, hearing notice, court order, report, act, roster, certificate guideline.
- Status: current, withdrawn, superseded, legacy, missing, draft, or verification-needed.
- Short summary: one sentence describing legal or documentary effect.
- Source: published PDF URL plus source authority, when known.
2. Evidence checks before marking complete
- Does the PDF text match the notification number, date, and printed title?
- Does it add, amend, withdraw, classify, or merely implement another document?
- What earlier document does it cite, and what later document changes it?
- For inclusion/categorisation: is there a Commission advice, survey, hearing, or benchmark record?
- For court records: what operative direction affects the current list or reservation percentage?
3. Missing-entry statuses
- Not yet archived: known source exists, file not yet added.
- Source not found: cited in another record, original PDF not located.
- Partial: source found only as quote, mirror, OCR, or bundled page inside another PDF.
- Needs OCR: scanned source exists but text is not searchable.
- Verification needed: source exists but date/number/content conflict needs checking.
Copyable JSON template for a new document
{
"notif_no": "",
"date": "YYYY-MM-DD",
"year": 2026,
"type": "notification | order | corrigendum | hearing_notice | court_order | report | act | roster | certificate_guideline",
"status": "current | withdrawn | superseded | legacy | missing | verification_needed",
"summary": "",
"filename": "",
"local_pdf": "obc_pdfs/YYYY-MM-DD_DOCUMENT-NO_short-title.pdf",
"authority": "BCW Department | WBCBC | Court | Commission | Research",
"text": "",
"links_to": ["notification/order/case ids this document cites"],
"changed_by": ["later document ids if known"],
"evidence_needed": ["survey report", "hearing notice", "commission advice"]
}
| Entry type |
Where it belongs |
Required cross-links |
Useful summary pattern |
| Notification / order | Timeline + corpus + PDF bundle | Previous notification, later amendment/withdrawal, affected communities | “Adds/amends/withdraws X and changes Y from date Z.” |
| Public hearing notice | Public Hearings + missing evidence trail | Community names, hearing date, later notification | “Notice calls hearing for named communities before inclusion/categorisation.” |
| Commission advice / survey | Reports/evidence + audit | Community, survey method, score/criteria, resulting notification | “Records evidence and recommendation behind notification X.” |
| Court order / judgment | Timeline + legal context | Case number, affected notifications, operative direction | “Court direction affects list/reservation/process by doing X.” |
| Policy report | Policy Reports & Criteria | Relevant sections, applied criteria, related state entries | “Explains criteria/evidence used to interpret the notification set.” |