-
Notifications
You must be signed in to change notification settings - Fork 6
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
Harvest discrepency log #14
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
During harvest of a collection, an isolated log should be created of failed SparQL requests, multiple most-specific types, missing required properties, duplicate literals with slight variation, and inconsistent language attribute use.
The log itself should probably be machine readable and contain as much relevant information as possible. The log may be emailed and or used in reattempts or other scheduled processes.
Size as assuming we won't be changing the existing SPARQL. Furthermore, this will occur only in the context of a full harvest and will re-create the log each time. Just put in hooks for logging whenever the various discrepancies are detected in the course of harvest.
Amending an existing log in place would be a future feature.
The text was updated successfully, but these errors were encountered: