forked from LibrarySimplified/library-simplified-website
-
Notifications
You must be signed in to change notification settings - Fork 0
/
project-design.html
executable file
·552 lines (464 loc) · 35.2 KB
/
project-design.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
<!DOCTYPE html>
<html language="english">
<head>
<meta charset="utf-8">
<title>Library Simplified · Project Design</title>
<meta name="About" content="Library Simplified is jointly funded by The New York Public Library and Institute for Museum and Library SciencesIMLS. The Product Owner (PO) for the Library Reading Experience is charged with proposing ways in which to employ technology, innovation in library policies, and the full range of library offerings to deliver a better experience to more patrons. The PO leads a small highly skilled technical team, and works in concert with partner libraries to analyze usser and library needs as well as the industry and technology landscape in order to develope a minimum viable product solution."/>
<link rel="icon" href="favicon.png">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<!-- Google Fonts (more: http://www.google.com/fonts) -->
<!-- Main Font -->
<link href="http://fonts.googleapis.com/css?family=Open+Sans:300,400,700" rel="stylesheet">
<!-- Headings -->
<link href="http://fonts.googleapis.com/css?family=Source+Sans+Pro" rel="stylesheet">
<!-- Handwritten -->
<link href="http://fonts.googleapis.com/css?family=Marck+Script" rel="stylesheet">
<!-- Countdown, Pricing Table Price Tag -->
<link href="http://fonts.googleapis.com/css?family=Oswald:300,400,700" rel="stylesheet">
<!-- Logo -->
<link href="http://fonts.googleapis.com/css?family=Cantora+One" rel="stylesheet" type="text/css">
<!-- CDN Bootstrap & FontAwesome -->
<link href="http://netdna.bootstrapcdn.com/bootstrap/3.0.0/css/bootstrap.min.css" rel="stylesheet">
<link href="http://netdna.bootstrapcdn.com/font-awesome/3.2.1/css/font-awesome.min.css" rel="stylesheet">
<!-- CSS Libraries -->
<link href="assets/css/animate.min.css" rel="stylesheet">
<link href="assets/css/bxslider.css" rel="stylesheet">
<link href="assets/css/magnific-popup.css" rel="stylesheet">
<!-- Theme Specific CSS -->
<link href="assets/css/styles.css" rel="stylesheet">
<link href="assets/css/custom.css" rel="stylesheet">
<!-- Predefined Color Scheme -->
<link href="assets/css/colors/blue.css" rel="stylesheet" id="colors">
</head>
<body>
<!-- Google Tag Manager -->
<noscript><iframe src="//www.googletagmanager.com/ns.html?id=GTM-RKWC"
height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-RKWC');</script>
<!-- End Google Tag Manager -->
<header id="header" class="navbar">
<div class="container">
<div class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
<span class="sr-only">Skip navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand logo" href="index.html">Library Simplified</a>
</div>
<nav class="collapse navbar-collapse" role="navigation">
<ul class="nav navbar-nav">
<li class="dropdown">
<a href="about.html">About</a>
<ul class="dropdown-menu">
<li><a href="OPDS.html">OPDS</a></li>
<li><a href="EPUB.html">EPUB</a></li>
<li><a href="Readium.html">Readium</a></li>
<li><a href="accessibility.html">Accessibility</a></li>
<li><a href="news-and-events.html">News and Events</a></li>
<li><a href="faq.html">FAQ</a></li>
</ul>
</li>
<li class="dropdown">
<a href="/">Community</a>
<ul class="dropdown-menu">
<li><a href="community.html">Our Community</a></li>
<li><a href="get-involved.html">Getting Involved</a></li>
</ul>
</li>
<li class="dropdown">
<a href="/">Implementors</a>
<ul class="dropdown-menu">
<li><a href="implementorsamigos.html">Amigos</a></li>
<li><a href="implementorscalifa.html">Califa</a></li>
<li><a href="implementorsdatalogics.html">Datalogics</a></li>
<li><a href="lyrasis.html">Lyrasis</a></li>
</ul>
</li>
<li class="dropdown">
<a href="IMLS.html">Grant Funded Projects</a>
<ul class="dropdown-menu">
<li><a href="project-design.html">IMLS: Library Simpliifed</a></li>
<li><a href="LEAP-project-design.html">IMLS: LEAP Project Design</a></li>
<li><a href="consortia-project-design.html">IMLS: SimplyE for Consortia</a><li>
</ul>
</li>
<li class="dropdown">
<a href="/">SimplyE</a>
<ul class="dropdown-menu">
<!--<li><a href="productbacklog.html">Product Backlog</a></li>
<li><a href="iOSUItour.html">Mobile: iOS ver 1.0</a></li>
<li><a href="androidtour.html">Mobile: Android ver 1.0</a></li>-->
<li><a href="deployinstruction.html">Deploying the application</a></li>
<li><a href="clientappfaq.html">Mobile Client application how to</a></li>
</ul>
</li>
</ul>
</nav>
</div>
</header><!-- .navbar-fixed-top -->
<div class="page-top">
<div class="container">
<h1 class="page-top-header">Project Design</h1>
<ol class="breadcrumb">
<li><a href="index.html">Home</a></li>
<li class="active">Project Design</li>
</ol>
</div>
</div>
<div class="container" id="main">
<div class="row">
<div class="col-md-3">
<div id="sidebar" class="affix" role="complementary">
<ul class="nav">
<li><a href="#overview">Overveiw</a></li>
<li><a href="#phase-1">Fact gathering and analysis</a></li>
<li><a href="#phase-2">Architecture and testing </a></li>
<li><a href="#phase-3">Build</a></li>
<li><a href="#phase-4">Implementation and Assessment</a><li>
<li><a href="#communication">Communication Plan</a><li>
<li><a href="#evaluation">Evaluation</a><li>
<li><a href="#resources">Resources</a><li>
</ul>
</div><!-- .affix -->
</div>
<div class="col-md-9">
<div>
<h2 id="overview"></h2>
<p class="lead">
<strong>Library Simplified</strong> is jointly funded by <a href="http://www.NYPL.org" data-toggle="tooltip" title="The New York Public Library" target="_blank">NYPL</a> and <a href="http://www.imls.org" data-toggle="tooltip" title="Institute for Museum and Library Sciences" target="_blank">IMLS</a>. This funding supports a full-time position at NYPL: “Product Owner (PO) for the Library Reading Experience.” The PO, is charged with proposing ways in which to employ technology, innovation in library policies, and the full range of library offerings to deliver a better experience to more patrons. The PO leads a small technical team, and works in concert with partner libraries to analyze the digital assessment findings and move the design process forward. Library Simplified will include four phases of work with major milestones and deliverables at the end of each: (I) Fact gathering and analysis, (II) Architecture and testing (III) Build and (IV) Implementation and assessment.
</p>
<h3><strong>Project Design</strong></h3>
<hr />
<h4 id="phase-1"><Strong>Phase 1:</strong> Fact gathering and analysis</h4>
<p>
There are three parts to the fact gathering and analysis of Library Simplified. The three parts are designed to clearly document the expereinces of users and non-users, the system infterfaces and technology architectures that deliver those expereinces and analyze the needs and wants of users and how those are met or not met.
</p>
<ul class="nav nav-tabs tab-header">
<li class="active"><a href="#part1" data-toggle="tab"><i class="icon-user icon-large"></i> Part 1 </a></li>
<li><a href="#part2" data-toggle="tab"><i class="icon-search icon-large"></i> Part 2 </a></li>
<li><a href="#part3" data-toggle="tab"><i class="icon-cogs icon-large"></i> Part 3 </a></li>
</ul>
<div class="tab-content">
<div class="tab-pane active" id="part1">
<h5>User Experience (UX) Assessment</h5>
<p>
<h6>Mapping the User Journey -</h6>
<p>The team will document all relevant interaction points at all partner libraries, the end-to-end journey of a user borrowing an e-book.</p>
<h6>Heuristic Evaluation -</h6>
<p> The team, assisted by expert consultant(s) as needed, will conduct an audit of all current screen-based catalog/reading interfaces by assessing them in terms of usability heuristics and identifying "trouble spots" in the current design.
</p>
<h6>Library Policy ‘pain’ points –</h6>
<p>This will demonstrate how and for whom current library policies create “pain points; providing key support for senior library decision makers evaluating the pros and cons of policy changes.
</p>
<h6>Storyboard Experiences -</h6>
<p>The team will create visual representations (storyboards) of proposed new directions intended to serve as a foundation for further prototyping. These UX Storyboards will describe the ideal process.</p>
</p>
</div>
<div class="tab-pane" id="part2">
<h5>Needs/Wants of Users and Non-users</h5>
<p>
The project team will engage directly with users throughout the first two phases to test hypotheses and gather input. Since the first goal of this project is to build audience, at all stages it will be critical to gather insights from non-users. For example, in January 2013 when NYPL’s Office of Strategic Planning sought feedback on a new Netflix-type card, users in focus groups conveyed that they wanted to be able to check out at least 10 items and expressed anxiety about fines but also a belief that they were important to teach personal responsibility. Many non-users, on the other hand, indicated they would be happy to sacrifice the number of items available (e.g. accepting a card with a 3-5 item borrowing limit) if that meant a promise that they would never incur fines. These critically different perspectives must be considered and addressed throughout the duration of the project.
</p>
<p>
With that in mind, the project team will be tasked to conduct at least the following analysis of users and non-users:
</p>
<h6><a href="roll-up.html">Survey Data roll up and gap assessment</a> -</h6>
<p>
NYPL’s Office of Strategic Planning’s User Insights Group has conducted large-scale surveys with user and non-user quantitative and qualitative data. Similar research completed by partner libraries or published elsewhere (American Community Survey, Pew) will also be included. </br>
<ul>
<li><a href="LSsurvey1.html">Library Simplified Survey One </a></li>
<li><a href="LSsurvey2.html">Library Simplified Survey Two </a></li>
</ul>
<h6>User & Non-User Ethnographies -</h6>The team will conduct a small field study of selected circulating branch libraries and online users to explore the behaviors and attitudes of current users, with a particular focus on policy issues and related UX design implications.
<h6>Personas of users and non-users -</h6> The team will also develop user personas that capture the needs and wants of the most largest and most important groups of potential users, including heavy media consumers & ereaders; and youth and students.
</p>
</div>
<div class="tab-pane" id="part3">
<h5>Systems Architecture analysis</h5>
<p>
<h6>Architectural Schematics of/for all Partners -</h6>
<p>
The Product Owner will work with partner project leads to develop a simple but comprehensive annotated schematic diagram of the IT architecture for each partner library.
</p>
<h6>Overlay of Data sources and feeds -</h6>
<p>
A key component of the architectural diagnostic will be to understand the potential sources of patron and collections data from an <a data-toggle="tooltip" title="ILS: Integrated Library System" target="_blank">ILS</a>, e-content from vendors, and supplemental UGC and/or recommendation from other third party products. This overlay, which will sit “on top” of schematic diagrams, will capture not what the systems are but also how they interact, a critical first step toward proposing ways they can be streamlined.</p><h6>Market Scan -</h6>
<p>
The Product Owner and team will review products that are available to libraries but not in use at all/any of the partners. This work will come late in the Fact gathering/Analysis phase so that it can focus on exploring strong hypotheses about how new products could be integrated to satisfy unmet needs and wants.
</p>
<p>
<strong>Note:</strong> At the end of the Phase I, the team will produce and circulate a comprehensive report with all the findings and raw data. Although the team will likely have begun to develop ideas about how to solve for the user stories gathered, this report will stop short of recommendation or proposed product design. It will instead create the robust foundation for the next phase, which will be to design the actual product offering.
</p>
</div>
</div>
<hr />
<h3 id="phase-2"><Strong>Phase 2:</strong> Architecture and testing </h3>
<p>
During Phase II, the team will attempt to sketch a wide variety of products that could be built and test them against user stories and user personas to identify the most impactful design. This will be an iterative process and will include engagement with a variety of external technology experts; partners will come together physically to discuss the different approaches.
</p>
<ul class="nav nav-tabs tab-header">
<li class="active"><a href="#2part1" data-toggle="tab"><i class="icon-thumbs-up icon-large"></i>  Partner Review and Assesment </a></li>
<li><a href="#2part2" data-toggle="tab"><i class="icon-search icon-large"></i>  Test and Evaluate</a></li>
</ul>
<div class="tab-content">
<div class="tab-pane active" id="2part1">
<h5>Partner review and assesment of options</h5>
<p>
Partners will be asked to review the options through the lens of three main factors,
</p>
<ol>
<li>Feasibility (i.e. does the partner feel confident that, if built, they could implement the proposed product at their library),</li>
<li>Willingness to adopt implied policies,</li>
<li>Satisfaction with goals.</li>
</ol>
<p>
The project team will review partner feedback, and during an in-person event, build consensus to go forward with a product build that will have the broadest impact. The team will then develop detailed technical documentation of the proposed solution that can serve as a roadmap for an in-house software development effort or become the basis of outsourced contract development work.
</p>
</div>
<div class="tab-pane" id="2part2">
<h5>Implement and test</h5>
<p>
Each partner library will be responsible for implementing the test product at their institution and will bear any associated costs (e.g. securing needed data feeds from ILS or vendors). As such, partners are not formally committing to implement the product, just to go through steps (I) and (II) and then try to locate resources customized for their institution. Partner activities and contributions will be managed using an adapted Agile methodology. All partners will have access to a living online work plan that will be owned by the Product Owner but maintained and updated by the owner of each ‘to-do’. Project leads at partner libraries will convene on regular calls, not less than once a month but more frequently during the first six months of the grant (the planning and architecture phases). Partners will also meet in person at least two times during the project, for a kick-off and during the later portion of the architecture phase.
<p>
Additional elements and deliverable of the product could be optional and adopted by some partners and not others. For example, any physical component that proves too radical for one library’s senior management in terms of policy (e.g. no fines) or to costliness (e.g. delivery by mail) but other libraries may want to use this product as a vehicle for experimentation. The delivery of a better ebook discovery and access experience should be considered the base case, from which additional branches/ offerings may be added (e.g. by mail) as/if libraries are able and willing to support them. At the close of Phase II, the project team will deliver a final proposal, including product vision and detailed functional specification (RFP or similar).
</p>
</div>
</div>
<hr />
<h3 id="phase-3"><strong>Phase 3:</strong> Build</h3>
<p>
During this phase the Product Owner will identify and commission the most cost effective way to build the chosen product, estimating the time and cost associated with building the project in-house using staff resources and seeking quotes from vendors to compare the cost of outsourcing. The team will also look for opportunities to build/accelerate parts of the build by convening hackathons or codes sprints, drawing from the local developer pool in New York City hosting at one of our partner libraries, including those in Silicon Valley, and/or seek support and contributions, as appropriate, from existing industry developer communities such as Code4Lib.
</p>
<ul class="nav nav-tabs tab-header">
<li class="active"><a href="#3part1" data-toggle="tab"><i class="icon-code-fork icon-large"></i> Middleware/Application Backend</a></li>
<li><a href="#3part2" data-toggle="tab"><i class="icon-tablet icon-large"></i> Client Applications</a></li>
</ul>
<div class="tab-content">
<div class="tab-pane active" id="3part1">
<h6>Middleware/Application Backend</h6>
<strong> Normalized Catalogue/Content Inventory Application Programing Interface (API)</strong>
<p>
During this phase the project team will prepare for integration by vetting and adopting new policies and practice suggested by the product visions and by preparing any technical enablers that will be required for implementation. In addition to the existing <a data-toggle="tooltip" title="API: Application Programing Interface" target="_blank">ILS</a>, e-content vendor platform (i.e. 3M, Baker & Taylor), and catalog frontend being in place, several more pieces of infrastructure would be brought together to make the existing components work well with one another and provide a better experience to users. The project would develop piece of middleware to coordinate ebook inventory and activity between multiple vendors across a common API, enabling 3M, Overdrive, and Baker & Taylor to be accessed and served in a uniform way. This middleware would sit between the ILS, ebook vendors (via their APIs), and the Library Simplified frontend, pulling the aggregate list of titles from the catalog, inventory details from the vendors, and facilitate user’s transaction to check out a title from any vendor. Library Simplified’s frontend would be powered by the same data feeds that drive existing catalog frontends coming out of the ILS, as well as the vendor management middleware.
</p>
<strong> Normalized Recommendation Application Programing Interface (API)</strong>
<p>
The data feeds and APIs that power this user-facing frontend would be implemented first for the web, but would also enable the creation of integrated Library Simplified native apps for mobile devices and some dedicated e-readers like the Kindle Fire and the Nook. This frontend would utilize a third-party recommendation engine, such as Hunch or LibraryThing, which would index the ILS’s corpus of ebooks, and with a little knowledge about each user (what it needs will vary depending on the recommendation engine or engines used). The recommendation engine would also interface with the vendor middleware to determine titles a patron might be interested in reading that are immediately available, will be available in a day or so, or for which the user might wish to join a longer hold queue. This common discovery interface could power more than just the e-reading experience, but discovery for all of Library Simplified’s offerings.
</p>
</div>
<div class="tab-pane" id="3part2">
<h6><i class="icon-tablet 2x"></i> Client Applications</h6>
<strong>Web/Connected Client Application</strong>
<p>
Ebook delivery will be offered two ways. To facilitate immediate reading, without undergoing the arduous process of transferring an ebook to a device, the project will follow the example of OpenLibrary’s browser-based lending system and build a HTML5 browser-based reader that can be used on any browser connected to the internet, optimized both for tablets and smartphones. Checking out an e-book to read in the browser will result in the book being checked out to a server controlled by the library with the digital rights management (<a data-toggle="tooltip" title="DRM: Digital Right Management" target="_blank">DRM</a>) certificate being tied to the library server for the lending period. When a user requests a page in the book, that page will be rendered on-the-fly on the server, and sent to the user’s browser. When a user moves to a new page, the service copy of the previous page will be deleted from the server so no more than one page is available at any given time, but offering all the features of a standard e-reader including searching the full text of the book.
</p>
<strong>Native Client Application</strong>
<p>
While the browser-based model works only when connected to the internet, it doesn’t replace reading on a dedicated app that can be used offline. Delivery of ebooks can be arduous due to the complex requirements of the underlying DRM. Major sellers like Amazon and Apple own the process from end-to-end and have created the illusion of no DRM within that ecosystem. Library Simplified will do something similar by taking advantage of the existing e-reader software on devices which is compatible with libraries and making the delivery experience to those apps seamless via the checkout API of the vendor middleware, and serving the book to the user via a special URL. By visiting that URL to pick up the book, they’ll be presented with a list of options, and by clicking on the user’s preferred reading app, Library Simplified will trigger via special URLs to tell those apps to access the books directly, without any special steps. This leaves the possibility open for a set of Library Simplified native apps, but makes immediately actionable the seamless checkout of ebooks to smartphones, tablets, and some dedicated readers without needing to build specific apps for each platform.</br>
</p>
</div>
</div>
<hr />
<h4 id="phase-4"><strong>Phase 4:</strong> Implementation and Assessment</h4>
<p>
By the time the technical build of the new product is complete, project managers at NYPL and each partner library should have prepared their library for integration, meaning that new policies and/or practices implied by the product have been approved or adopted and that technical infrastructure is ready to integrate. As the product is rolled out, local marketing campaigns will advertise the tools and encourage use.
</p>
<hr />
<h3 id="communication"><strong> Communication Plan</strong></h3>
<p>
In parallel to the technical build, the project leads at partner libraries will prepare and implement a communications plan focused on reaching all libraries that may be interested in implementing the product. This communication will include dissemination of the final product vision as well as detailed information and instructions implementation requirement. This communications push will leverage the deep industry knowledge and networks of the partner libraries include dissemination by taking advantage of channels such as ReadersFirst, listservs provided by ALA, PLA, ULC, DPLA, and other marketing opportunities with state and local library associations. The partners will seek to speak about the project and encourage other libraries to implement it at conferences and directly with peer institutions. The goal will be to ensure that all libraries are aware of the opportunity and that as many as possible choose to adopt the product.
</p>
<p>
Each partner will also prepare a marketing plan to make the public aware of the product once it is launched by their libraries. These will undoubtedly leverage low-cost marketing approaches like using the library's social media presence, but will also purchase paid marketing to the degree resources permit. Partners will be encouraged, but not required, to use their partner stipend to seed these marketing budgets and to supplement these activities in other ways.
</p>
<hr />
<h3 id="evaluation" ><strong>Evaluation</strong></h3>
NYPL and partner libraries will pool data about use and qualitative feedback from users, staff, and other stakeholders to assess the degree to which this project is meeting its goals. Evaluation and assessment will measure the following objectives:
<ul>
<li>The project has been successful in disproportionately attracting new users</li>
<li>The project has succeeded in driving use (and to what extent) </li>
<li>The project has accelerated a rise in use of electronic collections as compared to the national average over the same period</li>
<li>There is a deeper understanding of the impacts of alternative policies tested through this project (including for example, return rates, holds pick-ups)</li>
<li>Product users are more satisfied with their experience using the library than users who access the libraries resource through traditional pre-existing channels </li>
<li>To understand and document opportunities to improve core systems (other than the product this project creates)</li>
</ul>
</p>
<p>
Evaluation of this project will be based primarily on use, but will also include quantitative and qualitative feedback from users and stakeholders. There will be six main inputs to assessment:
<ol>
<li>Use data reported by partner and participating libraries sent on a quarterly basis. (At any time throughout the first year, partner libraries and other invested stakeholders may request data and/or findings from the NYPL team. At the end of the first year after product launch, all use data will be included in one comprehensive summative analysis that will be made publicly available.</li>
<li>Demonstrated user behavior from embedded analytics in the product </li>
<li>Self-reported use data and feedback from participating non-partner libraries. (At a minimum, the project team will work to identify (a) the total number of libraries that have adopted the product and their population served and (b) the total number of users of the product (likely available from embedded analytics and therefore not dependent on survey response).</li>
<li>Insights from user direct testing, conducted as part of the product design phase. (The primary purpose will be to compare and improve competing prototypes, but the team will also use these interactions with users to glean insights, especially qualitative.)</li>
<li>Quantitative and qualitative feedback from user via feedback box, surveys and focus groups. (NYPL User Insights team will lead a process with partner libraries to gather summative and formative feedback from users and non-users)</li>
<li>Input from other stakeholders including partner participating and other libraries, and industry partners, including interviews, a partner staff survey, and a partner retrospective or ‘post mortem’.</li>
</ol>
All data will be analyzed by NYPL’s Office of Strategic Planning. Both the findings and the raw data will also be made available to partners and open for public dissemination.
</p>
<hr />
<h3><strong>Resources</strong></h3>
<div class="well">
<h5>Product Development / Engineering</h5>
<p>
Product Owner / Engineering Manager - James English</br>
Application Architect, NYPL - Leonard Richardson</br>
iOS Client - Winnie Quinn / Sam Tarakajian - NYPL
Android Client - Mark Raynsford - Independent, UK
</p>
<h6><i class="icon-beaker"></i> NYPL Labs</h6>
<p>
Based at The New York Public Library's landmark central branch on 42nd Street, NYPL Labs is an award-winning design and technology team working to re-imagine The Library for the Internet age. </p><a href='http://www.nypl.org/collections/labs' target="new"/> Learn more...</a>
</p>
<p>
Mauricio Giraldo - UX Designer and Labs Engineering Manager
</p>
<h6><i class="icon-group"></i><strong>  Other Contributors</strong></h6>
<p>
Ben Anderman, Raduz Benicky, Juan Corona - Evident Point, Corp</br>
Hadrien Gardeur - Feedbooks, SAS </br>
Mikael Menu, Jean-Marie Geofroy - Mantano, SAS</br>
</p>
</div>
</div><!-- .col-md-9 -->
</div>
</div>
</div><!-- .container -->
<footer id="footer">
<div class="newsletter">
<div class="container">
<div class="row">
<div class="col-md-8">
<a href="http://eepurl.com/bo9K3T"><h3 class="title"><i class="icon-envelope-alt"></i> Subscribe to updates</h3></a>
<span class="lead">We will only send you good stuff. Promise!</span>
</div>
<!--<div class="col-md-4">
<form class="input-group small" method="post" action="">
<input type="text" class="form-control" placeholder="Your Email Address" />
<div class="input-group-btn">
<button class="btn btn-default" type="button">Sign Up <i class="icon-angle-right"></i></button>
</div>
</form>
</div>-->
</div>
</div>
</div>
<div class="footer-top">
<div class="container">
<div class="row">
<div class="col-md-4">
<div class="social-networks">
<a href="https://www.facebook.com/nypl"><i class="icon-facebook"></i></a>
<a href="https://twitter.com/nypl"><i class="icon-twitter"></i></a>
<a href="https://plus.google.com/u/0/+newyorkpubliclibrary/posts"><i class="icon-google-plus"></i></a>
<a href="http://nypl.tumblr.com/"><i class="icon-tumblr"></i></a>
<a href="https://www.pinterest.com/nypl/"><i class="icon-pinterest"></i></a>
<!-- <a href=""><i class="icon-linkedin"></i></a>
<a href=""><i class="icon-dribbble"></i></a>
<a href=""><i class="icon-instagram"></i></a>
<a href=""><i class="icon-pinterest"></i></a>
<a href=""><i class="icon-youtube-play"></i></a>
<a href=""><i class="icon-rss"></i></a> -->
</div>
</div>
<div class="col-md-4">
<h6 class="title">About</h6>
<p>
We are a team of remarkable institutions doing great things. Get to know a little bit more <a href="about">about us</a>.
</p>
</div>
<div class="col-md-4">
<h6 class="title">Get in Touch</h6>
<address>
<i class="icon-map-marker"></i> <a class="lightbox-iframe" href="https://maps.google.com/maps?q=NYPL+5th+Ave+at+42nd+St,+New+York+City,+New+York&hl=en&t=v&hnear=5th+Ave+at+42nd+St,+New+York+City,+New+York" data-toggle="tooltip" title="Show on Google Maps">42nd Street 5th Avenue, New York City, United States</a><br />
<i class="icon-envelope"></i> <a href="mailto:[email protected]" data-toggle="tooltip" title="Email Us">[email protected]</a><br />
<i class="icon-phone"></i> +1 212 621 40520<br />
</address>
</div>
</div>
</div>
</div>
<div class="container footer-bottom">
<div class="footer-copyright">
<p>© 2013 by Olin. All Rights Reserved.</p>
</div>
</div>
</footer>
<a href="#" id="scrollToTop">
<i class="icon-angle-up icon-2x"></i>
</a>
<!-- Contact Popup (Modal) -->
<div class="modal fade" id="contact" tabindex="-1" role="dialog" aria-labelledby="myModalLabel" aria-hidden="true">
<div class="modal-dialog">
<div class="modal-content">
<div class="modal-header">
<button type="button" class="close" data-dismiss="modal" aria-hidden="true">×</button>
<h4 class="modal-title">We would love to hear from you</h4>
</div>
<div class="modal-body">
<p class="lead">
Ask us anything you want. We will get back to you during the work week.</strong>
</p>
<form name="contactform" id="contactform" class="margin-bottom-large" method="post" action="contactform.php">
<div class="row">
<div class="form-group col-md-6">
<label for="name">Name</label>
<input type="text" name="name" id="name" placeholder="" class="form-control" />
</div>
<div class="form-group col-md-6">
<label for="email">Email <span class="text-warning">*</span></label>
<input type="text" name="email" id="email" placeholder="" class="form-control" />
<div id="email_error_empty" class="error">Please enter your email address.</div>
<div id="email_error_invalid" class="error">Please enter a valid email address.</div>
</div>
</div>
<div class="form-group">
<label for="subject">Subject</label>
<input type="text" name="subject" id="subject" class="form-control" placeholder="" />
</div>
<div class="form-group">
<label for="message">Message <span class="text-warning">*</span></label>
<textarea name="message" id="message" cols="30" rows="10" class="form-control" placeholder=""></textarea>
<div id="message_error_empty" class="error">Please enter a message.</div>
<div id="message_error_invalid" class="error">Please check your message for any errors.</div>
</div>
<div id="mailsuccess" class="success">Your message has been sent successfully.</div>
<div id="mailfail" class="error">Sorry, error occured this time sending your message.</div>
<div class="margin-top-base">
<input type="submit" id="submit_contact_form" class="btn btn-primary" value="Send">
<small class="pull-right text-muted">* required</small>
</div>
<script src="assets/js/validation.js"></script>
</form>
<div class="row">
<div class="col-sm-6">
<h4 class="invert">Library Simplified</h4>
<address>
<i class="icon-map-marker"></i> the New York Public Library, 5th Ave at 42nd St, New York City, United States<br />
<i class="icon-map-marker"></i> 42nd Street and 5th Avenue, New York City, United States<br />
<i class="icon-envelope"></i> [email protected]<br />
<i class="icon-phone"></i> +1 212 621 0520<br />
</address>
</div>
</div>
</div>
</div>
</div>
</div>
<!-- JavaScript Libraries & jQuery Plugins -->
<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js"></script>
<script src="http://netdna.bootstrapcdn.com/bootstrap/3.0.0/js/bootstrap.min.js"></script>
<script src="assets/js/jquery.bxslider.min.js"></script>
<script src="assets/js/jquery.isotope.min.js"></script>
<script src="assets/js/jquery.fittext.js"></script>
<script src="assets/js/jquery.fitvids.js"></script>
<script src="assets/js/jquery.magnific-popup.min.js"></script>
<script src="assets/js/jquery.hoverdir.js"></script>
<script src="assets/js/validation.js"></script>
<script src="assets/js/theme.js"></script>
</body>
</html>