Library Catalog Pages Ranking in Search Engines
Published: 2012-02-26 08:36:39 -0500
Recently there was a thread on the code4lib list about local catalog records showing up in results in the search engines like Google, Bing, and Yahoo!. The anecdotal evidence is that Google is actively crawling and indexing library catalogs like Johns Hopkins’.
Some of the discussion has revolved around how useful this local catalog data is to folks coming from search engines. How many of these users are satisfied with coming to a local library catalog? I think many people will be unsatisfied because they have found something interesting that they cannot access. Much of what academic libraries have is only available to their own students, faculty, and staff or to other institutions through inter-library loan. This situation may be improving for users.
Increasingly data about people comes to search engines through social networks. Facebook and Google+ are collecting information about user preferences that can be worked into algorithms for search results. Social connections and their preferences are starting to figure in to the ranking algorithm. My social circles are starting to change what results show up on the first page. The results with this social component added in are different from those with it removed. Many will turn off or away from these new factors to search ranking. There are legitimate concerns about the filter bubble search engines are placing us in. There are some ways, though, that library catalogs and other interfaces could be improved for those who opt in and likely also improve things for others as well.
Location vs. Affiliation
One suggestion is that the user’s geographic location could figure in to which library catalogs show up in results. Geographic location is a very rough way of determining relevance in this case. It may work for public libraries, but does not work well for academic libraries. I could live right next door to a university with a fabulous library, but have no rights to access the collections.
This is basically how WorldCat works to determine relevance by location. The problem is that WorldCat shows me all results even those where the closest copy is over 100 miles away from my current location. It is not until you get to the view of an individual resource that you find out that the library that holds the resource is too far away to ever be relevant. Even if the search engines used my location along with location data from WorldCat the results may still not be relevant or something I could borrow.
Geographic location has been a crude surrogate for personal relevance. What would be better would be for the search engines to use affiliation. Affiliation is more accurate for determining an appropriate resource to present in search results. The motivation for search engines to use affiliation to effect relevance is to improve the user experience and keep users coming back to the single search box. Folks already use search engines to find content on their institutional websites. Often this is done to work around sites that have poor information architecture or search capabilities. This issue is not something that is specific to library catalogs, but cuts across lots of information from institutions.
Google+ already knows my current work affiliation. How does a search engine use that information to make results from the local catalog rank higher for me? The missing component is for the library catalog (or any institutional site) to advertise institutional ownership.
URLs already do this in some cases, but there is no explicit link between the text of the institution name I enter into a social network profile and the URL for a library catalog or website. In other cases, library catalogs and other applications are hosted by third parties so not within the institutional domain. A URL is not always sufficient for determining institutional ownership.
Another approach that could work across these cases is to use embedded semantic markup to effectively brand a site for machines like crawlers. This kind of annotation can unambiguously state that a page is from a particular institution. It is easier to link the organization name on a Web page with the name given as an affiliation in a social network profile.
Here’s an example using Microdata and the Schema.org vocabulary. It covers both the geographic location and affiliation cases. The latitude and longitude are given, making more exact than just a zip code. More importantly it is clear that “NCSU Libraries” is the name of an organization.
<div itemscope itemtype="http://schema.org/Organization" itemid="http://lib.ncsu.edu/"> <span itemprop="name">NCSU Libraries</span> <div itemprop="address" itemscope itemtype="http://schema.org/PostalAddress"> <span itemprop="streetAddress">2 Broughton Drive</span>, <span itemprop="addressLocality">Raleigh</span>, <span itemprop="addressRegion">NC</span> <span itemprop="postalCode">27695-7111</span> </div> <span itemprop="telephone">(919) 515-3364</span> <span itemprop="location" itemscope itemtype="http://schema.org/Place"> <span itemprop="geo" itemscope itemtype="http://schema.org/GeoCoordinates"> <meta itemprop="latitude" content="35.78743" /> <meta itemprop="longitude" content="-78.67012" /> </span> </span> </div>
This markup might be enough of a hint to the search engines to give a boost to content from my institution if I have that information in my profile. I don’t have evidence that the search engines are currently doing this, but it seems within the realm of possibility. Whether Google will do this kind of linking with library catalog pages, I don’t know, but Google is increasingly becoming this kind of aggregator. Adding markup like this to the library catalog would be a low cost way to see if over time the search engines do use the data to effect relevance for particular users.
WorldCat is in the same space by more explicitly aggregating information about holdings but only for their member libraries that submit holdings data (that’s how it works, right?). Using Microdata and Schema.org would allow for this kind of aggregation of distributed sites on the Web. The search engines may not be the only service providers for this kind of aggregated data, though the search engines have the advantage of being the first place users look. Since this is open data, others could also provide services around the same embedded data.
One thing that would make this easier would be the adoption of unique identifiers on both ends. In the example above the
itemid attribute gives a URL as an institutional identifier. If social profiles either explicitly or behind the scenes used the institutional URL http://lib.ncsu.edu/ as an identifier for “NCSU Libraries” then this linking would be more solid.
There is more that needs to be worked out for affiliation to work like this more generally on the Web. Sometimes you may have the right to borrow something as part of a consortium that does not share a name with your place of work. While there is not a way to stipulate this kind of relationship in many social network profiles, it may be possible through a profile on your own website. If you eschew giving lots of information about yourself to social networks, this approach may work for you. In this scenario the search engines would still need to know that a particular searcher is associated with a particular website to make this kind of link.
Here’s a short partial snippet of some Microdata using Schema.org to communicate to machines my affiliation with the Triangle Research Library Network. (TRLN is a collaborative organization of Duke University, North Carolina Central University, North Carolina State University, and The University of North Carolina at Chapel Hill.) I could place something like this on my own website.
<div itemscope itemtype="http://schema.org/Person"> <h1 itemprop="name">Jason Ronallo</h1> <p> Website: <a itemprop="url" href="http://ronallo.com/">Preliminary Inventory of Digital Collections</a> </p> <div> <h2>Affiliations</h2> <ul> <li itemprop="worksFor" itemscope itemtype="http://schema.org/Organization"> <span itemprop="name"><a href="http://lib.ncsu.edu" itemprop="url">NCSU Libraries</a></span> </li> <li itemprop="affiliation" itemscope itemtype="http://schema.org/Organization"> <span itemprop="name"><a href="http://www.trln.org" itemprop="url">Triangle Research Library Network</a></span> </li> </ul> </div> </div>
So in some ways what I’ve written about here could help the search engines provide a basic appropriate copy relevancy boost for resources represented in the library catalog. This is a parallel to what our institutional link resolvers do for resources like individual articles which are not usually represented in our catalogs. This is all hints to the search engines, but in line with the direction the search engines are going. As the search engines get smarter about directing users to appropriate content, there will probably be more reasons to have local library catalogs crawled and indexed.