Skip to content
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

Include bels_match_string even on failure #65

Open
jbest opened this issue May 6, 2024 · 1 comment
Open

Include bels_match_string even on failure #65

jbest opened this issue May 6, 2024 · 1 comment

Comments

@jbest
Copy link

jbest commented May 6, 2024

It would be useful to have the bels_match_string returned in a API response even if a georeffed match isn't found so that string could be stored locally and compared to other local records. We would use this to find duplicate locality records that aren't yet georeffed so we can prioritize those with the most dups.

@jbest
Copy link
Author

jbest commented May 6, 2024

Oops, duplicate of #40

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant