-
Notifications
You must be signed in to change notification settings - Fork 11
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
dashboard: show more information on submission participants in manager widget #469
Comments
The information contained in the Looking at the code for the manager widget, there is a line:
that doesn't seem to do anything apart from print four dashes. It could be that this line was the start of an uncompleted implementation to show information on "Recent Activity" of participants. It can be removed if we add "Claimed" and "Last Action" columns for each primary participant. |
Could/should the 'last action' column show what the last action is as well as giving the time indication? e.g. Uploader:
Reviewer:
|
We already have information on whether data has been uploaded, how many tables, and the review status of each table in the visualisation on the left-hand side of each entry in the main Dashboard. So maybe better not to duplicate this information in the manager widget, and just show a "Claimed" checkbox and "Last Action" timestamp. |
Related to this, there is however an interesting feature that could help coordinators, namely, a basic mechanism to inform the coordinator when the persons nominated to different roles regarding an on-going encoding actually interact with the HepData portal based either on the email they receive or simply by accessing the temporary record created for the encoding. This would be of great help in order to understand why for some records there is no progress for a long time and it could help in re-opening discussions about the feasibility of publishing some specific record to HepData (some times proponents are urged to prepare their measurement for HepData, but discover at some point during journal review there is either no time to invest in this action or there are no more available human resources for the task). I think what I propose is to have a limited amount of time (a few months) for an invitation to expire and then have the dashboard pop-up some warning that the record is "forgotten". I could open a different issue on the subject if you consider it worthy of debate.
Originally posted by @alex-t-grecu in #94 (comment)
The text was updated successfully, but these errors were encountered: