Comment 5 for bug 1308090

As of now, we would only want it to apply to the 100, 110, 111, 700,710,711
fields and perhaps 800, 810, 811

Elaine

J. Elaine Hardy
PINES & Collaborative Projects Manager
Georgia Public Library Service
1800 Century Place, Ste 150
Atlanta, Ga. 30345-4304

404.235-7128
404.235-7201, fax
<email address hidden>
www.georgialibraries.org
www.georgialibraries.org/pines

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Mike
Rylander
Sent: Wednesday, April 16, 2014 2:17 PM
To: <email address hidden>
Subject: [Bug 1308090] Re: sorting of name headings with relator codes

It looks like we could add subfield e to the list of ignored subfields in
the get_graphic_880s macro in misc_util.tt2 ... But that would have an
effect on 100, 110, 111, 245, 260, 264, 250 and 505, so it might need to be
tag-specific logic (or, better, an "additional ignore list" that macro
callers could supply).

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1308090

Title:
  sorting of name headings with relator codes

Status in Evergreen - Open ILS:
  New

Bug description:
  Name headings created under RDA rules often have a relator code in the
  |e that is not present in headings created under AACR2R rules. These
  headings (1xx and 7xx fields) sort separately from those without those
  codes. For example:

  100 1 |a Roth, Veronica.

  vs.

  100 1 |a Roth, Veronica, |e author.

  sorts as two different headings. While this is OK in browse search
  since both names are displayed, in advanced search, clicking on one
  heading in a search result list does not lead immediately to the other
  heading. (From the OPAC display of a record, it does).

  Since we will have databases with both kinds of headings for a very
  long time, ideally, having the indexing/sorting ignore the relator
  code should be considered provided it does not adversely affect other
  sorting/indexing issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evergreen/+bug/1308090/+subscriptions