1 file was added to this release more than 14 days after its initial publication. Inspect the release files before installing.
Secure Infrastructure for Research with Administrative Data (SIRAD)
sirad is an integration framework for data from administrative systems. It
deidentifies administrative data by removing and replacing personally
identifiable information (PII) with a global anonymized identifier, allowing
researchers to securely join data on an individual from multiple tables without
knowing the individual's identity. It is developed by
Research Improving People's Lives (RIPL).
For a worked example and further details, please see sirad-example.
To learn more about the motivation for creating this package and its potential uses, please see our article in Communications of the ACM:
J.S. Hastings, M. Howison, T. Lawless, J. Ucles, P. White. (2019). Unlocking Data to Improve Public Policy. Communications of the ACM 62(10): 48-53. doi:10.1145/3335150
Installation
Requires Python 3.7 or later.
To install from PyPI using pip:
pip install sirad
To install using Anaconda Python:
conda install -c ripl-org sirad
To install a development version from the current directory:
pip install -e .
Running
There is a single command line script included, sirad.
sirad supports the following arguments:
process- split raw data files into data and PII filesresearch- create a versioned set of research files with a unique anonymous identifier
Configuration
To set configuration options, create a file called sirad_config.py and place
either in the directory where you are executing the sirad command or
somewhere else on your Python path. See _options in config.py for a
complete list of possible options and default values.
The following options are available:
-
DATA_SALT: secret salt used for hashing data values. This shouldn't be shared. A warning will be outputted if it is not set. Defaults to None. -
PII_SALT: secret salt used for hashing pii values. This shouldn't be shared. A warning will be issued if it is not set. Defaults to None. -
LAYOUTS: directory that contains layout files. Defaults tolayouts/. -
RAW_DIR,DATA_DIR,PII_DIR,LINK_DIR,RESEARCH_DIR: paths to where the original data, the processed files, and the research files will be saved. -
VERSION: the current version number of the processed and research files.
Layout files
sirad uses YAML files to define the layout, or structure, of raw data files.
These YAML files define each column in the incoming data and how it should be
processed. More documentation to come on this YAML format.
The following file formats are supported:
- csv - change delimiter with delimiter option
- fixed with
- xlsx (xls not currently supported)
Development
Sample test data is randomly generated using Faker; none of the information identifies real individuals.
- tax.txt - sample tax return data. Includes first, last, DOB and SSN.
- credit_scores.txt - sample credit score information. Includes first, last and DOB but no SSN.
Run unit tests as:
python -m unittest discover
sirad can also be used as an API from custom Python code. Documentation to come.
Authors
- Mark Howison
- Ted Lawless
- John Ucles
- Preston White
Metadata
Release files for sirad 0.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
File added late
1 file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release files before installing.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| sirad-0.3.2.tar.gz | 20.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sirad-0.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 43.7 kB
Release files / sirad-0.3.2.tar.gz
| Download URL | sirad-0.3.2.tar.gz |
|---|---|
| Size | 20.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
21b306c43ec74254fa34aea42063e0c6812d734b50d4bebb8d1386423b26d7e0
|
|
BLAKE2b-256 checksum How to use checksums |
7b086496e8fb3d52b80f4add7ad19d414b31eb2d68997370f61175ce29e98acf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.6.4 pkginfo/1.8.2 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.1 CPython/3.7.8
|
Release files / sirad-0.3.2-py3-none-any.whl
File added late
This file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release file before installing.
| Download URL | sirad-0.3.2-py3-none-any.whl |
|---|---|
| Size | 23.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6e909dc8fd40a64434a6c60d92fc1e7b079748f384aba91a8489dca5fb0f7ce8
|
|
BLAKE2b-256 checksum How to use checksums |
ffe9c5ccc3d654b3e75deb0aed1b5e4f13a15faa8040222e747c76247adfda1c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.5
|
Security for sirad 0.3.2
Upload timing
File added late
1 file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.