Admin Tools

The Admin Tools page will provide an administrator with the tools they need to manage the Ancient Graffiti Project's data. An administrator account (these will be the only accounts, but could they possibly have different permissions?), will be able to update their own passwords, add an editor, remove an editor, see all current editor accounts, edit graffiti, update EpiDocs, generate reports for all graffiti, export all graffiti as an EpiDoc file, add words to the blacklist, remove words from the blacklist, and see all words currently blacklisted. Before a user can have access to all of these features, they must first sign-in as an administrator. This is done through a login screen, where the user must supply a valid username and password. New accounts should not be created at this phase. Only current administrators should have the authority to add accounts. This will protect the integrity of the data on the site. Once the admin is logged in, they will be taken to an editing hub. Here they will find links to the pages where they can exercise their various permissions, neatly and properly organized of course. Each of these features respective pages will need to be designed and implemented, though it should be mentioned that preliminary versions of many already exist.

Feature Description

Prerequisites

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. 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

While the administrator will have all of the functionality that a regular visitor of the site does, they will have additional functionality to fit their needs. Administrators will be able to use the features described on the individual feature pages, while other visitors will only be able to access the login page. This will be the extent of the access to Admin Tools that a visitor of the site will have, as they will not be able to successfully login.

Use Cases

The use cases of the various features are listed within the individual features.

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: Edit Graffiti and EpiDocify Content
  • 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 can be seen within the individual feature's page.

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