LISTSERV mailing list manager LISTSERV 16.0

Help for BIBFRAME Archives


BIBFRAME Archives

BIBFRAME Archives


[email protected]


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  July 2014

BIBFRAME July 2014

Subject:

Re: bf:Title Was: [BIBFRAME] BibFrame and Linked Data: Identifiers

From:

Sally McCollum <[log in to unmask]>

Reply-To:

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

Date:

Fri, 25 Jul 2014 22:12:01 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (47 lines)

I apologize if this was confusing.  I simply meant all the catalogers out there who have helped to make the rules used to describe bibliographic material.  For many years the aacr2 rules were used and recently catalogers have started moving to the Resource Description and Access (RDA) rules.  MARC has been the carrier of the data that is formulated according to these cataloging rules.  Does this help?
Sally
Sent from my iPad

> On Jul 25, 2014, at 4:34 PM, "[log in to unmask]" <[log in to unmask]> wrote:
> 
> I'm a little confused-- who are "the rule makers" to whom you are referring?
> 
> ---
> A. Soroka
> The University of Virginia Library
> 
>> On Jul 25, 2014, at 4:06 PM, "McCallum, Sally" <[log in to unmask]> wrote:
>> 
>> Phil and A.,  I agree that the investigation would be very useful and interesting, but you have to have it with the folks who make the rules.  Too often we (or at least I) assume something is not important or useless or whatever until I consult the rule makers, who have given thought to many things (of course they are not perfect either:)).  
>> 
>> Sally
>> 
>> ***********************************
>> Sally H. McCallum
>> Chief, Network Development and MARC Standards Office
>> Library of Congress, 101 Independence Ave., SE
>> Washington, DC 20540  USA
>> [log in to unmask]
>> Tel: 1-202-707-5119 - Fax 1-202-707-0115
>> ***********************************
>> 
>> -----Original Message-----
>> From: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] On Behalf Of [log in to unmask]
>> Sent: Friday, July 25, 2014 3:00 PM
>> To: [log in to unmask]
>> Subject: Re: [BIBFRAME] bf:Title Was: [BIBFRAME] BibFrame and Linked Data: Identifiers
>> 
>> Phil--
>> 
>> Thanks for this-- it helps me clarify my thinking. Perhaps we can "back up" even a little bit further... Taking your example of title and title statement, we can ask ourselves what the purpose is of recording this kind of information, or to put it another way, what do we expect our patrons to _do_ with this kind of information? What are the differences in the ways that a patron might use a title and a title statement? I think those differences will tell us a good deal about how we should record that information.
>> 
>> ---
>> A. Soroka
>> The University of Virginia Library
>> 
>>> On Jul 25, 2014, at 2:11 PM, Philip Schreur <[log in to unmask]> wrote:
>>> 
>>> While acknowledging the enormous difficulty of this translation, I'd like to add a +1 to what Karen wrote (I was starting to write the same thing :)).  And I'm sure Karen meant this as well but just to be more explicit, we need to make sure that the intention and meaning we had originally is still valid, that there is no better way of expressing that intent currently, and that we use the the most appropriate way of expressing that intent in the new language.
>>> 
>>> As a means of communication, BibFrame will need to find a way of recording the intentions of various communities and sometimes those subtleties make less sense outside of that context.  For instance, the distinction between bf:title and bf:titleStatement.  To me, a bf:title can be almost anything, taken from any part of a resource or even made up by the person creating the data because there wasn't a title.  Some cataloging rules require that you use a transcribed title from a clearly defined place in the resource (that's what the bf:titleStatement is for).  To a cataloger, this is a valid distinction.  Without questioning the validity of making such a distinction (at least not yet :)),   what is the clearest most appropriate way of making this distinction?

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

June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
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