myCI Module Definitions

Table of Contents:

Overview

These definitions describe module content management responsibilities and appropriate module content for sections within myCI.

Login Module

  1. What does the module do? Enables single-sign on authentication to Shibboleth/SAML and CAS-federated systems to access key services
  2. Who is owner/maintainer? portal program manager
  3. Who is technical contact? portal program manager
  4. Who determines what content goes in here? portal program manager
  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 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

[back to top]

  1. What does the module do? Display links to key ITS tools and services that can be accessed through myCI. This includes "Pinned Services", which enables myCI users to select their favorite services and curate their own list of favorites.
  2. Who is owner/maintainer? portal program manager
  3. Who is technical contact? portal program manager
  4. Who determines what content goes in here? portal program manager
  5. Criteria for what content goes in here
    1. Links to technology services and tools which are used on frequent 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 fills out MyCI Service Request Form which is routed automatically to the ITS Solution Center and the ITS Web Services team.
    2. Portal project manager evaluates and approves request, and communicates to requestor
    3. Module owner coordinates changes with IT technical staff
    4. IT technical staff publish changes to module

[back to top]

Important Student Information Module

  1. What does the module do? Display content created by Enrollment Management to notify students within myCI. This module displays within the "Message Center" in myCI, accessed through the user's Account menu.
  2. Who is owner/maintainer? Enrollment Management
  3. Who is technical contact? Portal program manager
  4. Who determines what content goes in here? Asst VP for Enrollment Management (Ginger Reyes)
  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 & Public Relations (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.

[back to top]

Important Faculty Information Module

  1. What does the module do? Display content created by Academic Affairs Office to notify faculty within myCI. This module displays within the "Message Center" in myCI, accessed through the user's Account menu.
  2. Who is owner/maintainer? Associate Dean of the Faculty.
  3. Who is technical contact? Portal program manager.
  4. Who determines what content goes in here? Provost and VPAA
  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. Jerilee Petralba 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

[back to top]

Important Staff Information Module

  1. What does the module do? Display content created by Human Resources Department to notify all staff within myCI. This module displays within the "Message Center" in myCI, accessed through the user's Account menu.
  2. Who is owner/maintainer? Human Resources Department
  3. Who is technical contact? portal program manager
  4. Who determines what content goes in here?
    • Primary: Martha Ferguson
    • Back-up: Sherie Frame
    • Ultimate approval will come from Human Resources Director (Laurie Nichols)
  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 submits the following information: their name, approvers name, announcement title & text, and start/end date/time for the announcement.
    2. Requestor obtains approval from designated Approver for division
      • Divisions will designate message Approvers
      • Requestor may or may not be an Approver
    3. HR evaluates the request and contacts the requestor if information is not clear.
    4. HR Director (Laurie Nichols) approves request.
    5. HR posts approved message within EchoCI, and sets the day/time parameters.
    6. Approved message is published by EchoCI to live server once start date/time is reached.
    7. Message is retrieved by myCI module application via HTTP, parsed, cached, and displayed within the myCI module
    8. Message is removed by myCI module and/or EchoCI once message expiration date has passed

[back to top]

ITS System Updates Module

  1. What does the module do? Display IT notifications created by IT staff within myCI. This module lives on the login page of myCI.
  2. Who is owner/maintainer? ITS Manager of User Services
  3. Who is technical contact? Portal program manager
  4. Who determines what content goes in here? Manager of User Services & Director of Application Services
  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 Application Services 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.

[back to top]

FAQ

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

Please fill out MyCI Service Request Form which is routed automatically to the ITS Solution Center and the ITS Web Services team. A member of the ITS team will contact you to complete the configuration.

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

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

Who is the Portal Program Manager?

Peter Mosinskis, Director of IT Strategy

About this Document

Prepared by: Peter Mosinskis
Updated 7/2/2020
Created 6/23/2009

Back to myCI Information page

[back to top]

Back to Top ↑
©