Series Search Not Including 490 if Traced Series
Bug #1750009 reported by
Robert J Jackson
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Undecided
|
Unassigned |
Bug Description
web client 3.0.3
WHen performing a series search and data being searched is contained within the 490 $a - there isn't a match if the 490 has a 1 (traced series) such as
=490 1\$a[Chief Inspector Gamache novel ;$v13]
If the subfield is a 0 as opposed to a 1 then the series search returns the desired bib.
Traced series should be included in results from a series search that contains Inspector Gamache even if it is in a traced series entry.
example record:
description: | updated |
tags: | added: webstaffclient |
tags: | removed: webstaffclient |
tags: |
added: cat-marc search removed: cataloging marc |
To post a comment you must log in.
Per https:/ /www.loc. gov/marc/ bibliographic/ bd490.html and http:// www.loc. gov/standards/ mods/v3/ mods-mapping. html#relatedite m the indexing seems to be doing what the rules say, and indexing the 8xx instead of the 490 when the latter is traced.
I believe the real bug here is that we're generating a series search link for data we're not indexing (a traced 490). As it happens, I'm working on bug 1744385 which incidentally addresses this by only generating links for things that we actually pull out of records and store for search. It does this by leveraging the display field infrastructure (which is bound to index definitions) instead of hard-coding XPath in the OPAC templates that doesn't necessarily map to what we index.