Discovery Layer Strategies for Kuali OLE: Indiana University
1. Discovery Layer Strategies
for Kuali OLE
Courtney Greene McDonald, Indiana University
Frances McNamara, University of Chicago
Andrew Preater, Senate House Libraries, University of London
29-30 Oct 2013 | Senate House, London | tweet at #kduk13
2. Discovery Layer Strategies
for Kuali OLE
Indiana University
Courtney Greene McDonald
Head, Discovery & Research Services
IU Bloomington Libraries
crgreene@indiana.edu
29-30 Oct 2013 | Senate House, London | tweet at #kduk13
3. A few words about Indiana University
Nine campuses, 50 libraries
IUCAT – shared statewide online catalog
SirsiDynix Symphony ILS
System-wide request delivery
Diversity of collections (monographs,
e-resources, various media, digital
collections)
8 mil bibliographic records
Statewide participation leads to a complex
data environment:
- Who shares records? What records?
How?
- Cataloging services provided to “extra-systems”
libraries
- Vendor records
- Widely varying formats, classification
schemes; numerous languages
IPFW
4. A few words about Indiana University
Nine campuses, 50 libraries
IUCAT – shared statewide online catalog
SirsiDynix Symphony ILS
System-wide request delivery
Diversity of collections (monographs,
e-resources, various media, digital
collections)
8 mil bibliographic records
Statewide participation leads to a complex
data environment:
- Who shares records? What records?
How?
- Cataloging services provided to “extra-systems”
libraries
- Vendor records
- Widely varying formats, classification
schemes; numerous languages
IPFW
5. A few words about Indiana University
Nine campuses, 50 libraries
IUCAT – shared statewide online catalog
SirsiDynix Symphony ILS
System-wide request delivery
Diversity of collections (monographs,
e-resources, various media, digital
collections)
8 mil bibliographic records
Statewide participation leads to a complex
data environment:
- Who shares records? What records?
How?
- Cataloging services provided to “extra-systems”
libraries
- Vendor records
- Widely varying formats, classification
schemes; numerous languages
7. Discovery Layer Selection
• Review took place in early 2011, candidate
applications were Blacklight & VuFind
• Either system judged able to fulfill baseline
requirements
• Report & recommendations available at:
http://hdl.handle.net/2022/13621
8. Highlights on Selection
• Reasons for choosing Blacklight
• Exceptional flexibility
• Development community
Other general requirements included
•
•
•
•
•
Integrate non‐MARC metadata from local collections
Integrate with technologies enabling single sign on for login to IUCAT services (My
Account, tagging, lists, etc) & off‐campus access to online resources.
Permalinks for records & searches
Generate properly formatted citations for major styles (Chicago, APA, MLA).
Single search box on screen (with access to advanced search) that performs a keyword search using an
index defined by librarians.
9.
10.
11.
12.
13.
14.
15. Implementation
• Work began in Summer 2011
• public beta release in November 2012
• transition to Blacklight interface as primary entry point
in May 2013
• A few details
•
•
•
•
Ruby v PHP
Data: Indexing, refreshing, displaying
Campus views
Browse Call Number
28. Implementation: Ask A Librarian
Improved patron service:
directing reference questions submitted via
IUCAT to the appropriate campus reference
service
routing patrons directly to campus library
websites
More details at: https://blogs.libraries.iub.edu/iucatbeta/2013/01/ask-a-librarian/
11/7/2013
34. Implementation: tricky bits
• Data
•
•
•
Configuration of indexes
Going from more to less structured search
Format fun!
• Authentication & account management
•
•
•
•
My Account services
Off-campus authentication
Single sign-on (sort of: 2 systems + limited resident access)
Requesting items (2 systems: Sirsi + offsite storage)
• Statewide scope
35. Implementation: tricky bits
• Data Structures Group
– Formed Data Structures Group: technical services
staff (incl representatives from serials, music
library, law library)
• Charge: make and document recommendations
for configuration of indexing and record display
within Blacklight. This includes but is not limited
to search indexes, faceting, the display of
bibliographic records and other search and
browse displays.
36. Implementation: tricky bits
• Data Structures Group
– Formed Data Structures Group: technical services
staff (incl representatives from serials, music
library, law library)
• Charge: make and document recommendations
for configuration of indexing and record display
within Blacklight. This includes but is not limited
to search indexes, faceting, the display of
bibliographic records and other search and
browse displays.
44. Looking forward
• Lists
• New titles
• Enhanced views /
additional customization
by campus or format
• Transition to Kuali OLE
http://www.flickr.com/photos/waikikiweekly/3639971503/
http://www.flickr.com/photos/afeicht1/2797850952/
45. Discovery Strategy for Kuali OLE
• Implement catalog discovery layer overlay (Blacklight) - check
• Expected Kuali OLE Implementation December 2015
• Integration with Blacklight and Ebsco Discovery Service for subscribing
campuses (Bloomington, Kokomo, South Bend) [using Ebsco Blacklight
gem; similar functionality available for VuFind]
•
Integration with other structured data sources (not explicitly dependent
on OLE migration)
• IU Digital Collections
• Other campus specific or contextual search data
46. Ebsco Discovery Service
• IU Bloomington
o EDS beta partner, launched as OneSearch@IU in August 2011
o Integrated into library site search/resource gateway search, link on home
page, tab in subject guides, tabbed search box on Find Information page
o Drupal 7 module for website integration
• IU Kokomo
o Launched Sept 2011
o Search box on home page, Find Information page, resources A-Z guide, and
Public Access & Research Resources page
• IU South Bend
o Just launched for this academic year
• All campuses share a single catalog extract
48. Thank you!
Courtney Greene McDonald
crgreene@indiana.edu
Access IUCAT: http://iucat.iu.edu/
Additional reading on the project
•
Moore, Kate B., and Courtney Greene. 2012. “The Search for a New OPAC: Selecting an Open Source
Discovery Layer.” Serials Review 38 (1) (March): 24–30.
•
Greene, Courtney, Barbara Gushrowski, Randall Lent, Chris Evin Long, Mary Beth Minick, Kate Banet
Moore, Gwendolyn Pershing, Mary Pagliero Popp, and Susan Skekloff. 2011. “IU Libraries Discovery Layer
Task Force Summary Report and Recommendation”. Indiana University Libraries.
http://hdl.handle.net/2022/13621.
Notas del editor
4 areas were identified in the Discovery Layer TF report Courtney just mentioned. Each of these areas included, required, highly desirable, and desirable attributes. I’ve selected some of the “big ticket items” that were either particularly crucial, unique, difficult or all of the above.General Features & Functionality - required and desired features and functionalities of the overall interface of the discovery layer as well as features and functionalities not easily classified under the other four rubric categories.Authentication & Account Management - Many of these functions are highly reliant upon the underlying ILS, and are crucial to maintaining a baseline level of patron services. Ultimately, public acceptance of the new interface for IUCAT and for the OLE project is dependent upon our ability to integrate with existing local systems used to facilitate identity management, to provide critical patron services related to account management, such as request delivery, holds management, renewals, etc., and to facilitate off‐campus access to campus‐specific electronic subscription‐based resources.Export & Sharing - citation services, creating bibliographies/lists, standard sharing functionsSearch Functionality & Results Display – features and functions of search and results display
4 areas were identified in the Discovery Layer TF report Courtney just mentioned. Each of these areas included, required, highly desirable, and desirable attributes. I’ve selected some of the “big ticket items” that were either particularly crucial, unique, difficult or all of the above.General Features & Functionality - required and desired features and functionalities of the overall interface of the discovery layer as well as features and functionalities not easily classified under the other four rubric categories.Authentication & Account Management - Many of these functions are highly reliant upon the underlying ILS, and are crucial to maintaining a baseline level of patron services. Ultimately, public acceptance of the new interface for IUCAT and for the OLE project is dependent upon our ability to integrate with existing local systems used to facilitate identity management, to provide critical patron services related to account management, such as request delivery, holds management, renewals, etc., and to facilitate off‐campus access to campus‐specific electronic subscription‐based resources.Export & Sharing - citation services, creating bibliographies/lists, standard sharing functionsSearch Functionality & Results Display – features and functions of search and results display
4 areas were identified in the Discovery Layer TF report Courtney just mentioned. Each of these areas included, required, highly desirable, and desirable attributes. I’ve selected some of the “big ticket items” that were either particularly crucial, unique, difficult or all of the above.General Features & Functionality - required and desired features and functionalities of the overall interface of the discovery layer as well as features and functionalities not easily classified under the other four rubric categories.Authentication & Account Management - Many of these functions are highly reliant upon the underlying ILS, and are crucial to maintaining a baseline level of patron services. Ultimately, public acceptance of the new interface for IUCAT and for the OLE project is dependent upon our ability to integrate with existing local systems used to facilitate identity management, to provide critical patron services related to account management, such as request delivery, holds management, renewals, etc., and to facilitate off‐campus access to campus‐specific electronic subscription‐based resources.Export & Sharing - citation services, creating bibliographies/lists, standard sharing functionsSearch Functionality & Results Display – features and functions of search and results display
4 areas were identified in the Discovery Layer TF report Courtney just mentioned. Each of these areas included, required, highly desirable, and desirable attributes. I’ve selected some of the “big ticket items” that were either particularly crucial, unique, difficult or all of the above.General Features & Functionality - required and desired features and functionalities of the overall interface of the discovery layer as well as features and functionalities not easily classified under the other four rubric categories.Authentication & Account Management - Many of these functions are highly reliant upon the underlying ILS, and are crucial to maintaining a baseline level of patron services. Ultimately, public acceptance of the new interface for IUCAT and for the OLE project is dependent upon our ability to integrate with existing local systems used to facilitate identity management, to provide critical patron services related to account management, such as request delivery, holds management, renewals, etc., and to facilitate off‐campus access to campus‐specific electronic subscription‐based resources.Export & Sharing - citation services, creating bibliographies/lists, standard sharing functionsSearch Functionality & Results Display – features and functions of search and results display
4 areas were identified in the Discovery Layer TF report Courtney just mentioned. Each of these areas included, required, highly desirable, and desirable attributes. I’ve selected some of the “big ticket items” that were either particularly crucial, unique, difficult or all of the above.General Features & Functionality - required and desired features and functionalities of the overall interface of the discovery layer as well as features and functionalities not easily classified under the other four rubric categories.Authentication & Account Management - Many of these functions are highly reliant upon the underlying ILS, and are crucial to maintaining a baseline level of patron services. Ultimately, public acceptance of the new interface for IUCAT and for the OLE project is dependent upon our ability to integrate with existing local systems used to facilitate identity management, to provide critical patron services related to account management, such as request delivery, holds management, renewals, etc., and to facilitate off‐campus access to campus‐specific electronic subscription‐based resources.Export & Sharing - citation services, creating bibliographies/lists, standard sharing functionsSearch Functionality & Results Display – features and functions of search and results display
4 areas were identified in the Discovery Layer TF report Courtney just mentioned. Each of these areas included, required, highly desirable, and desirable attributes. I’ve selected some of the “big ticket items” that were either particularly crucial, unique, difficult or all of the above.General Features & Functionality - required and desired features and functionalities of the overall interface of the discovery layer as well as features and functionalities not easily classified under the other four rubric categories.Authentication & Account Management - Many of these functions are highly reliant upon the underlying ILS, and are crucial to maintaining a baseline level of patron services. Ultimately, public acceptance of the new interface for IUCAT and for the OLE project is dependent upon our ability to integrate with existing local systems used to facilitate identity management, to provide critical patron services related to account management, such as request delivery, holds management, renewals, etc., and to facilitate off‐campus access to campus‐specific electronic subscription‐based resources.Export & Sharing - citation services, creating bibliographies/lists, standard sharing functionsSearch Functionality & Results Display – features and functions of search and results display
4 areas were identified in the Discovery Layer TF report Courtney just mentioned. Each of these areas included, required, highly desirable, and desirable attributes. I’ve selected some of the “big ticket items” that were either particularly crucial, unique, difficult or all of the above.General Features & Functionality - required and desired features and functionalities of the overall interface of the discovery layer as well as features and functionalities not easily classified under the other four rubric categories.Authentication & Account Management - Many of these functions are highly reliant upon the underlying ILS, and are crucial to maintaining a baseline level of patron services. Ultimately, public acceptance of the new interface for IUCAT and for the OLE project is dependent upon our ability to integrate with existing local systems used to facilitate identity management, to provide critical patron services related to account management, such as request delivery, holds management, renewals, etc., and to facilitate off‐campus access to campus‐specific electronic subscription‐based resources.Export & Sharing - citation services, creating bibliographies/lists, standard sharing functionsSearch Functionality & Results Display – features and functions of search and results display
4 areas were identified in the Discovery Layer TF report Courtney just mentioned. Each of these areas included, required, highly desirable, and desirable attributes. I’ve selected some of the “big ticket items” that were either particularly crucial, unique, difficult or all of the above.General Features & Functionality - required and desired features and functionalities of the overall interface of the discovery layer as well as features and functionalities not easily classified under the other four rubric categories.Authentication & Account Management - Many of these functions are highly reliant upon the underlying ILS, and are crucial to maintaining a baseline level of patron services. Ultimately, public acceptance of the new interface for IUCAT and for the OLE project is dependent upon our ability to integrate with existing local systems used to facilitate identity management, to provide critical patron services related to account management, such as request delivery, holds management, renewals, etc., and to facilitate off‐campus access to campus‐specific electronic subscription‐based resources.Export & Sharing - citation services, creating bibliographies/lists, standard sharing functionsSearch Functionality & Results Display – features and functions of search and results display
Within the campus views, users will be presented with 4 options:IUCAT Help (links to UITS Knowledge Base IUCAT information – we will continue to add to this info)Ask A Librarian (links to your campus library’s ask a librarian page; in the case where a campus has multiple libraries [ie Bloomington], queries will need to be forwarded as appropriate from the linked reference point)Report error/Submit feedback (leads to a web form that submits to the implementation team) – Jira issue and bug tracking systemLibrary website (links to your campus library’s website, or in the case of IUPUI, to a splash page: http://www.iupui.edu/about/libraries.html)
Within the all-IUCAT (union catalog) view, users will be presented with 3 options:IUCAT Help (links to UITS Knowledge Base IUCAT information – we will continue to add to this info)Report error/Ask a Research QuestionUsers will be able to use this single form, below, to report errors, share comments, or ask research questions.For responses in which the category Ask A Research Question is selected, the form data will route directly as an email to the selected campus library’s reference email address (as previously, in the case where a campus has multiple libraries [ie Bloomington], queries will need to be forwarded as appropriate.) Error reports and general comments will route to a Jira (issue and bug tracking system) project site where they can easily be transformed into bug reports and enhancement requests for developers.Campus information (links to campus splash page) that allows user to select appropriate campus homepage (not library page)
To improve the presentation of our data, a Data Structure Subgroup was formed whose charge was make and document recommendations for … The group did what I consider some painstaking work looking through the SOLR MARC and indexing scripts underpinning Blacklight to make recommendations. The TF then used this information to look at how the facets were populated from the indexes and made adjustments to accommodate differences in data. By customizing and prioritizing the data being indexed, we were able to improve the relevancy ranking of search results and the filing of records within the facets.A fair amount of data cleanup also occurred to correct issues that couldn’t otherwise be rectified.
To improve the presentation of our data, a Data Structure Subgroup was formed whose charge was make and document recommendations for … The group did what I consider some painstaking work looking through the SOLR MARC and indexing scripts underpinning Blacklight to make recommendations. The TF then used this information to look at how the facets were populated from the indexes and made adjustments to accommodate differences in data. By customizing and prioritizing the data being indexed, we were able to improve the relevancy ranking of search results and the filing of records within the facets.A fair amount of data cleanup also occurred to correct issues that couldn’t otherwise be rectified.
5/18/2012Robert McDonald met with the Discovery Layer Implementation Task Force this Tuesday and in the course of our discussion we talked about issues surrounding authentication and authorization within the new Blacklight interface. Robert has put together a specification for a 'redirector' service to enable access to e-resources from within the catalog (attached).