Skip to content
Innovative Idea Exchange

Settings and activity

1 result found

  1. 10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    AJ shared this idea  · 
    An error occurred while saving the comment
    AJ commented  · 

    Skip certain MARC subfields when preparing data for SIP2 connection.

    Specifically:
    When Sierra needs to send information to display an item title on a patron-facing device (automated materials handler, self-checkout kiosk, etc.) via SIP2, it currently appears to concatenate all occupied subfields of MARC field 245 and remove the delimiters. This means that certain information not intended to be patron-facing can end up appearing in the title the patron sees on screen (e.g. "880-01 Desu nôto 2..." appearing instead of just "Desu nôto 2...", where "880-01" is not actually part of the title, but rather a reference to another field elsewhere in the MARC record.)

    If Sierra excluded certain internal-only fields (like subfield 6 in field 245, where that "880-01" in the example was stored) when preparing data for SIP2 field ID "AJ" ("title identifier"), endpoints like self-checkout kiosks and automated materials handlers could display the correct title without displaying unecessary/confusing information.

    There may be other examples of subfields that should be skipped (within MARC field 245 and in others), but this is the first one we've run across.