| Issues & Concerns | Proposed Solutions |
|---|
Canvas Proxy Integration Requirement |
| A | Colleges have raised concerns about the proxy integration requirement for Canvas. |
| - The immediate priority are the colleges who are attempting to comply with the Canvas/Proxy requirement for the fall 2018 term.
- Remove the requirement for Fall 2018 and allow the Tech Center and ES to 1) develop & complete implementation with colleges, 2) improve the Proxy sign-in UI and workflow, and 3) develop a "short-form" Account creation process for existing students.
- Colleges need information and options from the Tech Center on how to roll out the proxy integration for Canvas.
- The Tech Center needs to put together a communication to all colleges with implementation suggestions for several different scenarios:
- Implementation process for colleges that haven't been storing the CCCID for students (in other words, the college is not sending over the CCCID for any students, even if the student has an OpenCCC account);
- Implementation process for colleges that haven't informed staff, faculty or students on the purpose of the proxy, what students need to do, etc.
- Implementation process for colleges that have a large number of non-credit or special populations that don't have CCCIDs.
|
| B | Many colleges have been using Canvas but haven't implemented the proxy to avoid challenges to students, faculty, staff and IT. |
|
| C | Many colleges have completed the IT proxy integration, but don't understand or haven't adequately prepared operationally for the workflow changes |
|
| D | Faculty and staff have complained that they are getting redirected to the proxy along with students; adequate information hasn't been provided to the college. |
|
Proxy Perception Issues |
| A | - Colleges do not understand the underlying purpose of the proxy, or the importance of the OpenCCC Account and the CCCID.
|
| Tech Center needs to implement an effective implementation process for the proxy to send out communication to all colleges with a consist |
| B | - Colleges that adopted OpenCCCApply years ago never stored the CCCID in their SIS, thus the processes are not in place to implement the full workflow process
|
|
|
| C | - Based on feedback from colleges, students perceive the proxy to be illegitimate ("Is this for real?"). It appears to be a phishing attempt or scam, and doesn't feel congruent to their expectation that they were on their way to Canvas from their college portal..
|
|
|
| D | - Colleges perceive the proxy as a barrier for their students
|
|
|
| E | - Faculty and staff perceive the proxy as a barrier for them - they are frustrated
|
|
|
| F | - Colleges need better training and support on the proxy web service and overall workflow.
|
|
|
UI/UX Design & Workflow Issues |
| UI Issues |
|
|
| A | - The proxy sign-in page needs a better design to legitimize the service for students and colleges.
|
|
|
| B | - The sign-in page lacks legitimate, recognizable branding to the user so they feel comfortable that the re-direct is official and approved by the college, the CCCCO, and the application they are trying to access.
|
|
|
| C | - The sign-in page messaging is confusing for the user; it's not clear what login credentials we are asking for. The student has just signed in to their college IdP and then immediately we are redirecting them to a second, different sign in page. The messaging lacks enough information to explain why the student is seeing the proxy sign-in page.
|
|
|
| D | - The sign-in page needs a Help link or better, an embedded video tutorial that can guide the student through the process (either sign-in with OpenCCC credentials, or recover account credentials and sign-in, or create an account if you don't have one.
|
|
|
| UX Workflow Issues: |
|
|
| A | - To streamline the proxy workflow, colleges want a "short-form" OpenCCC Account creation process for the students who are already students at a college.
|
|
|
| B | - Colleges are frustrated that students are re-directed to the proxy while they to complete assignments for a course or program. Colleges want an optional workflow process that doesn't interrupt their students on their way to an important are trying to access a systemwide application
|
|
|
| C | - Colleges are frustrated that we don't offer an easy way for bulk assignment of CCCID numbers to non-credit or special needs students (Adult Ed, Inmates, special K12 programs, and non-credit students).
- Colleges want to provide the Tech Center with a spreadsheet of account data and get back bulk-assigned CCCID assignment process
|
|
|
| D | - Many colleges don't know how to get the CCCIDs created during proxy re-direct back into their SIS or common directory systems. Better, comprehensive Information needs to be provided to colleges about the EPPN>CCCID API process.
|
|
|
| OpenCCC Account Issues: |
|
|
| A | - Overall, the OpenCCC Account Creation process, especially when asked during proxy re-direct, is perceived as redundant, unnecessary, long and intrusive; especially when the user has already provided most of the information to the college already when they applied, enrolled, registered, etc.
|
|
|
| B | - Students are put off by the questions, especially SSN, Birthdate, address, phone, email, etc.
|
|
|
Project Management Issues |
| A | - It is very unclear whether the SSO proxy is a product or a required technology component or simply a system technical requirement - both internally and externally from the field.
|
|
|
| B | - Currently the SSO proxy does not have a project charter, project plan, business requirements, or roadmap; thus making it extremely difficult for continuous improvement and supporting our colleges.
|
|
|
| C |
|
|
|
Development & Deployment Issues |
| A | - The SSO Proxy also lacks a clear development team and
|
|
|
| B |
|
|
|
| C |
|
|
|