Changes

= '''Manage MeetingLectures''' =

User can manage meetings lectures by creating, editing, and excluding them.

=='''Scenario 1:''' Create new meetinglecture.==

| style="text-align: center;" | 1 || Clicks on the empty section of a calendar date or clicks the "Create Event" button. || Returns a page with editable fields regarding meeting lecture details. || Database is not affected.

| style="text-align: center;" | 2 || Chooses "MeetingLecture" as type of event from the drop-down list. || "Event Type " field is set to "MeetingLecture". || Database is not affected.

| style="text-align: center;" bgcolor="#E0E0E0" | 6 || bgcolor="#E0E0E0" | Confirms whether or not inserted information is correct. || bgcolor="#E0E0E0" | Returns to the page with previously filled in meeting lecture details including updated schedule information. || bgcolor="#E0E0E0" | Database is not affected.

| style="text-align: center;" rowspan="2" bgcolor="#E0E0E0" | 7 || rowspan="2" | (1). Chooses to save meetinglecture, or (2). chooses to cancel meeting lecture creation process. || (1). Persists meeting lecture and schedule details. || (1). Meeting Lecture title, if presenter-only camera activation will only be available for the presenter, if a public whiteboard will be used, if the meeting will be lecture recorded, meeting lecture date, meeting lecture schedule, and attendees white-list whitelist definitions are added to updated in the database. All fields in the 'lecture', 'lecture_schedule', 'lecture_presentation', 'lecture_attendance', and 'guest_lecturer' tables are used.

| bgcolor="#E0E0E0" | (2). Discards inserted meeting lecture and schedule details. || bgcolor="#E0E0E0" | (2). Database is not affected.

* User gets a feedback message informing that transaction was successful transaction.* A new meeting lecture is added to user's calendar.* On the screen, user has the option to create another meetinglecture, to view the created meeting lecture being shown in the calendar, and to simply return to the calendar page.

=='''Scenario 2:''' Edit meetinglecture.==

| style="text-align: center;" | 1 || Searches a meeting lecture by using the calendar and clicks the meeting lecture label. || Returns a page with editable fields regarding the respective meetinglecture. || Database is not affectedAll fields in the 'lecture', 'lecture_schedule', 'lecture_presentation', 'lecture_attendance', and 'guest_lecturer' tables are used.

| style="text-align: center;" bgcolor="#E0E0E0" | 5 || bgcolor="#E0E0E0" | Confirms whether or not inserted information is correct. || bgcolor="#E0E0E0" | Returns to the page with previously filled in meeting lecture details including updated schedule information. || bgcolor="#E0E0E0" | Database is not affectedAll fields in the 'lecture', 'lecture_schedule', 'lecture_presentation', 'lecture_attendance', and 'guest_lecturer' tables are used.

| style="text-align: center;" rowspan="2" | 6 || rowspan="2" | (1). Chooses to save edited meetinglecture, or (2). chooses to cancel meeting lecture editing process. || (1). Persists edited meeting lecture and schedule details. || (1). Meeting Lecture title, if presenter-only camera activation will only be available for the presenter, if a public whiteboard will be used, if the meeting will be lecture recorded, meeting lecture date, meeting lecture schedule, and attendees white-list whitelist definitions are updated in the database.All fields in the 'lecture', 'lecture_schedule', 'lecture_presentation', 'lecture_attendance', and 'guest_lecturer' tables are used

| bgcolor="#E0E0E0" | (2). Discards edited meeting lecture and schedule details. || bgcolor="#E0E0E0" | (2). Database is not affected.

* User gets a feedback message informing that transaction was successful transaction.* Meeting Lecture has its information updated.* User see updated meeting lecture in the calendar page.

=='''Scenario 3:''' Delete meetinglecture.==

| style="text-align: center;" | 1 || Searches a meeting lecture by using the calendar , and clicks the meeting lecture label. || Returns a page with editable fields regarding the respective meetinglecture. || Database is not affectedAll fields in the 'lecture', 'lecture_schedule', 'lecture_presentation', 'lecture_attendance', and 'guest_lecturer' tables are used.|-| style="text-align: center;" | 2 || Chooses to delete lecture by clicking the "Delete" button. || Prompts if lecture shall really be deleted. || All fields in the 'lecture', 'lecture_schedule', 'lecture_presentation', 'lecture_attendance', and 'guest_lecturer' tables are used.

| style="text-align: center;" rowspan="2" | 2 3 || Chooses to delete meeting by clicking the rowspan="Delete2" button. || Prompts if meeting Confirms whether or not lecture shall really be deleted. || Database Deletes lecture and schedule details. || All lecture data (lecture title, presenter-only camera, public whiteboard, lecture recorded, lecture date, lecture schedule, and attendees whitelist definitions) is not affecteddeleted from the database. All fields in the 'lecture', 'lecture_schedule', 'lecture_presentation', 'lecture_attendance', and 'guest_lecturer' tables are used.

| stylebgcolor="text-align: center;#E0E0E0" | 3 || Confirms whether or not meeting shall be deleted(2). Returns to home page. || Deletes meeting and schedule details. bgcolor="#E0E0E0" || All meeting data (meeting title, if camera activation will only be available for the presenter, if a whiteboard will be used, if the meeting will be recorded, meeting date, meeting schedule, and attendees white-list definitions2) . Database is deleted from the databasenot affected.

* User gets a feedback message informing that transaction was successful transaction.* Meeting Lecture is deleted.* User see updated calendar page (without meetingthe lecture).