Request - Update documentation pop-ups for search fields in "Place" section of record search

[genevieve-anderegg]

Describe what you're trying to do

From geography committee meeting yesterday @happiah-madson @falco-rk @sharpphyl @dustymc @mkoo Specific items that need updating on the Place section of the catalog record search page as mentioned in https://github.com/ArctosDB/arctos/issues/8272 Picture of the part of the catalog record search page in question:

Many of these fields do not have documentation in the pop ups describing what they are/what they do. Here is a list of the fields and what is missing (or where there are bugs!):

• [ ] Any Geographic Element - bug, links instead to AnyID documentation (fixed in next release)
• [ ] Geography Shape Name - "concatenation" misspelling - probably needs a better definition too (made less Finnish, better definition most welcome)
• [ ] Place Terms - no documentation (fixed for next release)
• [ ] Age (Mya) - no documentation (see below)
• [ ] Chronostratigraphy - links to "age" - bug? (not exactly, but kinda - these draw from CT metadata, IDK how to better define them without just adding confusion, help?? https://github.com/ArctosDB/PG/blob/master/includes/specimenSearchQueryCode__param.cfm#L4407)
• [ ] Feature - no documentation ()
• [ ] Quad - no documentation
• [ ] Coordinate Precision - no documentation
• [ ] Asserted Continent/Ocean - no documentation
• [ ] Asserted Sea - no documentation
• [ ] Asserted Country - no documentation
• [ ] Asserted State/Province -"Curatorially-asserted state or province" (could be more specific "per GADM" - DLM - thats just current, I very much do not want to hard-code a source here! - and this may not survive long anyway)
• [ ] Asserted County - Curatorially-asserted GADM2-level geography. (see above)

Suggesions:

• There should be clarification between which fields search textually, and which spatially, and which both.
• It should be clear that "Asserted" fields mean things that are used for Higher Geography as per GADM. THese should also probably be grouped together under their own subheading
• Age and Chronostratigraphy can be grouped under their own subheading specifying that they are for fossils

Please tell me to split these out into separate issues as necessary. -- we can track here!

[mkoo]

Thanks for getting this organized Genna (and taking my speedcall yesterday!) I think I will edit your post so we can check off the ones with new definitions/ suggested entries-- are you going to add them here in the issue or have them in a separate google table? What's easiest for the group? Add that info here and we can adjust this into a workable task!

[happiah-madson]

I think that ultimately we should have a separate google table. But per our WG meeting this week, @genevieve-anderegg @sharpphyl and I don't know the answers to a lot of these things. We need someone with technical information to weigh in on a lot/most of these fields.

[happiah-madson]

I've converted @genevieve-anderegg 's documentation above to a google table. I've tried to capture the types of information we think is useful to know, as well as a place to revise definitions. Feel free to edit!

https://docs.google.com/spreadsheets/d/10L_1rMklTg2SINIqPuyVGOnU5zlKZIdN2EmZmerfwS4/edit?gid=0#gid=0

[genevieve-anderegg]

Thank you @happiah-madson ! And agreeing that we will need @mkoo and @dustymc technical knowledge of how these fields work in order to update the documentation.

[dustymc]

Some comments in the initial issue, probably need to wait for a release to move, more here...

clarification between which fields search textually, and which spatially, and which both.

"yes" - not sure this can be adequately explained in a language other than SQL...

"Asserted" fields mean things that are used for Higher Geography

.. and maybe locality attributes and such...

as per GADM

nope

specifying that they are for fossils

Not really?? Plants grow in association with rocks of certain ages, the rocks get cataloged, etc, lots of reasons these data might noy involve a fossil (but not sure we actually do any of that at the moment).

[happiah-madson]

Our next Geog meeting is on 12/2 at 12/3pm. @dustymc and @mkoo are you able to come? Seems like we could talk about this issue there.