DICOM Directory to PostgreSQL DB
Have you ever gotten a DICOM dataset from the internet in the form of a folder with a bunch of DCM files in it? I did recently and wanted to get an idea of the data that was housed in all of these DCM files, so I wrote this small tool that will extract all of the the DICOM elements you're interested in from all of the DCM files in the directory and it will put the data into a PostgreSQL DB table so you can indirectly query the DICOM header data.
1 maintainer
Metadata
1 maintainer
Release files for metadata-to-db 0.0.8
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 |
|---|---|---|---|---|
| metadata_to_db-0.0.8.tar.gz | 6.6 kB | Without provenance | Details for metadata_to_db-0.0.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| metadata_to_db-0.0.8-py3-none-any.whl | Python 3 | none | any | Details for metadata_to_db-0.0.8-py3-none-any.whl |
Total release size: 15.4 kB
Release files / metadata_to_db-0.0.8.tar.gz
| Download URL | metadata_to_db-0.0.8.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
63d09d079cd91e5a6a568f54ab8abf23f88ace53a1060f5065dd53aa8fdbb087
|
|
BLAKE2b-256 checksum How to use checksums |
6f47868f043912c563dd3a941afebc6296ef9b7c211ba5b56b753ab54d9f2f0a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.6.9
|
Release files / metadata_to_db-0.0.8-py3-none-any.whl
| Download URL | metadata_to_db-0.0.8-py3-none-any.whl |
|---|---|
| Size | 8.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a5f7bf490c497f05251ac2a5c5c50875d9d9f32db6411360ec960349ccf16ec0
|
|
BLAKE2b-256 checksum How to use checksums |
1aebaa8b54d868c409a4286736542065f7181863418c29e7274d2cb4573b1d34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.6.9
|
Security for metadata-to-db 0.0.8
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.
