LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


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

CODE4LIB Home

CODE4LIB Home

CODE4LIB  April 2016

CODE4LIB April 2016

Subject:

Re: authority work with isni

From:

Stephen Hearn <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Fri, 15 Apr 2016 14:21:49 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (103 lines)

A cautionary note.  Linked data works best when the entities identified by
URIs are unambiguous. That's not always the case with VIAF and ISNI.  They
aggregate data from other ID registries algorithmically and with limited
review.  High-performing algorithms still make mistakes, as do the more
manually built descriptions they depend on.

I did a search in VIAF on "morgan, eric" (which retrieves names matching
and associated with "eric morgan") and found matched records ISNI
0000000116490460 / VIAF 56843669, both of which conflate the physicist
Patricia Lewis, born 1957 per the LCNAF record where she's "Lewis, P. M.",
and lecturer on management Patricia Lewis, born 1963 per the LCNAF record
where she's "Lewis, Patricia, 1963-", and a "Lewis, Patricia, 1954-" who
appears to be a French Canadian author writing in French on emotions from a
self-help perspective, who has been confused with the management lecturer
who also writes on emotions from a management perspective.

I also noted ISNI 0000000384457106 / VIAF 275988911, both associated with
the management lecturer's LCNAF authority, so she effectively has two ISNI
and VIAF IDs.

And the first title cited in the LCNAF authority for physicist "Lewis, P.
M." is a document on the effects of shift work produced in Washington State
for the US Nuclear Regulatory Commission in 1985. That doesn't match with
the physicist Lewis's biography in Wikipedia.  A bit more poking around in
OCLC suggests this work belongs instead to Paul Michael Lewis, who has
contemporaneous works for the NRC on work schedules in the Pacific
Northwest. He's not properly established at all in LCNAF; nor is the French
Canadian author.

This kind of sifting of data is what takes time in authority work, and
what--when it's done well--makes authority data valuable for the semantic
web. The point of the above is NOT that algorithmic aggregation is a bad
idea--just that it leaves a lot of necessary work still to do. Cases like
the above are too easy to find at present in VIAF and ISNI. ISNI has been
very responsive for me when I've reported problems (and I will work to
resolve the problems noted above), but much remains to be done. Rather than
leaping ahead to more algorithmic matching of VIAF and ISNI IDs to other
identity records, I'd like to see developers work on programs which could
mine ISNI and VIAF to detect discrepancies in the aggregated ID sources for
further review.  That could reduce the proliferation of errors already in
the data records and make all of these data resources ultimately more
valuable for semantic web use.

Stephen





On Fri, Apr 15, 2016 at 10:57 AM, Kyle Banerjee <[log in to unmask]>
wrote:

> On Fri, Apr 15, 2016 at 2:16 AM, Eric Lease Morgan <[log in to unmask]> wrote:
>
> > ...
> > My questions are:
> >
> >   * What remote authority databases are available programmatically? I
> > already know of one from the Library of Congress, VIAF, and probably
> > WorldCat Identities. Does ISNI support some sort of API, and if so, where
> > is some documentation?
> >
>
> Depends on what you have in mind. For databases similar to your example, I
> believe ORCID has an API. GNIS, ULAN, CONA, and TGN might be interesting to
> you, but there are tons more, particularly if you add subject authorities
> (e.g. AAT, MeSH). The Getty stuff is all available as LoD.
>
>   * I believe the Library Of Congress, VIAF, and probably WorldCat
> > Identities all support linked data. Does ISNI, and if so, then how is it
> > implemented and can you point me to documentation?
> >
> >   * When it comes to updating the local (MARC) authority records, how do
> > you suggest the updates happen? More specifically, what types of values
> do
> > you suggest I insert into what specific (MARC) fields/subfields? Some
> > people advocate $0 of 1xx, 6xx, and 7xx fields. Other people suggest 024
> > subfields 2 and a. Inquiring minds would like to know.
> >
>
> Implementation would be specific to your system and those you wish to
> interact with. The MARC record is used to represent/transmit data, but it
> doesn't actually exist in the sense that systems use it internally as is.
>
> Having said that, I think the logical place to put control numbers from
> different schema is in 024 because that field allows you to differentiate
> the source so it doesn't matter if control numbers overlap
>
> kyle
>



-- 
Stephen Hearn, Metadata Strategist
Data Management & Access, University Libraries
University of Minnesota
160 Wilson Library
309 19th Avenue South
Minneapolis, MN 55455
Ph: 612-625-2328
Fx: 612-625-3428
ORCID:  0000-0002-3590-1242

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

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
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager