Thanks. Iím familiar with this because I drafted the proposal ;-) These are now (or will be) core elements, but this only means that they will be recorded at the element level (MARC 21 368). We may still be limited, as you note, to adding it to the access point in cases of conflict. I donít know for certain what happened to my optional addition at 18.104.22.168, but weíll have to wait for the final text of the revisions in January, to see what will actually be in the revised text.
Itís unfortunate that, having finally got these elements into RDA last year, we might hardly ever use them in an authorized acess point. We didnít intend them to be used just to break conflicts; they were designed primarily to identify, contextualise, and enable the conversion of data from the LCSH authority file.
From: Program for Cooperative Cataloging [mailto:[log in to unmask]]
On Behalf Of Mark K. Ehlert
Sent: 27 November 2013 14:38
To: [log in to unmask]
Subject: Re: [PCCLIST] Greek deities and mythological figures - subfield c?
Moore, Richard <[log in to unmask]> wrote:
Unfortunately, itís my understanding that the proposal was completely reversed at JSC, so that no ďother designationĒ would be included in an access point except in case of conflict.
Last weekend I walked through the various proposals discussed by the JSC, reading over what they reviewed and the outcomes given by John Attig on his blog. Attig wrote: "6JSC/BL/13: Revision of RDA 9.6. This proposal seeks to adjust the core requirements for the element Other designation associated with the person, as well as the instructions for including this element in authorized access points representing persons. The proposal was approved[!], with minor wording revisions. In addition, the JSC approved LC suggestions for revisions to (a) the lists of core elements at 0.6.4 and 8.3; and to (b) the instructions for constructing authorized access points at 22.214.171.124."
The LC response (here: <http://www.rda-jsc.org/docs/6JSC-BL-13-LC-response.pdf>) includes, among others, a revised 126.96.36.199 on adding to access points fictitious character monikers to names not conveying the idea of a person. The same response had a revised 188.8.131.52.6 to give such monikers in cases of conflict, with the option to give it even when there is not conflict (much like dates or fuller forms of name); whether this particular bit won out, I don't know. The changes in LC's 0.6.4 and 8.3 core element lists tells us that these elements are core for fictitious persons, and also used for conflict breaking, mirroring the access point guidelines above. (The LC wording of these core instructions leaves out the "conveying the idea of a person" clause, however).
BL's original proposal and the responses are here: <http://www.rda-jsc.org/working2.html#bl-13>
Nothing's official until the JSC makes their pronouncements, of course, but I wanted to point this out.
Mark K. Ehlert Minitex
Coordinator University of Minnesota
Digitization, Cataloging & 15 Andersen Library
Metadata Education (DCME) 222 21st Avenue South
Phone: 612-624-0805 Minneapolis, MN 55455-0439