Editor's Notes

1. Here’s our plan: we hope to give a bit of background about the project, to share info with you about the process, including usability results, and to share info about the tools/applications we’re using. We’ll finish up with what we learned and observed.
2. And this was an internal or secondary page on the site.
3. Knew all along that we had a phase II in the works, but a 4-member web team was given a charge…When Dean of Library says “I can’t find anything and neither can my faculty colleagues” you know you have to do something different not only with the design, but also with the content and the delivery of that content. On a decentralized campus, having the Dean endorse a plan to centralize appearance, services and interactions via the web was huge. The initial problem we were attempting to solve was to remove ‘location-based content’ or silos and to present ‘information’ and web interactions in a more consistent, coherent way. In a separate development path, Mlibrary was looking at an interface overlay on the OPAC, specifically, another group was attempting to test, develop and launch VuFind as the primary/additional catalog interface. In yet another development path, a third group was attempting to identify a tool for our resource/research/technology/subject guides. Prior to and during phase I we had 3 different methods for presenting guide-like information and recognized that we had to identify a single, web 2.0-like solution for all libraries. This 3rd group was in the process of evaluating SpringShare’s product, LibGuides.These other projects had an impact on development and decisions related to the web site redesign, and luckily we had a convergence of staff and planets that allowed us to tap into these tools and applications. We’ll talk more about the details of integrating the various tools in a moment. What it cost: before we go any further, we want to anticipate your question about how much did this process/project cost. While we don’t have a figure to share with you, it might help your understanding of the slides to come to know that: 3 librarians + PR specialist = web team 2 web developers8K on student help who initially migrated content from old web site/architecture into new application/architecture + usability40 or content managers who reviewed content migrated from old site to newAs we moved toward our second wave of project, phase II, we used an analogy with library staff of ‘building a house’. Mike will share more on this process.
4. The far right column is contacts -- who to see for more help.Subject specialists - up to 3 -- appear via call number mapping. User’s query in the catalog top 100 results mapped to call numbers High enough number of matches -> you get a subject specialist Or “Ask a Librarian” (default)Services or libraries can appear here based on keyword matchingAsk a Librarian ALWAYS appears