The Search Section

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

This information is not applicable to Primo VE environments. Only the Display, Facets, and Search sections are configurable in Primo VE. For more details, see Mapping to the Display, Facets, and Search Sections in the Primo VE Record.

Return to menu

The Search section in the PNX includes the data (including metadata and full-text) being indexed during a search. The data is in several indexes to enable qualified searching—that is, to search for a specific index and/or enable ranking based on the field in which the query search terms were found.

Repeatable fields of the source record are mapped to repeatable fields of the PNX record.

The following table describes the fields in the Search section. In addition to these fields, Primo sites can add up to fifty local index fields.

Search Section Fields
Field	Description
addsrcrecordid	The index that is created from the additional source record ID from the Control section. If the title links on the Requests and Loans tabs are not working in My Library Card, make sure that your normalization rules are correctly mapping the MMS ID from the Alma source records to the search/addsrcrecordid field in the PNX.
addtitle	This field contains additional titles that are related to the record. Examples of MARC 21 source data: 440 subfield $$a 830 subfield $$a
Alttitle	The alternative titles. Examples of MARC 21 source data: MARC 21: 130, 210, 240, 246
creationdate	This field contains the publication date, which is the year when either the resource was created or the resource was published or manufactured. Valid years are one to four digits (0 - 9). For example: 1, 75, 910, and 2016. BCE dates are preceded by a minus sign. For example: -5. Multiple occurrences of this field are possible. The creation dates are used during searches and when refining dates with the date slider. The following notes apply to the date slider: The initial date ranges that display in the date slider are based on the ranges in the creation date facet (see facets section), not the dates from this field. Out of the box, the Creation Date facet ranges are hidden. If you want to display the facet ranges, change display:none to display:block in the following line of your local CSS file: .EXLFacetContainer ol li.EXLHiddenFacetCreationDate {display:none;}
creatorcontrib	The normalized form of the creators and contributors. Examples of MARC 21 source data: MARC 21:1XX and 700/710/711 fields.
creator	Replaces the creatorcontrib field to allow separate ranking of the creator and contributor fields. Examples of MARC 21 source data: MARC 21:1XX fields.
contributor	Replaces the creatorcontrib field to allow separate ranking of the creator and contributor fields. Examples of MARC 21 source data: MARC 21:700, 710, and 711 fields.
crsdept	The course department.
crsid	The course ID.
crsinstrc	The course instructor.
crsname	The course name.
description	Description of the content of the resource. This includes abstract, contents notes, summary, and so forth. Examples of MARC 21 source data: MARC 21: 502, 505, 520 fields.
enddate	Contains the end date in date ranges. For more information, see Configuring Date Ranges.
frbrid	The ID assigned to records following the FRBRization process. The field is updated by the system.
fulltext	Words from the full-text that were added in the enrichment phase.
general	A general index for fields that have not yet been added to any of the specific indexes and should be. For example, publisher.
isbn	The ISBN of the item. Example of MARC 21 source data: MARC 21:020.
issn	The ISSN of the item. Example of source data: MARC 21: 022.
orcidid	The ORCID ID.
pnxtype	An internal Primo index that defines the type of PNX record. The field is updated by the system.
recordid	The recordid field from the Control section, which is used to locate a specific record. This is an internal Primo index.
recordtype	Record type—not in use.
ressearscope	The restricted search scope, used to limit discovery of certain PNX records to specific user groups. In order to limit discovery, the records should be assigned a denied search scope. Access is enabled based on the denied search scopes defined in a Back Office table. Access can be enabled based on institution, on-off campus, and user group. This field is copied to the scope field for indexing by the search engine.
rsrctype	The type field from the Display section.
scope	Used in creating search scopes and denied search scopes. The values from the search scope and restricted search scope fields above should be copied to the scope field.
searchscope	Used to create search scopes values for use in Primo views. This field is copied to the scope field for indexing by the search engine.
sourceid	Based on the sourceid field from the Control section. It may be required to filter out certain records and is an internal Primo index.
startdate	Contains the start date in date ranges. For more information, see Configuring Date Ranges.
subject	The topic of the content of the resource. Example of source data: MARC 21: 6XX fields.
syndetics_fulltext	Used for abstracts and other data loaded from Syndetics. This field is updated by the system.
syndetics_toc	Used for table of contents data loaded from Syndetics. This field is updated by the system.
title	The main title. Examples of source data: MARC 21: 245 subfields $$a and $$b In the UI, title searches also include the alttitle and addtitle fields, but they are given far less boost in the rankings than the main title. When performing Starts with searches in Primo, the sort/title mapping is used instead of this field.
toc	This field contains words from the table of contents.
usertag	This field contains end-user tags. This field is updated by the system.
lsr01 - lsr50	Local search fields.