Differences

This shows you the differences between two versions of the page.

--- courses:cs335:spring2019:graffiti:admin [2019/04/30 15:21] – [What the User Sees] stalnakert
+++ courses:cs335:spring2019:graffiti:admin [2019/05/01 02:25] (current) – [Relative Priority] cohene
@@ Line 12: / Line 12: @@
   * [[grafEdit|Edit Graffiti and EpiDocify Content]]
   * [[blacklist|Blacklist and Group Words]]
-  * Generate Reports for All Graffiti
+  * [[reports|Generate Reports for All Graffiti]]
-  * Export all Graffiti Data as EpiDoc
+  * [[export|Export all Graffiti Data as EpiDoc]]
 ====Prerequisites====
@@ Line 32: / Line 32: @@
     * What data structures will best suit our needs?
 ==== What the User Sees ====
-The administrator or a user that managed to navigate to the admin authorization page should see a window asking for a username and a password. These two fields are represented by text field and password field respectively.  Once the admin logs in successfully, they should see a list of tools laid out clearly on the page, with each tool linking to a new page that has the corresponding admin functionality. These links will ideally be sorted in a way that maximizes usability for administrators and editors.  Currently we consider three groupings of the links: account management, editor management, and content management.  More or fewer categories can be used per the preferences of the client. The EpiDoc functionality is mostly already implemented in the specific graffiti selection, allowing highlighting abilities. The user should be able to save the EpiDoc changes to the database.  This too should already be implemented, but may require some tweeks or fine-tuning.  The blacklist will feature words in a tabled format that should not be included in the index.  The feature for removing these words will look very similar, with the addition of a remove check box for each word.  The user will see a text-field when they go to add words to the blacklist.  Maybe the current blacklist should also be displayed for reference.   The website should be able to check if the items entered qualified as blacklist items.
+The administrator or a user that managed to navigate to the admin authorization page should see a window asking for a username and a password. These two fields are represented by text field and password field respectively.  Once the admin logs in successfully, they should see a list of tools laid out clearly on the page, with each tool linking to a new page that has the corresponding admin functionality. These links will ideally be sorted in a way that maximizes usability for administrators and editors.  Currently we consider three groupings of the links: account management, editor management, and content management.  More or fewer categories can be used per the preferences of the client.
 ====User Behavior====
@@ Line 43: / Line 42: @@
 ====Relative Priority====
 While the Admin Tools might not be the top priority on this project, it still has fairly high priority as administrators will need to access functionality of the site that typical visitors of the site are unable to. In terms of priority of the individual Admin Tools features, the priority is as follows, from high priority to low priority:
-  * **High:** Generate Reports for All Graffiti, Export all Graffiti Data as Epidoc
+  * **High:** Edit Graffiti and EpiDocify Content
-  * **Medium:** Managing Editors, Password Changes, Edit Graffiti and EpiDocify Content
+  * **Medium:** Managing Editors, Password Changes
-  * **Low:** Blacklist and Group Words for the Index
+  * **Low:** Blacklist and Group Words for the Index, Generate Reports for All Graffiti, Export all Graffiti Data as Epidoc
 More in-depth descriptions about the prioritization of each feature can be seen within the individual feature's page.