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

CODE4LIB August 2012

Subject:

Re: Corrections to Worldcat/Hathi/Google

From:

Corey A Harper <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Mon, 27 Aug 2012 13:33:20 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (113 lines)

Karen,

I think there's a useful distinction here. Ed can correct me if I'm
wrong, but I suspect he was not actually suggesting that Git itself be
the user-interface to a github-for-data type service, but rather that
such a service can be built *on top* of an infrastructure component
like GitHub.

I agree that there's a barrier to use if we just plunk a bunch of our
bib data in GitHub and call it done, but the version control model and
implementation there could definitely provide a good bit of the
library-version-control stack down below the UI layer.

Cheers,
-Corey

On Mon, Aug 27, 2012 at 8:49 AM, Karen Coyle <[log in to unmask]> wrote:
> Actually, Ed, this would not only make for a good blog post (please, so it
> doesn't get lost in email space), but I would love to see a discussion of
> what kind of revision control would work:
>
> 1) for libraries (git is gawdawful nerdy)
> 2) for linked data
>
> kc
> p.s. the Ramsay book is now showing on Open Library, and the subtitle is
> correct... perhaps because the record is from the LC MARC service :-)
> http://openlibrary.org/works/OL16528530W/Reading_machines
>
>
> On 8/26/12 6:32 PM, Ed Summers wrote:
>>
>> Thanks for sharing this bit of detective work. I noticed something
>> similar fairly recently myself [1], but didn't discover as plausible
>> of a scenario for what had happened as you did. I imagine others have
>> noticed this network effect before as well.
>>
>> On Tue, Aug 21, 2012 at 11:42 AM, Lars Aronsson <[log in to unmask]> wrote:
>>>
>>> And sure enough, there it is,
>>> http://clio.cul.columbia.edu:7018/vwebv/holdingsInfo?bibId=1439352
>>> But will my error report to Worldcat find its way back
>>> to CLIO? Or if I report the error to Columbia University,
>>> will the correction propagate to Google, Hathi and Worldcat?
>>> (Columbia asks me for a student ID when I want to give
>>> feedback, so that removes this option for me.)
>>
>> I realize this probably will sound flippant (or overly grandiose), but
>> innovating solutions to this problem, where there isn't necessarily
>> one metadata master that everyone is slaved to seems to be one of the
>> more important and interesting problems that our sector faces.
>>
>> When Columbia University can become the source of a bibliographic
>> record for Google Books, HathiTrust and OpenLibrary, etc how does this
>> change the hub and spoke workflows (with OCLC as the hub) that we are
>> more familiar with? I think this topic is what's at the heart of the
>> discussions about a "github-for-data" [2,3], since decentralized
>> version control systems [4] allow for the evolution of more organic,
>> push/pull, multimaster workflows...and platforms like Github make them
>> socially feasible, easy and fun.
>>
>> I also think Linked Library Data, where bibliographic descriptions are
>> REST enabled Web resources identified with URLs, and patterns such as
>> webhooks [5] make it easy to trigger update events could be part of an
>> answer. Feed technologies like Atom, RSS and the work being done on
>> ResourceSync also seem important technologies for us to use to allow
>> people to poll for changes [6]. And being able to say where you have
>> obtained data from, possibly using something like the W3C Provenance
>> vocabulary [7] also seems like an important part of the puzzle.
>>
>> I'm sure there are other (and perhaps better) creative analogies or
>> tools that could help solve this problem. I think you're probably
>> right that we are starting to see the errors more now that more
>> library data is becoming part of the visible Web via projects like
>> GoogleBooks, HathiTrust, OpenLibrary and other enterprising libraries
>> that design their catalogs to be crawlable and indexable by search
>> engines.
>>
>> But I think it's more fun to think about (and hack on) what grassroots
>> things we could be doing to help these new bibliographic data
>> workflows to grow and flourish than to get piled under by the errors,
>> and a sense of futility...
>>
>> Or it might make for a good article or dissertation topic :-)
>>
>> //Ed
>>
>> [1] http://inkdroid.org/journal/2011/12/25/genealogy-of-a-typo/
>> [2] http://www.informationdiet.com/blog/read/we-need-a-github-for-data
>> [3] http://sunlightlabs.com/blog/2010/we-dont-need-a-github-for-data/
>> [4] http://en.wikipedia.org/wiki/Distributed_revision_control
>> [5] https://help.github.com/articles/post-receive-hooks
>> [6] http://www.niso.org/workrooms/resourcesync/
>> [7] http://www.w3.org/TR/prov-primer/
>
>
> --
> Karen Coyle
> [log in to unmask] http://kcoyle.net
> ph: 1-510-540-7596
> m: 1-510-435-8234
> skype: kcoylenet



-- 
Corey A Harper
Metadata Services Librarian
New York University Libraries
20 Cooper Square, 3rd Floor
New York, NY 10003-7112
212.998.2479
[log in to unmask]

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

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