Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    The Display Section

    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 Display section in the PNX includes data used in the brief and full display formats of the UI.

    The basis for the data elements used in the Display section is the Dublin Core element set. Dublin Core was selected as a metadata standard that is intended to support a broad range of purposes and resource types. In some cases, the names of the Dublin Core elements have been modified and a number of additional fields have been added.

    • Some sources may not include all of the data elements. In other cases, it is necessary to map data to the most suitable element.

    • Some formatting of the data for display is performed during the mapping process in order that this processing need not be performed online. For example, multiple occurrences of some fields are concatenated within the normalized record; it may be necessary to add or remove punctuation.

    • The display form of some of the fields noted below also serve as a hyperlinks that are used to search for additional records. It is important that you add all of these strings in the display to the corresponding fields in the Search section. For more information, see Enhanced Hypertext Linking.

    The following table lists the fields that are available in the Display section of the PNX.

    Display Section Fields
    Field Name Description

    availinstitution

    The availability institution is used at runtime to calculate the availability status for the brief results set. Automatically calculated by Primo from all availlibrary fields that belong to the institution, using the following logic:

    Primo merges the availability status from $$S for all availlibrary fields for the institution and creates the merged availability status as follows:

    • If one of the statuses is check_holdings, Primo sets the merged availability status to check_holdings.

    • If one of the statuses is available, Primo sets the merged availability status to available.

    • If neither of the above conditions exists, Primo sets the merged availability status to unavailable.

    If an institution does not have an availability field, Primo creates a field with the availability status does_not_exist.

    availlibrary

    The library-level availability status, which includes availability information per Primo library or sub-location, in addition to location information. The field is structured with subfields as follows:

    • $$I – institution code (required)

    • $$L – library code (required)

    • $$1 – sub-location

    • $$2 – call number

    • $$S – availability status (available, unavailable, check_holdings) (required)

    • $$3 – number of items

    • $$4 – number of unavailable items

    • $$5 – multi-volume flag: Y/N

    • $$6 – number of loans (for ranking purposes)

    • $$9 – indicates that the location represents online material. For more information, refer to Adding $$9ONLINE to Library Level Availability.

    • $$P – priority

    • $$X — source institution code (required for OvP)

    • $$Y — source library code (required for OvP)

    • $$Z — source sublocation code (not required for OvP)

    availpnx

    The availability PNX. Calculated by Primo from all availinstitution fields in the Display section, using the following logic:

    Primo takes all availinstitution fields and merges the availability status from $$S as follows:

    • If one of the statuses is check_holdings or available, Primo sets availpnx to available.

    • If the above condition does not exist, Primo sets availpnx to unavailable.

    This field is used in the UI when filtering by availability.

    contributor

    The contributor is an entity that is responsible for making a contribution to the content of the resource. Multiple occurrences are concatenated with a semicolon.

    Example of source data:

    • MARC21: 700/710/711 fields, stripping subfield $$d, and stripping from subfield $$t to the end. It is possible to reverse the author's last and first name by using a special routine (for example, Stephans, Mary to Mary Stephans).

    The display form of the contributor also serves as a hyperlink to search for additional records. It is important that all of the strings in the display also be added to the creatorcontrib field in the Search section.

    coverage

    The extent or scope of the content of the resource.

    creationdate

    The date or year when the resource was created or the year when the resource was published or manufactured.

    Example of source data:

    • MARC21: 008/07-10; 260 $$c.

    creator

    The content creator is an entity that is responsible for creating the content of the resource. Multiple occurrences are concatenated with a semicolon.

    An example of source data:

    • MARC21: 245 subfields $$c OR if 245 $$c is not present, 1XX, stripping subfield $$d, and stripping from subfield $$t to the end. It is possible to reverse the author's last and first name (for example, Stephans, Mary to Mary Stephans) by using a special routine.

    The display form of the creator also serves as a hyperlink to search for additional records. It is important that all of the strings in the display also be added to the creatorcontrib field in the Search section.

    crsinfo

    Course reserve information.

    description

    The description is any information that describes the content of the resource. This can be an abstract, contents notes, summary, and so forth. Multiple occurrences are not concatenated.

    Example of source data:

    • MARC21: 502, 505, 520 fields.

    edition

    The edition of the resource. This is one of the fields of the PNX record that is not derived from Dublin Core. The edition field is a key element in grouping bibliographic records.

    Example of source data:

    • MARC21: 250 $a and $b.

    format

    The physical format—physical description, extent, or digital manifestation of the resource. Multiple occurrences are concatenated with a semicolon.

    Example of source data:

    • MARC21: 300 and 340 fields. Can also be created from the control data in the leader and 008, 006 fields.

    identifier

    Any unique identifier of the record. Dublin Core defines this as an unambiguous reference to the resource within a given context. In the context of the PNX record, this is intended to be used for standard identifiers like ISBN and ISSN. Multiple occurrences are concatenated with a semicolon.

    Examples of source data (MARC21):

    • 020 $$a: prefix the value with ISBN.

    • 022 $$a: prefix the value with ISSN.

    ispartof

    The resource from which this resource is derived (for example, in an article from a journal - the journal is the source). Multiple occurrences are not concatenated. This type of relationship has been added as a specific relationship so it can be displayed as part of the brief results display.

    Example of source data:

    • MARC21: 773.

    The display form of this field also serves as a hyperlink to search for additional records. It is important that all of the strings in the display also be added to the title field in the Search section.

    language

    The language of the resource. The language is stored in coded form (ISO 639-2) and is translated in the UI. Multiple occurrences are concatenated with a semicolon.

    If the language is not in ISO 639-2 form, the normalization process attempts to convert it to this form. If this is not possible, the language is unknown (using the und code).

    Example of source data:

    • MARC21: 008/35-37; if blank, use 041 subfield $$a.

    oa

    Intended for use by Primo Central to indicate whether a record is open access or not.

    publisher

    An entity that is responsible for making the resource available. Multiple occurrences are concatenated with a semicolon.

    Example of source data:

    • MARC21: 260 subfields $a and $b.

    relation

    A reference to a related resource. Multiple occurrences are not concatenated.

    Example of source data:

    • MARC21: 440, 830, 760-787 except for 773.

    The display form of this field also serves as a hyperlink to search for additional records. It is important that all of the strings in the display also be added to the title field in the Search section.

    rights

    Information about the rights of the resource.

    source

    The source repository from which the record was derived.

    subject

    The topic of the resource’s content. Multiple occurrences are concatenated with a semicolon.

    Example of source data:

    • MARC21: 6XX fields

    The display form of the subject also serves as a hyperlink to search for additional records. It is important that all of the strings in the display also be added the subject field in the Search section.

    title

    The name that is given to a resource. The title can be created from a number of fields and subfields from the source record. Multiple occurrences are not concatenated.

    Example of source data:

    • MARC21: 245 subfields $$a and $$b.

    type

    The resource type that represents the main format of the record or the type, based on a master list of main record types. It is recommended to include only a minimum number of types (~10). Primo sites are able to modify this list so that it is suited to the content of its repository and its users. The type is used to determine which icon displays next to the record in the brief and full results list. Every record must have a single type field.

    The default resource type list includes book, journal, article, text_resource (includes text resources that cannot be identified as a book, journal, or article), image, video, audio, map, score, and other (includes records that cannot be classified as any other resource type).

    Example of source data:

    • MARC21: Mapping based on the leader position 6 and the 007 and 008 fields.

    unititle

    The uniform title will be displayed with the title of the resource when the merged FRBR record is displayed.

    Example of source data:

    • MARC21: 240 subfields a, d,m,n, p, r, s

    The display form of this field also serves as a hyperlink to search for additional records. It is important that all of the strings in the display also be added to the title field in the Search section.

    userrank

    A rank or score that is assigned by the end user for the resource.

    userreview

    The user review, which is added by the end user.

    vertitle

    The vernacular title is used when the record contains both a transliterated title and a title in the vernacular (as in the MARC format).

    Example of source data:

    • MARC21: 880 with subfield 6 =245 and subfields a and b.

    lds01 - lds200

    Local display fields.

    • lds50 is reserved for use with Primo Central and should not be used locally.

    • The display form of this field also serves as a hyperlink to search for additional records. It is important that all of the strings in the display also be added to the corresponding field in the Search section.

    • Was this article helpful?