Make it possible to export data from UI #786
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…-occurrences-data
- Designed a structured framework for data exports. - Integrated export registry for modular and extensible export formats. - Implemented occurrences export for simple JSON and CSV formats.
…nickLab/antenna into feat/export-occurrences-data
- Added 'project' relationship to DataExport model.
- Refactored 'status' and 'file_url' in DataExport to be computed properties from the associated Job.
- Updated DataExportViewSet.get_queryset() to filter by active project and optimize queries with select_related('job').
- Updated DataExportSerializer to include nested Job details instead of separate job-related fields.
- Removed redundant retrieve and list methods from DataExportViewSet, relying on DRF's default behavior.
- Added DataExportAdmin with list display, filtering, and a new action to manually trigger an export job.
- Squashed migrations to consolidate schema changes and reduce migration overhead.
…nickLab/antenna into feat/export-occurrences-data
|
Thanks for pushing those changes! 🙏 It makes sense, I don't expect the data export model to handle progress, I just want to present progress information in UI but how we return this info is up to you! I think our current solution works well though! We show total records and a progress bar next to it (based on job progress). If it was a bit easier to access number of records exported, I could present that as well, but no biggie! I would currently have to search the dynamic jobs stages after this specific key. I think a bit unnecessary complexity in frontend code for a small win. Let's keep things as is! |
mihow
approved these changes
Apr 3, 2025
…nickLab/antenna into feat/export-occurrences-data
…-occurrences-data
mihow
approved these changes
Apr 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
In this PR we implement views to make export features available to users from UI.
As part if this work, we add following views:
Related Issues
Closes #737.
How to Test the Changes
The changes has to be tested with a backend that has export support. The easiest way to do that is to checkout this branch locally.
Screenshots
List exports:
Export details:
Register new export:
Delete export:
List export jobs:
Export job details:
