OWNER REPAIR / RAZE PATTERNS — 2015 THROUGH OCTOBER 18, 2026

Open Owners.html for the searchable report. The Property Search page links to it.
owner_summary.csv ranks named owner groups; owner_cases.csv lists supporting cases.
owner_name_match_candidates.csv contains possible additional links for review only.
owner_analysis_data.json preserves the report data and linked source passages.

WHAT A CASE COUNT MEANS
One CE case number, associated with a recorded owner name in a detailed hearing
packet, and containing at least one explicit repair or raze order with a labelled
issue date between January 1, 2015 and October 18, 2026. A case number is counted
once for each named owner group even if it appears at several hearings or contains
separate vacate, repair and raze pages. Repair and raze counts overlap where the
same case includes both. These figures are not counts of individual legal orders,
violations, final affirmations, demolitions completed or fines paid.

Ranking uses distinct case numbers, not appearances. Address counts are indexed
source spellings, not independently verified parcels. One property can have more
than one case number over time. Sources with no usable case number cannot enter
the distinct-case ranking. The owner detail retains first/last source dates and
all available order issue dates, and links to the saved originals and source URLs.

OWNER ATTRIBUTION
The owner field is reproduced as recorded in each source. A name in a later
hearing packet may identify a later purchaser, successor, estate or co-owner.
Association with a case DOES NOT establish ownership when the original order was
issued, responsibility for the condition, current ownership, or wrongdoing.
Explicit new-owner and deceased labels are retained in source context. Possible
heirs, guardians and tax-purchaser labels requiring role review are excluded from
case totals. Procurement/demolition business does not establish an owner/order
association and is excluded entirely from this analysis.

NAME GROUPING
Case, spacing, punctuation, &/AND, and LLC/INC/CORP spelling variants are normalized.
These remain name-based groups, not verified legal identities. Staff/inspector
initials appearing at the end of older agenda listings are removed from the name
key; the source text stays intact. The unnormalized alias and full owner context
are retained for every indexed observation.

Separately labelled owners are indexed individually. Shared-surname pairs such as
"Clark P. and Gail S. Braun" remain a joint group; an individual's missing surname
is not invented. Joint groups are not automatically merged with individual names.
Initials, spelling differences, trade names, missing company suffixes and similar
names are offered as review candidates rather than merged. Shared addresses help
identify review leads but do not establish common identity or beneficial ownership.
Affiliated LLCs are not combined into an assumed common owner.

SEPARATE / EXCLUDED EVIDENCE
Explicit owner names in agendas are searchable but do not count as documented
order cases. Agenda address counts can overlap with detailed case addresses, and
do not mean additional properties or orders. Case numbers with missing order
dates, or observations showing issue dates before 2015, are reported separately.
These categories can overlap if different source versions contain different dates.
No date is guessed from a CE number or a meeting date.

COVERAGE
This uses the existing public online collection, not a complete agency case export.
2015 is partial. The collected 2022 hearing series has agendas but no minutes.
Other years also have gaps in detailed packets. See year_coverage.csv and
historical_research.txt. An absent owner may still have cases. Rankings describe
this collection, not all owners in Vanderburgh County, and do not measure the
fraction of an owner's property portfolio affected.

SQLITE TABLES
owner_analysis_metadata: date limits and counting / identity / attribution rules.
owner_groups: normalized name keys and stable report IDs.
owner_observations: name-to-source-record links, original parsed name and context,
                    evidence basis, new-owner and deceased labels.
owner_case_summary: one row per owner group / case, addresses, order types/dates,
                    record IDs and source URLs stored as JSON arrays.
owner_summary: distinct case counts, repair/raze counts, address counts, dates,
               separate agenda/unknown/earlier evidence and alias arrays.
owner_name_match_candidates: review links only; not merged into the ranked totals.

The original records/documents/properties are preserved. Owner tables are additive.
Owners may share a case; do not sum all owner case counts as a county case total.

EXAMPLE SQL
SELECT owner_name,distinct_cases,repair_cases,raze_cases,indexed_address_strings
FROM owner_summary WHERE distinct_cases>=2
ORDER BY distinct_cases DESC,owner_name;

SELECT s.owner_name,c.* FROM owner_case_summary c
JOIN owner_summary s USING(owner_id)
WHERE s.owner_name LIKE '%MASRANI%';

SELECT s.owner_name,r.case_number,p.address_normalized,r.meeting_date,
       r.date_order_issued,r.order_type,o.owner_context,d.url,d.local_file,r.page
FROM owner_observations o JOIN owner_summary s USING(owner_id)
JOIN records r ON r.id=o.record_id JOIN properties p ON p.id=r.property_id
JOIN documents d ON d.id=r.document_id
WHERE s.owner_name LIKE '%VALLEY%' ORDER BY r.case_number,r.meeting_date;