No edit summary |
|||
| Line 28: | Line 28: | ||
The essence of our solution is to find an easier way for professional creatives to find material that is covered by CC-licenses. Our idea is to built an online archive with only CC-licensed stock. Furthermore, a specialized filter-function would provide an easier and faster search. We had research-filters like licenses, themes and colors in mind. An important new function should be a specialized tagging and labeling method for the CC-licenses material. It should be easy, clear and not attract too much attention when in use. Therefore we would like to find a way to hide the labeling of the work, for example by the use of a meta level. | The essence of our solution is to find an easier way for professional creatives to find material that is covered by CC-licenses. Our idea is to built an online archive with only CC-licensed stock. Furthermore, a specialized filter-function would provide an easier and faster search. We had research-filters like licenses, themes and colors in mind. An important new function should be a specialized tagging and labeling method for the CC-licenses material. It should be easy, clear and not attract too much attention when in use. Therefore we would like to find a way to hide the labeling of the work, for example by the use of a meta level. | ||
<div style="color:#32828C"> | |||
* Finding CC-Licenced content is a very important topic. As well it is a quite broad one – if you review your user research again, is there anything that helps you to focus the topic to a ''certain aspect'' of searching and finding that needs attention? (e.g. is the licence filter of e.g. [https://secure.flickr.com/search/advanced/ Flickr's advanced search] understandable for the users? What about saving files once they are found? You could as well compare "professional" image databases with their open "amateur" counterparts. What is different?) | |||
* What do you mean by tagging and labeling? Can you please provide some sketches, a scenario or the like to make it easier to grasp (and to save you the work to write a looong text about it) | |||
</div> | |||
====Why are current solutions unable to support users in this?==== | ====Why are current solutions unable to support users in this?==== | ||