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

Ambiguities in use of assessment performance levels

    XMLWordPrintable

Details

    • Story
    • Resolution: Approved
    • Major
    • Data Standard v4.0-a
    • None
    • None
    • None

    Description

      In mappings to the Ed-Fi assessment API, some ambiguities in how to use assessment performance levels has emerged:

      See the data model: https://schema.ed-fi.org/datahandbook-v331b/index.html#/AssessmentPerformanceLevel484

      First ambiguity

      It is unclear what score is being referred to in Maximum and MinimumScore, as an assessment can have multiple scores. It seems like there should be some explicit way to connect what scores these are referring to.

      Shouldn't there be a element that makes that connection explicit?

      Note that this COULD be done via AssessmentReportingMethod (i.e., the Score AssessmentReportingMethod and the PerformanceLevel AssessmentReportingMethod match), but that seems risky / bad as, 

      1. it means that each score can only have 1 set of cut scores/performance levels.
      2. it provides no way to give a "human-readable name" to the performance level - you end up confusingly using the score name

      Second ambiguity

      Why even have ResultDatatypeType as part of AssessmentPerformanceLevel? It's optional, but it will always be "level" - why not just remove it?

      Acceptance Criteria

      Data model redesigns and/or normative guidance on how to solve these problems, attached to this ticket

      Attachments

        1. image-2022-04-19-08-13-21-160.png
          152 kB
          Emilio Baez
        2. image-2022-04-19-08-15-00-079.png
          130 kB
          Emilio Baez
        3. image-2022-04-19-08-15-44-733.png
          289 kB
          Emilio Baez

        Issue Links

          Activity

            People

              ecomer Ed Comer
              Eric.Jansson Eric Jansson
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Salesforce