Answered
Hi,
We use the API to pull data for a report. When using the listenrollments command for a particular course, a reference GUID is the same for two of the periods. The single digit ID for each period is distinct across the periods in the data returned by the API though, and when we look at the domain level settings, the reference GUIDs for the periods are distinct. So far, we're only seeing this issue for one course, in one school.
Any idea on how this might have occurred, maybe through some action in the UI? And in general, should the GUIDs be safe to use as a way to match up course periods with domain periods?
Thanks
Tony
Comments (6)
Hey Tony:
The GUIDs should be unique per period and they should match that in the domain. Without having the course ID, I'm guessing that someone importing the period, changed the title manually in the course, and then imported the period again. If you look at the course history, you may find some evidence that suggest this occurred or what order and how the changes occurred.
Hi Brad,
Here's the course ID:
Looking at the history of the course, it does appear that the periods were edited in the past. But when I look at the most recent details, the project reference GUIDs and the IDs seem to match up with the domain's projects, and I don't see a duplicate GUID in the details. But when I do a listenrollments (with metrics), limited to that course and a specific student, I still see the reference GUID in two different periods.
Maybe the earlier period edits left things in a strange state?
Thanks
Tony
Sorry, sounds like some miscommunication/misunderstanding must've occurred. I thought that in this one course you said that there were multiple periods with the same GUID.
Within each period in enrollment metrics, you may see a `category` or `objectivescore` reused. This would happen if there are activities aligned to that `category` or `objectivescore` across the multiple periods.
Does that make sense?
Hi Brad,
Listenrollments shows two periods with the same GUID. Here's the periods array, with the student removed, leaving just the period ID and reference GUID. IDs 2 and 3 have the same GUID.
"periods":{
"period":[{
"id":0,
"reference":"0529d9ad69f94f7cb0bb7cdb1040c3ba",
}
},{
"id":1,
"reference":"c6a02dc4b06045bda23297dc97105803",
}
},{
"id":2,
"reference":"7540f4dc4f894a88a993ebb549f0309e",
},{
"id":3,
"reference":"7540f4dc4f894a88a993ebb549f0309e",
},{
"id":4,
"reference":"d531c7f1b6c24ea08d0b502808a2c70d",
},{
"id":5,
"reference":"ffe65045165b4333bdf18d036cc3052c",
}]
}
Thanks
Tony
That is interesting behavior. We will likely need some dev investigation into this. Could you have your authorized support contact create a support ticket for us to further investigate this?
Hi Brad,
I've asked them to open a support ticket.
In the meantime, they discovered another course with the same problem. I've confirmed that the periods for the new course have the same duplication of GUIDs, for the same periods, IDs 2 and 3.
The new course ID is: 78177634
"periods":{
"period":[{
"id":0,
"reference":"0529d9ad69f94f7cb0bb7cdb1040c3ba",
}
},{
"id":1,
"reference":"c6a02dc4b06045bda23297dc97105803",
}
},{
"id":2,
"reference":"7540f4dc4f894a88a993ebb549f0309e",
}
},{
"id":3,
"reference":"7540f4dc4f894a88a993ebb549f0309e",
},{
"id":4,
"reference":"d531c7f1b6c24ea08d0b502808a2c70d",
}
},{
"id":5,
"reference":"ffe65045165b4333bdf18d036cc3052c",
}
So maybe this problem is related to editing the periods at a domain level, instead of a course level?
Thanks again,
Tony