civic-data-identity-us-il
This repository hosts raw and processed Illinois datasets used for testing normalization, deterministic identifier generation, and candidate record consolidation in the Civic Interconnect project.
The primary dataset is the City of Chicago Contracts Dataset, which provides 182,000+ procurement records suitable for testing:
- Vendor-name normalization across capitalization, punctuation, and abbreviations.
- Deterministic identifier generation from canonicalized inputs.
- Procurement adapter behavior with real-world source data.
- Candidate record grouping and normalization collision detection.
- Reproducible data extraction and provenance documentation.
This repository contains both the full raw dataset and curated subsets designed as identity test fixtures.
Repository Organization
data/raw/
Unmodified raw datasets retrieved directly from official public sources. Contains large files (up to ~50 MB). These files are not stored in the main Civic Interconnect repo to avoid repository bloat.
data/identity/
Curated, size-limited datasets (~5k–20k rows) used for:
- testing consistency of generated identifiers for equivalent canonical inputs
- evaluating string normalization
- testing adapters against realistic naming variations
These subsets are suitable for inclusion as examples in the main CEP spec repo.
docs/provenance/
Contains PROV-YAML metadata files describing dataset lineage, publishers, and retrieval activities. These files follow W3C PROV-DM conventions.
src/civic_data_identity_us_il/
Utility code for extracting and shaping subsets from raw data. The provided Python tool generates deterministic vendor-name samples.
Data Source
City of Chicago – Contracts Dataset
- URL: https://data.cityofchicago.org/Administration-Finance/Contracts/rsxa-ify5
- Publisher: City of Chicago
- License: Public Domain
- Fields include procurement descriptions, award amounts, departments, vendor names, addresses, and contract timeline fields.
- Used to test:
- identity resolution
- canonicalization
- adapters for procurement verticals
Full provenance is provided in
docs/provenance/chicago_contracts.prov.yaml.
Relationship to civic-interconnect
This repository serves as a data companion to the main specification and implementation in:
https://github.com/civic-interconnect/civic-interconnect
Only smaller derived files (e.g., 5k–20k row identity samples) are copied into
the main repository under examples/identity/.
The separation keeps CEP maintainable and free of large artifacts while preserving full reproducibility.
Changelog
Citation
If you use this repository, please cite both:
- CITATION.cff
- The original City of Chicago dataset (included in references)
Documentation
License
Raw public datasets retain their original license (Public Domain for Chicago Open Data).
All derived outputs, scripts, and documentation in this repository are licensed under the MIT Licence unless otherwise noted.
Metadata
Release files for civic-data-identity-us-il 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| civic_data_identity_us_il-0.1.2.tar.gz | 14.0 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| civic_data_identity_us_il-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.0 MB
Release files / civic_data_identity_us_il-0.1.2.tar.gz
| Download URL | civic_data_identity_us_il-0.1.2.tar.gz |
|---|---|
| Size | 14.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a5c5d4c3cc351ddd2d95114fb6016e7a5e300c057f6ced2629fa7dd5016254d
|
|
BLAKE2b-256 checksum How to use checksums |
9b31d9a41695dafc6d6eb10b8b27c4d18e562698fc4818b04a0638665b493d6c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logRelease files / civic_data_identity_us_il-0.1.2-py3-none-any.whl
| Download URL | civic_data_identity_us_il-0.1.2-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2018a70a2f9b36256cca2b3d52412849a4bc3ab0a8c4811100c5ba5305f8c3fd
|
|
BLAKE2b-256 checksum How to use checksums |
ed84951e28d9039e3f924d7a35fd5a188c441aab43a233e4754aa8dd9bcbd218
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logSecurity for civic-data-identity-us-il 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for civic_data_identity_us_il-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.