Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| courses:cs335:spring2019:graffiti:admin [2019/04/29 19:02] – [Feature Description] stalnakert | courses:cs335:spring2019:graffiti:admin [2019/05/01 02:25] (current) – [Relative Priority] cohene | ||
|---|---|---|---|
| Line 11: | Line 11: | ||
| * [[passChange|Password Changes]] | * [[passChange|Password Changes]] | ||
| * [[grafEdit|Edit Graffiti and EpiDocify Content]] | * [[grafEdit|Edit Graffiti and EpiDocify Content]] | ||
| - | * [[blacklist|Blacklist Words]] | + | * [[blacklist|Blacklist |
| - | * Generate Reports for All Graffiti | + | * [[reports|Generate Reports for All Graffiti]] |
| - | * Export all Graffiti Data as EpiDoc | + | * [[export|Export all Graffiti Data as EpiDoc]] |
| - | * Password recovery | + | |
| - | * Email passwords | + | |
| - | * Use the Washington and Lee University Computer Science Department server\\ | + | |
| - | * Record revisions to Epidoc | + | |
| - | * Save Epidoc | + | |
| - | * Reapply Epidoc | + | |
| - | * Edit Epidoc | + | |
| - | * Index maintenance | + | |
| - | * Add/remove words from the vocabulary index blacklist | + | |
| - | * Group words | + | |
| ====Prerequisites==== | ====Prerequisites==== | ||
| - | - An understanding of admin tools and their functionalities\\ | ||
| - | - An understanding of the EpiDoc: how does it work? what is the existing EpiDoc function look like? Anything we need to change?\\ | ||
| - | - An understanding of the blacklist index: what does the blacklist look like? what qualifies as a blacklist item? What data structures will best suit our needs\\ | ||
| - | ==== 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, | ||
| + | ===For Use=== | ||
| + | * The user must first navigate to the admin login portal (something for which there is not currently a link) | ||
| + | * The user must have a valid username and password, which they remember | ||
| + | * The users session must not have timed-out. | ||
| + | |||
| + | ===For Implementation=== | ||
| + | * An understanding of the various admin tools and their functionalities | ||
| + | * An understanding of the EpiDoc | ||
| + | * How does it work? | ||
| + | * What does the existing EpiDoc function look like? | ||
| + | * Is their anything we need to change? | ||
| + | * An understanding of the blacklist and the index | ||
| + | * What does the blacklist look like? | ||
| + | * What qualifies as a blacklist item? | ||
| + | * 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. | ||
| ====User Behavior==== | ====User Behavior==== | ||
| - | While the administrator will have all of the functionality that a regular | + | While the administrator will have all of the functionality that a regular |
| \\ | \\ | ||
| ====Use Cases==== | ====Use Cases==== | ||
| - | Many potential | + | The use cases of the various features |
| \\ | \\ | ||
| - | ====Relative Priority | + | ====Relative Priority==== |
| - | While this feature | + | While the Admin Tools might not be the top priority |
| + | * **High:** Edit Graffiti | ||
| + | * **Medium:** Managing Editors, Password Changes | ||
| + | * **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 | ||
