Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

These are the gaps identified by the Core schools that were still outstanding at 1.5

Core Apps

  • Gap 265: Heirarchical organization of sites
  • Gap 272: Section subsites may inherit items from the main class site
    • Child section inheritance is tool specific
    • Editing permissions also inherited
  • Gap 260/18: Ability to create groups/subgroups within list / Support for group restriction in every tool
    • These groups provide the author with the ability to restrict certain tools within the application to a subset of the entire class
  • Gap 22: Ability for users to organize sites by semester/term
  • Gap 275: Add student view for instructor for every tool
  • Gap 205: Allow varying levels of administrator access
    • On a system-wide/site-side level for the CMS, Stanford's CourseWork has a higher class of administrator or 'super-user' with the capability to do anything that a 'regular' administrator (Admin) does in any course. This super-user also has the ability to perform system admin functions through the CMS's GUI
  • Gap 206/207: Full author access to all sites without being a member - can be restricted by department / Ability to move through course as if faculty of record in course
  • Gap 244/246: Syllabus tool / Allow file upload
  • Gap 11: Ability to disable users (removes user's access without removing membership)
    • Set a user's access to a particular course either to "Active" or "Inactive". Setting this status does not limit the user's access to other courses or remove data associated with that particular user. If a user is inactivated, s/he can later be reactivated.
  • Gap 213: Ability to post global announcements (posted to every site in system
    • The system administrator can post messages (e.g. "this website will be read-only from midnight to 1 a.m. today while we update the servers") which all users see when they log-in to the application. The system administrator can remove the message when it is no longer appropriate.
  • Gap 284: The ability to enable public access (as a group)
    • An instructor should be able to make their site world readable. This means they can post the URL for their class to their favorite yahoo group (for example) and know that everyone will guest access to the site with out having to worry about adding permissions for anyone. There are no guest accounts, and no prompts for authentication at all. From the guest's perspective it will be just like entering any world-readable site on the web.
  • Gap 42: Ability to control what content appears on homepage and it's layout - option to have formatted course information
    • Class template - Every class homepage displays this information in this order, which makes it easy for students to browse through class websites.
  • Gap 277: Centralized repository for file upload with ability to restrict access based on permissions
    • Within Stanford's CourseWork system exists a tool called Course Materials. Instructors/Admins can post and organize materials for electronic distribution to course members. Materials that are uploaded in other tools, like Assignments, will also be shown in this central repository. Admins can set visibility for students to visible or hidden.
  • Gap 23: Ability for user to enter personal information and allow restriction based on system defined role (Profile Tool)
  • Gap 149: Ability to create multiple discussion forums in a single site
  • Gap 258: Aggregate statistics for each term can be generated with number of courses, students, instructors,TAs, grades, guests, Headcounts,etc. and exported to excel. By term or course
  • Gap 208: Edit faculty of record information
  • Gap 173: Private Chat
    • Click on a name in the chat presence and open a separate, non logable chat room
    • Different than whisper – whispers are logged
  • Gap 211: Ability to change username within CMS WE DON'T WANT THIS
  • Gap 212: Ability to query production database via web interface
    • Super-users can query the current user sessions.
    • This feature is used to ascertain who and how many currently logged as well as aid developers with what is contained in users' sessions.

Gradebook Specific

  • Gap 153: Allow point value
  • Gap 221: All activity based on permissions/roles
  • Gap 228: Specify grade scale (A+ - F) using points or percentages (Gradebook)
  • Gap 230: Specify total points or percentage of final grade for auto-calculating gradebook (Gradebook)
  • Gap 232: Specify columns (title, number and descriptive data) (Gradebook)
  • Gap 234: Final course grade, total points, running stats (mean, median, etc.) column with ability to hide from students (Gradebook)
  • Gap 236: Ability to automatically transfer grades from assessment tool
  • Gap 242: Allow export of gradebook to .CSV
  • Gap 266: System wide back button works
  • Gap 280: Support for foreign language (European, Asian (Chinese, Japanese), Semitic (Arabic, Hebrew))
  • No labels