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

CourseTranscripts Endpoint Does Not Allow for More Than One of the Same Course Credits In A Term

    XMLWordPrintable

Details

    • Question
    • Resolution: Approved
    • Major
    • None
    • None
    • None
    • None

    Description

      Hi all, 

      I have a question/clarification related to the CourseTranscripts endpoint.  We are implementing the endpoint for a customer from Illuminate SIS database extracts to load data into the ODS.  We are running into a case where multiple course credits from Illuminate are overwriting each other on upload to the ODS.  

      The case in question is a student who has two transfer course credits during the summer session of 2017 (see screenshot) that correspond to the same internal course (V-ONONAG).  If I am understanding the primary keys properly, the primary keys are the required fields in the endpoint.  

      • courseAttemptResultDescriptor -> Both records are passing
      • courseReference  -- > Both records refer to the same internal course (V-ONONAG)
      • studentAcademicRecordReference -> Both records refer to the same ed org and the same term
      • earnedCredits  -> Both records earned 4 credits

       

      As a result, the two records are overwriting each other on upload to the ODS using a POST.  So a few questions:

      • Am I understanding the primary keys properly such that differences in an optional field (like CourseTitle) wouldn't matter for the identity of the record?
      • Does the data standard here not account for this case or am I missing something?

      Seems like there was maybe a related ticket a while back around this but it is old so hard to tell DATASTD-1073.  

      I believe this is the same on 3.2 (our current version) and 5.2.  

      Let me know what you all think.  Appreciate the help!

      Thanks,

      Mario

       

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              mariopalmisano Mario Palmisano
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Salesforce