A command-line tool for aggregating various bits of data from DDHI-encoded Interviews into a set of files that can be ingested by the DDHI’s Drupal application.
Description
There is a single command, ddhi_aggregate, which takes two arguments: a directory of TEI-encoded interviews to be processed, and a directory for the output:
ddhi_aggregate -i interviews/ -o aggregated_data/
Note
This project has been set up using PyScaffold 3.2.3. For details and usage information on PyScaffold see https://pyscaffold.org/.
1 maintainer
Metadata
1 maintainer
Release files for ddhi-aggregator 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ddhi_aggregator-1.1.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for ddhi_aggregator-1.1.0-py2.py3-none-any.whl |
Release files / ddhi_aggregator-1.1.0-py2.py3-none-any.whl
| Download URL | ddhi_aggregator-1.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 10.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
b0b2f109469a765f6aa0fd4e133a8ab639c9a769d1c800bf52eb6d8a5ece7fec
|
|
BLAKE2b-256 checksum How to use checksums |
c11aaa2e59beeaa779008a27f535c3aa7172644892b8ff82854d3aff9a8ef717
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.2 CPython/3.9.6
|
Security for ddhi-aggregator 1.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.
