We need to do some design work to abstract the File Uploader to the level appropriate for it to be reusable across many apps. The goal is to identify the workflow that is reusable and the parts of the workflow that are specific to the various contexts. The reusable workflow becomes the component. The context specific aspects should either become a configuration on the component or development work that is required to implement the component described in a design pattern.
Applying the current designs, http://bugs.sakaiproject.org/confluence/display/GAL/Add+Images#AddImages-desktop, to other contexts for evaluation is one way to do this analysis. We'll look at file upload in:
- Open collections (this is mostly images although some other media files are also uploaded)
- uPortal - Gary, cany you identify 1 or 2 contexts file upload makes sense?
- Sakai - upload in the Resources tool, upload using the WYSIWYG editor (available in many tools like, wiki, syllabus, announcements).
Scenarios should be created for each of the contexts and a Cognitive Walkthrough completed and rough notes shared with the team.
Estimating 2 hours for each cognitive walkthrough and note creation.