ammcpc --- Archivematica (AM) MediaConch (MC) Policy Checker (PC)
This command-line application and python module is a simple wrapper around the MediaConch tool which takes a file and a MediaConch policy file as input and prints to stdout a JSON object indicating, in a way that Archivematica likes, whether the file passes the policy check.
Installation
Install with pip:
pip install ammcpc
Install from source:
python setup.py install
Usage
Command-line usage:
ammcpc <PATH_TO_FILE> <PATH_TO_POLICY>
Python usage with a policy file path:
>>> from ammcpc import MediaConchPolicyCheckerCommand
>>> policy_checker = MediaConchPolicyCheckerCommand(
policy_file_path='/path/to/my-policy.xml')
>>> exitcode = policy_checker.check('/path/to/file.mkv')
Python usage with a policy as a string:
>>> policy_checker = MediaConchPolicyCheckerCommand(
policy='<?xml><policy> ... </policy>',
policy_file_name='my-policy.xml')
>>> exitcode = policy_checker.check('/path/to/file.mkv')
Requirements
System dependencies:
- MediaConch version 16.12
Testing
To run the tests, make sure tox is installed, then:
tox
4 maintainers
Metadata
4 maintainers
Release files for ammcpc 0.3.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 | |
|---|---|---|---|---|
| ammcpc-0.3.0.tar.gz | 44.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ammcpc-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 75.0 kB
Release files / ammcpc-0.3.0.tar.gz
| Download URL | ammcpc-0.3.0.tar.gz |
|---|---|
| Size | 44.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0ce56b4a52d926b257b6c8c285056179c331a1ac517ec70618cca7ba54e21f9b
|
|
BLAKE2b-256 checksum How to use checksums |
becb1e320141ee6e33fae510aaf18d43e46928b259564fdf0bc428c19aef5b7a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 3, 2025.
Transparency logRelease files / ammcpc-0.3.0-py3-none-any.whl
| Download URL | ammcpc-0.3.0-py3-none-any.whl |
|---|---|
| Size | 30.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4939ae98772f07f114f51f78492425dd06bd0f88739476af578d2ce4ffdd8fce
|
|
BLAKE2b-256 checksum How to use checksums |
52c21c9982013a5ac9b42259de416db0c8c344a00f0600dcde588d56b7c2b0cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.0.1 CPython/3.12.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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 3, 2025.
Transparency logSecurity for ammcpc 0.3.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for ammcpc-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 3, 2025.
Transparency logA 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.
