Your SlideShare is downloading. ×
Design for Crowdsourcing
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Design for Crowdsourcing

710

Published on

Presented Dec. 8 at the Powerhouse Museum, Sydney, Australia.

Presented Dec. 8 at the Powerhouse Museum, Sydney, Australia.

Published in: Education, Technology, Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
710
On Slideshare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
0
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Design  for  crowdsourcing Recent  projects  at  the  New  York  Public  Library Presented  to  the  Powerhouse  Museum 8  December  2011 Michael  Lascarides Senior  Manager  for  Web  IniFaFves,  NYPL @mlascarides  /  @nypl michaellascarides@nypl.orgMonday, December 12, 2011
  • 2. Map  Warper maps.nypl.org 2009Monday, December 12, 2011[35:00]
  • 3. Monday, December 12, 2011
  • 4. Monday, December 12, 2011
  • 5. Monday, December 12, 2011
  • 6. Monday, December 12, 2011
  • 7. Monday, December 12, 2011
  • 8. Monday, December 12, 2011
  • 9. Monday, December 12, 2011
  • 10. (sadly,  not  easy)Monday, December 12, 2011
  • 11. Monday, December 12, 2011
  • 12. Monday, December 12, 2011
  • 13. Monday, December 12, 2011
  • 14. Monday, December 12, 2011
  • 15. Monday, December 12, 2011
  • 16. Monday, December 12, 2011
  • 17. Monday, December 12, 2011
  • 18. Monday, December 12, 2011
  • 19. Monday, December 12, 2011
  • 20. Monday, December 12, 2011
  • 21. Gaze:eers  &  directoriesMonday, December 12, 2011
  • 22. Monday, December 12, 2011Most importantly, locational data is an important pivot point for a lot of otherprojects.
  • 23. What’s  On  The  Menu? menus.nypl.org 2011Monday, December 12, 201140:00
  • 24. Monday, December 12, 2011
  • 25. Monday, December 12, 2011
  • 26. Monday, December 12, 2011
  • 27. Buried  treasure   (literally)Monday, December 12, 2011
  • 28. Monday, December 12, 2011
  • 29. Monday, December 12, 2011
  • 30. Monday, December 12, 2011
  • 31. Monday, December 12, 2011
  • 32. Monday, December 12, 2011
  • 33. Consider  the  oyster…Monday, December 12, 2011
  • 34. Monday, December 12, 2011
  • 35. Monday, December 12, 2011
  • 36. Monday, December 12, 2011
  • 37. Monday, December 12, 2011
  • 38. Monday, December 12, 2011
  • 39. Monday, December 12, 2011
  • 40. Monday, December 12, 2011
  • 41. Monday, December 12, 2011
  • 42. Monday, December 12, 2011
  • 43. Monday, December 12, 2011Strangely enough, weʼve gotten a lot of attention for simply putting these canned searches here on theright.
  • 44. Monday, December 12, 2011
  • 45. Monday, December 12, 2011
  • 46. Monday, December 12, 2011
  • 47. Monday, December 12, 2011
  • 48. Monday, December 12, 2011
  • 49. Food  enthusiasts,  chefs,   librarians,  writers,   random  obsessives…  Monday, December 12, 2011
  • 50. Monday, December 12, 2011School for the deaf in Texas.
  • 51. Over  58,000  visitors  in  4.5  mos. 10,000+  menus  fully  transcribed 600,000+  dishes  transcribedMonday, December 12, 2011We could have done more but we ran out of digitizedmenus!
  • 52. Monday, December 12, 2011We could have done more but we ran out of digitizedmenus!
  • 53. Monday, December 12, 2011
  • 54. Monday, December 12, 2011
  • 55. Next:  Linked  DataMonday, December 12, 2011
  • 56. Rules  for  good crowdsourcing  designMonday, December 12, 2011
  • 57. “Choose  your  parents  wisely”Monday, December 12, 2011Start with great rawmaterials!
  • 58. Engage  on  an  emoFonal  level   through  storiesMonday, December 12, 2011Expose the stories behind a collection, and make them relatable to users. Use feedback to create narratives (as in Old Weather, where every entry moves the ship along on a map).
  • 59. Appeal  to  the  user’s beer  natureMonday, December 12, 2011We have found that participation increases dramatically when we frame our calls for participation in terms of helping the library. Frame it the same way you would any other volunteer opportunity, evenif it’s one that only lasts 10 seconds.
  • 60. DemysFfy  the  purposeMonday, December 12, 2011People want to participate in projects they understand. Practice your “elevator pitch” for your project: describe it in the time it takes to go ten floors in an elevator with someone. People don’t get excitedabout typing, but they will get excited about participating in the building of an important historical research tool.
  • 61. Make  the  task   as  small  as  possibleMonday, December 12, 2011 This one can’t be stressed enough: pay extremely close attention to exactly what action you’re asking people to do, and make the task as discrete as possible. If the project involves transcribing apage of text, ask participants to transcribe a sentence, or a line, or even a single word. Complicated tasks with multiple steps run the risk of ending half-complete.
  • 62. Encourage  conFnuaFonMonday, December 12, 2011 Once the tasks are broken down into small enough pieces, completing one will feel like a bite-size morsel that leaves the participant wanting more. Thank the participant immediately for theircontribution, then immediately ask them to contribute a bit more.
  • 63. Lower  the  barriers  to   parFcipaFonMonday, December 12, 2011If at all possible, allow immediate and anonymous contribution. It can definitely be useful to get users to register and sign in, so that you can reward top participants and track participation. But a sign-up page can be a barrier that may discourage the casual participant. A far better approach is to allow immediate participation without registration, and passively communicate the benefits of signing upas the user proceeds.
  • 64. Encourage  a  feeling  of  shared   ownershipMonday, December 12, 2011While critics of Wikipedia claim that anyone can enter false or vandalizing information, it’s heartening that the converse is true: anyone can also correct and repair bad information. By allowing otherusers to proofread and correct what’s previously been entered, you give participants a sense of pride that this is their “neighborhood” and it should be looked after.
  • 65. Show  results  immediatelyMonday, December 12, 2011 This is another critical one. When you’re collecting input from participants, don’t send the fruits of their labor off to some unseen holding queue; instead, post the result proudly as completed. In our“What’s on the Menu?” project, every time a patron transcribes a dish off of a menu, the name of that dish becomes a clickable link leading to a page showing all menus where that dish appears andfacts about it (earliest and latest appearances, high and low prices, etc.). If the dish was incorrectly transcribed, it can always be corrected later. For us, it was far more important to treat the contributionas official the moment it was transcribed, allowing users to see their transcription become part of the research tool instantly.
  • 66. Place  the  project  in  contextMonday, December 12, 2011Don’t try to be the center of the universe; link to other reference sources. On the NYPL’s menu project, at the moment a new dish is transcribed, a page for that dish is created which in turn containslinks to canned searches on other sites from Google to MenuPages to the library catalog, encouraging immediate exploration elsewhere.
  • 67. Play  gamesMonday, December 12, 2011The short “participate, get feedback” cycle we’re describing here lends itself extremely well to game dynamics. If possible, keep score, and give top participants some sort of public recognition.
  • 68. Reward  effortMonday, December 12, 2011 If it’s possible to keep track of who’s participating, give rewards. Hold a special reception with refreshments in your library, and only give the invitation to online participants. If you’re not trackingthe identity of participants, make sure the messaging you display is loaded with gratitude.
  • 69. Report  resultsMonday, December 12, 2011Let users know how the project is progressing. If the goal is to transcribe a collection, show how many documents are in that collection, and how many have been completed. Show progress bars toindicate how far you’ve come and how far there is to go. If you’re using public participation to create a research tool, use a blog or social media to report how that research has been used by historians,authors or other researchers and ink to their work.
  • 70. Share  the  fruits  of  laborMonday, December 12, 2011 When content is publicly created, make the resulting product publicly available. If the goal is to create a database of some sort, make the entire database available for download, or expose data withan Application Programming Interface (API) and encourage anyone to create “mashups” of your data. Promote any works that people derive from your data on your site or blog, and encourage others todo the same.
  • 71. Build  a  communityMonday, December 12, 2011 Getting patrons involved in a project is an ideal opportunity to unite people with a common interest around your collections. Use social networks, a blog with comments, and/or an online forum tobuild a conversation with the people who are you top users. Listen to feedback, take suggestions, and point out interesting findings.
  • 72. Thank  you! Presented  to  the  Powerhouse  Museum 8  December  2011 Michael  Lascarides Senior  Manager  for  Web  IniFaFves,  NYPL @mlascarides  /  @nypl michaellascarides@nypl.orgMonday, December 12, 2011

×