SIRAS has the capability of processing CALPADS-formatted data files for the demographics and other data.

Currently this is enabled and has been customized to the needs of Ventura SELPA only, for both Special Ed and 504 student records.

 

The CALPADS files are evaluated in sequence.  Both SPRG and SENR are evaluated before making any changes to SIRAS data.

The rules for applying data are similar to those used for other file-based data transfer processes, with some differences due to how CALPADS data is split up across several different files.

 

SPRG:  Indicator of Special Ed or 504 status.  Deprecated (CALPADS no longer specifies Program 144 as Special Ed, so this cannot be used without a special modification to include Special Ed students in the file as code 144).  If 144 is indicated here, this will allow SIRAS to create new records based on the presence of this indicator.  Program code 101 is used for 504 Plan and SIRAS can create and update 504 Plan records based on the presence of this code.

 

SENR:   (Enrollment)

Enrollment Status (EnrlStatus) must be 10 (Primary Enrollment) or Siras will not update anything further via this process.

District Exit (ExitDate) must not be before the current date or Siras will not update anything further via this process.

DistID and SchID will potentially setup a Transfer Request (or automatically update a School of Service within an unchanged District) if they are different from the Siras Student's district or school code.

Grade will be updated

District Enrollment Date = EnrlDate will be updated

Migrant program indicator will be updated

 

Issues related to multiple school-level entities sharing the same code:

These issues are the same for other files-based data transfers.  Documentation link.

 

SINF:  (Student Information)

EffectiveEnd must not be before the current date or Siras will not update anything further via this process.

Demographics will be updated:  Race 1-3, Ethnicity, Gender, actually that is all of the demographics that we are able to use from this file.

 

SCON:  Contact Data (not yet implemented)

 

SELA:

Potential to import EL Type, Native Language and RFEP Date

However due to issues that were unclear, update via this file was disabled for Ventura SELPA.  Instead we are using their custom SSTU file.

 

SSTU (Custom additional data file used by Ventura SELPA):

EL Type

Native Language

Residential Status

RFEP Date