We've Moved!

Think Clearly has a new home! Click here to see our latest posts.

*If there’s older content you’d like to catch up on, you can browse right where you are, until Friday, April 5th.
We know it takes a minute to get used to change!

Artificial Intelligence (AI) – An Important Tool for Special Librarians

Posted by Ron Aspe, CEO on 11/13/2018
Find me on:
Artificial Intelligence (AI) – An Important Tool for Special Librarians

It used to be that everything a special library’s clients needed to know was available ‘in the stacks’—and it was therefore a reasonable assumption that if it was shelved, it should be easily retrievable. Today’s flood of digital content makes it difficult for many libraries to meet the ‘all access’ expectation.

Separating the wheat from the chaff

Remember the days of ‘weeding’ the collection? Periodically, library staff would decide what was needed and what could be discarded. This was done to manage storage costs and physical workloads. An interesting by-product of this process was that it also ensured the overall relevancy of the library’s collection.

With digital content, the drivers of storage cost and physical workloads no longer apply. As digital resources ‘age out’, they can clutter up your library’s knowledge base. Compounding this problem is the reality that it costs more for a librarian to weed a digital resource than it does to just ignore it; yet ignoring it causes a reduction in digital content’s relevance over time.

AI could be used to help weed a digital collection by automatically deleting content within certain parameters. More useful, however, is teaching your AI search engines to ignore content that is less relevant. With that approach, if someone can’t find what they’re looking for, they can still access the expertise of the library staff to help them find what they need.

Frankly, I’m not sure we are ready for a machine to decide what to keep and what to delete—even Microsoft doesn’t go that far! Then again, perhaps we should offer a ‘deleted items’ archive and ask users if they want to search that too?

Do you need to dam the flood?

If you take away physical limits, it’s a reasonable expectation that a library system (ILS) should be able to store everything. Most end users have no appreciation for the need to curate the collection, so hiring extra staff to do so is a tough sell. On the other hand, while storing everything and offering what’s current is a big challenge, it is a great opportunity to expand the scope and influence of the library.

So, if everything could go into your ‘virtual library’, how do you decide what shouldn’t? Maybe, it’s better not to restrict what goes in, but instead use AI to make the process of adding content to the collection less time consuming—while preventing your collection from becoming a ‘junk drawer’ that people rummage around in to find a rubber band to tie their thoughts together.

AI can also quickly review almost any piece of content and tease out important metadata such as possible subjects and match them against your library system’s taxonomy or thesaurus. Supervised by a human operator, AI can dramatically increase throughput. Furthermore, AI can actually learn from the process of having humans correct its errors. AI might never be 100% accurate, but would definitely be better than having nothing in the drawer. And, if you flag which items were machine cataloged, your search engine can be taught to offer these as supplementary, rather than primary resources.

The more things change…

Having been in the library automation industry for 3 decades, we’ve seen a lot of change. Early versions of our software were capable of printing catalog cards! Before long, those same catalogs could be searched online using our software, via the library’s computer(s). Then, there were wide area networks—and then the internet. People were then able to get their information from any digital device, which represented significant change.

Here's a bit of irony and also a possible indicator of our future. Recently, in response to our clients’ needs, we introduced a Request Tracking and Management function to help manage reference requests. Apparently, the volume of requests our clients handle has increased, rather than decreased. Probably because of the flood which shows no signs of receding.

 

Topics: Special Librarianship, Technology, Artificial Intelligence
https://blog.lucidea.com/ai-an-important-tool-for-special-librarians
blog.lucidea.com
crawl=CC-MAIN-2019-13
61561
application/http; msgtype=response
sha1:Z4JHFTY5PUKSQRUN6ZZU2XST2GKBGTQD
<urn:uuid:746bfdf7-1f15-4ae6-babe-527404f46cfb>
2019-03-26T08:03:50Z
104.17.134.180
text/html
sha1:VUJGPGUUVLIEVDK4JOXHEFOJVKIBUMOZ
<urn:uuid:6d85e0f9-81de-4fa6-a901-739318a4e197>
https://blog.lucidea.com/ai-an-important-tool-for-special-librarians
response
<urn:uuid:d6c93d55-c74b-4fce-b5f7-0b976eb50d1b>
isPartOf: CC-MAIN-2019-13
publisher: Common Crawl
description: Wide crawl of the web for March 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-143-92-167.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/