Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
courses:cs335:spring2019:graffiti:admin [2019/04/30 14:36] – [User Behavior] cohenecourses:cs335:spring2019:graffiti:admin [2019/05/01 01:33] – [Feature Description] cohene
Line 12: Line 12:
   * [[grafEdit|Edit Graffiti and EpiDocify Content]]   * [[grafEdit|Edit Graffiti and EpiDocify Content]]
   * [[blacklist|Blacklist and Group Words]]   * [[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==== ====Prerequisites====
  
Line 32: Line 32:
     * What data structures will best suit our needs?     * What data structures will best suit our needs?
 ==== What the User Sees ==== ==== What the User Sees ====
-The Admin should see a window asking for a login name and a password at login (maybe a Reset Password option?). 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. The EpiDoc functionality should be implemented in the specific graffiti selectionallowing highlighting abilitiesBesides, the user should be able to save the EpiDoc in the case of uploading new data. The blacklist index, which should have similar functionality to the actual index, should use the same structure as the actual index. We will communicate closely with the Index team to make sure they match. Besides, 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 managementeditor management, and content management More or fewer categories can be used per the preferences of the client.
 ====User Behavior==== ====User Behavior====
  
courses/cs335/spring2019/graffiti/admin.txt · Last modified: 2019/05/01 02:25 by cohene
CC Attribution-Noncommercial-Share Alike 4.0 International
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0