At the start of a semester large numbers of teaching staff need to be made aware that automated lecture capture is available in their teaching environment and the offering of a lecture capture service (on an opt-in or opt-out basis) should be automated. As high volumes of courses / users are involved a system is required to:
1. Identify potential users (staff teaching in locations with capture agents).
2. Identify the user's course codes.
3. Identify the schedule of teaching (course code, date, location (capture agent), frequency)
4. Identify students on those course codes.
5.1. Email the teaching staff in a manner that records their consent to be recorded (opt-in).
5.2 Email the teaching staff informing them of the intention to record and allowing them to cancel the recording (opt-out)
6. Creates a schedule based on the above in Matterhorn.
The resulting feature should cover the following use cases:
Use Case 1 - Simple recruitment
Matterhorn sends out an email containing a request to record, a unique url for the request, a summary of the units requested. If the unique url is clicked, the user us directed to an authentication page and then redirected to confirmation page [see MMUI-1.png]. A confirmation email is sent to the user.
Use Case 2 - self-customised recruitment [see MMUI-2.png]
In the same email as scenario 1 there is a second option to customise the schedule. Clicking this option leads to a screen where individual course series and lectures can be added or removed.  disclosure arrows reveal the full schedule of a course.  Additional options are displayed before confirming the schedule. Additionally the user should be able to select the sources available in those locations (audio / audio + screen / audio + screen + video) and which distribution channels (engage / iTunes / YouTube). Finally a confirmation email is sent to the user.
Use Case 3 - Admin UI course scheduled recordings (opt-in) [see MMUI-3.png]
An additional 'Course Management' tab in the admin UI would allow an administrator to manually schedule the recording of whole courses or full sets of courses pulled through from timetabling data. Element  would allow:
The sending of recruitment emails to one or multiple courses, resulting in scenario 1 or 2.
The administrator to scheduling one or multiple course manually.
The administrator to 'black list' a course. Blocking it from being recorded.
Use Case 4 - Admin UI course scheduled recordings (opt-out) [Modified Use Case 3]
An additional 'Course Management' tab in the admin UI would allow an administrator to manually schedule the recording of whole courses or full sets of courses pulled through from timetabling data:
All events in a timetable are listed.
Element 1 from MMUI-3.png allows an administrator the option to schedule all lectures to be recorded.
Course unit staff are sent an email informing them their unit will be recorded with the option to opt out.
If opt-out is used a web link in the email cancels that staff members units (similar to scheduling them in MMUI-2.png)
A black list of units overrides the 'schedule all lectures' function, no bookings or emails are made / sent to black list units.
The user facing element of the system would likely form part of the engage server. Abstraction layers should be required to help account for differing timetable and email system across institutions.