This article is more than 5 years old.
“Just as GoogleBook search brought book search to the open web, this advancement brings full text book search and integrated content discovery to serious researchers. . .”
Today Mary Beth, Susan, Derrik, Lauren C, Tim, Audra, Craig, Cristina, Steve, Leslie, Lynn, Kaeley, Erik, Barry and Giz attended a webinar about the recent launch of the full text indexing of HathiTrust records in the SerialsSolutions Sumon service. David Lankes started the session with his view of how services like the HathiTrust compare with other cooperative projects and what motivates information seekers when they approach systems with an information need. David focused on a few themes, notably the concept that collaborative collections create opportunities for new communities to form around.
John wilkin gave an overview of the state of the hathitrust. Some interesting numbers included a current ~31% overlap with ARL libraries and near 50% overlap with Oberlin group libraries. The HathiTrust currenlty has around 8.2 Million titles with approximately 26% of them (2.1M) in the public domain. Wilkin indicated that with current contribution levels they are seeing about a 1% growth in overlap for every 200K submitted titles.
John Law finished up the webinar indicating that the Summon service would offer the full text index of HathiTrust records as an include-able option with other resources. The key idea appeared to be that full text indexing would be included in Summon with various options for content delivery (e.g. direct link for public domain resources, catalog link for owned resources, ILLfulfillmentlink for others). Interstingly, John Law indicated that these links will not always be based on OpenURL but will be ‘pre-calculated.’ SerialsSolutions is planning on offering some advanced content inclusion options (e.g. public domain only or fully indexed collection) using specific fulfillment options for each type of resource/licensing restriction.
As expected the questions from the audience focused on timeline (mid year), technical details (to be determined in the client center), and requests for a demo (forthcoming). A few questions centered around matching and merging of titles/records to provide a streamlined record discovery and presentation service for patrons. In response John Law said that SerialsSolutions is planning on finding ways to merge catalog records from the subscribing library with full text indexing from HathiTrust to provide both single-point access and enhanced bibliographic/full text access. There was a question about what the user experience would look like for items not in the public domain. It appears that Summon will attempt to make a ‘best-guess’ about resources but will provide multiple links (ILL, content link when possible). There was some interest about how resrouces outside of the puGiven the attendance from ZSR this is clearly an interesting area and I expect there will be more questions in the months to come!
3 Comments on ‘SerialsSolutions Summon and HathiTrust full-text indexing’
Thanks for setting up this session. Speaking of HathiTrust, here’s a new article titled HathiTrust: A Research Library at Web Scale — http://www.cdlib.org/cdlinfo/2011/04/22/heather-christenson-in-print/
I was not able to attend the webinar today as I had hoped, so I am very grateful for this full report. I am very interested in the development of Summon. In a paper the digital group within Special Collections read this week(Scan and Deliver: Managing User-initiated Digitization in Special Collections and Archives. Dublin, OH: OCLC Research. http://www.oclc.org/research/publications/library/2011/2011-05.pdf (.pdf: 166.2K/18 pp.), several libraries reported that they did not check the Hathi Trust or Google books before digitizing patron requests. They cited the reason as that it was too time consuming. These schools (Duke was one) have much more robust digitizing facilities than we do, so librarians find it easier to just send a request to the scanning department. We on the other hand only stand to benefit as tools like Summon make it easier for us to determine if a patron request is already in a digital collection to which we can send a link to the patron.
Thanks, Eric.
I missed the part about content links being “pre-calculated” rather than OpenURL. You’re right, that is interesting. Thanks for catching that.