Katzmann1983
commented
2 months ago The idea is great. At the moment the folder structure is a mess, especially in case of non english accounts. My dl_docs has folders like this: Abrechnung Abrechnung Ausführung Abschlüsse Auftragsbestätigung Ausführungsanzeige Basisinformationsblatt Contrato con el cliente Cryptoauszug Dividende Ex-Post Kosteninformation Hauptversammlung Información de protección de datos Información sobre la garantía de depósitos Kapitalmaßnahmen Kosteninformation Kundenanschreiben Kundenvereinbarung Listado de precios y servicios Löschbestätigung Saveback Sparplan Steuerreport Términos y condiciones de la oferta acción gratis Your terms of service for instant trading volume Zinsen
We should be using folder and file names without space, everything in English, with a proper translation to German, Spanish, etc.
b166er
BjBe82
Is your feature request related to a problem? Please describe. I would finally like a fixed folder structure, independent of API changes (like #91), which everyone can set according to their own preferences.
Describe the solution you'd like I suggest defining the target folders using several search criteria/search patterns. This search-target mapping should then be saved in a suitable configuration file. An example configuration file is attached.
for most search patterns you only need the following json nodes from the API-response: in root-event node: “type” ("event_type"), “subtitle” ("event_subtitle"), for a few documents you also need the “title” ("event_title"). In section-node: “title” ("section_title"), and finaly in "document"-node the “title” ("document_title").
most search patterns contain 1:1 strings. rarely, dynamic regex number patterns are also available, e.g. document number “\d” or for larger numbers e.g. years “\d+”.
There should also be a possibility for dynamic names in the target path, as predefined variables. In addition to the existing search patterns that can be reused in the path {event_type} - {event_title}, {event_subtitle}, {document_title}, there should also be environment variables, {iso_date} and {time} already exist, it would be nice to have the individual components, year: {%Y} => 2024, and of course month and day.
I personally find YAML format much more human-readable (especially because there is a comment option), nevertheless, in order to stay with the current technology and not want to introduce new dependencies into the project, here is the example configuration also in JSON format foldermap.json
Additional context
hope, this is possible.