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  August 2015

BIBFRAME August 2015

Subject:

Re: BIBFRAME Identifier, Role, and Authority Proposals

From:

Thomas Berger <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Thu, 27 Aug 2015 08:46:04 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (87 lines)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 27.08.2015 um 03:26 schrieb Karen Coyle:
> 
> 
> On 8/26/15 3:17 PM, Thomas Berger wrote:
>> LC records may be lacking explicit (especially death) dates, but
>> they usually contain a wealth of textual references which more often
>> than not reveal exact birth dates and other important contextual
>> information (affiliations, notable works, places of birth, death
>> and activity).
> You say "usually," but I see "occasionally." As an example, here's the
> LC authority record for me:
> http://id.loc.gov/authorities/names/n89613425.marcxml.xml, and if you
> can find "other important contextual information" you are a better
> reader than I am.

Sure I do. I "found: FRBR, before and after, 2016: ECIP t.p. (Karen
Coyle) data view (Karen Coyle is a librarian with over 30 years'
experience with library technology)" (probably you weren't aware the
record was changed last week and human readers should prefer the
text view < http://id.loc.gov/authorities/names/n89613425 > to grok
in the information more easily.

- From my personal experience I can tell that this exactly is the kind
of information needed when e.g. having to decide whether this person
could be identical with some E. K. Coyle, b. 1977 with a speciality in
constitutional law. Much of it works over exclusion and having data
(as opposed to text snippets as above) definitely will assist with
preliminary filtering. In case of exact matching data sometimes
doubts arise whether the records you're looking at already confuse
different persons. Especially beware of other authority records
citing LCauth records as source - they may have gotten it completely
wrong!


>  Plus, when that information is available it's in a
> note field and can be quite cryptic:
> 
> "found:Phone call to Curbstone Press, 07-13-94(Michael H. Cooper is a
> pseudonym of Michael Clark; b. 6-11-51; res. in Alaska)"
> "found:Message from J. Baker, 11/08/88(Michael D. Cooper; b. 10/30/41)
 "

Fortunately not in the same record...



> Thomas, I think you are being overly optimistic about the state of
> authority data today. I agree that it can get better, but I don't agre
e
> that VIAF extracts much "data" -- it basically gets what you can get
> from a MARC name heading field, and adds in titles of works (which it
> gets from the WorldCat database). There may be more information in
> non-US authority files, but rather than relying on impressions it woul
d
> be better to have a good study of available data.

Maybe I had been a bit sloppy but my intention was not talking about
authority data but on information contained in authority records. From
personal experience, and statements made by those involved with VIAF
(like Thom Hickeys blog < http://outgoing.typepad.com/ >) I've gathered
the firm conviction that in the Cooper example
http://id.loc.gov/authorities/names/n94067387.html
VIAF /does/ extract exact to the day birth dates from the variant
heading "Clark, Michael, 1951 June 11-" in order to perform tie-breaking
when needed. I mean, VIAF is all about data mining applied to library
generated information and unfolds its use exactly in situations where
suitable categorized data elements are lacking. In a world where
authority records are in a better shape they would almost immediately
find to each other based on the data they contain and we perhaps
wouldn't even need something like VIAF...

viele Gruesse
Thomas Berger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iJwEAQECAAYFAlXesioACgkQYhMlmJ6W47NoyAP+ODi+T6PKg+cEA4RLEyvJ8ZEJ
JbXhSfhb4tgpqUASc/z8xyVxhfD0M2I3hbszfUw91O8dm+q7CKxd4mPw96pXf0on
KCSY9fdfgCE/FPb5vV8RNLdQUlXWNIgeUXD6i3pedMRVoLjK+u4gfcp/2iL83Hzy
mIT/jj9aLMZxziKtP7w=
=cPrs
-----END PGP SIGNATURE-----

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