AzEDS for Developers
Current Use Case Scenarios and Release Notes
Below is the current version of the Use Case Scenarios and Release Notes for both the sandbox and production. Please note that Release Notes are updated for major releases.
**The Change Log, located in the tab below, will serve as a reference for any previous or historical versions.
|AzEDS Rest API Use Case||AzEDS Rest API Use Case Release Notes||API Last Updated|
|FY2019||Use Case 4.0||API 4.0 – Release Notes||1/31/18 (see change log)|
|FY2018||Use Case 3.0||API 3.0 – Release Notes||9/14/17 (see change log)|
|FY2017||Use Case 2.3.5||API 2.3 – Release Notes||11/21/16 (see change log)|
*The Use Case 4.0 will have more updates coming soon.
The Year End Code Changes in Use Case 3.0 Document is also available for reference.
|1/31/2018||Updated following from Use Case 4.0:
|12/12/17||Updated following from Use Case 3.0:
|09/14/17||Updated following from Use Case 3.0:
|09/01/17||Updated following from Use Case 3.0:
|7/1/2017||Updated following from Use Case 3.0:
|06/12/17||Updated following from Use Case 3.0:
Removed the following code values from Instructional Setting (Table 7):
Removed the following code values from Course Level Characteristics (Table 9):
|7/1/16||Corrected edfi.studentCharacteristic to include required BeginDate and DesignatedBy elements; made correction to EdOrg guidance on Notes tab (StudentEducationOrganizationAssociation.EducationOrganizationID refers to LEA ID), provided guidance on submitting US Territories|
|6/17/16||Reformatted Use Case to be more user friendly; Code values pulled out and placed on their own page.|
|2/16/16||Use Case – Removed American Sign Language from list of Home Language codes because it is not valid in SAIS.|
|9/2/15||Use Case -Removed enrollment activity code ET Use Case – Removed withdrawal activity code WT|
Links are provided for the last updated version of previous fiscal years. Previous versions will remain provided for the purpose of 915s. For requirements on data submissions accrued before 2016, refer to SAIS documentation.
|Date||AzEDS REST API – Release # Release Notes||Use Case Scenarios Release #||Use Case Release Notes Version #||FY|
|11/21/16||2.3 (see change log)||2.3.5 – Use Case||2.3.5 (see change log)||2017|
|9/1/16||2.3 (see change log)||2.3.3 – Use Case||2.3.3 (see change log)||2017|
|8/12/16||2.3 (see change log)||2.3.2 – Use Case||2.3.2 (see change log)||2017|
|7/6/16||2.3 – Sandbox||2.3 – Use Case||Use Case 2.3 Version 2||2017|
|7/1/16||2.3||2.1||2.1 (See change log)||2017|
|2/16/16||2.2 – Production||2.2 – Use Case||see change log||2017|
|12/8/15||Use Case 2.2 Version 1|
Features & Processes
|5/27/16||Web UI fix – Retired identities are removed from use when two identities are merged|
|4/8/16||Integrity: performance enhancement|
|3/9/16||AzEDS-to-SAIS bug fixes: Mother’s first name showing on TRANS11 for Summer Withdrawals, Need Code 21, Tribal Name character limit|
|2/12/16||AzEDS-to-SAIS bug fix: AzEDS Delete|
|2/9/16||AzEDS-to-SAIS: efficiency improvement|
Developing for AzEDS
The SIS certification process ensures that each student information system (SIS) used by Arizona educational institutions can pass all required information to ADE via the AzEDS REST API. Certification is conducted at the SIS vendor level for a specific version of that vendor’s SIS.
Conducted over the course of several 3-4 hour sessions, the certification process tests the vendor system’s ability to pull and push data via the AzEDS REST API. Prior to the first certification session, we will send you information about the vendor test environment (REST API urls, API key and secret, etc.) plus basic parameters we will be using during the certification process, such as district, school, class periods, and term types. This will give you time to make sure you have access to the environment and perform any necessary setup in your SIS prior to the first session.
Feel free to test your access to this environment, but please restrict your REST API calls to GETs as we want to make sure our certification scenarios are not affected by pre-existing data. After the certification process is complete, your test database will be archived in case it is ever needed for auditing purposes.
The certification process will take place as an online meeting. You will be asked to share your screen so that we can watch you enter the appropriate certification parameters into your SIS, and so we can watch how the resulting transactions are submitted to the REST API. We will email each group of scenarios during the certification session, and will run scripts to verify the information has landed correctly on our database.
Feel free to contact us by email with questions at [email protected]. We look forward to working through this process with you.
|1/27/15||AzEDS Sample Certification Scenarios – Release 2 Version 2||2.0||2.0|
|11/18/2014||AzEDS Sample Certification Scenarios – Release 2 Version 1||2.0||1.0|
|9/25/14||AzEDS Sample Certification Scenarios – Release 1 Version 1.1||1.0||1.1|
|9/25/14||AzEDS Sample Certification Scenarios – Release 1 Version 1.0||1.0||1.0|