reset password

MCRW Pilot Program Server Setup

Tasks1 Tasks2

Sites

  • /
    • colleges
      • al
      • cbe
        • departments
          • acct
          • econ
          • fin
          • is
          • mgmt
          • mkt
        • committees
          • iac
      • ccoe
      • ecst
      • hhs
      • nss
      • extension
      • honors
    • committees
      • epc
    • offices
      • ugs
      • registrar
      • get

Custom types and columns

Curriculum Proposal (inherits Document Set)

  • Title
  • Name
  • Description
  • College
  • Department
  • Proposal Type
  • Reviewer Comments
  • Submitter Comments
  • Proposal Status
  • Date Submitted
  • Data Approved

Lists and Libraries

Curriculum Proposals

The main library for the proposals; uses the Curriculum Proposal type. The curriculum review workflow is associated with this library.

  • Default View
  • Custom New Item form
  • Custom proposal display page

Curriculum Proposal Archive

The same as the Curriculum Proposals library except that this one is for storing scanned old proposals. This library uses the default New Item form. In the future (after we figure out how to use two different New Item form with the same library with proper access control), we can merge this library with Curriculum Proposals.

  • Default View
  • Custom New Item form
  • Custom proposal display page

Curriculum Review Process Lookup

This list is used for looking up the user groups to be notified during each step of the curriculum review workflow.

Tasks

Default task list.

Views

Curriculum Proposals for each department/college/office

User Groups for each department/college/office

My Tasks for each user

Workflow

Curriculum Review

  • Special Topics Course proposals need to be handled differently.

Security

Site Permissions and User Groups

There are five permission levels:

  • Full Control
  • Design
  • Contribute
  • Read
  • Limited Access

Each site has three basic user groups: Owners, Members, and Visitors.

  • Owners have the Full Control permission. Usually the staff who's in charge of maintaining the site should be in the Owners group. The Owners group should also be the owner of the other site groups so they can manage the membership of those groups.
  • Members have the Contribute permission. All the faculty/staff/administrators of a department/college/office/committee should be in the Members group of their corresponding site.
  • Visitors have the Read permission. By default all Visitor groups are empty. It's up to the site Owners to decide who should be in the Visitors group.

In addition to the basic groups, there are also groups created for the parties involved in the curriculum review process, e.g. <College> Associate Dean, <College> Other Associate Deans, and so on. These groups do not have specific site permissions because the members of these groups should all have proper permissions from their basic site groups.

University Groups

  • UNIV Staff: this group is used to manage the membership of other university groups. It should be the owner of those groups. Note that each office or committee may have their own staff group.
  • UNIV UGS
  • UNIV UGS Staff
  • UNIV EPC

Each college has the following user groups:

  • <College> Staff: this group is used to manage the membership of the other college groups. It should be the owner of those groups.
  • <College> Associate Dean
  • <College> Other Associate Deans: this group is used in the feedback collection phase of the curriculum proposal review.
  • <College> IAC

Each department has the following user groups:

  • <College> <Department> Chair
  • <College> <Department> Faculty
  • <College> <Department> Staff: again, used for membership management and should be the owner of other department groups.
  • <College> <Department> IAC

Access Control

This page has been viewed 8544 times.