Enable assignment/tracking of DMP feedback reviews; enable feedback from multiple admins

[magdalenadrafiova]

@xsrust
We were asked to add some basic status tracking to the plan feedback notification table. This will display the department (if in use), allow anyone with reviewer privileges to be allocated or to self-select a plan and will provide basic status indications to show whether work is in progress.

[xsrust]

Rationelle of request

In the Netherlands, there are often 3 or more data-stewards who are responsible for the review of plans within an organisation. Generally, they are allocated across different schools/departments, so it would be helpful to display the plan's owner's department in this table.

Further, they need a way to keep track of who's reviewing which plan so that multiple people don't spend time on the same plan. Here, it would be nice to associate the reviewer with a plan, and mark that plan as under review to the other admins.

It's probably worthwile adding department as a column to the paginable table of plans on the same page while we're at it.

[briri]

related to #2367

[sjDCC]

Basic idea of feature to consult with users on

[briri]

As noted in #2450 we should move the feedback table to its own page.

We need to decide how a user would access the new page though. My recommendation would be through a new 'Feedback' menu item in the Admin Features menu. We could also possible display one of those red bubbles/dots that many apps now use to give the user a heads-up that there are plans requiring feedback.

[magdalenadrafiova]

Just addition to the ticket - admins would be also interested in the following:

see when the plan was:
last opened
last accessed
last edited

[xsrust]

@magdalenadrafiova
We currently display the time of last edit on each DMP as the updated column of the Plans table for admins.
I'm not entirely sure of the difference between last opened and last accessed, but we don't currently have a mechanism for tracking either.

I could see those being useful for any Plan within our system though, and don't know how they would relate to the feedback-specificly. It may make sense to open a new ticket for these new data-collection requirements. I could see those feeding into some more interesting statistics for the usage-dashboard as well.

[pherterich]

At our demo session today, it was suggested that some of this could also be duplicated on the plan page, e.g. have a complete feedback button on the "write plan" page so you don't have to click back to a dashboard to send the navigation. Not sure if that's very different and should be split out into a separate issue.