Showing posts with label open badges. Show all posts
Showing posts with label open badges. Show all posts

Thursday, January 9, 2014

The Participatory Design Culture and Terms of Badges

As we all know, the Badges project seeks to provide users with a mechanism to shape their online identities: showcasing the skills that they have earned over time or in the case of an issuer, the skills that they might have to offer. 

So let's take a second to talk about collaboration -- or as I like to think of it: the conversation:

By nature, badges are a participatory design project. From its very conception, the project was designed by and for the learning,  design and tech communities to help ensure that the product that was ultimately designed met their needs and was in fact usable. 

However, Participatory design also requires user - generated content for culmination. Every badge is, in essence, an invitation to a conversation. For example:  I make a badge with some basic criteria (this is in essence a "call to action")  , and then a maker responds to the call with evidence (like a   photograph), and then I react to the response with a conversation about  that data.  
 
Badges say: "User generated content : you complete me. "
This call and response culminates in co-authorship of a badge that then has the ability to be viewed by any viewer in a way  that  allows them to be kind of like an eavesdropper on the  conversation.
This leaves us with questions about "ownership."  This question is more than just legal.  It's the foundation of the entire project.  

The notions of Participatory design + ownership require developing a community of practice around: (1) establishing authenticity (2) engaging in collaboration/remix culture and (3) attributing content ethically.   

I believe that Open Badges needs a method to instill the practices of remix and participatory culture that are at this project's core.  This project seeks fundamentally -- to show what you can do!  If I can put up a badge that says I can do X but I can't do X,  (or says that I am an expert judge of this skill) then the badge is meaningless.  This comes down to ethics for badgemakers 101 :) 

Henry Jenkins said that "Everyone sees the future will be more  participatory, but we are fighting over the terms of participation."  I don't know what the best terms of co-creation and remixing are, however I am interested in considering the opportunity that we are providing to badge makers, who are engaging in conversation via the vehicle of the medium. 

Through the exploration of co-authorship and remixing practices that are already happening or are desired, I suspect that we can start to propose some options for flexible options of copyright or licensing.

Before  I get too far along in the solution, let me guide you through some  potential use cases for participatory design within the badge making experience.

  • As a badge issuer I might want people to:
    • be able to use my badge 'as is' and re-issue it as their own.
      • They can re-use the art
      • They can re-use the metadata
      • They can re-use the badge name 
      • They can re-use the badge criteria
    • be able to 'fork' and modify my badge and re-issue it as their own.
    • be able to tweak my badge's metadata
    • be able to publicly issue my badge
    • be able to only issue the badge privately 
    • use the badge artwork that I designed
    • be able to issue this badge to <13 span="" users="">
    • be able to issue this badge with age restrictions
    • be able to issue this badge only to >13 users (etc)
    • be able to localize the badge

These are all interactions that could impact a license. What is implicit here  is the desire to freely circulate and allow for tinkering of content.  Without the free circulation content, participatory culture cannot  exist. After  Connected Educators Month, Chicago Summer of Learning and general badge issuing in the Hive we know that there is a  desire to  "fork", "clone" or "copy" badges or parts of a badge. We have already  started to deal with licensing issues with regard to badge  imagery -  utilizing icons from the Noun Project and Subtle Patterns, however we  know that there is a large scope for metadata that could in fact be  cloned or forked.  

Let's  take a look at the badge studio wireframes to see where there are  licensing touchpoints in the badge making process. These wireframes were  designed by Matthew Willse and will be incorporated into the upcoming  release for BadgeKit. Some of the ideas represented in these mockups  will be implemented in a future iteration of BadgeKit. 





   
As a badge maker is using this part of the BadgeKit site, they can define  many parts of the badge - from visual design to badge description.  Additionally, as you can see in the wireframe, in the optional  information we could enable users to add licensing and set parameters  for the project. This is really not an answer to the intellectual  property question, but just some context.

Currently there is no way to credit someone in any form in components/ or a whole badge through using the tools that we have developed. So, without clearly attributing ownership, the wrong person could be credited as the maker, etc

I believe that a creative commons license is the direction that we should head with this project, however, there are many existing forms of licenses that support creative digital content and I want to go over how I came to this decision. *You can scan my overview in the etherpad.

  • Pros: automatic,  the default, commonly understood 
  • Cons: Doesn't encourage this type of creating

2. OPEN SOURCE  + Copy Left  (SOME RIGHTS RESERVED)
  • Pros:
    • More closely matches this project's underlying purpose--cooperation, collaboration...
    • This sharing model allows people to quickly use, change, and share badges
  • Cons:
    • Seems to apply more acutely to the core software (vs. the bi-product) 

3. Badge Common License (BCL) *something i totally just made up 
  • PRO: A unique license structure could allow users to badge component parts or whole badges.
  • CON: This  seems a bit over the top, considering how many great  licensing frameworks are already in existence. This would be another thing that  badge issuers would need to conform to, and really, who is going to police it ? 
    The response from my colleague Michelle Thorne was so strong, I have to add it here:  " Please, please, please don't make a new license! It will cause confusion and lack of interoperability. This is more restrictive than all rights reserved. Instead, consider a "badge licensing policy" which suggests how to license and attribute based on existing licensing standards, like Creative Commons."

This leaves me to my choice, the: 

4. CREATIVE COMMONS LICENSE -which is actually not a single license, but many licenses. Lawrence Lessig founded the free culture movement  to promote greater legal freedom in the reuse of published content, which later lead to the Creative Common flexible"licenses" that offer a range of legal protections..

  • Pros: 
    • Alligns w/ this project's purpose 
    • Flexible, so that it offers a media maker the ability to state what level of remixability she is comfortable with
    • Allows someone to fulfill ambition of encouraging dialogue, collaboration, etc., w/o sacrificing control, etc.  
  • Cons:
    • New, not universally recognized or understood --> I'd argue these are some of the best known copyright licenses with lots of adoption. Education space already using widely.
    • Not made for source code. So, worth considering how to use CC for creative work (like badge design and descriptions) and source code (but not metadata) like the OBI. 

As I mentioned earlier, my goal is to get a sense of the options available to us so that I can incorporate it into the software. This will allow us to start to develop a community of practice around attribution.  At the moment, I feel that we should go with creative commons licenses. 
That said, I still have a lot of questions in terms of application. For example, should the software allow for different operations to have different licenses? or What about when a badge earner submits their content for review, does this part of the conversation have a separate license? 

I would be interested in hearing about additional use cases for badges remixing, co-authorship and cloning and hearing more thoughts on licensing and copyright. 


FURTHER READING:

  • Elkin-Koren,  Niva. "Intellectual Property and Public Values: What Contracts Cannot  Do: The Limits of Private Ordering in Facilitating a Creative Commons." Fordham Law Review. (2005): 375.
---------------
Please note: I am not a lawyer, nor do I pretend to be. I am merely researching the subject.

----------------

Monday, December 2, 2013

Brainstorming on Dashboards

During the summer, I spent some time thinking about badge directories and dashboards. The general idea was to prototype a tool for badge earners to make sense of the larger badge ecosystem and in turn to create an integrated dashboard that would help them to collect, maintain and analyze their personal data on their learning, goals and skill acquisition.

Initially I had come up with a few ideas for this dashboard:

a. focusing and personalizing skill search. Here, the user might type in skills that are of interest to them and then popular badges would appear. I like exploring the interaction of incorporating some narrative elements into this framework. Here, instead of just a search box - you have a statement of intent. 

-1 


b. pathways focused -  This mock up lays out skills you already have and then upon click/hover you can see where your skills could lead you. This is personalized approach, so once you log in, it will display a visualization of skills that relate to your data. However, if you are not logged in, it could display popular or trending skills or even .. geolocate badges based on your location.


-2 

c. Toggle vision - this gives you the chance to explore what is available in the ecosystem as well as in your personal badge library - as a list, as a visual display, and on a map.

-3 

d. Whimsical Exploration - still playing with the theme of exploration, discovery and happenstance - this is kind of like a wheel of fortune. Each node coming out of the circle lists skills and then if you are logged in and in fact have the skill, it will be notated. There is a natural progression from this view to a more sophisticated learning pathways exploration. 

-4 


e. Your (data) garden - This one is a little crazy - but imagine that all of the trees below represent your skills at different stages of growth. You can have "community" gardens as well as "secret gardens" - giving you the ability to curate what data you are in fact sharing. Here you can also set goals, be informed about your "garden health" - which might just equate to giving feedback on various goals that you have set up for yourself - and tool tips - which could be mentorship or coaching based on your goals. There's a lot of metaphor going on here and it probably would be a brain game to figure out how to design it .... but this is just a sketch, so wha ha ha haaaa.


-5 


So - the Summer came and went and I thought about these prototypets a little bit more. More specifically, I started to consider what a dashboard and a discovery feature would mean in the context of something like BadgeKit. The goals of the dashboard, by nature would change to accommodate an issuer (as opposed to an earner). I think that these explorations are still totally valid and even hackable to modify for this new lens. Some of the goals for the user might include:
  • keeping track of the badges that they are offering
  • getting notifications regarding badge assessment needs
  • analyzing trends for badge earners. 
  • sharing rights for admin functionality. 

While I push forward on the thinking some more - I was reminded of the video, the Powers of Ten, when thinking about the display of badge data and badge ecosystem information. Upon first glance, a user might want a 1000 ft view of their world, but perhaps they want the ability to easily navigate back and forth through the level of detail that their data could be providing. Maybe an issuer only wants to view their goals, or their assessments - but perhaps they want to see trends, data about individual badges, and individual users. Maybe an issuer wants to connect their data to algorithms... the possibilities are endless!   Will update as we start to think about this more.


Thursday, November 21, 2013

Rethinking the Annual Review Self Evaluation

Every year I have to do an annual review - where I meet with my manager and discuss my performance over the course of the past year. Usually these reviews require me to respond to some sort of questionnaire about my work - with questions kinda like these:

List the projects that you worked on?
Which project are you the most proud of?
How can you improve?
  
For my last review, I felt inspired to switch up my submission to my manager and handed her this instead of the traditional q and a response form:
jessklein-birthday
My manager, Erin Knight, responded to it well and was able to ask me relevant questions based on the things that I chose to highlight. This year I was going to take it up a notch and make this an interactive experience. As I started to think about how to go about this work.

The first thing that I did was create a list in Evernote of all of my work:


Then I started to think about if this was going to be interactive - where would I link out to my work. This helped me to realize that I have my work documented in several places online, including: this blog, flickr and github. This lead me to an a-ha moment. I had skills that I wanted to show off, evidence to back up that I did in fact earn or enhance those skills and... I had a peer reviewer to potentially endorse me. Are you following me here? BADGES!

What I imagining here is a re-envisioning of the self evaluation. Instead of thinking about this as an evaluation - you can imagine this being a tool to help to uncover what you have learned over the course of the year and how you could potentially further your learning moving forwards. I am proposing a tool where I can self issue badges, with evidence and have those badges endorsed by my peer. A more complex version of this would integrate career pathways and mentorship opportunities - as well as a recommendation system.

Here is my first sketch on this idea:


Thinking to be continued.....