The extensible nature of this project makes a number of options possible. All of the below meet particular school needs, and fit into the overall model, but are clearly out of scope at present time. Items will be removed from this list when they become relevant to the scope of the current version.

Version 1.0 Scope excludes:

• pushing information TO WatIAM
  • warning if WatIAM room information conflicts with existing data (would be useful, but requires access to postgres WatIAM database).
• pushing information directly to the RSG subscriptions database (perhaps for future version)
• interfacing with, or replacing, the Grad Office filemaker database. Grad office is comfortable with this decision. (perhaps for future version)
• Users: for a future version:
  • Grad students: read-access (or partial write access) to their own records
    • recording extended grad student user-added free-form information, such as preferred languages, titles/roles
    • gender: used for reporting on equity/balance
    • TA selections: major app addition: replacing grad TA app (if Isaac's project isn't very far).
  • Faculty: read-access (or partial write access) to their own records, and records relevant to their research-groups / office areas
  • Staff: read-access (or partial write access)
• recording extended information useful for all users:
  • general relationships table replacing "supervised by" column. Used for faculty/staff/students to make web-pages and reports. (eg., staff admin X is Faculty Support for Prof. Y)
  • committee roles (faculty): used for web-page of current committee makeup and potentially to replace SACA web-app authorization
  • job responsibilities (staff): used for web-pages of "who's responsible for what".
  • Photo URL (relationship to stalled project to provide grad student photos; and to WCMS photo-uploads for staff/faculty).

-- DanielAllen - 25 Mar 2013