Information
These are the XHTML mockups for the resources viewer tool.
_Latest Version_
Harriet Truscott has suggested some changes to the text, shown in version 5, which also includes a couple of minor interface additions.
Mockups
| Name | Size | Creator (Last Modifier) | Creation Date | Last Mod Date | Comment | ||
|---|---|---|---|---|---|---|---|
 |
 res-slice4.zip |
405 kB | Gonzalo Silverio | Oct 25, 2006 | Oct 25, 2006 | v4 of markup package - final | |
|
res-slice2.zip |
400 kB | Gonzalo Silverio | Oct 17, 2006 | Oct 17, 2006 | v2 of markup package - simplified | |
|
 res-viewer-flowv2.pdf |
70 kB | Gonzalo Silverio | Oct 24, 2006 | Oct 24, 2006 | v2 of resource viewer tool flow - simplified | |
|
res-slice1.zip |
40 kB | Gonzalo Silverio | Oct 24, 2006 | Oct 24, 2006 | self contained markup package | |
|
res-viewer-flow.pdf |
87 kB | Gonzalo Silverio | Oct 24, 2006 | Oct 24, 2006 | Resource Viewer Flow Diagram | |
|
res-viewer-flowv3.pdf |
149 kB | Gonzalo Silverio | Oct 24, 2006 | Oct 24, 2006 | v3 of resource viewer tool flow | |
|
res-slice3.zip |
407 kB | Gonzalo Silverio | Oct 24, 2006 | Oct 24, 2006 | v3 of markup package | |
|
Resource_viewer_Harriet.zip |
487 kB | Harriet Truscott | Nov 15, 2006 | Nov 15, 2006 | v5, essentially with suggested improvements to text |
Comments (7)
Oct 16, 2006
Jim Eng says:
I'm looking at the first set of mockups dated Oct 15, and I'd like to focus on o...I'm looking at the first set of mockups dated Oct 15, and I'd like to focus on one issue. Assuming I come in as a consumer. I am viewing a "slice", which corresponds to a folder in resources, I assume. But there is also a drop-down at the top of the tool that allows me to choose some other "slice". In email, Aaron posed this question: "Should it be one tool per site or one tool per resource view? (or both should work?)"
In the original JIRA tickets we are working from, the use cases focus on multiple instances of this tool per site with one resources view per instance of the tool. But one of the comments in the tool requirements page suggests that having many instances of this tool in a site may pose problems.
The requirements outlined in JIRA suggest a model for worksite setup in which the lefthand menu focuses on the content and flow of the course instead of the functionality that is available. In a functional view, the left menu contains a list of tools ("Chat", "Discussion", "Calendar", "Dropbox", "Resources", etc). What some users want to do is add buttons to the left menu to represent content-units or timing of materials (e.g. "Week 1", "Week 2", "Week 3", ... or maybe "Chapters 1-3", "Chapters 4-5", ... or maybe some set of content-oriented labels). The original idea of this tool was that it could help support that approach.
If we are designing a tool primarily to support that alternative way of structuring content in a course site, any one instance of the tool needs only present one resources view. That's not to say that we shouldn't consider also enabling multiple views within an instance of the tool. But we will not be addressing the underlying requirements unless we enable multiple instances of the tool in a site pointing at different resource views.
question is whether this tool
Oct 19, 2006
Mike Osterman says:
This may be beyond of the scope this first iteration, but I wanted to get this o...This may be beyond of the scope this first iteration, but I wanted to get this out there.
One of the higher user requirements with regard to the Resources tool is the lack of a "View as..." capability for users with Instructors/maintain, etc.
Use case:
An instructor wants to see how other roles/groups in their site would view the content. They could have a drop-down menu (possibly up by "Edit slice") that allows them to switch between the existing roles and groups defined for their site.
Oct 19, 2006
Mike Osterman says:
Not sure if this was the best place for this comment. It was a result of looking...Not sure if this was the best place for this comment. It was a result of looking at the mock-ups.
Oct 24, 2006
Mike Osterman says:
Gonzalo great job with rev 3! I like the visualizations of the different "Show H...Gonzalo - great job with rev 3! I like the visualizations of the different "Show How" options.
One question - your first commment says "this tool will be shown populated and usable even if mantain chooses to take the resource tool out". I think removing the resources tool is a critical thing to avoid confusion/interface overload. But if this is done, how does the instructor populate the Resources area so they have slices to present? Would they have to access it from My Workspace? And if that's the case, what does that mean for getting to the WebDAV url for the course without the Resource tool?
If there's any way to roll it in, or do the following work in parallel, it would be great to have an option to disable the Resource tool in the portal for users with maintain/Student. Or perhaps tie rendering Resources in portal navigation to site.update or a particular role if the ResourceViewer is enabled. Just thinking/babbling out loud...
Thanks again for your hard work - this is a HUGE step towards meeting our faculty's needs!
Oct 24, 2006
Jim Eng says:
I disagree with the view that a few people have expressed that the Resources too...I disagree with the view that a few people have expressed that the Resources tool should not be shown if one or more Resources tools are used in a site. Some maintainers may want to do that, but others will not. The ResourcesViewer will provide a way of structuring a view of some content, but the Resources tool will have other functionality that will not be available in the ResourcesViewers (at least this first version). I hate to keep using the example of viewer buttons labeled "Week 1", "Week 2", etc., but it's handy ... I can imagine an instructor removing the the "Week 1" viewer when adding "Week 3" and announcing to the class that the "Week 1" material is still available through the Resources tool. By that time, the students are familiar with the content in that folder, and the descriptions are not as important. I can also imagine an instructor structuring some of the content, but also telling students they will find certain other things of interest in the Resources tool. From my experience as an instructor, I think most students will not find this confusing.
That said, the Resources tool is not required for the instructor to access the site's resources collection. We will need to make sure that the addition of a ResourceViewer to the site triggers creation of a site-level collection, like the addition of a dropbox or resources tool do. Once that's done, the instructor can use the Resources tool in MyWorkspace to add items to the site's resources collection.
Our plan is to allow the first version ResourcesViewer to point at folders in the current site and not at folders in other sites. A later version may allow selection of folders in other sites, including the instructor's MyWorkspace.
Oct 24, 2006
Mike Osterman says:
Good point, Jim. I wouldn't say that it should not be shown in all cases, but ha...Good point, Jim. I wouldn't say that it should not be shown in all cases, but having the flexibility to optionally disable Resources when using ResourceViewer would be a big help to us.
I can see some instructors happily continuing with Resources as is, but this would help the others that would like a more presentation-driven layout to their Resources.
Oct 25, 2006
Mike Osterman says:
I should also mention that this is coming from a desire of some faculty to have ...I should also mention that this is coming from a desire of some faculty to have an "assets" area where they can store document support files (images, etc.) that are not intended to be first-class documents. They would like these assets to be usable in HTML documents and wikis, for example, but not show up in the listing of course Resources for students.
I believe I still owe you a JIRA ticket for similar functionality within the Resources tool itlself.