Module as subtype of DigitalResourceCollection
Module as subtype of DigitalResourceCollection
Submitted by abg35@psu.edu on Mon, 10-Sep-2018 11:10.
One of the views in which our instructors and course designers would like to see analytics data is by module (lesson). We can add this information currently in our caliper sensors for our cms by adding a generic DigitialResourceCollection to the isPartOf field of our event objects. However, it would be nice if there was a standard definition for a Module entity as a subtype of a DigitalResourceCollection. A standard definition would cause it to be more likely to be included for lms and 3rd party events, so that we can easily integrate all the events that happen within a module reguardless if it's from the lms, the cms, or a third party tool.
update from discussion at Feb 2019 quarterly workgroup meeting
Hi - this topic was also discussed at the most recent quarterly workgroup meeting in Tempe. The consensus was that the practice which you have outlined is actually the recommended one (adding a generic DigitialResourceCollection to the isPartOf field of the event object). There was some discussion about a module entity, however one of the issues is that there are differences in terminology usage for terms like "module", "unit" and "lesson". So for now, it seems the standard should allow for DigitalResourceCollections to be called by various names with relationships defined using the isPartOf construct. We also noted that the implementation guide should explicitly discuss this issue.
Hope this helps, Linda