OPAC view title display – punctuation missing

Bug #1867025 reported by Elaine Hardy
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Undecided
Unassigned

Bug Description

OPAC view title display – punctuation missing

When a bib record for a work containing multiple titles and the 245 containing either the correct punctuation between the |a and |b (a semicolon) or a |h GMD is present, the OPAC view excludes the punctuation in both the result list and the record display.

Examples:

For bib record of video recording containing “Assassins” and “The Specialist”, the 245 correctly formatted as:

245 00 ‡aAssassins ; ‡bThe specialist / ‡cWarner Bros.

Displays in OPAC view as:

Assassins The specialist (see: https://gapines.org/eg/opac/record/4221829?locg=1;detail_record_view=0;page=0;query=title%3Aassassins%20specialist)

If the incorrect : is used to separate multiple titles in the 245, the punctuation is included in the OPAC view title and search result display.

If the |h is still present (while it is no longer used in RDA, PINES still has older records with the |h):

245 00 ‡aAssassins ‡h[videorecording] ; ‡bThe specialist / ‡cWarner Bros. Entertainment.

OPAC view:

Assassins The specialist (see https://gapines.org/eg/opac/record/5752001?locg=1;detail_record_view=0;page=0;query=title%3Atitle%3Aassassins%20specialist)

Result list for search also excludes separating punctuation:
https://gapines.org/eg/opac/results?locg=1;detail_record_view=0;page=0;query=title%3Atitle%3Aassassins%20specialist

Revision history for this message
Elaine Hardy (ehardy) wrote :

This is for version 3.4.1 and earlier

Revision history for this message
Jeff Davis (jdavis-sitka) wrote :

I noticed in bug 1864507 that MODS will strip some trailing punctuation. I think that's probably what is happening here, as you can see from the MODS representation of Elaine's example:

https://gapines.org/opac/extras/supercat/retrieve/mods32/record/4221829

Standard title display field configuration (config.metabib_field) is based on MODS, so if the MODS version doesn't include the semicolon, it won't be displayed. I don't think we want to modify the MODS transformation itself, so maybe display fields need to be based on MARCXML?

Revision history for this message
Elaine Hardy (ehardy) wrote :

Agree to not modifying MODS transformation. I did find this :

Punctuation

If using International Standard Bibliographic Description (ISBD) punctuation in creating MODS records, punctuation should be retained if it occurs within an element, but should be dropped between elements. If desired, an XSLT stylesheet may be used to generate an ISBD display from the MODS elements and data.

https://www.loc.gov/standards/mods/userguide/introduction.html#xml_structures

tags: added: opac
tags: added: cataloging
Changed in evergreen:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.