This lesson will provide additional information on importing data files for key subgroup reporting features available in DnA.
Through the process of reviewing the Data Specs, mapping your fields, managing code tables, and importing your data, you will see that some fields are required and others are not. Whether or not a field is required addresses only technical requirements to allow an import to work and allow the system to function in a limited fashion. For example, if you only import required fields, your DnA instance will technically work, but functionally, it will be lacking. You'll have a system full of students with only names and birth dates, limited teacher/user data, and very limited schedule data. None of the key reporting features in DnA will work as you expect them to.
Below are some tips for ensuring that you are providing all of the right data fields to get some of the key data and reporting components working correctly in DnA.
EL is a significant subgroup used for reporting in DnA. On many pages there are pre-installed filters to account for your EL population. In order to report accurately on EL students, you'll need to ensure the following:
- ProvideEnglish Proficiency/Language Fluency Code(Column 14) in your studemo.txt file.
- Make sure that the codes that you are sending are represented in your English Proficiency code table in your DnA installation. (Admin > Other > Code Management > English Proficiency)
- If your codes vary from the pre-installed codes, talk to the DnA data team or your implementation manager about appropriately remapping codes so that the DnA system keys are accounted for. EL data is specially tracked and tagged using a behind-the-scenes system key. This enables an installation to use whatever codes are appropriate, yet still tag a code as an EL code.
DnA looks at two key fields in order to accurately report whether or not a student is part of the Special Education subgroup. Both fields are available in the studemo.txt data file.
- Provide Primary Disability Code (Column 16) in your studemo.txt file.
- Provide Special Ed Exit Date (Column 28) in your studemo.txt file.
- Ensure that your data is importing accurately and your codes are accurate in your Primary Disability code table (Admin > Other > Code Management > Primary Disability).
- If a student has a valid Primary Disability Code and their Special Ed Exit Date is either blank or is a date in the future, the student will be counted with the Special Ed population.
There are a few fields that come into consideration when disaggregating data by Race/Ethnicity. All of the data to properly report this data is available in thestudemo.txtdata file.
- ProvideRace Code 1(Column 8) in your studemo.txt file.
- ProvideRace Code 2(Column 9) in your studemo.txt file.
- ProvideRace Code 3(Column 10) in your studemo.txt file.
- ProvideIs Hispanic(Column 11) in your studemo.txt file.
- Review your Ethnicity code table (Admin > Other > Code Management > Ethnicity) in your DnA installation to ensure that data is mapping and importing correctly.
- Also, when reviewing your code tables, take a look at the Race Slash Ethnicity mapping to ensure that individual races are appropriately mapping to the desired reporting Race/Ethnicity. This mapping is what allows multiple Asian races, for example, to report as an individual Asian subgroup.
- Students with multiple races, as provided by Race Code 1, 2, or 3 will generally report as Two or More Races."
Your SED population is automatically generated based on one of three pieces of data. If a student is participating in a Free or Reduced lunch program OR if a student's parent's highest level of education is not a high school graduate OR the student is identified as Homeless, Migrant, or a Foster child, they will be considered to be a part of the SED population. In order to ensure that this data element is reporting correctly, ideally, provide all of these data points.
- ProvideParent/Guardian Highest Education Level(Column 22) in the studemo.txt file.
- Ensure that your code tables are accurate (Admin > Other > Code Management > Parent Education).
- Provide lunch program data in the programs.txt file.
- Pay attention to enter and exit dates in your programs.txt file for student participation in the lunch programs.
- Ensure that your code tables are accurate (Admin > Other > Code Management > Student Programs).
- Provide homeless, migrant, and foster data in the programs.txt file.
- Pay attention to enter and exit dates in your programs.txt file for student participation in these programs.
- Ensure that your code tables are accurate (Admin > Other > Code Management > Student Programs).
If your lunch program codes vary from the pre-installed codes, talk to the DnA data team or your Customer Success Manager about appropriately remapping codes so that the DnA system keys are accounted for.
Like SED data, the gifted data is tracked and reported with programs.
- Provide student participation in the Gifted program in your programs.txt file.
- Like lunch program data, ensure that students have enter and exit dates for their participation in the Gifted program.
- Ensure that your code tables are accurate (Admin > Other > Code Management > Student Programs).
If your codes vary from the pre-installed codes, talk to the DnA data team or your implementation manager about appropriately remapping codes so that the DnA system keys are accounted for.
Gifted program data is specially tracked and tagged using a behind-the-scenes system key. This enables an installation to use whatever codes are appropriate, yet still tag a program as a Gifted program.
Next Steps
Review your data imports and look out for tips in tricks in Data Import Tools.