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

Directory & File naming convention #13

Open
OpenHypervideo opened this issue Jun 25, 2021 · 1 comment
Open

Directory & File naming convention #13

OpenHypervideo opened this issue Jun 25, 2021 · 1 comment

Comments

@OpenHypervideo
Copy link
Member

OpenHypervideo commented Jun 25, 2021

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).

  • 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 ;)

@OpenHypervideo
Copy link
Member Author

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... ;)

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

1 participant