Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Legend: NOT STARTED IN PROGRESS STALLED DECIDED

Status

DECIDED

Description

Should we harmonize our default search profiles in Primo VE? If so, how should the default search profile be configured?

Decision

We recommend harmonizing the default search profile across campuses. The default search profile should be configured to include the IZ + NZ Physical/Electronic + CDI

Owning group

Discovery FG

Approver

PPC

Stakeholders

R = Discovery FG
A = WG
C =  Campus Discovery groups, Resource Management, Acquisitions & E-Resources, Fulfillment FG
I = End User Outreach Subgroup, Digital Collections FG

Decision-making process

  • Consulted with other consortia (University at Buffalo) and local UC campus groups for feedback

  • Compared configuration options and their impact on end user experience

  • Tested existing configurations at other Primo VE institutions (CSU, SUNY)

Priority

Mandatory before Go-live

Due date

02/15/2021

Recommendation

We do recommend harmonizing the default search profile across campuses. The default search profile should be configured to include the IZ (local collections) + NZ (entire network, both electronic and physical) + CDI

Reasoning

  • This configuration facilitates the discovery of desired materials without requiring the user to change search profiles (aka scopes)

  • Maximizing the materials discoverable via the default search profile reduces the need for the user to understand the system architecture

  • Including network holdings improves the discovery of desired known items

  • Boosting local holdings allows prioritization of immediately accessible items to local users

  • Additional reasoning included in Pros/Cons table below

Background

The Discovery Functional Group is charged with the delivery of, “A Primo VE instance for the UC Libraries Network Zone (NZ) will also be developed to provide centralized indexing, shared customization of views via a Central Package, and centralized configuration of mapping and code tables, allowing for the discovery of records and holdings across the NZ, and services such as fulfillment and resource sharing.”

The most common default search profile configurations for consortial Primo VE instances are:

  • IZ only (eg. “Library Catalog”)

  • IZ + CDI (eg. “[Campus] Collections” or “Book, articles, and more at [Campus]”)

  • IZ + NZ + CDI (eg. “Everything [Campus/Consortia]”)

Proposal: Discovery FG should make a recommendation on whether or not campuses should harmonize on the configuration of their default search profile. If harmonization is recommended, Discovery FG should make a recommendation on how the default search profile should be configured.

Working assumptions:

  • Campuses can effectively boost their local holdings to display above those of consortia members in search results

  • Staff at UC libraries will continue to assist patrons from across the UC system via chat reference

  • Materials managed in the NZ will be accessible via the IZ if that item is available to that campus

Dependencies

No dependencies identified

Questions to consider

What are the benefits and risks of harmonizing on the default search profile?

How is the end user experience impacted by the inclusion or exclusion of network materials (NZ) in the default search profile?

How is the end user experience impacted by the inclusion or exclusion of CDI records in the default search profile?

Options considered

Harmonize default search profile?

Not Harmonized

Harmonized

Training and end-user communication artifacts can be shared among campuses.

(minus)

(plus)

Reference staff helping patrons at another UC have a consistent experience.

(minus)

(plus)

Campuses can configure search profiles their own way.

(plus)

(minus)
Campuses with separate sites for small, special libraries (e.g. law or medical) can still chose a different default search profile for a home page.

Include network materials in the default search profile?

Network materials not included in default

Network materials are included in default

End users seeking a known item at another UC would discover it via the default search scope

(minus)

(plus)

End users would not need to understand search profiles in order to effectively use the system thereby improving the experience of novice users.

(minus)

(plus)

End users can surface content imported directly into the Network Zone via the default search scope, exposing users to content they may not have otherwise known was in the system (eg. digital collections such as Calisphere)

(minus)

(plus)

End users can discover eBooks and journals from CDL packages in the default search profile. +

(plus)

(plus)

Users will not be frustrated by finding eBooks only available at another UC

(plus)

(minus)

However, it’s possible for signed-in users to initiate purchase requests for campuses that want this enabled. It can be limited by user group, e.g. faculty.

Advanced end users who want to see only materials available to them locally do not have to use a facet to restrict their search results. *

(plus)

(minus)

+ Confirmed in Basecamp message. 'If a record is managed in the NZ and available for your institution, the record is searchable in LibraryCatalog scope.' https://3.basecamp.com/3765443/buckets/15553579/messages/3354455308

Include CDI in the default search profile?

CDI materials not included in default

CDI materials are included in default

End users would discover articles, book chapters, music, and other CDI items in the default search profile.

(minus)

(plus)

Aligns with end users' expectation (as seen in catalog analytics data and described in the literature) of a “single search” experience for finding library materials.

(minus)

(plus)

End users would not need to understand search profiles in order to effectively use the system thereby improving the experience of novice users.

(minus)

(plus)

Advanced end users who only want to see books or other local material in their search results will not have to use a facet to restrict their results set. *

(plus)

(minus)

Advanced, known-item type search results may sometimes defy user expectations (such as book review records appearing above the record for the book)

(plus)

(minus)

However, during the test-load phase campuses will test the local boosting in Primo to see if it alleviates some known issues with more advanced searches.

* Using facets is straightforward and already-Primo campuses do see thousands of sessions of facet use per month. At Irvine, for 2019 and 2020, totals of sessions where facets are used are about 15% of total sessions.

Action Log

Action/Point Person

Expected Completion Date

Notes

Status

Create document summarizing Primo Search Profile configuration options

12/11/2020

Primo Search Profiles Overview document shared in Google Drive

Complete

Ask Primo listserv for consortial experiences

01/06/2021

Complete

Deliver summary document to campus stakeholders and discuss end user needs for discovery / All Discovery FG members

01/15/2021

Complete

Consult with Resource Management, Acquisitions & E-Resources, and Fulfillment groups

02/10/2021

PPC for approval

  • No labels