https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21302 Heather <heather_hernandez@nps.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |heather_hernandez@nps.gov --- Comment #1 from Heather <heather_hernandez@nps.gov> --- I disagree--the linking entry fields, https://www.loc.gov/marc/bibliographic/bd760787.html are common in serial records where the $a and $t are often very common terms (e.g., made up example, $a Maritime History Society. $t Newsletter) and so this is why the $w contains _exact_ record numbers--the primary key for the record to be searched. In OCLC libraries, it is common to place the OCLC number in the 001 as the primary key, and the $w will carry the OCLC record number of the linking record as well as the $w of the Library of Congress record, etc. Also, if the linking record has a uniform title, it is mandatory that this be in the $s, and this can be very generic for legal materials. Large library systems (even WorldCat.org) use the $w record numbers as the search term for record linking in these fields, and this is going to be more common as RDA encourages more linking entry fields. If this is pursued, I would strongly encourage it to be configurable by the library, so the library has the choice of whether their Koha catalog will operate as other systems using the $w as the search term in the search executed by selecting a field in a 78X linking entry field, or via the $a & $t. Our Koha is configured to use the $w not only because it is the standard and offers the same functionality to our users as, e.g., WorldCat.org, but also because only a tiny minority of linking entry fields have distinguishing $a fields in them, and a search on the $t in these fields would retrieve so much as to be useless. (E.g., $t Newsletter, $t Proceedings, $t Annual report, etc.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.