-
Notifications
You must be signed in to change notification settings - Fork 58
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
Check for references to core IDs that do not exist #1246
Comments
Related issue in DwC-A validator: http://dev.gbif.org/issues/browse/TOOL-7 |
@cgendreau I anticipate the IPT will do referential integrity checks on DwC-As by making external calls to the GBIF Data Validator API. For large datasets, it may take hours for the data validator to finish. Therefore, instead of the user having to wait for the results, how about they can have them sent directly to their email? Of course they would have to provide an email in their API request for this to work. Thanks. |
There is no plan to send a response by e-mail at the moment. But if we were to do that it is very likely that we would use the GBIF login instead. Running the validation on large dataset won't take hours if we do not interpret all records. |
Relevant issue on portal feedback. |
@CecSve Thank you for the comment. |
@mike-podolskiy90 it seems like it is the scope of the new data model though (point 5)? |
Yes, but that is frictionless data package and those checks will be performed by the frictionless library itself |
Would that mean that the publisher would not get any notification similar to the messages they receive when publishing currently? |
No. Data package would not be generated, and validation errors would be displayed. |
Would the checks and validation errors only be for publishers using the frictionless packages? Or is it planned to also have such checks for regular DwC archives? |
It is not planned |
Ok. I will not make a new issue as the origin of this issue is capturing what I would suggest. Ideally, the IPT should validate referential integrity of DwC-A's to capture mismappings and potentially stop the generation of an archive if the issues are not fixed by the publisher. Relevant issues for inclusion of referential integrity checks are: gbif/portal-feedback#4522 @ManonGros please add to this if I am missing something |
Another issue related to referential integrity: gbif/portal-feedback#5359 (comment) |
The IPT should validate that all the core ID used in the extension(s) references a core ID that exists.
Please note, this check can currently be performed by http://tools.gbif.org/dwca-validator/
The text was updated successfully, but these errors were encountered: