<mods:mods version="3.3" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd" xmlns:mods="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><mods:titleInfo><mods:title>Google Books linking: OCLC number as an alternative to ISBN and LCCN</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Steve</mods:namePart><mods:namePart type="family">Bischof</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>Most systems tend to use the ISBN or the ISSN as the primary key to make calls to the Google Books API, but many libraries are more likely to have an OCLC number present in the record. This is especially true of pre-1923 imprints, where the link to Google Books is more likely to present a link to a full text version of the item. However sending an OCLC number to GBS does present some additional scripting challenges.</mods:abstract><mods:classification authority="lcc">General Topics</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2011-05</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>