The main goal for this week is to establish a dashboard that certain higher-privileged users can use to access statistics about the student-generated graphs. The dashboard should be accessed by a button that only appears if the logged-in user is in a list of high-privileged users (i.e. the professor of the class)
The dashboard will be populated via statistics returned from the backend API. We will establish a call called /getGraphStatistics which will return data about the graphs. At this point, the dashboard can simply be a separate window that shows each user, the number of nodes in their graph, and the number of links in their graph. However, it should be able to be extended to have other features in the future.
Professor username: wmt4
User Nodes Links
user1 10 20
...
[ ] Qingyu: add front end support for the dashboard
[x] Hayden: add backend support to return basic graph statistics per user
Other tasks:
[ ] I'm still working on configuring the UCI login system and how it will work with our system. We will use the shibboleth service to authenticate. More later on this.
[ ] Can we trigger an automatic submit upon user logout? What about if the browser window is closed? If there is an error in the graph, can we warn the user and prevent the window from closing? "Could not submit graph due to {some error}, are you sure you want to leave changes unsaved?"
[ ] The relationship labels should be on top of the relationship line, not below the line
[ ] The arrows should start and end at the edge of the node circles, not inside the circles
[ ] The link menu with "delete link" and "change link name" should come up when clicking on the relationship label in addition to the relationship line itself
Minor changes:
[ ] In the Create Node and Create Link popups, instead of "No" and "Yes", it should say "Cancel" and "Add"
[ ] On the side panel, "Node number" should just say "Nodes" and "Link number" should just say "Links"
[ ] Remove the notification "The graph is a subset!" when viewing the collective graph
The main goal for this week is to establish a dashboard that certain higher-privileged users can use to access statistics about the student-generated graphs. The dashboard should be accessed by a button that only appears if the logged-in user is in a list of high-privileged users (i.e. the professor of the class)
The dashboard will be populated via statistics returned from the backend API. We will establish a call called
/getGraphStatisticswhich will return data about the graphs. At this point, the dashboard can simply be a separate window that shows each user, the number of nodes in their graph, and the number of links in their graph. However, it should be able to be extended to have other features in the future.Professor username: wmt4
[ ] Qingyu: add front end support for the dashboard
[x] Hayden: add backend support to return basic graph statistics per user
Other tasks:
[ ] I'm still working on configuring the UCI login system and how it will work with our system. We will use the shibboleth service to authenticate. More later on this.
[ ] Can we trigger an automatic submit upon user logout? What about if the browser window is closed? If there is an error in the graph, can we warn the user and prevent the window from closing? "Could not submit graph due to {some error}, are you sure you want to leave changes unsaved?"
[ ] The relationship labels should be on top of the relationship line, not below the line
[ ] The arrows should start and end at the edge of the node circles, not inside the circles
[ ] The link menu with "delete link" and "change link name" should come up when clicking on the relationship label in addition to the relationship line itself
Minor changes:
[ ] In the Create Node and Create Link popups, instead of "No" and "Yes", it should say "Cancel" and "Add"
[ ] On the side panel, "Node number" should just say "Nodes" and "Link number" should just say "Links"
[ ] Remove the notification "The graph is a subset!" when viewing the collective graph