Bib MARC field 505$t should be indexed in the Primo PNX file as a title entry
The MARC 505$r is indexed in the PNX as Creator and contributor. The MARC 505$t is not similarly indexed in the PNX as an added or alternate title.
Steve Michaels
shared this idea
Thank you for posting this idea. with the Primo VE June 2021 release Primo VE will index the 505 $t as well. This will be gradual rolled out pending the semi-annual indexing process planned to be completed by August.
-
Manu Schwendener commented
2023Q1: 505$t will be indexed in additional title instead of title (Primo VE).
-
Announced for 2021Q2
-
Lisa Hatt
commented
Absolutely. That's a major reason to put enhanced coding in the 505 in the first place. The inconsistent treatment of $r and $t is strange.
-
Paul Barton
commented
I add the Bib Marc field 505 alot into records that I am working with and it should be indexed as an added or alternateto title in Primo
-
Alex Pfundt
commented
Indexing for keyword search as well is greatly needed!
-
Jeff Karlsen commented
I would settle for 505$t being available in keyword search. Ex Libris is telling customers to copy the content to a local field via normalization rule and index it for search in Primo VE. This is nuts. Fix the bug.
-
Anonymous
commented
This functionality is critical. What is particularly problematic is that the 505 $t content isn't even searchable as a keyword. It makes no sense that purely by nature of it being $t it is invisible to Primo search under certain circumstances.
-
Anonymous
commented
This functionality is very much needed. Our collection already has hundreds of records from our previous system with enhanced contents notes, which are unsearchable in Primo. This issue also has workflow implications since we purchased vendor records and import records from Connexion. There are further implications when we contribute records to OCLC since we'll need to remove information from our records that will be of value to other libraries. Not having this functionality means more work for us and less quality information for our users.
-
Anonymous
commented
Please add this functionality to Primo VE. It will make it much more usuable!
-
Jeremy Barney
commented
Please add this functionality to Primo VE. The point of having an enhanced 505 field is to make it easier to search. 505 $t should be, by default, indexed in Primo VE.
-
Cindy Ehlers
commented
We would also like to see this functionality in place for Primo VE. It seems unhelpful that only $a and $r are indexed for search, although all subfields of the 505 field are indexed for display. At very least, the $t should be indexed for search as well.
-
We would also like to see this functionality in place for Primo VE. Indexing MARC field 505 $t to search content note titles should be considered a high priority. Thank you.
-
Nancy Babb
commented
We would also like to see this functionality in place for Primo VE. It seems unhelpful that only $a and $r are indexed for search, although all subfields of the 505 field are indexed for display. At very least, the $t should be indexed for search as well.
