Admin page (System Admin POV) review and fixes
Hi @John.kopanas and @danjela
I've moved the Admin page briefs from issues #26 (closed) and #29 (closed) to the wiki.
I've reviewed the work completed to date, and ticked off the features that work as expected for each page and modal:
Create organisation modal:
-
1. Create organisation (enter name, email, and save) -
2. Change the status of the agreement from "pending" to "signed". -
3. On save, an email is sent to the email provided "[Organisation name] is active". ( I will discuss the wording for the email with NCBI)
Some minor fixes for this page:
-
1. The red text 'Name is Required' should read 'Name is required' (lower case 'r')
Overview of organisations page:
-
1. See all organisations, and click through to each org -
2. Search by organisation name and email -
3. Access the modal to create a new organisation -
4. Change the status of the agreement from "pending" to "signed". -
5. Delete organisations
Some minor fixes for this page:
-
1. The link 'Organization' should read 'Admin' -
2. The link 'NCBI' should read 'Bookshelf SFM'
Organisation page:
-
1. Edit organisation data (then cancel or save) -
2. View all users in the organisation -
2. Search all users in the organisation -
3. Change status of agreement -
4. Delete organisation -
5. Accept users' requests to join organisation -
6. Make users organisation admins -
7. Add accepted users to organisation teams -
8. Click through to users data -
For point 5 above: After creating 'Organisation A', I signed up as a user to that organisation. When I signed in as the Admin, there was no user to accept or reject.
-
For point 6 - 8: could not test
Some minor fixes for this page:
I have started an Editorial stylesheet here and I'm happy to make these kinds of changes myself. Otherwise, please search and replace throughout.
-
1. The button 'DELETE ORGANISATION' should read 'DELETE ORGANIZATION'. -
2. The column head 'E-MAIL' should read ''EMAIL'
User modal:
-
1. View the users data -
2. Edit the users data (troubleshooting purposes) -
3. Make a user an organisation admin -
5. Accept the user to the organisation -
6. Add or remove the accepted user to organisation teams -
7. Disable the accepted user
For all points above: I could not test because the signed up user wasn't shown