-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathslides.html
1836 lines (1593 loc) · 65.8 KB
/
slides.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
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<meta name="viewport" content="width=1024, user-scalable=no">
<title>You Gotta Keep 'em Separated: The Case for “Bento Box” Discovery Interfaces</title>
<!-- Required stylesheet -->
<link rel="stylesheet" href="deck.js/core/deck.core.css">
<!-- Extension CSS files go here. Remove or add as needed. -->
<link rel="stylesheet" media="screen" href="deck.js/extensions/goto/deck.goto.css">
<link rel="stylesheet" media="screen" href="deck.js/extensions/menu/deck.menu.css">
<link rel="stylesheet" media="screen" href="deck.js/extensions/navigation/deck.navigation.css">
<link rel="stylesheet" media="screen" href="deck.js/extensions/status/deck.status.css">
<link rel="stylesheet" media="screen" href="deck.js/extensions/scale/deck.scale.css">
<link rel="stylesheet" media="screen" href="deck.js/extensions/notes/deck.notes.css">
<!-- Style theme. More available in /themes/style/ or create your own. -->
<link rel="stylesheet" media="screen" href="deck.js/themes/style/simpleblack.css">
<!-- Transition theme. More available in /themes/transition/ or create your own. -->
<link rel="stylesheet" media="screen" href="deck.js/themes/transition/fade-and-no-transition.css">
<!-- Misc local styles that don't belong in the theme -->
<link rel="stylesheet" media="screen" href="styles.css">
<!-- Basic black and white print styles -->
<link rel="stylesheet" media="print" href="print_styles.css">
<!-- Required Modernizr file -->
<script src="deck.js/modernizr.custom.js"></script>
</head>
<body>
<div class="deck-container">
<!-- Begin slides. Just make elements with a class of slide. -->
<section class="slide">
<h1>You Gotta Keep ’em Separated
<div class="subtitle">The Case for Bento Box Discovery Interfaces</div>
</h1>
</section>
<section class="slide fade-in">
<h1>The Case</h1>
<div class="notes">
<p>So, I submit to you the following.</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/bento_lunch.png" />
<div class="notes">
<p>First the obligatory, here's where the bento box UI metaphor comes from. A Japanese lunch where</p>
</div>
</section>
<section class="slide ">
<img class="vcenter" src="code4lib2015_images/bento_lunch_2.png" />
<div class="notes">
<p>several different types of delicious food</p>
</div>
</section>
<section class="slide fade-out">
<img class="vcenter" src="code4lib2015_images/bento_lunch_3.png" />
<div class="notes">
<p>are subdivided into little compartments.</p>
</div>
</section>
<section class="slide fade-in">
<img class="vcenter" style="opacity: 0.4;" src="code4lib2015_images/bento_lunch.png" />
<h1>Bento ...</h1>
<div class="notes">
<p>Bento box.</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/michigan_bento.png" />
<div class="notes">
<p>And so here we have a search results UI where</p>
</div>
</section>
<section class="slide ">
<img class="vcenter" src="code4lib2015_images/michigan_bento_2.png" />
<div class="notes">
<p>results are subdivided</p>
</div>
</section>
<section class="slide fade-out">
<img class="vcenter" src="code4lib2015_images/michigan_bento_3.png" />
<div class="notes">
<p>into compartments by category,</p>
</div>
</section>
<section class="slide fade-in">
<img class="vcenter" style="opacity: 0.4;" src="code4lib2015_images/michigan_bento.png" />
<h1>Bento ...</h1>
<div class="notes">
<p>like a Japanese bento box. This is from University of Michigan Libraries. Which is great and all, but isn't this just another in a long line of library hacks and workarounds?</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/google_bento.png" />
<div class="notes">
<p>Well, last I'll show you another search results UI where, again,</p>
</div>
</section>
<section class="slide ">
<img class="vcenter" src="code4lib2015_images/google_bento_2.png" />
<div class="notes">
<p>results are subdivided</p>
</div>
</section>
<section class="slide fade-out">
<img class="vcenter" src="code4lib2015_images/google_bento_3.png" />
<div class="notes">
<p>into compartments by category.</p>
</div>
</section>
<section class="slide fade-in">
<img class="vcenter" style="opacity:0.4;" src="code4lib2015_images/google_bento.png" />
<h1>Bento ...</h1>
<div class="notes">
<p>Bento box ...</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/google_bento.png" />
</section>
<section class="slide">
<div class="vcenter" style="overflow:hidden;">
<img style="transform:scale(1.5) translate(16.5%, 16.5%);" src="code4lib2015_images/google_bento.png" />
</div>
</section>
<section class="slide">
<div class="vcenter" style="overflow:hidden;">
<img style="transform:scale(2.5) translate(30%, 30%);" src="code4lib2015_images/google_bento.png" />
</div>
</section>
<section class="slide">
<div class="vcenter" style="overflow:hidden;">
<img style="transform:scale(6.0) translate(45%, 36%);" src="code4lib2015_images/google_bento.png" />
</div>
<div class="notes">
<p>from Google!</p>
</div>
</section>
<section class="slide">
<h1>Questions?</h1>
<div class="notes">
<p>Questions? [Hopefully pause for laughter] But seriously—I do have to fill 20 minutes, here...</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>You Gotta Keep ’em Separated
<div class="subtitle">The Case for Bento Box Discovery Interfaces</div>
</h1>
</section>
<section class="slide fade-in fade-out">
<img class="vcenter" src="code4lib2015_images/c4l_ven.png" />
<div class="notes">
<p>So, the thing about talking about this at Code4lib is that the Code4lib community is professionally pretty diverse. And when we're talking about bento box interfaces,</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>#justacademic<br />librarythings</h1>
<div class="notes">
<p>we have a distinct bias toward academic libraries.</p>
</div>
</section>
<section class="slide fade-in fade-out">
<img class="vcenter" src="code4lib2015_images/ncsu_old.png" />
<div class="notes">
<p>I mean that *is* where the term originated and, as far as I know, that's mainly the context where it's used.</p>
<p>And—especially in academic libraries, we have sort of a collective history of implementing what we might call </p>
</div>
</section>
<section class="slide fade-in fade-out">
<img class="vcenter" src="code4lib2015_images/hacks.jpg" />
<div class="notes">
<p>“hacks,” especially when trying to facilitate a particular user experience on our websites. That's not to put anyone down, by the way, as we're all pretty much in this boat. We often have to get</p>
</div>
</section>
<section class="slide fade-in fade-out">
<img class="vcenter" src="code4lib2015_images/play_together.png" />
<div class="notes">
<p>different systems from different vendors to play nicely together.</p>
</div>
</section>
<section class="slide fade-in">
<img class="vcenter" src="code4lib2015_images/hacking_summon.png" />
<div class="notes">
<p>Sometimes we need to customize things that aren't easily customizable. </p>
</div>
</section>
<section class="slide fade-out">
<img class="vcenter" src="code4lib2015_images/hacking_millennium.png" />
<div class="notes">
<p>Sometimes we need to try to get data out of systems that just don't want to give it up.</p>
</div>
</section>
<section class="slide fade-in fade-out">
<img class="vcenter" src="code4lib2015_images/borg_girl.jpg" />
<div class="notes">
<p>Sometimes we just need to make things work together that weren't meant to work together.</p>
</div>
</section>
<section class="slide fade-in fade-out">
<img class="vcenter" src="code4lib2015_images/open_source.png" />
<div class="notes">
<p>Granted, things are better than they used to be. Open source software in libraries is thriving, and it's become more or less the norm for vendors to offer APIs or other methods of getting at our data. </p>
</div>
</section>
<section class="slide fade-in fade-out">
<img class="vcenter" src="code4lib2015_images/bike_hack.jpg" />
<div class="notes">
<p>And so we build better and more sophisticated hacks—like this lovely treadmill bike. Or bento box discovery interfaces.</p>
<p>But, you know, as I look at resource discovery solutions in libraries and outside of libraries,</p>
</div>
</section>
<section class="slide fade-in">
<h1>Not <br /> #justacademic<br />librarythings</h1>
<div class="notes">
<p>I'm seeing bento box as an interesting type of UI for more reasons than just the solutions it provides for the immediate problems it was designed to work around. While I think it's true that those problems are real for academic libraries and bento box UIs are still attractive to us as a solution to those problems, I'm becoming more convinced that there's more to it than that.</p>
</div>
</section>
<section class="slide fade-in">
<h1 class="title">Bento Box UI as Hack</h1>
<div class="notes">
<p>But this is mainly what I'm going to be talking about, because I promised I have some stats to share that might be relevant. So let's delve into “bento box UI as hack.” What</p>
</div>
</section>
<section class="slide fade-in">
<h1>Problems</h1>
<div class="notes">
<p>are the actual problems that it was meant to solve?</p>
</div>
</section>
<section class="slide">
<h1 style="margin-top:130px;">Problems<br /> <div class="subtitle">The story of Library<br />Discovery (so far)</div></h1>
<div class="notes">
<p>To answer that, we have to get into the story of library discovery.</p>
</div>
</section>
<section class="slide">
<h1 style="margin-top:75px;">Problems<br /> <div class="subtitle">#justacademiclibrarythings</div></h1>
<div class="notes">
<p>And I really tried to think of a way to start this next part that didn't involve telling this story, because it's one we know so damn well. But, just in case, I'll refresh our memories and make sure we're all up to speed.</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/users.png" />
<div class="notes">
<p>Library users have repeatedly told us: </p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/google2.png" />
<div class="notes">
<p>Google—</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/users.png" />
<h1 style="margin-left:275px; margin-top:-25px;">:-)</h1>
<div class="notes">
<p>good, easy to use!</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/unt_old.png" />
<div class="notes">
<p>library sites—</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/users.png" />
<h1 style="margin-left:275px; margin-top:-25px;">:-(</h1>
<div class="notes">
<p>bad, hard to use.</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/librarian.jpg" />
<div class="notes">
<p>So we've said: let's make </p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/unt_old.png" />
<div class="notes">
<p>library sites </p>
</div>
</section>
<section class="slide">
<h1> == </h1>
<div class="notes">
<p>more like</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/google2.png" />
<div class="notes">
<p>Google</p>
</div>
</section>
<section class="slide">
<h1>Yeah!</h1>
</section>
<section class="slide">
<h1>?</h1>
<div class="notes">
<p>And what *is* Google?</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/goog_seq1.png" />
<div class="notes">
<p>A single search box that </p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/goog_seq2.png" />
<div class="notes">
<p>searches a Web index </p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/goog_seq3.png" />
<div class="notes">
<p>and presents a list of relevance-ranked results. Right?</p>
</div>
</section>
<section class="slide">
<h1>?</h1>
<div class="notes">
<p>And what are library systems?</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/silos_seq1.png" />
<div class="notes">
<p>Information silos! Many data stores, impossible to search at once, </p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/silos_seq2.png" />
<div class="notes">
<p>users have to know which ones to use or how to find out which ones to use,</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/silos_seq3.png" />
<div class="notes">
<p>interfaces are all different, searching takes forever.</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/librarian.jpg" />
<div class="notes">
<p>So we said: well okay,</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/fed_seq1.png" />
<div class="notes">
<p>let's try taking a user's </p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/fed_seq2.png" />
<div class="notes">
<p>search and sending it out </p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/fed_seq3.png" />
<div class="notes">
<p>to a bunch of databases for them at once. </p>
</div>
</section>
<section class="slide">
<img style="width:90%;" class="vcenter" src="code4lib2015_images/metalib.jpg" />
<div class="notes">
<p>Let's even bring the results together on the fly into one list! </p>
</div>
</section>
<section class="slide">
<h1>Yeah!</h1>
<div class="notes">
<p>Yeah! So much like Google!</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/users.png" />
<h1 style="margin-left:275px; margin-top:-25px;">:-(</h1>
<div class="notes">
<p>Nope. Not like Google. Too slow. Way too many possible endpoints and we can't search them all at once. No way to rank results effectively.</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/librarian.jpg" />
<div class="notes">
<p>So we said: all right,</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/ngc_seq1.png" />
<div class="notes">
<p>what we need is a central index. That's what Google has.</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/ngc_seq2.png" />
<div class="notes">
<p>Some of us started putting stuff into Solr.</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/ngc_seq3.png" />
<div class="notes">
<p>But only the stuff we could get.</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/ngc_seq4.png" />
<div class="notes">
<p>And we put search interfaces on top.</p>
</div>
</section>
<section class="slide">
<h1>Yeah!</h1>
<div class="notes">
<p>Yeah! Next Generation Catalogs! So awesome!</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/users.png" />
<div class="notes">
<p>Users were like</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/users.png" />
<h1 style="margin-left:275px; margin-top:-100px;">Articles?</h1>
<div class="notes">
<p>What about articles?</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/librarian.jpg" />
<div class="notes">
<p>So we said: </p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/librarian.jpg" />
<h1 style="margin-left:325px; margin-top:-100px;">Fine.</h1>
<div class="notes">
<p>Fine. Let's make </p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/wsd_seq1.png" />
<div class="notes">
<p>deals with publishers and content providers,</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/wsd_seq2.png" />
<div class="notes">
<p>and build a big ass central index of licensed content.</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/wsd_seq3.png" />
<div class="notes">
<p>And—hey, now we can even put the catalog and all of our other stuff in it too!</p>
</div>
</section>
<section class="slide">
<h1>Yeah!</h1>
<div class="notes">
<p>Yeah! Web scale discovery!</p>
<p>*Now* are we like Google?</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/wsdcheck_seq1.png" />
<div class="notes">
<p>Let's see. Single index for our stuff?</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/wsdcheck_seq2.png" />
<div class="notes">
<p>Check. Single relevance-ranked results list?</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/wsdcheck_seq3.png" />
<div class="notes">
<p>Check. Single search box? </p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/wsdcheck_seq4.png" />
<div class="notes">
<p>Check.</p>
<p>Okay. So...yeah. A lot like Google.</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/users.png" />
<div class="notes">
<p>Right?</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/users.png" />
<h1 style="margin-left:275px; margin-top:-25px;">:-)</h1>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/users.png" />
<h1 style="margin-left:275px; margin-top:-25px;">:-)</h1>
<h1 style="margin-left:150px; margin-top:-100px;">:-\</h1>
</section>
<section class="slide">
<h1>Meh</h1>
<div class="notes">
<p>Meh. The similarities are skin deep.</p>
</div>
</section>
<section class="slide">
<h1>?</h1>
<div class="notes">
<p>Look, what is it *really* that makes Google Google? </p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/goog_seq1.png" />
<div class="notes">
<p>Is it the Google interface?</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/goog_seq2.png" />
<div class="notes">
<p>the single search index?</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/goog_seq3.png" />
<div class="notes">
<p>the Google style of search results?</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/goog_seq4.png" />
<div class="notes">
<p>No—</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/web.jpg" />
<div class="notes">
<p>it's the Web itself. More than that, it's how</p>
</div>
</section>
<section class="slide">
<h1>Beyond full-text indexing</h1>
<div class="notes">
<p>Google moved beyond full-text indexing </p>
</div>
</section>
<section class="slide">
<h1>Harnessed ... </h1>
<div class="notes">
<p>and actually harnessed the unique properties of the Web—</p>
</div>
</section>
<section class="slide">
<h1>Hyperlinks</h1>
<div class="notes">
<p>the hyperlinks, </p>
</div>
</section>
<section class="slide">
<h1>Loosely structured</h1>
<div class="notes">
<p>the loosely structured, </p>
</div>
</section>
<section class="slide">
<h1>Open</h1>
<div class="notes">
<p>openly-available data stored in </p>
</div>
</section>
<section class="slide">
<h1>Standard</h1>
<div class="notes">
<p>standard</p>
</div>
</section>
<section class="slide">
<h1>Machine-readable</h1>
<div class="notes">
<p>machine-readable document formats—and figured out how to do </p>
</div>
</section>
<section class="slide">
<h1>Crazy good relevance ranking</h1>
<div class="notes">
<p>crazy good relevance ranking for Web searches. *That's* what made them the best, and that's why people use them.</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/library_data.png" />
<div class="notes">
<p>And library data doesn't have the same characteristics as Web data. It just doesn't. Though I know lots of folks working on Web Scale Discovery have made big strides, nobody has *solved* relevance ranking for full library discovery the way Google solved it for the Web.</p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/users.png" />
<div class="notes">
<p>So yeah users tell us they want us </p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/users.png" />
<h1 style="margin-left:-25px; margin-top:-100px;">Be like Google!</h1>
<div class="notes">
<p>to be like Google </p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/point_seq1.png" />
<div class="notes">
<p>because Google </p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/point_seq2.png" />
<div class="notes">
<p>gets them to the information they want with little fuss. </p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/unt_web_new.png" />
<div class="notes">
<p>And, on our library websites, when we're trying to figure out how we want to direct different user groups with various and possibly incompatible tasks to find the resources they need to solve their tasks, that's what we're trying to do, too. </p>
<p>What we don't want </p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/point_seq3.png" />
<div class="notes">
<p>is to funnel everyone to one system that looks, feels, and acts like Google but then </p>
</div>
</section>
<section class="slide">
<img class="vcenter" src="code4lib2015_images/point_seq4.png" />
<div class="notes">
<p>fails to return the most relevant results for major categories of user tasks.</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>Bento Box UI as Hack</h1>
<div class="notes">
<p>So Bento box UI design is a workaround for this problem. It's mainly an attempt by libraries to deliver a single search that works better across a wider variety of user scenarios, given the realities of library systems and data. There are at least three things that it tries to do.</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>More equal weight to resources from different systems</h1>
<div class="notes">
<p>It gives more equal weight to resources from multiple systems that might otherwise drown each other out in a single results list. This helps bring more variety to a user's immediate attention.</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>Funnel users to systems <em>after</em> search</h1>
<div class="notes">
<p>It funnels people to the resources they need in the particular systems that natively store and provide services over those resources *after* they've searched.</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>Separate and group by resource type</h1>
<div class="notes">
<p>And it attempts to accommodate different uses by separating results visually by resource type. People don't have to futz around with filters and facets that they tend not to use anyway.</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>Strategery</h1>
<div class="notes">
<p>From a strategic POV, bento box design also has benefits: mainly that libraries maintain more control over their primary search interface,</p>
</div>
</section>
<section class="slide fade-in">
<img class="vcenter" src="code4lib2015_images/puzzle.jpg" />
<div class="notes">
<p>relegating vendor interfaces to components that can be more readily switched out. (If you have the technical staff and expertise.)</p>
</div>
</section>
<section class="slide fade-in">
<h1 class="title">Evidence</h1>
<div class="notes">
<p>So. I'm standing up here talking like all of this is obvious, and you might assume that I have clear evidence to back me up that, number 1, the problems that these UIs</p>
</div>
</section>
<section class="slide fade-out">
<img class="vcenter" src="code4lib2015_images/chupacabra.jpg" />
<div class="notes">
<p>were designed to solve actually exist and, number 2, </p>
</div>
</section>
<section class="slide fade-in fade-out">
<img class="vcenter" src="code4lib2015_images/hammer_nail.jpg" />
<div class="notes">
<p>that these UIs actually solve them.</p>
</div>
</section>
<section class="slide fade-in fade-out">
<img class="vcenter" src="code4lib2015_images/truth.jpg" />
<div class="notes">
<p>The truth is that the evidence isn't clear, especially when just looking at the user studies that are available.</p>
</div>
</section>
<section class="slide fade-in fade-out">
<img class="vcenter" src="code4lib2015_images/hand1.png" />
<h1 style="margin-left:200px; margin-top:-80px;">:-)</h1>
<div class="notes">
<p>On the one hand you have many studies showing pretty high user satisfaction with combined-results systems, primarily from undergraduates.</p>
</div>
</section>
<section class="slide fade-in fade-out">
<img class="vcenter" src="code4lib2015_images/hand2.png" />
<h1 style="margin-left:-220px; margin-top:-220px; font-size:200%;">Articles</h1>
<h1 style="margin-left:300px; margin-top:-140px; font-size:200%;">Books</h1>
<div class="notes">
<p>And on the other hand are studies suggesting that most users come to the library interface knowing at a very broad level what type of resource they need to get (like articles or books), and so results that blend them together are confusing.</p>
</div>
</section>
<section class="slide fade-in">
<img class="vcenter" src="code4lib2015_images/shrug.jpg" />
<div class="notes">
<p>I don't actually have any answers. Sorry. BUT, I might have something useful to add to the picture. </p>
</div>
</section>
<section class="slide fade-out">
<h1>Stats!</h1>
<div class="notes">
<p>Yes, that means it's almost time for stats show-and-tell.</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>BACKGROUND</h1>
<div class="notes">
<p>First I want to mention a few things that are useful in interpreting the stats.</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>4 years</h1>
<div class="notes">
<p>During my time at UNT, part of my job has been to</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>Resource discovery experience</h1>
<div class="notes">
<p>help guide improvements to our users' resource discovery experience, including:</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>Library catalog redesign: September 2011</h1>
<div class="notes">
<p>a redesign of our library catalog,</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>Summon (beta): Spring 2012</h1>
<div class="notes">
<p>Implementation of Summon, which ran as a beta in Spring 2012 and was released as a live service in the Fall</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>Website redesign: September 2012</h1>
<div class="notes">
<p>along with a website redesign. In the redesign, we featured</p>
</div>
</section>
<section class="slide fade-in">
<img style="width:90%" class="vcenter" src="code4lib2015_images/web_tab1.png" />
<div class="notes">
<p>a tabbed search box—the “Find Box”—front and center. Articles, which searched Summon, was the default tab,</p>
</div>
</section>
<section class="slide fade-out">
<img style="width:90%" class="vcenter" src="code4lib2015_images/web_tab2.png" />
<div class="notes">
<p>and a Books and Media tab that searched the catalog was also prominent.</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>Google Analytics</h1>
<div class="notes">
<p>We ran Google Analytics on both systems to collect stats.</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>September 2014</h1>
<div class="notes">
<p>So by September 2014</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>2-3 years of data</h1>
<div class="notes">
<p>we'd accumulated 3 years of data on our catalog and over 2 years of data on Summon. At that point we were already in the planning stages on a bento box design, </p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>→ Bento box design</h1>
<div class="notes">
<p>and I wanted to see what I could glean about how people used our existing discovery systems. So that's when I did my analysis.</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>Primary question:</h1>
<div class="notes">
<p>My primary question was: </p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>Do users use articles and books differently?</h1>
<div class="notes">
<p>do our users actually seem to use articles differently than they use books and other catalog materials? Are those useful distinctions to make in our interfaces? And to answer that it seemed I also needed to prove two other things: one, that, in our environment, </p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>Summon<br />==<br/>Articles?</h1>
<div class="notes">
<p>people *are* mainly using Summon as an articles search and</p>
</div>
</section>
<section class="slide fade-in fade-out">
<h1>Catalog<br />==<br /> Books & Media?</h1>
<div class="notes">
<p>they *are* mainly using the catalog to find books, media, etc. And two,</p>
</div>
</section>
<section class="slide fade-in">
<h1>Different use patterns</h1>
<div class="notes">
<p>that the use patterns we see between those two systems is different enough to suggest different use cases for those types of materials.</p>
</div>
</section>
<section class="slide fade-out">
<h1>METHODS</h1>
<div class="notes">
<p>To conduct the analysis, I wrote Python scripts that </p>
</div>
</section>
<section class="slide fade-in fade-out">