Image
EAN-139780748769964   EAN-13 barcode 9780748769964
Product NameNelson Handwriting
CategoryBook / Magazine / Publication
Short DescriptionPaperback
Amazon.comA Buy on Amazon ~ 074876996X
SKUACOMMP2_BOOK_USEDVERYGOOD_074876996X
Price New13.04 US Dollars    (curriencies)
Price Used3.60 US Dollars    (curriencies)
Long DescriptionThis work contains clearly laid out pages with Focus, Extra and Extension. The 'Getting ready to write' flap at the front of each book enables pupils to check that they are ready to begin writing. The 'Handwriting Checklist' section on the reverse of the flap enables pupils to check on their own progress. It also provides links to Progression in Phonic at Red level.
Created11-14-2012 6:25:17pm
Modified12-23-2013 8:00:23am
MD58eddd7212ffeffc7e02f021422052d13
SHA256c2400e125cbbf333c57587181f786bfcf4b9f0062509ea0efba18c44c1a880f9
Search Googleby EAN or by Title
Query Time0.0050130

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