For example: db_dump/parliaments/DE/ or similar for the German Bundestag for the data dumps.
Directories & files should also be named more generic (& singular) depending on the type, so instead of /mdbs/ or /mdbs.json/ it could be: /memberOfParliament/, /party/, /faction/ and then just data-formatted.json, data-final.json etc.
The idea would be that the directories & files are directly derived from the input data, so the request parts parliament=DE&type=memberOfParliament would look for results in db_dump/parliaments/DE/data/memberOfParliament/data-final.json.
These are just examples. If with the current implementation a different structure makes more sense, feel free to adjust ;)
Oh miconception here on my side: parties are of course not per parliament, so only factions & members of parliament are located in /parliaments/DE/. I'll give this another thought... ;)
For use with multiple parliaments, the directories & files should be structured accordingly (maybe similar to https://github.com/OpenParliamentTV/OpenParliamentTV-Parsers/tree/main/parliaments/DE).
db_dump/parliaments/DE/
or similar for the German Bundestag for the data dumps./mdbs/
or/mdbs.json/
it could be:/memberOfParliament/
,/party/
,/faction/
and then justdata-formatted.json
,data-final.json
etc.The idea would be that the directories & files are directly derived from the input data, so the request parts
parliament=DE&type=memberOfParliament
would look for results indb_dump/parliaments/DE/data/memberOfParliament/data-final.json
.These are just examples. If with the current implementation a different structure makes more sense, feel free to adjust ;)