Skip to content

Latest commit

 

History

History
77 lines (58 loc) · 4.91 KB

README.rst

File metadata and controls

77 lines (58 loc) · 4.91 KB
Raw

MIG AHB Utility Stack (MAUS) 🐭

ℹ If you're looking for a wrapper around the new (2024) BDEW XMLs for MIG and AHB, checkout our fundamend repository. This maus package uses a different data format, because it's older than 2024.

Unittests status badge Coverage status badge Linting status badge Black status badge pypy status badge read the docs
maus logo
This repository contains the Python package maus.
MAUS is an acronym for MIG AHB Utility Stack where MIG stands for Message Implementation Guide and AHB stands for Anwendungshandbuch.
The maus software/package allows matching single lines from the AHB with fields specified in the MIG.
This package is necessary because EDI@Energy does not provide any real technical and machine-readable description of the MIGs and AHBs, only PDFs.
MAUS can also be used as a data model (maus.model) , without using the software or logic included in the package (MIG/AHB matching logic).

We're all hoping for the day of true digitization on which this repository will become obsolete.

What Problem Does It Solve?

Image you scraped the AHB PDFs into something machine-readable. Machine-readability in this context implies, that for each field/information inside the AHB you can easily access

  • segment group (e.g. "SG4")
  • segment (e.g. "LOC")
  • data element ID (e.g. "3225")
  • AHB Expressions (e.g. "Muss [123] U ([456] O [789])[904]")

The exact data format (be it CSV, JSON, XML ...) is not important beyond an initial deserialization.

(BTW: The AHB Expression can be parsed and evaluated using the 🦅 AHBicht Library or our AHBicht REST API which is publicly available.)

Image you also had a machine-readable version of the MIG -- spoiler: Hochfrequenz can help you with that (please contact @JoschaMetze for a demo) -- you still weren't able to make use of your data because the MIG data and AHB data are still unrelated. MAUS creates a connection between machine readable AHBs and machine readable MIGs. This allows to associate certain lines from the AHB with certain fields in the MIG and is the basis for a meaningful content evaluation/validation of EDIFACT messages, or, to be more precise, validation of data structures that might be converted to EDIFACT.

Code Quality / Production Readiness

  • The code has at least a 95% unit test coverage. ✔️
  • The code is rated 10/10 in pylint and type checked with mypy (PEP 561). ✔️
  • The code is MIT licensed. ✔️
  • There are only few dependencies. ✔️

Installation

For the bare maus data model and matching logic it's sufficient to install pip install maus. Only if the MIG you're using is based on XML (namely the Hochfrequenz XML based MIG representation), you need to install pip install maus[xml]. If you want to use the CLI tool, you need to install pip install maus[cli].

Once installed you can either use the package and its data model in your own Python code or use the mapping logic (of only the Hochfrequenz EDIFACT XML templates as of now) via CLI: maus --flat_ahb_path flat_ahb_by_kohlrahbi.ahb.json --sgh_path path_to_segment_group_hierarchy.sgh.json --template_path UTILMD5.2e.template --output_path file_to_be_created.maus.json. The CLI tool is not only available via pip but also as standalone executable in the respective release assets.

Development

Please follow the detailed instructions in the README of our Python Template Repository on how to setup your local development environment (tl;dr: tox).

Contribute

You are very welcome to contribute to this template repository by opening a pull request against the main branch.