2025-02-14 DSWG Meeting #7

Participants

Number of Attendees: 31

The meeting was held Feb 14, 2025 12:00Pm -1:15pm CT via WebEx

Meeting Agenda

1. Replace StudentSectionAssociation with Student and Section references in StudentSectionAttendanceEvent, and similar for (Ref: DATASTD-1006, DATASTD-1358)

   • StudentSchoolAttendanceEvent,

   • StudentProgramAttendanceEvent,

   • StudentInterventionAttendanceEvent.

2. Assessment Registration domain Accommodations related update request (Ref: DATASTD-2376)

3. National School Lunch Program (NSLP) Direct Certification (Ref: DATASTD-1624)

4. Changing the data type for EducationOrganizationId from integer to string

5. Career and Technical Education (CTE) use cases

Meeting Materials

• Presentation Deck:

Meeting Notes

1. Replace StudentSectionAssociation with Student and Section references:

• Discussion:

  • Current Model Issues: The current model references Student and Section separately, leading to data integrity issues where students are reported without being enrolled in a section.

  • Proposal: Replace separate references with StudentSectionAssociation to ensure data integrity.

  • Concerns:

    • Complexity and data stability, especially with begin dates as part of the key.

    • Potential issues when students change sections or have multiple enrollments.

  • Suggestions:

    • Remove BeginDate from keys to simplify data management.

    • Consider the impact on data systems and the need for additional searches.

    • To have a Tech Congress discussion session to see pros and cons of switching to referencing association instead of two domain entities separately.

• Outcome:

  • General agreement on the need for a more stable and less complex solution.

  • Further analysis required to determine the best approach.

2. Assessment Registration domain Accommodations update request:

• Discussion:

  • Current Model Limitations: The current model lacks the capacity to preload accommodations specific to subjects.

  • Proposal: Create an assessment accommodation domain entity applicable to specific assessments.

  • Concerns:

    • Practical implementation and alignment with existing systems.

    • The need for subject-specific accommodations and how they vary by assessment.

  • Suggestions:

    • Add subject identifiers to the general accommodations model.

    • Ensure accommodations can be specified for different subjects and assessments.

• Outcome:

  • Agreement on the need for subject-specific accommodations.

  • Further clarification and detailed proposal required.

3. National School Lunch Program (NSLP) Direct Certification:

• Discussion:

  • Current Model: DirectCertification is currently a Boolean value, which does not meet the needs for more granular data collection.

  • Proposal:

    • Extend the StudentSchoolFoodServiceProgramAssociation with additional descriptors for direct certification sources (e.g., SNAP, TANF, homelessness).

    • Alternative proposal to create a standalone eligibility determination entity.

  • Concerns:

    • The impact on data systems and the need for detailed reporting.

    • The practicality of implementing a new entity versus extending existing models.

  • Suggestions:

    • Consider the best approach to meet federal reporting requirements without overburdening stakeholders.

• Outcome:

  • Mixed opinions on the best approach.

  • Further analysis to determine the most effective solution.

4. Changing the data type for EducationOrganizationId from integer to string:

• Discussion:

  • Previous Changes: The EducationOrganizationId was previously extended from 32 to 64 characters as an integer.

  • Concerns:

    • Data quality and consistency if switched to string (e.g., leading zeros, case sensitivity).

    • Potential issues with data matching and interpretation across systems.

  • Suggestions:

    • Retain integer type for better data quality.

    • Consider alternative solutions for specific identification needs.

• Outcome:

  • Consensus to keep EducationOrganizationId as an integer.

  • Consideration of alternative solutions for specific identification needs.

5. Career and Technical Education (CTE) use cases:

• Discussion:

  • State-Specific Needs: Various states (Vermont, Delaware, Wisconsin) have specific CTE data needs and extensions.

  • Vermont's Approach: Includes average daily minutes of instruction, CTSO memberships, and program-specific details.

  • General Needs:

    • Support for diverse CTE requirements.

    • Detailed tracking of student participation and outcomes in CTE programs.

  • Suggestions:

    • Collect more detailed use cases and feedback from states.

    • Consider how to represent CTE courses and other related data.

• Outcome:

  • Agreement to collect more detailed use cases and feedback from states.

  • Plan to revisit the topic in the next meeting for further discussion.

Next Meeting: March 14, 2025
Topics for Next Meeting:

• Continued discussion on CTE use cases.

• Student record transfer domain updates.

• EPDM related updates in the 5 model.

Action Items:

• Collect more detailed use cases and feedback on CTE requirements.

• Analyze feedback on NSLP direct certification proposals.

• Reevaluate the impact of references in assessment registration.

Notes:

• Participants are encouraged to send additional topics or suggestions via email or Slack.

Next Meeting Mar 14, 2025

• Topics to cover:

  • CTE related extension specifications in Ed-Fi states,

  • Student Record Transfer domain related updates,

  • Summary of EPDM Community extension mode to Ed-Fi UDM and community feedback collection,

  • Any other topics community members share with Mustafa.