MCT-master/mct-master.github.io

Replace all local video URI's with an embedded YouTube URL

Closed this issue · 19 comments

ulrikah commented
Replace all local video URI's with an embedded YouTube URL
stefanofasciani commented

this should be top priority for Spring 2020. Large files should be hosted elsewhere and just linked.

alexarje commented

We should also find a more longterm archive solution for video files (non-YouTube).

jacksongoode commented

It would be very nice to find some non-Google archive for these video files. As of now, I've created a Google account to host some of the larger video files that I found in the repository - the login info and email account used was created and shared with the MCT students. All of the video links are currently unlisted but it would be possible to simply replace the media embedded in the blog posts with the urls.

ulrikah commented

At NTNU, all students have their own server space at folk.ntnu.no. Maybe it could be an idea to request an account like that for MCT, at either NTNU or UiO?

With folk.ntnu.no, it's possible to drag and drop files from the local file system to the server, which is a nice option. Also, we could scp the entire assets folder and do an auto replace of all the URI's, instead of uploading one by one.

alexarje commented

Yes, all UiO users can set up their own space on http://folk.uio.no/, so it may be possible to solve it like this.

stefanofasciani commented

I´m wondering what happens to folk.ntnu.no and fold.uio.no if/when the user account gets deleted, or when one is no longer an active student or employee.
An option for large files can be to create another repository under the account MCT-master (we can call it large files, or assets...). There we can upload large files directly from the browser (upload button, or drag and drop). This second repository will now be downloaded on your machines and you will never pull/commit to this repo.

ssaue commented
ulrikah commented
alexarje commented

From a GDPR point of view, it is best to stick with UiO/NTNU solutions. We are not allowed to use solutions that rely on storing files on non-European servers.

stefanofasciani commented

We decided that for the time being we will use the G Drive associated with the Google Suite of my UiO account (suitable for the GDPR point of view because data is stored in European servers).

This is a medium-term solution (not yet ideal) because these G Drives will be deleted when a staff/student is no longer affiliated with UiO.

Before adopting this solution (and writing the instructions in the MCT github), we should check how it integrated with the blog.

This is the link to the folder (it contains a video and an image)
https://drive.google.com/open?id=1YaZQPs3YMJqcKQqO1c9kkZxhUGfYBaUd
(anyone with the link can see, to edit/add files I must add you to the list of google account with editing credentials).

Select the file, choose open in a new window, and then click on the row of 3 vertical dots on the top right. There you will "Embed Item".

@alexarje @ulrikah @jacksonmgoode send me via email the Google-linked email you want to use to edit/add files in this folder.

alexarje commented

Is this a shared folder or a Team Drive? Not sure if there is a difference in practice between the two types (except for ownership to the files)?

stefanofasciani commented

That is a shared folder in my G Drive. This is fine for the GDPR perspective.

It is also possible to setup a "Shared Drive". The workflow is a bit different as you have to set the visibility of each individual file you upload rather that setting visibility at folder level.
I've just set up one, and here are the links to the sample files
https://drive.google.com/open?id=1dCL2IR8kC_xcA2tALA669zeh0Mu7N7rQ
https://drive.google.com/open?id=1sVWVKW6I1POzQMbWDcrdZV57CtIgtf-b

The "Shared Drive" seems a better solution from the collaboration point of view. If one member leave (including the creator), the files will remain there. However, it is not clear where these files will be stored (EU servers?). To ensure that files are stored in EU servers everyone should join the shared drive with the UiO G Suite account.

https://support.google.com/a/users/answer/9310351?hl=en
https://support.google.com/a/users/answer/9310352#1.1

ulrikah commented
stefanofasciani commented

Do you know how many large files are currently stored in Github rather than embedded from youtube&co.? Just to get an idea on the effort for this migration.

ulrikah commented
stefanofasciani commented

I did not the number to be so high. If we migrate now we should aim for a final solution, not for a temporary one. A shared G Drive where users sign in only with UiO G Suite account seems the safest way to go (it wont be deleted, and it's fine from the GDPR perspective).
However, this require for each student to create a G suite account linked to the UiO account (it's fairly easy to have it up and running, there is no need for a new username and password). https://www.uio.no/english/services/it/store-collaborate/gsuite/
What do you think?

ulrikah commented

Now that we have started merging into this new solution, how do we remove the previous assets from the version control? From what I can see, the .git file weighs ~1G. If we manage to remove both the .git and most of the assets folder (~991MB), the repo size will be much more comfortable.

  • 👍1
jacksongoode commented

I say we close this issue and open two new issues:

  • Migrating large media files to G-Drive, see #10
  • Reducing the version control size, see #12
  • 👍1
stefanofasciani commented

In general, it is better to store them in G Drive. When embedding from youtube (iframe) the Markdown preview in Atom keeps refreshing every few seconds and the video wont preview. The G Drive is also preferred for GDPR reason.