The Arizona indexing workflow received additional normalization checks for the fields used across search results, county views, and record pages. Public sources often describe the same kind of information with different labels or formats, so careful normalization is necessary for useful browsing.
Why normalization is needed
One source may use a full county name while another uses an abbreviation. Dates may arrive in different orders, agency names may include varying punctuation, and identifiers may contain spaces or separators. Without consistent handling, equivalent information can sort poorly, produce confusing labels, or become harder to locate through search.
Normalization creates a predictable presentation layer while retaining the source meaning. It is formatting and organization work; it does not rewrite the official facts.
Fields included in the checks
- names and the separation of available name components;
- booking, arrest, or record identifiers;
- arrest, booking, and publication dates when supplied;
- county and agency labels;
- charge descriptions and related available text; and
- links and metadata needed to build a stable public record page.
Not every record contains every field. The checks focus on whether the available combination provides enough identity and event context for a page to be meaningful.
Publication and sitemap eligibility
Records that lack sufficient context should not be promoted through the XML sitemap merely because a database entry exists. The improved workflow separates stored material from pages that are ready for normal public discovery. This supports a cleaner sitemap and reduces low-value or incomplete destinations.
Normalization does not determine guilt, change a charge, update custody, or establish a court outcome. Those facts remain controlled by the office responsible for the original record.
What visitors should see
The practical result is more consistent county names, dates, identifiers, and agency labels across cards and individual pages. Search results should be easier to scan because similar fields appear in familiar positions. Where source information is unavailable, the interface should avoid implying that a missing value has been verified as none.
Verifying the underlying record
Presentation consistency cannot make a historical page current. Charges may be amended, people may be released, and cases may later be dismissed or resolved. Visitors should use the displayed county, agency, identifier, and date as clues when checking the responsible jail, court, clerk, or agency for the latest official information.