<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Library User Experience Community - Medium]]></title>
        <description><![CDATA[A blog and slack community organized around design and the user experience in libraries, non-profits, and the higher-ed web. - Medium]]></description>
        <link>https://medium.com/libux?source=rss----a8eb0742e908---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Library User Experience Community - Medium</title>
            <link>https://medium.com/libux?source=rss----a8eb0742e908---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:35:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/libux" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Accessibility Information on Library Websites]]></title>
            <link>https://medium.com/libux/accessibility-information-on-library-websites-cda5c46a7f4b?source=rss----a8eb0742e908---4</link>
            <guid isPermaLink="false">https://medium.com/p/cda5c46a7f4b</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[assistive-technology]]></category>
            <category><![CDATA[libraries]]></category>
            <dc:creator><![CDATA[Carli Spina]]></dc:creator>
            <pubDate>Fri, 17 Nov 2017 13:58:20 GMT</pubDate>
            <atom:updated>2017-11-17T13:58:20.095Z</atom:updated>
            <content:encoded><![CDATA[<h4>An important part of making your library accessible is advertising that your library’s spaces and services are accessible and inclusive.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yMpP4UaSdFdw2aX6OZ8Qdg.jpeg" /><figcaption>Wrapping braille books to be sent to blind patrons of the New York Public Library.</figcaption></figure><p>An important part of making your library accessible is advertising that your library’s spaces and services are accessible and inclusive. A public statement about your accessibility policy and assistive technologies, together with contact information for someone who can answer questions, is invaluable to those planning a visit and can help to set an inclusive and welcoming tone.</p><p>Below are a few examples I have come across over the years that show how different libraries approach this content on their websites.</p><ul><li>Michigan State University Libraries maintains an <a href="https://lib.msu.edu/general/accessibility/">Accessibility section</a> of their website that includes access and service information for users and also policy information.</li><li>NCSU has an <a href="http://www.lib.ncsu.edu/nrl/accessibility">Accessibility page</a> that covers physical access and available technology as well as contact details for those needing more information.</li><li>Oberlin College Libraries has an <a href="http://www2.oberlin.edu/library/policies/accessibility.html">Accessibility page</a> that covers services, equipment, material retrieval information, and contact details for more information.</li><li>UC Berkeley Library has a <a href="http://www.lib.berkeley.edu/help/disability-resources">Disability Resources section</a> of their website with pages for different types of disabilities, information on services, and contact details for those who need more information.</li><li>Boston Public Library has an <a href="http://www.bpl.org/central/access.htm">Accessibility Resources and Services page</a> that covers access, services, and equipment.</li><li>New York Public Library separates their information onto multiple pages: <a href="https://www.nypl.org/accessibility">Accessibility</a>, <a href="https://www.nypl.org/node/87">Services for Persons with Disabilities</a>, <a href="https://www.nypl.org/accessibility/physical-disabilities">For Patrons with Physical Disabilities</a>, &amp; <a href="https://www.nypl.org/accessibility/print-disabilities">For Patrons with Print Disabilities or Visual Impairments</a>.</li><li>San Francisco Public Library has two pages, one their <a href="https://sfpl.org/index.php?pg=2000059001">Accessibility Policy</a> for Commission public meetings and another with <a href="https://sfpl.org/index.php?pg=2000002501">Accessibility Services</a>.</li><li>The Bodleian Library has a page called <a href="http://www.bodleian.ox.ac.uk/using/disability">Information for disabled readers</a>. It includes access information, resources, and contact details for those needing more information.</li><li>Cambridge University Library has a <a href="http://www.lib.cam.ac.uk/using-library/readers-disabilities">Readers with disabilities</a> section on their site that includes building access and parking information, assistive technology information, contact details for those needing more information, and fire evacuation information.</li><li>The British Library has an <a href="http://www.bl.uk/reshelp/inrrooms/stp/disabilities/rraccessguide.html">Accessibility page</a> that covers access, using their facilities, emergency procedures, and contact information.</li></ul><p>This is far from a complete list of libraries that offer online accessibility information, but hopefully these sites will give you a sense of the different approaches that libraries have taken to sharing this information. If you know of other libraries that have accessibility information online, please let me know by <a href="https://goo.gl/forms/NhmFt6hLtTBLciX12">filling out this form</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cda5c46a7f4b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/libux/accessibility-information-on-library-websites-cda5c46a7f4b">Accessibility Information on Library Websites</a> was originally published in <a href="https://medium.com/libux">Library User Experience Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is autocomplete on your library home page?]]></title>
            <link>https://medium.com/libux/is-autocomplete-on-your-library-home-page-f51077ee6955?source=rss----a8eb0742e908---4</link>
            <guid isPermaLink="false">https://medium.com/p/f51077ee6955</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[autocomplete]]></category>
            <category><![CDATA[libraries]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[search]]></category>
            <dc:creator><![CDATA[Jaci Paige Wilkinson]]></dc:creator>
            <pubDate>Mon, 21 Aug 2017 04:50:32 GMT</pubDate>
            <atom:updated>2017-08-21T04:50:31.578Z</atom:updated>
            <content:encoded><![CDATA[<h4>Literature and some testing I’ve done this semester convinces me that autocomplete fundamentally improves the user experience</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rh2zbuXdslyvw7CNqYLOnA.png" /><figcaption>Autocomplete in the <a href="https://sherman.library.nova.edu/">Alvin Sherman Library</a>’s full-text finder</figcaption></figure><p>If your library has a vendor-based discovery system, chances are you, or your systems administrator, can go straight to the settings page and enable or disable a built-in search autocomplete.</p><p>If you haven’t considered that setting before or don’t know whether it exists, check it now. Is it enabled? Do you know why or why not?</p><p>To begin answering some of these questions, check that your vendor provides clear documentation on how they handle user data. The<a href="http://www.ala.org/advocacy/privacy/checklists/library-management-systems"> ALA has strict suggested guidelines on user data for a reason</a>; as librarians we care about privacy and its direct tie to intellectual freedom.</p><p>The additional question I want to ask: <strong>have you considered the use of autocomplete on your library <em>homepage</em></strong>?</p><p>Literature and some testing I’ve done this semester convinces me that autocomplete fundamentally improves the user experience, especially on the library homepage. But sometimes it isn’t as easy to implement and I often see it used only within the discovery system interface. This is a huge missed opportunity. Here’s why:</p><h3>#1 Autocomplete prevents user failure</h3><p>I am astounded at the level of failure I see in usability testing that results directly from users misspelling a search term. Often times, the testing script (and therefore, the spelling) is right in front of them.</p><p>Regardless of any doomsday predictions that the internet is ruining our spelling and grammar habits, we need to recognize autocomplete dependency is real. Our users rely on it to remember or correct everything from search strings, URLs, to the spelling of words. In my experience, younger users use it in lieu of bookmarks. <a href="https://tfa.stanford.edu/download/TenUsabilityHeuristics.pdf">Nielsen heuristic #5 is “error prevention”</a>.</p><p>Autocomplete is, in my experience, the most impactful feature library websites have at their disposal to prevent user error. Research by Ward et al. (2012) shows that using autocomplete improves search results and even allows dyslexic users to compensate for their slow writing speeds, spelling difficulties, and reduced reading speeds (Berget and Sandnes, 2016).</p><h3>#2 Autocomplete can combat library anxiety</h3><p>Library anxiety is a well-documented phenomena (most recently, Kwon, et al., 2007). Users are susceptible to anxiety stemming from mechanical barriers (using computers or other equipment) and affective barriers: feelings of inadequacy or ineptness in “attempting library tasks, which are exacerbated by assuming that other people are more proficient”.</p><p>Our websites are complex and filled with jargon that users do not understand (<a href="http://escholarship.org/uc/item/3qq499w7#page-1">see John Kupersmith’s extensive research on the subject</a>). This compounds anxiety; especially for newer or less-experienced researchers and library users. Besides the error prevention provided by autocomplete, there is a compelling argument to be made for how the feature boosts user confidence.</p><p>Documentation for Primo Autocomplete says it is, “derived from a combination of your top local Primo and Primo Central queries and from other data taken from your Primo institution and the Primo Central index.” Given the repeated nature of classes, the local data captured can reflect a blueprint of the institutional research experience and help along successive groups of students.</p><h4>Wait, could autocomplete negatively impact user behavior?</h4><p>But that raises another question: are we, as librarians, comforted to know that users are providing the data that creates autocomplete suggestions for users that come after? A popular search string can still be a bad one. One study even found that,</p><blockquote>“Far from reflecting neutrally users’ preferences, Instant Search can direct users’ attention to other searches: by attracting user curiosity, it could orient them towards searches they would have not otherwise performed” (Karapapa et al., 2015).</blockquote><p>Unlike most corners of the internet, library websites do not run on popularity and purchase power; we are an educational tool and therefore seek to exercise a certain level of control over the search experience to teach good research behavior. Does autocomplete obstruct a library website from being the most effective educational tool? This is conversation us tech librarians need to have with our instruction and research librarian team.</p><h3>#3 We can manipulate autocomplete suggestions to improve search results</h3><p>The article “Autocomplete as a Research Tool: A Study on Providing Search Suggestions” goes so far as to suggest influencing autocomplete with librarian-suggested terms and keywords to improve query formulation and search term identification (Ward et al., 2012).</p><p>North Carolina State University seemingly separates its influenced autocomplete using the label “Best Bets”. This design allows library influence into the autocomplete process with transparency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MW_mP8XmTf2tj_2T.png" /><figcaption>Screencapture from North Carolina State’s discovery system autocomplete (not available from home page…)</figcaption></figure><p>Yet even while Ward et al. recommend autocomplete, they conclude that in-person “instruction on search-term formulation should include a review of autocomplete suggestions as well as practical methods for integrating these suggestions into the research process.” (14)</p><p>Try as librarians might to influence and improve the user experience with design and content, in-person interaction (in the classroom or one-on-one) is still an irreplaceable tool. This is especially true with use of the home page; the most highly trafficked portion of a library website.</p><h3>Enabling autocomplete is worth your time</h3><p>Perhaps all it takes is pressing a radio button to enable autocomplete on your library’s whole discovery system. But if your users’ primary point of contact with the discovery system is your library home page, then you have a different issue. The discovery system’s autocomplete might not be plug-and-play.</p><p>It is worth your time, or a programmer’s time, to create an autocomplete that draws from the same data as your discovery system’s autocomplete library to make sure they operate identically. Or, it is time to reach out to your vendor and ask if any other institutions have used their autocomplete on their CMS.</p><p>I hope the information here has convinced you that autocomplete, specifically on the library home page, has the potential to significantly improve the user experience of your library’s discovery system.</p><h4>Works Cited</h4><p>Berget, Gerd and Frode Eika Sandnes. “Do Autocomplete Functions Reduce the Impact of Dyslexia on Information-Searching Behavior? The Case of Google.” Journal of the Association for Information Science &amp; Technology, vol. 67, no. 10, Oct. 2016, pp. 2320–2328. EBSCOhost.</p><p>Breeding, Marshall. “Privacy and Security of Automation and Discovery Products.” Smart Libraries Newsletter 35.01 (2015): 2–7. Web. Jun 8, 2017.</p><p>“Library Privacy Checklist for Library Management Systems/Integrated Library Systems.” Advocacy, Legislation &amp; Issues. -02–06T11:00:52–06:00 2017. Web. Jun 8, 2017 &lt;<a href="http://www.ala.org/advocacy/privacy/checklists/library-management-systems">http://www.ala.org/advocacy/privacy/checklists/library-management-systems</a>&gt;.</p><p>Karapapa, Stavroula, and Maurizio Borghi. “Search Engine Liability for Autocomplete Suggestions: Personality,</p><p>Privacy and the Power of the Algorithm.” International Journal of Law and Information Technology 23.3 (2015): 261–89. CrossRef.</p><p>Kupersmith, John. (2012). Library Terms That Users Understand. UC Berkeley: UC Berkeley Library. Web. Jun 8, 2017 &lt;http://escholarship.org/uc/item/3qq499w7&gt;.</p><p>Ward, David, Jim Hahn, and Kirsten Feist. “Autocomplete as a Research Tool: A Study on Providing Search Suggestions.” Information Technology and Libraries (Online) 31.4 (2012): 6–19. ABI/INFORM Professional Advanced.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f51077ee6955" width="1" height="1" alt=""><hr><p><a href="https://medium.com/libux/is-autocomplete-on-your-library-home-page-f51077ee6955">Is autocomplete on your library home page?</a> was originally published in <a href="https://medium.com/libux">Library User Experience Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Writing for the User Experience with Rebecca Blakiston]]></title>
            <link>https://medium.com/libux/writing-for-the-user-experience-with-rebecca-blakiston-6f059121379e?source=rss----a8eb0742e908---4</link>
            <guid isPermaLink="false">https://medium.com/p/6f059121379e</guid>
            <category><![CDATA[content-strategy]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[webinar]]></category>
            <category><![CDATA[libraries]]></category>
            <dc:creator><![CDATA[Michael Schofield]]></dc:creator>
            <pubDate>Tue, 01 Aug 2017 12:32:13 GMT</pubDate>
            <atom:updated>2017-08-21T03:57:06.603Z</atom:updated>
            <content:encoded><![CDATA[<h4>53:25 | Rebecca Blakiston — author of books on usability testing and writing with clarity; Library Journal mover and shaker — talks shop in this video and makes the case for content strategy, using active and authentic voice, removing unnecessary words, writing meaningful titles/headings, using parallelism, and more.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m4Ly1cQ6BXs3DfLC.jpg" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F225453862%3Fbyline%3D0&amp;url=https%3A%2F%2Fplayer.vimeo.com%2Fvideo%2F225453862%3Fbyline%3D0&amp;image=http%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F644775974_1280.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=vimeo" width="1920" height="1080" frameborder="0" scrolling="no"><a href="https://medium.com/media/aa38092893f948f8fe216743947a70fa/href">https://medium.com/media/aa38092893f948f8fe216743947a70fa/href</a></iframe><p><strong>Writing for the User Experience</strong> is our second ever<a href="https://libux.co/"> Library User Experience Community</a> webinar. Ours is a community of designers, developers, librarians, info architecture people, content strategists, marketing folks, accessibility enthusiasts, and others, started by me — <a href="https://medium.com/u/3c060db90ff8">Michael Schofield</a> (<a href="https://twitter.com/schoeyfield">@schoeyfeld</a>) — and Amanda L. Goodman (<a href="https://twitter.com/godaisies">@godaisies</a>). We do our best to make content that pushes the conversation around the user experience and libraries, non-profits, and higher-ed a little forward.</p><p>In this session, Rebecca Blakiston — author of books on usability testing and writing with clarity; Library Journal mover and shaker — talks shop and makes the case for content strategy, using active and authentic voice, removing unnecessary words, writing meaningful titles and headings, using parallelism, and more.</p><p>Rebecca is the team lead for Web Design &amp; User Experience at the University of Arizona Libraries. She is the author of two books: <a href="https://www.amazon.com/Usability-Testing-Practical-Librarians-Guides/dp/1442228997">Usability Testing: a Practical Guide for Librarians</a>, and <a href="https://www.amazon.com/Writing-Effectively-Print-Web-Librarians/dp/1442278854">Writing Effectively in Print and on the Web: a Practical Guide for Librarians</a>. She’s also the former Chair of the University Libraries Section, Association of College and Research Libraries (ACRL ULS). In 2016, she was named a Library Journal Mover and Shaker.</p><h3>How people read on the web</h3><p>Excerpt from the transcript awesomely, edited by Emma Boettcher</p><p>Writing is all about the reader. It’s an obvious statement, but something that we sometimes forget. How do you know how people are going to approach content on your website?</p><p>Keep in mind that people are on your website for a specific reason. They rarely go to your website to discover or explore or find something new. Library websites especially are often heavily transactional websites. People go there to search, they go to find your hours, they go to find information on your services, they go to connect with a librarian or ask a question. They have a question in mind when they come to your site or they’re thinking about a task that they want to complete.</p><p>People skim. They skim on the web. They also skim in print as well. The difference between digital content and physical content is getting fuzzier, I think, and the way people are interacting with print media and digital media is becoming strangely similar.</p><p>But especially on the web, people are skimming. They’re goal-motivated. They’re task-driven. A heat map from our Contact Us page shows a core set of things people are doing on that page. They’re not reading through everything or looking at everything. They’re very task-driven.</p><p>People are also very impatient, especially on the web. They only stick around if it’s worth the time investment that they’re putting into it.</p><p>On the University of Arizona library site, the vast majority are really only on the site less than a minute. They’re not there for twenty minutes, 30 minutes, diving deep, deep-reading the content. That’s just not the way people are interacting with our websites. Very few people are on more than 10 minutes on our site.</p><p>So how do we write content with such people in mind?</p><p><em>This writeup was put together as a perk for the super nice folks who were able to support making this webinar free to everyone. If you’d like a copy and can support upcoming webinars, </em><a href="https://www.patreon.com/posts/writing-for-user-13968461"><em>consider being a patreon</em></a><em>.</em></p><p>These events are bootstrapped with your help. Either through donations, old-fashioned street-teaming, talking these events up to the boss — it all goes a long way.</p><p>Specific and heartfelt thanks to Lauren Seaton, Stephen Bateman, Emma Boettcher, Emily King, Rum Rubinstein, Kelly Sattler, Anna Stackeljahn, Alyssa Hanson, Amanda Brite, Amy Croft, <a href="http://tobystereo.com/">Tobias Treppmann</a>, Stephanie Van Ness, and Angie Chan-Geiger.</p><p><a href="http://novarelibrary.com/"><strong>Novare Library Services</strong></a> provides our webinar-space, records, and archives our video. They specializes in IT solutions for libraries and small businesses. In addition to our Library User Experience Community webinars, they’re behind a bunch of other events, too.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f059121379e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/libux/writing-for-the-user-experience-with-rebecca-blakiston-6f059121379e">Writing for the User Experience with Rebecca Blakiston</a> was originally published in <a href="https://medium.com/libux">Library User Experience Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[First look at Primo’s new user interface]]></title>
            <link>https://medium.com/libux/first-look-at-primos-new-user-interface-154e0b1fd98f?source=rss----a8eb0742e908---4</link>
            <guid isPermaLink="false">https://medium.com/p/154e0b1fd98f</guid>
            <category><![CDATA[primo]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[libraries]]></category>
            <category><![CDATA[search]]></category>
            <category><![CDATA[angular]]></category>
            <dc:creator><![CDATA[Ron Gilmour]]></dc:creator>
            <pubDate>Mon, 19 Jun 2017 12:10:24 GMT</pubDate>
            <atom:updated>2017-06-19T12:10:23.487Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>Impressions of some key innovations of Primo’s new UI as well as challenges involved making customizations.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5TTgT8l-PvEuzeb6.png" /></figure><p><a href="http://exlibrisgroup.com/">Ex Libris</a> recently did a complete overhaul of the user interface for their <a href="http://www.exlibrisgroup.com/category/PrimoOverview">Primo discovery layer</a>. They did a great job and developed a UI that is responsive, modern, and (mostly) easy to use.</p><p>In this article I’d like to first look at some key innovations of Primo’s new UI and then discuss the process of implementing local customizations and some of the challenges involved.</p><h3>The New UI</h3><p>I’m not a big fan of tabbed interfaces and was always bothered by the distribution of item information across tabs in the old Primo interface (e.g., Locations, Details, and Browse). As a user, I found that even when I saw exactly what I wanted in a list of results, I still had to spend a second thinking about where I needed to click next (assuming I wanted more than just a call number).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*tQbBbUD3yBwG8IdP.png" /><figcaption>Old UI item view. Location info not immediately visible. Actions are under a menu.</figcaption></figure><p>The new UI displays everything in a single panel, so anything you want to know about an item is only one click away from the result list. Actions are arrayed across the top rather than being listed in a menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*SH8FoxEHHrcE3OWU.png" /><figcaption>New UI item view. Location info is visible. Actions are visible without activating a menu.</figcaption></figure><p>With the new UI, Ex Libris made huge strides toward mobile usability. The old UI was usable, but not very pretty. Some features, most notably facets, were not usable. The new UI is a tremendous improvement. I’m especially fond of the facets menu as a sticky footer, a design choice that will keep the possibility of refinement in the user’s mind as she scrolls through results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*UKE2V4THijmKhJ6-.png" /><figcaption>Old UI on iPhone 6s, Safari.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*b61OIOG7YvDEWJf3.png" /><figcaption>New UI on iPhone 6s, Safari.</figcaption></figure><p>As with any complex UI, not everything is perfect. The product is still in development and Ex Libris is actively making improvements, many based on input from librarians via the Primo listserv and the Ex Libris Ideas platform. They recently ditched the unpopular “infinite scroll” results list in favor of paginated results, based on accessibility concerns from customers. They’re still addressing a problem with the new UI in “private browsing” mode on iOS.</p><p>The speed of the new UI is not good. It seems to have improved marginally with the most recent release, but it still feels slow. This slowness is especially apparent when a facet is applied to a search, requiring a complete redraw of the screen. If you accidentally click on the wrong facet, then have to remove that facet and choose another one, that’s three redraws, and probably at least one expletive.</p><p>Possibly related to the speed problem is the number of animations. For the most part, these are subtle, professional, and not distracting. They make the interface feel interactive and modern. But there are an awful lot of them and I wonder what cost they exact on performance.</p><h3>Customization</h3><p>For those of us who like to customize and add functionality to library systems, a new interface can mean a lot of work. The new Primo UI was no exception.</p><h3>Angular?</h3><p>Very early on, the Primo community learned that the new interface would be based on <a href="https://angularjs.org/">Angular JS</a>, a JavaScript framework mainly maintained by Google. This seemed like an odd decision on the part of Ex Libris. It isn’t surprising that the Ex Libris developers wanted to work in Angular — it’s a popular framework. For <em>developers</em>.</p><p>What surprises me is that they expected <em>librarians</em> to work in Angular. An “average” library, whatever that is, almost certainly has some internal expertise in CSS, basic JavaScript, and jQuery. But Angular? Not as likely.</p><p>At my library, there was no internal expertise. So it was off to the Internet. There are many great tutorials out there on Angular JS, and the framework itself has excellent documentation. But the tutorials are generally project based: “Build an X with Angular JS,” where X is some variety of search/display interface on top of some JSON data.</p><p>So despite the knowledge I’d gained from the tutorials, I still had no idea how to make even simple modifications to the new Primo UI.</p><p>It turns out that the key to inserting content into Primo is something called an Angular “component,” a concept barely touched upon in most tutorials and books. Ex Libris liberally sprinkled their new UI with Angular “directives” (i.e., custom HTML elements) to which developers can add code by creating a corresponding component. The component, in turn, may optionally refer to a “controller,” which is where you can insert your own programming logic. For most things, it’s not <em>terribly</em> difficult once you get used to that model, but it feels very restrictive. What if I want to do something in a location where there isn’t a pre-defined directive? And what if I want to alter existing content rather than create something new?</p><p><strong>Editor</strong>: Ron gave me (<a href="https://medium.com/u/3c060db90ff8">Michael Schofield</a>) the okay to duck-in for a moment to elaborate. An Angular component can be a little weird if you’re predominately coming from jQuery. Think of a component like a custom HTML element, that has styles and functionally baked into it. For instance, you could make a carousel using an arrangement of &lt;div&gt;s and images, and wherever you want to place a carousel you must copy all that markup. Or, you could write it just once and tell Angular to -- from now on -- recognize the &lt;slider&gt; element instead. Components are both useful for substituting a little code for a lot of code, and also a way to sanitize and streamline how people -- like librarians customizing Primo -- use it. -- @schoeyfield</p><h3>The Development Environment</h3><p>Ex Libris was nice enough to provide a <a href="https://github.com/ExLibrisGroup/primo-explore-devenv">development environment</a> via GitHub so that developers can have a local sandbox for the new interface. This includes a ready-made Gulp workflow to deal with things like minification, concatenation, and bundling the whole thing up into a package that can be uploaded to the Primo Back Office for live implementation.</p><p>Again, this is nice if you’re familiar with the technologies, but I get the impression that not all librarians are finding this as approachable as its creators intended.</p><h3>The Customizations</h3><p>Ithaca College Library has implemented a few additions in the current version of Primo: a “text this call number” feature, a “not on shelf” (trace request) link, a “notify me on arrival” feature for on-order items, and a map highlighting a physical item’s location.</p><p>We’ve managed to implement all of these features in the new UI, but it has been a long process, with a lot of false starts. Once I figured out that I could often drop existing code into an Angular controller with only minor modifications, things went a lot faster.</p><h3>Lessons Learned</h3><p>The work we’ve done at Ithaca College so far would have been impossible without the support of the Primo listserv and the Slack group that formed following an Ex Libris-sponsored webinar. There are people in these groups who are far better programmers than I am, and I’ve learned a lot from them. I can’t think of another project I’ve worked on where success has been so dependent on the kindness of strangers.</p><p>While I enjoy extolling the generosity and creativity of the many Primo-using librarians out there, the dependence on informal information sharing points to the inadequacy of Ex Libris’s documentation. As with any product, quality documentation in a single location goes a long way toward meeting the needs of customers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=154e0b1fd98f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/libux/first-look-at-primos-new-user-interface-154e0b1fd98f">First look at Primo’s new user interface</a> was originally published in <a href="https://medium.com/libux">Library User Experience Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What users expect]]></title>
            <link>https://medium.com/libux/what-users-expect-f1076a50b7a9?source=rss----a8eb0742e908---4</link>
            <guid isPermaLink="false">https://medium.com/p/f1076a50b7a9</guid>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[libraries]]></category>
            <category><![CDATA[netflix]]></category>
            <dc:creator><![CDATA[Trey Gordner]]></dc:creator>
            <pubDate>Sun, 18 Jun 2017 04:56:45 GMT</pubDate>
            <atom:updated>2017-06-18T04:56:45.287Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>We thought it would be fun to emulate some of our favorite sites in a lightweight concept discovery layer we call Libre.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cJGFcXQ991hbJb-5.png" /><figcaption>An overview of a Libre book-detail page, which one tester referred to as “dark Amazon.” We took that as a good thing.</figcaption></figure><p>Users have high expectations these days. The hours spent in elegant web apps like Netflix and Spotify seem to be sharpening the collective sense of design. What was once the pinnacle is now the convention, and as Don Norman said, “Conventions are slow to be adopted and, once adopted, slow to go away.” So we thought it would be fun to emulate some of our favorite sites in a lightweight concept discovery layer we call Libre. Below are some of the expectations we prioritized in the design. <a href="#_ftn1">1</a></p><h3>#1: Things worth doing also look cool</h3><p>First, we wanted to elevate books to the same “cool status” of other media. Thanks to Netflix and Spotify, that meant choosing a dark theme with white lettering and neon trim. Because of the ready association with the <a href="http://www.ala.org/tools/national-library-symbol">national library symbol</a>, we chose blue for the secondary color.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/991/0*MElOpNalA9XNFw4-.png" /><figcaption>Search bar and category navigation within Libre. These categories could later be personalized.</figcaption></figure><h3>#2: The most useful things are also the most visible</h3><p>The intent in a known-item search (33–60% of all queries <a href="#_ftn2">2</a>) is rapid visual confirmation, so we highlighted title, author, and cover image. In more serendipitous browsing, the intent is evaluation, so average rating and a synopsis are prioritized second. <a href="#_ftn3">3</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/0*tmmxOoL07T7UKGg_.png" /><figcaption>Central section of a Libre book-detail page. Other proposed tabs were Reviews (from Goodreads) and Library Info.</figcaption></figure><h3>#3: All the answers are here</h3><p>Several friends of mine have revealed, at one point or another, that they didn’t know the library was free. While this can seem shocking, it’s bad design to assume that the user knows everything they need: immigrants may never have had access to a public library before, and the less tech-savvy might need to know that borrowing ebooks is legal. Hence, we avoided jargon like “Place Hold,” list requirements, and explained the basic premise of a library in fine print beneath the main call-to-action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/594/0*7zQRMhmY1iNtIuTr.png" /></figure><h3>#4: Browsing is always assisted</h3><p>Other sites deliver personalized recommendations by capturing reams of personal data. Content-based recommendations like “Nebula Award Winners” or “NYT Bestsellers — Fiction” assist users in a similar way, though. Offering a compelling alternative is more important at the library than anywhere else online, since the title a user came looking for could be out on loan already. We wanted to keep our users from leaving in frustration if they encountered an unavailable title.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GcWmXLmbKgr0IONS.png" /><figcaption>In our model, content-based recommendation lists like this one are curated by local librarians.</figcaption></figure><h3>#5: I can bring friends</h3><p>A site without sharing is a city without roads. Even if the features aren’t used too often, we decided that it was important to offer up multiple options for users to save, share, and otherwise show off their discoveries. We distinguish subtly between casual users, who might know to post or tweet, and the power user, who may want to embed a free link on his book review blog, for instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z38AJVTyD4JH9ntx.png" /></figure><p>What other expectations are important? What features did we miss? Feel free to play around with the <a href="http://www.readlibre.com/">Libre</a> prototype and let us know on Twitter at <a href="https://twitter.com/readlibre">@readlibre</a>.</p><h4>Endnotes</h4><p><a href="#_ftnref1"><strong>1</strong></a>: Our work in this article focuses on a popular reading use case, and will therefore seem more applicable to public libraries. Still, we hope our friends in academics get something out of it too.</p><p><a href="#_ftnref2"><strong>2</strong></a>: EBSCO and Ex Libris are at odds over this figure. EBSCO says “<a href="http://www.niso.org/news/events/2015/webinars/granularity_pt1/">Just under 30</a>” and Ex Libris “<a href="http://www.exlibrisgroup.com/files/Products/Primo/HowDoUsersSearchandDiscover.pdf">over 50</a>.” Both of them exclude author searches from their definition of “known-item” entirely, which seems to me a mistake. Often an author search is an easier route to a known item: for instance, when the title is so long as to be annoying to type or so short as to be ambiguous. Therefore, I inflate their estimates by about 5%.</p><p><a href="#_ftnref3"><strong>3</strong></a>: Notably absent are Format and Availability. These are currently displayed after the user clicks “See at the Library.” A more robust implementation might have them both appear on the page.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f1076a50b7a9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/libux/what-users-expect-f1076a50b7a9">What users expect</a> was originally published in <a href="https://medium.com/libux">Library User Experience Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Write for LibUX]]></title>
            <link>https://medium.com/libux/guest-posting-b79795cb760d?source=rss----a8eb0742e908---4</link>
            <guid isPermaLink="false">https://medium.com/p/b79795cb760d</guid>
            <category><![CDATA[guest-post]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[libraries]]></category>
            <dc:creator><![CDATA[Michael Schofield]]></dc:creator>
            <pubDate>Sat, 17 Jun 2017 20:32:56 GMT</pubDate>
            <atom:updated>2017-06-17T20:41:25.958Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>We should aspire to push the #libweb forward by <strong>creating content that sets the bar for the conversation</strong> way up there, and I would love your help. Our interests and <strong>topical commitment</strong> to the user experience, data, design, and development for libraries, non-profits, and the higher-ed web make LibUX (as in, the Library User Experience Co.) a groovy place, and I am really proud of the articles, podcasts, and the community.</p><p>Now, I’d like to crowd this space a little bit with new and different people — like you. What do you think?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y8Gsiq_GtJPu2yg0ZA6KOg.jpeg" /><figcaption>Aidan Mayer (<a href="https://unsplash.com/@aidanjjmeyer">https://unsplash.com/@aidanjjmeyer</a>)</figcaption></figure><h4>Topics and vibe</h4><p>Write only about something you are really interested in or have insight into. These aren’t mutually exclusive, but I show preference for enthusiasm more than expertise. We are all friends just trying to figure this stuff out.</p><p>I’m looking for<br> 1. beginner articles about research methods, models, principles, tools, concepts<br> 2. useful data snippets and what it implies<br> 3. opinion posts about privacy, personalization, design ethics, workflow, organizational culture, trends, …</p><p>and really just about anything you think makes sense for this blog and our community. Write with authority and don’t be overly concerned with being academic. If there’s a source, link it up, but we think conversations don’t start with a stern lecture. Have fun.</p><p>If you’d rather be given a topic, you’re in so much luck! I have an <a href="https://trello.com/b/GLdVT731">editorial board on Trello</a> full of pitches.</p><h4>Payment</h4><p>Also, I don’t think librarians should blog for exposure any more. I want to pay you for your work. Right now, it’s more like “buy a bunch of coffees” money rather than “pay some bills” money, but I think it’s an important gesture.</p><p>My budget is determined through <a href="https://patreon.com/libux">Patreon support</a>, so the volume of commissioned work I can afford is limited, but if you are cool with arranging some sort of barter — ad spots in our podcasts (<a href="https://twitter.com/metricpodcast">@metricpodcast</a>, <a href="https://twitter.com/w3_radio">@w3_radio</a>) or Patreon perks without being a patron (!) — let’s talk and figure something out.</p><h4>Examples</h4><ul><li>Ron Gilmour showed us a “<a href="https://libux.co/primo-user-interface/">First look at Primo’s new user interface</a>”</li><li>Trey Gordner writes about “<a href="https://libux.co/what-users-expect/">What users expect</a>”</li><li>Jenn Dandle explains how her team went about “<a href="https://libux.co/evaluating-digital-library-accessibility/">Evaluating Digital Library Accessibility</a>”</li><li>Tim Broadwater teaches us how to weigh “<a href="https://libux.co/value-vs-feasibility/">Value vs. Feasibility</a>” of one project over another.</li></ul><h4>Reach out</h4><p>So, let’s talk. Shoot me an <a href="/service/mailto:michael@schoeyfield.com">email</a> and we’ll discuss some ideas.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b79795cb760d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/libux/guest-posting-b79795cb760d">Write for LibUX</a> was originally published in <a href="https://medium.com/libux">Library User Experience Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On the User Experience of Ebooks]]></title>
            <link>https://medium.com/libux/on-the-user-experience-of-ebooks-5a66ca5506?source=rss----a8eb0742e908---4</link>
            <guid isPermaLink="false">https://medium.com/p/5a66ca5506</guid>
            <category><![CDATA[libraries]]></category>
            <category><![CDATA[kindle]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Michael Schofield]]></dc:creator>
            <pubDate>Mon, 05 Jun 2017 04:05:00 GMT</pubDate>
            <atom:updated>2015-10-05T22:04:07.875Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>So, when it comes to ebooks I am in the minority: I prefer them to the real thing. The aesthetic or whats-it about the musty trappings of paper and ink or looming space-sapping towers of shelving just don’t capture my fancy. But these are precisely the go-to attributes people wax poetically about — and you can’t deny there’s something to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/541/1*TgkKTWT0t-IkeFpp9uNyCA.png" /><figcaption>Reading magazines through <a href="https://flipster.ebsco.com/">Flipster</a> — check with your library — is actually pretty pleasant. The responsive web app is pretty slick.</figcaption></figure><p>In fact, beyond <strong>convenience </strong>ebooks don’t have much of an upshot. They are certainly not as convenient as they could be. All the storytelling power of the web is lost on such a stubbornly static industry where print — where it should be most advantageous — drags its feet. Write in the gloss on medium.com, but not in an ebook; <a href="http://www.nytimes.com/projects/2012/snow-fall/#/?part=tunnel-creek">embellish a narrative with animation at the New York Times</a> (a newspaper), but not in an ebook; share, borrow, copy, paste, link-to anything but an ebook.</p><blockquote>Note what is lacking when it comes to ebook’s advantages: the user experience. True, some people certainly prefer an e-reader (or their phone or tablet), but a physical book has its advantages as well: relative indestructibility, and little regret if it is destroyed or lost; tangibility, both in regards to feel and in the ability to notate; the ability to share or borrow; and, of course, the fact a book is an escape from the screens we look at nearly constantly. At the very best the user experience comparison (excluding the convenience factor) is a push; I’d argue it tilts towards physical books.<br>— Ben Thompson in <a href="https://stratechery.com/2015/DISCONFIRMING-EBOOKS/">Disconfirming Ebooks</a></blockquote><p>All things being equal, where an ebook lacks can be made-up by the no-cost of its distribution, but the rarely discounted price of the ebook is often more expensive for those of us in libraries or higher ed — if not substantially subjectively so given that <a href="http://motherboard.vice.com/blog/do-you-ever-own-your-e-books">readers neither own nor can legally migrate their ebook-as-licensed-software</a> to a device, medium, or format where the user experience can be improved.</p><p>This aligns with <a href="http://www.pewinternet.org/2014/09/10/younger-americans-and-public-libraries/">findings</a> which <a href="http://www.pewresearch.org/fact-tank/2014/06/30/7-surprises-about-libraries-in-our-surveys/">show</a> while ebook access improves (phones, etc …) their reading doesn’t meaningfully pull away from the reading of print books.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/521/1*vyrU3yFP45boVwaew7XwHA.jpeg" /></figure><p>Recent hullabaloo involving the ebookalypse may be <a href="http://www.theverge.com/2014/1/16/5316854/pew-study-americans-reading-more-e-books">a misreading which ignores data from sales of ebooks without isbns (loathed self-publishers)</a> in which Amazon dominates because of the ubiquity of Kindle and its superior bookstore. There, big-publisher books are forced to a fixed price using an Amazon-controlled <a href="http://libux.co/the-library-interface/">interface</a> wherein authors add and easily publish good content on the cheap. We are again reminded that <a href="https://speakerdeck.com/libux/championing-the-user-experience?slide=16">investing in even a slightly better user experience than everyone else is good business</a>:</p><ul><li>the price of ebooks are competitively low — or even free;</li><li>ebooks, through Kindles or the Kindle App, can be painlessly downloaded that while largely encumbered by DRM doesn’t require inconvenient additional software or — worst — to be read on a computer;</li><li>and features like WhisperSync enhance the reading experience in a way that isn’t available in print.</li></ul><p>Other vendors, particularly those available to libraries, have so far been able to only provide a middling user experience that doesn’t do much for their desirability for either party.</p><p><em>Originally published at </em><a href="http://libux.co/user-experience-ebooks/"><em>libux.co</em></a><em> on September 23, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a66ca5506" width="1" height="1" alt=""><hr><p><a href="https://medium.com/libux/on-the-user-experience-of-ebooks-5a66ca5506">On the User Experience of Ebooks</a> was originally published in <a href="https://medium.com/libux">Library User Experience Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unambitious and incapable men in librarianship]]></title>
            <link>https://medium.com/libux/unambitious-and-incapable-men-in-librarianship-f3a893c58935?source=rss----a8eb0742e908---4</link>
            <guid isPermaLink="false">https://medium.com/p/f3a893c58935</guid>
            <category><![CDATA[sexism]]></category>
            <category><![CDATA[librarianship]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Michael Schofield]]></dc:creator>
            <pubDate>Mon, 05 Jun 2017 04:04:47 GMT</pubDate>
            <atom:updated>2015-10-26T04:25:41.267Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>A <a href="http://litablog.org/2015/10/is-technology-bringing-in-more-skillful-male-librarians/">brief post by Jorge Perez</a> — sharing <a href="http://www.amazon.com/Technology-Professional-Identity-Librarians-Cybrarian/dp/1466647353">D. Hicks’ data</a> — about the stereotype of men in librarianship and the potential that as librarianship becomes an increasingly tech discipline whether better-skilled males will flock to the profession.</p><blockquote>And — this is going to sound harsh — the men choosing LIS probably could not compete in the much more rigorous environments that command the higher salaries. Put it another way: if they could compete in these higher-paid markets, they would. Kathleen de la Pena McCook</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*YiqPElULsH3GUjIs.png" /></figure><p>None of us are surprised by this stereotype — I mean, hell, profession factors in to the gut checks I make about others, even other male colleagues ( I admit ) who aren’t in dev ops or library systems — but it’s wrong. I mean this not just in the “unfounded” sense of wrongness, but as moral failure.</p><p><strong>“Librarian</strong>” describes for muggles no actual job function but only the hushing no-reality of horned-rims, unabashedly and unrealistically women’s work. Such sexism surrounding and pervading librarianship also feminizes men in the profession, which can only mean whore-painted balding amoeba-shaped cheap-suits in sad sniveling drag. The sweat they leave behind in their chair is the sum-all of their worth among the alphas in startups and Silicon Valley.</p><p>How stupid. You should see the blistering code librarians — women and men — write that makes higher education function.</p><p><em>Originally published </em><a href="http://schoeyfield.com/blog/unambitious-powerless-librarian/"><em>here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3a893c58935" width="1" height="1" alt=""><hr><p><a href="https://medium.com/libux/unambitious-and-incapable-men-in-librarianship-f3a893c58935">Unambitious and incapable men in librarianship</a> was originally published in <a href="https://medium.com/libux">Library User Experience Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Blur the Line Between the Website and the Building]]></title>
            <link>https://medium.com/libux/blur-the-line-between-the-website-and-the-building-ee5d9a04fbd9?source=rss----a8eb0742e908---4</link>
            <guid isPermaLink="false">https://medium.com/p/ee5d9a04fbd9</guid>
            <category><![CDATA[content-liberation]]></category>
            <dc:creator><![CDATA[Michael Schofield]]></dc:creator>
            <pubDate>Mon, 05 Jun 2017 04:03:45 GMT</pubDate>
            <atom:updated>2015-11-02T19:59:27.547Z</atom:updated>
            <content:encoded><![CDATA[<p>So it’s a new year and, like everyone else, libraries are looking at the writing on the wall. We are two or three years in to a market of web-ready devices that is competitive, arguably standardized, and affordable. Every quarter institutions are reminded that the web is increasingly liberated from the home office. The web is not just in your phones and tablets, but it’s in your scale, your fridge, your car. In his blog over at <a href="http://faillab.wordpress.com/"><strong>FAIL!LAB</strong></a>, Ryan Hess sums-up a year’s-worth of trendwatching by telling us that <a href="http://faillab.wordpress.com/2013/01/11/library-website-will-disappear/">“The Library Website Will Disappear”</a>. Prescient gems:</p><blockquote>So, the way we gather information and where we go to get it is already changing. And the interfaces are already being revolutionized and that pace will accelerate dramatically over the next 5 years as voice and sight overtake the the very impractical and immobile keyboard…even the touchscreen may be reduced to the point where iPads seem like a whimsical dead-end much like 8 track or Beta tapes.</blockquote><blockquote>Mobile devices have changed all that. Not only do they steer away from typical web interfaces in favor of “apps,” they actually de-link parts of the web from each other. The result, in most cases is a much more curated and manageable Internet.</blockquote><blockquote>And this is important for libraries, whose pages are almost hard-wired around interconnecting pages together in rather daunting tangles of hyperlinks, portals and gateways.</blockquote><p>I like this one:</p><blockquote>The users 5 years from now that enter our libraries’ virtual spaces, will expect a curated, largely automated experience. Already, we see this on the ground where incoming students are completely beside themselves in the antiquated library environment.</blockquote><p>I made the point in one of my <a href="http://schoeyfield.com/blog/2012/09/28/future-friendly-web-design-for-libraries/">talks</a> that the effort to rethink the library’s website to go mobile-first and adaptive (I like “adaptive” better than “responsive”) is not to just be able to be accessed from the palm of your patron’s hand — that’s just a technicality. Rather, the process of #FFLY design liberates the content librarians provide so that through API’s it can be syndicated and targeted to the first round of Google Glasses and wetware wireless integrated in the human brain.</p><p>But I don’t think the website will disappear. The architecture, the “framework” the word “website” connotes is disintegrating, so that the Library (and other institutions) don’t <em>have</em> websites, but their presence on the web just <em>is</em> — like the inherent vision of libraries being about books.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee5d9a04fbd9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/libux/blur-the-line-between-the-website-and-the-building-ee5d9a04fbd9">Blur the Line Between the Website and the Building</a> was originally published in <a href="https://medium.com/libux">Library User Experience Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Say “Ok Library”]]></title>
            <link>https://medium.com/libux/say-ok-library-c50c16b01605?source=rss----a8eb0742e908---4</link>
            <guid isPermaLink="false">https://medium.com/p/c50c16b01605</guid>
            <category><![CDATA[speech-recognition]]></category>
            <category><![CDATA[libraries]]></category>
            <category><![CDATA[user-experience-design]]></category>
            <dc:creator><![CDATA[Michael Schofield]]></dc:creator>
            <pubDate>Mon, 05 Jun 2017 04:03:25 GMT</pubDate>
            <atom:updated>2015-10-28T23:40:38.951Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*NEnQsbSvr9Q2l8IX9Fj67g.jpeg" /></figure><p>Smartphones didn’t capitalize on that whole “library without walls” promise like we expected. Instead, the library as a place became more tangible and responsive than ever. Our user-centric push to be at our patrons’ point of need — especially through <a href="http://libux.co/?s=mobile">mobile-first responsive web design</a> — reinforces precisely what makes libraries hyperlocal. Our potential to interact through geolocation, beacons, cameras, and context is a pretty strange and newfangled opportunity — especially since <a href="http://www.pewinternet.org/fact-sheets/mobile-technology-fact-sheet/">an internet-ready device is predictably on almost every person</a> — to iron out the kinks that complicate how <a href="http://libux.co/the-library-interface/">patrons interface with the library</a>.</p><p>I have a favorite hypothetical when I talk about designing around the internet of things. Pretend you happen to wander into the range of a beacon and you get this text from the library:</p><blockquote>Hey, it’s pretty chilly this morning. We just made some coffee. If you have time, swing by and have a cup.</blockquote><p>Cool, huh? This isn’t vaporware. Let’s walk through this. First, a user comes in range of a beacon or GPS coordinates, which triggers a notification. Second, an opening sentence based off the time of day and the weather is puzzled together: “Hey, it’s <strong>pretty chilly</strong> this <strong>morning</strong>.” Then, third, the app makes a time- and weather-relevant suggestion to invite you into the building.</p><p>This alone is pretty nifty. Were this suggestion actionable and you swiped to confirm and tapped through an order, then the library just compelled you on a journey with the promise that each touchpoint is pleasant. At this point, it’s on the library to deliver.</p><p>Even then, wouldn’t it be easier if all you had to do was talk back?</p><blockquote>Good idea. I’ll be there in ten. I take my coffee black.</blockquote><h4>A Voice User Interface</h4><p>I read <a href="http://www.oreilly.com/design/free/design-for-voice-interfaces.csp">Design for Voice Interfaces</a> by <a href="http://www.usersknow.com/">Laura Klein</a> and I am having fun thinking about the library application for voice user interfaces (VUI). Voice recognition’s been around but it hasn’t quite lived-up to the dream (yet) fanned through scifi. We’re getting there, though.</p><blockquote>Some products in 1999 had around a 65 percent recognition rate, whereas today’s rates are closer to 92 percent. ( Klein, p. 27)</blockquote><p>Good speech recognition has unique design challenges in that unlike other visual interfaces where the way we interact has precedence in physical objects — we push buttons, we turn pages and move things around in our hands, sometimes there’s even haptic feedback — there is no analog for VUI other than human conversation.</p><p>Skeuomorphic <a href="https://www.google.com/design/spec/material-design/introduction.html">material design</a> uses depth and animation to feel like shuffling paper around on a desk. For Siri and Cortana to succeed they need to mimic consciousnesses who can parse complex meaning in human speech. The more artificial they seem by clearly misunderstanding, then the poorer the user experience and the greater the failure.</p><blockquote>We need to practice contextually aware design. If I say, ‘Make it warmer’ in my house, something should know if I mean the toast or the temperature. So, successful voice interfaces must understand context. (Thomas Hebner, quoted in Klein, p. 6)</blockquote><p>So, yeah, context is key. In “<a href="http://libux.co/best-library-web-design-eliminate-choice/">Does the best library web design eliminate choice?</a>” I wrote about how services that anticipate your needs are built on three (or so) pillars: context, behavior, and personal data.</p><p>Context can be inferred from neutral information such as the time of day, business hours, weather, events, holidays. If the user opts in, then information such as device orientation, location or location in relation to another, and motion from the accelerometer can build a vague story about that patron and make educated guesses about which content to present — like our cup-of-coffee example. Behavior can be deduced using analytics for broad site-wide usage as well as user behavior specific to an individual through the use of cookies and other utilities.</p><p>However, it can only be a user experience for one when personal data can expose real preferences — Michael loves science fiction, westerns, prefers Overdrive audiobooks to other vendors and formats — to automatically skip the hunt-and-peck and tailor a unique service.</p><p>Unlike forms and other visual interfaces, the input for voice can be loaded with meaning that must buffer through a ton of logic. Whether your VUI has to open an app, search the web, text a friend, place a hold, tell you about upcoming events (but not all 23 — that’d be too much), is determined by what it knows about you. That’s why Siri is a “personal assistant:” she knows your agenda and watches you sleep.</p><p>An uncanny valley of personalization can be overcome if the voice interface is useful enough.</p><p>For libraries, that killer app might be real close to home: our bread and butter — complex search.</p><blockquote><strong>Ok Library</strong>: I need a recent full-text article about design patterns that’s been peer reviewed.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/661/1*FTVmZG47gHo2rZ3f5cF_xA.png" /></figure><h4>Footnotes</h4><ul><li>I used Aaron Schmidt’s redesigned library-guy graphic as the logo in <a href="http://libux.co/wp-content/uploads/okay-library.png">the “Ok Library” mockup</a> from his post, “<a href="http://www.walkingpaper.org/page/21">National Library Symbol History &amp; Implications</a>.”</li><li>The card in the same mockup, which reads “Stories of Strength,” is from a screenshot from the <a href="http://public.library.nova.edu/lists">Alvin Sherman Library’s Lists</a> site, where librarians make lists (which is what librarians like to do).</li></ul><p><em>Originally published at </em><a href="http://libux.co/say-ok-library/"><em>LibUX</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c50c16b01605" width="1" height="1" alt=""><hr><p><a href="https://medium.com/libux/say-ok-library-c50c16b01605">Say “Ok Library”</a> was originally published in <a href="https://medium.com/libux">Library User Experience Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>