Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| courses:cs335:spring2019:graffiti:admin [2019/04/30 14:36] – [User Behavior] cohene | courses:cs335:spring2019:graffiti:admin [2019/04/30 17:29] – [What the User Sees] stalnakert |
|---|
| * 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 selection, allowing highlighting abilities. Besides, 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 management, editor management, and content management. More or fewer categories can be used per the preferences of the client. 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 could include functionality to check if the items entered qualified as blacklist items, that is, do the words even occur on the site currently. |
| |
| ====User Behavior==== | ====User Behavior==== |
