{"id":397,"date":"2016-11-07T13:55:02","date_gmt":"2016-11-07T19:55:02","guid":{"rendered":"http:\/\/apps.lib.ua.edu\/blogs\/webservices\/?p=397"},"modified":"2016-11-08T16:01:41","modified_gmt":"2016-11-08T22:01:41","slug":"research-help-bento-card","status":"publish","type":"post","link":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/2016\/11\/07\/research-help-bento-card\/","title":{"rendered":"Research help in website search results (OneSearch)"},"content":{"rendered":"

OneSearch Refresher
\n<\/strong><\/p>\n

OneSearch is the search interface on the library website. \u00a0The idea behind OneSearch is to provide a jumping off point to the various library resources available on a topic.<\/p>\n

\"onesearchexampleresultspage\"<\/a><\/p>\n

You can search anywhere on the library website and see results broken down into content type — articles, books, et cetera. \u00a0Results from webpages on the library web site are also included in the Libraries’ Website section. \u00a0For a detailed look\u00a0at OneSearch,\u00a0click here<\/a>.<\/p>\n

What we’re adding to the OneSearch results<\/strong><\/p>\n

Web Technologies and Development has been working on adding a Research Help section to our OneSearch results that will display\u00a0subject specialists based on the user’s query. These result ‘Cards’ are similar to result cards you might see in Google search results when you search for common items such as a thing or a location. Specifically, these new ‘research specialist cards’ use call number range mapping to associate keywords (pulled from the query) with subjects, and then with subject specialists. The point is that (a) keywords – when mapped & appropriate (meaning matching) – should then result in a collection development \/ subject specialist’s image, name, title and contact information appearing along with search results because (b) we feel that it is helpful to users to see the person responsible for materials in a certain subject area.<\/p>\n

The user may have a question, or want to know what our policies are in regards to subject areas under their domain, or be spurred to ask for a certain item, or just want to know general information. It’s a heck of a lot easier for the user if the CD librarian appears at the point of a subject\/keyword search, rather than the user go hunting for them at another time.<\/p>\n

The basis for the research specialist cards is the University of Michigan federated \/Bento-style search, which uses a similar system to serve CD librarians to users during typical resource searches (more on this at the end of the blog post). For more info on how it works, issues, inherent problems, etc., please scroll down to the Q&A at the bottom of the post.<\/p>\n

Show and Tell<\/strong><\/p>\n

As an example, let’s try to search for\u00a0john keats poetry<\/a>\u00a0in OneSearch. \u00a0The results in the Research Help section are shown below:<\/p>\n

\"researchhelpresults\"<\/a><\/p>\n

In response to the query, the user gets English subject specialists in the Research Help section that appears\u00a0below the first row of results.<\/p>\n

How about results for\u00a0operas by mozart<\/a>?<\/p>\n

\"researchhelpmusic\"<\/a><\/p>\n

This doesn’t work perfectly for every query, unfortunately. \u00a0For some subjects, we don’t have accurate call number information entered in yet (see more here<\/a>). \u00a0Other subjects\u00a0have other challenges<\/a> associated with them.<\/p>\n

You can give this new functionality a try at https:\/\/wwwdev2.lib.ua.edu<\/a>. \u00a0Keep in mind that our “wwwdev2”\u00a0site can only be accessed from computers on campus that are in the University Libraries faculty\/staff IP range.<\/p>\n

If you are interested in further information, I’ve answered what I expect will be common questions below.<\/p>\n

Research Specialist Card Q & A<\/strong><\/p>\n

Q:\u00a0<\/strong>Will these results display in Scout?<\/p>\n

A:\u00a0<\/strong>These results aren’t currently slated to display in Scout, but it’s possible to do so and it’s something we will consider for the future.<\/strong><\/p>\n

Q:\u00a0<\/strong>How did this come about?<\/p>\n

A:\u00a0<\/strong>Since the initial launch of OneSearch in the fall\u00a0of 2015, Web Services has been eager to add a section\u00a0to OneSearch\u00a0that promotes\u00a0reference services. \u00a0Ideally, we didn’t want to just display static links — we wanted the reference services of individual librarians to appear based on the context that the user’s\u00a0search terms\u00a0provide. \u00a0We spoke to other institutions that had a Research Help section of their search results and decided it was something we could implement as well.<\/p>\n

Q:\u00a0<\/strong>How do you match user queries to subject specialties?<\/p>\n

A:\u00a0<\/strong>Our first iteration of this idea\u00a0used\u00a0the keywords that University of Alabama librarians\u00a0supplied before the launch of the redesign last summer. \u00a0This approach was fairly limited, since a very large\u00a0proportion\u00a0of OneSearch\u00a0user queries\u00a0didn’t match\u00a0any of our keywords.<\/p>\n

We couldn’t help but notice that Michigan’s site returned relevant librarians for a wide range of queries. \u00a0When we emailed Michigan\u00a0to ask them how they were accomplishing this, they informed us\u00a0that\u00a0they were taking the query the user put in, searching the catalog with it, and using the call numbers from the results to classify the query in their in-house\u00a0taxonomy<\/a> for subject specialties. \u00a0 Once they had classified a query into that hierarchy, they would display the librarian associated with that specialty or specialties.<\/p>\n

We thought: what a good idea! \u00a0So we have worked on implementing a beta version of this functionality in OneSearch that displays staff directory information when a query matches a subject specialty. \u00a0For librarians providing services\u00a0that don’t easily map to Library of Congress\u00a0call numbers, keywords are still available to ensure that they are returned in search results for specific\u00a0searches.<\/em><\/span><\/p>\n

Q:\u00a0<\/strong>Where are the call numbers for each subject specialty getting pulled from?<\/p>\n

A:\u00a0<\/strong>This (incomplete)\u00a0spreadsheet<\/a>.\u00a0 Call numbers have been pulled from LibGuides where available, and in instances where doing some sort of rough classification was easy based on the structure of the Library of Congress classification, I have tried to add those into the spreadsheet as well.<\/p>\n

Q:\u00a0<\/strong>These call numbers are wrong and\/or incomplete!<\/p>\n

A: <\/strong>Our hope is to get accurate\u00a0call number ranges from subject specialists.\u00a0<\/strong>Currently, the call numbers being used have been pulled together from what’s in LibGuides for each subject and what’s easy to pull out of the Library of Congress\u00a0classification online. If you want to make additions or changes to the call numbers getting used for your subject specialty, take a look at this spreadsheet<\/a>\u00a0and please\u00a0email me<\/a>!<\/p>\n

Q: <\/strong>Why aren’t results displaying for <insert query here><\/p>\n

A:\u00a0<\/strong>There may not be any call numbers in our system associated with\u00a0that subject specialty — see the question above.<\/p>\n

We’ve also set a minimum relevance threshold for\u00a0subject specialists getting displayed in search results. \u00a0If one call number out of one hundred returned from the catalog maps to a subject specialist (in an extreme example), it’s unlikely that specialist is pertinent to that query and it seemingly makes sense to exclude that subject specialist from the results. \u00a0Where exactly that threshold should be, however, is tricky, and that’s something we’re still experimenting with.<\/p>\n

Finally, we are using AND as the default Boolean operator for catalog queries. \u00a0Using OR would increase the number of queries that return staff directory results, but decrease their likely relevance.<\/p>\n

If you actually want to see which\u00a0call numbers are getting matched to each subject, you can — but there are several\u00a0steps involved.<\/p>\n

Here’s an example URL:<\/p>\n

http:\/\/wwwdev2.lib.ua.edu\/oneSearch\/api\/search\/YOUR QUERY HERE\/engine\/128\/resultType\/relevance<\/p>\n

Replace YOUR QUERY HERE in the above URL with a query you want to see the raw results\u00a0for, then paste the URL into your browser.<\/p>\n

The results will be hard to read, so you’ll want to make use of an online formatter. \u00a0Go to jsonformatter.org<\/a>, paste your results on the left-hand side, then click Format \/ Beautify. \u00a0You should see formatted results on the right-hand side.<\/p>\n

\"onesearchjsonformattedresults\"<\/a><\/p>\n

 <\/p>\n

There’s still a lot of information that’s irrelevant to you here, so I recommend using Ctrl-F to search for “subject”. The most important items are\u00a0the name of the subject and the relevance listed after it, which is the number of call numbers that matched call number ranges associated with\u00a0that subject.<\/p>\n

<\/span>
\n\"onesearchjsonresultsnippet\"<\/a><\/p>\n

 <\/p>\n

If you’re interested specifically in what those call numbers are, you can see call numbers listed in “callNumber” next to the ranges they matched. \u00a0If there are call numbers that didn’t map to any subject, they appear in the\u00a0“nonMatchingCallNumbers” section (if not, the section won’t appear). \u00a0<\/span><\/p>\n

Q: <\/strong>What are some limitations of this approach?<\/p>\n

A:\u00a0<\/strong>Our approach does not work well for queries that mostly return electronic resources — Computer Science is a good example. \u00a0This is because Voyager’s somewhat dated SearchService API can’t be configured to return call numbers if there’s nothing in the 852 location field, as is the case with our electronic resources. \u00a0If we used Z39.50 (an older search technology) instead of the API, we could get results with call numbers for these resources — but that would entail quite a bit of additional work and may not integrate\u00a0well with an application that currently\u00a0works with API results only.<\/p>\n

Some subjects are largely subsets of other subjects in the LC hierarchy — for example, PN is Literature (General) and Motion pictures are PN1993-1999. \u00a0When I first tested film-related queries, English subject specialists were always returned ahead of Telecommunication and Film for film queries like “quentin tarantino” because the English call number range included all of the film results and then other literature results as well. \u00a0The simple solution is to take the motion pictures call numbers out of the literature range. \u00a0\u00a0Instead of using all of PN for English, it’s now specified as PN1-1993, PN2000-6790. \u00a0In other instances where this super\/subset relationship exists, similar changes may need to be made to call numbers.<\/p>\n

More generally, some subjects are multidisciplinary and don’t neatly fit into the Library of Congress classification system.<\/p>\n

Q: <\/strong>Is this the final design of how the results will display?<\/p>\n

A:\u00a0<\/strong>Not necessarily. \u00a0We are also looking into other options for where and how to display the Research Help results. \u00a0Once we have something to share, we’ll send those along.<\/p>\n

We also want to make it more clear to users that OneSearch results don’t end with the Research Help box in instances where that’s what a user sees at the bottom of the browser before scrolling.<\/p>\n","protected":false},"excerpt":{"rendered":"

OneSearch Refresher OneSearch is the search interface on the library website. \u00a0The idea behind OneSearch is to provide a jumping off point to the various library resources available on a topic. You can search anywhere on the library website and see results broken down into content type — articles, books, et cetera. \u00a0Results from webpages … Continue reading Research help in website search results (OneSearch)<\/span><\/a><\/p>\n","protected":false},"author":489,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20213,20208],"tags":[],"class_list":["post-397","post","type-post","status-publish","format-standard","hentry","category-onesearch","category-website"],"_links":{"self":[{"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/posts\/397","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/users\/489"}],"replies":[{"embeddable":true,"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/comments?post=397"}],"version-history":[{"count":77,"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/posts\/397\/revisions"}],"predecessor-version":[{"id":482,"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/posts\/397\/revisions\/482"}],"wp:attachment":[{"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/media?parent=397"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/categories?post=397"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/apps.lib.ua.edu\/blogs\/webservices\/wp-json\/wp\/v2\/tags?post=397"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}