Successfully reported this slideshow.

Day 2, workshop 6, Jill Cousins


Published on

Published in: Technology, News & Politics
  • Be the first to comment

  • Be the first to like this

Day 2, workshop 6, Jill Cousins

  1. 1. From Repository to Wunderkamer: user participation in Europeana DISH 2009, Rotterdam Thursday 10, 2009
  2. 2. A typology of User Generated Content @ Olga – EuropaOne Runar - Avinet
  3. 3. The role and place of User Generated Content in Europeana @ Olga – EuropaOne Runar - Avinet
  4. 4. Issues of User Generated Content @ Olga – EuropaOne Runar - Avinet
  5. 8. UGC Europeana is considering or has started <ul><li>Tagging – need to ensure it adds to search and discovery </li></ul><ul><li>Exhibitions on Rhine or Great War </li></ul><ul><li>Addition of metadata to objects from cultural heritage institutions </li></ul><ul><li>People are currently thinking about </li></ul><ul><li>Subject cloud, based on users clicking on particular subjects </li></ul><ul><li>Digital Stories </li></ul><ul><li>The M word </li></ul>
  6. 10. Scenarios? <ul><li>“ .. storylines which tell about contexts of use of a system, which can be used as a meeting-place between developers / technology-providers / system-integrators and consumers in order to permit actual satisfaction of the context needs..” </li></ul><ul><li>Means not Ends </li></ul><ul><ul><li>helping to achieve something else </li></ul></ul><ul><ul><li>i.e. from thought to actual development </li></ul></ul>
  7. 11. What is a User Scenario? <ul><li>A storyline giving contexts of use of a “system” or a feature or functionality </li></ul><ul><li>Describes for developers/technology-providers/system-integrators what the “consumers” want to do or see. </li></ul><ul><li>Scenarios depend on the perspective from which the feature or functionality is perceived by a given “actor” </li></ul><ul><li>There can be many and various types and subtypes of actors: </li></ul><ul><li>“ content providers”, “content creators”, “institutions”, “business managers”, “technical managers”, “rights holders”, “end users” </li></ul>
  8. 12. Additional Requirements or Criteria <ul><li>Perspectives of the actors, according to their role </li></ul><ul><ul><li>i.e.: Content Providers, Aggregators, Europeana Business and Technical Staff, Editors, Moderators, Rights Holders, End Users </li></ul></ul><ul><li>Consider the evolution of the proposed feature, functionality, idea </li></ul><ul><ul><li>Describe the current situation </li></ul></ul><ul><ul><li>Draw a path from now to the future </li></ul></ul><ul><ul><li>Keep in mind available or possible technical solutions </li></ul></ul><ul><li>Balance between specific and general cases </li></ul><ul><li>Encompass standards and open approaches </li></ul><ul><li>Record the dimensions </li></ul><ul><ul><li>quantities, countries, scope </li></ul></ul>
  9. 13. a scenario shape <ul><li>Background / Characteristics </li></ul><ul><ul><li>description of the feature or functionality as it currently exists </li></ul></ul><ul><ul><li>why it is interesting </li></ul></ul><ul><ul><li>what is specific to it </li></ul></ul><ul><li>Questions addressed </li></ul><ul><ul><li>identification of the issues, critical points (decisions/options), needs </li></ul></ul><ul><li>Users and Roles </li></ul><ul><ul><li>who are the stakeholders / actors </li></ul></ul><ul><ul><li>what are their roles and relationships </li></ul></ul><ul><li>Description of cases </li></ul><ul><ul><li>detailed examples of what should happen, why, for whom and how </li></ul></ul><ul><li>Open Questions </li></ul><ul><ul><li>specific influences </li></ul></ul>
  10. 14. rough example <ul><li>Background / characteristics </li></ul><ul><ul><li>Addition of digitised user owned Great War memorabilia with metadata </li></ul></ul><ul><li>Questions addressed </li></ul><ul><ul><li>What digital formats can be allowed </li></ul></ul><ul><ul><li>What size can the images be </li></ul></ul><ul><ul><li>What type of storage solution is needed </li></ul></ul><ul><ul><li>What metadata can be reasonably collected </li></ul></ul><ul><ul><li>Where will the UGC be displayed </li></ul></ul><ul><ul><li>How will it be searched </li></ul></ul><ul><li>Users and Roles </li></ul><ul><ul><li>User generating the content and metadata </li></ul></ul><ul><ul><li>User using the content </li></ul></ul><ul><ul><li>Moderator ? </li></ul></ul>
  11. 15. rough example <ul><li>Description of Use Cases </li></ul><ul><ul><li>User has letter from aunt Freda that came from the pocket of uncle Bert who was shot in the war, letter has bullet hole through it </li></ul></ul><ul><ul><li>User wants to add letter to Great War Archive on Europeana </li></ul></ul><ul><ul><li>User needs a button to click on upload content to Europeana </li></ul></ul><ul><ul><li>User is given some guidelines over formats he </li></ul></ul><ul><ul><li>can use e.g. Jpeg, tif etc. </li></ul></ul><ul><ul><li>User uploads digital image and is asked </li></ul></ul><ul><ul><li>to complete form (this becomes the metadata) </li></ul></ul><ul><ul><li>User agrees to waiver all rights and allow reuse </li></ul></ul><ul><ul><li>User searches for letters from Great War </li></ul></ul><ul><ul><li>User retrieves letters held in national </li></ul></ul><ul><ul><li>archives and user clicks on one of Aunt Freda to Bert </li></ul></ul><ul><ul><li>User sees that this content is not from the Cultural institions </li></ul></ul><ul><ul><li>User shares letter with Great Aunt Gertrude </li></ul></ul>
  12. 16. rough example <ul><ul><li>Open Questions </li></ul></ul><ul><ul><ul><li>Are all fields on form mandatory? </li></ul></ul></ul><ul><ul><ul><li>Can user remove own data? </li></ul></ul></ul><ul><ul><ul><li>Does user need to register? </li></ul></ul></ul><ul><ul><ul><li>How to manage multilingualism ? </li></ul></ul></ul>
  13. 17. Expectations of Workshop <ul><li>Some nice new ideas for Europeana UGC or UGI </li></ul><ul><li>Knowledge on how to create a user scenario </li></ul>