LISTSERV mailing list manager LISTSERV 16.0

Help for BIBFRAME Archives


BIBFRAME Archives

BIBFRAME Archives


BIBFRAME@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  November 2012

BIBFRAME November 2012

Subject:

Re: BIBFRAME relationship indicators & coding

From:

"J. McRee Elrod" <[log in to unmask]>

Reply-To:

Bibliographic Framework Transition Initiative Forum <[log in to unmask]>

Date:

Thu, 29 Nov 2012 18:53:07 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (44 lines)

Kevin Ford said:


>We are looking at defining the relationships that we absolutely need,
>because they are already supported in our data (7XXs) or because they
>are new/different ...

Library and Archives Canada (LAC) has said that if they use
relationship indicators, in RDA/MARC21, they intend to use $4 codes as
opposed to $e terms, because of LAC's bilingual situation.

SLC would follow LAC for three reason: most of our derived records for
Canadian material come from LAC; we have a multilingual client base,
and we would like to avoid having several lists in different
languages; the RDA terms are split up among different lists, as
well as being in some cases too verbose and redundant (e.g., "composer
of music for a sound film" as opposed to just "composer" in a record
for a sound film).  

The MARC code list is shorter and simpler, is in one alphabetical
order, and has a better list of terms following the codes than the RDA
terms, available in more than one language, which we could use for
export to clients who prefer terms to codes.

Our questions are, will Bibframe have coding for codes as well as
terms, and will the present MARC codes carry over?

How we use MARC21 for RDA would be influenced by Bibframe
expectations.  We would want to crosswall all RDA/MARC21 records to
Bibframe, to avoid having three flavours.  We would want the
AAACR2/RDA and MARC21/Bibframe breaks to be the same, and not have a
midgroup of RDA/MARC21.

Speaking of crosswalks, it would be strange to crosswalk MARC21 245 $b
*and* $c to <title remainder>; we do hope you decide to code statement
of responsibility.  That granularity is needed, particlarly if we are
asked to crosswalk from Bibframe to MARC for a client.  With many
libraries' investment in MARC, we anticipate being asked to do that.


   __       __   J. McRee (Mac) Elrod ([log in to unmask])
  {__  |   /     Special Libraries Cataloguing   HTTP://www.slc.bc.ca/
  ___} |__ \__________________________________________________________

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
July 2011
June 2011

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager