There are at least TWO scenarios in which teachers upload new versions of their files:
- Single Teacher, multiple courses of the same sort, with different classes: every file he/she uploads may be a first draft, a second improved draft, and a final one. Every draft being refined and tuned and improved with the students collaboration, something you develop during the course
- Multiple Teachers, multiple courses of the same sort, with different classes: dito
A real course area, with files lying on the OS file system, still has its reasons to continue to exist like in 1.9, even if it were only to make life easier for system admins who have to recover sigle files from tapes, when teachers lose them or acidentally overwrite them with the wrong version of the same file, which in principle is the very same danger/mess of the new file system. The only difference is that in 1.9 a lost or overwritten file belonged to the course's file area and could easily be retrieved from tape. Now in 2 you never know which version of the file uploaded with the same name and hence replaced is still referenced by which resource. And copying the whole file into a resource's file area only makes things worse, because teacher know this copy of the file only by its original file name and not by the metadata produced by Moodle to correctly handle it internally. So teachers will definitively get lost. A slightly better approach would really be to keep only ONE copy of an uploaded file, so as to store it really only once on the OS' file system and save a lot of disk space, but then a certain file name could only be used once. And if the file's name would be allowed to be used in each course, we return to the point where we startet, the course-file-area of 1.9
As I already said, resources/activities/etc. belong to a course anyway and hence keeping the legacy file system of 1.9 is the best solution for teachers and system admins.
Why do you not combine the CONS of both file systems?
- I would even agree on creating not a course-file-area any more, BUT on a personal basis, i.e. per given teacher or group of teachers (cohort?)
- this area would be created transparently on the OS' file-system to facilitate backup&recovery to/from tapes, no hash no scramble no lookup-tables necessary
- so a file would exist only once and could be referenced in different courses/activities/resources/etc.
- uploading a file with the same name replaces any older version and all references to that file would still continue to work, no link-update necessary
- course backups would include all referenced files to be consistent when you restore them
- restore of backup-zip-files would include an intelligent mechanism to RElink and save the referenced files again into the new teacher's/cohort's file area. So this process has to be interactive so as to specifiy the teacher/cohort before starting the restore
- access permissions should be inherited from the activity/resource/etc. where the file is referenced and not from the file-area where the file resides
- so as not to offer the students the opportunity of guessing a file name like it was in 1.9 links should not show the original file name but a randomly generated ID when the links in activities/resources/etc. are created
- file-areas of single teachers or teacher teams (cohorts?) should be treated as private and hence should not be accessible for others
- still there should be a global Moodle file area like site files in 1.9 accessible to all teachers and admins only. Files from there have to be downloaded first and then uploaded into the teachers'/cohorts' file area, or copied internally to avoid criss-cross references and orphaned links if someone deletes a file there
- multiple references to one file are still dangerous in such shared file areas but we have to leave this to the responsibility of the teacher teams which have to agree on a common policy if they reference a file in different courses/activities/resources/etc.
As per http://moodle.drupalgardens.com/article/tue-06152010-1918/ftp-files-moodle-20-repository-api
Then you can go ahead and create folders for each teacher, or course or however you want to structure the files, and give the content creators (probably the teachers) upload permissions to the folders using FTP or whatever method you allow.
The Moodle 2.0 admin can then add those directories as sources for files in the file picker.
is far too complicated for a medium to large scale site like ours. This should be handled internally by Moodle as I proposed, one directory per teacher oder teacher team. Whether the sysadmin wants to expose those directories per FTP or WebDav should be possible and stay in his/her responsibility.