Conditions
- User needs to find records where the original coordinate data has been altered by the data aggregator.
- User needs to visualize results on a map.
- User wants to explore additional facets of these records, e.g. what collections within an institution they belong to.
Example scenario
Institutional data manager would like to identify how well different collections are doing on their georeferencing projects. Data manager wants to understand this from both a record-level and collection-level perspective, and needs to be able to show collection managers the affect that coordinate data quality issues have on a specimen record.
Links to external solutions
Solutions hosted in this repo
- identify-suspicious-coordinate-data (view in browser) (download for local use)