Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add New Output To Export All EBD In One Excel File #217

Open
5 tasks
hf-krechan opened this issue Jul 8, 2024 · 2 comments
Open
5 tasks

Add New Output To Export All EBD In One Excel File #217

hf-krechan opened this issue Jul 8, 2024 · 2 comments

Comments

@hf-krechan
Copy link

Claudia would like to have an Excel file which contains all EBD tables.

The goal is to have something similar like the following excel file
EBD_GPKE_LFW.xlsx

We do not need to fill column Häufigkeit.

Features

  • Add a new subcommand to the ebdamame cli interface to export one excel file with all EBDs. See kohlrahbi as an example.
  • Add flag to choose format version
  • Add flag to choose EBDs (if no EBD flag is given, export all EBDs)
  • Add flag to set path to edi energy mirror (there are all EBD documents)
  • Add flag to set path to machine readable anwendungshandbücher (this is needed to check in which prüfis is the EBD)
@OLILHR OLILHR self-assigned this Jul 8, 2024
@OLILHR
Copy link
Member

OLILHR commented Jul 8, 2024

important columns: C D F G I J K (basically everything an EBD is made off) + M

@hf-kklein
Copy link
Contributor

OK, let's split this into easy-to-handle isolated features:

  • (0) allow excel export
  • (1) instead of a docx file it should be possible to provide a path to a directory
  • (2) add a wrapper around (1) that, given a path to edi_energy_mirror, exports all the files from a specific format version (which translates to a sub-directory)
  • (3) add a feature that, given a list of machine-readable AHBs, returns the prüfis of those that refer to a given EBD (str)
  • (4) add a wrapper around (3) that accepts the machine-readable-ahb repo + format version as argument, and reads the AHB information from there

So basically it's 3 real features (0), (1) and (3) and two utiliy functions/wrappers (2) + (4) around those features.

@OLILHR OLILHR removed their assignment Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants