Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Request No.2019-36
Date of Request07-01-19
RequesterCCCApply Steering/Advisory Committee
Application(s)All CCCApply Applications
Section / Page

General Use / Legal Docs / Footer 

Steering Hearing DateAugust 13, 2019
Proposed Change to Download FileN/A
Proposed Change to Residency LogicN/A


Table of Contents


Problem / Issue

In order to support colleges and students, colleges need access to student application data during and after they submit their application for admission, and Promise Grant applications.

As part of the effort to obtain student consent to share information about themselves once they commit their intent (click the link to a college Application URL) - directory information and additional data will help the college reach out and provide support to the student during the process.

This is one piece of the feature story:  Allow Access to In-Progress CCCApply Data. 

See also:

  • Revise Consent to Release Information Language in CCCApply applications
  • Implement mechanism to obtain student's consent to release in-progress information (example: add a checkbox asking the student to agree to accept the terms of use, or a specific statement). 
  • Integrate Glue to deliver in-progress data to college

    expand and enhance our current CCCApply data collection and sharing policies, it was determined that a comprehensive review (complete overhaul) is needed of all CCCApply legal information, privacy policies, consent to release information, mandated disclosures and terms of use policies - to ensure we are compliant with all state, federal and CCCCO laws and regulations. 



    Proposed Solution

    Work with the Chancellor's Office on the legal requirements while updating the Terms of Use policy - This will allow us to add other requests to agree to Terms as needed in the future.

    The CCCApply Terms of Use policy language should be updated and the revised document made available to students in Standard, Noncredit, Promise Grant, and International applications.

    /wiki/spaces/OPENAPPLY/pages/174497256

    Terms of Use _ The Common Application.pdf

    /wiki/spaces/ADM/pages/217874894

    Consent to Release Information Language in CCCApply/wiki/spaces/OPENAPPLY/pages/846463003

    2019-35: Revise Consent to Release Information Language & Implementation in CCCApplyRequirements for New Consent to Release Information Policy

    /wiki/spaces/OPENAPPLY/pages/909934899

    2016-30: Colleges Want Access to In-Progress Applications

    Legal Info/wiki/spaces/OPENAPPLY/pages/172866614

    /wiki/spaces/OPENAPPLY/pages/847348225

    Policies

    2019-34: Allow Colleges Access want access to In-Progress Application Data - Tools and Integrationsapplication data to support student success


    Requirements


    Privacy PolicyConsent to Release InfoSSNTerms of Use
    Additions to current policy



    Edits to current policy



    Personally Identifiable Info (PII)
    1. Define PII in Privacy Policy
    2. Confirm with Jeff Holden which definition we are using



    GDPR
    1. Work with Jeff Holden to draft requirements and/or set our policy relative to the GDPR




















    Supporting Documentation

    DescriptionFile TypeURLNotes


















    Dependencies, Risks and/or Reporting Requirements?


    Question

    Yes

    No

    Which data field(s)?

    What/How?

    Would this change affect an existing question or data field on the Standard Application?
    •   
    •   


    Would Account (OpenCCC) data be affected by this change?
    •   
    •   


    Does this change affect any other state or federal regulations or requirements?

    •   
    •   


    Would students users be affected by this change?
    •   
    •   


    Would colleges be affected by this change? 
    •   
    •   


    What other tech center web services will be affected by this change?
    •   
    •   

    i.e., Glue staging table?  Multiple Measur
    Other dependencies?



    Other implementation considerations?