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

Spatial coverage duplication #117

Open
atomrab opened this issue Jan 18, 2017 · 2 comments
Open

Spatial coverage duplication #117

atomrab opened this issue Jan 18, 2017 · 2 comments
Assignees

Comments

@atomrab
Copy link

atomrab commented Jan 18, 2017

In a PeriodO collection that I am cleaning, there was a typo in the entry of the spatial coverage of one of the items. Specifically, there were two records associated with Argentina, but in one the spatial coverage was "Argentina" and in the other "argentina". This generated two facets in the search filter. When I edited the "argentina" entry to correct it to "Argentina", the case of the second "Argentina" in the search filter changed, but it still appeared separately from the "Argentina" that was originally capitalized.

Existing spatial coverage terms come up in a pull-down list, of course, but I can see fast or inaccurate typists putting in an entire term that's already there, rather than selecting, or putting in a misspelling that prevents the right term from showing up in the populated list ("Fnance"). We want to have a way to correct "Fnance" to "France" without then having both "France" and "France" appear separately in the facet window.

@atomrab
Copy link
Author

atomrab commented Jan 27, 2017

Perhaps connected, Elijah reports that in some cases -- her examples were Argentina and France, which is why I think this might be related -- the user selects a value from the pulldown menu and saves the new record, but when the record is viewed later, the spatial coverage value has disappeared and has to be re-entered manually, with a new record save.

@rybesh
Copy link
Member

rybesh commented May 12, 2017

@ptgolden Does this have something to do with facets not being recalculated after a change to a spatial coverage description?

@rybesh rybesh added the bug label May 12, 2017
@rybesh rybesh self-assigned this Jun 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants