SpeciesFileGroup / taxonworks

Workbench for biodiversity informatics.
http://taxonworks.org
MIT License
87 stars 26 forks source link

Geographic Area -> Show: Previous/Next button not alphabetical below country level #3255

Closed AntWeb-org closed 1 year ago

AntWeb-org commented 1 year ago

Feature or enhancement

From the Geographic Area Lookup task, search Italy then click on any Italy. In the GA page the Previous/Next button scrolls alphabetically through countries, but below the country level Previous/Next scrolling seems arbitrary.

For example, search and click Arizona in Honduras from the GA page and the first record is:

Name: Arizona Parent: Atlántida

Next

Name: Brus Laguna Parent: Gracias a Dios

Next

Name: Jutiapa Parent: Atlántida

Next

Name: Azacualpa Parent: Santa Bárbara

Perhaps Previous/Next options on the GA could be alphabetical, i.e., Arizona in Honduras should be followed by Arizona in the United States. There could be an additional option for Previous/Next within country or state but I am unclear on what Previous/Next is scrolling through below the country level.

@bpescador, @chrisgrinter, @rich-keller

Location

Task - Geographic Area Lookup - Geographic Areas

Screenshot, napkin sketch of interface, or conceptual description

No response

Your role

No response

mjy commented 1 year ago

GA page the Previous/Next button scrolls alphabetically through countrie

It navigates by (internal) ID, it is by chance that countries were loaded first.

Show navigation back/forth is a scaffolded view. By this we mean any model uses the exact same code. This permits us to create many show view quickly, but each one is limited in some way to act like all the others. Here we take advantage of the fact that all internal records have an ID, so we sort on that property.

As mentioned in other issues these are auto-generated views, "Show", like /<model>/:id are not intended to be part of day-today routines, but rather as debugging or last-chance checks on the data.

We haven't had requests to browse the GA in our "Filter" style world (I think this is the functionality you're geting at) or to flesh out a "Browse geographic area". If we can demonstrate the need for such we can build it out. I can imagine uses, but prioritization-wise we're going to be limited to building testing improvements like those proposed here.

Antweb definitely has different needs (a focus on curating existing data rather than producing new data), than the communities we've worked with so far. So this isn't an outright dismissal, it's a feeling-out of where this concept truly fits in TW.

mjy commented 1 year ago

Closing as stale. This hasn't come up as an issue, Geographic Areas in this view are rarelys used in the curatorial interface, and access via the autocompeltes and maps make navigation/choice fairly seemless.