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

Data import filtering: do it earlier! #13

Open
niconoe opened this issue Nov 10, 2021 · 1 comment
Open

Data import filtering: do it earlier! #13

niconoe opened this issue Nov 10, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@niconoe
Copy link
Member

niconoe commented Nov 10, 2021

As mentioned by @damianooldoni in riparias/gbif-alert#40, it would be good that the data filtering is done as much as possible at the "GBIF download" stage (and not in the import script itself).

It would be good to already review the existing filtering (records without at least a year, a location, ...), the planned filtering (absence records, ...) and see if this can be already pushed to the "generate GBIF download" step.

Some related things we should think about:

  • should we make the import script more defensive in case a user attempt to import a "less filtered" DWC-A file by using the --source-dwca option of the import_occurrences management command?
  • should we keep a more details log/report in the DataImport model (i.e. list exactly which records were skipped and why)?
@niconoe niconoe added the enhancement New feature or request label Nov 10, 2021
@niconoe niconoe self-assigned this Nov 10, 2021
@niconoe niconoe transferred this issue from riparias/gbif-alert Oct 2, 2023
@niconoe
Copy link
Member Author

niconoe commented Oct 2, 2023

The filtering is (mostly) instance-specific, so I moved this there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant