Administrator #1114
Open
Administrator #1114
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…strator routing to router.js
…le, Added displayDataChangedAction that submits another action to the router which submits a new query based on the sort/filter requested.
… and Award Cells. Added drop down filtering for status cell
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The goal of this branch was to create a dashboard aimed at a super user, who should have access to all the submissions and grants.
For more information regarding super user requirements, see the google docs below.
Similar to the Submission and Grants dashboard, the Administrator dashboard populates the data in to the Ember Models Table. The aim was to have all the columns be sortable and filterable from Elastic Search. The only columns that, however, could be filterable/ sortable were those that had direct access to the data.
I could not find a solution for columns that relied on URI to access their data, like the publication in the Submission model. A possible fix that was suggested by my advisor, Mark Patton, was to have the Elastic Search document index changed.
https://docs.google.com/document/d/1Tcaf53ghYZcf33zwDvhDZxfC12WOrg0WngmgfFFAIjY/edit#heading=h.jitx4pf4gow6