search

SpeciesFileGroup / taxonworks

Workbench for biodiversity informatics.
http://taxonworks.org
Other
85 stars 25 forks source link

Task - Browse Collection Objects - Next/previous buttons unhidden behind Go (Feature request). #3229

Closed AntWeb-org closed 1 year ago

AntWeb-org commented 1 year ago

Feature or enhancement

Would like a 'Previous/Next by ID' button on CO display page that is not hidden within additional 'Go'/Navigate button. Similar to 'Previous/Next' found in Browse CE display but with 'by ID'.

Location

Task - Browse Collection Objects

Screenshot, napkin sketch of interface, or conceptual description

No response

Your role

No response

AntWeb-org commented 1 year ago

@bpescador, @chrisgrinter, @rich-keller

mjy commented 1 year ago

Can you clarify whether you want this by true ID, i.e. internal, with no semantic meaning, or by a proxy, i.e. Catalog Number?

mjy commented 1 year ago

And b) would a hotkey bound to next/previous be a suitable work-around?

AntWeb-org commented 1 year ago

Catalog number would be great. I'd try the workaround for starters.

mjy commented 1 year ago

Catalog number, in our experience, requires the "Go", it takes time to compute (we even just added some caching to speed it up), and we don't want to wait for all the options to calculate for those who don't need it. We've iterated on this several times already, it was originally requested as herin, then people wanted more, or different. I feel this reflects on where the project is at, it's begining, mid, or near the end (just slamming in data, working through specific data points, cleaning up on a few things at the end, for example). I'm not sure what best overal solution is.

One other thought is that you have a filter window open, with the range of catalog numbers selected, then you pivot specimen to specimen that way, using tabs.

Again though, unsure where the balance is.

BTW - thanks for "itemizing" or keeping this to a single issue. It's good to group them for context in some cases, but in the long run having one issue per TODO is the way to go.

AntWeb-org commented 1 year ago

Thanks for the feedback. I'll send each feature request separately unless they are connected in some way. Do you prefer UI Issues separate as well or itemized?

mjy commented 1 year ago

Itemized please! Thanks.

On Tue, Dec 13, 2022 at 10:57 AM AntWeb-org @.***> wrote:

Thanks for the feedback. I'll send each feature request separately unless they are connected in some way. Do you prefer UI Issues separate as well or itemized?

— Reply to this email directly, view it on GitHub https://github.com/SpeciesFileGroup/taxonworks/issues/3229#issuecomment-1349061339, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAFQSHH3BD4FD4HJW6H2QLWNCTGRANCNFSM6AAAAAAS4ORN4A . You are receiving this because you commented.Message ID: @.***>