/
TestHound Data Integration

TestHound Data Integration

TestHound

 

Welcome to TestHound Data Integration!

Follow this guide to send data from your SIS to TestHound

Introduction

TestHound is a premiere education administration software. Your district and school-level testing coordinators will use TestHound to assign, manage, and report standardize tests/scores for your students.

Data Sets:

TestHound will require at least four of the below data from your SIS. See Part 4part5on details on your state’s data requirements.

Minimum Data Sets:

The following data sets are required for all TestHound districts:

  1. Schedules Data: Contains current semester/term course schedules for your students. These are the courses that students are taking right now.

  2. Students Data: Contains basic data for your students.

  3. Teachers Data: Contains basic data for your testing administrators; staff that are in the room overseeing students taking their standardized tests.

  4. Users: Contains basic information (not passwords) for your district/school testing administrators who will be using TestHound.

Additional Data Sets:

These additional data sets may be required for your district:

  1. Demographics Data: Contains additional data for TX state reporting; required for TX districts.

  2. Accommodations Data: Contains data for student testing accommodations. In most cases, this data will be sent directly to TestHound from your Accommodations Vendor.

Adding Users:

Please email the completed User List to your DI Engineer, who will add the bulk of your users to TestHound. Additional users will be added/removed by your district’s TestHound admin.

SFTP & Send Schedules

Data sets (except the user list) will be sent to TestHound using SFTP. Please schedule all files to send nightly (including weekends) before 1am CST.

Hostname: uploads.testhound.com

Port: 22

Credentials: will be provided by your DI Engineer in a separate email. This one-click link will expire in 48hrs.

Please send the User List directly to your DI Engineer via email. For security reasons, please do not send any other data sets via email.

 

Data Transfer & Responsibilities

TestHound views your SIS as the Single Source of Truth for all data. Please review the steps below for how data is sent from your SIS to TestHound.

1 - Manage Data in SIS – Sending data to TestHound begins with adding, updating, and maintaining the accuracy of course request, student, and teacher data within your SIS.

2 - Export Data from SIS – Your district IT, with help from your TestHound Data Integrations Engineer, will configure SIS data exports that create the TestHound data files.

3 - Send Files to EAI – Your SIS/District IT will send data files to TestHound on a regular basis (via SFTP or API, depending on your SIS).

4 - Maintain Servers – TestHound will create and maintain servers for the purpose of securely retrieving data from your SIS.

5 - ETL & Data Security – EAI will retrieve the data files from SFTP, encrypt, and store data using AWS. See EAI’s Data Privacy page for more information on how EAI secures your data.

6 - EAI Product - EAI will display your district data in TestHound.

 

Timeline & Checklist

Ideally, your TestHound data Integration will take two weeks to complete. The actual timeframe will depend on your regional center and other 3rd parties who may need to send data to TestHound.

Day 1: Tech KO:

A meeting with your TestHound DI Engineer to review the data requirements and/or configure exports in your SIS. This meeting can be up to 45 minutes.

Weeks 1: Send First Files:

By the end of the first week, SFTP will be configured and the first files (data sets) sent to TestHound.

Please configure all files to be sent nightly (including weekends) before 1am CST.

Week 2: Data Validation:

Your TestHound DI Engineer will review and validate the sent data, then follow up with you for any needed adjustments to the exports.

After: Data Management:

Once the data in TestHound is validated, you will continue to maintain data within your SI; you may be contacted by your staff if data abnormalities are discovered in TestHound.

Please reach out to your DI Engineer if you need assistance troubleshooting any of these data abnormalities.

 

Data Requirements

See below for TestHound’s data requirements. Note that Florida and Texas districts will need to send additional data sets.

All States

The following data sets are required by all districts using TestHound:

Data sets sent via SFTP

 

Contents: data for current-semester courses for your full-time students. File Naming Convention: d_th_schedules_ST_ST-District-ID.csv Example Filename = d_th_schedules_tx_123456.csv Best Practices: Use the exact filenames provided by your TestHound DI Engineer. Do not send Social Security Numbers for any of the requested data. Export your state-assigned district id as the "District ID" on this file. Export your local school ids as the "CampusID" on this file. Headers are required and all elements must be in the order above. Whitelist all recommended TestHound IPs. Data Requirements: Example Output:
Contents: data for full-time students taking standardized tests at your district. File Naming Convention: d_th_students_ST_ST-District-ID.csv Example Filename = d_th_students_tx_123456.csv Best Practices: Use the exact filenames provided by your TestHound DI Engineer. Do not send Social Security Numbers for any of the requested data. Export your state-assigned district id as the "District ID" on this file. Export your local school ids as the "CampusID" on this file. Headers are required and all elements must be in the order above. Whitelist all recommended TestHound IPs. Data Requirements: Example Output:
Contents: data for teachers and staff who administer standardize tests for your district. File Naming Convention: d_th_teachers_ST_ST-District-ID.csv Example Filename = d_th_teachers_tx_123456.csv Best Practices: Use the exact filenames provided by your TestHound DI Engineer. Do not send Social Security Numbers for any of the requested data. Export your state-assigned district id as the "District ID" on this file. Export your local school ids as the "CampusID" on this file. Headers are required and all elements must be in the correct order. Whitelist all recommended TestHound IPs. Data Requirements: Example Output:

User List:

Please also complete and email the below user list to your DI Engineer.

Instructions: Download and fill out the Users Template in the Downloads section below. Then email the completed Users List to your TestHound DI Engineer. Contents: Account information for district and school testing coordinators who will be using TestHound File Naming Convention: NA Best Practices: Leave CampusIDs blank (NULL) for district staff. Email is the primary key for TestHound users; each staff person on the file must have a unique email. Only include staff person’s primary school. Contact your DTC about staff that coordinate tests for multiple schools. Roll Types: Data Requirements: Example Data:

Florida - Additional Data

Students’ accommodation data is also required for Florida districts. This data set will be sent with the other files via SFTP.

Accommodations Data Template:

Accommodations Data Requirements: