On Wed, Oct 15, 2008 at 4:04 PM, Walker, David <dwalker_at_calstate.edu> wrote:
> >So, I would assume that the 2416076 record
> > was merged into the 24991049 record
>
> Or maybe this is an example of WorldCat's FRBR work set grouping at work?
> I've been struggling to wrap my mind around this recently.
>
In this particular case I can confirm 2416076 was merged into the 24991049
record.
xiaoming
>
> --Dave
>
> ==================
> David Walker
> Library Web Services Manager
> California State University
> http://xerxes.calstate.edu
> ________________________________________
> From: Code for Libraries [CODE4LIB_at_LISTSERV.ND.EDU] On Behalf Of Custer,
> Mark [CUSTERM_at_ECU.EDU]
> Sent: Wednesday, October 15, 2008 12:45 PM
> To: CODE4LIB_at_LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] Google books js api, oclc/lccn, any problems?
>
> I haven't noticed any problems like that myself lately, but I have had
> some trouble/confusion with OCLC numbers and GBS in the past.
>
> If you do a search for OCLC number 2416076 in worldcat.org, you get
> directed to the book:
>
> http://www.worldcat.org/search?q=no%3A2416076&qt=advanced [which, of
> course, features no link to Google Books right now]
>
> but the OCLC number listed is 24991049, and no longer 2416076. So, I
> would assume that the 2416076 record was merged into the 24991049 record
> (which was just recently updated on 2008-08-28), and so I would also
> assume that the records retained by Google would not reflect this
> update? In any event, I would suspect that it might not be a problem
> with the GBS api, but rather with the change in metadata that is tracked
> by OCLC but not by Google (since they wouldn't have known).
>
> Do you have any other suspect examples, though, that might provide other
> evidence?
>
>
> Mark Custer
>
>
> -----Original Message-----
> From: Code for Libraries [mailto:CODE4LIB_at_LISTSERV.ND.EDU] On Behalf Of
> Jonathan Rochkind
> Sent: Wednesday, October 15, 2008 3:04 PM
> To: CODE4LIB_at_LISTSERV.ND.EDU
> Subject: [CODE4LIB] Google books js api, oclc/lccn, any problems?
>
> Anyone else noticed any problems with the GBS javascript api?
>
> It seems to have stopped returning hits for me for LCCN or OCLCnum,
> where it used to work. Seems to work now only for ISBN.
>
> Here's a URL call that used to return hits, and now doesn't:
>
> http://books.google.com/books?jscmd=viewapi&callback=gbscallback&bibkeys
> =OCLC%3A2416076%2CLCCN%3A34025476<http://books.google.com/books?jscmd=viewapi&callback=gbscallback&bibkeys=OCLC%3A2416076%2CLCCN%3A34025476>
>
> Jonathan
>
> ---
> Jonathan Rochkind
> Digital Services Software Engineer
> The Sheridan Libraries
> Johns Hopkins University
> 410.516.8886
> rochkind_at_jhu.edu
>
Received on Wed Oct 15 2008 - 17:21:41 EDT