Closed saschaben closed 5 years ago
Hi Sascha,
That's a really interesting feature! The CI doesn't have anything to model that kind of relationship yet, does it?
@scottkroyer it does not. I suspect we would either need to express them as a single entity with Primary-secondary assignments of event type, or (more likely) an updated version of the CI will include this sort of linkage.
For the UI, the current "Due By" label is replaced by a toggle. State 1 is the current status quo:
State 2 replaces the calendar/date picker with a drop down select list of all the current sessions in the course:
Future states may require the extension to select sessions from other concurrent courses in the program.
A session to session link would be similar, allowing for a toggle on/off of linkage, and a selection of the linked session.
Linked ILM in the calendar would provide this to students:
ILMs in the calendar view would now get pulled from the grid and "boxed" like multi-day events, displaying in the day and week view for 14 days prior to due by date; In WAAG and agenda, they would display in line chronologically as normal.
For session-session links, need to discuss how to present (or if to present) linkage.
With the increased use of the "flipped learning" model, as well as more interest in linking specific learning events to assessment events, we need to allow for sessions to be associated with one another at a more granular level than just course. For example, if we have a session assigned to the independent review of material ("watch the video") as well as a session for the large group discussion and review of that material, we need the means to associate the two for analytics. Similarly, a learning session ("lecture") with a directly associated assessment session ("exam") should be able to be associated in the same way, without effecting the overall structure of the course or other sessions.
A paired key ID that could be transferable across cloning and rollover (sime=ilar to that proposed for objectives) could be a simple solution to this, which could then be captured in the API and expressed on the front end.