Participant Management

Below are some features identified as important in the context of Participant Management (derived from Requirement Outcomes From Planning Workgroups)

• Ability to protect intellectual property
• Ability to manage releases from students, faculty and presenters
• Ability to ensure copyright compliance according to local guidelines/laws
• Ability to communicate copyrights to end users
• Provide/incorporate institutional policies regarding rights to publish
• Define and configure roles according to institutional needs
• Ability to automatically invite instructors to podcast

Participant Management

One of the considerations for a coursecasting system is how to manage the participants. By participants, this generally means the instructors who are delivering the lectures that are to be captured and distributed. Although for most purposes this is faculty, anyone who is captured should be considered a participant, including guest lecturers, teaching assistants, student presenters, etc. (please feel free to add to this list). Issues of consideration for participant management will vary considerably with each school, and can include:

• Identification of lecturers for classes scheduled to be recorded (could be manually identified or make use of existing class information/scheduling data systems)
• Verification that a class is "eligible" to be captured; could be based on infrastructure needs (e.g. capabilities of the room in which the class is being held) or business needs (e.g. payment from the department is required).
• Identification of all participants that may be captured for a particular class (e.g. guest lecturers, student presentations, etc).
• Capture of course information, which may come in part from the participant. For example, capture of some metadata can be automated (e.g. course title, date, time), but may need to be supplemented by the instructor (e.g. titles for each individual lecture).
• Obtained "permission" from each participant for capture and distribution of recording.
• (feel free to add other considerations to this list)

Best Practice Examples

• UC Berkeley has developed an administrative application that supports Participant Management and Semester Startup Workflow