MORRIS HOLDINGS NOW AVAILABLE IN QUICKSEARCH!

Morris holdings now appear in Quicksearch!

The best way to view this new feature is to search for a law-related topic like ‘Human Rights Law’ in Quicksearch, http://search.library.yale.edu.

In the Search Results list you will now see real-time availability information.    A red ‘x’ appears if the title is checked out, and a green check mark displays if the title is available.

morris_search_results.fw

In the individual holdings screen, you can see the location, call number, and status of the title pulled directly in real time from Morris.

morris_title_holdings.fw

This is an important milestone in the Quicksearch project ;  the two Yale Library catalogs, Orbis and Morris, are both now fully represented in Quicksearch.

Learn about discovery interfaces at YUL with Rediscover Discovery

Last year, after the successful upgrade of our Articles+ e-resource discovery service and the beginning of the public beta phase of our Quicksearch unified discovery interface, library staff held an information session called Rediscovery Discovery, where we demonstrated features, functionality and sample search strategies in the Articles+ discovery interface and debuted the Quicksearch discovery interface.

This year, we will hold Rediscover Discovery again, covering Articles+ but with more focus Quicksearch. We will also introduce the digital collections search currently in development.

Rediscover Discovery is primarily aimed at instruction and public services staff, but is open to anyone who’d like to attend. Please register for each session as space is limited!

There will be two information sessions:

  • Tuesday August 18th, 10-11am in Bass L06 A&B register
  • Thursday August 20th, 2:30-3:30pm in 17 Hillhouse L07 register

See you at Rediscover Discovery!

SearchFest! sessions for August and October

Based on the success of the first SearchFest! event held in Bass L06 on Thursday July 9th, there will be two more sessions scheduled for the fall semester.

The goals of SearchFest!:

  • test out existing Orbis or Morris search strategies in our new unified discovery interface, Quicksearch.
  • demonstrate the features and functionality that are unique to Quicksearch
  • review the timeline for Quicksearch’s transition to production in January 2016
  • answer any questions from staff about how to use Quicksearch in either instruction or daily work

As with the first SearchFest!, there will also be pizza served at the beginning of each session.

To register for the August 18th session, click here.

To register for the October 8th session, click here.

See you at SearchFest!

FindIt, QuickSearch Security Design Review Completed

"data.path Ryoji.Ikeda - 4" by r2hox is licensed under CC BY-SA 2.0
data.path Ryoji.Ikeda – 4” by r2hox is licensed under CC BY-SA 2.0

Yale University Library FindIt and QuickSearch services have completed a Security Design Review (SDR) by the Information Security Office of Yale ITS.  These systems use the Hydra repository solution as the underlying technology stack.  The SDR process is used to provide recommendations for building, improving, or reengineering services to meet University policies, industry best practices, laws, and regulation requirements.  Thanks to Bob Rice for evaluating and implementing the recommendations and Tom Castiello and Marcus Aden from the Information Security Office for their insight and participation.

Development Notes for 10/13 – 10/17

Just a brief update on the work of our group for the past week.

We continue our efforts in contributing to the Fedora 4 project. We use Fedora as one of the core products in our Hydra implementation. Currently we have several installations of version 3. Version 4 has been in development for a little over a year with an expected release date of June 2015. While Yale has been a financial contributor to the Fedora Commons project for many years now, we only started contributing code to the project in 2013.

The Quicksearch project is also moving along swiftly. This week the major milestone of handling CAS login was completed. This is used for some features in the Blacklight software like the bookbag and search history. CAS is generally simple to integrate with most software products as long as the link between a NetID and the local user database can be made. In the case of Blacklight, making this link became complicated because of the use of several different code libraries in the specific version of Blacklight being used for Quicksearch, which is different from the version we use for our Hydra interface, FindIt.

Almost all efforts this week were related to ingest operations for the Kissinger project. There was also some vacation time taken so the output this week was limited.

Yesterday we met to discuss the development for full text search for objects ingested into Hydra. The work is broken up into the following steps:
1- alter the SOLR index to accept 2 new fields that will store full text
2- alter the Hydra ingest application to store the content of the TXT files into the new SOLR fields
3- setup the Blacklight controllers for handling if/when each of the FT fields are used in user searches
4- develop the Blacklight user interface to allow the FT search option

At this point we are only focused on the first two steps. 3&4 require us to have data in place. We will be moving steps 1 & 2 to the test environment the week of Oct 20 and then roll these changes into production the week of Oct 27. We will be doing all our FT testing with the Day Missions collection which uses a Hydra ingest package very similar to Kissinger.

This is a repost from another location that has more information on our full text search plan. So I will give a brief overview of what that plan looks like with the use cases used to draft this approach.

There are two types of full text search for objects we ingest into Hydra.

The first is the simplest, OCR text from a scanned image like a page in a book or a manuscript. This type of text is treated as an extension of the metadata making it simple to combine into search results since the text is considered open access.

The second is significantly more complex, it is where the contents of the full text require special permission to search so instead of the text being treated as an extension to the metadata, it is treated the same as we treat files that carry special access conditions. This permission would have been granted ahead of time so at the time you execute your full text search it will include results from the restricted items. This use case is currently specific to the Kissinger papers project but is being programmed to scale out as needed.

So the approach we are taking is kind of simple, we place the open access full text into one SOLR field and then the restricted access full text into a field specifically designed for restricted content. At the point when the search is executed, the open access text is searched and the restricted is filtered so that your search is only applied to the restricted contents which you have been granted access to view.