Print

Print


As the 3XX fields are not core, their lack should not be considered a deficiency.

 

And the DCM instructions for a 670 clearly say that the URL is optional:

 

Catalogers may optionally provide a uniform resource identifier (URI) in subfield $u of the 670 citation to link to the cited resource if it contains significant information related to the established entity that cannot be cited succinctly in the authority record. 

 

For a long time, we were discouraged from including URLs, and with Google searching, I think they are unnecessary.  In general, the rules for the 670 are grounded in a time when research involved going to print resources that were not readily accessible to all.

 

I wasn’t going to say anything about this topic, but now that I’ve started, I do have to comment once again that in looking forward to using identifiers rather than character strings, it would be nice to be a little less finicky about details such as punctuation, which do not affect access.

 

Amy

 

[log in to unmask]

 

 

 

 

 

From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Benjamin A Abrahamse
Sent: Tuesday, September 20, 2016 10:07 AM
To: [log in to unmask]
Subject: Re: [PCCLIST] Colon in title proper

 

I’m not in any position to make an official statement on behalf of anyone, but in our practice here at MIT (and we establish a lot of conference headings) we would just transcribe the colon as it appears, without the space. It is not, as you say, an ISBD punctuation mark, but rather a part of the conference heading itself. I would also note that for an English-language corporate body or conference, we would capitalize every word (except prepositions, conjunctions, and articles). Finally, since there is nothing in this name to indicate it is in fact a conferece, we would qualify it per RDA 11.13.1.2.

 

So we would have established it as:

 

Whaling in the Antarctic: the ICJ Judgment and its Implications (Conference) ǂd (2014 : ǂc Kōbe-shi, Japan)

 

There are a number of other deficiencies in this record, including the lack of any kind of 3xx informational fields, and the lack of $u URL in the second 670 pointing to the electronic resource cited, the use of an initial article in the first 411 (see the alternative instruction/LC-PCC PS to 11.2.2.8), the strange quote at the beginning of the second 411, and the lack of matching qualifiers on the 411s.

All in all, it’s a bit alarming to learn that this record was created by LC in 2016!

 

--Ben

 

 

From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Alexis Zirpoli
Sent: Tuesday, September 20, 2016 9:43 AM
To: [log in to unmask]
Subject: [PCCLIST] Colon in title proper

 

Greetings colleagues,

 

I am wondering if there has ever been anything solidly decided about handling a colon in a title proper or a name (specifically 130 for series title or 111 for conference title). I've searched the PCC archives, and saw a discussion thread on this topic (see PCC list archive thread for "Help with a series title", April 2015). However, I'm still not entirely clear on how to treat this. 

 

Here is an example:

 

111 2 Whaling in the Antarctic : the ICJ Judgment and its implications $d (2014 : $c Kobe-shi, Japan)

 

In this example, there is a space colon space, indicating that the information after the colon is considered to be "other title information". But we don't include other title information in the 111 for conferences, do we? So, if we assume that the information after the colon in this example is actually the title proper, wouldn't we change either the spacing (to colon space) or the punctuation (from space colon space to comma space)? 

 

ISBD says this:

C. Each unit of other title information is preceded by a space, colon, space ( : ), unless a word or phrase is given on the resource to link a second or subsequent unit with the preceding unit. 

 

Note this is for "other" title information. 

 

I haven't been able to find anything on explaining what to do when transcribing title proper information when there is a colon in it. I have been told that it's "ISBD" to change the colon to a comma, but I haven't found where, in the documentation, that is mentioned.

 

I have seen examples where people denoted it using colon space, or changed the colon to a comma space. 

 

Can I get some clearly spelled out official guidance on this please? I thank you for your patience with my newbiness.

 

- Alexis

 

--

Alexis Zirpoli

Cataloging Services Librarian

University of Michigan Law Library

734-647-1563