4. What Moodle does with files This is going to be mildly complex. You will cope.
5. What Moodle does with files Moodle is a website Sometimes you store files there Add a resource -> File Sometimes you just store links Add a resource -> URL
6. What Moodle does with files If you add a File to Moodle: You can use Moodle to control things like Permissions and Visibility Moodle can backup the resource with the site
7.
8.
9. What Moodle does with files When you add a file… The file is placed in the file store, and its location in your site is stored in the database
10. What Moodle does with files When someone else adds the same file The file isn’t stored againAnother location is recorded in the database
11. Eachuse of that file can have different permissions etc… and can be used / removed / changed independently! That’s really cool
12. What Moodle does with files When an instance of a file is deleted The location is deleted from the database
13. What Moodle does with files When all instances of a file have been deleted A cleanup process removes the file from the file system
15. Moodle repositories Moodle 2 introduces a new type of plugin: REPOSITORIES Any systemthat stores resources of any kind can be a repository A repository plugin provides a simple way of getting files into Moodle from one of those systems.
20. about a dozen other systemsGerwood has built one that talks to eReserve
21. Why use a particular repo? It’s where your stuff is (e.g. Dropbox, GoogleDocs) It’s where someone’s sharing something(e.g. Flickr CC images, YouTube) It helps make other things easier eReserve: CAL reporting une.tv: tools for managing audio & video, syndication
22. Repo examples: link GOOD Change original (YouTube); change everywhere(link is just a link) BAD Delete original; break links everywhere Repo has to serve files publicly(link is just a link)
23. Repo examples: file (import) GOOD Delete original; we’re ok Moodle provides access control BAD Change original;update nowhere We might be storing for no reason
24. What about “Shared Files” (“Legacy course files”) Shared Files is just an external repository which happens to sit in a particular “site” (course) in Moodle It supports link(URL) and import(file)
25. What about “Shared Files” (“Legacy course files”) AS LINK GOOD Files are in Moodle A splash of Moodle access control (linked to course/site) BAD Change original; maybe update where it’s used Delete original; break links everywhere No fine-grained access control Moodle storage limits for massive files Encourages storage of junk that’s never used
26. What about “Shared Files” (“Legacy course files”) AS FILE As per any other file resource… i.e. the file is copied into the place where it is used.
27. The holy grail: import & sync From http://docs.moodle.org/en/Repository_API (14-12-2010) Once a repository has been used the file will usually be copied into Moodle there and then. However there will also be options to: only return the URL to the file if it's desired to keep it external (but this does present security and integrity risks), or refresh the local file copy regularly and automatically refresh the file manually if desired Once in Moodle, it is subject to the Development:File API for access control like any other file. GREEN = not actually built
28. The holy grail: import & sync GOOD Change once;update everywhere Moodle provides access control BAD Doesn’t solve the file storage issue (files ARE imported) Doesn’t yet exist
29. So where do I put… ? * Perhaps importing (and syncing) from a new repo at a later date?
30. Q. When should I use Shared Files? Less often than you think! A. If multiple (link) resources will point to different parts of the same bucket of filesi.e. an HTML “mini-site” Remember: Shared files provide far less access control Links to Shared Files aren’t magical – they can still be broken if the original disappears!
