SVM Historical Requriments

This is the original requriments document that we were basing our needs on before Beau broke it apart and added in additional Faculty requirements.

AuthZ,AuthN

  • Log-in allows for use of central university username and kerberos password to access portal.
  • Access to specific applications within portal (VMACS/EPIC) without additional login.
  • Timeout function that logs user out after a defined period of inactivity.
  • Well defined roles determine functionality within the portal and access to applications.
    • Define our role requirements here...(Including librarian access)

Calendar

  • Enterprise-wide calendar allows central organization of personal and administrative appointments for all school employees & students
  • Ties into course calendar for students and instructors automatically
  • By default, all users can see busy/available status of any other calendar (eg. Joe Student can see that the Dean has something scheduled for 2-3 on Friday, but can't see what it is).
    • Need to be able to override this ability (Provost?)
    • Fine control over who can see calendar events details based on username and/or roles.
    • Need to define default abilities (eg. all MSOs should be able to see calendar for all employees of that department)
  • Allows user to set the level of access for others to add appointments to calendar.
  • Users 'subscribe' to other calendars and merged calendar is displayed (think Photoshop Layers - with each layer representing a subscribed cal).
    • Minimal view permission required to 'subscribe' to a user/group/class/project calendar.
  • Want rich UI (Outlook level)
  • Support download for import to desktop calendar
    • Outlook (comma delim)
    • Palm Desktop PC (dba)
    • Palm Desktop Mac (tab delimited)
    • iCal (vcs)
    • Sunbird (vcs)
  • How do we deal with rapidly changing calendars? If everyone is using their personal calendar as their main calendar, how do we get just the changed info to the PDA? Build a custom conduit to Sakai?

Academic

Course Management

  • Calendar
  • Gradebook
    • Linked to Banner
    • Students can view their scores for existing assignments for specific course
  • Resources
  • Student Roster
    • List of students for specific course
    • Allows users to determine student numbers for electives and to access individual student emails.
    • Should differentiate between enrolled and auditing students
  • Course Approval
    • Allow users to access the campus course approval process from within the portal.
    • At present the course outline in used to generate the outline on the course web pages. It is important that a mechanism be put in place to keep the course information in the course approval process current without requiring curriculum committee meetings.
    • Need to keep the feature that allows the automatically generated course outline to be overridden.
  • Course Sections (Core Gap 265)
    • Need automated way to set up multiple sections - The method described by the inital gap analysis describe a manual method.
    • Described method currently takes minutes to create additional sections as duplicates are created. - need to automate/speed up this process

Content/Resource Manager

  • Content Management API requirements are being reviewed now (1/05) by SEPP-Content group
  • Link to existing VMTH Image database

Evaluations

  • Integrate the current evaulation system into Sakai
  • Integrate VOLES (senior student, faculty, resident evaluations sytem) into Sakai. Currently perl based.
  • Tie to Merit & Promotions?

Course Catalog

  • Electronic version of curriculum handbook
  • Allow users to view all SVM courses and from here access non-Sakai pages (CALF)
  • Searchable (thesaurian vocabulary)
  • Allows users to view drafts of new courses or pending changes in courses. (3)

Merit & Promotions

  • At least 4 components are presently either under discussion or under construction.
    • My InfoVault - Allows users to generate an up-to-date dossier that can be outputted using for merit/promotion, grants etc using a template format
      • Presently being used in the Medical School, to be used by 2 department in the Vet School next year and under consideration for implementation by the campus
    • Web-based application to allow electronic evaluation by the department, FPC, CAP.
    • There are several departmental applications (entomology) on campus at present that are under consideration for implementation by the campus; tracking process that allows packets to be tracked through the system. Application in place by currently only available by the Academic Personnel Office;
    • A Vet School database that tracks all merit/promotion actions.
  • These four applications need to be integrated with each other and with current campus databases to pull required information from 1 source and need to be available within the portal.
  • Teaching Effort - allows departments to check and correct teaching effort based on last years topical outline and this years schedule and allows academic programs to generate the teaching effort report.

Miscellaneous

  • Externship database
    • Set up by a student but is under academic programs. It does not currently have maintenance. It meets some needs but is deficient in others and will need work.
    • Look at job opportunities application on campus to see whether we could use this.
  • Financial Aid - allow users to access the campus system - simple link
  • Scholarship - allows students to apply for scholarships
    • Prepopulate with basic profile information – allow the student to fill in the rest.
  • Access and usage logs
    • Detailed logs for all aspects of the system.
    • How many times has a specific resource been accessed? When was the last time? Has Joe Student viewed it? When?

Helpdesk

  • Helpdesk allows users to email to a central area where messages will be triaged to specific areas for follow-up.
  • Should be some automated responses for simple problems.

Directory

  • Direct tie-in to main campus LDAP

Administration

  • Links
  • Admissions
  • DaFIS features
    • Account balances
    • Asset management/Inventory - Dan and Ray are working on a semi-automated system
    • Purchasing
  • Facility Management (same as assest management?)
    • Allows access to current system which allows restricted access to all rooms and what’s in each room as well as AV equipment.
  • Grant Management
    • School's system is not robust enough so plans are needed to improve system or wait as campus is presently looking into a system.
  • Payroll Decision Support - allow access to UCOP surepay system
  • Personnel Decision Support - allow access to campus job opportunities information
  • Policy and Procedures allow access to on-line material
  • Staff Merit/Promotion - there are electronic forms but paper is generated and no support on campus for changing this in the near future.

General

  • Links tool
    • User defined bookmarks which can be organized heirarchically.
  • Integrated email client
    • Portlet/iframe for Geckomail
  • Library portlet
    • Allows users to access the library and all its services including the Californian digital library seamlessly from within the portal.
  • Messaging
    • Security alert allows the system to generate and distribute security alerts.
    • Distribute messages appropriately based on roles – to appear first page of portal

Definitions

  • Course / Section definitions can be found in the SakaiPedia
  • Section subsite - a recitation section of the main class. Everyone in the main class is a member of at most one subsite. Subsites are fully functional class websites.
  • Site - The over-all Course Management System.
  • Admin - Usually a course instructor, this user can use course tools to author course materials and administrate the parameters of their particular course.
  • Super-user - a higher class of administrator with the capability to do anything that the regular Admin does in any course. The super-user also has the ability to perform system admin functions.