Rather than only return the bels_match_string for matching records with coordinates, the BELS web API could also return the hash/bels_match_string for unmatched records. This would provide a way for users to discover all the identical localities in their dataset thereby making it easier to prioritize georeferencing of the most prevalent localities.
The web UI currently returns all hashes/match strings (as bels_matchwithcoords, bels_matchverbatimcoords, bels_matchsanscoords) even when none match records with coordinates.
Rather than only return the bels_match_string for matching records with coordinates, the BELS web API could also return the
hash/bels_match_string for unmatched records. This would provide a way for users to discover all the identical localities in their dataset thereby making it easier to prioritize georeferencing of the most prevalent localities.The web UI currently returns all
hashes/match strings (as bels_matchwithcoords, bels_matchverbatimcoords, bels_matchsanscoords) even when none match records with coordinates.