You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an output checker going to the requests page, the first thing you see is your personal requests, which if i'm visiting as an output checker I don't care about. I'd prefer to have a page where, as a researcher you can see your workspaces and your requests and then a separate page for output checkers where you just see any open requests.
Implementation notes
In airlock/views/request.py, create two new view functions to replace request_index. One should be called requests_for_researcher and the other should be called requests_for_output_checker.
requests_for_researcher should pass the results of calling bll.get_requests_authored_by_user() to a new template (requests_for_researcher.html), which should only contain the relevant parts of requests.html.
requests_for_output_checker should first check that the user is an output checker (via permissions.user_can_review(request.user)) and raise PermissionDenied if not. If the user is an output checker, it should calculate outstanding_requests, returned_requests, and approved_requests, and pass these to a new template (requests_for_output_checker.html), which should only contain the relevant parts of requests.html.
In airlock/urls.py, add two new patterns for these two new view functions.
In airlock/urls.py, add a redirect from "requests/" to the new requests_for_researcher view.
Having done this, we should get input from users (including @LFISHER7) about how to navigate to these new pages.
The text was updated successfully, but these errors were encountered:
From @LFISHER7:
Implementation notes
request_index
. One should be calledrequests_for_researcher
and the other should be calledrequests_for_output_checker
.requests_for_researcher
should pass the results of callingbll.get_requests_authored_by_user()
to a new template (requests_for_researcher.html), which should only contain the relevant parts of requests.html.requests_for_output_checker
should first check that the user is an output checker (viapermissions.user_can_review(request.user)
) and raisePermissionDenied
if not. If the user is an output checker, it should calculateoutstanding_requests
,returned_requests
, andapproved_requests
, and pass these to a new template (requests_for_output_checker.html), which should only contain the relevant parts of requests.html."requests/"
to the newrequests_for_researcher
view.The text was updated successfully, but these errors were encountered: