Uploaded image for project: 'Ed-Fi Data Standard'
  1. Ed-Fi Data Standard
  2. DATASTD-1596

Alternative or expanded definitions of Ed-Fi Section

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Major
    • Data Standard v5.0
    • None
    • None
    • None
    • Sprint 10, Sprint 13, Sprint 11, Sprint 12, Sprint 14, Sprint 15, Sprint 16, Sprint 17, DS Refinement, Sprint 18, Sprint 19, Sprint 20, Data Standard Sprint 22, Data Standard Sprint 23, Data Standard Sprint 25
    • 8

    Description

      In the Ed-Fi data model, Section is a strong entity tied to the notion of a CourseOffering, and from there to a Course.

      However, in the field and in K12 practice, such a connection in not always there, as Section can be more of a scheduling construct than a Course-related construct.

      For example, the attached slides from the SEA workgroup provide some examples of this issue, drawn from SEA experiences. One case is credit recovery schools: in such schools students will often be in the same section, but involved in very different course work during that section.

      One key question to consider is the representation of sections in SIS systems: do SIS systems model both concepts (section as exclusively a time/place grouping concept and section as a course-related concept) via the same entity?

      Side note: in Suite 2, Section was also tied to unified "time and place" scheduling - e.g. there was a Location in the key for example. This proved unsustainable - such connections emerged as volatile key fields. 

       

      AC

      • Propose one or more long-term fixes for review in subsequent tasks
      • Propose shorter-term non-breaking options or workarounds that could be deployed for 2023-24 school year (if any)

       

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              Eric.Jansson Eric Jansson
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Salesforce