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

Collapse query results well from bottom (in addition to the top) #20

Closed
peterdm opened this issue Nov 8, 2019 · 2 comments
Closed

Collapse query results well from bottom (in addition to the top) #20

peterdm opened this issue Nov 8, 2019 · 2 comments

Comments

@peterdm
Copy link

peterdm commented Nov 8, 2019

Is your feature request related to a problem? Please describe.
I most frequently enter judgments on a single query at a time. If multiple wells are open at once it's very easy to lose track of which query is being worked with so I close each query well once I'm done rating.

In order to close a query well, I need to scroll all the way back up to the query header (often 2-3 swipes), stop exactly on the header, and then click the collapse trigger (glyphicon-chevron-up)

Describe the solution you'd like
Currently the collapse trigger lives in the header (up top), but I tend to work my way down the results and then want to collapse the query once I've finished rating all the unrated. A second trigger (glyphicon-chevron-up) at the bottom of results (in the right side of the "Peek at..." div) would remove most of the excess scrolling from this task.

Describe alternatives you've considered (not exclusive)
Alternative 1: If the query header for the query-results in view scrolls up out of the frame, freeze and stack that div under the quepid-header-div allowing the results for the query in focus to scroll underneath it. This way the existing collapse trigger is always in view. (Actually probably a more usable solution... just requires more work)

Alternative 2: Automatically collapse once no "unrated" results remain.

Bonus 3: Keyboard shortcuts (right-arrow open well, left-arrow close well, up/down focus on next result-or-query which is visible above focus (last action).

Additional context
Accelerating judgment entry in Quepid reduces the overall time needed to build judgments. Since the OSC engagement model pushes judgments as a prerequisite, the effort of building judgment lists is likely a major brake on engagement with OSC. Faster human automatons == more work for OSC :-)

@epugh
Copy link
Member

epugh commented Nov 24, 2019

This makes a lot of sense, and does highlight that maybe we need a view to Quepid that is optimized for the rater experience ;-) But that is a whole nother thing! I'm hoping someone picks this issue up, or that i can get to it.

@epugh
Copy link
Member

epugh commented Jan 8, 2020

And fixed! Will push to app.quepid.com on January 10th.

@epugh epugh closed this as completed Jan 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants