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

EducationContent choice uses inline sequence of elements

    XMLWordPrintable

Details

    Description

      Summary of outcomes for Data Standard 2.1

      • Problem Addressed: MetaEd does not support the inline listing of child elements of a choice directly within the entity, as is presently the case with the LearningResourceChoice referenced in EducationContent.
      • High-level Reasoning: The EducationContent domain entity includes a choice (LearningResourceChoice) between providing the LearningResourceMetadataURI or providing a series of other properties to describe the learning resource. Presently, the series of other properties are not contained in a common type. This is not supported by MetaEd.
      • Changes Made: Created new inline common type LearningResource to contain the alternate group of properties used to define a learning resource if a LearningResourceMetadataURI is not provided as part of the LearningResourceChoice. LearningResourceChoice now contains a choice between the LearningResourceMetadataURI (as before) and the new LearningResource common type containing the alternate group of properties.

      Original ticket description follows:

      The choice in EducationContent between specifying the LearningResourceMetadataURI or the learning resource metadata properties does not use a common type for the LRMI elements.

      Proposed solution: replace the inline sequence with a new Common type LearningResource which will contain all elements in the current "inline sequence":

      No ODS Impact
      No Api Impact
      No Bulk Loader Impact
      Sample Data- No impact

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              EdFi-Aaron Aaron Wells (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 hours
                  4h

                  Salesforce