Image
EAN-139780788437410   EAN-13 barcode 9780788437410
Product NameKerr County, Texas Probate Records, 1856-2002
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionHardcover
Amazon.comA Buy on Amazon ~ 0788437410
SKU9780788437410ING
Price New25.11 US Dollars    (curriencies)
Price Used32.81 US Dollars    (curriencies)
Long DescriptionKerr County began numbering their probate records about 1862 and Roland Nichols is the first numbered entry. Prior to this numbering system, the earliest probate is for Daniel C. Murphy who was killed in 1856. This volume documents records from that time
Created11-21-2012 7:29:53am
Modified12-23-2013 9:19:35am
MD52629e04549484ba07b895c497d8d1cfd
SHA2565ecec2d0b83c00a14dff759ad1119e6945e027744b753586d3ea825f9a6b3e7d
Search Googleby EAN or by Title
Query Time0.0052559

Article of interest

With version 3.2 comes a new way to handle product images. This should give you more control over the images you display.

Prior to version 3.2, you simply had to check for the existance of the product>image property. If it existed and was not blank, you could safely display the image. 

Starting with version 3.2, you may want to check one more field before you display the product image. Many API users wanted access to the pending images. The only reasonable way to do this was to add a new property named product>hasImage which can be one of four values.

If you are displaying the product images to your users and you DO NOT want to display pending images that have not been checked, you should only display the image if product>hasImage=Yes. If you want to show production and pending images, you can simply check the product>image property if you like. We suggest using product>hasImage as your main check and only display the image if it meets your needs. Here are samples of the JSON structure.

The property product>hasImage will always be regurned even if you specified a list of properties in the "get" string that does not include the image property. The main reason for this is that it is possible to calculate the image path on your side thereby saving the bandwidth of returning the image path.

If you want to calculate the path to the image on your end instead of requesting it from us, you can do this in two ways. 

  1. If product>hasImage=Pending then simply use the path https://eandata.com/image/pending/{13_digit_EAN}.jpg
  2. If product>hasImage=Yes then it gets a little more tricky. We split the images into subfolders because there are so many of them. To calculate the path start with the 13 digit EAN and split it up like this: https://eandata.com/image/product/{1st_3_digits}/{2nd_3_digits}/{3rd_3_digits}/{13_digit_EAN}.jpg

This should make interacting with product and pending images much easier for you. Look at the example JSON shown above for working exmples of image paths.

Close

Search

Close

Share

Close

Dialog