[DG: User Experience] Interesting blog post on CMS user interfaces

Very interesting - thanks Michael!

There were a couple of paras that struck me particularly as relating to the
possibilities for the new Sakai 3:

"The buttons link to pages that simply provide a place to upload a document,
which is exactly what most instructors do: upload word–processed files of their
classroom materials. They are encouraged to “plug in” their content under the
appropriate category instead of envisioning a translation of their individual
pedagogical style into an online environment. Blackboard “tends to encourage a
linear pathway through the content” [3], and its default is to support easy
uploading and text entry to achieve that goal.
The construction of the course syllabus is a familiar beginning point for most
instructors, yet few CMSs consider this. It would be natural and useful for
novice instructors to see a blank schedule into which they could create each
week’s or unit’s activities, rather than a selection of pre–set buttons or
links. Most professors think in terms of the semester, and how their
pedagogical goals can be achieved within the context of time, rather than
space. Some think in terms of topics they want to cover. Blackboard/WebCT’s
default organization accepts neither of these approaches in its initial
interface. It forces the instructor to think in terms of content types instead,
breaking the natural structure of the semester, or of a list of topics. Again,
we know that the setup can be customized with relative ease, by going to the
Control Panel and selecting Manage Course Menu, then using Modify buttons. You
could change all the course menu buttons into “Week 1”, “Week 2”, or organize
by topic instead of content type. But few professors try that, or they assume
that they can’t do it. Blackboard can be highly intimidating to learn, and may
“seriously hinder” choices the faculty member makes while using the tool [4].
Faculty are led by the interface of a CMS not only because they do not
immediately see an alternative, but because the familiar signposts (the
Syllabus button) imply a single way of completing the task (upload a document).
Only the Moodle system provides a default setup that looks like a calendar-style
syllabus ..."

I'd agree very strongly with this statement about pedagogies, and the initial
presentation of potential course structures, rather than tools, to the
lecturer, seems to be something that Sakai 3 has the potential to support

"Although it is an oversimplification, it is useful to separate course
management systems into two types: Opt–In and Opt–Out. In an Opt–Out system
(such as Blackboard) all the features are available by default and must be
excluded to avoid confusing students. Opt–Out systems are most likely to
overwhelm Web novices, because they present an array of tools, and the tendency
is to reduce cognitive load by using the defaults. In an Opt–In system (such as
Moodle), the instructor selects each activity and presentation factor from a
menu list, effectively designing much of the interface for students. Fewer
defaults are pre–set, forcing the instructor to think holistically about the
class structure. Features such as chat, polls, and interactive lessons as
options presented with the same weight as more traditional text–based
resources. Thus there is less of an implication that presentation is key, and
more of an implication that interactivity is important. In an Opt–In
environment, the instructor makes choices about context on a macro level, and
choices about features and tools on a micro level. This makes it possible to
explore pedagogical options more freely"

Again, perhaps a future strength of Sakai 3?

Harriet

Quoting Michael Korcuska mkorcuska@...:

	[DG: User Experience] Interesting blog post on CMS user interfaces by Michael Korcuska-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message It's worth a read.... http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 -- Michael Korcuska Executive Director, Sakai Foundation mkorcuska@... phone: +1 510-859-4247 (google voice) skype: mkorcuska _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"
	Re: [DG: User Experience] Interesting blog post on CMS user interfaces by Harriet Truscott :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Very interesting - thanks Michael! There were a couple of paras that struck me particularly as relating to the possibilities for the new Sakai 3: "The buttons link to pages that simply provide a place to upload a document, which is exactly what most instructors do: upload wordprocessed files of their classroom materials. They are encouraged to plug in their content under the appropriate category instead of envisioning a translation of their individual pedagogical style into an online environment. Blackboard tends to encourage a linear pathway through the content [3], and its default is to support easy uploading and text entry to achieve that goal. The construction of the course syllabus is a familiar beginning point for most instructors, yet few CMSs consider this. It would be natural and useful for novice instructors to see a blank schedule into which they could create each weeks or units activities, rather than a selection of preset buttons or links. Most professors think in terms of the semester, and how their pedagogical goals can be achieved within the context of time, rather than space. Some think in terms of topics they want to cover. Blackboard/WebCTs default organization accepts neither of these approaches in its initial interface. It forces the instructor to think in terms of content types instead, breaking the natural structure of the semester, or of a list of topics. Again, we know that the setup can be customized with relative ease, by going to the Control Panel and selecting Manage Course Menu, then using Modify buttons. You could change all the course menu buttons into Week 1, Week 2, or organize by topic instead of content type. But few professors try that, or they assume that they cant do it. Blackboard can be highly intimidating to learn, and may seriously hinder choices the faculty member makes while using the tool [4]. Faculty are led by the interface of a CMS not only because they do not immediately see an alternative, but because the familiar signposts (the Syllabus button) imply a single way of completing the task (upload a document). Only the Moodle system provides a default setup that looks like a calendar-style syllabus ..." I'd agree very strongly with this statement about pedagogies, and the initial presentation of potential course structures, rather than tools, to the lecturer, seems to be something that Sakai 3 has the potential to support "Although it is an oversimplification, it is useful to separate course management systems into two types: OptIn and OptOut. In an OptOut system (such as Blackboard) all the features are available by default and must be excluded to avoid confusing students. OptOut systems are most likely to overwhelm Web novices, because they present an array of tools, and the tendency is to reduce cognitive load by using the defaults. In an OptIn system (such as Moodle), the instructor selects each activity and presentation factor from a menu list, effectively designing much of the interface for students. Fewer defaults are preset, forcing the instructor to think holistically about the class structure. Features such as chat, polls, and interactive lessons as options presented with the same weight as more traditional textbased resources. Thus there is less of an implication that presentation is key, and more of an implication that interactivity is important. In an OptIn environment, the instructor makes choices about context on a macro level, and choices about features and tools on a micro level. This makes it possible to explore pedagogical options more freely" Again, perhaps a future strength of Sakai 3? Harriet Quoting Michael Korcuska <mkorcuska@...>: > It's worth a read.... > > http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 > > > -- > Michael Korcuska > Executive Director, Sakai Foundation > mkorcuska@... > phone: +1 510-859-4247 (google voice) > skype: mkorcuska > > > > > _______________________________________________ > sakai-ux mailing list > sakai-ux@... > http://collab.sakaiproject.org/mailman/listinfo/sakai-ux > > TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... > with a subject of "unsubscribe" > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"
	Re: [DG: User Experience] Interesting blog post on CMS user interfaces by Jacques Raynauld :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message I also agree. It is a very interesting article. I have always been struck by the Moodle first page template that naturally leads to a week or theme interpretation by users. I think it is one of the important factor that explains Moodle popularity. This is the kind of need we wanted to adress in Sakai/Open Syllabus ... but in a more semantic way than Moodle. Jacques Raynauld HEC Montréal -------- Message original -------- Sujet : Re: [DG: User Experience] Interesting blog post on CMS user interfaces De : harriet@... Pour : Michael Korcuska mkorcuska@... Copie à : pedagogy@... pedagogy@..., Sakai UX sakai-ux@... Date : 2009-11-03 04:58 Very interesting - thanks Michael! There were a couple of paras that struck me particularly as relating to the possibilities for the new Sakai 3: "The buttons link to pages that simply provide a place to upload a document, which is exactly what most instructors do: upload word–processed files of their classroom materials. They are encouraged to “plug in” their content under the appropriate category instead of envisioning a translation of their individual pedagogical style into an online environment. Blackboard “tends to encourage a linear pathway through the content” [3], and its default is to support easy uploading and text entry to achieve that goal. The construction of the course syllabus is a familiar beginning point for most instructors, yet few CMSs consider this. It would be natural and useful for novice instructors to see a blank schedule into which they could create each week’s or unit’s activities, rather than a selection of pre–set buttons or links. Most professors think in terms of the semester, and how their pedagogical goals can be achieved within the context of time, rather than space. Some think in terms of topics they want to cover. Blackboard/WebCT’s default organization accepts neither of these approaches in its initial interface. It forces the instructor to think in terms of content types instead, breaking the natural structure of the semester, or of a list of topics. Again, we know that the setup can be customized with relative ease, by going to the Control Panel and selecting Manage Course Menu, then using Modify buttons. You could change all the course menu buttons into “Week 1”, “Week 2”, or organize by topic instead of content type. But few professors try that, or they assume that they can’t do it. Blackboard can be highly intimidating to learn, and may “seriously hinder” choices the faculty member makes while using the tool [4]. Faculty are led by the interface of a CMS not only because they do not immediately see an alternative, but because the familiar signposts (the Syllabus button) imply a single way of completing the task (upload a document). Only the Moodle system provides a default setup that looks like a calendar-style syllabus ..." I'd agree very strongly with this statement about pedagogies, and the initial presentation of potential course structures, rather than tools, to the lecturer, seems to be something that Sakai 3 has the potential to support "Although it is an oversimplification, it is useful to separate course management systems into two types: Opt–In and Opt–Out. In an Opt–Out system (such as Blackboard) all the features are available by default and must be excluded to avoid confusing students. Opt–Out systems are most likely to overwhelm Web novices, because they present an array of tools, and the tendency is to reduce cognitive load by using the defaults. In an Opt–In system (such as Moodle), the instructor selects each activity and presentation factor from a menu list, effectively designing much of the interface for students. Fewer defaults are pre–set, forcing the instructor to think holistically about the class structure. Features such as chat, polls, and interactive lessons as options presented with the same weight as more traditional text–based resources. Thus there is less of an implication that presentation is key, and more of an implication that interactivity is important. In an Opt–In environment, the instructor makes choices about context on a macro level, and choices about features and tools on a micro level. This makes it possible to explore pedagogical options more freely" Again, perhaps a future strength of Sakai 3? Harriet Quoting Michael Korcuska mkorcuska@...: It's worth a read.... http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 -- Michael Korcuska Executive Director, Sakai Foundation mkorcuska@... phone: +1 510-859-4247 (google voice) skype: mkorcuska _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"
	Re: [DG: User Experience] User Experience] Interesting blog post on CMS user interfaces by Plourde, Mathieu :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. Funny that this thing has come to a full circle… Anyone remember VirtualU? The default course was a long table organized as a list of event with links to discussions and resources. I think the goal of that article was not to say that organizing your content in a calendar was the best way to think, but that the defaults are what most faculty will select. If Sakai 3’s default is to present multiple options in terms of course/activity structure, and can support faculty in choosing an appropriate one to start with, half the battle will be won. Best Regards, ================================= Mathieu Plourde, MBA Project Leader, LMS/Instructional Designer IT-Client Support & Services mathieu@... ================================= TOP LINKS: Technology Troubleshooting: http://www.udel.edu/help Sakai@UD Support and Training: http://www.udel.edu/sakai/training ================================= From: sakai-ux-bounces@... [mailto:sakai-ux-bounces@...] On Behalf Of Jacques Raynauld Sent: Tuesday, November 03, 2009 8:51 AM To: Sakai UX Cc: Michael Korcuska; pedagogy@... Learning Subject: Re: User Experience] Interesting blog post on CMS user interfaces I also agree. It is a very interesting article. I have always been struck by the Moodle first page template that naturally leads to a week or theme interpretation by users. I think it is one of the important factor that explains Moodle popularity. This is the kind of need we wanted to adress in Sakai/Open Syllabus ... but in a more semantic way than Moodle. Jacques Raynauld HEC Montréal -------- Message original -------- Sujet : Re: [DG: User Experience] Interesting blog post on CMS user interfaces De : harriet@... Pour : Michael Korcuska mkorcuska@... Copie à : pedagogy@... pedagogy@..., Sakai UX sakai-ux@... Date : 2009-11-03 04:58 Very interesting - thanks Michael! There were a couple of paras that struck me particularly as relating to the possibilities for the new Sakai 3: "The buttons link to pages that simply provide a place to upload a document, which is exactly what most instructors do: upload word–processed files of their classroom materials. They are encouraged to “plug in” their content under the appropriate category instead of envisioning a translation of their individual pedagogical style into an online environment. Blackboard “tends to encourage a linear pathway through the content” [3], and its default is to support easy uploading and text entry to achieve that goal. The construction of the course syllabus is a familiar beginning point for most instructors, yet few CMSs consider this. It would be natural and useful for novice instructors to see a blank schedule into which they could create each week’s or unit’s activities, rather than a selection of pre–set buttons or links. Most professors think in terms of the semester, and how their pedagogical goals can be achieved within the context of time, rather than space. Some think in terms of topics they want to cover. Blackboard/WebCT’s default organization accepts neither of these approaches in its initial interface. It forces the instructor to think in terms of content types instead, breaking the natural structure of the semester, or of a list of topics. Again, we know that the setup can be customized with relative ease, by going to the Control Panel and selecting Manage Course Menu, then using Modify buttons. You could change all the course menu buttons into “Week 1”, “Week 2”, or organize by topic instead of content type. But few professors try that, or they assume that they can’t do it. Blackboard can be highly intimidating to learn, and may “seriously hinder” choices the faculty member makes while using the tool [4]. Faculty are led by the interface of a CMS not only because they do not immediately see an alternative, but because the familiar signposts (the Syllabus button) imply a single way of completing the task (upload a document). Only the Moodle system provides a default setup that looks like a calendar-style syllabus ..." I'd agree very strongly with this statement about pedagogies, and the initial presentation of potential course structures, rather than tools, to the lecturer, seems to be something that Sakai 3 has the potential to support "Although it is an oversimplification, it is useful to separate course management systems into two types: Opt–In and Opt–Out. In an Opt–Out system (such as Blackboard) all the features are available by default and must be excluded to avoid confusing students. Opt–Out systems are most likely to overwhelm Web novices, because they present an array of tools, and the tendency is to reduce cognitive load by using the defaults. In an Opt–In system (such as Moodle), the instructor selects each activity and presentation factor from a menu list, effectively designing much of the interface for students. Fewer defaults are pre–set, forcing the instructor to think holistically about the class structure. Features such as chat, polls, and interactive lessons as options presented with the same weight as more traditional text–based resources. Thus there is less of an implication that presentation is key, and more of an implication that interactivity is important. In an Opt–In environment, the instructor makes choices about context on a macro level, and choices about features and tools on a micro level. This makes it possible to explore pedagogical options more freely" Again, perhaps a future strength of Sakai 3? Harriet Quoting Michael Korcuska mkorcuska@...: It's worth a read.... http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 -- Michael Korcuska Executive Director, Sakai Foundation mkorcuska@... phone: +1 510-859-4247 (google voice) skype: mkorcuska _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"
	Re: [DG: User Experience] User Experience] Interesting blog post on CMS user interfaces by Michael S Elledge :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message You may also want to look at the approach aTutor uses for creating course content which as I recall uses the syllabus as the starting point...promotes accessible content, too. :^) http://www.atutor.ca/atutor/demo.php Mike Plourde, Mathieu wrote: > > Funny that this thing has come to a full circle… Anyone remember > VirtualU? The default course was a long table organized as a list of > event with links to discussions and resources. > > I think the goal of that article was not to say that organizing your > content in a calendar was the best way to think, but that the defaults > are what most faculty will select. > > If Sakai 3’s default is to present multiple options in terms of > course/activity structure, and can support faculty in choosing an > appropriate one to start with, half the battle will be won. > > Best Regards, > > ================================= > > Mathieu Plourde, MBA > > Project Leader, LMS/Instructional Designer > > IT-Client Support & Services > > mathieu@... > > ================================= > > TOP LINKS: > > Technology Troubleshooting: http://www.udel.edu/help > > Sakai@UD Support and Training: http://www.udel.edu/sakai/training > > ================================= > > From: sakai-ux-bounces@... > [mailto:sakai-ux-bounces@...] On Behalf Of > Jacques Raynauld > Sent: Tuesday, November 03, 2009 8:51 AM > To: Sakai UX > Cc: Michael Korcuska; pedagogy@... Learning > Subject: Re: User Experience] Interesting blog post on CMS user > interfaces > > I also agree. It is a very interesting article. I have always been > struck by the Moodle first page template that naturally leads to a > week or theme interpretation by users. I think it is one of the > important factor that explains Moodle popularity. This is the kind of > need we wanted to adress in Sakai/Open Syllabus ... but in a more > semantic way than Moodle. > > Jacques Raynauld > HEC Montréal > > -------- Message original -------- > Sujet : Re: [DG: User Experience] Interesting blog post on CMS user > interfaces > De : harriet@... <mailto:harriet@...> > Pour : Michael Korcuska <mkorcuska@...> > <mailto:mkorcuska@...> > Copie à : "pedagogy@... Learning" > <mailto:pedagogy@...> > <pedagogy@...> > <mailto:pedagogy@...>, Sakai UX > <sakai-ux@...> > <mailto:sakai-ux@...> > Date : 2009-11-03 04:58 > > Very interesting - thanks Michael! > > There were a couple of paras that struck me particularly as relating to the > possibilities for the new Sakai 3: > > "The buttons link to pages that simply provide a place to upload a document, > which is exactly what most instructors do: upload word–processed files of their > classroom materials. They are encouraged to “plug in” their content under the > appropriate category instead of envisioning a translation of their individual > pedagogical style into an online environment. Blackboard “tends to encourage a > linear pathway through the content” [3], and its default is to support easy > uploading and text entry to achieve that goal. > The construction of the course syllabus is a familiar beginning point for most > instructors, yet few CMSs consider this. It would be natural and useful for > novice instructors to see a blank schedule into which they could create each > week’s or unit’s activities, rather than a selection of pre–set buttons or > links. Most professors think in terms of the semester, and how their > pedagogical goals can be achieved within the context of time, rather than > space. Some think in terms of topics they want to cover. Blackboard/WebCT’s > default organization accepts neither of these approaches in its initial > interface. It forces the instructor to think in terms of content types instead, > breaking the natural structure of the semester, or of a list of topics. Again, > we know that the setup can be customized with relative ease, by going to the > Control Panel and selecting Manage Course Menu, then using Modify buttons. You > could change all the course menu buttons into “Week 1”, “Week 2”, or organize > by topic instead of content type. But few professors try that, or they assume > that they can’t do it. Blackboard can be highly intimidating to learn, and may > “seriously hinder” choices the faculty member makes while using the tool [4]. > Faculty are led by the interface of a CMS not only because they do not > immediately see an alternative, but because the familiar signposts (the > Syllabus button) imply a single way of completing the task (upload a document). > Only the Moodle system provides a default setup that looks like a calendar-style > syllabus ..." > > I'd agree very strongly with this statement about pedagogies, and the initial > presentation of potential course structures, rather than tools, to the > lecturer, seems to be something that Sakai 3 has the potential to support > > > "Although it is an oversimplification, it is useful to separate course > management systems into two types: Opt–In and Opt–Out. In an Opt–Out system > (such as Blackboard) all the features are available by default and must be > excluded to avoid confusing students. Opt–Out systems are most likely to > overwhelm Web novices, because they present an array of tools, and the tendency > is to reduce cognitive load by using the defaults. In an Opt–In system (such as > Moodle), the instructor selects each activity and presentation factor from a > menu list, effectively designing much of the interface for students. Fewer > defaults are pre–set, forcing the instructor to think holistically about the > class structure. Features such as chat, polls, and interactive lessons as > options presented with the same weight as more traditional text–based > resources. Thus there is less of an implication that presentation is key, and > more of an implication that interactivity is important. In an Opt–In > environment, the instructor makes choices about context on a macro level, and > choices about features and tools on a micro level. This makes it possible to > explore pedagogical options more freely" > > Again, perhaps a future strength of Sakai 3? > > Harriet > > > > Quoting Michael Korcuska <mkorcuska@...> <mailto:mkorcuska@...>: > > > > It's worth a read.... > > > > > > > > http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 > > > > > -- > > Michael Korcuska > > Executive Director, Sakai Foundation > > mkorcuska@... <mailto:mkorcuska@...> > > phone: +1 510-859-4247 (google voice) > > skype: mkorcuska > > > > > > > > > > _______________________________________________ > > sakai-ux mailing list > > sakai-ux@... <mailto:sakai-ux@...> > > http://collab.sakaiproject.org/mailman/listinfo/sakai-ux > > > > TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... <mailto:sakai-ux-unsubscribe@...> > > with a subject of "unsubscribe" > > > > > > > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > _______________________________________________ > sakai-ux mailing list > sakai-ux@... <mailto:sakai-ux@...> > http://collab.sakaiproject.org/mailman/listinfo/sakai-ux > > TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... <mailto:sakai-ux-unsubscribe@...> with a subject of "unsubscribe" > > > > ------------------------------------------------------------------------ > > _______________________________________________ > sakai-ux mailing list > sakai-ux@... > http://collab.sakaiproject.org/mailman/listinfo/sakai-ux > > TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"
	Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces by Daphnedmdp6 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Yes, thanks for sharing Michael. Mathieu's post makes me wonder if we have a good understanding of the multiple types of course/activity structures we need to support in Sakai 3? It seems Moodle handles the syllabus/time-based and topic-based structures which make sense. Are there others? Understanding these will be key to creating the right context, cues, flows to help faculty build there course space in ways that match their mental models and then represent the course in ways that make sense to students. -Daphne On Nov 3, 2009, at 6:21 AM, Plourde, Mathieu wrote: Funny that this thing has come to a full circle… Anyone remember VirtualU? The default course was a long table organized as a list of event with links to discussions and resources. I think the goal of that article was not to say that organizing your content in a calendar was the best way to think, but that the defaults are what most faculty will select. If Sakai 3’s default is to present multiple options in terms of course/activity structure, and can support faculty in choosing an appropriate one to start with, half the battle will be won. Best Regards, ================================= Mathieu Plourde, MBA Project Leader, LMS/Instructional Designer IT-Client Support & Services mathieu@... ================================= TOP LINKS: Technology Troubleshooting: http://www.udel.edu/help Sakai@UD Support and Training: http://www.udel.edu/sakai/training ================================= From: sakai-ux-bounces@... [sakai-ux-bounces@...] On Behalf Of Jacques Raynauld Sent: Tuesday, November 03, 2009 8:51 AM To: Sakai UX Cc: Michael Korcuska; pedagogy@... Learning Subject: Re: User Experience] Interesting blog post on CMS user interfaces I also agree. It is a very interesting article. I have always been struck by the Moodle first page template that naturally leads to a week or theme interpretation by users. I think it is one of the important factor that explains Moodle popularity. This is the kind of need we wanted to adress in Sakai/Open Syllabus ... but in a more semantic way than Moodle. Jacques Raynauld HEC Montréal -------- Message original -------- Sujet : Re: [DG: User Experience] Interesting blog post on CMS user interfaces De : harriet@... Pour : Michael Korcuska mkorcuska@... Copie à : pedagogy@... pedagogy@..., Sakai UX sakai-ux@... Date : 2009-11-03 04:58 Very interesting - thanks Michael! There were a couple of paras that struck me particularly as relating to the possibilities for the new Sakai 3: "The buttons link to pages that simply provide a place to upload a document, which is exactly what most instructors do: upload word–processed files of their classroom materials. They are encouraged to “plug in” their content under the appropriate category instead of envisioning a translation of their individual pedagogical style into an online environment. Blackboard “tends to encourage a linear pathway through the content” [3], and its default is to support easy uploading and text entry to achieve that goal. The construction of the course syllabus is a familiar beginning point for most instructors, yet few CMSs consider this. It would be natural and useful for novice instructors to see a blank schedule into which they could create each week’s or unit’s activities, rather than a selection of pre–set buttons or links. Most professors think in terms of the semester, and how their pedagogical goals can be achieved within the context of time, rather than space. Some think in terms of topics they want to cover. Blackboard/WebCT’s default organization accepts neither of these approaches in its initial interface. It forces the instructor to think in terms of content types instead, breaking the natural structure of the semester, or of a list of topics. Again, we know that the setup can be customized with relative ease, by going to the Control Panel and selecting Manage Course Menu, then using Modify buttons. You could change all the course menu buttons into “Week 1”, “Week 2”, or organize by topic instead of content type. But few professors try that, or they assume that they can’t do it. Blackboard can be highly intimidating to learn, and may “seriously hinder” choices the faculty member makes while using the tool [4]. Faculty are led by the interface of a CMS not only because they do not immediately see an alternative, but because the familiar signposts (the Syllabus button) imply a single way of completing the task (upload a document). Only the Moodle system provides a default setup that looks like a calendar-style syllabus ..." I'd agree very strongly with this statement about pedagogies, and the initial presentation of potential course structures, rather than tools, to the lecturer, seems to be something that Sakai 3 has the potential to support "Although it is an oversimplification, it is useful to separate course management systems into two types: Opt–In and Opt–Out. In an Opt–Out system (such as Blackboard) all the features are available by default and must be excluded to avoid confusing students. Opt–Out systems are most likely to overwhelm Web novices, because they present an array of tools, and the tendency is to reduce cognitive load by using the defaults. In an Opt–In system (such as Moodle), the instructor selects each activity and presentation factor from a menu list, effectively designing much of the interface for students. Fewer defaults are pre–set, forcing the instructor to think holistically about the class structure. Features such as chat, polls, and interactive lessons as options presented with the same weight as more traditional text–based resources. Thus there is less of an implication that presentation is key, and more of an implication that interactivity is important. In an Opt–In environment, the instructor makes choices about context on a macro level, and choices about features and tools on a micro level. This makes it possible to explore pedagogical options more freely" Again, perhaps a future strength of Sakai 3? Harriet Quoting Michael Korcuska mkorcuska@...: It's worth a read.... http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 -- Michael Korcuska Executive Director, Sakai Foundation mkorcuska@... phone: +1 510-859-4247 (google voice) skype: mkorcuska _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" _______________________________________________ pedagogy mailing list pedagogy@... http://collab.sakaiproject.org/mailman/listinfo/pedagogy TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... with a subject of "unsubscribe" Daphne Ogle Senior Interaction Designer University of California, Berkeley Educational Technology Services daphne@... cell (925)348-4372 _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"
	Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces by Michael Feldstein-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Moodle provides a number of different structures. The time/topic structure is the default and by far the most popular (and the most polished), but it's not the only one. It might make sense for some folks to spend some time looking at what they've done. - m On 11/3/2009 1:16 PM, Daphne Ogle wrote: Yes, thanks for sharing Michael. Mathieu's post makes me wonder if we have a good understanding of the multiple types of course/activity structures we need to support in Sakai 3? It seems Moodle handles the syllabus/time-based and topic-based structures which make sense. Are there others? Understanding these will be key to creating the right context, cues, flows to help faculty build there course space in ways that match their mental models and then represent the course in ways that make sense to students. -Daphne On Nov 3, 2009, at 6:21 AM, Plourde, Mathieu wrote: Funny that this thing has come to a full circle… Anyone remember VirtualU? The default course was a long table organized as a list of event with links to discussions and resources. I think the goal of that article was not to say that organizing your content in a calendar was the best way to think, but that the defaults are what most faculty will select. If Sakai 3’s default is to present multiple options in terms of course/activity structure, and can support faculty in choosing an appropriate one to start with, half the battle will be won. Best Regards, ================================= Mathieu Plourde, MBA Project Leader, LMS/Instructional Designer IT-Client Support & Services mathieu@... ================================= TOP LINKS: Technology Troubleshooting: http://www.udel.edu/help Sakai@UD Support and Training: http://www.udel.edu/sakai/training ================================= From: sakai-ux-bounces@... [sakai-ux-bounces@...] On Behalf Of Jacques Raynauld Sent: Tuesday, November 03, 2009 8:51 AM To: Sakai UX Cc: Michael Korcuska; pedagogy@... Learning Subject: Re: User Experience] Interesting blog post on CMS user interfaces I also agree. It is a very interesting article. I have always been struck by the Moodle first page template that naturally leads to a week or theme interpretation by users. I think it is one of the important factor that explains Moodle popularity. This is the kind of need we wanted to adress in Sakai/Open Syllabus ... but in a more semantic way than Moodle. Jacques Raynauld HEC Montréal -------- Message original -------- Sujet : Re: [DG: User Experience] Interesting blog post on CMS user interfaces De : harriet@... Pour : Michael Korcuska mkorcuska@... Copie à : pedagogy@... pedagogy@..., Sakai UX sakai-ux@... Date : 2009-11-03 04:58 Very interesting - thanks Michael! There were a couple of paras that struck me particularly as relating to the possibilities for the new Sakai 3: "The buttons link to pages that simply provide a place to upload a document, which is exactly what most instructors do: upload word–processed files of their classroom materials. They are encouraged to “plug in” their content under the appropriate category instead of envisioning a translation of their individual pedagogical style into an online environment. Blackboard “tends to encourage a linear pathway through the content” [3], and its default is to support easy uploading and text entry to achieve that goal. The construction of the course syllabus is a familiar beginning point for most instructors, yet few CMSs consider this. It would be natural and useful for novice instructors to see a blank schedule into which they could create each week’s or unit’s activities, rather than a selection of pre–set buttons or links. Most professors think in terms of the semester, and how their pedagogical goals can be achieved within the context of time, rather than space. Some think in terms of topics they want to cover. Blackboard/WebCT’s default organization accepts neither of these approaches in its initial interface. It forces the instructor to think in terms of content types instead, breaking the natural structure of the semester, or of a list of topics. Again, we know that the setup can be customized with relative ease, by going to the Control Panel and selecting Manage Course Menu, then using Modify buttons. You could change all the course menu buttons into “Week 1”, “Week 2”, or organize by topic instead of content type. But few professors try that, or they assume that they can’t do it. Blackboard can be highly intimidating to learn, and may “seriously hinder” choices the faculty member makes while using the tool [4]. Faculty are led by the interface of a CMS not only because they do not immediately see an alternative, but because the familiar signposts (the Syllabus button) imply a single way of completing the task (upload a document). Only the Moodle system provides a default setup that looks like a calendar-style syllabus ..." I'd agree very strongly with this statement about pedagogies, and the initial presentation of potential course structures, rather than tools, to the lecturer, seems to be something that Sakai 3 has the potential to support "Although it is an oversimplification, it is useful to separate course management systems into two types: Opt–In and Opt–Out. In an Opt–Out system (such as Blackboard) all the features are available by default and must be excluded to avoid confusing students. Opt–Out systems are most likely to overwhelm Web novices, because they present an array of tools, and the tendency is to reduce cognitive load by using the defaults. In an Opt–In system (such as Moodle), the instructor selects each activity and presentation factor from a menu list, effectively designing much of the interface for students. Fewer defaults are pre–set, forcing the instructor to think holistically about the class structure. Features such as chat, polls, and interactive lessons as options presented with the same weight as more traditional text–based resources. Thus there is less of an implication that presentation is key, and more of an implication that interactivity is important. In an Opt–In environment, the instructor makes choices about context on a macro level, and choices about features and tools on a micro level. This makes it possible to explore pedagogical options more freely" Again, perhaps a future strength of Sakai 3? Harriet Quoting Michael Korcuska mkorcuska@...: It's worth a read.... http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 -- Michael Korcuska Executive Director, Sakai Foundation mkorcuska@... phone: +1 510-859-4247 (google voice) skype: mkorcuska _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" _______________________________________________ pedagogy mailing list pedagogy@... http://collab.sakaiproject.org/mailman/listinfo/pedagogy TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... with a subject of "unsubscribe" Daphne Ogle Senior Interaction Designer University of California, Berkeley Educational Technology Services daphne@... cell (925)348-4372 _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" -- Michael Feldstein \| Principal Product Manager \| +1.818.817.2925 Oracle Academic Enterprise Solutions Group 23A Glendale Road, Glendale, MA 01229 _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"
	Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces by Michael S Elledge :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message You may also want to look at the approach aTutor uses for creating course content which as I recall uses the syllabus as the starting point...promotes accessible content, too. :^) http://www.atutor.ca/atutor/demo.php Mike michael feldstein wrote: > Moodle provides a number of different structures. The time/topic > structure is the default and by far the most popular (and the most > polished), but it's not the only one. It might make sense for some > folks to spend some time looking at what they've done. > > - m > > > On 11/3/2009 1:16 PM, Daphne Ogle wrote: >> Yes, thanks for sharing Michael. Mathieu's post makes me wonder if >> we have a good understanding of the multiple types of course/activity >> structures we need to support in Sakai 3? It seems Moodle handles >> the syllabus/time-based and topic-based structures which make sense. >> Are there others? Understanding these will be key to creating the >> right context, cues, flows to help faculty build there course space >> in ways that match their mental models and then represent the course >> in ways that make sense to students. >> >> -Daphne >> >> On Nov 3, 2009, at 6:21 AM, Plourde, Mathieu wrote: >> >>> Funny that this thing has come to a full circle… Anyone remember >>> VirtualU? The default course was a long table organized as a list of >>> event with links to discussions and resources. >>> >>> I think the goal of that article was not to say that organizing your >>> content in a calendar was the best way to think, but that the >>> defaults are what most faculty will select. >>> >>> If Sakai 3’s default is to present multiple options in terms of >>> course/activity structure, and can support faculty in choosing an >>> appropriate one to start with, half the battle will be won. >>> >>> Best Regards, >>> >>> ================================= >>> >>> Mathieu Plourde, MBA >>> Project Leader, LMS/Instructional Designer >>> IT-Client Support & Services >>> mathieu@... <mailto:mathieu@...> >>> >>> ================================= >>> >>> TOP LINKS: >>> >>> Technology Troubleshooting: http://www.udel.edu/help >>> Sakai@UD Support and Training: http://www.udel.edu/sakai/training >>> >>> ================================= >>> >>> From: sakai-ux-bounces@... >>> <mailto:sakai-ux-bounces@...> [mailto:sakai-ux-bounces@...] On >>> Behalf Of Jacques Raynauld >>> Sent: Tuesday, November 03, 2009 8:51 AM >>> To: Sakai UX >>> Cc: Michael Korcuska; pedagogy@... >>> <mailto:pedagogy@...> Learning >>> Subject: Re: User Experience] Interesting blog post on CMS user >>> interfaces >>> >>> I also agree. It is a very interesting article. I have always been >>> struck by the Moodle first page template that naturally leads to a >>> week or theme interpretation by users. I think it is one of the >>> important factor that explains Moodle popularity. This is the kind >>> of need we wanted to adress in Sakai/Open Syllabus ... but in a more >>> semantic way than Moodle. >>> >>> Jacques Raynauld >>> HEC Montréal >>> >>> -------- Message original -------- >>> Sujet : Re: [DG: User Experience] Interesting blog post on CMS >>> user interfaces >>> De : harriet@... <mailto:harriet@...> >>> Pour : Michael Korcuska <mkorcuska@...> >>> <mailto:mkorcuska@...> >>> Copie à : "pedagogy@... Learning" >>> <mailto:pedagogy@...> <pedagogy@...> >>> <mailto:pedagogy@...>, Sakai >>> UX <sakai-ux@...> >>> <mailto:sakai-ux@...> >>> Date : 2009-11-03 04:58 >>> >>> Very interesting - thanks Michael! >>> >>> There were a couple of paras that struck me particularly as relating to the >>> possibilities for the new Sakai 3: >>> >>> "The buttons link to pages that simply provide a place to upload a document, >>> which is exactly what most instructors do: upload word–processed files of their >>> classroom materials. They are encouraged to “plug in” their content under the >>> appropriate category instead of envisioning a translation of their individual >>> pedagogical style into an online environment. Blackboard “tends to encourage a >>> linear pathway through the content” [3], and its default is to support easy >>> uploading and text entry to achieve that goal. >>> The construction of the course syllabus is a familiar beginning point for most >>> instructors, yet few CMSs consider this. It would be natural and useful for >>> novice instructors to see a blank schedule into which they could create each >>> week’s or unit’s activities, rather than a selection of pre–set buttons or >>> links. Most professors think in terms of the semester, and how their >>> pedagogical goals can be achieved within the context of time, rather than >>> space. Some think in terms of topics they want to cover. Blackboard/WebCT’s >>> default organization accepts neither of these approaches in its initial >>> interface. It forces the instructor to think in terms of content types instead, >>> breaking the natural structure of the semester, or of a list of topics. Again, >>> we know that the setup can be customized with relative ease, by going to the >>> Control Panel and selecting Manage Course Menu, then using Modify buttons. You >>> could change all the course menu buttons into “Week 1”, “Week 2”, or organize >>> by topic instead of content type. But few professors try that, or they assume >>> that they can’t do it. Blackboard can be highly intimidating to learn, and may >>> “seriously hinder” choices the faculty member makes while using the tool [4]. >>> Faculty are led by the interface of a CMS not only because they do not >>> immediately see an alternative, but because the familiar signposts (the >>> Syllabus button) imply a single way of completing the task (upload a document). >>> Only the Moodle system provides a default setup that looks like a calendar-style >>> syllabus ..." >>> >>> I'd agree very strongly with this statement about pedagogies, and the initial >>> presentation of potential course structures, rather than tools, to the >>> lecturer, seems to be something that Sakai 3 has the potential to support >>> >>> >>> "Although it is an oversimplification, it is useful to separate course >>> management systems into two types: Opt–In and Opt–Out. In an Opt–Out system >>> (such as Blackboard) all the features are available by default and must be >>> excluded to avoid confusing students. Opt–Out systems are most likely to >>> overwhelm Web novices, because they present an array of tools, and the tendency >>> is to reduce cognitive load by using the defaults. In an Opt–In system (such as >>> Moodle), the instructor selects each activity and presentation factor from a >>> menu list, effectively designing much of the interface for students. Fewer >>> defaults are pre–set, forcing the instructor to think holistically about the >>> class structure. Features such as chat, polls, and interactive lessons as >>> options presented with the same weight as more traditional text–based >>> resources. Thus there is less of an implication that presentation is key, and >>> more of an implication that interactivity is important. In an Opt–In >>> environment, the instructor makes choices about context on a macro level, and >>> choices about features and tools on a micro level. This makes it possible to >>> explore pedagogical options more freely" >>> >>> Again, perhaps a future strength of Sakai 3? >>> >>> Harriet >>> >>> >>> >>> Quoting Michael Korcuska <mkorcuska@...> <mailto:mkorcuska@...>: >>> >>> >>> >>> It's worth a read.... >>> >>> >>> >>> >>> >>> >>> >>> http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 >>> >>> >>> >>> >>> -- >>> >>> Michael Korcuska >>> >>> Executive Director, Sakai Foundation >>> >>> mkorcuska@... <mailto:mkorcuska@...> >>> >>> phone: +1 510-859-4247 (google voice) >>> >>> skype: mkorcuska >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> >>> sakai-ux mailing list >>> >>> sakai-ux@... <mailto:sakai-ux@...> >>> >>> http://collab.sakaiproject.org/mailman/listinfo/sakai-ux >>> >>> >>> >>> TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... <mailto:sakai-ux-unsubscribe@...> >>> >>> with a subject of "unsubscribe" >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> ---------------------------------------------------------------- >>> This message was sent using IMP, the Internet Messaging Program. >>> >>> _______________________________________________ >>> sakai-ux mailing list >>> sakai-ux@... <mailto:sakai-ux@...> >>> http://collab.sakaiproject.org/mailman/listinfo/sakai-ux >>> >>> TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... <mailto:sakai-ux-unsubscribe@...> with a subject of "unsubscribe" >>> >>> >>> >>> _______________________________________________ >>> pedagogy mailing list >>> pedagogy@... >>> <mailto:pedagogy@...> >>> http://collab.sakaiproject.org/mailman/listinfo/pedagogy >>> >>> TO UNSUBSCRIBE: send email >>> to pedagogy-unsubscribe@... >>> <mailto:pedagogy-unsubscribe@...> with a subject >>> of "unsubscribe" >> >> Daphne Ogle >> Senior Interaction Designer >> University of California, Berkeley >> Educational Technology Services >> daphne@... <mailto:daphne@...> >> cell (925)348-4372 >> >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> sakai-ux mailing list >> sakai-ux@... >> http://collab.sakaiproject.org/mailman/listinfo/sakai-ux >> >> TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" > > -- > > > Oracle <http://www.oracle.com> > Michael Feldstein \| Principal Product Manager \| +1.818.817.2925 > Oracle Academic Enterprise Solutions Group > 23A Glendale Road, Glendale, MA 01229 > ------------------------------------------------------------------------ > > _______________________________________________ > pedagogy mailing list > pedagogy@... > http://collab.sakaiproject.org/mailman/listinfo/pedagogy > > TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... with a subject of "unsubscribe" _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"
	Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces by Lynn Ward :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. I think we can probably identify the most common models. But, the system should be flexible enough to allow innovators to push the envelope. I think approach that Angel uses is quite interesting—it’s basically modeled on a file system. The instructor can create folders and place any number of objects inside each folder. Object types include discussion forums, html pages, assessments, wiki, survey, blog, SCORM package, another folder, etc. Every object can be associated with specific learning objectives and outcomes. And, in advanced mode, the instructor can create agents that enable conditional release, branching, and other types of triggers and relationships among objects. The file system metaphor allows the instructor to organize the course in whatever way she pleases: by time, topic, project, group, or even by tool type if you happen to like the Sakai 2.x way of doing things. I’m not necessarily advocating a file system as the visual metaphor. But an object-oriented approach in which there are containers (things that hold other things) and learning objects (think content and activities—not necessarily traditional notion of LO’s) that can be easily organized and grouped in a way that visually represents the instructor’s mental model of the course could be very powerful. Lynn ========================== Lynn Ward, Principal Systems Analyst, Academic and Faculty Services University Information Technology Services Indiana University-Purdue University Indianapolis Information Technology and Communications Complex (IT 218R) 535 West Michigan Street, Indianapolis, IN 46202 Phone: 317-278-5713 E-mail: leward@... From: pedagogy-bounces@... [mailto:pedagogy-bounces@...] On Behalf Of Daphne Ogle Sent: Tuesday, November 03, 2009 1:17 PM To: Plourde, Mathieu Cc: Michael Korcuska; pedagogy@... Learning; Sakai UX Subject: Re: [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces Yes, thanks for sharing Michael. Mathieu's post makes me wonder if we have a good understanding of the multiple types of course/activity structures we need to support in Sakai 3? It seems Moodle handles the syllabus/time-based and topic-based structures which make sense. Are there others? Understanding these will be key to creating the right context, cues, flows to help faculty build there course space in ways that match their mental models and then represent the course in ways that make sense to students. -Daphne On Nov 3, 2009, at 6:21 AM, Plourde, Mathieu wrote: Funny that this thing has come to a full circle… Anyone remember VirtualU? The default course was a long table organized as a list of event with links to discussions and resources. I think the goal of that article was not to say that organizing your content in a calendar was the best way to think, but that the defaults are what most faculty will select. If Sakai 3’s default is to present multiple options in terms of course/activity structure, and can support faculty in choosing an appropriate one to start with, half the battle will be won. Best Regards, ================================= Mathieu Plourde, MBA Project Leader, LMS/Instructional Designer IT-Client Support & Services mathieu@... ================================= TOP LINKS: Technology Troubleshooting: http://www.udel.edu/help Sakai@UD Support and Training: http://www.udel.edu/sakai/training ================================= From: sakai-ux-bounces@... [sakai-ux-bounces@...] On Behalf Of Jacques Raynauld Sent: Tuesday, November 03, 2009 8:51 AM To: Sakai UX Cc: Michael Korcuska; pedagogy@... Learning Subject: Re: User Experience] Interesting blog post on CMS user interfaces I also agree. It is a very interesting article. I have always been struck by the Moodle first page template that naturally leads to a week or theme interpretation by users. I think it is one of the important factor that explains Moodle popularity. This is the kind of need we wanted to adress in Sakai/Open Syllabus ... but in a more semantic way than Moodle. Jacques Raynauld HEC Montréal -------- Message original -------- Sujet : Re: [DG: User Experience] Interesting blog post on CMS user interfaces De : harriet@... Pour : Michael Korcuska mkorcuska@... Copie à : pedagogy@... pedagogy@..., Sakai UX sakai-ux@... Date : 2009-11-03 04:58 Very interesting - thanks Michael! There were a couple of paras that struck me particularly as relating to the possibilities for the new Sakai 3: "The buttons link to pages that simply provide a place to upload a document, which is exactly what most instructors do: upload word–processed files of their classroom materials. They are encouraged to “plug in” their content under the appropriate category instead of envisioning a translation of their individual pedagogical style into an online environment. Blackboard “tends to encourage a linear pathway through the content” [3], and its default is to support easy uploading and text entry to achieve that goal. The construction of the course syllabus is a familiar beginning point for most instructors, yet few CMSs consider this. It would be natural and useful for novice instructors to see a blank schedule into which they could create each week’s or unit’s activities, rather than a selection of pre–set buttons or links. Most professors think in terms of the semester, and how their pedagogical goals can be achieved within the context of time, rather than space. Some think in terms of topics they want to cover. Blackboard/WebCT’s default organization accepts neither of these approaches in its initial interface. It forces the instructor to think in terms of content types instead, breaking the natural structure of the semester, or of a list of topics. Again, we know that the setup can be customized with relative ease, by going to the Control Panel and selecting Manage Course Menu, then using Modify buttons. You could change all the course menu buttons into “Week 1”, “Week 2”, or organize by topic instead of content type. But few professors try that, or they assume that they can’t do it. Blackboard can be highly intimidating to learn, and may “seriously hinder” choices the faculty member makes while using the tool [4]. Faculty are led by the interface of a CMS not only because they do not immediately see an alternative, but because the familiar signposts (the Syllabus button) imply a single way of completing the task (upload a document). Only the Moodle system provides a default setup that looks like a calendar-style syllabus ..." I'd agree very strongly with this statement about pedagogies, and the initial presentation of potential course structures, rather than tools, to the lecturer, seems to be something that Sakai 3 has the potential to support "Although it is an oversimplification, it is useful to separate course management systems into two types: Opt–In and Opt–Out. In an Opt–Out system (such as Blackboard) all the features are available by default and must be excluded to avoid confusing students. Opt–Out systems are most likely to overwhelm Web novices, because they present an array of tools, and the tendency is to reduce cognitive load by using the defaults. In an Opt–In system (such as Moodle), the instructor selects each activity and presentation factor from a menu list, effectively designing much of the interface for students. Fewer defaults are pre–set, forcing the instructor to think holistically about the class structure. Features such as chat, polls, and interactive lessons as options presented with the same weight as more traditional text–based resources. Thus there is less of an implication that presentation is key, and more of an implication that interactivity is important. In an Opt–In environment, the instructor makes choices about context on a macro level, and choices about features and tools on a micro level. This makes it possible to explore pedagogical options more freely" Again, perhaps a future strength of Sakai 3? Harriet Quoting Michael Korcuska mkorcuska@...: It's worth a read.... http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 -- Michael Korcuska Executive Director, Sakai Foundation mkorcuska@... phone: +1 510-859-4247 (google voice) skype: mkorcuska _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" _______________________________________________ pedagogy mailing list pedagogy@... http://collab.sakaiproject.org/mailman/listinfo/pedagogy TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... with a subject of "unsubscribe" Daphne Ogle Senior Interaction Designer University of California, Berkeley Educational Technology Services daphne@... cell (925)348-4372 _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"
	Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces by Plourde, Mathieu :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. Hi Lynn, It strikes me that the way Angel works is very close to our current Resources tool. If everything in Sakai could have a URL/URI (every quiz question, poll, quiz, gradebook item, discussion thread, blog, etc.) and that conditional release was enabled, this model could be deployed in Sakai. Just a thought. Best Regards, ================================= Mathieu Plourde, MBA Project Leader, LMS/Instructional Designer IT-Client Support & Services mathieu@... ================================= TOP LINKS: Technology Troubleshooting: http://www.udel.edu/help Sakai@UD Support and Training: http://www.udel.edu/sakai/training ================================= From: Ward, Lynn E. [mailto:leward@...] Sent: Wednesday, November 04, 2009 7:23 AM To: 'Daphne Ogle'; Plourde, Mathieu Cc: 'Michael Korcuska'; 'pedagogy@... Learning'; 'Sakai UX' Subject: RE: [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces I think we can probably identify the most common models. But, the system should be flexible enough to allow innovators to push the envelope. I think approach that Angel uses is quite interesting—it’s basically modeled on a file system. The instructor can create folders and place any number of objects inside each folder. Object types include discussion forums, html pages, assessments, wiki, survey, blog, SCORM package, another folder, etc. Every object can be associated with specific learning objectives and outcomes. And, in advanced mode, the instructor can create agents that enable conditional release, branching, and other types of triggers and relationships among objects. The file system metaphor allows the instructor to organize the course in whatever way she pleases: by time, topic, project, group, or even by tool type if you happen to like the Sakai 2.x way of doing things. I’m not necessarily advocating a file system as the visual metaphor. But an object-oriented approach in which there are containers (things that hold other things) and learning objects (think content and activities—not necessarily traditional notion of LO’s) that can be easily organized and grouped in a way that visually represents the instructor’s mental model of the course could be very powerful. Lynn ========================== Lynn Ward, Principal Systems Analyst, Academic and Faculty Services University Information Technology Services Indiana University-Purdue University Indianapolis Information Technology and Communications Complex (IT 218R) 535 West Michigan Street, Indianapolis, IN 46202 Phone: 317-278-5713 E-mail: leward@... From: pedagogy-bounces@... [mailto:pedagogy-bounces@...] On Behalf Of Daphne Ogle Sent: Tuesday, November 03, 2009 1:17 PM To: Plourde, Mathieu Cc: Michael Korcuska; pedagogy@... Learning; Sakai UX Subject: Re: [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces Yes, thanks for sharing Michael. Mathieu's post makes me wonder if we have a good understanding of the multiple types of course/activity structures we need to support in Sakai 3? It seems Moodle handles the syllabus/time-based and topic-based structures which make sense. Are there others? Understanding these will be key to creating the right context, cues, flows to help faculty build there course space in ways that match their mental models and then represent the course in ways that make sense to students. -Daphne On Nov 3, 2009, at 6:21 AM, Plourde, Mathieu wrote: Funny that this thing has come to a full circle… Anyone remember VirtualU? The default course was a long table organized as a list of event with links to discussions and resources. I think the goal of that article was not to say that organizing your content in a calendar was the best way to think, but that the defaults are what most faculty will select. If Sakai 3’s default is to present multiple options in terms of course/activity structure, and can support faculty in choosing an appropriate one to start with, half the battle will be won. Best Regards, ================================= Mathieu Plourde, MBA Project Leader, LMS/Instructional Designer IT-Client Support & Services mathieu@... ================================= TOP LINKS: Technology Troubleshooting: http://www.udel.edu/help Sakai@UD Support and Training: http://www.udel.edu/sakai/training ================================= From: sakai-ux-bounces@... [sakai-ux-bounces@...] On Behalf Of Jacques Raynauld Sent: Tuesday, November 03, 2009 8:51 AM To: Sakai UX Cc: Michael Korcuska; pedagogy@... Learning Subject: Re: User Experience] Interesting blog post on CMS user interfaces I also agree. It is a very interesting article. I have always been struck by the Moodle first page template that naturally leads to a week or theme interpretation by users. I think it is one of the important factor that explains Moodle popularity. This is the kind of need we wanted to adress in Sakai/Open Syllabus ... but in a more semantic way than Moodle. Jacques Raynauld HEC Montréal -------- Message original -------- Sujet : Re: [DG: User Experience] Interesting blog post on CMS user interfaces De : harriet@... Pour : Michael Korcuska mkorcuska@... Copie à : pedagogy@... pedagogy@..., Sakai UX sakai-ux@... Date : 2009-11-03 04:58 Very interesting - thanks Michael! There were a couple of paras that struck me particularly as relating to the possibilities for the new Sakai 3: "The buttons link to pages that simply provide a place to upload a document, which is exactly what most instructors do: upload word–processed files of their classroom materials. They are encouraged to “plug in” their content under the appropriate category instead of envisioning a translation of their individual pedagogical style into an online environment. Blackboard “tends to encourage a linear pathway through the content” [3], and its default is to support easy uploading and text entry to achieve that goal. The construction of the course syllabus is a familiar beginning point for most instructors, yet few CMSs consider this. It would be natural and useful for novice instructors to see a blank schedule into which they could create each week’s or unit’s activities, rather than a selection of pre–set buttons or links. Most professors think in terms of the semester, and how their pedagogical goals can be achieved within the context of time, rather than space. Some think in terms of topics they want to cover. Blackboard/WebCT’s default organization accepts neither of these approaches in its initial interface. It forces the instructor to think in terms of content types instead, breaking the natural structure of the semester, or of a list of topics. Again, we know that the setup can be customized with relative ease, by going to the Control Panel and selecting Manage Course Menu, then using Modify buttons. You could change all the course menu buttons into “Week 1”, “Week 2”, or organize by topic instead of content type. But few professors try that, or they assume that they can’t do it. Blackboard can be highly intimidating to learn, and may “seriously hinder” choices the faculty member makes while using the tool [4]. Faculty are led by the interface of a CMS not only because they do not immediately see an alternative, but because the familiar signposts (the Syllabus button) imply a single way of completing the task (upload a document). Only the Moodle system provides a default setup that looks like a calendar-style syllabus ..." I'd agree very strongly with this statement about pedagogies, and the initial presentation of potential course structures, rather than tools, to the lecturer, seems to be something that Sakai 3 has the potential to support "Although it is an oversimplification, it is useful to separate course management systems into two types: Opt–In and Opt–Out. In an Opt–Out system (such as Blackboard) all the features are available by default and must be excluded to avoid confusing students. Opt–Out systems are most likely to overwhelm Web novices, because they present an array of tools, and the tendency is to reduce cognitive load by using the defaults. In an Opt–In system (such as Moodle), the instructor selects each activity and presentation factor from a menu list, effectively designing much of the interface for students. Fewer defaults are pre–set, forcing the instructor to think holistically about the class structure. Features such as chat, polls, and interactive lessons as options presented with the same weight as more traditional text–based resources. Thus there is less of an implication that presentation is key, and more of an implication that interactivity is important. In an Opt–In environment, the instructor makes choices about context on a macro level, and choices about features and tools on a micro level. This makes it possible to explore pedagogical options more freely" Again, perhaps a future strength of Sakai 3? Harriet Quoting Michael Korcuska mkorcuska@...: It's worth a read.... http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 -- Michael Korcuska Executive Director, Sakai Foundation mkorcuska@... phone: +1 510-859-4247 (google voice) skype: mkorcuska _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" _______________________________________________ pedagogy mailing list pedagogy@... http://collab.sakaiproject.org/mailman/listinfo/pedagogy TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... with a subject of "unsubscribe" Daphne Ogle Senior Interaction Designer University of California, Berkeley Educational Technology Services daphne@... cell (925)348-4372 _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"
	Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces by Luke Fernandez-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message The container metaphor Lynn describes below makes sense; one sees it used in Moodle and Blackboard as well. The caution here is that if one is putting content and activities into "weekly containers" one also needs to present the content and activities in ways that allow the student to easily discern what needs to be completed for the entire semester. The weekly container approach, so often used by instructors in Moodle and Blackboard, doesn't provide this aggregate view as well as it could. Luke On Wed, Nov 4, 2009 at 5:22 AM, Lynn E. Ward <leward@...> wrote: > I think we can probably identify the most common models. But, the system > should be flexible enough to allow innovators to push the envelope. I think > approach that Angel uses is quite interesting—it’s basically modeled on a > file system. The instructor can create folders and place any number of > objects inside each folder. Object types include discussion forums, html > pages, assessments, wiki, survey, blog, SCORM package, another folder, etc. > Every object can be associated with specific learning objectives and > outcomes. And, in advanced mode, the instructor can create agents that > enable conditional release, branching, and other types of triggers and > relationships among objects. > > > > The file system metaphor allows the instructor to organize the course in > whatever way she pleases: by time, topic, project, group, or even by tool > type if you happen to like the Sakai 2.x way of doing things. I’m not > necessarily advocating a file system as the visual metaphor. But an > object-oriented approach in which there are containers (things that hold > other things) and learning objects (think content and activities—not > necessarily traditional notion of LO’s) that can be easily organized and > grouped in a way that visually represents the instructor’s mental model of > the course could be very powerful. > > > > Lynn > > > > > > ========================== > > Lynn Ward, Principal Systems Analyst, Academic and Faculty Services > > University Information Technology Services > Indiana University-Purdue University Indianapolis > Information Technology and Communications Complex (IT 218R) > 535 West Michigan Street, Indianapolis, IN 46202 > Phone: 317-278-5713 E-mail: leward@... > > > > From: pedagogy-bounces@... > [mailto:pedagogy-bounces@...] On Behalf Of Daphne Ogle > Sent: Tuesday, November 03, 2009 1:17 PM > To: Plourde, Mathieu > Cc: Michael Korcuska; pedagogy@... Learning; Sakai UX > Subject: Re: [DG: Teaching & Learning] User Experience] Interesting blog > post on CMS user interfaces > > > > Yes, thanks for sharing Michael. Mathieu's post makes me wonder if we have > a good understanding of the multiple types of course/activity structures we > need to support in Sakai 3? It seems Moodle handles the syllabus/time-based > and topic-based structures which make sense. Are there others? > Understanding these will be key to creating the right context, cues, flows > to help faculty build there course space in ways that match their mental > models and then represent the course in ways that make sense to students. > > > > -Daphne > > > > On Nov 3, 2009, at 6:21 AM, Plourde, Mathieu wrote: > > Funny that this thing has come to a full circle… Anyone remember VirtualU? > The default course was a long table organized as a list of event with links > to discussions and resources. > > > > I think the goal of that article was not to say that organizing your content > in a calendar was the best way to think, but that the defaults are what most > faculty will select. > > > > If Sakai 3’s default is to present multiple options in terms of > course/activity structure, and can support faculty in choosing an > appropriate one to start with, half the battle will be won. > > > > Best Regards, > > > > ================================= > > > > Mathieu Plourde, MBA > > Project Leader, LMS/Instructional Designer > > IT-Client Support & Services > > mathieu@... > > > > ================================= > > > > TOP LINKS: > > > > Technology Troubleshooting: http://www.udel.edu/help > > Sakai@UD Support and Training: http://www.udel.edu/sakai/training > > > > ================================= > > > > From: sakai-ux-bounces@... [mailto:sakai-ux-bounces@...] On > Behalf Of Jacques Raynauld > Sent: Tuesday, November 03, 2009 8:51 AM > To: Sakai UX > Cc: Michael Korcuska; pedagogy@... Learning > Subject: Re: User Experience] Interesting blog post on CMS user interfaces > > > > I also agree. It is a very interesting article. I have always been struck > by the Moodle first page template that naturally leads to a week or theme > interpretation by users. I think it is one of the important factor that > explains Moodle popularity. This is the kind of need we wanted to adress in > Sakai/Open Syllabus ... but in a more semantic way than Moodle. > > Jacques Raynauld > HEC Montréal > > -------- Message original -------- > Sujet : Re: [DG: User Experience] Interesting blog post on CMS user > interfaces > De : harriet@... > Pour : Michael Korcuska <mkorcuska@...> > Copie à : "pedagogy@... > Learning" <pedagogy@...>, Sakai > UX <sakai-ux@...> > Date : 2009-11-03 04:58 > > > Very interesting - thanks Michael! > > > > There were a couple of paras that struck me particularly as relating to the > > possibilities for the new Sakai 3: > > > > "The buttons link to pages that simply provide a place to upload a document, > > which is exactly what most instructors do: upload word–processed files of > their > > classroom materials. They are encouraged to “plug in” their content under > the > > appropriate category instead of envisioning a translation of their > individual > > pedagogical style into an online environment. Blackboard “tends to encourage > a > > linear pathway through the content” [3], and its default is to support easy > > uploading and text entry to achieve that goal. > > The construction of the course syllabus is a familiar beginning point for > most > > instructors, yet few CMSs consider this. It would be natural and useful for > > novice instructors to see a blank schedule into which they could create each > > week’s or unit’s activities, rather than a selection of pre–set buttons or > > links. Most professors think in terms of the semester, and how their > > pedagogical goals can be achieved within the context of time, rather than > > space. Some think in terms of topics they want to cover. Blackboard/WebCT’s > > default organization accepts neither of these approaches in its initial > > interface. It forces the instructor to think in terms of content types > instead, > > breaking the natural structure of the semester, or of a list of topics. > Again, > > we know that the setup can be customized with relative ease, by going to the > > Control Panel and selecting Manage Course Menu, then using Modify buttons. > You > > could change all the course menu buttons into “Week 1”, “Week 2”, or > organize > > by topic instead of content type. But few professors try that, or they > assume > > that they can’t do it. Blackboard can be highly intimidating to learn, and > may > > “seriously hinder” choices the faculty member makes while using the tool > [4]. > > Faculty are led by the interface of a CMS not only because they do not > > immediately see an alternative, but because the familiar signposts (the > > Syllabus button) imply a single way of completing the task (upload a > document). > > Only the Moodle system provides a default setup that looks like a > calendar-style > > syllabus ..." > > > > I'd agree very strongly with this statement about pedagogies, and the > initial > > presentation of potential course structures, rather than tools, to the > > lecturer, seems to be something that Sakai 3 has the potential to support > > > > > > "Although it is an oversimplification, it is useful to separate course > > management systems into two types: Opt–In and Opt–Out. In an Opt–Out system > > (such as Blackboard) all the features are available by default and must be > > excluded to avoid confusing students. Opt–Out systems are most likely to > > overwhelm Web novices, because they present an array of tools, and the > tendency > > is to reduce cognitive load by using the defaults. In an Opt–In system (such > as > > Moodle), the instructor selects each activity and presentation factor from a > > menu list, effectively designing much of the interface for students. Fewer > > defaults are pre–set, forcing the instructor to think holistically about the > > class structure. Features such as chat, polls, and interactive lessons as > > options presented with the same weight as more traditional text–based > > resources. Thus there is less of an implication that presentation is key, > and > > more of an implication that interactivity is important. In an Opt–In > > environment, the instructor makes choices about context on a macro level, > and > > choices about features and tools on a micro level. This makes it possible to > > explore pedagogical options more freely" > > > > Again, perhaps a future strength of Sakai 3? > > > > Harriet > > > > > > > > Quoting Michael Korcuska <mkorcuska@...>: > > > > > > It's worth a read.... > > > > > > > > http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 > > > > > > -- > > Michael Korcuska > > Executive Director, Sakai Foundation > > mkorcuska@... > > phone: +1 510-859-4247 (google voice) > > skype: mkorcuska > > > > > > > > > > _______________________________________________ > > sakai-ux mailing list > > sakai-ux@... > > http://collab.sakaiproject.org/mailman/listinfo/sakai-ux > > > > TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... > > with a subject of "unsubscribe" > > > > > > > > > > > > > > ---------------------------------------------------------------- > > This message was sent using IMP, the Internet Messaging Program. > > > > _______________________________________________ > > sakai-ux mailing list > > sakai-ux@... > > http://collab.sakaiproject.org/mailman/listinfo/sakai-ux > > > > TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... > with a subject of "unsubscribe" > > > > > > > > _______________________________________________ > pedagogy mailing list > pedagogy@... > http://collab.sakaiproject.org/mailman/listinfo/pedagogy > > TO UNSUBSCRIBE: send email > to pedagogy-unsubscribe@... with a subject of > "unsubscribe" > > > > Daphne Ogle > > Senior Interaction Designer > > University of California, Berkeley > > Educational Technology Services > > daphne@... > > cell (925)348-4372 > > > > > > > > _______________________________________________ > pedagogy mailing list > pedagogy@... > http://collab.sakaiproject.org/mailman/listinfo/pedagogy > > TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... > with a subject of "unsubscribe" > _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"
	Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces by Lynn Ward :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message I completely agree that other views and features are needed to allow instructors and students to effectively manage their time and tasks. I think of the container as a sort of workspace, the purpose of which is defined by the instructor. So, for example, regardless of how the instructor organizes the content in the course (by week, topic, tool, etc), there might also be a container or space, hidden from students, where the instructor and TAs can communicate and share resources with one another-- the instructor might even include a blog there and encourage each TA to blog about their teaching experiences. Or in a fully online course, there might be a virtual lounge to foster community building where students can get to know one another and discuss issues outside the scope of the course. The value of this approach is that it doesn't require us to identify and document every possible organizational framework up front on order to support it. Lynn ========================== Lynn Ward, Principal Systems Analyst, Academic and Faculty Services University Information Technology Services Indiana University-Purdue University Indianapolis Information Technology and Communications Complex (IT 218R) 535 West Michigan Street, Indianapolis, IN 46202 Phone: 317-278-5713 E-mail: leward@... -----Original Message----- From: Luke Fernandez [mailto:luke.fernandez@...] Sent: Wednesday, November 04, 2009 10:15 AM To: Ward, Lynn E. Cc: Daphne Ogle; Mathieu' 'Plourde; pedagogy@... Learning; Sakai UX; Michael Korcuska Subject: Re: [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces The container metaphor Lynn describes below makes sense; one sees it used in Moodle and Blackboard as well. The caution here is that if one is putting content and activities into "weekly containers" one also needs to present the content and activities in ways that allow the student to easily discern what needs to be completed for the entire semester. The weekly container approach, so often used by instructors in Moodle and Blackboard, doesn't provide this aggregate view as well as it could. Luke On Wed, Nov 4, 2009 at 5:22 AM, Lynn E. Ward <leward@...> wrote: > I think we can probably identify the most common models. But, the system > should be flexible enough to allow innovators to push the envelope. I think > approach that Angel uses is quite interesting-it's basically modeled on a > file system. The instructor can create folders and place any number of > objects inside each folder. Object types include discussion forums, html > pages, assessments, wiki, survey, blog, SCORM package, another folder, etc. > Every object can be associated with specific learning objectives and > outcomes. And, in advanced mode, the instructor can create agents that > enable conditional release, branching, and other types of triggers and > relationships among objects. > > > > The file system metaphor allows the instructor to organize the course in > whatever way she pleases: by time, topic, project, group, or even by tool > type if you happen to like the Sakai 2.x way of doing things. I'm not > necessarily advocating a file system as the visual metaphor. But an > object-oriented approach in which there are containers (things that hold > other things) and learning objects (think content and activities-not > necessarily traditional notion of LO's) that can be easily organized and > grouped in a way that visually represents the instructor's mental model of > the course could be very powerful. > > > > Lynn > > > > > > ========================== > > Lynn Ward, Principal Systems Analyst, Academic and Faculty Services > > University Information Technology Services > Indiana University-Purdue University Indianapolis > Information Technology and Communications Complex (IT 218R) > 535 West Michigan Street, Indianapolis, IN 46202 > Phone: 317-278-5713 E-mail: leward@... > > > > From: pedagogy-bounces@... > [mailto:pedagogy-bounces@...] On Behalf Of Daphne Ogle > Sent: Tuesday, November 03, 2009 1:17 PM > To: Plourde, Mathieu > Cc: Michael Korcuska; pedagogy@... Learning; Sakai UX > Subject: Re: [DG: Teaching & Learning] User Experience] Interesting blog > post on CMS user interfaces > > > > Yes, thanks for sharing Michael. Mathieu's post makes me wonder if we have > a good understanding of the multiple types of course/activity structures we > need to support in Sakai 3? It seems Moodle handles the syllabus/time-based > and topic-based structures which make sense. Are there others? > Understanding these will be key to creating the right context, cues, flows > to help faculty build there course space in ways that match their mental > models and then represent the course in ways that make sense to students. > > > > -Daphne > > > > On Nov 3, 2009, at 6:21 AM, Plourde, Mathieu wrote: > > Funny that this thing has come to a full circle. Anyone remember VirtualU? > The default course was a long table organized as a list of event with links > to discussions and resources. > > > > I think the goal of that article was not to say that organizing your content > in a calendar was the best way to think, but that the defaults are what most > faculty will select. > > > > If Sakai 3's default is to present multiple options in terms of > course/activity structure, and can support faculty in choosing an > appropriate one to start with, half the battle will be won. > > > > Best Regards, > > > > ================================= > > > > Mathieu Plourde, MBA > > Project Leader, LMS/Instructional Designer > > IT-Client Support & Services > > mathieu@... > > > > ================================= > > > > TOP LINKS: > > > > Technology Troubleshooting: http://www.udel.edu/help > > Sakai@UD Support and Training: http://www.udel.edu/sakai/training > > > > ================================= > > > > From: sakai-ux-bounces@... [mailto:sakai-ux-bounces@...] On > Behalf Of Jacques Raynauld > Sent: Tuesday, November 03, 2009 8:51 AM > To: Sakai UX > Cc: Michael Korcuska; pedagogy@... Learning > Subject: Re: User Experience] Interesting blog post on CMS user interfaces > > > > I also agree. It is a very interesting article. I have always been struck > by the Moodle first page template that naturally leads to a week or theme > interpretation by users. I think it is one of the important factor that > explains Moodle popularity. This is the kind of need we wanted to adress in > Sakai/Open Syllabus ... but in a more semantic way than Moodle. > > Jacques Raynauld > HEC Montréal > > -------- Message original -------- > Sujet : Re: [DG: User Experience] Interesting blog post on CMS user > interfaces > De : harriet@... > Pour : Michael Korcuska <mkorcuska@...> > Copie à : "pedagogy@... > Learning" <pedagogy@...>, Sakai > UX <sakai-ux@...> > Date : 2009-11-03 04:58 > > > Very interesting - thanks Michael! > > > > There were a couple of paras that struck me particularly as relating to the > > possibilities for the new Sakai 3: > > > > "The buttons link to pages that simply provide a place to upload a document, > > which is exactly what most instructors do: upload word-processed files of > their > > classroom materials. They are encouraged to "plug in" their content under > the > > appropriate category instead of envisioning a translation of their > individual > > pedagogical style into an online environment. Blackboard "tends to encourage > a > > linear pathway through the content" [3], and its default is to support easy > > uploading and text entry to achieve that goal. > > The construction of the course syllabus is a familiar beginning point for > most > > instructors, yet few CMSs consider this. It would be natural and useful for > > novice instructors to see a blank schedule into which they could create each > > week's or unit's activities, rather than a selection of pre-set buttons or > > links. Most professors think in terms of the semester, and how their > > pedagogical goals can be achieved within the context of time, rather than > > space. Some think in terms of topics they want to cover. Blackboard/WebCT's > > default organization accepts neither of these approaches in its initial > > interface. It forces the instructor to think in terms of content types > instead, > > breaking the natural structure of the semester, or of a list of topics. > Again, > > we know that the setup can be customized with relative ease, by going to the > > Control Panel and selecting Manage Course Menu, then using Modify buttons. > You > > could change all the course menu buttons into "Week 1", "Week 2", or > organize > > by topic instead of content type. But few professors try that, or they > assume > > that they can't do it. Blackboard can be highly intimidating to learn, and > may > > "seriously hinder" choices the faculty member makes while using the tool > [4]. > > Faculty are led by the interface of a CMS not only because they do not > > immediately see an alternative, but because the familiar signposts (the > > Syllabus button) imply a single way of completing the task (upload a > document). > > Only the Moodle system provides a default setup that looks like a > calendar-style > > syllabus ..." > > > > I'd agree very strongly with this statement about pedagogies, and the > initial > > presentation of potential course structures, rather than tools, to the > > lecturer, seems to be something that Sakai 3 has the potential to support > > > > > > "Although it is an oversimplification, it is useful to separate course > > management systems into two types: Opt-In and Opt-Out. In an Opt-Out system > > (such as Blackboard) all the features are available by default and must be > > excluded to avoid confusing students. Opt-Out systems are most likely to > > overwhelm Web novices, because they present an array of tools, and the > tendency > > is to reduce cognitive load by using the defaults. In an Opt-In system (such > as > > Moodle), the instructor selects each activity and presentation factor from a > > menu list, effectively designing much of the interface for students. Fewer > > defaults are pre-set, forcing the instructor to think holistically about the > > class structure. Features such as chat, polls, and interactive lessons as > > options presented with the same weight as more traditional text-based > > resources. Thus there is less of an implication that presentation is key, > and > > more of an implication that interactivity is important. In an Opt-In > > environment, the instructor makes choices about context on a macro level, > and > > choices about features and tools on a micro level. This makes it possible to > > explore pedagogical options more freely" > > > > Again, perhaps a future strength of Sakai 3? > > > > Harriet > > > > > > > > Quoting Michael Korcuska <mkorcuska@...>: > > > > > > It's worth a read.... > > > > > > > > http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 > > > > > > -- > > Michael Korcuska > > Executive Director, Sakai Foundation > > mkorcuska@... > > phone: +1 510-859-4247 (google voice) > > skype: mkorcuska > > > > > > > > > > _______________________________________________ > > sakai-ux mailing list > > sakai-ux@... > > http://collab.sakaiproject.org/mailman/listinfo/sakai-ux > > > > TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... > > with a subject of "unsubscribe" > > > > > > > > > > > > > > ---------------------------------------------------------------- > > This message was sent using IMP, the Internet Messaging Program. > > > > _______________________________________________ > > sakai-ux mailing list > > sakai-ux@... > > http://collab.sakaiproject.org/mailman/listinfo/sakai-ux > > > > TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... > with a subject of "unsubscribe" > > > > > > > > _______________________________________________ > pedagogy mailing list > pedagogy@... > http://collab.sakaiproject.org/mailman/listinfo/pedagogy > > TO UNSUBSCRIBE: send email > to pedagogy-unsubscribe@... with a subject of > "unsubscribe" > > > > Daphne Ogle > > Senior Interaction Designer > > University of California, Berkeley > > Educational Technology Services > > daphne@... > > cell (925)348-4372 > > > > > > > > _______________________________________________ > pedagogy mailing list > pedagogy@... > http://collab.sakaiproject.org/mailman/listinfo/pedagogy > > TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... > with a subject of "unsubscribe" > _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"
	Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces by jrnorman :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message I _think_ we have this one covered, at least in theory, in Sakai 3. The web page is our container, a common tag applied to a set of pages can be a higher-level container. I think it is interesting to speculate (as we have many times) whether a folder metaphor is more familiar/intuitive than a web page metaphor, but if we call one set/ type of tags "folder names" we could render a folder metaphor too. Sitemap is like a folder 'explorer' Not to say the problem is solved, but I don't think the option is excluded. John On 4 Nov 2009, at 12:22, Ward, Lynn E. wrote: > I think we can probably identify the most common models. But, the > system should be flexible enough to allow innovators to push the > envelope. I think approach that Angel uses is quite interesting— > it’s basically modeled on a file system. The instructor can create > folders and place any number of objects inside each folder. Object > types include discussion forums, html pages, assessments, wiki, > survey, blog, SCORM package, another folder, etc. Every object can > be associated with specific learning objectives and outcomes. And, > in advanced mode, the instructor can create agents that enable > conditional release, branching, and other types of triggers and > relationships among objects. > > The file system metaphor allows the instructor to organize the > course in whatever way she pleases: by time, topic, project, group, > or even by tool type if you happen to like the Sakai 2.x way of > doing things. I’m not necessarily advocating a file system as the > visual metaphor. But an object-oriented approach in which there are > containers (things that hold other things) and learning objects > (think content and activities—not necessarily traditional notion of > LO’s) that can be easily organized and grouped in a way that > visually represents the instructor’s mental model of the course > could be very powerful. > > Lynn > > > ========================== > Lynn Ward, Principal Systems Analyst, Academic and Faculty Services > University Information Technology Services > Indiana University-Purdue University Indianapolis > Information Technology and Communications Complex (IT 218R) > 535 West Michigan Street, Indianapolis, IN 46202 > Phone: 317-278-5713 E-mail: leward@... > > From: pedagogy-bounces@... [mailto:pedagogy- > bounces@...] On Behalf Of Daphne Ogle > Sent: Tuesday, November 03, 2009 1:17 PM > To: Plourde, Mathieu > Cc: Michael Korcuska; pedagogy@... Learning; > Sakai UX > Subject: Re: [DG: Teaching & Learning] User Experience] Interesting > blog post on CMS user interfaces > > Yes, thanks for sharing Michael. Mathieu's post makes me wonder if > we have a good understanding of the multiple types of course/ > activity structures we need to support in Sakai 3? It seems Moodle > handles the syllabus/time-based and topic-based structures which > make sense. Are there others? Understanding these will be key to > creating the right context, cues, flows to help faculty build there > course space in ways that match their mental models and then > represent the course in ways that make sense to students. > > -Daphne > > On Nov 3, 2009, at 6:21 AM, Plourde, Mathieu wrote: > > > Funny that this thing has come to a full circle… Anyone remember > VirtualU? The default course was a long table organized as a list of > event with links to discussions and resources. > > I think the goal of that article was not to say that organizing your > content in a calendar was the best way to think, but that the > defaults are what most faculty will select. > > If Sakai 3’s default is to present multiple options in terms of > course/activity structure, and can support faculty in choosing an > appropriate one to start with, half the battle will be won. > > Best Regards, > > ================================= > > Mathieu Plourde, MBA > Project Leader, LMS/Instructional Designer > IT-Client Support & Services > mathieu@... > > ================================= > > TOP LINKS: > > Technology Troubleshooting: http://www.udel.edu/help > Sakai@UD Support and Training: http://www.udel.edu/sakai/training > > ================================= > > From: sakai-ux-bounces@... [mailto:sakai-ux- > bounces@...] On Behalf Of Jacques Raynauld > Sent: Tuesday, November 03, 2009 8:51 AM > To: Sakai UX > Cc: Michael Korcuska; pedagogy@... Learning > Subject: Re: User Experience] Interesting blog post on CMS user > interfaces > > I also agree. It is a very interesting article. I have always been > struck by the Moodle first page template that naturally leads to a > week or theme interpretation by users. I think it is one of the > important factor that explains Moodle popularity. This is the kind > of need we wanted to adress in Sakai/Open Syllabus ... but in a more > semantic way than Moodle. > > Jacques Raynauld > HEC Montréal > > -------- Message original -------- > Sujet : Re: [DG: User Experience] Interesting blog post on CMS > user interfaces > De : harriet@... > Pour : Michael Korcuska <mkorcuska@...> > Copie à : "pedagogy@... Learning" <pedagogy@... > >, Sakai UX <sakai-ux@...> > Date : 2009-11-03 04:58 > > > Very interesting - thanks Michael! > > There were a couple of paras that struck me particularly as relating > to the > possibilities for the new Sakai 3: > > "The buttons link to pages that simply provide a place to upload a > document, > which is exactly what most instructors do: upload word–processed > files of their > classroom materials. They are encouraged to “plug in” their content > under the > appropriate category instead of envisioning a translation of their > individual > pedagogical style into an online environment. Blackboard “tends to > encourage a > linear pathway through the content” [3], and its default is to > support easy > uploading and text entry to achieve that goal. > The construction of the course syllabus is a familiar beginning > point for most > instructors, yet few CMSs consider this. It would be natural and > useful for > novice instructors to see a blank schedule into which they could > create each > week’s or unit’s activities, rather than a selection of pre–set > buttons or > links. Most professors think in terms of the semester, and how their > pedagogical goals can be achieved within the context of time, rather > than > space. Some think in terms of topics they want to cover. Blackboard/ > WebCT’s > default organization accepts neither of these approaches in its > initial > interface. It forces the instructor to think in terms of content > types instead, > breaking the natural structure of the semester, or of a list of > topics. Again, > we know that the setup can be customized with relative ease, by > going to the > Control Panel and selecting Manage Course Menu, then using Modify > buttons. You > could change all the course menu buttons into “Week 1”, “Week 2”, or > organize > by topic instead of content type. But few professors try that, or > they assume > that they can’t do it. Blackboard can be highly intimidating to > learn, and may > “seriously hinder” choices the faculty member makes while using the > tool [4]. > Faculty are led by the interface of a CMS not only because they do not > immediately see an alternative, but because the familiar signposts > (the > Syllabus button) imply a single way of completing the task (upload a > document). > Only the Moodle system provides a default setup that looks like a > calendar-style > syllabus ..." > > I'd agree very strongly with this statement about pedagogies, and > the initial > presentation of potential course structures, rather than tools, to the > lecturer, seems to be something that Sakai 3 has the potential to > support > > > "Although it is an oversimplification, it is useful to separate course > management systems into two types: Opt–In and Opt–Out. In an Opt–Out > system > (such as Blackboard) all the features are available by default and > must be > excluded to avoid confusing students. Opt–Out systems are most > likely to > overwhelm Web novices, because they present an array of tools, and > the tendency > is to reduce cognitive load by using the defaults. In an Opt–In > system (such as > Moodle), the instructor selects each activity and presentation > factor from a > menu list, effectively designing much of the interface for students. > Fewer > defaults are pre–set, forcing the instructor to think holistically > about the > class structure. Features such as chat, polls, and interactive > lessons as > options presented with the same weight as more traditional text–based > resources. Thus there is less of an implication that presentation is > key, and > more of an implication that interactivity is important. In an Opt–In > environment, the instructor makes choices about context on a macro > level, and > choices about features and tools on a micro level. This makes it > possible to > explore pedagogical options more freely" > > Again, perhaps a future strength of Sakai 3? > > Harriet > > > > Quoting Michael Korcuska <mkorcuska@...>: > > > It's worth a read.... > > > > http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 > > > -- > Michael Korcuska > Executive Director, Sakai Foundation > mkorcuska@... > phone: +1 510-859-4247 (google voice) > skype: mkorcuska > > > > > _______________________________________________ > sakai-ux mailing list > sakai-ux@... > http://collab.sakaiproject.org/mailman/listinfo/sakai-ux > > TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... > with a subject of "unsubscribe" > > > > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > _______________________________________________ > sakai-ux mailing list > sakai-ux@... > http://collab.sakaiproject.org/mailman/listinfo/sakai-ux > > TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... > with a subject of "unsubscribe" > > > > _______________________________________________ > pedagogy mailing list > pedagogy@... > http://collab.sakaiproject.org/mailman/listinfo/pedagogy > > TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... > with a subject of "unsubscribe" > > Daphne Ogle > Senior Interaction Designer > University of California, Berkeley > Educational Technology Services > daphne@... > cell (925)348-4372 > > > > > > _______________________________________________ > pedagogy mailing list > pedagogy@... > http://collab.sakaiproject.org/mailman/listinfo/pedagogy > > TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... > with a subject of "unsubscribe" _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"
	Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces by Michael Korcuska-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Just catching up on this from a busy Educause but I would say this is definitely squarely part of my vision for Sakai 3. I think the raw capabilities are being built into Sakai 3 to really make a substantial leap forward on being able to provide a variety of metaphors to instructors (and to students and researchers). What we will need to do, once those raw capabilities are ready, is use them to construct different metaphors/models for site organization and store those as reusable templates. There will lots of interesting debates about which are best and how many there should be (a usability question), etcetera, but I look forward to those interactions in the community--I'll know Sakai 3 has arrived. Michael On Nov 4, 2009, at 10:49, John Norman wrote: > I _think_ we have this one covered, at least in theory, in Sakai 3. > The web page is our container, a common tag applied to a set of pages > can be a higher-level container. I think it is interesting to > speculate (as we have many times) whether a folder metaphor is more > familiar/intuitive than a web page metaphor, but if we call one set/ > type of tags "folder names" we could render a folder metaphor too. > Sitemap is like a folder 'explorer' > > Not to say the problem is solved, but I don't think the option is > excluded. > > John > > On 4 Nov 2009, at 12:22, Ward, Lynn E. wrote: > >> I think we can probably identify the most common models. But, the >> system should be flexible enough to allow innovators to push the >> envelope. I think approach that Angel uses is quite interesting— >> it’s basically modeled on a file system. The instructor can create >> folders and place any number of objects inside each folder. Object >> types include discussion forums, html pages, assessments, wiki, >> survey, blog, SCORM package, another folder, etc. Every object can >> be associated with specific learning objectives and outcomes. And, >> in advanced mode, the instructor can create agents that enable >> conditional release, branching, and other types of triggers and >> relationships among objects. >> >> The file system metaphor allows the instructor to organize the >> course in whatever way she pleases: by time, topic, project, group, >> or even by tool type if you happen to like the Sakai 2.x way of >> doing things. I’m not necessarily advocating a file system as the >> visual metaphor. But an object-oriented approach in which there are >> containers (things that hold other things) and learning objects >> (think content and activities—not necessarily traditional notion of >> LO’s) that can be easily organized and grouped in a way that >> visually represents the instructor’s mental model of the course >> could be very powerful. >> >> Lynn >> >> >> ========================== >> Lynn Ward, Principal Systems Analyst, Academic and Faculty Services >> University Information Technology Services >> Indiana University-Purdue University Indianapolis >> Information Technology and Communications Complex (IT 218R) >> 535 West Michigan Street, Indianapolis, IN 46202 >> Phone: 317-278-5713 E-mail: leward@... >> >> From: pedagogy-bounces@... [mailto:pedagogy- >> bounces@...] On Behalf Of Daphne Ogle >> Sent: Tuesday, November 03, 2009 1:17 PM >> To: Plourde, Mathieu >> Cc: Michael Korcuska; pedagogy@... Learning; >> Sakai UX >> Subject: Re: [DG: Teaching & Learning] User Experience] Interesting >> blog post on CMS user interfaces >> >> Yes, thanks for sharing Michael. Mathieu's post makes me wonder if >> we have a good understanding of the multiple types of course/ >> activity structures we need to support in Sakai 3? It seems Moodle >> handles the syllabus/time-based and topic-based structures which >> make sense. Are there others? Understanding these will be key to >> creating the right context, cues, flows to help faculty build there >> course space in ways that match their mental models and then >> represent the course in ways that make sense to students. >> >> -Daphne >> >> On Nov 3, 2009, at 6:21 AM, Plourde, Mathieu wrote: >> >> >> Funny that this thing has come to a full circle… Anyone remember >> VirtualU? The default course was a long table organized as a list of >> event with links to discussions and resources. >> >> I think the goal of that article was not to say that organizing your >> content in a calendar was the best way to think, but that the >> defaults are what most faculty will select. >> >> If Sakai 3’s default is to present multiple options in terms of >> course/activity structure, and can support faculty in choosing an >> appropriate one to start with, half the battle will be won. >> >> Best Regards, >> >> ================================= >> >> Mathieu Plourde, MBA >> Project Leader, LMS/Instructional Designer >> IT-Client Support & Services >> mathieu@... >> >> ================================= >> >> TOP LINKS: >> >> Technology Troubleshooting: http://www.udel.edu/help >> Sakai@UD Support and Training: http://www.udel.edu/sakai/training >> >> ================================= >> >> From: sakai-ux-bounces@... [mailto:sakai-ux- >> bounces@...] On Behalf Of Jacques Raynauld >> Sent: Tuesday, November 03, 2009 8:51 AM >> To: Sakai UX >> Cc: Michael Korcuska; pedagogy@... Learning >> Subject: Re: User Experience] Interesting blog post on CMS user >> interfaces >> >> I also agree. It is a very interesting article. I have always been >> struck by the Moodle first page template that naturally leads to a >> week or theme interpretation by users. I think it is one of the >> important factor that explains Moodle popularity. This is the kind >> of need we wanted to adress in Sakai/Open Syllabus ... but in a more >> semantic way than Moodle. >> >> Jacques Raynauld >> HEC Montréal >> >> -------- Message original -------- >> Sujet : Re: [DG: User Experience] Interesting blog post on CMS >> user interfaces >> De : harriet@... >> Pour : Michael Korcuska <mkorcuska@...> >> Copie à : "pedagogy@... Learning" <pedagogy@... >>> , Sakai UX <sakai-ux@...> >> Date : 2009-11-03 04:58 >> >> >> Very interesting - thanks Michael! >> >> There were a couple of paras that struck me particularly as relating >> to the >> possibilities for the new Sakai 3: >> >> "The buttons link to pages that simply provide a place to upload a >> document, >> which is exactly what most instructors do: upload word–processed >> files of their >> classroom materials. They are encouraged to “plug in” their content >> under the >> appropriate category instead of envisioning a translation of their >> individual >> pedagogical style into an online environment. Blackboard “tends to >> encourage a >> linear pathway through the content” [3], and its default is to >> support easy >> uploading and text entry to achieve that goal. >> The construction of the course syllabus is a familiar beginning >> point for most >> instructors, yet few CMSs consider this. It would be natural and >> useful for >> novice instructors to see a blank schedule into which they could >> create each >> week’s or unit’s activities, rather than a selection of pre–set >> buttons or >> links. Most professors think in terms of the semester, and how their >> pedagogical goals can be achieved within the context of time, rather >> than >> space. Some think in terms of topics they want to cover. Blackboard/ >> WebCT’s >> default organization accepts neither of these approaches in its >> initial >> interface. It forces the instructor to think in terms of content >> types instead, >> breaking the natural structure of the semester, or of a list of >> topics. Again, >> we know that the setup can be customized with relative ease, by >> going to the >> Control Panel and selecting Manage Course Menu, then using Modify >> buttons. You >> could change all the course menu buttons into “Week 1”, “Week 2”, or >> organize >> by topic instead of content type. But few professors try that, or >> they assume >> that they can’t do it. Blackboard can be highly intimidating to >> learn, and may >> “seriously hinder” choices the faculty member makes while using the >> tool [4]. >> Faculty are led by the interface of a CMS not only because they do >> not >> immediately see an alternative, but because the familiar signposts >> (the >> Syllabus button) imply a single way of completing the task (upload a >> document). >> Only the Moodle system provides a default setup that looks like a >> calendar-style >> syllabus ..." >> >> I'd agree very strongly with this statement about pedagogies, and >> the initial >> presentation of potential course structures, rather than tools, to >> the >> lecturer, seems to be something that Sakai 3 has the potential to >> support >> >> >> "Although it is an oversimplification, it is useful to separate >> course >> management systems into two types: Opt–In and Opt–Out. In an Opt–Out >> system >> (such as Blackboard) all the features are available by default and >> must be >> excluded to avoid confusing students. Opt–Out systems are most >> likely to >> overwhelm Web novices, because they present an array of tools, and >> the tendency >> is to reduce cognitive load by using the defaults. In an Opt–In >> system (such as >> Moodle), the instructor selects each activity and presentation >> factor from a >> menu list, effectively designing much of the interface for students. >> Fewer >> defaults are pre–set, forcing the instructor to think holistically >> about the >> class structure. Features such as chat, polls, and interactive >> lessons as >> options presented with the same weight as more traditional text–based >> resources. Thus there is less of an implication that presentation is >> key, and >> more of an implication that interactivity is important. In an Opt–In >> environment, the instructor makes choices about context on a macro >> level, and >> choices about features and tools on a micro level. This makes it >> possible to >> explore pedagogical options more freely" >> >> Again, perhaps a future strength of Sakai 3? >> >> Harriet >> >> >> >> Quoting Michael Korcuska <mkorcuska@...>: >> >> >> It's worth a read.... >> >> >> >> http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 >> >> >> -- >> Michael Korcuska >> Executive Director, Sakai Foundation >> mkorcuska@... >> phone: +1 510-859-4247 (google voice) >> skype: mkorcuska >> >> >> >> >> _______________________________________________ >> sakai-ux mailing list >> sakai-ux@... >> http://collab.sakaiproject.org/mailman/listinfo/sakai-ux >> >> TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... >> with a subject of "unsubscribe" >> >> >> >> >> >> >> ---------------------------------------------------------------- >> This message was sent using IMP, the Internet Messaging Program. >> >> _______________________________________________ >> sakai-ux mailing list >> sakai-ux@... >> http://collab.sakaiproject.org/mailman/listinfo/sakai-ux >> >> TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... >> with a subject of "unsubscribe" >> >> >> >> _______________________________________________ >> pedagogy mailing list >> pedagogy@... >> http://collab.sakaiproject.org/mailman/listinfo/pedagogy >> >> TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... >> with a subject of "unsubscribe" >> >> Daphne Ogle >> Senior Interaction Designer >> University of California, Berkeley >> Educational Technology Services >> daphne@... >> cell (925)348-4372 >> >> >> >> >> >> _______________________________________________ >> pedagogy mailing list >> pedagogy@... >> http://collab.sakaiproject.org/mailman/listinfo/pedagogy >> >> TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... >> with a subject of "unsubscribe" > > _______________________________________________ > pedagogy mailing list > pedagogy@... > http://collab.sakaiproject.org/mailman/listinfo/pedagogy > > TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... > with a subject of "unsubscribe" -- Michael Korcuska Executive Director, Sakai Foundation mkorcuska@... phone: +1 510-859-4247 (google voice) skype: mkorcuska _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"
	Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces by Joanna Proulx :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces Hi Daphne et al, As we focus, here at MIT, on the mental models of faculty with respect to their online teaching, there’s a constant effort to remember that any LMS has to be a two-way street. The students are partners in this process and their mental models matter equally to those of the faculty. If they are ignored, true learning is likely to be hampered if not arrested entirely. I have two examples to share by way of inveighling on behalf of the student perspective: http://tomprofblog.mit.edu/2009/10/13/974-online-learning-more-than-technical-savvy/ We posit that readiness for online learning has less to do with students’ knowledge of technology and digital dexterity and more to do with their knowledge of how to learn and their motivation to engage fully in the process. The teacher in the learner-centered class is a designer of learning opportunities, one who sets the stage and then steps aside while the students engage in knowledge constructing activities. http://news.slashdot.org/story/09/11/09/2347215/Attack-of-the-PowerPoint-Wielding-Professors Cheers, joanna :::::::::::::::::::::::::::::::::::::::::::::::::: Joanna Proulx : Team Lead Interaction Development Content & Collaboration Services .................................................. MIT : IS&T : ISDA : CCS : ID On 11/3/09 1:16 PM, "Daphne Ogle" <daphne@...> wrote: Yes, thanks for sharing Michael. Mathieu's post makes me wonder if we have a good understanding of the multiple types of course/activity structures we need to support in Sakai 3? It seems Moodle handles the syllabus/time-based and topic-based structures which make sense. Are there others? Understanding these will be key to creating the right context, cues, flows to help faculty build there course space in ways that match their mental models and then represent the course in ways that make sense to students. -Daphne On Nov 3, 2009, at 6:21 AM, Plourde, Mathieu wrote: Funny that this thing has come to a full circle… Anyone remember VirtualU? The default course was a long table organized as a list of event with links to discussions and resources. I think the goal of that article was not to say that organizing your content in a calendar was the best way to think, but that the defaults are what most faculty will select. If Sakai 3’s default is to present multiple options in terms of course/activity structure, and can support faculty in choosing an appropriate one to start with, half the battle will be won. Best Regards, ================================= Mathieu Plourde, MBA Project Leader, LMS/Instructional Designer IT-Client Support & Services mathieu@... ================================= TOP LINKS: Technology Troubleshooting: http://www.udel.edu/help Sakai@UD Support and Training: http://www.udel.edu/sakai/training ================================= From: sakai-ux-bounces@... [sakai-ux-bounces@...] On Behalf Of Jacques Raynauld Sent: Tuesday, November 03, 2009 8:51 AM To: Sakai UX Cc: Michael Korcuska; pedagogy@... Learning Subject: Re: User Experience] Interesting blog post on CMS user interfaces I also agree. It is a very interesting article. I have always been struck by the Moodle first page template that naturally leads to a week or theme interpretation by users. I think it is one of the important factor that explains Moodle popularity. This is the kind of need we wanted to adress in Sakai/Open Syllabus ... but in a more semantic way than Moodle. Jacques Raynauld HEC Montréal -------- Message original -------- Sujet : Re: [DG: User Experience] Interesting blog post on CMS user interfaces De : harriet@... Pour : Michael Korcuska <mkorcuska@...> <mkorcuska@...> Copie à : "pedagogy@... Learning" <pedagogy@...> <pedagogy@...> <pedagogy@...> , Sakai UX <sakai-ux@...> <sakai-ux@...> Date : 2009-11-03 04:58 Very interesting - thanks Michael! There were a couple of paras that struck me particularly as relating to the possibilities for the new Sakai 3: "The buttons link to pages that simply provide a place to upload a document, which is exactly what most instructors do: upload word–processed files of their classroom materials. They are encouraged to “plug in” their content under the appropriate category instead of envisioning a translation of their individual pedagogical style into an online environment. Blackboard “tends to encourage a linear pathway through the content” [3], and its default is to support easy uploading and text entry to achieve that goal. The construction of the course syllabus is a familiar beginning point for most instructors, yet few CMSs consider this. It would be natural and useful for novice instructors to see a blank schedule into which they could create each week’s or unit’s activities, rather than a selection of pre–set buttons or links. Most professors think in terms of the semester, and how their pedagogical goals can be achieved within the context of time, rather than space. Some think in terms of topics they want to cover. Blackboard/WebCT’s default organization accepts neither of these approaches in its initial interface. It forces the instructor to think in terms of content types instead, breaking the natural structure of the semester, or of a list of topics. Again, we know that the setup can be customized with relative ease, by going to the Control Panel and selecting Manage Course Menu, then using Modify buttons. You could change all the course menu buttons into “Week 1”, “Week 2”, or organize by topic instead of content type. But few professors try that, or they assume that they can’t do it. Blackboard can be highly intimidating to learn, and may “seriously hinder” choices the faculty member makes while using the tool [4]. Faculty are led by the interface of a CMS not only because they do not immediately see an alternative, but because the familiar signposts (the Syllabus button) imply a single way of completing the task (upload a document). Only the Moodle system provides a default setup that looks like a calendar-style syllabus ..." I'd agree very strongly with this statement about pedagogies, and the initial presentation of potential course structures, rather than tools, to the lecturer, seems to be something that Sakai 3 has the potential to support "Although it is an oversimplification, it is useful to separate course management systems into two types: Opt–In and Opt–Out. In an Opt–Out system (such as Blackboard) all the features are available by default and must be excluded to avoid confusing students. Opt–Out systems are most likely to overwhelm Web novices, because they present an array of tools, and the tendency is to reduce cognitive load by using the defaults. In an Opt–In system (such as Moodle), the instructor selects each activity and presentation factor from a menu list, effectively designing much of the interface for students. Fewer defaults are pre–set, forcing the instructor to think holistically about the class structure. Features such as chat, polls, and interactive lessons as options presented with the same weight as more traditional text–based resources. Thus there is less of an implication that presentation is key, and more of an implication that interactivity is important. In an Opt–In environment, the instructor makes choices about context on a macro level, and choices about features and tools on a micro level. This makes it possible to explore pedagogical options more freely" Again, perhaps a future strength of Sakai 3? Harriet Quoting Michael Korcuska <mkorcuska@...> <mkorcuska@...> : It's worth a read.... http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 -- Michael Korcuska Executive Director, Sakai Foundation mkorcuska@... phone: +1 510-859-4247 (google voice) skype: mkorcuska _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" _______________________________________________ pedagogy mailing list pedagogy@... http://collab.sakaiproject.org/mailman/listinfo/pedagogy TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... with a subject of "unsubscribe" Daphne Ogle Senior Interaction Designer University of California, Berkeley Educational Technology Services daphne@... cell (925)348-4372 _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"
	Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces by jrnorman :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Thanks for these links Joanna. I am curious to know more about the Tomorrow's Professor collaboration. It looks like a grass-roots thing, but it could have institutional support... Also, the second link took me to a very interesting student blog "Carolyn Blogs" (http://blog.carolynworks.com). Do you have any coordinated collection of such blogs? It might be interesting to collect them in a fashion similar to Planet Sakai. Best, John On 12 Nov 2009, at 22:39, Joanna Proulx wrote: > Hi Daphne et al, > > As we focus, here at MIT, on the mental models of faculty with respect to their online teaching, there’s a constant effort to remember that any LMS has to be a two-way street. The students are partners in this process and their mental models matter equally to those of the faculty. If they are ignored, true learning is likely to be hampered if not arrested entirely. I have two examples to share by way of inveighling on behalf of the student perspective: > > http://tomprofblog.mit.edu/2009/10/13/974-online-learning-more-than-technical-savvy/ > > We posit that readiness for online learning has less to do with students’ knowledge of technology and digital dexterity and more to do with their knowledge of how to learn and their motivation to engage fully in the process. > > The teacher in the learner-centered class is a designer of learning opportunities, one who sets the stage and then steps aside while the students engage in knowledge constructing activities. > > http://news.slashdot.org/story/09/11/09/2347215/Attack-of-the-PowerPoint-Wielding-Professors > > Cheers, > joanna > > > :::::::::::::::::::::::::::::::::::::::::::::::::: > Joanna Proulx : Team Lead > Interaction Development > Content & Collaboration Services > .................................................. > MIT : IS&T : ISDA : CCS : ID > > > > On 11/3/09 1:16 PM, "Daphne Ogle" <daphne@...> wrote: > > Yes, thanks for sharing Michael. Mathieu's post makes me wonder if we have a good understanding of the multiple types of course/activity structures we need to support in Sakai 3? It seems Moodle handles the syllabus/time-based and topic-based structures which make sense. Are there others? Understanding these will be key to creating the right context, cues, flows to help faculty build there course space in ways that match their mental models and then represent the course in ways that make sense to students. > > -Daphne > > On Nov 3, 2009, at 6:21 AM, Plourde, Mathieu wrote: > > Funny that this thing has come to a full circle… Anyone remember VirtualU? The default course was a long table organized as a list of event with links to discussions and resources. > > I think the goal of that article was not to say that organizing your content in a calendar was the best way to think, but that the defaults are what most faculty will select. > > If Sakai 3’s default is to present multiple options in terms of course/activity structure, and can support faculty in choosing an appropriate one to start with, half the battle will be won. > > Best Regards, > > ================================= > > Mathieu Plourde, MBA > Project Leader, LMS/Instructional Designer > IT-Client Support & Services > mathieu@... > > ================================= > > TOP LINKS: > > Technology Troubleshooting: http://www.udel.edu/help > Sakai@UD Support and Training: http://www.udel.edu/sakai/training > > ================================= > > From: sakai-ux-bounces@... [mailto:sakai-ux-bounces@...] On Behalf Of Jacques Raynauld > Sent: Tuesday, November 03, 2009 8:51 AM > To: Sakai UX > Cc: Michael Korcuska; pedagogy@... Learning > Subject: Re: User Experience] Interesting blog post on CMS user interfaces > > I also agree. It is a very interesting article. I have always been struck by the Moodle first page template that naturally leads to a week or theme interpretation by users. I think it is one of the important factor that explains Moodle popularity. This is the kind of need we wanted to adress in Sakai/Open Syllabus ... but in a more semantic way than Moodle. > > Jacques Raynauld > HEC Montréal > > -------- Message original -------- > Sujet : Re: [DG: User Experience] Interesting blog post on CMS user interfaces > De : harriet@... > Pour : Michael Korcuska <mkorcuska@...> <mailto:mkorcuska@...> > Copie à : "pedagogy@... Learning" <mailto:pedagogy@...> <pedagogy@...> <mailto:pedagogy@...> , Sakai UX <sakai-ux@...> <mailto:sakai-ux@...> > Date : 2009-11-03 04:58 > > Very interesting - thanks Michael! > > There were a couple of paras that struck me particularly as relating to the > possibilities for the new Sakai 3: > > "The buttons link to pages that simply provide a place to upload a document, > which is exactly what most instructors do: upload word–processed files of their > classroom materials. They are encouraged to “plug in” their content under the > appropriate category instead of envisioning a translation of their individual > pedagogical style into an online environment. Blackboard “tends to encourage a > linear pathway through the content” [3], and its default is to support easy > uploading and text entry to achieve that goal. > The construction of the course syllabus is a familiar beginning point for most > instructors, yet few CMSs consider this. It would be natural and useful for > novice instructors to see a blank schedule into which they could create each > week’s or unit’s activities, rather than a selection of pre–set buttons or > links. Most professors think in terms of the semester, and how their > pedagogical goals can be achieved within the context of time, rather than > space. Some think in terms of topics they want to cover. Blackboard/WebCT’s > default organization accepts neither of these approaches in its initial > interface. It forces the instructor to think in terms of content types instead, > breaking the natural structure of the semester, or of a list of topics. Again, > we know that the setup can be customized with relative ease, by going to the > Control Panel and selecting Manage Course Menu, then using Modify buttons. You > could change all the course menu buttons into “Week 1”, “Week 2”, or organize > by topic instead of content type. But few professors try that, or they assume > that they can’t do it. Blackboard can be highly intimidating to learn, and may > “seriously hinder” choices the faculty member makes while using the tool [4]. > Faculty are led by the interface of a CMS not only because they do not > immediately see an alternative, but because the familiar signposts (the > Syllabus button) imply a single way of completing the task (upload a document). > Only the Moodle system provides a default setup that looks like a calendar-style > syllabus ..." > > I'd agree very strongly with this statement about pedagogies, and the initial > presentation of potential course structures, rather than tools, to the > lecturer, seems to be something that Sakai 3 has the potential to support > > > "Although it is an oversimplification, it is useful to separate course > management systems into two types: Opt–In and Opt–Out. In an Opt–Out system > (such as Blackboard) all the features are available by default and must be > excluded to avoid confusing students. Opt–Out systems are most likely to > overwhelm Web novices, because they present an array of tools, and the tendency > is to reduce cognitive load by using the defaults. In an Opt–In system (such as > Moodle), the instructor selects each activity and presentation factor from a > menu list, effectively designing much of the interface for students. Fewer > defaults are pre–set, forcing the instructor to think holistically about the > class structure. Features such as chat, polls, and interactive lessons as > options presented with the same weight as more traditional text–based > resources. Thus there is less of an implication that presentation is key, and > more of an implication that interactivity is important. In an Opt–In > environment, the instructor makes choices about context on a macro level, and > choices about features and tools on a micro level. This makes it possible to > explore pedagogical options more freely" > > Again, perhaps a future strength of Sakai 3? > > Harriet > > > > Quoting Michael Korcuska <mkorcuska@...> <mailto:mkorcuska@...> : > > > It's worth a read.... > > > > http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 > > > -- > Michael Korcuska > Executive Director, Sakai Foundation > mkorcuska@... > phone: +1 510-859-4247 (google voice) > skype: mkorcuska > > > > > _______________________________________________ > sakai-ux mailing list > sakai-ux@... > http://collab.sakaiproject.org/mailman/listinfo/sakai-ux > > TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... > with a subject of "unsubscribe" > > > > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > _______________________________________________ > sakai-ux mailing list > sakai-ux@... > http://collab.sakaiproject.org/mailman/listinfo/sakai-ux > > TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" > > > > _______________________________________________ > pedagogy mailing list > pedagogy@... > http://collab.sakaiproject.org/mailman/listinfo/pedagogy > > TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... with a subject of "unsubscribe" > > > Daphne Ogle > Senior Interaction Designer > University of California, Berkeley > Educational Technology Services > daphne@... > cell (925)348-4372 > > > > > > > > > > > > > _______________________________________________ > sakai-ux mailing list > sakai-ux@... > http://collab.sakaiproject.org/mailman/listinfo/sakai-ux > > TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"
	Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces by Joanna Proulx :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces Hello John, To the best of my knowledge – Tomorrow’s Professor does have some institutional backing. Feel free to add your comments to the posts or to ping the admins for more details. Thank you also for the student blog link. We don’t have a Planet Sakai equivalent (calling it “Planet Stellar” would be somewhat — anticlimactic) but we do keep an internal list of relevant and fascinating links to blogs, articles and the like: http://www.technologyreview.com/business/20872/ In a pinch, I’ve found that the Education section of MITWorld also delivers great food for thought: http://mitworld.mit.edu/browse/topic/6 Best, joanna On 11/15/09 6:59 PM, "John Norman" <john@...> wrote: Thanks for these links Joanna. I am curious to know more about the Tomorrow's Professor collaboration. It looks like a grass-roots thing, but it could have institutional support... Also, the second link took me to a very interesting student blog "Carolyn Blogs" (http://blog.carolynworks.com). Do you have any coordinated collection of such blogs? It might be interesting to collect them in a fashion similar to Planet Sakai. Best, John On 12 Nov 2009, at 22:39, Joanna Proulx wrote: > Hi Daphne et al, > > As we focus, here at MIT, on the mental models of faculty with respect to their online teaching, there’s a constant effort to remember that any LMS has to be a two-way street. The students are partners in this process and their mental models matter equally to those of the faculty. If they are ignored, true learning is likely to be hampered if not arrested entirely. I have two examples to share by way of inveighling on behalf of the student perspective: > > http://tomprofblog.mit.edu/2009/10/13/974-online-learning-more-than-technical-savvy/ > > We posit that readiness for online learning has less to do with students’ knowledge of technology and digital dexterity and more to do with their knowledge of how to learn and their motivation to engage fully in the process. > > The teacher in the learner-centered class is a designer of learning opportunities, one who sets the stage and then steps aside while the students engage in knowledge constructing activities. > > http://news.slashdot.org/story/09/11/09/2347215/Attack-of-the-PowerPoint-Wielding-Professors > > Cheers, > joanna > > > :::::::::::::::::::::::::::::::::::::::::::::::::: > Joanna Proulx : Team Lead > Interaction Development > Content & Collaboration Services > .................................................. > MIT : IS&T : ISDA : CCS : ID > > > > On 11/3/09 1:16 PM, "Daphne Ogle" <daphne@...> wrote: > > Yes, thanks for sharing Michael. Mathieu's post makes me wonder if we have a good understanding of the multiple types of course/activity structures we need to support in Sakai 3? It seems Moodle handles the syllabus/time-based and topic-based structures which make sense. Are there others? Understanding these will be key to creating the right context, cues, flows to help faculty build there course space in ways that match their mental models and then represent the course in ways that make sense to students. > > -Daphne > > On Nov 3, 2009, at 6:21 AM, Plourde, Mathieu wrote: > > Funny that this thing has come to a full circle… Anyone remember VirtualU? The default course was a long table organized as a list of event with links to discussions and resources. > > I think the goal of that article was not to say that organizing your content in a calendar was the best way to think, but that the defaults are what most faculty will select. > > If Sakai 3’s default is to present multiple options in terms of course/activity structure, and can support faculty in choosing an appropriate one to start with, half the battle will be won. > > Best Regards, > > ================================= > > Mathieu Plourde, MBA > Project Leader, LMS/Instructional Designer > IT-Client Support & Services > mathieu@... > > ================================= > > TOP LINKS: > > Technology Troubleshooting: http://www.udel.edu/help > Sakai@UD Support and Training: http://www.udel.edu/sakai/training > > ================================= > > From: sakai-ux-bounces@... [sakai-ux-bounces@...] On Behalf Of Jacques Raynauld > Sent: Tuesday, November 03, 2009 8:51 AM > To: Sakai UX > Cc: Michael Korcuska; pedagogy@... Learning > Subject: Re: User Experience] Interesting blog post on CMS user interfaces > > I also agree. It is a very interesting article. I have always been struck by the Moodle first page template that naturally leads to a week or theme interpretation by users. I think it is one of the important factor that explains Moodle popularity. This is the kind of need we wanted to adress in Sakai/Open Syllabus ... but in a more semantic way than Moodle. > > Jacques Raynauld > HEC Montréal > > -------- Message original -------- > Sujet : Re: [DG: User Experience] Interesting blog post on CMS user interfaces > De : harriet@... > Pour : Michael Korcuska <mkorcuska@...> <mkorcuska@...> > Copie à : "pedagogy@... Learning" <pedagogy@...> <pedagogy@...> <pedagogy@...> , Sakai UX <sakai-ux@...> <sakai-ux@...> > Date : 2009-11-03 04:58 > > Very interesting - thanks Michael! > > There were a couple of paras that struck me particularly as relating to the > possibilities for the new Sakai 3: > > "The buttons link to pages that simply provide a place to upload a document, > which is exactly what most instructors do: upload word–processed files of their > classroom materials. They are encouraged to “plug in” their content under the > appropriate category instead of envisioning a translation of their individual > pedagogical style into an online environment. Blackboard “tends to encourage a > linear pathway through the content” [3], and its default is to support easy > uploading and text entry to achieve that goal. > The construction of the course syllabus is a familiar beginning point for most > instructors, yet few CMSs consider this. It would be natural and useful for > novice instructors to see a blank schedule into which they could create each > week’s or unit’s activities, rather than a selection of pre–set buttons or > links. Most professors think in terms of the semester, and how their > pedagogical goals can be achieved within the context of time, rather than > space. Some think in terms of topics they want to cover. Blackboard/WebCT’s > default organization accepts neither of these approaches in its initial > interface. It forces the instructor to think in terms of content types instead, > breaking the natural structure of the semester, or of a list of topics. Again, > we know that the setup can be customized with relative ease, by going to the > Control Panel and selecting Manage Course Menu, then using Modify buttons. You > could change all the course menu buttons into “Week 1”, “Week 2”, or organize > by topic instead of content type. But few professors try that, or they assume > that they can’t do it. Blackboard can be highly intimidating to learn, and may > “seriously hinder” choices the faculty member makes while using the tool [4]. > Faculty are led by the interface of a CMS not only because they do not > immediately see an alternative, but because the familiar signposts (the > Syllabus button) imply a single way of completing the task (upload a document). > Only the Moodle system provides a default setup that looks like a calendar-style > syllabus ..." > > I'd agree very strongly with this statement about pedagogies, and the initial > presentation of potential course structures, rather than tools, to the > lecturer, seems to be something that Sakai 3 has the potential to support > > > "Although it is an oversimplification, it is useful to separate course > management systems into two types: Opt–In and Opt–Out. In an Opt–Out system > (such as Blackboard) all the features are available by default and must be > excluded to avoid confusing students. Opt–Out systems are most likely to > overwhelm Web novices, because they present an array of tools, and the tendency > is to reduce cognitive load by using the defaults. In an Opt–In system (such as > Moodle), the instructor selects each activity and presentation factor from a > menu list, effectively designing much of the interface for students. Fewer > defaults are pre–set, forcing the instructor to think holistically about the > class structure. Features such as chat, polls, and interactive lessons as > options presented with the same weight as more traditional text–based > resources. Thus there is less of an implication that presentation is key, and > more of an implication that interactivity is important. In an Opt–In > environment, the instructor makes choices about context on a macro level, and > choices about features and tools on a micro level. This makes it possible to > explore pedagogical options more freely" > > Again, perhaps a future strength of Sakai 3? > > Harriet > > > > Quoting Michael Korcuska <mkorcuska@...> <mkorcuska@...> : > > > It's worth a read.... > > > > http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/2530/2303 > > > -- > Michael Korcuska > Executive Director, Sakai Foundation > mkorcuska@... > phone: +1 510-859-4247 (google voice) > skype: mkorcuska > > > > > _______________________________________________ > sakai-ux mailing list > sakai-ux@... > http://collab.sakaiproject.org/mailman/listinfo/sakai-ux > > TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... > with a subject of "unsubscribe" > > > > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > _______________________________________________ > sakai-ux mailing list > sakai-ux@... > http://collab.sakaiproject.org/mailman/listinfo/sakai-ux > > TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" > > > > _______________________________________________ > pedagogy mailing list > pedagogy@... > http://collab.sakaiproject.org/mailman/listinfo/pedagogy > > TO UNSUBSCRIBE: send email to pedagogy-unsubscribe@... with a subject of "unsubscribe" > > > Daphne Ogle > Senior Interaction Designer > University of California, Berkeley > Educational Technology Services > daphne@... > cell (925)348-4372 > > > > > > > > > > > > > _______________________________________________ > sakai-ux mailing list > sakai-ux@... > http://collab.sakaiproject.org/mailman/listinfo/sakai-ux > > TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe" :::::::::::::::::::::::::::::::::::::::::::::::::: Joanna Proulx : Team Lead Interaction Development Content & Collaboration Services .................................................. MIT : IS&T : ISDA : CCS : ID _______________________________________________ sakai-ux mailing list sakai-ux@... http://collab.sakaiproject.org/mailman/listinfo/sakai-ux TO UNSUBSCRIBE: send email to sakai-ux-unsubscribe@... with a subject of "unsubscribe"

[DG: User Experience] Interesting blog post on CMS user interfaces

[DG: User Experience] Interesting blog post on CMS user interfaces

Re: [DG: User Experience] Interesting blog post on CMS user interfaces

Re: [DG: User Experience] Interesting blog post on CMS user interfaces

Re: [DG: User Experience] User Experience] Interesting blog post on CMS user interfaces

Re: [DG: User Experience] User Experience] Interesting blog post on CMS user interfaces

Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces

Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces

Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces

Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces

Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces

Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces

Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces

Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces

Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces

Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces

Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces

Re: [DG: User Experience] [DG: Teaching & Learning] User Experience] Interesting blog post on CMS user interfaces