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
When a community curator receives a new inclusion/review request, just by looking at the request page (or the record preview) there's no clear indication of any failing checks.
We should explore adding the "summary" box from the original mockups above the comment textbox.
In app-rdm, change request jinja template to show a check tab if CHECKS_ENABLED=true and if there is any check for this request
In app-rdm, change request jinja template to show a status icon (errors, warning, success) in the check tab title based on the latest check overall status
In invenio-checks, create a service to retrieve the latest check for a request (move logic from app-rdm to invenio-checks)
Show content inside the checks tab (in which module?)
Since high interactivity not needed, if possible, implement in jinja like the records preview tab
Otherwise, change request jinja template to inject something like data-checks next to data-record inside <div id="request-detail" with a the JSON details needed to display https://doi.org/10.5281/zenodo.10901185 (bottom of page 10) and implement the checks tab content React
Move the template to invenio-checks
UI looking lis the mockup
The text was updated successfully, but these errors were encountered:
slint
changed the title
Community curator can't easily see in a request if there are failing checks just by looking at the request page (or the record preview)
checks: community curator can't easily see in a request if there are failing checks
Mar 20, 2025
When a community curator receives a new inclusion/review request, just by looking at the request page (or the record preview) there's no clear indication of any failing checks.
We should explore adding the "summary" box from the original mockups above the comment textbox.
In invenio-checks, create a service to retrieve the latest check for a request (move logic from app-rdm to invenio-checks)Otherwise, change request jinja template to inject something likedata-checks
next todata-record
inside<div id="request-detail"
with a the JSON details needed to display https://doi.org/10.5281/zenodo.10901185 (bottom of page 10) and implement the checks tab content ReactThe text was updated successfully, but these errors were encountered: