You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we offer good documentation for the API, is this feature still required?
Is a JSON file good enough?
Can we do a cron scheduled export every night and only offer the 'latest' export file? That would prevent having to do a heavy query whenever someone clicks the export button.
Can the file be written to public downloads folder? Or do you guys use an S3 bucket or something similar for these kind of (larger) downloads?
Offering the data as JSON via a well documented API is always good. It would also be nice to offer the dataset as a CSV for people who can't use JSON/API's. The data is nested so I would break it up by creating one row for each function of a judge. So for example Aalderink would have 8 rows in the CSV. See this example CSV I made (it contains only the first 5 rows, but should make clear how I think it should look).
A daily cronjob to generate the CSV is fine! We can host it on our own server.
It would be great if we can make an export of the dataset and allow visitors to download it.
The text was updated successfully, but these errors were encountered: