QU4RTET EPCIS
Built on top of the world-class EPCPyYes python package. Real EPCIS support for serious people running real systems.
________ ___ ___ _______ ________ ________ ___ ________
|\ __ \|\ \ |\ \|\ ___ \ |\ __ \|\ ____\|\ \|\ ____\
\ \ \|\ \ \ \\_\ \ \ __/|\ \ \|\ \ \ \___|\ \ \ \ \___|_
\ \ \\\ \ \______ \ \ \_|/_\ \ ____\ \ \ \ \ \ \_____ \
\ \ \\\ \|_____|\ \ \ \_|\ \ \ \___|\ \ \____\ \ \|____|\ \
\ \_____ \ \ \__\ \_______\ \__\ \ \_______\ \__\____\_\ \
\|___| \__\ \|__|\|_______|\|__| \|_______|\|__|\_________\
\|__| \|_________|
The essential Open-Source EPCIS component for the QU4RTET traceability platform.
For more on QU4RTET see http://www.serial-lab.com
The quartet_epcis python package is a Django application that contains the base database models necessary for the support of EPCIS 1.2 data persistence to an RDBMS. The quartet_epcis.parsing package contains an EPCIS XML parser that will take an input stream of XML data and save it to a configured database back-end.
The quartet_epcis.app_models directory contains a set of Django ORM models that are used to define the database scheme and store EPCIS data in the database.
Documentation
Find the latest docs here:
https://serial-lab.gitlab.io/quartet_epcis/
The full (pre-built )documentation is under the docs directory in this project.
Quickstart
Install QU4RTET EPCIS
pip install quartet_epcis
Add it to your INSTALLED_APPS:
INSTALLED_APPS = (
...
'quartet_epcis',
...
)
Features
Maintains the database schema for EPCIS 1.2 support.
Parses EPCIS 1.2 XML streams to the configured backend database system.
Enforces business rules around decommissioning, commissioning, aggregation, disaggregation, etc.
Running The Unit Tests
source <YOURVIRTUALENV>/bin/activate
(myenv) $ pip install -r requirements_test.txt
(myenv) $ python runtests.py
Metadata
Release files for quartet-epcis 4.1.5
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 |
|---|---|---|---|---|
| quartet_epcis-4.1.5.tar.gz | 66.7 kB | Without provenance | Details for quartet_epcis-4.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| quartet_epcis-4.1.5-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for quartet_epcis-4.1.5-py2.py3-none-any.whl |
Total release size: 141.3 kB
Release files / quartet_epcis-4.1.5.tar.gz
| Download URL | quartet_epcis-4.1.5.tar.gz |
|---|---|
| Size | 66.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a234e6428a5ac71d4d9ce9c9ab1c14ffacca5d8a99a0ce1577ccec340510e0dd
|
|
BLAKE2b-256 checksum How to use checksums |
6ffef40dd09b311dae99e014125751ac40abbdc51be684cbd3b57f64352fa203
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / quartet_epcis-4.1.5-py2.py3-none-any.whl
| Download URL | quartet_epcis-4.1.5-py2.py3-none-any.whl |
|---|---|
| Size | 74.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
f0011a6202952de4a00795af1870ef27fd9717cb695b4de0136f2e9cdcee1f1c
|
|
BLAKE2b-256 checksum How to use checksums |
d3c270273784c00e9aee5955201beebe46399b0ae9600fc60afe03e32b52365f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for quartet-epcis 4.1.5
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.