hochfrequenz / ahbesser Goto Github PK

Create an api endpoint to provide all known format version.

This information can be taken from the azure blob storage.
Each format version is a directory which contains all "Formate" (e.g. INVOIC).

Add a type ahead field in the header section of the page.

This issue needs #8 to work.

The columns Segmentgruppe and Segmentname should switch places in the table

This issue needs a design review first.

We want to connect the solutions AHB Tabellen and Bedingungsbaum with each other.

So the user should be able to click on a condition and gets on the Bedingungsbaum page.
The condition like X [931][494] and the format version should already inserted on the page.

During the docker-compose start up a small script should fill the blob storage with the files from the machine readable ahbs repository.

So the endpoints for the format versions and prüfidentifikatoren can get developed.

The table header should still be visible even if the user scrolled down.

The goal is to establish an automatic update process starting from the edu-energy-mirror repository.

A GH Action should run and upload the latest version of the scraped documents in the azure blob storage.

In the azure blob storage we want to keep the following directory structure:

|- FV2304
|- FV2310
    |- ...
    |- REQOTE
    |- UTILMD
        |- csv
        |- flatahb
        |- xlsx
    |- ...
|- FV2404

Steps

• Create Resource Group in Azure with pulumi
• Add Azure Blob Storage to this Resource Group with pulumi
• Setup a GH Action in edi-energy-mirror which uploads the results of kohlrahbi into this Azure Blob Storage, see https://github.com/Hochfrequenz/edi_energy_mirror/blob/master/.github/workflows/kohlrahbi.yml
• Add "an azure resource" to run a Docker container

Add format version field in the header section.
It should be a dropdown field.

The values for this field will come from the endpoint /format-versions

Issue #7 is required.

As a user I would like to share a link which already contains the information format version, pruefidentifikator and my search.

This makes it easy to provide needed information for others, e.g. in a ticket.

The README should contain the following

• the current architecture
• a short manual how to start the application

Create an endpoint in the backend to serve the list of all available prüfis for a provided format version e.g. FV2310.

One idea in the workshop was to create an extra file for each format version during the upload of all files.