2
edits
No edit summary |
|||
(9 intermediate revisions by 4 users not shown) | |||
Line 51: | Line 51: | ||
====What is the essence of this solution?==== | ====What is the essence of this solution?==== | ||
A piece of software which eases the access to the Creative Commons license generator with the capability of storing a default chosen license. It is a one click solution for tagging content he shares on websites without the need for the user to know HTML or Markdown. | A piece of software which eases the access to the Creative Commons license generator with the capability of storing a default chosen license. It is a one click solution for tagging content he shares on websites without the need for the user to know HTML or Markdown. | ||
<div style="color:#32828C"> | |||
* It seems interesting to me, but it is not easy to imagine how exactly it will work. Could you give a brief scenario or some rough sketches to direct our thinking in the right direction? --[[User:JanD|JanD]] 22:24, 26 May 2013 (CEST) | |||
</div> | |||
====Why are current solutions unable to support users in this?==== | ====Why are current solutions unable to support users in this?==== | ||
We know of no current solution which addresses this usage scenario. Not all users are already familiar with a workflow using tabbed browsing to access the information on creativecommons.org and know how to properly tag their content. | We know of no current solution which addresses this usage scenario. Not all users are already familiar with a workflow using tabbed browsing to access the information on creativecommons.org and know how to properly tag their content. | ||
<div style="color:#32828C"> | |||
* Compare your ideas to: https://addons.mozilla.org/en-us/firefox/addon/openattribute/ It mainly seems for sharing and retrieving licence information, but might be a good inspiration.--[[User:JanD|JanD]] 22:24, 26 May 2013 (CEST) | |||
</div> | |||
==Implementations== | ==Implementations== | ||
Line 67: | Line 76: | ||
</gallery> | </gallery> | ||
<div style="color:#32828C"> | |||
* ''the images of the paper prototype are nice! '' | |||
* ''if I get it right, the licence manager and the "educator" are combined in the same add-on?'' | |||
* ''how do you get the user to install the add-on in the first palace? What are advantages users could see if they are only remotely aware of copyright and CC? ''--[[User:JanD|JanD]] 22:12, 26 May 2013 (CEST) | |||
</div > | |||
==Mentor's comments== | ==Mentor's comments== | ||
<!-- dear students, copy the headline and the this, so the mentors have a place to write their remarks and suggestions--> | <!-- dear students, copy the headline and the this, so the mentors have a place to write their remarks and suggestions--> | ||
=== Larissa's comments (Mozilla) === | |||
User Research | |||
* I like that you got specific in the target audience (students who didn't know anything about CC and were microblogging), instead of just interviewing any students. I also liked that you posted the interview with one of the students (even though I don't speak German) | |||
* I thought that your approach of interviewing the student while they were publishing content and then introducing the concept of CC was well thought out, and it yielded some interesting insights. | |||
* I would like to know more about how even the basic education about CC encouraged students to consider it an option when publishing their work. What value did they find in the CC model that they didn't have before? | |||
Product Ideas | |||
* I think the ideas you presented are creative, but I would like to see a stronger connection between the user needs and the proposed solutions. One place you are starting to do that is in the "license manager" where the user doesn't need to know html to generate the license. What other features would a user who isn't html-savvy need in order to successfully use CC in their work? | |||
* I'd like to see more ideation around the user need for education about CC licenses. Why would user education at an important point in the workflow be a good solution for your users? What would this look like in practice? | |||
=== Zhenshuo Fang's comments (Mozilla) === | |||
Research | |||
* Well-summarized research goal and method! | |||
* The problem you identified is the unawareness of CC. I'd like to see more reason behind why people are unaware of it, do they have alternatives, etc. | |||
* In "motivations and goals" you mentioned after introducing CC to users, they were all interested in using it. What's the reason behind it? what made them change? | |||
* The important activities can be more specific. For example how and which part of "usage of a web browser" an important activity. | |||
Ideas: | |||
* The add-on idea is interesting. Nice paper prototype! | |||
* Combining the educator and manager is an interesting approach. More questions to think about: Are these solutions solving the same problem? are they for same users? why people don't know about CC would install the add-on, and why someone already install the add-on need to know more about CC? | |||
=== Bram Pitoyo's comments (Mozilla) === | |||
First idea: | |||
Thinking about something that fits the existing workflow is good. Of course, there’s two sides of the equation: the user/remixer, and the creator/owner. Your educator idea hits the user/remixer. How can you extend it so that it can also be used from the side of the creator? | |||
Thought experiment: if imgur or Vimeo deploys an educator, what would it look like? | |||
Second idea: | |||
There’s a bit of a ‘preaching to the choir’ quality going on here. People who care about CC will look up and install the manager out of active curiosity, but people who don’t care might not be interested enough to find and install license manager in the first place. | |||
How would you build the manager in such a way that those who don’t know about CC will want to use it actively? | |||
=== Tony's comments (Mozilla) === | |||
Research | |||
* fantastic job defining your audience and then finding people in your student community that met those criteria. This would be a great study to expand with non students who are equally uninformed about copyright and see if your findings hold as you get a broader sample of age and occupation. | |||
* sharing and interview is a great way to make your research easier to understand for people who weren't there. It also makes your design ideas easier to sell later on. | |||
* are there other areas where these users' goals overlap the goals of the commons other than publishing? | |||
* what are the biases you have to take into consideration doing research with only students at your school? | |||
Ideas | |||
* I like the initial idea of an awareness campaign in places that it actually makes sense. How do you work around sites that automatically apply a license to uploaded content, like Facebook, does the alert still show there? If so, what does it say? | |||
* the license manager seems really useful, and I think it ties back to the things you learned from your research well. Again I have to ask about sites that don't let users choose a license, what does the plugin do then? Is there maybe some kind of activism for the commons component to this in these cases? |
edits