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

DisciplineAction.DisciplineActionLength (and ActualDisciplineActionLength) is int...make it decimal

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Duplicate
    • Major
    • Backlog
    • None
    • None

    Description

      MI extensions:

      In Ed-Fi v2.0,

      DisciplineAction.DisciplineActionLength
      and
      DisciplineAction.ActualDisciplineActionLength

      have a dataype of int.

      Please change it to decimal to allow for fractional day information.


      Design

      Change DisciplineAction.DisciplineActionLength and DisciplineAction.ActualDisciplineActionLength to have a decimal type.

      Alternates considered

      An alternate possibility is to change the entity definition to go from "school days" to "hours" or "minutes." Such a revised definition would create breaking changes in the field. Also, it is likely to introduce complexity that serves little purpose: since discipline actions are typically counted in school days or fractional school days, such a change would require knowing or calculating the length of the school day.

      Note that CEDS only allows discipline action length to be calculated in whole days (start and end dates) lending support to the concept that whole days are how such lengths are measured.

      Breaking change summary

      • REST API definitons should be unaffected as JSON type is still Number. However, implementations may assume int datatypes and be affected.
      • XML bulk definition change will cause validation and downstream failure.

      Business logic

      Transform existing ints to the corresponding language type:

      • XSD: decimal
      • JSON: Number (no change required)

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jeremybraden Jeremy Braden (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Salesforce