Enhanced Hypertext Linking
Previously, both the old and new UIs supported hypertext linking in the following PNX display fields: creator, contributor, subject, and lds30-lds39 fields. When a link was clicked, the system performed an advanced search using the exact contents of the entire field, which was created from multiple subfields.
This functionality includes the following enhancements:
-
For your local repository only, hypertext linking has been extended to the following PNX display fields: ispartof, unititle, and relation.
-
Each field continues to display all subfields, but advanced searches are performed using the subfields that are prefixed with the new $$Q parameter. For example:
<creator>Fitzgerald-Jones, Sandra 1938- interviewer$$QFitzgerald-Jones, Sandra</creator>
-
Allow exact and contains search operations in the Advanced search. The Hypertext Linking Definitions mapping table has been added to allow you to configure the search operator used for each of the supported display fields. For more information, see Defining a Field's Search Operator.
Back Office Configurations
This section describes the configurations that support this functionality.
Defining a Field's Search Operator
The Hypertext Linking Definitions mapping table allows you define which type of search is performed when users click the link provided for each type of display field: exact (exact phrase only), facet exact (exact phrase and facet), or contains. The Context field indicates whether the search is relevant to ANY (all scopes) or L (local scopes only) scopes.
You may need to enable the rows that contain the following new hypertext linking fields: relation, unititle, and ispartof.
Facet Exact Operator
For the new Primo UI only, the facet exact operator provides a more precise search than the exact operator by adding the value of the corresponding facet field to the advanced search query when users select an enhanced hypertext link in the record's full details. For example:
When using this operator, it is recommended that you use the same normalization rules for the facet field as you do with the $$Q subfield in the display field.
The following table lists the corresponding facet fields. Note that the facet field is not used with title searches.
Display Field |
Search Field |
Facet Field |
---|---|---|
lds30-lds39 |
lsr30-lsr39 |
lfc30-lfc39 |
contributor |
creator |
creator |
creator |
creator |
creator |
subject |
sub |
topic |
ispartof |
title |
not used |
relation |
title |
not used |
unititle |
title |
not used |
Default Normalization Rules
The normalization rules listed in the table below are included in the following MARC templates: Generic, Voyager, Aleph, Alma, Unicorn, and SFX. You will need to apply them to your normalization rules and run an update pipe to enable the new functionality.
-
If the linking text (the portion of the display field that is prefixed with $$Q) is omitted, the system will use the entire display field for linking.
-
If you are using lateral links (lds30 - lds39), you will need to add normalization rules that include the $$Q parameter. For more information, see Creating Lateral Links for Local Fields.
Source Tag | Displayed Subfields | $$Q (Subfields Searched) |
Display/creator: | ||
100, 880-100 | a, b, c, d, e, j, q, u | a, b, c, d, j |
110, 880-110 | a, b, c, d, e | a, b, c, d |
Display/contributor: | ||
700, 773-880 | a, b, c, d, e, j, q, u | a, b, c, d, j |
710, 880-710 | a, b, c, d, e | a, b, c, d |
Display/ispartof: | ||
773, 700-880 | all except for x, y, and z | t |
Display/relation: | ||
400, 400-880 | Exclude x | t |
410, 410-880 | Exclude x | t |
411, 411-880 | Exclude x | t |
440, 440-880 | Exclude x | a |
490, 490-880 | Exclude x | a |
800, 800-880 | Exclude x | t |
810, 810-880 | Exclude x | t |
811, 811-880 | Exclude x | t |
830, 830-880 | Exclude x | a |
840, 840-880 | Exclude x | a |
780, 880-780 | Exclude w, x, y, 6, 7 | t |
785, 880-785 | w, x, y, 6, 7 | t |
240 | a, d, m, n, p, r, s | a |
130 | a, d, m, n, p, r, s | a |