ALL Course Names Changed via One Roster - Impacting Rostering from Classlink

Is anyone noticing that Course Names changed this week via the One Roster API?

We have been using the One Roster API via Classlink all year and the data has been just as expected until Wednesday morning. There is an extra text string at the end of every class and that is impacting downstream processes.

For Example:

All year long until this week: Algebra I - 1

Starting this week: Algebra I - 1 (Fall Semester)

Is anyone else using Classlink Roster Server and the One Roster API?

If so, did 100% of all of your class names change starting this week?

Comments

  • Stephen Boyle
    Stephen Boyle Blackbaud Employee
    Tenth Anniversary Kudos 5 Name Dropper Participant

    @Amy Villa
    Your OneRoster Settings are set to return duplicate class rows for each term - thus the term information in the class name to distinguish between the duplicates.

    It may be that you need only one class row for all terms. Basically, the difference in how the data is sent looks like this:

    One record per term

    • Algebra 1 - 1 (Fall)
      sourceId: 1000001
      terms:
      • Fall
    • Algebra 1 - 1 (Spring)
      sourceId: 1000002
      terms:
      • Spring

    One record per school year

    • Algebra 1 - 1
      sourceId: 1000001
      terms:
      • Fall
      • Spring

    If that is not the case and you do need separate class rows with identical names, can you describe the scenario that requires it.