Designing an OPAC for Web 2.0 MAIUG 2006, Philadelphia Casey - PowerPoint PPT Presentation

Designing an OPAC for Web 2.0 MAIUG 2006, Philadelphia Casey Bisson online now at http://MaisonBisson.com ^ << >> 1

Q: What Is Web 2.0? • Is it about Google or Amazon? • Is it about tags or folksonomies? • Is it about AJAX or web applications? • Is it about XML or web services? • Is it about social software? • Is it about buzzwords? A: It’s about people, not technology ^ << >> 2

“2.0” Is About People ...a lot of people • Over 200 million Americans have internet access (source: Internet World Stats and Nielsen/NetRatings) • 94 million Americans use the internet on an average day (source: November 2005 Pew Internet Project report) • 80% of US internet users believe the internet is a reliable source of information (source: November 2004 Pew Internet Project commentary) Web 2.0 is about critical mass ^ << >> 3

“Bagged Products” ^ << >> 4

screenshot of a site demoed click to explore ^ << >> 5

screenshot of a site demoed click to explore ^ << >> 6

screenshot of a site demoed click to explore ^ << >> 7

screenshot of a site demoed click to explore ^ << >> 8

screenshot of a site demoed click to explore ^ << >> 9

screenshot of a site demoed click to explore ^ << >> 10

screenshot of a site demoed click to explore ^ << >> 11

screenshot of a site demoed click to explore ^ << >> 12

screenshot of a site demoed click to explore ^ << >> 13

screenshot of a site demoed click to explore ^ << >> 14

Vs. Search Engines ^ Source: OCLC Report 2005 << >> 15

“I wish I had known that the solution for needing to teach our users how to search our catalog was to create a system that didn't need to be taught…” — Roy Tennant, Library Journal, November 15 2005 ^ << >> 16

What To Do? • Take advantage of the greater memory and processing power of today’s technology • Give patrons better information; leverage their ability to iteratively refine their search (examples: search clustering at Clusty and NCSU Libraries) • Enrich the catalog display with non- inventory information (examples: author biographies, reader’s guides, subject information) ^ << >> 17

Challenges • Usability • Findability • Remixability ^ << >> 19

Findability? …yeah, this is about search engines ^ << >> 20

Where does research begin? Search Engine: 89% Source: OCLC Report 2005 ^ << >> 21

Ambient Findability Peter Morville ^ << >> 22

screenshot of a site demoed click to explore ^ << >> 23

screenshot of a site demoed click to explore ^ << >> 24

screenshot of a site demoed click to explore ^ << >> 25

Think of it Like This... • Search engines are like big OPACs • We need to understand and apply the appropriate cataloging rules to get the results we expect • Libraries can play a huge role, both as information providers and by providing “guidance” to those search engines • We’re better prepared for this evolution than anybody else ^ << >> 26

The Basics • Linking must be possible • Linking must be desirable • Linking must be measurable ^ << >> 27

Challenges to Linking and Indexing • Most OPAC URLs are time or context sensitive (non-OPAC example: broken link) • Many library resources can’t be indexed; some require authentication, others tell search engines explicitly not to index them • Some resources just aren’t online ^ << >> 28

Opening Our Content to Linking and Indexing • Put that content online, develop new materials online first (Story: OCLS in Orlando says online content used more often) • Make sure indexing is allowed on your online content, eliminate barriers to indexing • Make linking and bookmarking easy (examples: Amazon, SpeakEasy Speed Test, and AADL) ^ << >> 29

^ << >> 30

Remixability ^ << >> 31

^ << >> 32

= + There’s supposed to be something witty in here, but I’m not a very witty guy. Can’t you see? I’m very serious. It’s in the eyes. Yup. Serious. ^ << >> 36

^ << >> 37

^ << >> 38

^ << >> 39

Old World database application & business logic ^ << >> 41

Old World database + application + database business logic application all mixed up & business logic ^ << >> 41

New World application API database business logic ^ << >> 42

application API database business logic ^ << >> 43

application application application application database business logic application application ^ << >> 44

another database application application application application database business logic application application ^ << >> 46

another database application application application application database business logic business logic pplication application application ^ << >> 46

Plugins application plugin plugin plugin database ^ << >> 48

^ << >> 49

^ << >> 50

^ << >> 51

^ << >> 52

Why Remixability? ^ << >> 53

Library OPAC ^ << >> 55

Library OPAC Website Databases x 50 ^ << >> 57

Institution Online Web Portal PR Intranet Admit Alumni Parent Course- SIS CMS Portal Portal ware Blogs PSP TLA XTLA Library ^ << >> 57

Architectural Challenges • Our systems are rich with networkable data, but poor in ways to access it • Library software poses unique demands on programmers • We face high thresholds to development because our system architecture is not designed for remixing ^ << >> 58

Libraries The World “Standards” ^ << >> 59

Challenges • Usability • Findability • Remixability ^ << >> 60

Remember • The data supports usability improvements • Libraries are rich with the metadata that drives findability • The web increases the value of librarianship and, if we take advantage of it, can help us to serve more users than ever before • But, architectural barriers limit progress ^ << >> 61

Questions? Extend the discussion: casey.bisson@gmail.com http://MaisonBisson.com ^ << >> 62