“Can you add this county?” sounds like a geography question. In public records, it is also a question about record type, software platform and the local way records are published. A court docket, a recorded deed and a parcel file may all belong to one county yet require three different acquisition paths. The useful answer is therefore specific: which records, for which jurisdiction, with which fields and refresh schedule?
Separate the platform from the jurisdiction
An adapter is the code that understands a platform: how to find records, request them and interpret its responses. Configuration selects a jurisdiction and its local parameters. Neither alone proves that a county is covered. Coverage is a tested delivery of the requested records from that jurisdiction into the intended output.
North Carolina illustrates the distinction. In the court records pipeline, a Tyler Enterprise Justice adapter can address the state court layer across all 100 NC counties. That makes the court platform broadly addressable. It does not mean a complete, verified court, Register of Deeds and parcel pipeline is live in all 100. Wake and Guilford validated the North Carolina architecture, and the same engagement expanded into Texas. The published case describes live work in NC and TX; the 100-county figure describes the reach of one platform layer.
The Register of Deeds layer has a different boundary. Wake uses Peraton and Guilford uses BIS Software in the published case. A county on a known vendor may need configuration and a verification run. A new vendor needs an adapter. Parcel data can differ again in format and matching keys. The practical unit of expansion is the combination of requested record layers, not the county name on a map.
Reuse still requires a local check
The county meeting-minutes case shows another form of reuse: an initial dataset from six counties across five CMS platforms. The adapters collect the documents; downstream extraction, keyword rules and entity identification put them into a shared research format. The published case reports 1,453 meetings in that initial dataset. That is a measured result for those six counties, not proof that every municipality using the same CMS has been processed.
When adding a jurisdiction on a known platform, verify its publication path, date range, document formats and completeness. One county may expose text-rich PDFs; another may publish scans that require OCR. Some only publish recent minutes. If the historical window stops early, the output should say so. A working request to a shared CMS is only the beginning of coverage validation.
For court and property records, the check must also follow the data after collection. Can the court party be linked to a recorded instrument or parcel? Are ambiguous matches visible for review? Can an analyst open the original filing behind a signal? A row count alone does not answer those questions.
Define coverage in the request
A useful coverage request names one jurisdiction, the record types, the date range, the fields that matter and the intended use. Add the required refresh cadence and delivery destination. With those details, it is possible to identify which platform work is reusable, what local configuration is needed and what must be validated before calling a source live.
CivicMine brings court, property, municipal and other public-record sources into structured research workflows. If a county or record type is missing from your current data, send the jurisdiction and the exact gap.