NYPL Labs @ Wiki ♡ Maps 2015

NYPL Labs @ Wiki ♡ Maps 2015
Helsinki, Finland, February 5, 2015

Transcript

1. mauricio giraldo arteaga
   @mgiraldo
   nypl labs
   a few things we’ve learned so far
   wiki ♥ maps , helsinki, february 2015
   

   View Slide

2. hei
   

   View Slide

3. my name is mauricio
   

   View Slide

4. View Slide

5. View Slide

6. NYPL Labs
   

   View Slide

7. View Slide

8. View Slide

9. View Slide

10. we’ve been at it for 3+ years
    

    View Slide

11. a few things we’ve learned so far
    

    View Slide

12. disclaimer
    

    View Slide

13. a few things we’ve i’ve learned so far
    

    View Slide

14. four things
    

    View Slide

15. practical
    

    View Slide

16. View Slide

17. start with a prototype
    

    View Slide

18. View Slide

19. View Slide

20. View Slide

21. View Slide

22. View Slide

23. View Slide

24. View Slide

25. menus.nypl.org
    

    View Slide

26. 200k dishes in 13k menus
    

    View Slide

27. made the case for NYPL Labs
    

    View Slide

28. it started with a prototype
    

    View Slide

29. View Slide

30. View Slide

31. View Slide

32. View Slide

33. View Slide

34. View Slide

35. View Slide

36. View Slide

37. “wouldn’t it be cool if…?”
    

    View Slide

38. View Slide

39. View Slide

40. View Slide

41. A FEW DAYS later…
    

    View Slide

42. View Slide

43. View Slide

44. distill the task to its critical components
    

    View Slide

45. prototypes help determine viability
    

    View Slide

46. prototypes help communicate the idea
    

    View Slide

47. –@mikeindustries
    “a prototype is worth a thousand meetings”
    

    View Slide

48. View Slide

49. View Slide

50. “great! it’s just polish now, right?”
    

    View Slide

51. View Slide

52. “polish” takes (a lot of) time
    

    View Slide

53. View Slide

54. View Slide

55. 3 months later…*
    *REAL NUMBER
    

    View Slide

56. View Slide

57. View Slide

58. stereo.nypl.org
    

    View Slide

59. View Slide

60. View Slide

61. View Slide

62. still, three months is not that long
    when you’re used to year-long projects
    

    View Slide

63. …and polish is good
    

    View Slide

64. LATER that day at 1:00AM…
    

    View Slide

65. View Slide

66. View Slide

67. so far 47,000 images created
    

    View Slide

68. another “smaller” example
    

    View Slide

69. View Slide

70. View Slide

71. View Slide

72. View Slide

73. View Slide

74. View Slide

75. took about 2 weeks
    

    View Slide

76. spacetime.nypl.org
    

    View Slide

77. A FEW HOURS later…
    

    View Slide

78. View Slide

79. a good problem to have?
    

    View Slide

80. also, polish can wait
    

    View Slide

81. View Slide

82. View Slide

83. could use a redesign
    

    View Slide

84. View Slide

85. View Slide

86. View Slide

87. 1.1 million more dishes
    and that’s even though we’re not scanning menus as often
    

    View Slide

88. curatingmenus.org by @katie_rawson and @trevormunoz
    

    View Slide

89. @_BadTaste_ by @bibliotechy
    

    View Slide

90. polish works
    

    View Slide

91. “polish” is design
    

    View Slide

92. …but it takes time
    

    View Slide

93. “ok… so i just factor this in my planning”
    

    View Slide

94. View Slide

95. everything takes longer than anticipated
    

    View Slide

96. people are bad at making estimates*
    *S. Grimstada, M. Jørgensena, 2007; I. Newby-Clark, M. Ross, R. Buehler, D. Koehler, D.
    Griffin, 2007; V. Mahnič, T. Hovelja, 2012; and more…
    

    View Slide

97. (yeah, even in “agile development”)
    

    View Slide

98. people cannot estimate
    what they have not done
    

    View Slide

99. –@jasonfried
    “planning is guessing”
    

    View Slide

100. legacy website redesign
     ca. 2005
     

     View Slide

101. View Slide

102. View Slide

103. View Slide

104. “let’s take 90 days to redesign this”
     

     View Slide

105. 
     (huge red flag)
     

     View Slide

106. there are always surprises
     usually not the good kind of surprises
     

     View Slide

107. View Slide

108. View Slide

109. View Slide

110. View Slide

111. “we have to have this feature”
     

     View Slide

112. 18 months later…
     

     View Slide

113. View Slide

114. View Slide

115. View Slide

116. View Slide

117. View Slide

118. View Slide

119. View Slide

120. View Slide

121. digitalcollections.nypl.org
     

     View Slide

122. start with a scope or a deadline
     

     View Slide

123. …but not both
     

     View Slide

124. don’t take too long
     

     View Slide

125. –@schuyler
     “if you're proud of your code
     you waited too long to ship it”
     

     View Slide

126. …but take as long as it needs
     

     View Slide

127. …and prepare for surprises
     

     View Slide

128. View Slide

129. hackathons are starting points
     

     View Slide

130. View Slide

131. View Slide

132. year
     

     View Slide

133. street names
     year
     

     View Slide

134. use type
     street names
     year
     

     View Slide

135. use type
     street names
     name
     year
     

     View Slide

136. material
     use type
     street names
     name
     year
     

     View Slide

137. material
     use type
     street names
     name
     class
     year
     

     View Slide

138. material
     use type
     street names
     address
     name
     class
     year
     

     View Slide

139. material
     use type
     street names
     address
     floors
     name
     class
     year
     

     View Slide

140. material
     use type
     street names
     address
     floors
     name
     class
     year
     skylights
     

     View Slide

141. material
     use type
     street names
     address
     floors
     name
     class
     year
     skylights
     backyards
     

     View Slide

142. material
     use type
     street names
     address
     floors
     name
     class
     geo location
     year
     skylights
     backyards
     

     View Slide

143. footprint
     material
     use type
     street names
     address
     floors
     name
     class
     geo location
     year
     skylights
     backyards
     

     View Slide

144. footprint
     material
     use type
     street names
     address
     floors
     name
     class
     geo location
     year
     skylights
     backyards
     

     View Slide

145. View Slide

146. “wouldn’t it be cool if…?”
     

     View Slide

147. View Slide

148. View Slide

149. can we automate this?
     

     View Slide

150. View Slide

151. View Slide

152. View Slide

153. View Slide

154. View Slide

155. View Slide

156. View Slide

157. View Slide

158. View Slide

159. FIVE WEEKS later…
     

     View Slide

160. View Slide

161. github.com/NYPL/map-vectorizer
     

     View Slide

162. View Slide

163. View Slide

164. ~80k building footprints in a day
     instead of years
     

     View Slide

165. View Slide

166. this resulted in a new question
     

     View Slide

167. “is the output any good?”
     

     View Slide

168. …so we did a prototype
     

     View Slide

169. View Slide

170. View Slide

171. View Slide

172. View Slide

173. buildinginspector.nypl.org
     

     View Slide

174. 2 MONTHS later…
     

     View Slide

175. View Slide

176. View Slide

177. View Slide

178. View Slide

179. 84%: YES
     7%: FIX
     or about 91% good enough
     

     View Slide

180. we ♥ our contributors
     

     View Slide

181. we ♥ our contributors
     

     View Slide

182. …so we did more prototypes!
     

     View Slide

183. View Slide

184. View Slide

185. 1 million classifications so far!
     ~18 months since launch
     

     View Slide

186. View Slide

187. View Slide

188. View Slide

189. View Slide

190. …and it all started in a hackathon
     

     View Slide

191. recap
     

     View Slide

192. View Slide

193. start with a prototype
     

     View Slide

194. start with a prototype
     polish takes time
     

     View Slide

195. start with a prototype
     polish takes time
     everything takes longer than anticipated
     

     View Slide

196. start with a prototype
     polish takes time
     everything takes longer than anticipated
     hackathons are starting points
     

     View Slide

197. thank you
     ♥
     images from: NYPL digital collections - Wikimedia Commons - Flickr user wallyg - Giphy - John Resig - Peter Leonard
     mauricio giraldo arteaga
     @mgiraldo
     nypl labs
     

     View Slide