Yes, there are definitely errors in GBS. The errors are not in fact
limited to cover images. When you get the wrong cover image, it's
usually becuase Google has actually associated an ISBN (or LCCN or
OCLCnum) with the _wrong book_. It's not just the cover that's wrong,
it's the entire record. If you're using GBS APIs for more than just
covers, for instance for full text availability, that's the wrong book too.
Such is life.
Bethany R Levrault wrote:
> We use Google Books, and have sometimes found that the cover art displayed
> is not for the correct item. For example, a basic book on business had cover
> art for a wedding book. Usually we just notify them and they fix it. There
> haven't been any problems with slowness as far as I know.
>
> Bethany R. Levrault
> Head of Copy Cataloging
> Cataloging and Metadata Services Department
> University of Colorado at Boulder Libraries
> 184 UCB
> Boulder, CO 80309-0184
> Phone: (303) 735-2873
> Fax: (303) 492-0494
> bethany.levrault_at_colorado.edu
>
>
>
> -----Original Message-----
> From: Next generation catalogs for libraries
> [mailto:NGC4LIB_at_LISTSERV.ND.EDU] On Behalf Of Edward M. Corrado
> Sent: Monday, March 16, 2009 12:38 PM
> To: NGC4LIB_at_LISTSERV.ND.EDU
> Subject: [NGC4LIB] Free cover images?
>
> Hello all,
>
> We are reevaluating our source of cover images. At this point I have
> identified four possible sources of free images:
>
> 1. Amazon
> 2. Google Books
> 3. LibraryThing
> 4. OpenLibrary
>
> I know that their is some question if the Amazon and Google books images
> will allow this (although I've also yet to hear Amazon or Google telling
> libraries that use their Web services for this to cease and desist).
> However, besides that issue, has anyone noticed any technical problems
> with any of these four? I'm especially concerned about slow and/or
> non-consistent performance.
>
> Edward
>
>
Received on Mon Mar 16 2009 - 15:12:12 EDT