Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 37 Next »


Need: Implement a path in CCCApply for "non-credit" students, exempt from residency determination

Existing law requires each student to be classified as a resident or nonresident at a California community college [for instruction provided to the student at the CCCs]. 

However, the recently passed Assembly Bill 3101 (AB3101) exempts a student seeking to enroll exclusively in career development and college preparation courses, and other courses for which no credit is given, from community college residency classification requirements.

Therefore, the CCCApply application process needs to be updated to collect information/data on all students, provide colleges with an electronic admission application for their non-credit  1) exempt non-credit students from the residency determination, and only collect data that is required by the federal gov, state law, or that is otherwise necessary at the time of application.




Change Requirements


  1. The CCCApply Standard Application should be used for all students: Credit and Non-Credit

  2. Revise the CCCApply Standard application to include two workflow paths, one that determines residency (Standard Credit) and one that is exempt from residency determination (Non-Credit)
    The two workflow paths would be:

    1. Standard Credit Path (includes residency determination) - For students seeking college credits for courses taken at a California community college. 
      For all intents and purposes, this is the current Standard application - including all existing logic, services, field and error validation, pre- and post-submission services and processes (no change to the residency algorithm submission calculation service). 
      To comply with AB3101, some questions/fields in OpenCCC and the Standard Application will be removed, revised, or hidden via skip logic, in order to ONLY collect data that is required by the federal government, state law, or that is otherwise required during the application process. These changes will be specified in a separate change request (2018-38: Questions to be revised or removed to comply with AB3101)  

    2. Non-Credit Path: (does not include residency determination) - For students seeking to enroll exclusively in career development and college preparation courses, and other courses for which NO credit is given, this "path" is a variation of the Standard Application - accessed from a separate, unique URL - that uses skip logic to hide pages and questions, and collects only the data required by the federal government, state law, or that is otherwise necessary to uniquely identify the student during the application process. 

      To comply with AB3101, this path does not include pages, questions, field logic calculations that determines residency status, including the residency submission calculation service,  and will only display a set of questions that are required by the federal government, state law, or that are otherwise necessary to uniquely identify the student, during the application process.

  3. The Standard "Credit" path will function exactly like the current, existing Standard application; no significant changes have been identified for the existing, residency path 
    1. If the applicant intends to enroll in one or more college credit course(s), they will use the existing college-branded application URL (or the generic, unauthenticated version via MyPath).  and complete all questions required to determine California residency; and questions required by the federal government, state law, and other necessary requirements; 
    2. The Standard "Credit" workflow path will not change how it calculates the residency status implemented today;
    3. The Standard "Credit" workflow path will not change any post-submissions processes, web services, calculations (residency, AB540, financial aid) etc. 
    4. NOTE: All proposed changes to the Standard "Credit" path will be detailed in separate change requests.

       
  4. The Non-Credit path SHOULD include the following questions required by state, local & federal mandates, as well as questions required to identify the student
    1. All questions in the OpenCCC Account will be included to identify the student at the college, for OpenCCC account creation (CCCID) and account recovery, for federal IRS requirement
    2. All questions on the Enrollment page (Term, Ed Goal, and Major) will be included 
    3. All questions on the Account Info/Mailing page will be included - including the "Dependency Status" (Minors) question
    4. All questions on the Education page will be included
    5. All questions on the Demographic Information page will be included
    6. All questions on the Review, Consent & Submit page will be included

  5. The Non-Credit path SHOULD NOT include the following questions required exclusively to determine residency, or that are not required at the time of application
    1. The Citizenship & Military page will be removed completely - (all questions in the Citizenship section)
    2. The Residency page will be removed completely - (all questions in the Military Status section)
    3. The following questions may be removed from the Needs & Interests page:
      1. Main Language section: Are you comfortable reading and writing English?
      2. Financial Assistance section:
        1. Are you interested in receiving information about money for college?
        2. Are you receiving TANF/CalWORKs, SSI, or General Assistance?
      3. Athletic Interest set of fields:
        1. Are you interested in participating in a sport while attending college?
          1. Yes, I am interested in participating in one or more sports, including the possibility of participating of playing on an intra-collegiate team.
          2. Yes, I am interested in intramural or club sports, but not in playing on an intercollegiate team.
          3. No, I am not interested in participating in a sport (beyond taking a P.E. classes).
  6. Residency Status Field Requirements

    To comply with the new residency exemption for Non-credit students in AB3101, we need to revise the Residency Status field to include a value for "exempt" status. We need to do the following:

    • Add a new value of "N" to the Residency Status field <res_status> for "non-credit / exempt".
    • Ensure all applicants via the "Non-Credit Application" default to the exempt status.
  7. Add a New Integrity Flag (81) for "Non-Credit / Residency Exempt"
    • Upon check if non-credit flag is set, then set the residency status to N and add an int flag of 81.
    • Hard code res_area A,B,C,D to "9". "9" means a student is not eligible in that area so using 9 would be an appropriate value in this use case.
    • Add integrity_fg_81 to the Download Client
    • Add to Apply submit-ws and integration testing with college adaptor.



  8. Implement logic to allow a non-credit status student to re-apply to the same term, same college using the "credit" version of CCCApply, if they plan to transition from NC to Credit status

NOTE: Currently - CCCApply does not allow an applicant to submit more than one application to the same Term at the same college. For this proposal to work, we'd need to allow this process (be able to submit another application).

  1. We need to implement logic in CCCApply to allow anon-credit student ONLY to re-apply (submit another application) to the same college for the same Term in order to transition from "Non-Credit" status to "Credit" status (in order to change their intention from enrolling exclusively in non-credit courses to enroll in one or more college credit courses). Note - this applies to transitioning from non-credit to credit at any college/any terms - not just the same college/same term. 
  2. Logic should be in place to prevent a duplicate status from being submitted.  Example, if first application was for Non-Credit, they should only be able to re-apply as a Credit status.
  3. We should not allow a duplicate Credit application to be submitted to the same term/same college.
  4. To re-apply as a credit status (to transition from non-credit status to credit status) the student would have to use the college's Standard application URL.

Notes on Requirements

  1. This proposal has been approved by Omid on 10.26.18 - however some of the small details still need to be identified, approved 
  2. The previous proposal, which included adding a "qualifying" question to identify non-credit students from credit students was rejected/declined. 
  3. By designing the Non-Credit workflow to be a "variation of the Standard Application" - we will implement a separate, unique URL to the same Standard application 

Additional Requirements & Considerations

Workflow Considerations


The bullets below include additional requirements and considerations that need to be included in the overall implementation.  Can you think of any other ones?

ENSURE THAT....

  • The "Non-Credit Application" is optional to colleges that want to use it
  • The "Non-Credit Application" has a unique URL 
  • Confirmation numbers for applications submitted via the Non-Credit URL need to be unique from Standard Application confirmation numbers/App Ids 
  • Each college must have a unique URL for their Non-Credit Application per their MIS code
  • We need to figure out all changes to the download file, such as:
    • Would there be any reason to change their current download file? 
    • We need to look at each field being hidden in the non-credit workflow (i.e., citizenship status, military status, all the residency page fields, etc.) and make sure they can be blank in the download file
    • Ensure the Glue team is made aware of all requirements that might affect the Glue jar file and identify all required changes (if any)
  • The Non-Credit path should still function and adhere to all existing CCCApply standard application pre- and post-submission web services, functionality, logic, and processes; such as:
    • All NC applications should still start the same way as they do today - from the My Applications page (started or resumed) or auto-directed from Account Creation (new Account applicants)
    • All applications must be able to be Saved and Resumed at any time
    • Resumed from the My Applications page 
    • Must still be auto-populated when a returning applicant starts a new application in CCCApply within 2 years of last application submitted
    • Adhere to all post-submission pages, processes, web services, and activities
    • Auto-populated from previously submitted application data

During the Application process, a student on the NC workflow path...

  • Must still see and respond to the Review App / "Consent to Release Information" / Submit page
  • Must still go through the Electronic Signature process (VERY important)
  • Must still Submit their application
  • Must still see the Confirmation screen with all existing confirmation data (CCCID, confirmation number, etc.)
  • Must still see the Student Satisfaction Survey 
  • Must still see the Special Links & Opportunities page
  • Must still be redirected into MyPath if college has adopted MyPath
  • Must still be routed through the Spam Filter web service and all other post-submission web services (CCGI, CDE, student profile, etc.)
  • Must still be downloaded using the Download Client, Super Glue Jar files and all data must appear in the Report Center
  • Must still integrate with the CCCApply Administrator for the configuration of custom Terms, Majors, Major Categories, Spam Filter, Reset Downloads
  • Must still appear in the Submitted Applications and/or Resume Your Application tables in the My Applications page 

Implementation & Communication Requirements

Impacts

  • Rules - With the Residency page, Citizenship, and Military pages hidden - colleges that have Rules built around any fields on these pages will need to modify their rules to compensate for non-credit application
  • New Data Fields - 
  • Hidden Data Fields - 
  • Residency logic
  • No labels