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
{{ message }}
This repository was archived by the owner on Aug 26, 2022. It is now read-only.
Currently EvaluationType doesn't provide the severity of any of its elements (even if it's possible to get the default one for the flags related to Occurrences).
The idea is to map EvaluationType to a severity based on a ValidationProfile. For example, a Geodetic datum assumed WGS84 could be a warning in the default GBIF profile but an error in the context of a BID project.
Note that the concept of ValidationProfile refers to a profile in the context of new or updated data that will be shared/updated through GBIF. It is not referring to the concept of Fitness For Use of data after a download even if the 2 concepts are not mutually exclusive.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently
EvaluationType
doesn't provide the severity of any of its elements (even if it's possible to get the default one for the flags related to Occurrences).The idea is to map
EvaluationType
to a severity based on aValidationProfile
. For example, aGeodetic datum assumed WGS84
could be a warning in the default GBIF profile but an error in the context of a BID project.Note that the concept of
ValidationProfile
refers to a profile in the context of new or updated data that will be shared/updated through GBIF. It is not referring to the concept of Fitness For Use of data after a download even if the 2 concepts are not mutually exclusive.The text was updated successfully, but these errors were encountered: