Requirements Summary

We want this ready for initial review in mid-August and field testing by mid-September. We need to be frugal about requirements in order to do this. Note that as a simplification, initially, the coordinator and lexicographer will be merged into one coordinator role.

Everyone

• Request an account
• Request a password reset
• Creation of a new community (note you become the project coordinator)
• Creation of a new project. (note you become the project coordinator)

Logged in User can (using WeSay as a model)

• Above +
• Gather words
• From Texts
• From Semantic Domains
• From a word list
• Browse and edit
• Add Information
• Add Meanings
• Add grammatical usage
• Add examples
• Discuss Words (a comment will be a vote (down or up) and then text that tells why
• Comment on Meanings
• Comment on Grammatical usage
• Comment on examples
• Change what fields show
• Change what fonts show

Lexicographer can

• Above +
• Add or remove languages
• Process Web submissions (under review, approved, rejected)
• Process comments (todo, review, resolved)
• Respond to comments made by individuals (so all users can see thread)
• Resolve comments made by individuals (e.g. the lexicographer has determined that the comment has been addressed) (todo, review, resolved)
• Set up the project
• Input systems,
• fields
• Tasks
• Approve users to be part of the project
• Invite users to be part of a project
• Import a LIFT database
• Connect to an existing FieldWorks or WeSay repository

System Admin

Above + Can delete any project

The Lexical Web App will

• If they do not exist - Create the custom fields to denote
  • Web generated content
    • “web app created” content (true or false)
    • Current “state” of web app created content (under review, approved, rejected)
    • Web generated content state change information
      • Person who changed state
      • Date of state change
    • Comments
      • Votes field for each commentable field (how many votes)
      • Comment field for each commentable field
      • Commenter
      • Date comment created
      • Status (todo, reviewed, resolved)
      • reply information
        • Reply statement
        • Person who replied
        • Date of reply

• Each time new content is created via the web app:
  • Mark content as web created if created via the web app
  • Mark content state as “under review”
  • Denote date content created
  • Denote author
• Each time a new comment is created
  • Mark content as in a “todo” state
  • Denote comment date
  • Denote comment author