Google isbn代码错配

Question

当我试图用isbn代码找到一本书时，我遇到了一个奇怪的问题。

当我试图在谷歌图书网站上搜索它时，我得到了以下结果：

​

​

没什么大不了的。但是，当我试图搜索相同的isbn代码并请求google图书api时，如下所示：

https://www.googleapis.com/books/v1/volumes?q=isbn:8841274573

作为回应，我的结果与谷歌网站的搜索结果完全不同，我的目标是：

{
 "kind": "books#volumes",
 "totalItems": 1,
 "items": [
  {
   "kind": "books#volume",
   "id": "F1mCAQAACAAJ",
   "etag": "h72WBWNyItw",
   "selfLink": "https://www.googleapis.com/books/v1/volumes/F1mCAQAACAAJ",
   "volumeInfo": {
    "title": "Kitāb al-Thiqāt",
    "authors": [
     "Muḥammad Ibn Ḥibbān"
    ],
    "publishedDate": "1988",
    "industryIdentifiers": [
     {
      "type": "OTHER",
      "identifier": "OCLC:33995748"
     }
    ],
    "readingModes": {
     "text": false,
     "image": false
    },
    "printType": "BOOK",
    "categories": [
     "Hadith"
    ],
    "maturityRating": "NOT_MATURE",
    "allowAnonLogging": false,
    "contentVersion": "preview-1.0.0",
    "panelizationSummary": {
     "containsEpubBubbles": false,
     "containsImageBubbles": false
    },
    "language": "it",
    "previewLink": "http://books.google.it/books?id=F1mCAQAACAAJ&dq=isbn:8841274573&hl=&cd=1&source=gbs_api",
    "infoLink": "http://books.google.it/books?id=F1mCAQAACAAJ&dq=isbn:8841274573&hl=&source=gbs_api",
    "canonicalVolumeLink": "https://books.google.com/books/about/Kit%C4%81b_al_Thiq%C4%81t.html?hl=&id=F1mCAQAACAAJ"
   },
   "saleInfo": {
    "country": "IT",
    "saleability": "NOT_FOR_SALE",
    "isEbook": false
   },
   "accessInfo": {
    "country": "IT",
    "viewability": "NO_PAGES",
    "embeddable": false,
    "publicDomain": false,
    "textToSpeechPermission": "ALLOWED",
    "epub": {
     "isAvailable": false
    },
    "pdf": {
     "isAvailable": false
    },
    "webReaderLink": "http://books.google.it/books/reader?id=F1mCAQAACAAJ&hl=&printsec=frontcover&output=reader&source=gbs_api",
    "accessViewStatus": "NONE",
    "quoteSharingAllowed": false
   }
  }
 ]
}

是否有一种方法来区分(可能在请求参数中)不同的书籍有不同的isbn？

在文档中，没有对这个特殊参数的任何引用。(如果存在)

提前谢谢。

Answer 1

经过一年多的时间，谷歌似乎已经纠正了这个问题，如果我试图调用API，现在的反应与我在最初问题中提出的请求是一致的。