43
edits
| No edit summary | |||
| Line 55: | Line 55: | ||
| 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. | ||
| ==Process of development== | |||
| During the process of evaluating our first prototype we received a short message from one of our participants who complained  | |||
| about a change on her blog platform which messed up the layout of her license tag and rendered it functionally broken. | |||
| [sms bild] | |||
| This call for help gave us the impulse to focus our attention more towards the usability of our proposed license manager  | |||
| application, which will aid the non-tech-savvy user in the process of correctly tagging his works with the approriate license. | |||
| Our group came to the conclusion to roll back our initial development from behind and decided to approach the problem the  | |||
| opposite way around. We assume that the typical user of our chosen target group decrees an intrinsic motivation to tag his  | |||
| work with appropriate copyright information. | |||
| [development bild] | |||
| ==Revised idea== | |||
| In our new proposed solution we would offer the user a tiny license manager interface which would initially provide a default  | |||
| license corresponding to "all rights reserved". We deliberately chose an empty looking tag icon similar to those provided by  | |||
| Creative Commons, and would arrange those in view to spark the users interest in the CC licenses just because of their look.  | |||
| As soon as a license has been chosen the software would provide an option for the most common blogging platforms (tumblr,  | |||
| soup.io, wordpress, facebook, google+, etc). In case the user choses a platform whose own license agreements for publishing  | |||
| material collide with a Creative Commons license it warns the user about arising difficulties concerning his rights. Through  | |||
| this methology we achieve our goal of creating interest in the CC model and are able to educate the user during his usual  | |||
| workflow. | |||
| During the course we want to conduct a quantitive user study if there exists a particular interest in such a software. At the moment we concentrate on developing a testable prototype and invited our previous participants to take part in such a study. | |||
| ==Scenario== | ==Scenario== | ||
edits