The current file hierarchy looks something like this:
- Course Introduction
- Course section summaries (subfolders for each)
- Section backups (subfolders for each)
- Course backups
- Course files
- An assignment
- Activity backup
- Description
- Assignment instructions.pdf
- Assignment instructions.pdf
- Submission (for users that are able to submit files)
- 1st submitted file.doc
- 2nd submitted file.jpg
- A forum
- Activity backup
- Description
- A resource
- Activity backup
- Description
- description image.jpg
- description image.jpg
- Files and subfolders
- a picture to look at.png
- Course Introduction
- Course section summaries (subfolders for each)
- Section backups (subfolders for each)
- Course backups
- Activity backups
- An assignment
- A forum
- A resource
- Course files
- An assignment
- Description
- Assignment instructions.pdf
- Assignment instructions.pdf
- 1st submitted file.doc
- 2nd submitted file.jpg
- Description
- A forum
- Description
- Description
- A resource
- Description
- description image.jpg
- description image.jpg
- a picture to look at.png
- Description
- Remove the activity backups from each individual activity and place them all in a folder called 'Activity backups', stored at the top level of the course. The reason for suggesting this is that it makes the activity backups easy to find, when the user is looking for them, but prevents them from cluttering up the browser when you are not looking for them (95% of the time).
- Move the most relevant files for any given activity out of a subfolder and directly into the root folder for that activity (in the example above, it would be 'submitted files' for an assignment, or the main file contained by a resource, for a 'file resource'). Again, this is about anticipating what the user is most likely to be looking for when they click on the link to a particular activity in the file browser. Any subfolders for that activity's main files could be stored off the root of that activity as well. There is some potential for a name clash with this (if someone uploaded a resource, with a subfolder called 'Description', for example), but I don't think that would break anything, with regards to the code, and it should hopefully only cause confusion in a few very rare cases.
- Hide the 'Description' folder when there are no files attached to the description. This would require an extra database lookup, at the time when the user opens up the activity in the file browser, but I'd have though this was more than offset by the time saved by not having the user click on the link accidentally, only to find there are no files in it.
What does anyone else think?