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

AB#101818 Only export actual record for csv and jsonlines #532

Merged
merged 3 commits into from
Dec 15, 2023

Conversation

jjmurre
Copy link
Contributor

@jjmurre jjmurre commented Dec 15, 2023

Most users are not interested in the historical records. And, export is done every night. Bright export in line with the DSO API export.

Changes:

  • Only select current records for temporal tables
  • Change headers (capitalize) to be in line with the DSO API export (althought it seems a bit strange to me to use capitalize)
  • Change datetime notation to use iso format
  • Foreign keys only use the identificatie (not the dot-volgnummer)

To do:
Mabye we should also export current records only for the geopackages.

Most users are not interested in the historical records. And, export is
done every night. Bright export in line with the DSO API export.

Changes:

- Only select current records for temporal tables
- Change headers (capitalize) to be in line with the DSO API export
  (althought it seems a bit strange to me to use capitalize)
- Change datetime notation to use iso format
- Foreign keys only use the identificatie (not the dot-volgnummer)

To do:
Mabye we should also export current records only for the geopackages.
Some id fields are only there to give Django a non-composite PK.
@jjmurre jjmurre merged commit dc0d70e into master Dec 15, 2023
4 checks passed
@jjmurre jjmurre deleted the jan/ab-101818-exports-only-active-data branch December 15, 2023 10:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants