- A user logs in with their Seneca ID and password
- The user can join an existing lecture/meeting or create their own
- Teachers can create lectures (choosing the course from a drop-down list which in turn is populated by a courses.xml file) or general meetings (referred to here just as meetings) with the title coming from a text box
- Employees and students can create meetings, but not lectures
- Lectures have precedence in the list of available meetings
- Lectures can have the option to allow guests (bypassing LDAP) and to make the session recordable; meetings do not have these options
- Lectures can be given a section; meetings cannot
- In the list of available meetings, lectures will appear alphabetically as "<Course name> <Section> <Presenter's name>", meetings will appear alphabetically after the lectures as "<Meeting name> <Presenter's name>"
- The user creates a moderator password and viewer password (for lectures and meetings) and is responsible for distributing those passwords to anyone he/she wants to attend the meeting
- A user can edit/delete their own meetings and lectures
- A URL can be generated with the moderator or viewer password to distribute
Chad
- I think teachers should be able to create meetings as well. Take for instance Fardad. He's techincally listed as a Professor, but he also might want to make a meeting for CDOT purposes.
- There needs to be something added for viewing/distributing your own recordings
- I think employees should be able to allow guests into their meetings. Again for CDOT employees that want to allow outside people.
- When someone joins a lecture/meeting, either their own or another person's, should it load in the current tab/window or open another one?
- Add an option to allow the creator of a meeting to force the meeting to end? I think this is possible in the BBB API