NFDInspector
NFDInspector is designed to facilitate the inspection of formal quality issues pertaining to research data. It is currently compatible with the LIDO and EAD metadata standards. The project has been funded by the "4Memory Incubator Funds" of the NFDI4Memory consortium and is being developed and maintained by the Montanhistorisches Dokumentationszentrum (montan.dok) of the Deutsches Bergbau-Museum Bochum.
Installation
To install with pip on macOS or Linux, run:
python3 -m pip install nfdinspector
To install with pip on Windows, run:
py -m pip install nfdinspector
Quickstart Guide
LIDO inspection
Import LIDOInspector:
from nfdinspector.lido_inspector import LIDOInspector
Initialize a LIDOInspector. You can specify a language (currently available: "en" or "de") for the error messages:
lido_inspector = LIDOInspector(error_lang="de")
Read LIDO files you want to inspect:
lido_inspector.read_lido_files("files_path")
Refer to a configuration file (optional). Without this step the inspections are executed with a default configuration:
lido_inspector.config_file("file_path")
Execute the inspections:
lido_inspector.inspect()
Save the inspections as a JSON file. You can specify the indention (default: None):
lido_inspector.to_json("file_path", indent=4)
Save the inspections as a CSV file. You can specify a field separator/delimiter (default: ","):
lido_inspector.to_csv("file_path", delimiter=";")
EAD inspection
Import EADInspector:
from nfdinspector.ead_inspector import EADInspector
Initialize an EADInspector. You can specify a language (currently available: "en" or "de") for the error messages:
ead_inspector = EADInspector(error_lang="en")
Read EAD file you want to inspect:
ead_inspector.read_ead_file("file_path")
Refer to a configuration file (optional). Without this step the inspections are executed with a default configuration. It is highly recommended to use different configuration files for archive tectonics and finding aids:
ead_inspector.config_file("file_path")
Execute the inspections:
ead_inspector.inspect()
Save the inspections as a JSON file. You can specify the indention (default: None):
ead_inspector.to_json("file_path", indent=4)
Save the inspections as a CSV file. You can specify a field separator/delimiter (default: ","):
ead_inspector.to_csv("file_path", delimiter=";")
Contribute
If you'd like to contribute to NFDInspector, check out https://github.com/montan-code/nfdinspector
Metadata
Release files for NFDInspector 0.2.1
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 |
|---|---|---|---|---|
| nfdinspector-0.2.1.tar.gz | 42.4 kB | Without provenance | Details for nfdinspector-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| NFDInspector-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for NFDInspector-0.2.1-py3-none-any.whl |
Total release size: 61.1 kB
Release files / nfdinspector-0.2.1.tar.gz
| Download URL | nfdinspector-0.2.1.tar.gz |
|---|---|
| Size | 42.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e9680eb6c6c472b9de7c2d6bd431b51759fe101dc3ab8f8db5f3d6226af1891
|
|
BLAKE2b-256 checksum How to use checksums |
1114f29f000022b08cf1c61099594c4a81983514803d366e287ba1594149f745
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.13.0
|
Release files / NFDInspector-0.2.1-py3-none-any.whl
| Download URL | NFDInspector-0.2.1-py3-none-any.whl |
|---|---|
| Size | 18.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
49306f41d13c6b036faad4bc1ebe7f3c123e78df67478e6e51daaceecb4f328b
|
|
BLAKE2b-256 checksum How to use checksums |
06d5dadb5b55fa68e1ec9a192dc0af726d37c5944a89e2fd44c34bfed2646e58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.13.0
|
Security for NFDInspector 0.2.1
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.