(Go Live) Make the 930 Field Searchable in Primo

Legend: NOT STARTED IN PROGRESS STALLED DECIDED

Recommendation

We recommend that campuses make the 930 field searchable in Primo to facilitate the finding and aggregation of CDL collections.

Campuses that have historically used the 973 field for local collections information should also consider making that field searchable, if helpful for staff.

Campuses can choose to include the 930 field search in their Advanced search, if desired. In this case, we recommend campuses choose the display label “Package Name” in order to avoid user confusion.

This is an interim solution that should be revisited in 6-12 months. Discovery recommends that the eResources Operations Sub-Team lead the effort to find a more robust, alternative approach for facilitating these staff workflows. Coordination with the Discovery Operations Sub-Team and the forthcoming Analytics group is also recommended.

Reasoning

The use of the 930 field as a title hook for CDL collections predates the SILS project; this use was identified by the Next-Generation Technical Services initiative. Collections staff rely on this field for finding, identifying, and aggregating materials from CDL licensed collections. Library staff may also use the information in the 930 field for troubleshooting purposes.

In discussions with RMFG and AEFG groups, Discovery has learned that this use of the 930 field may be more limited and less robust in Primo VE than it was in traditional LMS systems previously used by campuses. Due to the structure of Alma/Primo, using the 930 field for this work probably yields non-comprehensive results. Activation of Dedup may also reduce effectiveness of using the 930 field for this work.

Regardless of its limitations, searchability of the 930 field is still valuable for library staff and should be facilitated as an interim solution to facilitate this staff work.

Additional/Alternative Methods

Alma Analytics can also be used for finding and aggregating materials from CDL licensed collections. However, this approach is not usable by staff who do not have Alma logins and is less useful for troubleshooting purposes.

Using Alma Analytics as a search tool may be helpful for this type of work. See these instructions from UC Santa Cruz for more information.

Configuration

To add 930 as a searchable field first go to Configuration>Discovery>Other>Local Fields Using Search and Facet Normalization Rules and click on Add and choose a local field number:

Next go to Configure>Discovery>Display Configuration>Manage display and local fields and click on Add field and select the Add local field:

This will open the Define a Local Field form. Select the local field that you are adding from the Field to edit field and create the index’s name in the Display label field. In Local Field Details check Enable field for search.

Next you will need to go down to the normalization rules and create a MARC21 normalization rule for display…

… and a MARC21 normalization rule for search and facet.

Note that above sample norm rule only indexes the 930 subfield a. This may need to be altered once CDL/SCP documents the subfields it will be using in the 930. Once you have finished creating your normalization rules click Save (in the upper right corner of the Define a Local Field form) to complete the local field configuration.

To add a new local index to your local PrimoVE interface go to Configuration>Discovery>Display Configuration>Configure Views and select the Advanced Search Configuration tab. In the List of Indexes area click on Add Index:

This will open a form. Select your new index from the top drop-down menu (you should see your new display label, in this case “Package Name”) and choose which search slots the index should be applied.

Finish by clicking Add index (bottom right).

Open your PrimoVE in a browser (if already open be sure to refresh and/or clear your cache) you should see the new index in your advanced search drop down.

Once you have completed your configuration you will need to open a Salesforce ticket with ExLibris to re-index (this required for all new 9xx indexes). The re-index should probably be run prior to adding the new index to the discovery layer.

Dependencies

No dependencies identified

Questions to consider

What are the benefits of making the 930 field searchable in Primo?

Are there any usability impacts on end-users?

Action Log