7.7 Learning and Teaching
7.7.1 File Share Tool
The file share tool is a simple shared file space, which can be configured in a number of ways, including:
write-only A coursework drop box for students to submit work to.
read-only A repository of course materials for students to download.
wead-write A space for students to share collaborative group work.
No support for more complex file permissions was implemented, such as allowing students to see only files they have uploaded, or allowing students to only see files they or other students in the same tutorial group, have uploaded. A screenshot of this tool is shown in figure 7.10
Files are stored on disk in a structure matching that of the file share tool provided by TAGS; a single directory per file share tool, with two files for each “real” file uploaded. This file pair consists of the stored file itself, a second file containing metadata such as the unique ID of the user who uploaded the file.
Uploader Filename Date Comment Visible Select
Upload new file Choose Fileno file selected Upload Reinaud, Jean NoelAssessmentofMT1001.doc Sep 26, 2007 2:57:12 PM Lindsay, Peter MT1001-project2-examples.mwAug 6, 2007 3:21:12 PM Lindsay, Peter MT1001-project2-exercises.mwAug 6, 2007 3:21:27 PM Lindsay, Peter MT1001-project3-examples.mwsAug 6, 2007 3:21:36 PM Lindsay, Peter MT1001-project3-exercises.mwAug 6, 2007 3:21:45 PM Reinaud, Jean NoelMT1001RACEN.doc Sep 26, 2007 2:57:03 PM Reinaud, Jean NoelMT1001_1.doc Sep 26, 2007 2:13:41 PM Reinaud, Jean NoelMT1001warningnotice.doc Sep 26, 2007 2:13:06 PM Lindsay, Peter mt1001-project1-examples.mwAug 6, 2007 3:20:59 PM Lindsay, Peter mt1001-project1-exercises.mwAug 6, 2007 3:21:05 PM Reinaud, Jean Noelpresentation.pdf Sep 26, 2007 2:12:53 PM
Delete Selected Files Hide Selected Files Show Selected Files Copy Selected Files to student area
Configuration options
Files are grouped by individual student only . Students can Read Write. Update Access
Files
2007/8-S1 MT1001 (Introductory Mathematics) staff area
MT1001 - File Share Bulk Events Modules Logout
Administration
2007/8-S1 MT1001 (Introductory Mathematics) staff area
MT1001 - File Share Bulk Events Modules Logout
Administration
Figure 7.10: Screenshot of Scratchspace Tool
“Scratchspace” Tool
When originally ported to MMS, the coursework tool had a feature (ad-hoc assignments) which allowed students to upload files as submitted work without requiring an assignment to be defined ahead of time by staff (discussed in detail in 7.4.1).
As usage of MMS expanded, it became clear that users were finding this confusing; work would be accidentally uploaded to ad-hoc assignments despite a correct assignment be- ing available, or would upload multiple versions of the same piece of work into different assignments.
The “Scratchspace” tool was a short-lived attempt to blend the file share and coursework tools, providing a space for students to upload files without requiring any specific structure. This would both replace these ad-hoc assignments, and provide an online secure space for students to store files they were working on as part of their studies. It derived much of its core from the file share tool, while adding significantly more powerful configuration options, enabling it to be used as a drop-box (where students could write but not read), or
for file sharing within a group of students, amongst other scenarios.
It was developed independently of the file share tool rather than replacing the existing tool, in the expectation that there was demand for providing both tools as individual options. Staff had frequently complained contradictorily both of the rate of change, and of the lack of change, and in providing an improved tool option without requiring users to change to it, it was hoped to find an effective compromise position.
Content Tool
The “Scratchspace” file sharing and storage tool was adequate for simple use-cases, how- ever it lacked the fine-grain permission controls, content layout, and other functionality that was expected for content management. As a prerequisite of the move of content from WebCT, it underwent an almost complete rewrite, resulting in a new software architecture for the tool, as well as significant changes to its underlying data structures, and of course user interface.
The result was a massively improved tool, which provided a streamlined interface while adding in content metadata and more flexible content types (folders, external URLs, etc.) It did not cover quite the same extensive range of content handling options as WebCT or Moodle, however it was not intended to either; the design was to cover most cases, and to do so simply. A screenshot of the interface is shown in figure 7.11.
The tool utilised the FileAPI8, HTML 59 drag and drop functionality and XMLHttpRe-
quest level 210to enable users to drag files from outside their browser directly into the page to be uploaded. Drag and drop was a major part of the revised user interface, and the tool was one of the earliest production uses of the Javascript File API (many drag and drop file upload interfaces at this point in time were Flash based), in part due to support for the feature being limited to the Firefox browser. Compared to the previous process of using a file selector dialogue, this interface was anticipated to be easier and faster, and informal feedback from users suggested this was the case.
8http://www.w3.org/TR/FileAPI/– accessed 4th May 2013
9http://www.w3.org/TR/2013/CR-html5-20130806/– accessed 20th October 2013
10http://www.w3.org/TR/2012/WD-XMLHttpRequest-20120117/ – accessed 20th Octo-
The extremely early adoption of a number of standards caused a number of issues, however. Some of the implementation had to be re-written as changes were made to both the FileAPI and XMLHttpRequest level 2 specifications. Users reported confusion caused by lack of widespread browser support for the functionality (requests to adapt it to work in browsers without suitable specification support were common). Experiences gained developing this functionality were later used to assist with the Moodle drag and drop plugin11, written by Davo Smith, specifically in relation to handling differences in specification implementa- tions between the Chrome and Firefox browsers.