Testing for Admin Dashboard

[sebastianbarry]

I have started the admin dashboard found at https://github.com/e-mission/op-admin-dashboard/tree/master and it is working!

I had expected to see more of the other changes, such as the Token generation button, view available tokens, etc. but what I got on my computer working looks far more barebones than that, I may be checking out the wrong branch:

@shankari I see that you are the only person who has made commits to this branch, is @asiripanich branch somewhere?

[asiripanich]

Hi @sebastianbarry, please see the dev branch. We are in the final stages of implementing the authentication. :)

The code in master is just a Dash dashboard template from NREL visualisation team.

[sebastianbarry]

Thanks @asiripanich! I have switched to the dev branch but I'm having trouble using docker-compose, it seems to be getting hung up on this point:

Additional info:

• I did delete my Docker images and containers, and re-built and started the containers again and am still getting hung up at this same point.
• I am also not connected to any VPN or anything.

Have you encountered this before, or have any tips for me?

[sebastianbarry]

I see that this line was added to the dev branch in this commit: e-mission/op-admin-dashboard@054132c#diff-f34da55ca08f1a30591d8b0b3e885bcc678537b2a9a4aadea4f190806b374ddc

This may be why the main branch was working for me but the dev branch is not (using docker-compose method)

[asiripanich]

I havent tested the latest version of commits. Alireza should be able to guide you to setup the dashboard during our today meeting. :)

[sebastianbarry]

I was able to get the admin dashboard working and loaded some test user data!

Here are my thoughts while testing

Screenshot of issue	Explanation of issue
	So far the dashboard looks good. I am not used to being a program admin, so I don't know how helpful or important the diagram of "user sign up count" would be, that requires them to be on the first page dashboard, but I do believe the diagrams look really good and are easy to interact with
	I see that the users opcodes are loaded in the above image, that is great! I know that one of the challenges of admins is knowing which User's name/email associates with which OPcode, @shankari would it be against users data privacy if we were to store this information together?
	Because a lot of our users are in US, we may want to change this date picker to be in the mm/dd/yyyy format
	Occasionally the loading takes a while and I have no feedback that it is loading, is it possible to add some sort of animated loading circles until the page has fully loaded?
	Here's another example where a loading animation would be very informative, since without this, the loading on this screen when you click "trips" takes about 8 seconds and without some sort of feedback that it is loading, I would think that the data for "trips" and "UUIDs" would be the same
	What are the requirements that consider a user an "active user". If I were a program admin, I would be alarmed that I have 14 users but none of them are "active?".
	This map froze the webpage for about 3 minutes before it loaded and it took a lot of computer power to do so (see the Firefox error I got at the top of the screenshot)

[shankari]

@sebastianbarry

I was able to get the admin dashboard working and loaded some test user data!

how much test user data?

I know that one of the challenges of admins is knowing which User's name/email associates with which OPcode, would it be against users data privacy if we were to store this information together?

correct. we are not allowed to store any PII (name/email etc) on the NREL hosted system per our cyber security rules. Most admins store this separately in an excel file/google doc on their local computer.

Because a lot of our users are in US, we may want to change this date picker to be in the mm/dd/yyyy format

@asiripanich and @AlirezaRa94 are not building this as a custom project for NREL, they are contributing this to the open source community. As such, we should not hardcode any country-specific assumptions unless absolutely essential. For dates/times, I would suggest using a locale-specific display method (e.g. https://docs.python.org/3/library/locale.html)

[shankari]

Closing this since the related issues are being tracked separately in the admin dashboard repo