myCI Module Definitions

Back to myCI Information page

Overview

The purpose of these definitions is to establish consensus about module ownership and appropriate module content as well as stabilize "scope creep" for new features to be added to myCI prior to v2 launch in March 2010.

Important Student Information Module

  1. What does the module do? Display content created by Enrollment Services to notify students within myCI
  2. Who is owner/maintainer? Enrollment Services
  3. Who is technical contact? Portal project manager
  4. Who determines what content goes in here? Dean of Enrollment Services (Jane Sweetland)
  5. Criteria for what content goes in here
    1. Notifications critical to students continuing enrollment at the University
    2. Notifications critical to campus access to key services
  6. Examples: key student deadlines, parking/road closures, building closures, emergency/crime notices, notices with legal requirements for distribution
  7. What does not go in here:
    1. Academic events (guest speakers, symposiums, art gallery shows, etc) and their cancellations
    2. Administrative events or event announcement (all-hands meetings, committee meetings) and their cancellations
    3. Student Affairs events or event announcements (Discover CI, Orientation, Student Awards ceremony, ASI events, etc) or their cancellations
    4. Non-critical notifications to students (schedule of classes now available, catalog now available, schedule of classes changes)
  8. Business Process for Content Updates to this Module
    1. Divisions will designate message Approvers
    2. Requestor obtains approval from designated Approver for division
    3. Requestor may or may not be an Approver
    4. Requestor goes to Message Request Form web site
    5. Requestor fills out form fields, including their name, approvers name, announcement title & text, and start/end date/time for the announcement. Requestor must complete all required fields.
    6. Form is sent via email to Enrollment Services and Communication & Marketing (C&M) management and staff
    7. Dean of Enrollment Services evaluates the request (verifying request with the Approver, if necessary), and communicate back to the Requestor. In their absence, C&M staff fulfill this role.
    8. Enrollment Services staff posts message in approved request within EchoCI, and sets a start and expiration date/time
    9. Approved message is published by EchoCI to live server once start date/time is reached.
    10. Message is retrieved by myCI module application via HTTP, parsed, cached, and displayed within the MyCI module
    11. Message is removed by myCI module and/or EchoCI once message expiration date has passed.

Important Faculty Information Module

  1. What does the module do? Display content created by Academic Affairs Office to notify faculty within myCI
  2. Who is owner/maintainer? Associate Dean of the Faculty.
  3. Who is technical contact? Portal project manager.
  4. Who determines what content goes in here? Associate Dean of the Faculty (Dan Wakelee) and in his absence AVP Faculty Affairs (Renny Christopher)
  5. Criteria for what content goes here
    1. Notifications deemed important to all instructional faculty.
    2. Notifications critical to campus access to key services.
  6. What does not go in here:
    1. Academic events (guest speakers, symposiums, art gallery shows, etc) and their cancellations.
    2. Student Affairs events or event announcements (Discover CI, Orientation, Student Awards ceremony, ASI events, etc) or their cancellations.
  7. Business Process for Content Updates to this Module
    1. Submit a request for the Faculty Information module
    2. Academic Affairs evaluates the request
    3. Callie Juarez or Nathan Revard posts approved message within EchoCI, and sets a start and expiration date/time
    4. Approved message is published by EchoCI to live server once start date/time is reached.
    5. Message is retrieved by myCI module application via HTTP, parsed, cached, and displayed within the myCI module
    6. Message is removed by myCI module and/or EchoCI once message expiration date has passed

Important Staff Information Module

  1. What does the module do? Display content created by Human Resources Department to notify all staff within myCI
  2. Who is owner/maintainer? Human Resources Department
  3. Who is technical contact? Portal project manager
  4. Who determines what content goes in here?
    • Primary: Sherie Frame
    • Back-up: Janet Korsmo
    • Ultimate approval will come from the Interim AVP Human Resources Department (Anna Pavin)
  5. Criteria for content of bulletins
    1. What will post:
      • Notifications deemed important to all employees
      • Notifications critical to campus access to key services
      • Examples: Dates of benefits open enrollment, staff training opportunities, campus events, new employee orientation, etc.
      • Campus deadlines/news intended for all employees
    2. What will not post:
      • Student Affairs events or event announcements (Discover CI, Orientation, Student Awards ceremony, ASI events, etc) or their cancellations
      • Faculty specific announcements
      • Student announcements
      • Department specific announcements
  6. Business Process for Content Updates to this Module
    1. Requestor fills out form fields, including their name, approvers name, announcement title & text, and start/end date/time for the announcement.
      • Requestor must complete all required fields
      • Requestor uses web form: (to be developed at a later date) For now please contact Sherie Frame at sherie.frame@csuci.edu
    2. Requestor obtains approval from designated Approver for division
      • Divisions will designate message Approvers
      • Requestor may or may not be an Approver
    3. Form is sent via email to Janet Korsmo and Sherie Frame in HR.
      • janet.korsmo@csuci.edu and sherie.frame@csuci.edu
    4. HR evaluates the request and contacts the requestor if information is not clear.
    5. AVP (Anna Pavin) approves request.
    6. HR posts approved message within EchoCI, and sets the day/time parameters.
    7. Approved message is published by EchoCI to live server once start date/time is reached.
    8. Message is retrieved by myCI module application via HTTP, parsed, cached, and displayed within the myCI module
    9. Message is removed by myCI module and/or EchoCI once message expiration date has passed

My Links Module

  1. What does the module do? Display links to key T&C tools and services that are used frequently
  2. Who is owner/maintainer? Portal project manager
  3. Who is technical contact? Portal project manager
  4. Who determines what content goes in here? Portal project manager
  5. Criteria for what content goes in here
    1. Links to Information Technology tools/services which are used on a day-to-day basis for communication with the university, learning or academics
    2. Examples: Dolphin Email, CI Learn, Dolphin Files
  6. What does not go in here
    1. Links to documentation (HTML, PDF files, etc)
    2. Links to events or news
    3. Static text or announcements
  7. Business Process for Content Updates to this Module
    1. Requestor submits change request to module owner
    2. Module owner evaluates and approved request, and communicates to requestor
    3. Module owner coordinates changes with IT technical staff
    4. IT technical staff publish changes to module

Manage My Account Module

  1. What does the module do? Display static links to key IT tools and services that are used occasionally
  2. Who is owner/maintainer? Portal project manager
  3. Who is technical contact? Portal project manager
  4. Who determines what content goes in here? Portal project mgr
  5. Criteria for what content goes in here
    1. Links to Information Technology tools/services which students use on a occasionally to modify/update their personal profile, records, passwords, course registration, or other account-related information
    2. Examples: Pay Bills, Change Password, Update Personal Information, Register for Classes
  6. What does not go in here
    1. Links to documentation (HTML, PDF files, etc)
    2. Links to static content
    3. Links to events or news
    4. Static text or announcements
  7. Business Process for Content Updates to this Module
    1. Requestor submits change request to module owner
    2. Module owner evaluates and approved request, and communicates to requestor
    3. Module owner coordinates changes with IT technical staff
    4. IT technical staff publish changes to module

CI at a Glance Module

  1. What does the module do? Display content from CI home page within myCI
  2. Who is owner/maintainer? Nancy Gill and C&M staff
  3. Who is technical contact? Portal project manager
  4. Who determines what content goes in here? Nancy Gill and C&M staff
  5. Criteria for what content goes in here
    1. Based on criteria for what appears on the home page in section with the same name
    2. Examples: "Art Gallery/Ventura Announces "Summertime Blues" as Next Show", "New Dean of University Library Appointed"
  6. What does not go in here:
    1. News releases
    2. Images
    3. Full text
  7. Business Process for Updating Content in this Module
    1. Requestor contacts C&M staff with message request
    2. C&M staff evaluate the request (verifying request with the requestor, if necessary), and communicate back to the Requestor.
    3. C&M staff logs onto EchoCI and edits the items in the "CI At A Glance" area on the CI home page
    4. C&M staff approves changes in EchoCI
    5. myCI application module parses content at special URL, and displays in the module interface
    6. Message is removed by manually from EchoCI by owner/maintainer, and myCI module is updated automatically to reflect the change.

Events Module

  1. What does the module do? Display content from CI home page within myCI
  2. Who is owner/maintainer? Amber Weir (Academic Affairs)
  3. Who is technical contact? Portal project manager
  4. Who determines what content goes in here? Amber Weir
  5. Criteria for what content goes in here
    1. Links to R25 calendar events
    2. Based on criteria for what appears on the home page in section with the same name
    3. Additional events may be added per owner's discretion
    4. Examples: Island View Orientation, Commencement, New Employee Orientation, Student Art Show
  6. What does not go in here:
    1. News releases
    2. Images
    3. Full text
  7. Business Process for Updating Content in this Module
    1. Requestor ?contacts module owner with message request
    2. Module owner evaluates the request (verifying request with the requestor, if necessary), and communicates back to the Requestor.
    3. Module owner logs onto EchoCI and edits the items in the "Events" area on the CI home page
    4. Module owner approves changes in EchoCI
    5. myCI application module parses content at special URL, and displays in the module interface
    6. Message is removed by manually from EchoCI by owner/maintainer, and myCI module is updated automatically to reflect the change.

Login Module

  1. What does the module do? Enables authentication to myCI and CAS system to access key services
  2. Who is owner/maintainer? Portal project manager
  3. Who is technical contact? Portal project manager
  4. Who determines what content goes in here? Portal project mgr
  5. Criteria for what content goes in here
    1. Form and functionality to enable authentication to myCI portal.
    2. Links to help and password recovery resources
    3. Examples: Dolphin Name, Dolphin Password, Login button, "Forgot Password" link, Get Help
  6. What does not go in here:
    1. News feeds
    2. Announcements
    3. Links to other unrelated web sites
  7. Business Process for Content Updates to this Module
    1. Requestor submits change request to module owner
    2. Module owner evaluates and approved request, and communicates to requestor
    3. Module owner coordinates changes with IT technical staff
    4. IT technical staff publish changes to module

IT System Updates Module

  1. What does the module do? Display IT notifications created by IT staff within myCI
  2. Who is owner/maintainer? Manager of User Services
  3. Who is technical contact? Portal Project Manager
  4. Who determines what content goes in here? Manager of User Services & Director of AS/CMS
  5. Criteria for what content goes in here
    1. System warnings regarding slowness, non-critical system issues, or scheduled system maintenance
    2. Critical system messages regarding unscheduled outages, system errors and downtime.
    3. CMS outage and maintenance messages
    4. Examples: network outages, wireless issues, CI Learn logon problems, data center issues, phone issues, critical patches, CMS maintenance
  6. What does not go in here:
    1. Event information (workshops, meetings etc)
    2. Non-critical notifications to students or employees (new IT services/software, non-critical updates, non-IT related messages)
  7. Business Process for Updating Content in this Module
    1. Requestor contacts module owner (for general IT issues) or Director of AS or designee (for CMS messages) to make message request
    2. Designated IT staff logs onto EchoCI and creates a new message in the "System Status" area
    3. Designated IT staff sets a start and end date on message, and approves message changes in EchoCI
    4. myCI application module parses content at special URL, and displays in the module interface
    5. Message is removed from live server by EchoCI according to expiration date, and myCI module is updated automatically to reflect the change.

FAQ

I want to create a new module. How do I do this?

Please contact the Portal project manager. The manager will gather information about your request, and prioritize the request based on estimated benefits and cost of creation.

I want to upgrade/change a module, because we have changed out process. How do I do this?

Please contact the Portal project manager. The manager will gather information about your request, and prioritize the request based on estimated benefits and cost of changes.

About this Document

Prepared by: Peter Mosinskis
Revised 2/22/2010 (by Judy Swanson)
Revised 3/23/2012 (by Zachary Plat)
Created 6/23/2009

Back to myCI Information page

©