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  February 2016

BIBFRAME February 2016

Subject:

Re: Cataloging in multiple schemas (and content standards)

From:

"Folsom, Steven" <[log in to unmask]>

Reply-To:

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

Date:

Tue, 9 Feb 2016 12:06:31 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

To take the points James makes further—  [hopefully] we’ll start seeing
data produced outside of the library context brought into our workflows
more and more, with less and less overhead.

One area where the content standards and carrier/models intersect is with
regard to how Authorized Access Points are prescribed to be formed to
avoid “collision”. In an open world workflow, to attempt to get everyone
in the world to agree to refer to a person/place/thing/etc with the same
label is not advisable, nor in a linked data context do we have to. We
just need need enough data about the entity so that we can reconcile the
URIs and to allow users to disambiguate one entity from another in users
interfaces. This data doesn’t have to be captured in an authorized access
point, but rather through the various properties permitted for used with
that entity type. 

A lot of what I’ve said above is theoretical, of course, because library
systems by and large do not make use of URIs in these ways.


————
Steven Folsom
Metadata Technologies Program Manager
Harvard Library
http://orcid.org/0000-0003-3427-5769







On 2/9/16, 4:30 AM, "Bibliographic Framework Transition Initiative Forum
on behalf of James Weinheimer" <[log in to unmask] on behalf of
[log in to unmask]> wrote:

>On 2/8/2016 8:03 PM, Karen Coyle wrote:
>> This brings to mind something that I have often heard Diane Hillmann
>> say: that catalogers do not talk in terms of AACR (or now, RDA) rules,
>> but instead they speak "MARC". This of course is a confusion of the
>> content and the carrier, something we should be more carefully aware
>> of. To consider yourself cataloging in BIBFRAME would be making the
>> same mistake. The cataloging rules are RDA or ISBD or DACS (etc.), and
>> that determines the content of the catalog entry. The carrier is MARC
>> or BIBFRAME or ISBD or any number of other possible data carriers. It
>> should be possible to transport our data in a variety of carriers, and
>> to define a variety of profiles for different uses.  We do need to be
>> able to catalog in all of the detail of our rules, even if many
>> applications use only a portion of that detail.
>
>I don't think I agree with this. When catalogers speak, they speak
>primarily in terms of rules and procedures, not so much in terms of
>MARC. A quick review of Autocat or RDA shows this. When catalogers do
>use MARC, it is more of a shorthand for the rules, e.g. they might use
>245$b in place of typing out "other title information".
>
>What catalogers do not talk about is rules other than their own.
>Occasionally, catalogers might bring up other, related cataloging rules
>that are still library-based, e.g. rare books, but they almost never
>discuss how non-library related sets of rules, e.g. Onix, handles a
>bibliographic concept. When the universe is widened even further, for
>instance in the case of author-created metadata, no discussions at all
>take place. In my opinion, this is highly unfortunate since library
>records will be encountered more and more often *outside* of the
>traditional library systems--after all, that is one of the main purposes
>of linked data--and catalogers should concern themselves with making
>their records coherent in those settings.
>
>A single example of what I mean is: how do we make a subject heading
>such as this:
>
>Dostoyevsky, Fyodor, 1821-1881--Homes and haunts--Russia
>(Federation)--Novokuznet︠s︡k.
>
>which is both useful and coherent when it is within the library catalog,
>but when taken out (as here) becomes something very strange. Absolutely
>nobody (except for a library cataloger) would ever think to look up
>anything like this. How do we make this type of bibliographic oddity
>less bizarre in the linked data universe?
>
>James Weinheimer [log in to unmask]
>First Thus http://blog.jweinheimer.net
>First Thus Facebook Page https://www.facebook.com/FirstThus
>Personal Facebook Page https://www.facebook.com/james.weinheimer.35
>Google+ https://plus.google.com/u/0/+JamesWeinheimer
>Cooperative Cataloging Rules
>http://sites.google.com/site/opencatalogingrules/
>Cataloging Matters Podcasts
>http://blog.jweinheimer.net/cataloging-matters-podcasts
>The Library Herald http://libnews.jweinheimer.net/
>
>[delay +30 days]

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

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