Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Create Best Practices Document for the Alternative and Supplemental Services Domain

Description

A service provider for TEA was trying to load program association data into StudentSpecialEducationProgramAssociation. When doing so, would receive an error message 

and the help desk member noticed that there was data in the StudentProgramAssociation with ProgramTypeDescriptor of uri://ed-fi.org/ProgramTypeDescriptor#Special Education"

 

Our working theory is that the data is set up to load the same data to both the StudentProgramAssociation and StudentSpecialEducationProgramAssociation endpoints. When I looked through the `Alternative and Supplemental Services Domain` I do not see anything that tells a user not to do that. I also searched TechDocs and didn't find anything related.

 

This ticket is document that when adding program enrollment that you cannot and should not try to add A student to A program through multiple endpoints. Or maybe that the StudentProgramAssociation should be used only if another endpoint doesn't cover the enrollment

Attachments

1

Activity

Show:

Edward ComerJuly 2, 2024 at 4:48 PM

The first draft of the

is attached and ready for review.

Mustafa YilmazJune 11, 2024 at 1:40 PM

I have changed the ticket name from "studentSpecialEducationProgramAssociations EDFI data load issue" to "Create Best Practices Document for the Alternative and Supplemental Services Domain" to better reflect the further direction of the ticket and align with the naming convention for tickets in the Ed-Fi UDM Best Practices Documentations (2024) epic.

Mustafa YilmazMay 15, 2024 at 3:49 PM
Edited

We need to create best practices for Student Program Association, Special Education Program Association and General Student Program Association.

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Sprint

Story Points

Fix versions

Parent

Priority

Created May 14, 2024 at 5:40 PM
Updated January 6, 2025 at 3:52 PM
Resolved July 8, 2024 at 1:37 PM