BCopenEd, Student as Producer

Case Studies on the Student as Producer (Slides)

“In the end, an essay or an exam is an instance of busywork: usually written in haste; for one particular reader, the professor; and thereafter discarded.” – Jon Beasley-Murray, from Was introducing Wikipedia to the classroom an act of madness leading only to mayhem if not murder?

Novak and I recently had the opportunity to present at ETUG’s Fall Workshop on the topic of “Case Studies for Students as Producers.” In the Student as Producer model, as Derek Bruff has eloquently distilled from Mike Neary’s conceptualization: “students should move from being the object of the educational process to its subject. Students should not be merely consumers of knowledge but producers, engaged in meaningful, generative work alongside the university’s faculty”.

This idea of positioning student work as as a collaborative and valuable resource alongside that of faculty members is an important driver of uptake for some the tools and technologies, such as UBC Blogs and the UBC Wiki, that support open education initiatives. Here are a couple of the amazing open projects working using these tools to support students as producers:

  • Some instructors in the Arts One program are asking their students to critique or analyze readings and lectures on blogs. The use of blogs takes the writings out of a closed loop with only the instructor reading and responding to a student’s work. Instead, the students are sharing their critiques and thoughts openly on the internet, where they are contributing to the scholarly conversation of classic texts of the past two millennia. Furthermore, the student blog posts are syndicated via rss to the Arts One Open site, where the student content appears along side the instructor content, creating a rich and robust extension of the course. Clicking on any given tag, such as Borges, gives amazing and growing archive of online lectures, podcasts, essays, and critiques. Finally, since the students are blogging on their own personal blogs, they control their content, which they can delete, edit, or move to a new space at will.
  • Similarly, in LAW423B: Video Game Law, students can author directly on the public facing course website, allowing them to create and post content along side the instructor. This content is not just limited to the student and instructor, but is on an open website that is quickly becoming a highly trafficked and widely-read resource about a specific topic. Thus, students are sharing their work and being read by leaders in the video game law community.
  • Students in FNH200 are asked to author collaborative open wiki and video projects, thus students are not only sharing their work with instructor, each other, and, well, the world, but also future students who will take the course. This is important because, as it turns out, current and past students are setting the bar for the quality of future projects. The quality of the student work is being elevated as students are able to review and reference previous years projects, build upon them, and develop what is effectively an open knowledge base on food science (and their work is being incorporated into he course).

And here’s our slides for our presentation:

We broke pretty much every rule there is about using slides effectively in a presentation (bad design, low colour contrast, mismatched fonts on walls of text, etc) but I’m going to position that strategy as intentional effort to highlight the artistry of the projects we’ve been fortunate to witness and support in one way or another.

Standard
BCopenEd, Open Badges, Privacy Issues

Thinking Through Open Badges and Privacy

I’ve been working with a number of different projects that are interested in the idea of utilizing open badges as a hook for creating a motivational and pedagogical pathway through their open course content.  Being located in a province and institution with a strong privacy commitment means thinking hard about privacy before implementing  tools that potential share student information with third parties, such as the WPBadger WordPress plug-in that would allow us to issues badges to Mozilla’s Open Badge Backpack.

Just to help think through privacy from the user perspective, I believe that there’s basically three levels to information sharing that would be involved in open badges – one is at the university level, one is at the system level, and one is at the individual badge level.  I’m going to use a very clumsy and simplified metaphor here: in some ways issuing badges via something like the WPBadger plugin would be similar to the “tweet this” widget found on the bottom of many university sites.  Clicking on the twitter icon will send the user to twitter, where they have to log-in, then they see a pre-formatted tweet that they can edit, then they have to hit publish to push that message into their twitter stream.

So at the university level, you have a twitter widget that sends information – “this user” clicked tweet this on “this page” –  between the university webpage and twitter.  For an open badge system, the information communicated between the university site and the badge framework is “this user” earned “this badge”.  Mozilla treats “this user” as an email address.  Indeed, a badge issuing tool like the WordPress WPbadger plug-in, the user data transmitted from the issuing site to Mozilla is only an email address – and the badge, more info about that shortly.  So only contact information – no names, student numbers, grades, etc.

At the system level, a user will have to have log-into a third party account.  In twitter, once clicking that “tweet this” button on a university site, the user has to have a twitter account to actually tweet anything.  Similarly, with badges, the user has to have a location (called a “backpack” in Mozilla terminology) where they collect/store and display their badges that they have earned across multiple places (i.e. a user may have badges from Purdue, Illinois, UBC, etc).  The Mozilla backpacks are, again, based only on a verified email address (nothing more).  Similar to twitter, where the user still has to publish the tweet, users still have to publish the badges they have earned in order to make them publicly visible.

At the individual badge level is probably the area where the most sensitive information could possibly be shared.  In the twitter widget, a pre-formatted message can be created.  This pre-formatted message could be anything and thus, theoretically, could contain information, which when combined with a user account, could be seen as sensitive (e.g Will tweeted “I just enrolled in BIOL104”).  Similarly, the open badge is really just a collection of metadata and thus could also contain sensitive info such as a grade (The BIOL104 A+ badge).   Again though, users will have to manually publish any badges they earn before they are publicly viewable.

It’s possible to build a system that’s not predicated on a third party like Mozilla, but in many ways this will decrease the usefulness of an open badge and will not decrease the metadata issue as well.  Information conveyed in an open badge is meant to be, well, open but the key aspect when it comes to privacy is that such badges are also meant to be optional, opt-in, and user controlled at many different levels: optional to earn, optional to have an account, optional to display.

Standard
BCopenEd, Creative Commons

Creating a Global Education Commons

Paul Stacey recently spoke at UBC on the topic of the impact of Creative Commons on education as part of the part of the Teaching, Learning, & Technology lecture series and the Open Education Community of Practice:

Teaching and learning involve knowledge creation and dissemination, which requires faculty, librarians, students and staff to work within legal requirements of copyright and intellectual property. For many this has been highly contentious, pitting end users against major publishers or resulting in widespread abuse of the law. Creative Commons licenses give rights owners and users a set of tools that enable a differently balanced copyright system…

Be sure to check out the full audio recording and slides of Paul’s talk, which are available via the UBC Wiki.

Standard