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

Reviewer Main Navigation Elements #193

Open
ricardobaeta opened this issue Mar 2, 2018 · 3 comments
Open

Reviewer Main Navigation Elements #193

ricardobaeta opened this issue Mar 2, 2018 · 3 comments
Labels
enhancement Improvements are needed over an existent feature v1 v1 candidates

Comments

@ricardobaeta
Copy link
Contributor

ricardobaeta commented Mar 2, 2018

We have to rethink the main navigation for Requester. For the Worker we have a solid navigation, but the Requester still needs a little love. We must have a way to move forward and backwards. The PREVIOUS dropdown/button should only enable the user to go backwards, and this raises the need of a navigation element to move forward. We must have a NEXT button, creating therefore a consistent navigation for this profile.

@ricardobaeta
Copy link
Contributor Author

ricardobaeta commented Mar 2, 2018

@dpordomingo @bzz @smacker @carlosms

Here's the wireframe for the Reviewer's Main Navigation. The NEXT button should convey btn btn-info to couple with Annotator's Main Navigation SKIP button.

screen shot 2018-03-02 at 14 58 54

Side-note: The PREVIOUS button/dropdown should only enable backwards navigation on the survey.

@dpordomingo dpordomingo added enhancement Improvements are needed over an existent feature v1 v1 candidates labels Mar 9, 2018
@dpordomingo
Copy link
Contributor

Thanks @ricardobaeta for rewording the issue desc; now it's clear!!!

Let me ask one related question:
Should the worker view follow the same logic? I mean: should the PREVIOUS button on the Requester view, list only the previous FilePairs?

@ricardobaeta
Copy link
Contributor Author

Yes @dpordomingo :) Previous is only previous :) We're getting feedback on the need to move forward based on ID, or search, but that's other thing we need to tackle in a separate issue :) And after research report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvements are needed over an existent feature v1 v1 candidates
Projects
None yet
Development

No branches or pull requests

2 participants