May 2009

1

Welcome and Introductions Training Overview

◦ Evolution from CSRS to CEDARS (Fri)◦ Submission and Editing Process (Tues)◦ Course Catalog, Student Schedules, Grade History

- including phase-in of State Course Codes (Wed)◦ Staff Information, including Certification Numbers

(Thurs)◦ Expanded Program data and New Ethnicity and

Race codes (Fri)

2May 2009

CEDARS Submission deadline CEDARS Error Processing Reports Overview

3May 2009

CEDARS submissions are required at least monthly

More frequent submissions are encouraged◦ OSPI will have your most recent data◦ OSPI will have corrected data

Requesting ‘unlocks’ from Customer Support is ‘NO LONGER REQUIRED’

OSPI will process CEDARS submissions nightly

4May 2009

Thirteen (13) files are submitted◦ The 13 files come to OSPI in a Zipped

(compressed) file using a SFTP (secure file transfer protocol) process

◦ Vendors may support the data extract and submission process

◦ The SFTP process ensures that the data is sent securely

◦ Do not send student data via email (not secure)◦ Contact OSPI Customer Support if you need help

sending your data to OSPI at CustomerSupport@k12.wa.us

5May 2009

All files submitted to OSPI must be in text tab delimited format

File naming and file layout should be exactly as specified in the Data Manual

CEDARS runs overnight Confirmation and errors available next

morning

6May 2009

7

 Screen clipping taken: 5/19/2009, 4:26 PM

   

May 2009

Naming convention for each file:◦ COUNTY-DISTRICT CODE_SCHOOLCODE_FileName_YYYYMMDD.TXT

Naming convention for the Zip File:◦ 12345_0000_CEDARS_20070303.zip

8May 2009

Resources Customer Support Student Information System Vendors

9May 2009

CEDARS Data Submission consists of 13 data files

The 13 files are run through two error reconciliation processes that produce:

Process errors Individual File errors

11May 2009

Process errors occur when: Data formats are incorrect Required data elements are missing data or

have invalid valuesThe first step in error reconciliation is to

review and correct process errors

12May 2009

There is a hierarchical (phased) relationship with the 13 data files. The files are loaded in a defined order

An error in one file may cause errors “downstream”

Error reconciliation should be done in the same hierarchical order

13May 2009

14May 2009

Corrections for CEDARS should be done at the source:◦ Student Information Data System◦ Human Resources Data System◦ Special Education Data System◦ Other data collections maintained by the district

Data from the source is sent to OSPI OSPI cannot correct source data

15May 2009

CEDARS Corrections are currently processed by resubmitting data files◦ There is no unlock process because submission

can be daily Some data elements in CEDARS can be

updated using a process similar to Manage Students in CSRS◦ This data editing process is in development and

will be available in the fall◦ Just-in-time training will occur in the late summer

16May 2009

17

CEDARS errors are found in EDS. Log in to EDS and select CEDARS from the application list Select Reports/Exception Reports/CEDARS Exception

May 2009

18May 2009

19May 2009

20May 2009

21May 2009

This is a test environment• The screen shots for this presentation are from

the test environment• As you submit CEDARS 2.1 data you will see your

reports populate with that new data. Until then, we have populated these test reports from your April CSRS submission

22May 2009

23May 2009

24

 Comprehensive Education Data And Research Systemhttps://eds.tst.ospi.k12.wa.us/Cedars/Reports/MonthlyEnrollment.aspxScreen clipping taken: 5/19/2009, 11:49 AM

  

May 2009

25May 2009

26May 2009

SQL Reporting services has a standardized tool bar that allows you to:◦ See that your report is being generated◦ Export or download into various formats◦ Tab through the pages

Additionally, we’ve added headers, footers, etc.

Please send us your comments/suggestions and we will add to the wish list for inclusion

27May 2009

Most recent Date Range (e.g., month) As of (specific) date (e.g., October 1st, last

day of February)These can include enrollment data for that

date or range with the student attributes submitted at that time

OR include enrollment data for that date or

range with the latest attributes for those students

28May 2009

If you have any trouble viewing these reports in Test, please contact Customer Support for assistance:

(360) 725-6371 or 1 (800) 725-4311

 customersupport@k12.wa.us

29May 2009

This presentation and session recording will be posted to the K12 web site at http://www.k12.wa.us/DataAdmin/default.aspx

We will also post questions and answers:◦ That are asked/answered during the session◦ That we did not get to during the session◦ That we receive after the session

30May 2009

Customer Support (360) 725-6371 or 1 (800) 725-4311 customersupport@k12.wa.us

Data Manual and Appendices and Supporting Documents http://www.k12.wa.us/CEDARS/default.aspx

Feasibility Study report to the Legislaturehttp://www.k12.wa.us/LegisGov/2009documents/

DataFeasibilityReport.pdf

31May 2009