assessments & accountability v 1.0 assessments & accountability suspense resolution and...

Assessments & Accountability v 1.0

ASSESSMENTS & ACCOUNTABILITY

Suspense Resolution and

Reports


– Mute phones while listening (*6 to mute and un-mute)– Do not place your phone on HOLD– Silence cell phones– Hold questions until Q&A periods– Submit all questions via the Chat function

GROUND RULES


Assessment and Accountability (A/A)


A/A Expectations

Assessment and Accountability functionality in CALPADS is being implemented to support:

− Building a complete individual student assessment history for STAR, CAHSEE, and CELDT

− Improving the accuracy and consistency of data used to evaluate performance of individual students and educational entities


A/A Expectations

Achieving these objectives will require several iterations of CALPADS functionality

− Current phase of functionality is focused on identifying issues for both LEAs and CDE related to the loading of data

− Future functionality will address these issues as well as enhance the accessibility and usability of the data for LEAs and CDE


A/A Expectations

The initial CALPADS A/A functionality requires no changes in the way LEAs currently work with assessment vendors or with CDE

− Student Demographic changes will continue to be made through the testing vendor

− Testing Vendors will provide test results & reports as usual

− Pre-ID, where applicable, will continue as usual− Testing processes will continue as directed by

assessment program offices− AYP/API results will continue to use the student data you

supply to test vendors


A/A Expectations

LEAs will:−Match student records for your LEA to the correct

SSID when CALPADS cannot make the match automatically

−Verify the reports−Provide feedback to improve functionality


A/A Expectations

CDE will:

− Match student records to the correct SSID in CALPADS, when a LEA flags a record as “Not Mine”

− Negotiate contracts with assessment vendors that ensure the data needed for a student’s complete assessment history in CALPADS is available and timely

− Coordinate with each assessment program area to enable CALPADS to…− Provide a consistent approach to managing and

reporting assessment data − Report assessment results that reflect the testing

procedures communicated to LEAs


A/A Expectations

CDE will: − Evaluate the outcome to determine the impact on LEAs

and Accountability reports of using CALPADS data instead of vendor test data

− Work with LEAs to provide functionality focused on data accessibility and usability

− Communicate When and How: Results data left in suspense will impact Accountability

reporting Current vendor relationships will be impacted


A/A Expectations

LogisticsA schedule for data loads is included in the report sections for each Program

Assessment and Accountability Coordinators receive an email when vendor data is loaded

Report content is frozen when CDE performs the last snapshot for a Program Administration after all data received from the assessment vendor has been loaded


Suspense Management


Suspense Management

Suspense - (i.e. unsuccessful matches)Matched – (i.e. successful matches)

CALPADS Assessment Results:


Suspense Management

Reason for Suspense Record:

Miss-match in student demographic data (gender, date of birth year) between the assessment results file and CALPADS

Missing CALPADS enrollment at time of testing Missing SSID Administration Date

As soon as one of these conditions is not met, CALPADS places the record in suspense.


Suspense Management

Importance of Suspense Resolution:

A record in suspense will not be matched to a CALPADS SSID, which leaves the CALPADS assessment longitudinal record incomplete for this SSID

As students enroll at other districts their assessment data will be missing if not matched

Records in suspense do not appear in reports; therefore, your CALPADS assessment and AYP/API reports will not be complete


Suspense Management

Suspense data can be resolved both Online & in Batch

Both methods are accessed from the Assessment menu

CALPADS Functionality


MANAGING SUSPENSE DATA - ONLINE


Manage Suspense Data - Online

LEA SUSPENSE Workflow

• Review Suspense Records• Determine best resolution• Apply resolution• Wait for refresh and verify suspense resolved



Suspense Resolution Workflow



LEA SUSPENSE REASONS

• Date of Birth Mismatch: If Student Date of Birth Year for SSID in results record <> Student Date of Birth Year in ODS SINF data that was valid at the time of testing

• Gender Mismatch: If Student Gender Code for SSID in results record <> Student Gender Code in ODSR SINF data that was valid at the time of testing

• SSID Mismatch: If SSID in results record does not exist in ODSR

• Admin Date Empty: If the Administration Date in the results record is blank

• LEA Mismatch: If enrollment in LEA at the time of testing could not be validated



LEA SUSPENSE RESOLUTIONS

− the LEA correcting CALPADS data− the vendor correcting results data− the LEA and/or CDE manually assigning the suspense

record to the correct SSID



Filter : Program, Administration, Academic Year, and Matched Result (LEA Suspense) Note: Filter Options are subject to user’s access rights

Resolution STEP 1: Review LEA Suspense

LEA MatchedLEA SuspenseCDE Suspense

ADMIN Date &Suspense Reason



If the resolution for the Suspense Reason requires …– Data addition/changes in CALPADS, make the additions/changes and either 1) match

immediately to the corrected record using STEP 3, since the changes to ODS are available real-time, or 2) wait for the nightly suspense process to recognize that the CALPADS demo has changed and now matches the results record demo, eliminating the suspense automatically

– Contacting the vendor to make changes, the suspense process that runs during a load will eliminate the suspense when CDE receives and loads the corrected data from the vendor.

– Manual Matching the record with incorrect demographic data to a CALPADS record with the correct demographic data.

Resolution STEP 2a: Determine Resolution



1. If the student record in suspense does not belong to your LEA, select “Not Mine”

2. The record is placed in CDE’s queue for resolution. CDE can match the record to a student in another LEA.

Resolution STEP 2b: Determine Resolution

1

2

1

2


Mismatch Condition

Source Action Comment

SSID Mismatch Results record SSID does not exist in ODSR

Update CALPADS first & match after

Nightly Suspense Process will provide correct CALPADS data as report data the next day after CALPADS corrected

Results record SSID incorrect Correct vendor results data

Subsequent load of vendor data will cause a re-evaluation of the suspense record, clearing the suspense automatically

Demo Mismatch(Birth Date/Gender)

Results record demo correct Correct CALPADS


Results record demo incorrect Correct Vendor Results

Subsequent load of vendor data will cause a re-evaluation of the suspense record, clearing the suspense automatically

LEA Mismatch(Enrollment Not Validated)

CALPADS enrollment incorrect Correct CALPADS


SSID in result record incorrect Use SELECT MATCH to match results to correct SSID

Must also update Vendor data

CALPADS enrollment correct but no match made

Submit Service Ticket

SSID Administration Data Missing

Assessment Date in result record blank

Contact Vendor




When match is successful, return to Student List to resolve another record

Resolution STEP 3: Return to Student List

The newly matched record is available for reporting immediately



When you make changes to data in the ODS, they are replicated to the ODSR in real time. However, the change will not resolve a suspense until one of the following:

– You match the suspense data to the corrected CALPADS record– Suspense processing clears the suspense (in nightly process, load,

or CDE snapshot)

Resolution STEP 4: Wait for Refresh



Resolution STEP 5: Verify Resolved



Select Match initiates the user-defined search for a CALPADS SSID to which the result record belongs

Resolution – SELECT MATCH



Resolution – SELECT MATCH, step 1

Select Match

John Doe



Enter SSID and/or demographics, using * wildcard if needed


Enter Search Criteria



Review matching results displayed by SSID and/or Demographics, depending on the criteria entered


Suggested Correction Record

Note the incorrect Birth Year



Make selection and answer “OK” to initiate the match


Select the record to which suspense record will be matched



Both the suspense record and the selected match record are displayed Select Match Record to resolve


Select “Match Records”



The Matched Student List displays the Assessment Results record and the CALPADS record to which it has been matched

Matched Records




The source of the match is identified in the field “Match Source”. The source could be Batch, LEA, or State.

MATCHED STEP 1: Confirm Matches




Matched records can be ….

MATCHED STEP 2: Resolve Incorrect Match

− unmatched if incorrectly matched (UNMATCH) and re-matching will occur later− unmatched if incorrectly matched and re-matching will occur now (SELECT

NEW MATCH)− unmatched and sent to CDE for matching to another LEA (NOT MINE)


Understanding Suspense Data

Name Trigger Resolution

Date Of Birth Mismatch

If Student Date of Birth Year for SSID in results record <> Student Date of Birth Year in ODS SINF data that was valid at the time of testing

• If SSID in results record is incorrect, use CALPADS “Select Match” to match the results record to a CALPADS student record with the correct SSID

• If SSID is correct but Date of Birth Year in results record is incorrect, use “Select Match” to match the results record to a CALPADS student record with the same SSID which has the correct DOB Year

• If no record is found, use SSID Enrollment Validation rules to identify the Assessment Date for the SSID and locate the SINF data for that date. If missing, add a SINF record or correct existing SINF data. Repeat “Select Match”.

• If the SSID Assessment Date identified does not accurately represent the time of testing for the student, contact the vendor to correct the SSID Administration Date (after contacting Service Desk).

• If SSID and Date of Birth Year in results record are correct, correct CALPADS data before making a match. Use SSID Enrollment Validation rules to identify the Assessment Date for the SSID and locate the SINF data for that date. Add a SINF record if missing or correct existing SINF data. Then use “Select Match” to match the results record to the CALPADS student record with the same SSID which now has the correct DOB Year

LEA SUSPENSE REASONS & RESOLUTIONS




Gender Mismatch

If Student Gender Code for SSID in results record <> Student Gender Code in ODSR SINF data that was valid at the time of testing

Same as Date of Birth Mismatch, using Gender

SSID Mismatch

If SSID in results record does not exist in ODSR

• Enroll student in CALPADS• Use “Select Match” to match the results record to new CALPADS

student record for the SSID

Admin Date Empty

If the Administration Date in the results record is blank

• Contact vendor to correct the SSID Administration Date in the results record (after contacting Service Desk)

LEA SUSPENSE REASONS & RESOLUTIONS




LEA Mismatch

If enrollment in LEA at the time of testing could not be validated

• If SSID in results record is incorrect, use CALPADS “Select Match” to match the results record to a CALPADS student record with the correct SSID

• If SSID is correct in results record, use SSID Enrollment Validation rules to identify the SSID Assessment Date that CALPADS is using to identify the enrollment record at the time of testing

• If the student was enrolled in the LEA on the Assessment Date, either enroll the student in CALPADS or correct existing CALPADS enrollment. Then use “Select Match” to match the results record to the CALPADS student record with the same SSID which now has an enrollment that includes the Assessment Date.

• If the student was enrolled in the LEA at the time of testing, but not on the Assessment Date, contact vendor to correct the SSID Administration Date in the results record for the SSID (after contacting Service Desk).

LEA SUSPENSE REASONS & RESOLUTIONS (Cont.)


Assessment Reports


ASSESSMENT REPORTS

Operational STATUS REPORTS

CDE Only 50.1 Assessment

Upload – Detail 52.1 Assessment

Snapshots - Detail


ASSESSMENT REPORTS

51.1 Assessment Suspense – Summary Summary of LEA and School Assessment Suspense by Administration

STATUS REPORTS - SUSPENSE


ASSESSMENT REPORTS

51.2 Assessment Suspense – Student DetailDetail of LEA and School Assessment Suspense for one or more

Programs and/or Administrations

STATUS REPORTS - SUSPENSE (Cont)

Grey, Jordan

Abdul, Jordan

Ferrell, J

3224589451,

2274589451,

5288589451,


ASSESSMENT REPORTS

The following types of Assessment reports are available– Summary LEA results for STAR, CAHSEE and CELDT, including

county & state comparisons– Individual student result detail supporting the summary results for

STAR, CAHSEE, and CELDT– Currently enrolled students missing CAHSEE – Currently enrolled students needing CELDT

The following types of AYP/API reports will be available– Students included in the AYP/API results

The following types of individual student reports are available

– Individual student assessment history

REPORTS AVAILABLE


ASSESSMENT REPORTS

Assessment reports use vendor assessment results data

The Student Profile data display as follows:– For reports that present results data by ADMIN, data valid at the

time of testing is used for filters and report content– For reports that present results data for Current Students, current

data is used for filters and data valid at the time of testing is used for report content


ASSESSMENT REPORTS

Report content for a Program Administration can continue to change as long as suspense processing is occurring for that Program Administration

– Students can be added when a new match is made through the Suspense Resolution Process, either online or batch, which updates the AADS immediately

– Student demographic data on the report can change when the Suspense Process, either nightly or in a data load, refreshes student data in AADS for students whose data have changed in the ODS (Note: Non-Participant only in Load)

– Students can be removed when the Suspense Process, either nightly or in a data load, is not able to re-validate the student’s enrollment due to changes made in ODS enrollment data that were valid at the time of testing


ASSESSMENT REPORTS

ASSESSMENT MENU

Two entry points from Assessment

Menu


ASSESSMENT REPORTS

xxxxxxxxx

REPORTS


ASSESSMENT REPORTS

xxxxxxxxx

REPORTS (Cont)

CDE Only50.1 Assessment

Upload – Detail52.1 Assessment

Snapshots - Detail

Coming


UNDERSTANDING STAR REPORTS


Understanding STAR Reports

The STAR Program has one Administration, called ANNUAL

The ANNUAL Administration includes multiple Assessments:

California Standards Tests (CST) California Modified Assessment (CMA) California Alternate Performance Assessment (CAPA) Standards-based Tests in Spanish (STS)

INTRODUCTION



INTRODUCTION (Cont)

STAR vendor results for the ANNUAL Administration are loaded multiple times

– The loads are named P1, P2, P3, and Post P-3

– Loads P2 and P3 overwrite the previous load

– The Post-P3 load does not overwrite P3



GENERAL CALENDAR - STARSchedule Event Description

August

(Week 1)

P1 LOAD Includes approximately 99.9% of LEA participants Received about 8/1. Required to meet statutory reporting deadline of 8/15.

August

(Week 2/3)

AYP/ API (P1) LOAD

Concurrent with posting on DataQuest STAR aggregate downloadable files from

assessment vendor AYP/API reports and data files pre-release for LEAs AYP/API reports and data files release to the public

(August 15)

September (Week 1)

P2 LOAD Includes 100% of results, including LEA’s remaining results not included in the P1 (e.g. Year-round schools). Received about 9/1.

September

(Week 2-4)

LEA Data Review

LEAs examine STAR and CAHSEE data to identify needed student data changes. LEAs make changes in CALPADS and through vendor.

Assumption: Results data is loaded to CALPADS within x days of its receipt by CDE



GENERAL CALENDAR – STAR (Cont)

Schedule Event Description

October AYP/ API (P2) LOAD

Concurrent with posting on DataQuest AYP/API reports and data files that incorporate P2

STAR late testing LEAs, CAHSEE data corrections, appeal and exception decisions, and CAPA reallocations related to 1% cap for LEAs (October 1)

October - December

LEA Data Review

LEAs examine AYP/API (P2) results to identify needed student data changes. LEAs make changes in CALPADS and through vendor.

December/ January

P3 LOAD Includes 100% of results, including LEA student data changes made since P2.

December/ January

AYP/ API (P3) LOAD

Concurrent with posting on DataQuest AYP/API reports and data files that incorporate P3

student data changes




GENERAL CALENDAR - STAR (Cont)


January - February

LEA Data Review

LEAs examine AYP/API (P3) results to identify needed student data changes. LEAs initiate appeal process through CDE for approval to submit changes to vendor.

January - February

Post-P3 LOAD(s)

Includes only LEA specific results submitted to the vendor that have been approved by CDE through the appeals process. The number of loads and the timing will vary.

February AYP/ API (Post-P3) LOAD

Concurrent with posting on DataQuest Final AYP and Growth API that incorporate all Post-

P3 changes (February) and Final Base API (March)




REPORT 20.1 LEA SummarySummary of the most current STAR results for a school by grade

Test Type should beAssessment



REPORT 20.1 LEA Summary (Cont)

Test Type should be Assessment



REPORT 20.2 Student ListDetail of the most current STAR results by student for Test Participants for all or selected assessments. If multiple scores exist for a student at the same school for the same test, the best result is reported.




REPORT 20.3 LEA and State SummarySummary of the most current results for an LEA and the state



UNDERSTANDING CAHSEE REPORTS


Understanding CAHSEE Reports

The CAHSEE Testing Program has multiple monthly Administrations (ADMINs):

– JUL, OCT, NOV, DEC, FEB, MAR, & MAY

A CAHSEE vendor results file is loaded and stored for each monthly Administration

Cumulative results files are also received quarterly and at the end of the year

INTRODUCTION



All result files may include records for a previous ADMIN during the year (e.g. The monthly file for a DEC ADMIN may include corrected data for a student from the previous OCT ADMIN)

– If a record in a load for an SSID was in a previous load for the same Test &

same ADMIN, the most current record is reported for the ADMIN different ADMIN, each record is reported for its ADMIN

INTRODUCTION (Cont)



GENERAL CALENDAR - CAHSEESchedule Event Description

September

(Middle)

MONTHLY-JUL Includes: JUL. Received 6-7 weeks after ADMIN

September (End)

QUARTERLY-1 Includes: JUL

December (Middle)

MONTHLY-OCT Includes: OCT. Received 6-7 weeks after ADMIN

January

(Middle)

MONTHLY-NOV Includes: NOV. Received 6-7 weeks after ADMIN

February (Middle)

MONTHLY-DEC Includes: DEC. Received 6-7 weeks after ADMIN

February (End)

QUARTERLY- 2 Includes: OCT, NOV, DEC + Q1 (JUL)

April (Middle)

MONTLY-FEB Includes: FEB. Received 6-7 weeks after ADMIN

Assumption: Results data is loaded to CALPADS within 2 days of its receipt by CDE



GENERAL CALENDAR – CAHSEE (Cont)


June

(First)

MONTHLY-MAR Includes: MAR (largest ADMIN). Received 7-8 weeks after ADMIN

June

(End)

QUARTERLY-3 Includes: FEB, MAR + Q2 (JUL, OCT, NOV, DEC)

Pre-EOY - Used for LEA Preview Reports

July

(Middle)

MONTHLY-MAY Includes MAY (Make-up ADMIN). Received 6-7 weeks after ADMIN

July - Sep LEA Data Review

After last ADMIN, LEAs can do corrections for all ADMINS during the year. Corrections must be complete by Oct 8.

July/August (Begin)

QUARTERLY-4 Includes: MAY + Q3 (JUL, OCT, NOV, DEC, FEB, MAR)

Preliminary Final for DataQuest & AYP/API for AYP Participation Rate




GENERAL CALENDAR – CAHSEE (Cont)


August

(Week 2/3)

AYP/ API (P1) LOAD

Concurrently with posting on Data Quest … STAR aggregate downloadable files from

assessment vendor AYP/API reports and data files pre-release for

LEAs AYP/API reports and data files release to the

public (August 15)

October (Middle)

EOY Includes: JUL, OCT, NOV, DEC, FEB, MAR, MAY

Final - Cumulative for DataQuest & AYP/API

October AYP/ API (P2) LOAD

Concurrently with posting on DataQuest … AYP/API reports and data files that incorporate

P2 STAR late testing LEAs, CAHSEE data corrections, appeal and exception decisions, and CAPA reallocations related to 1% cap for LEAs (October 1)




Three types of CAHSEE reporting are available in CALPADS Census – Provides an unduplicated count of enrolled 10th grade

students who took either part or all parts of the test at the enrolled school during the administration(s) being reported.

Administration - Provides overall results of CAHSEE administrations for all currently students enrolled in a school who took either part or all parts of the test at the enrolled school by grade level during the administration(s) being reported.

Enrollment - Provides overall results of CAHSEE administrations for all currently students enrolled in a school, both students who did not take the test and students who took the test, regardless of where the test was administered.

REPORTING TYPES



REPORT 21.1 Census – LEA Summary



REPORT 21.1 Census – LEA SummarySummary of the CENSUS Reporting Type results for Student Tested on each part of the assessment. The number and percentage of students who met the high school graduation requirement are also included.



REPORT 21.2 Census – Student ListStudent detail of the CENSUS Reporting Type results for Students Tested in Grade 10.



REPORT 21.2 Census – Student ListStudent detail of the CENSUS Reporting Type results for Students Tested in Grade 10



REPORT 21.3 Administration – LEA SummarySummary of the ADMINISTRATION results for Students Tested (grades 10-12 and AD) and the number and percentage of students who met the high school graduation requirement.



REPORT 21.4 Administration – Student ListDetail of ADMINISTRATION results for enrolled Students in grades 10-12 and AD that were tested at the reporting school. Although Requirement Met recognizes scores received from other schools, they are not displayed.

Report Operation: The individual student data can be displayed using all of an LEA’s schools or using only selected schools. Report can be filtered to display the results for selected Administrations, and for subgroups of students. The following legend appears at the bottom of the report to explain the Result column.



REPORT 21.4 Administration – Student ListDetail of ADMINISTRATION results for enrolled Students in grades 10-12 and AD that were tested at the reporting school. Although Requirement Met recognizes scores received from other schools, they are not displayed.



REPORT 21.5 Enrollment – LEA Summary (Cont)

Report Operation: This report displays results for all/selected schools within an LEA, which can be filtered to display the results for subgroups of students. It also includes a County summary for comparison.



REPORT 21.5 Enrollment – LEA SummarySummary of testing results for current enrollment in grades 10-12 and AD

Not Tested should be No Test



REPORT 21.6 Enrollment – Student ListDetailed CAHSEE results for individual students for current enrollment in grades 10-12 and AD. If multiple scores exist for an enrolled student, all scores received are displayed regardless of the school in which the score was received.



REPORT 21.7 Administration-LEA DisaggregatedSummary of CAHSEE results for Students Tested in grades 10-12 and AD with the number and percentage of students who met the high school graduation requirement.


UNDERSTANDING CELDT REPORTS


Understanding CELDT Reports

The CELDT Testing Program has an Administration (ADMIN) every month:– JUL, AUG, SEP, OCT, NOV, DEC, JAN, FEB, MAR, APR,

MAY, & JUN

The Annual assessments occur from July 1 – October 31. CDE receives the data in January/early February. If an initial assessment occurred during this timeframe, it will be included in the data received.

Initial assessments occur each month as students enroll. CDE receives the data at the end of the year.

CDE is negotiating with the vendor to receive results monthly

INTRODUCTION



GENERAL CALENDAR - CELDTSchedule Event Description

January/ February

PRE-DRM LOAD

Includes (Annuals & Initials): JUL, AUG, SEP, OCT

LEAs get results to vendor by Mid-November. When CDE receives, it is checked before it goes into LEA DRM (Data Review Module)

February - March

LEA Data Review

LEAs make corrections in DRM

April (Early)

POST-DRM LOAD

Includes: JUL, AUG, SEP, OCT

Concurrent with posting on DataQuest & calculation of Title III AMAO

FINAL Includes (Initials): NOV, DEC, JAN, FEB, MAR, APR, MAY, JUN




REPORT 22.1 CELDT – LEA SUMMARY



REPORT 22.1 CELDT – LEA SUMMARYSummary of selected administration(s) by Grade



REPORT 22.2 CELDT – Student ListDetail for currently enrolled Students Tested during the selected administration(s). If multiple scores exist for an enrolled student, all scores received at the school for the reported administration(s) are displayed.



REPORT 22.3 CELDT – English Learner StatusDetail of the current year status of the CELDT for currently enrolled English Learners. If there is no current year data, it reports if it is Due or Overdue.



REPORT 22.4 CELDT – County Trend by LEASummary of results for selected administration(s) and academic years by LEA


UNDERSTANDING INDIVIDUAL STUDENT

ASSESSMENT REPORTS


Understanding Student Reports

GENERAL CALENDAR

Report is available at any time to the school in which the student is primarily enrolled

The data included is subject to the loads and suspense processing of each Program.



REPORT 40.1 Individual Student Profile

Description: Displays the entire Assessment history for individual students currently enrolled in the selected LEA. It displays scores for all administrations, regardless of the LEA administering the Assessment. If multiple scores exist for an administration, all scores are displayed. Assessment modifications and accommodations are included in the report as Testing Conditions. Enrollment Status Code of students included = 10 (Primary).Data as of: Last Load date +/- subsequent suspense processingData Included: Test Purpose (e.g. Initial, Annual), Administration, Administration Date, Test Condition that makes the result an Invalid Result (see Legend), Result (CELDT = Criterion Met, CAHSEE = Requirement Met, STAR = N/A)Totals: None

Links: None

Glossary References: SSID Administration Date, Criterion Met, Requirement Met



REPORT 40.1 Individual Student Profile (Cont)

Report Operation: This individual student report can be printed for currently enrolled students for all of an LEA’s schools or only selected schools. It can also print for an individual student. When printing for a school/LEA, the report displays results regardless of where the assessment was administered. It can be filtered to display the results for selected Academic Years, Programs, Assessments, Tests, etc. It can be requested for subgroups of students. The legend on the following page appears at the bottom of the report. A user selection allows it to print per student.



REPORT 40.1 Individual Student Profile (Cont)

Entries appear only if used in report



VIEW STUDENT RESULTS - Online

STAR=AllCAHSEE=10-12, ADCELDT=EL+ TBD

Results available online for all Programs by …

•Administration(s)•Result•SSID

Click Individual student for details


Understanding Student Reports (Cont)

VIEW STUDENT RESULTS – Online (Cont)

Complete history of STAR, CAHSEE, and CELDT


Wrap-UP

Please Complete Our Survey

93

Questions

http://www.csis.k12.ca.us/survey/calpads-training/


WRAP-UP


Wrap-Up

QUESTIONS

When should I begin resolving suspense data?If suspense conditions exist in your data, the suspense records are available to you for resolution after each suspense evaluation. Data is evaluated … when vendor results data is received and loaded for a Program Administration nightly after the first vendor data is loaded for a Program Administration when CDE initiates a manual snapshot

The schedule for receiving results data differs for each Program Administration. Therefore, the data is received and loaded at different times during the Academic Year. See General Calendar in the Reports Training for information about each Program’s data load schedule. Because reports are available for viewing immediately after the completion of the load process, this load schedule also indicates the schedule for the availability of suspense data.


Wrap-Up

QUESTIONS (Cont)

How will I know when I have suspense data to resolve?When Assessment results have been loaded (which means that the suspense and snapshot processes have also completed), notification that suspense items are available for resolution and that reports are available for viewing will be: Displayed in CALPADS Notifications on the Home page Emailed to the following roles:

– LEA STAR Coordinator for STAR data load– LEA CAHSEE Coordinator for CAHSEE data load– LEA CELDT Coordinator for CELDT data load– CDE Assessment Coordinator

NOTE: Notification occurs only after data is loaded. There is no notification after the nightly process or after a CDE initiated snapshot.


Wrap-Up

QUESTIONS (Cont)

Should I monitor the status of my records through the operational reports?

The operational reports are available for your convenience. Monitoring can be accomplished solely through the “Student List”.

How frequently should I monitor the status of my suspense records?Once you begin resolving your suspense records, you will want to monitor your list of records to verify that data changes you made have removed the record from your list of suspense records as expected.

Since records in suspense do not appear in reports, your schedule for monitoring them should be based on the schedule that accurate reports need to be available for your LEA and the CDE. See General Calendar in the Reports Training for information about each Program’s data availability for reports.


Wrap-Up

When you make changes to data in the ODS, they are replicated to the ODSR in real time. However, the change will not resolve a suspense until one of the following:

– You match the suspense data to the corrected CALPADS record– Suspense processing clears the suspense (in nightly process, load, or CDE

snapshot)

KEY POINTS

A suspense record can be resolved in CALPADS by one of the following …− the LEA correcting CALPADS data− the vendor correcting results data− the LEA and/or CDE manually assigning the suspense record to the

correct SSID


Wrap-Up

The rules for identifying an SSID Assessment Date (i.e. date CALPADS used to locate the enrollment at the time of testing) may not accurately identify a student’s enrollment at the time of testing, since an actual day of testing is not available in the results data for STAR and CELDT. Consult the Service Desk if you suspect this has occurred.

CDE will be working with assessment vendors to get the actual date of testing in the results file, which will eliminate the need to calculate this date.

KEY POINTS (Cont)


Wrap-Up

QUESTIONS

Will I need to resolve CALPADS suspense records and work with my vendor to correct vendor results data that caused the suspense?

Yes, until CDE announces that it will use CALPADS data for Data Quest reports. When CALPADS provides data to the CDE accountability process (AYP/API), it will provide both CALPADS and vendor data for evaluation. CDE will compare the data to determine whether/when CALPADS data can be used.


DOCUMENTATION Key Terminology Loading Assessment Results Data Validation & Reporting Data Managing Suspense – Batch Files Glossary of Terms and Business Rules –

Assessments (separate document)

Wrap-Up


KEY TERMINOLOGY


Key Terminology

KEY TERMS & RELATIONSHIPS

PROGRAM STAR

CAHSEECELDT

ADMINISTRATION

ASSESSMENT STAR = CST, CMA, CAPA

CAHSEE = CAHSEECELDT = CELDT

ASSESSMENT DATE (Reported)

TESTExamples:

English/Language ArtsAlgebra I EOC

CONTENT AREA

ADMINISTRATION DATE (SSID)

CALENDAR

Reporting and Data Storage utilize standard definitions


ASSESSMENT DATE (SSID)

PROGRAM STAR

CAHSEECELDT

ADMINISTRATION

ASSESSMENT STAR = CST, CMA, CAPA

CAHSEE = CAHSEECELDT = CELDT

ASSESSMENT DATE (Reported)

TESTExamples:

English/Language ArtsAlgebra I EOC

CONTENT AREA


CALENDAR


ASSESSMENT DATE (SSID)


Key Terminology

Program (Testing Program)

– STAR Testing Program– CAHSEE Testing Program– CELDT Testing Program

Administration - ADMIN (Program Administration) Indicator for a Program’s testing

DATA DEFINITIONS

cycle:– STAR = ANNUAL– CAHSEE = JUL, OCT, NOV, DEC, FEB, MAR, & MAY– CELDT = JUL, AUG, SEP, OCT, NOV, DEC, JAN, FEB, MAR, APR, MAY, & JUN


Key Terminology

DATA DEFINITIONS (Cont)

Calendar (Program Testing Calendar)

The schedule for each Program Administration used to indicate the valid testing days for a Program Administration

Assessment – STAR =

California Standards Tests (CST) California Modified Assessment (CMA) California Alternate Performance Assessment (CAPA) Standards-based Tests in Spanish (STS)

– CAHSEE = CAHSEE– CELDT = CELDT


Key Terminology

DATA DEFINITIONS (Cont)

Test

• Content Area (Test Content Area) Subject content area to which the Test belongs(See Documentation)

Name of testing instrument (See Documentation)


LOADING ASSESSMENT RESULTS


Loading Assessment Results

AADS Requires …– Vendor Results Data

– Student Profile Data Enrollment (SENR) Student Information (SINF) Student Program (SPRG)

LOAD PROCESS

CALPADSPortal

CALPADS Staging

Area

CALPADS Integration

Hub (ZIS, FTP,

ESB)

LEA Systems

Local CALPADS

ZIS

State Users

Other Systems

LEA

Assessment Vendors

CALPADS Assessment & Accountability

Data Store(AADS)

CALPADS Operational Data Store Replicated

(ODSR)

CALPADS State

Reporting Snapshots

CALPADS Operational Data Store

(ODS)A

BC

D

Reporting



STUDENT PROFILE DATA LOAD

What data does CALPADS replicate into ODSR from ODS and when?

Student Profile data is replicated from the ODS into the ODSR in real-time as transactions in the ODS occur. The data in the ODSR is a subset of ODS data from all enrollments for currently and previously enrolled students.



STUDENT PROFILE DATA LOAD (Cont)

When does ODSR data get replicated into AADS for reporting?

ODSR Student Profile data for a Program Administration gets replicated into AADS as a part of the Suspense Resolution Process by LEAs and CDE, as part of the Suspense Process evaluation of data (nightly and when a Snapshot is taken during a load or manually initiated by CDE i.e. update & freeze of reporting data for a Program Administration). The data include:

− For Test Participants without data in suspense: Data that were valid at the time of testing (i.e. SSID Assessment Data Records)

− For Non-Test Participants: Data that were valid during the time of testing (i.e. LEA Testing Window) Note: occurs only during Snapshot Process

− For currently enrolled students without data in suspense: Current data

SSID Assessment Data Records are the ODSR Student Profile Records (SENR, SINF, SPRG) valid at the time of testing that are used in the Suspense Process to validate a Testing Participant’s enrollment.

Test Participants are students with results records for a Program Administration (both valid and invalid results)



STUDENT PROFILE DATA LOAD (Cont)

What data does CALPADS snapshot in AADS?

data replicated into AADS from ODSR for the Program Administration.

This is the data used to report results for Program Administrations, as well as to report results/lack of results for currently enrolled students.

The Snapshot process updates and freezes both the vendor results data for the Program Administration and all of the Student Profile



LOADING RULES SUMMARY

Program Load Name Initial Load Rules

STAR P1 P2 P3

Overwrite previous load for academic year. Evaluate for Suspense

If previous record exists for UIN (student Unique Identification Number), reevaluate for suspense, except for

– LEA or CDE Resolved. Do not re-match demo

Post P3-LEA(s) No overwrite of P3. Load & evaluate for Suspense If previous record exists for UIN, reevaluate for suspense,

except for– LEA or CDE Resolved. Do not re-match demo.

Note: Multiple loads are possible for different sets of LEA(s).

• Load Name is used for Snapshot Name and Extract Name

When new data are loaded, suspense records that have been resolved stay resolved, unless enrollment can no longer be validated



LOADING RULES SUMMARY (Cont)

Program Load Name Initial Load Rules

CAHSEE MONTHLY-ADMIN NAME QUARTERLY 1-4 EOY

No overwrite of previous load for academic year. Load & evaluate for suspense

If SSID is in a subsequent load for the same Test &– Same ADMIN, replace previous record & reevaluate for

suspense, except for LEA or CDE Resolved. Do not re-match demo.

– Different ADMIN, save each record & evaluate new for suspense

CELDT MONTHLY-ADMIN NAME PRE-DRM POST-DRM

No overwrite of previous load for academic year. Load & evaluate for suspense

If SSID is in a subsequent load for the same Test &– Same ADMIN, replace previous record & reevaluate for

suspense, except for LEA or CDE Resolved. Do not re-match demo.

– Different ADMIN, save each record & evaluate new for suspense

Multiple ADMINS are stored for same test (CAHSEE & CELDT)

assessments & accountability v 1.0 assessments & accountability suspense resolution and...

Documents

assessments accountability

calpads data

accountability aa slide

accountability functionality

suspense management

accountability reports

assessment results data

accountability coordinators