ResolvER
ResolvER is an extensible framework for building Entity Resolution pipelines in order to merge datasets around "things" based on complex join logic and transitive linking.
Entity Resolution is a complex and computationally expensive process. ResolvER seeks to provide tools that cover the majority of use cases, the ability to enhance those tools with machine learning, and leverage developers' experiential knowledge of data to provide a flexible and efficient solution to the Entity Resolution problem.
Quick/Simple Example
The University of Leipzig provides test datasets for Entity Resolution, let's say you're working with the DBLP-ACM dataset.
The dataset provides two files, both describing published papers, with similar columns:
- A unique id (unique to that file only)
- A title
- A list of authors
- A venue
- A year
The titles vary slightly between files, and different authors may be listed for a given paper - in short, there's no clean or consistent way to deduplicate the data.
Using ResolvER, you can specify any number of complex operations to determine whether two given records are duplicates of each other in what are called "Strategies." One such strategy may be:
titlehas Levenshtein ratio of at least 0.9 ANDauthorshas Jaccard distance of at least 0.4 ANDyearis an exact match
In Depth examples
For more in depth workflows and explanations of the methodology, reference the notebooks folder.
Install
Install the latest version of ResolvER:
$ pip install entity-resolution
Research
ResolvER is (most notably) inspired by the below publications:
- Collective Entity Resolution in Relational Data
- Comparative Analysis of Approximate Blocking Techniques for Entity Resolution
License
Released under standard MIT license (see LICENSE.txt):
Copyright (c) 2021 ResolvER Developers
Carl Best
Metadata
Release files for entity-resolution 0.1.0
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 | Actions |
|---|---|---|---|---|
| entity-resolution-0.1.0.tar.gz | 16.0 kB | Without provenance | Details for entity-resolution-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| entity_resolution-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for entity_resolution-0.1.0-py3-none-any.whl |
Total release size: 34.3 kB
Release files / entity-resolution-0.1.0.tar.gz
| Download URL | entity-resolution-0.1.0.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ae52c9c0cdec49c1ab8a3609d116a6f1bfb97d902ca03194af93e41fbf343543
|
|
BLAKE2b-256 checksum How to use checksums |
3899ed89589b990aac877ac7f4f2af0579aa850de6e474c1ca015b3986edc479
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/34.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.9 tqdm/4.63.0 importlib-metadata/4.11.3 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.6
|
Release files / entity_resolution-0.1.0-py3-none-any.whl
| Download URL | entity_resolution-0.1.0-py3-none-any.whl |
|---|---|
| Size | 18.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5377849c7740224a396f59ae562cf1533bde98c58f2c0b6260b0e4ab82237ae3
|
|
BLAKE2b-256 checksum How to use checksums |
e04afa97f9a2e4f94044ff2e9186e4b0b68a23020ff1ad06549d34b8a65faddd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/34.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.9 tqdm/4.63.0 importlib-metadata/4.11.3 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.6
|
Security for entity-resolution 0.1.0
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.