This is an old revision of the document!


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

  • Create new logins
  • Password recovery
    • Email passwords
    • Use the Washington and Lee University Computer Science Department server
  • Password Changes
    • Should probably require the user to input their current password
  • Record revisions to Epidoc
    • Save Epidoc
    • Reapply Epidoc
  • Edit Epidoc
  • Index maintenance
    • Add/remove words from the vocabulary index blacklist
    • Group words

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

User Behavior

While the administrator will have all of the functionality that a regular user does, they will have additional functionality to fit their needs. What the administrators are doing on the page might be slightly different than a typical user. First and foremost, an administrator might perform any of the activities listed when they first log in: Edit a Graffito, Generate a Report for all Graffiti, Download all Graffiti as an Epidoc, Change their Password, Add a new Editor, and/or Remove an Editor. When viewing any Graffito, an administrator can edit that Graffito. When viewing all of the graffiti, an admin can generate a report.

Use Cases

Many potential use cases of an administrator are listed above. Some functionality we are hoping to bring to this feature is to create new admin logins, store admin information, use that information to see who made revisions, allow admins to add/remove words from a list of “blacklist” vocabulary on the index, and to group words on the index. For example, if an administrator notices that there have been some changes on a graffito, they can look to see what administrator made those changes. There might be potential to even notify an administrator if a change has been made.

Relative Priority of Feature

While this feature might not be the top priority, it still has fairly high priority as administrators will require different permissions than typical users to make updates and edits to the content easily and efficiently. Certain functionality within this feature has higher priority than others. For example, allowing new logins, and tracking the Epidoc is much more important to this feature than the vocabulary index “blacklist” and the ability to group words together.

courses/cs335/spring2019/graffiti/admin.1556564209.txt.gz · Last modified: 2019/04/29 18:56 by stalnakert
CC Attribution-Noncommercial-Share Alike 4.0 International
Driven by DokuWiki Recent changes RSS feed Valid CSS Valid XHTML 1.0