Thanks, Mac. The problem with 'writer of added text' is that it is
defined as 'contributing to an expression of a primarily non-textual
work by providing text for the non-textual work' - but this compilation
is all textual and all the input is of equal standing. (We aren't
considering using the
Many thanks to Elizabeth O'Keefe of The Morgan Library Museum. She sent us
the necessary coding that enabled my systems librarian to tweak our Ex Libris
Voyager display created exactly what we want in terms of a display. This
coding will surely come in handy as we continue to work with RDA
Responding to Paul Davey's comment and question concerning the use of
field 264 in OCLC:
Field 264 was implemented in OCLC as part of the OCLC-MARC Update 2012
in May 2012. It is documented in OCLC Technical Bulletin 261
(http://www.oclc.org/support/documentation/worldcat/tb/261/default.htm)
According to PCC guideline, all new RDA records use 264 field. The field is
in Library of Congress bib format.
www.loc.gov/aba/*pcc*/documents/*264*-*Guidelines*.doc
http://www.loc.gov/marc/bibliographic/bd264.html
By the way, Library of Congress training materials are comprehensive. They
help a
I had always assumed that the 33x fields for streaming video should look like
this due to the online nature of the resource:
336 __ $a two-dimensional moving image $2 rdacontent
337 __ $a computer $2 rdamedia
338 __ $a online resource $2 rdacarrier
However, I was recently reviewing something
'contributor' would make sense. We definitely need a way to distinguish
authors of introductions and prefaces from authors of the main text.
On 2/25/2013 3:20 AM, Bernadette Mary O'Reilly wrote:
Thanks, Mac. The problem with 'writer of added text' is that it is
defined as 'contributing to an
I think RDA relationships should be structured like a controlled vocabulary,
with links to and from broader and narrower terms. Contributor and creator
would be the top-level terms. If a narrower term has not been established
(author of preface, for example) the cataloger would use the higher
Paul Davey asked:
ps 264 - I understand that OCLC allows it, but it's not in their bib =
format. Would it be right that I use 260 by default?
PCC says to use 264 rather than 260 in any new RDA record. I hope OCLC
will change the RDA test record which have 260.
__ __ J. McRee (Mac)
Kelly McGrath posted for streaming videos:
336 __ $a two-dimensional moving image $2 rdacontent
337 __ $a computer $2 rdamedia
338 __ $a online resource $2 rdacarrier
I agree with your choice of 336 and 338. I think most patrons would
think of video as a disk played on a device.
The one
FYI
On 2/11/2013 12:15 PM, Casey A Mullin wrote:
[Cross-posted widely. Please excuse the duplication]
Colleagues,
The MLA-BCC RDA Music Implementation Task Force is happy to announce
the release of the first complete draft of Best Practices for Music
Cataloging using RDA and MARC21. This
Dear collective wisdom,
My apologies, because I believe this has been asked and answered before, but I
cannot find the relevant emails.
At this point is it considered necessary in fields 336-338 to use both subfield
$a with the term spelled out and also subfield $b with the code, or is
Michael Borries asked:
At this point is it considered necessary in fields 336-338 to use both subf=
ield $a with the term spelled out and also subfield $b with the code ...
SLC considers having both to be redundant. We will use $aterms in
336-338, but $4codes for relators.
That's a tad
I was cataloging one of these the other day and faced the same conundrum. I
turned to the OLAC best practices document
(http://www.olacinc.org/drupal/?q=node/47) which is several years old and needs
to be updated for RDA and the new fields, but is still useful.
Following the definitions of
If you are using OCLC Connexion, there is a macro to supply these fields
and it supplies both the term and code in $a and $b. So that is one
reason you are seeing both in many records. LC's policy for its
catalogers (see DCM B.13.13.2) is to record the term in $a, but if $b is
present in
OLAC is in the process of updating its streaming media best practices to be
RDA-compatible so it's coming soon.
I do think there is something fundamentally wrong with the computer media type
and have thought so since the days when we were commenting on the RDA drafts.
There is nothing
Documents posted recently on the public JSC web site are the following:
(1) revisions of five Sec final documents to correct minor errors in
examples:
-- 6JSC/ALA/6/Sec final/rev
-- 6JSC/ALA/11/Sec final/rev
-- 6JSC/ALA/15/Sec final/rev
-- 6JSC/LC/10/Sec final/rev
-- 6JSC/LC/21/Sec final/rev
Kelly,
I agree that this is a tough issue to untangle. Especially if we are trying to
infer what users are thinking with respect to find, identify, select, obtain.
We decided on using your second option in our digital asset description:
336 __ $a two-dimensional moving image $2 rdacontent
Bernadette,
My understanding is that the relator term author is meant to be related to a
creator of a work. In the model you are describing the contributing authors
aren't the creator of the described work which is the dictionary of biography.
I think general practice is not to delve into the
Sean Chen said:
I believe the computer media type is now irrelevant and I think that =
referring to things as needing a computer is not going to be in =
alignment with how users are doing FISO.
I of course agree.
I have no argument that electronic is better as a media type than
digital.
19 matches
Mail list logo