 To integrate Zoom with Moodle, we first check out if there was any existing Moodle plug-in for Zoom. And we found one in the Moodle plug-in repository. This plug-in is developed by UCLA, University of California, Los Angeles. So our journey with Zoom started by installing the UCLA plug-in to one of our test sites and we started testing it. On top of that, we started talking to course creators, administrators, teachers and several people about their work processes and requirements on the technology. So basically how the UCLA plug-in works is that the activity creator is automatically set as the host of the meeting. In our case where course creators are not necessarily the teachers of the class, that wouldn't work out. So we basically needed something where the course creator can either assign a host if the teacher of the class is already known, or that could be left blank for later, let's say till the start of term. Another thing that wasn't covered by the UCLA plug-in was any handling of exceptions, say a teacher fell sick or a guest lecturer wants to appear in a class. Zoom itself provides a feature called alternative hosts, but that feature wasn't supported by the UCLA plug-in. So we decided to create our own plug-in, but not from scratch. We simply forked UCLA plug-in to create our own plug-in. Then we developed our require features and we also did some improvement. For example, we handled automatically Zoom authentication. So imagine the teacher click on the link, start meeting, and within this link we include a token that we grabbed from Zoom API that's going to identify the user when it starts the meeting. So no need for the teacher to type any Zoom login or Zoom password is already automatically logged in. So challenges, Zoom was a new system and never used it before, never heard about, so we first had to learn how to use it. Then we map our user stories with Zoom technologies. So Zoom was a new technology for most users involved. So a lot of training sessions and comms had to pave the way for a successful launch in May this year. The launch went very well and we were able to gather feedback for further improvements from the pilot group. Of course, successful launch always attracts like other people or other colleges got interested in using the Zoom plug-in. With new people interested, they always come with new requirements as well. So one of the major things that wasn't covered by version one of the plug-in was any handling of lecture recordings. So what we basically wanted to achieve is that the teacher can simply hit the record meeting button and the recording becomes automatically available in Moodle for the student afterwards. For us, it was very important to have a secure solution to store the recordings and to protect the privacy of the students. So we identified few issues keeping the recording in Zoom Cloud. The first one was all the recordings were under the teacher account. So what happened when the teacher left or decided to delete the recordings? There is no branding, which means no watermark and no... And the cost to keep your recording in Zoom Cloud is just prohibitive. So we decided to move our recording to AWS. Why AWS? Because it's the biggest cloud provider. It's available in each region our businesses are and we already work with AWS. So let me show you our solution, our stack we have in AWS. We can deploy the solution in less than 30 minutes using CloudFormation script. So all our recordings are stored in S3 bucket. We use Elastic Transcoder to add watermark and copyright statements. And to download or stream the video within Moodle, we use AWS platform. With this service, our S3 bucket are not publicly exposed. And we provide a whole bunch of statistics regarding our usage. With this solution in about 30 minutes after the class ends, it's already available for the students in Moodle. So how much does it cost to run that in AWS? So using AWS calculator, let's take an example. You have 1,000 videos, one hour each. Each video if you 100 times. It will cost you around 2,500 dollars. So let's have a look how Zoom activity actually looks like in Moodle. In the top area you can see basic information about the Zoom meeting. And in the bottom area you can see how recordings are displayed. So version 2 with recording went live 2 weeks ago. We're still gathering some feedback regarding the recording management. And we're now going to start the process to submit this new plugin to Moodle HQ. So we can share it with the community. So we know this was quite a short presentation. And we didn't cover every detail, as much detail as we wanted. So if you have any questions, please ask. Thanks. I'm actually from UCLA. And I work with Rex Lorenza, who together with the rest of our team created the Zoom plugin. And we worked extensively modifying it to take care of some of the use cases that you mentioned as not being covered. So I just wanted to make sure we were on the same page. You said that our plugin made it impossible for the students and or participants to enter the meeting if the host wasn't there. Is that correct? So you needed to have the host. The host had to have the meeting going before the participants could enter it. I'm not quite sure what you mean. But now we were talking about that the host is automatically locked into Zoom. He or she doesn't have to log in when you hit the start meeting button. You don't have to log in to Zoom. The system does it for you. So I think I was talking about something slightly different. But I guess with our system, a lot of our instructors use Zoom by taking advantage of the recurring meeting option. They go in, create a meeting, start it. It's open forever. And they also then choose the enable or allow students to enter before host. They can go into that meeting space anytime they want without the instructor knowing. So for some instructors it's quite a useful feature. And my sense was that that wasn't... I think what we had to change was when we create Zoom activity, you need the creator of the Zoom activity has to be the host. So the teacher has to create an activity. So the problem we have is when we create this activity, we basically don't know who's going to be the host. But we need to create an empty shelf, an empty activity to be here. And later on we will set up the host. The problem persists. Thank you. Other questions? We probably have time for one or possibly two questions. No? Just quickly, that fee again, two and a half thousand dollars. Annual, monthly... Per month. It was per month. When you generate first month if you create one thousand videos. Okay. Thank you Nick. Thank you Andrea.