Request - Clarify "Place" fields and search results (and a watery example) #8272
Labels
Curatorial Search
Function-Locality/Event/Georeferencing
geography
Geography-focused issues
Priority-High (Needed for work)
High because this is causing a delay in important collection work..
Help us understand your request (check below):
Describe what you're trying to do
Related Issues: https://github.com/ArctosDB/code-table-work/issues/59 , most recent activity in https://github.com/orgs/ArctosDB/projects/30
Currently, searching for records by place data in Arctos on the main catalog record page is confusing and not streamlined. Some fields search by locality spatial data (coordinates), some by text (from multiple different fields), and some by both. This is not immediately clear, as many of these fields are missing information in the documentation pop-ups.
A UI update that groups fields together with subheadings, or organizes them more thoughtfully would be useful.
The main reason for this issue is that data describing location of things collected in a waterbody are very unstandardized. You can have watery locality data in: Higher Geography (which has some oceans and seas) and Specific Locality (which can be any text data; and you might need to have your waterbody data here because you ALSO need to pick an administrative area for Higher Geography instead).
You can also search by Associated Names, which are chosen by a service based on which spatial shapes intersect with the coordinates (but this is resource limited). And you can search with a polygon or by selecting a drop down from
All of these search capabilities and fields are useful in their own ways, but they are all slightly different and give different results depending on the data. Because Waterbody in Arctos is not standardized (way less standardized than terrestrial data), searching for different things gives different results (which again isn't necessarily terrible because each is useful for different things) but the overall process is opaque.
Hopefully this helps explain our need for the Darwincore Waterbody field. Then we could search by this one field and pull up every record we want regardless of if there are coordinates, if Associated Names have been applied, what the Higher Geography is, etc.
Example with DMNS:Inv courtesy of @sharpphyl :
The text was updated successfully, but these errors were encountered: