From tachtorn.meier at yale.edu  Tue May  7 12:19:45 2024
From: tachtorn.meier at yale.edu (Meier, Tachtorn)
Date: Tue, 7 May 2024 16:19:45 +0000
Subject: [yul-naco] FW: Punctuation in name-titles
In-Reply-To: <CO1PR08MB7674661CC27510C9D12F272DD2E42@CO1PR08MB7674.namprd08.prod.outlook.com>
References: <DM4PR03MB7014CEEE7132EE9338C07A0E8AE42@DM4PR03MB7014.namprd03.prod.outlook.com>
 <CO1PR08MB767498D9E0D14867FB72EB2DD2E42@CO1PR08MB7674.namprd08.prod.outlook.com>
 <CO1PR08MB7674661CC27510C9D12F272DD2E42@CO1PR08MB7674.namprd08.prod.outlook.com>
Message-ID: <BL3PR08MB7452E051E1083FC2781BA4F1F0E42@BL3PR08MB7452.namprd08.prod.outlook.com>

Dear Colleagues,

I'm forwarding this discussion from the PCC list because it contains information related to NACO that you might find useful.

Best,
Wheat

From: Program for Cooperative Cataloging <PCCLIST at LISTSERV.LOC.GOV> On Behalf Of Adam L Schiff
Sent: Tuesday, May 7, 2024 11:57 AM
To: PCCLIST at LISTSERV.LOC.GOV
Subject: Re: [PCCLIST] Punctuation in name-titles

The same info is in the authority format.

https://www.loc.gov/marc/authority/adx00.html


Name portion of a name/title field ends with a mark of punctuation. The mark of punctuation is placed inside a closing quotation mark.
100
1#$aRavel, Maurice,$d1875-1937.$tSelections;$oarr.
100
0#$aThomas$c(Anglo-Norman poet).$tRoman de Tristan.$lEnglish
100
0#$aChristo,$d1935-$tSurrounded islands
100
0#$aDemetrius,$cof Phaleron,$db. 350 B.C.$tDe elocutione.$lRussian
Adam
Adam L. Schiff
Principal Cataloger
University of Washington Libraries
(206) 543-8409
aschiff at uw.edu<mailto:aschiff at uw.edu>

________________________________
From: Program for Cooperative Cataloging <PCCLIST at LISTSERV.LOC.GOV<mailto:PCCLIST at LISTSERV.LOC.GOV>> on behalf of Adam L Schiff <aschiff at UW.EDU<mailto:aschiff at UW.EDU>>
Sent: Tuesday, May 7, 2024 8:51 AM
To: PCCLIST at LISTSERV.LOC.GOV<mailto:PCCLIST at LISTSERV.LOC.GOV> <PCCLIST at LISTSERV.LOC.GOV<mailto:PCCLIST at LISTSERV.LOC.GOV>>
Subject: Re: Punctuation in name-titles

This is in the MARC format itself.  https://www.loc.gov/marc/bibliographic/bdx00.html<https://urldefense.com/v3/__https://www.loc.gov/marc/bibliographic/bdx00.html__;!!K-Hz7m0Vt54!h_17ICrpJrrLTCjxJxf4AmAURmYRs9oVz5L1ssQVO9sC2i7lKQQccV8kM4KbB9-Xal4xDyfNSMGIJmA$>:


Punctuation - Punctuation of the subelements of a heading is generally dictated by descriptive cataloging or subject heading system/thesaurus rules. These input conventions clarify MARC punctuation practices. Fields 100, 600, 700, and 800 end with a mark of punctuation or a closing parenthesis. If the final subfields are subfield $0, $2, $3, $4, or $5, the mark of punctuation or closing parenthesis precedes those subfields.


600
10$aCapote, Truman,$d1924-$xCriticism and interpretation.
700
1#$aEllington, Duke,$d1899-1974.$tSelections;$oarr.$f1986.
700
0#$aThomas$c(Anglo-Norman poet).$tRoman de Tristan.$lEnglish.
100
1#$aGrozelier, Leopold.$4art
Name portion of a name/title heading ends with a mark of punctuation. The mark of punctuation is placed inside a closing quotation mark. A name or title portion followed by a subject subdivision does not end with a mark of punctuation unless the name or title portion ends with an abbreviation, initial/letter, or open date.
And mark of punctuation is defined at https://www.loc.gov/marc/bibliographic/bdintro.html<https://urldefense.com/v3/__https://www.loc.gov/marc/bibliographic/bdintro.html__;!!K-Hz7m0Vt54!h_17ICrpJrrLTCjxJxf4AmAURmYRs9oVz5L1ssQVO9sC2i7lKQQccV8kM4KbB9-Xal4xDyfNj8aOCMA$>:

The input conventions area provides general guidance for the application of the content designators, and for such things as punctuation, spacing, and the use of display constants. The punctuation used within a field is generally dictated by descriptive cataloging or subject heading system/thesaurus rules. The input conventions clarify MARC punctuation practices especially with respect to final punctuation. In the discussion of punctuation practices, mark of punctuation is a period (.), a question mark (?), an exclamation mark (!), or a hyphen (-).

So if the name portion ends in a hyphen, no period is added because there is already a mark of punctuation.

Adam Schiff

Adam L. Schiff
Principal Cataloger
University of Washington Libraries
(206) 543-8409
aschiff at uw.edu<mailto:aschiff at uw.edu>
________________________________
From: Program for Cooperative Cataloging <PCCLIST at LISTSERV.LOC.GOV<mailto:PCCLIST at LISTSERV.LOC.GOV>> on behalf of Cronquist, Michelle J <cronquim at EMAIL.UNC.EDU<mailto:cronquim at EMAIL.UNC.EDU>>
Sent: Tuesday, May 7, 2024 8:15 AM
To: PCCLIST at LISTSERV.LOC.GOV<mailto:PCCLIST at LISTSERV.LOC.GOV> <PCCLIST at LISTSERV.LOC.GOV<mailto:PCCLIST at LISTSERV.LOC.GOV>>
Subject: Punctuation in name-titles


Hi all,



I?m trying to find the rule that I have known for decades but can?t find written anywhere, that when you have a name-title access point you put a period after the name portion unless it ends in a hyphen.



e.g.,



Beethoven, Ludwig van, ?d 1770-1827. ?t Symphonies, ?n no. 1, op. 21, ?r C major



but



Adams, John, ?d 1947- ?t Short ride in a fast machine



Is this documented somewhere in the LC-PCC PSs?



Thanks,



Michelle



---
Michelle Cronquist (she/her/hers)
Special Collections Cataloger
Special Collections Technical Services
CB#3926, Wilson Library
University of North Carolina at Chapel Hill

 919-962-4271


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.yale.edu/pipermail/yul-naco/attachments/20240507/3d30a94f/attachment-0001.html>

From tachtorn.meier at yale.edu  Wed May  8 15:53:51 2024
From: tachtorn.meier at yale.edu (Meier, Tachtorn)
Date: Wed, 8 May 2024 19:53:51 +0000
Subject: [yul-naco] =?utf-8?q?FW=3A_Polish_places_beginning_with_Wojewo?=
 =?utf-8?q?=CC=81dztwo?=
In-Reply-To: <CO1PR08MB7674533991751FC6D2B4B6FDD2E52@CO1PR08MB7674.namprd08.prod.outlook.com>
References: <CO1PR08MB767470E2D76C57FB2E7441B4D26E2@CO1PR08MB7674.namprd08.prod.outlook.com>
 <SA1PR09MB1180298099E6CBC7F9A01DCC4D4742@SA1PR09MB11802.namprd09.prod.outlook.com>
 <CO1PR08MB7674DE00432C5E7B4AF66B14D22C2@CO1PR08MB7674.namprd08.prod.outlook.com>
 <CO1PR08MB7674405BF7AD6C4E8499D58AD2E52@CO1PR08MB7674.namprd08.prod.outlook.com>
 <CACtkQBu2isxAgSPe6jegmjPz1XCEwck0tV+HU0nWOQ84WkkaKA@mail.gmail.com>
 <CO1PR08MB7674533991751FC6D2B4B6FDD2E52@CO1PR08MB7674.namprd08.prod.outlook.com>
Message-ID: <BL3PR08MB74523AD8EB3F8E8E088C4C98F0E52@BL3PR08MB7452.namprd08.prod.outlook.com>

Dear Colleagues,

Just an FYI, there?s a NACO-related topic on PCC listserv.

Best,
Wheat
From: Program for Cooperative Cataloging <PCCLIST at LISTSERV.LOC.GOV> On Behalf Of Adam L Schiff
Sent: Wednesday, May 8, 2024 12:27 PM
To: PCCLIST at LISTSERV.LOC.GOV
Subject: Re: [PCCLIST] Polish places beginning with Wojewo?dztwo

Sounds like there's an even bigger cleanup needed than even I imagined.  In the case of Wojew?dztwo Mazowieckie, the BGN approved name is just Mazowieckie, and we are supposed to follow BGN.  I haven't looked at any of the other places in Geographic Names Server, but it's probably similar there for them.

Adam

Adam L. Schiff
Principal Cataloger
University of Washington Libraries
(206) 543-8409
aschiff at uw.edu<mailto:aschiff at uw.edu>

________________________________
From: Robert J. Rendall <rr2205 at columbia.edu<mailto:rr2205 at columbia.edu>>
Sent: Wednesday, May 8, 2024 8:25 AM
To: Adam L Schiff <aschiff at uw.edu<mailto:aschiff at uw.edu>>
Cc: slavcat at lists.illinois.edu<mailto:slavcat at lists.illinois.edu> <slavcat at lists.illinois.edu<mailto:slavcat at lists.illinois.edu>>; Program for Cooperative Cataloging <PCCLIST at listserv.loc.gov<mailto:PCCLIST at listserv.loc.gov>>
Subject: Re: Polish places beginning with Wojewo?dztwo

Wojew?dztwo Mazowieckie and the rest of these are like R?publique fran?aise - the second word is an adjective.

The way these wojew?dztwa/voivodeships have been established in the NAF is very inconsistent; sometimes the whole phrase, sometimes the related noun for either a city or a historic region (in this case that would be Mazowsze, in English Mazovia), sometimes with the adjective alone (which looks wrong to me).


Robert Rendall

Head of Cataloging

Cataloging & Metadata Services, Columbia University Libraries

102 Butler Library, 535 West 114th Street, New York, NY 10027

tel.: 212 851 2449

e-mail: rr2205 at columbia.edu<mailto:rr2205 at columbia.edu>


On Wed, May 8, 2024 at 11:03?AM Adam L Schiff <slavcat at lists.illinois.edu<mailto:slavcat at lists.illinois.edu>> wrote:
As a NACO reviewer, I was asked earlier this year to review this new NAR:



151  Borkowice (Wojewo?dztwo Mazowieckie, Poland)



LC established the access point Wojewo?dztwo Mazowieckie (Poland) [n 2001105288] and it was coded as RDA, but I don't think it was correct.  I believe that this heading should have been established as Mazowieckie (Poland).  Wojewo?dztwo is a word for a type of jurisdiction, in English: Voivodeship.



Here's the entry in GNS:



[cid:ii_18f58c78789bd7334ba1]

[cid:ii_18f58c787899fe1bd132]





Here's what it says in RDA 16.2.2.8<https://urldefense.com/v3/__http://16.2.2.8__;!!K-Hz7m0Vt54!klaGF2J35ddPHyrqLsL0nk0EvzR3oMINP2_eM1LWFByGyCAFc9H80yJahc-ddSd1aNHU9StPqxFu_AJ4qw$>:



[cid:ii_18f58c787897c3cbfe63]



And in RDA 11.13.1.6<https://urldefense.com/v3/__http://11.13.1.6__;!!K-Hz7m0Vt54!klaGF2J35ddPHyrqLsL0nk0EvzR3oMINP2_eM1LWFByGyCAFc9H80yJahc-ddSd1aNHU9StPqxEgsKn7kQ$>:



[cid:ii_18f58c7878939ab9b924]



The GNS approved name is Mazowieckie.  There are no other places in Poland in GNS with the same name, so without a conflict, I believe that the AAP for this place should be just Mazowieckie (Poland)



That means that n 2001105288 should be revised to the correct access point Mazowieckie (Poland) but it also means that there are numerous other authority records that also must be revised, e.g. Dylewo (Wojewo?dztwo Mazowieckie, Poland); Jadwisin (Legionowo, Wojewo?dztwo Mazowieckie, Poland); Jeziory (Wojewo?dztwo Mazowieckie, Poland); Legionowo (Wojewo?dztwo Mazowieckie, Poland); Lipsko (Wojewo?dztwo Mazowieckie, Poland : Powiat); We?gro?w (Wojewo?dztwo Mazowieckie, Poland); and so on.  OCLC retrieves 71 geographic authority records that have Wojewo?dztwo Mazowieckie in them.



When I reported the above issue to PTCP, someone at LC did change the authority record to Mazowieckie (Poland) in February. But they did not change all of the additional place authorities that have (Wojewo?dztwo Mazowieckie, Poland) as a qualifier.  I'm wondering who should be responsible for fixing all of these others?



When I search for geographic keyword Wojewo?dztwo in the OCLC authority file, it's apparent that this is an even bigger problem, because I'm also finding headings for:



Wojewo?dztwo Lubuskie (Poland)

Wojewo?dztwo Opolskie (Poland)

Wojewo?dztwo Podkarpackie (Poland)

Wojewo?dztwo Podlaskie (Poland)

Wojewo?dztwo Pomorskie (Poland)

Wojewo?dztwo S?la?skie (Poland)

Wojewo?dztwo S?wie?tokrzyskie (Poland)

Wojewo?dztwo Zachodniopomorskie (Poland)



And, of course, all of the other places in the authority file that use one of these places as a qualifier.  It's a lot (650 matches on geographic keyword search for Wojewo?dztwo, plus any corporate bodies and titles that use any of these places as a qualifier, plus any 3XX fields that have had one of these places recorded as an attribute).



Perhaps the Slavic cataloging community and/or PCC community needs a project to clean these all up?



Adam Schiff



Adam L. Schiff

Principal Cataloger
University of Washington Libraries

(206) 543-8409

aschiff at uw.edu<mailto:aschiff at uw.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.yale.edu/pipermail/yul-naco/attachments/20240508/1058aa9f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-z2bhr3r2.png
Type: image/png
Size: 24499 bytes
Desc: Outlook-z2bhr3r2.png
URL: <http://mailman.yale.edu/pipermail/yul-naco/attachments/20240508/1058aa9f/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-rx1xgjpx.png
Type: image/png
Size: 43263 bytes
Desc: Outlook-rx1xgjpx.png
URL: <http://mailman.yale.edu/pipermail/yul-naco/attachments/20240508/1058aa9f/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-ng1dozau.png
Type: image/png
Size: 66978 bytes
Desc: Outlook-ng1dozau.png
URL: <http://mailman.yale.edu/pipermail/yul-naco/attachments/20240508/1058aa9f/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Outlook-3yi51pk1.png
Type: image/png
Size: 71714 bytes
Desc: Outlook-3yi51pk1.png
URL: <http://mailman.yale.edu/pipermail/yul-naco/attachments/20240508/1058aa9f/attachment-0007.png>

From tachtorn.meier at yale.edu  Thu May 30 13:54:20 2024
From: tachtorn.meier at yale.edu (Meier, Tachtorn)
Date: Thu, 30 May 2024 17:54:20 +0000
Subject: [yul-naco] Fw: [PCCLIST] Updates to PCC Guidelines for Relationship
 Designators in NARs
In-Reply-To: <CACC3-zEDuWY6XbppyocF_g6dwFzyQ5qvyBDSiUiGAU07FB-Ygg@mail.gmail.com>
References: <CACC3-zEDuWY6XbppyocF_g6dwFzyQ5qvyBDSiUiGAU07FB-Ygg@mail.gmail.com>
Message-ID: <BL3PR08MB7452534C0FFF5827AFCBA9FCF0F32@BL3PR08MB7452.namprd08.prod.outlook.com>


Dear Colleagues,

Please see the forwarded message regarding the PCC Guidelines for Relationship Designators in NARs.

Best,
Wheat


________________________________
From: Program for Cooperative Cataloging <PCCLIST at LISTSERV.LOC.GOV> on behalf of Matthew C. Haugen <matthew.haugen at COLUMBIA.EDU>
Sent: Thursday, May 30, 2024 11:54 AM
To: PCCLIST at LISTSERV.LOC.GOV <PCCLIST at LISTSERV.LOC.GOV>
Subject: [PCCLIST] Updates to PCC Guidelines for Relationship Designators in NARs

Dear Colleagues,

An updated version of the PCC Guidelines for the Application of Relationship Designators in NACO Authority Records<https://www.loc.gov/aba/pcc/rda/guidelines/authority-relationships.pdf> (May 2024) has been posted. The relevant changes are found in sections 13 and 15.

Catalogers may now use relationship designators for related places in field 551 in NACO Authority Records, using subfield $i in combination with subfield $w value ?r.? Catalogers may also update existing place name records that contain subfield $w values ?a? or ?b,? in field 551, to convert those code values to appropriate relationship designators from RDA Appendix K.4.3 for successive place names, merges, splits, etc. For example:

151 Oslo (Norway)
551 $w r $i Predecessor: $a Kristiania (Norway)

151 Kristiania (Norway)
551 $w r $i Successor: $a Oslo (Norway)

Optionally, relationships other than sequential place-to-place relationships, including hierarchical place-to-place relationships and relationships of other entities to places may also be recorded in 551 $i, using appropriate relationship designators from RDA Appendix K (for agent-to-place relationships) or Appendix I (for work/expression-to-place relationships). Appropriate terms from these appendices may be used since Appendix L was never developed. The updated guidelines provide some additional guidance and examples.

As a general reminder: catalogers may record a related entity in a MARC 5XX field only when the other entity has been established in the LCNAF. Catalogers may not record relationships in the 5XX field to entities in other vocabularies such as LCSH or Getty Thesaurus of Geographic Names (TGN). If the cataloger desires to formally record a related entity in a 5XX field for an entity appropriate to the LCNAF that has not yet been established, the cataloger must establish it (see best practice number 2, page 4). Catalogers may alternatively consider recording associated place names from other vocabularies using the 370 field in NARs.

The new practice may begin immediately (and some catalogers have already been doing so, as in the Oslo/Kristiania example above). The existing prohibition on the use of subfield $i found in the DCM Z1 section 551 may be disregarded, and will be removed in the next DCM update in August 2024. Additionally, links to the updated guidelines will be either revised or added elsewhere in the DCM Z1, NACO Participants' Manual, etc. at that time. The guidelines are now published in PDF format instead of Word (.docx) format, and the old Word link now contains a redirect to the new PDF version.

The updates were prepared by the PCC Standing Committee on Standards (SCS), and approved by the PCC Policy Committee (PoCo) in May 2024. Please direct any questions or comments to SCS.

Thank you,

Matthew Haugen and Honor Moody
SCS Co-Chairs

--
Matthew C. Haugen
Rare Book Cataloger | Columbia University Libraries
matthew.haugen at columbia.edu<mailto:matthew.haugen at columbia.edu> | 212-851-2451 | he/they<https://urldefense.com/v3/__https://universitylife.columbia.edu/pronouns__;!!EDx7F7x-0XSOB8YS_BQ!bbuAsRTsLf_VuFvsZHZMbP1OVDSGG4LfMoKvFwsFPk_olSRve5Tsi0JrSYO7F37k03N_vSE5_u-8_gGq6bPMneb_YlyMmY7ncJOd$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.yale.edu/pipermail/yul-naco/attachments/20240530/d8f23196/attachment.html>