 Thank you, everyone. That was really great to hear the last presentation. I love to hear about when people are using Moodle to help make the world better in some way. It really agrees with our values and empowering educators to improve the world. Now I'm talking about Google Drive, which is a improvement to an existing integration that we worked on for Moodle 3.3. Before Moodle 3.3, for a very long time we've had an integration with Google, which was done by Dan Holtowski, who's a good friend of mine, and a long-time Moodleer, and he's written a whole bunch of useful plugins. So the previous integration was very simple and it works very well and it's very stable. The way that it works is it just lets you browse your Google Drive integration and when you select a file it will make a copy of that file into your Moodle course. So the content of the file has been converted to an open format like a Google Doc will get converted to a rich text file and actually downloads the file and puts it in your Moodle site. And so at that point it's no longer connected to Google at all. It's just a rich text file sitting in your Moodle course. Which is like it's a nice integration. It helps people manage their files and it does work really well. But in talking to a lot of people we get feedback from all sorts of places. Martin in particular as well. There were some extra things that they wanted in their integration with Google. So what they really want some people were asking for is the ability to actually leave the file in Google. So they just want to have a link to the file. And they want it to work. Obviously when people click the link they don't want people to be blocked by you don't have access to this file or you have to worry about which account to log in with on your Google and all of these problems. But they don't want the file to exist in Moodle as a static copy. They want to be able to make changes to the file in Google and have them automatically reflected in Moodle. So we have updated our integration. So for this is the admin settings page for the new integration. Which not everybody needs to know exactly how it works. But the important thing to know on this particular page is that there are some new settings which you can use to configure how the files are either left in Google or copied into Moodle. So that's these settings down the bottom here. Where you can choose between external. So the links will actually stay in Google in this case. You can choose to internal which means that they'll be copied every time into Moodle just like the old integration. And then you could also choose to let the teacher decide when they're linking to a file. In which case they'll just have two radio buttons to choose between those two options when they're creating the link. So but the site admin will configure that and that determines how it will work across that entire Moodle site. So if you decide as a policy that all of your files are going to stay in Google you can set that and control it here. Or if you want all the files to be copied down and you don't want to use that link functionality at all you can set it here and they will never get the option and it will just work like that. The other thing that you can see here is that the new Google integration uses OAuth. So I have another presentation about OAuth but really what they're saying is that our authentication is now connected to the repository. So if people could log in from the front page of Moodle using their Google account and then they're already logged into Moodle and Google. So when they go to use Google Drive they're already in there with the right account for the institution and it's all synced up together. So how does it look for a student? A student can come along now. What I'm going to walk through here is this workflow about having a file that actually stays in Google because this is the new piece to this integration that people were asking for. It's not just as simple as the file stays in Google, it's actually a bit more involved than that. So the student will come along, they'll add their submission to their assignment and then they will use the Google Drive repository to list all their files. They'll pick any of their files from Google and create the link. Now the reason you can tell this is a link is it has that little arrow on it. And the other thing that you can see is that it's still a Google document at this point. So that's the GDoc extension is a Google document. So before that would have been converted into an RTF but now it's still a Google doc and you can do all the things that you can do with the Google file. So when they hit save changes and they submit this, the interesting thing that happens, so this is what was asked for by partners and different people. But when you're working on an assignment, it's a specific workflow that you need because you don't want to just have a link to the file in the student's own personal Google Drive account because the assignment might have a due date and the student's not supposed to be able to make changes after the due date. So you actually, what we do is we copy the file from the student's Google account to a system Google account. So it's now a different Google document and we link to the one that the system account owns. So that means that we can use Moodle to control who can have access to that file and when they can have access. It means that the student's Google account disappears for some reason. We still have the file. It's kept in an account that's controlled by Moodle. And it means that when people go in and make changes, they can still go in and make edits to the Google document and those will get reflected right away in Moodle, but it's all owned by the actual Moodle system. So yeah, you don't want students to be able to just keep making sneaky edits to their assignment submission after the due date. So if they make those edits, it won't actually update the file that they submitted. So they still have a process where they go through the assignment module and they're submitting, this is the version of the file that I'm submitting for assessment. So for a teacher though, a teacher might want to be able to go in and make changes to the file that the student submitted. And the reason that they might want to do that is they might want to give feedback. So if they can use all of the annotation and comments, features of Google documents to give the student feedback and the student will be able to go in and see those changes. So what happens is when a teacher sees a link in Moodle and they follow that link, at the point that they follow the link, Moodle will connect into the Google account and give them a temporary editing access to the file. And Moodle knows that the teacher should have access to the file at the point that they click on the link. So that's why they get a time limited access to make changes to that file. The reason that it's time limited is because your teachers might change over time and we don't want to have a big complicated sync process where we have to mirror all of the permissions and groups and users from Moodle in Google, but instead we want to make it a nice, like a really fast integration where we don't have any performance overheads but you still have all of the features that you need. So the teacher will see the file. This is just zoomed in from the assignment grading interface. So they see the file in Google and they just follow the link. One thing to note is that this is an existing capability in Moodle, but the ability to edit a student's submission is a capability in the assignment module. So you have to turn that on if you want teachers to be able to edit the Google documents that have been submitted. But that's the same as if they had just uploaded a Word document. It's the same capability. And then the teacher will be logged in to Google using their Google account and they will be able to make changes to the file. So the other interesting thing is this was just one part of the changes to the Google integration that we made in 3.3. The other parts here is we connected it to authentication, which is another talk that I'm giving at the Mood. And the other thing is that there's a new Google document converter, which is part of the workflow in an assignment where uploaded files are converted to PDF so that you can use the annotate PDF interface to draw on the assignment submission. There was troubles with the way that worked before because we were using another process. If you've heard of Unicom, you know what I'm talking about, but there's now a new option for a Google document converter, which works much simpler and better. Okay, thank you very much for listening. First question at the back. Is this or will this be compatible with the turned it in plugin? Yes. So turned it in will have to make updates, but it's built into the API so that any plugin can get the actual content of the file. So an example of that is the mobile app. If the student wants to download all the files, if the student wants to download the files for offline access, they'll get the converted version of the file. So it'll be converted to rich text file and downloaded to their mobile. And turned it in can use the same API to get the raw text. So yes. It's still there as an option. This is another option. It's been converted into a plugin type. Yes. Richard, it still converts to PDF. I have another talk on that one. So if you check the schedule, you'll see my other presentation on that just about that conversion piece. Yes. Okay, last question. Yes, and I have another presentation about that too. Okay, thank you everyone. Come and ask me questions at any time, but we'll stick to the schedule.