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

Staff Credential Level Descriptor Type

    XMLWordPrintable

Details

    • ODS/API v2.2 - Sprint 1

    Description

      Summary of outcomes for Data Standard 2.1

      • Problem Addressed: LevelDescriptor is a redundant structure.
      • High-level Reasoning: The Credential domain entity references the descriptor Level, which maps to GradeLevel. However, the annotation for this reference states "The grade level(s) certified for teaching." The Level descriptor is not referenced in any other place in the data standard. Since the Level reference in Credential could be replaced with a reference to the GradeLevel descriptor, this structure is no longer necessary.
      • Changes Made: Removed Level descriptor reference from the Credential domain entity and replaced it with a required reference to the GradeLevel descriptor; Removed LevelDescriptor from the model

      Original ticket description follows:

      In the xsd we have defined the Level of the Staff Credential as a new Descriptor type when there is no need to do this since the definition of this data element is
      "The grade level(s) certified for teaching."

      Therefore the Level type should be of just "GradeLevelDescriptorReferenceType"

      Otherwise this is creating an extra unnecessary descriptor that makes the definition and the reference to the grade level type and descriptor confusing and redundant.

      <xs:element name="Level" type="GradeLevelDescriptorReferenceType">
      <xs:annotation>
      <xs:documentation>The grade level(s) certified for teaching.</xs:documentation>
      <xs:appinfo>
      <ann:Descriptor>LevelDescriptor</ann:Descriptor>
      <ann:EdFiId>786</ann:EdFiId>
      </xs:appinfo>
      </xs:annotation>
      </xs:element>

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              sbrunetjones Silvia Jones (old account) (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Salesforce