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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  May 2013

BIBFRAME May 2013

Subject:

Re: Role a nature of Bibframe authorities

From:

Karen Coyle <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Tue, 28 May 2013 07:37:24 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (153 lines)

+1

On Tue May 28 07:28:27 2013, Diane Hillmann wrote:
> Two quick points:
>
> In MARC, there's the 720 field that's pretty generic, intended to be
> used when not much was known about the agent or it's relationship--a
> parking lot, if you will.
>
> For linked data, the ideal would be having a hierarchy of roles, like
> RDA has, from the more specific to the more generalized, so that a
> very specific role need not be used if the information wasn't
> available. I think we have the tools and the thinking to do a
> reasonable job of moving the legacy data forward, without necessarily
> labeling anything 'bad'.
>
> Diane
>
>
> On Tue, May 28, 2013 at 9:38 AM, Trail, Nate <[log in to unmask]
> <mailto:[log in to unmask]>> wrote:
>
> Hmm. I kind of like the suggestion of a parking lot field, that
> systems could display as notes. LC has a lot of these "from old
> catalog" entries, that just are begging to be cleaned up, and
> putting them there tells people we know they need cleanup. I'm
> sure there will be other things we can't figure out what to do with.
> Nate
> -------------------------------------------
> Nate Trail
> -------------------------------------------
> LS/TECH/NDMSO
> Library of Congress
> 202-707-2193 <tel:202-707-2193>
> [log in to unmask] <mailto:[log in to unmask]>
>
>
>
> -----Original Message-----
> From: Bibliographic Framework Transition Initiative Forum
> [mailto:[log in to unmask]
> <mailto:[log in to unmask]>] On Behalf Of Karen Coyle
> Sent: Saturday, May 25, 2013 10:34 AM
> To: [log in to unmask] <mailto:[log in to unmask]>
> Subject: Re: [BIBFRAME] Role a nature of Bibframe authorities
>
> On 5/25/13 6:47 AM, Kevin Ford wrote:
> > > It is hard to fathom that role is being considered as part of an
> > > authority.
> > -- It's not with the exception of one scenario, which I expect
> will be
> > very, very few cases overall: when it is impossible to determine the
> > role because of poor cataloger entry in existing MARC records.
>
> Given that there are tens of thousands of libraries using MARC in
> their local systems, only some of which are visible outside their
> own systems, I think it will be unwise to make decisions based on
> estimates of "very, very few cases". In fact, world-wide, we don't
> know how many such cases exist. Also, there are people using MARC
> whose language of cataloging is not English, and therefore they
> use different sets of codes or terms for roles (and for much else
> in the record).
>
> Once again, I wish our focus were NOT on transitioning MARC at
> this stage of the metadata development. I fear that we risk our
> future by looking backward, not forward. Honestly, just throw the
> "bad" MARC string into a "bad data" field and leave it in the
> bibliographic description. It is NOT author/agent information, it
> is bibliographic information, and should stay there.
>
> kc
>
>
> > This is the Bad Data example in the discussion paper. I also
> > anticipate this will only ever be an issue during a transition
> phase,
> > meaning that, moving forward, specific "codes" or links will be used
> > to describe the relation of an authority entity to a work. I
> also see
> > the scenario as a limited accommodation to be made during said
> > transition phase.
> >
> > If $e says "editor" or "author of," we can associate those lexical
> > entries with relator codes. If, however, $e says "edtor" or "autor
> > of," we cannot necessarily reliably associate those poorly entered
> > lexical entries with relator codes. This is why it is a limited
> > accommodation during a transition period. In the future,
> designating
> > a "role" would be done in a controlled manner.
> >
> > I'm not delighted about finding data entry errors in our current
> > bibliographic data, but I can see that they are a very small
> > percentage all told. Is a more elaborate solution required for
> such a
> > small amount of existing data, especially knowing we can improve on
> > this moving forward so that we do not have this problem?
> >
> > Cordially,
> > Kevin
> >
> >
> >
> >
> >
> > On 05/24/2013 07:25 PM, J. McRee Elrod wrote:
> >> It is hard to fathom that role is being considered as part of an
> >> authority.
> >>
> >> The person, family, or corporate body represented by an
> authority may
> >> have any number of roles. A person may be author, editor,
> >> illustrator, translator, depicted, or any other role to the work or
> >> instance listed in the RDA relator terms or MARC relator codes.
> >>
> >> There should be *one* authority per entity, and the relation(s) of
> >> that entity to the work or instance should be external to that
> >> authority, perhaps incorporated into the link?
> >>
> >> An entity may have more than one relation to a work or instance,
> >> e.g., actor/director, author/illustrator. There should not be
> links
> >> to two or moore authorities for the same entity because of the
> two or
> >> more roles. There should be one access point per entity per
> >> work/instance, with role(s) expressed externally to the authority.
> >>
> >>
> >>
> >>
> >> __ __ J. McRee (Mac) Elrod ([log in to unmask]
> <mailto:[log in to unmask]>)
> >> {__ | / Special Libraries Cataloguing
> HTTP://www.slc.bc.ca/
> >> ___} |__
> >> \__________________________________________________________
> >>
>
> --
> Karen Coyle
> [log in to unmask] <mailto:[log in to unmask]> http://kcoyle.net
> ph: 1-510-540-7596 <tel:1-510-540-7596>
> m: 1-510-435-8234 <tel:1-510-435-8234>
> skype: kcoylenet
>
>

--
Karen Coyle
[log in to unmask] http://kcoyle.net
ph: 1-510-540-7596
m: 1-510-435-8234
skype: kcoylenet

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

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
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