Image
EAN-139780140383195   EAN-13 barcode 9780140383195
Product NameBound For Oregon
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionPaperback
Amazon.comA Buy on Amazon ~ 0140383190
Price New3.00 US Dollars    (curriencies)
Price Used0.95 US Dollars    (curriencies)
Width0.5 inches    (convert)
Height7.75 inches    (convert)
Length5.06 inches    (convert)
Weight4.96 ounces    (convert)
AuthorJean Van Leeuwen
Page Count176
BindingPaperback
Published11/01/1996
FeaturesGreat product!
Long Description"Basing her story on the published accounts of her true-life heroine, Mary Ellen Todd, Van Leeuwen describes a family's tumultuous journey along the Oregon Trail in 1852." -- Publishers Weekly With only a guide book to show them the way, the Todd family sets out from their Arkansas home on a two thousand mile trek to claim unchartered Oregon Territory. Crossing rough terrain and encountering hostile people, the Todds show their true pioneering spirit. But as winter draws near, will the Todds have the strength to complete their journey? And if they make it, will Oregon fulfill their dreams? “This is a convincing picture of a pioneer journey that does a good job of showing the tremendous sacrifices people made to follow their dream of a better life.” – School Library Journal
Similar Items9781113151971: Amos Fortune, Free Man (Newbery Library, Puffin)
9780801490903: Amos Fortune, Free Man (Newbery Library, Puffin)
9780801053153: Amos Fortune, Free Man (Newbery Library, Puffin)
9780548587942: Amos Fortune, Free Man (Newbery Library, Puffin)
9780435082567: Amos Fortune, Free Man (Newbery Library, Puffin)
9780380715664: Amos Fortune, Free Man (Newbery Library, Puffin)
9780891452317: Blue Willow
9780340592472: Blue Willow
9780140309249: Blue Willow
9781575050263: A Head Full Of Notions: A Story About Robert Fulton (Creative Minds Biography)
View 123 more similar items
Created02-26-2012 6:38:13pm
Modified04-30-2020 4:01:13pm
MD5793fca0431b3e040f9815630d1acd78f
SHA25652627526ecff20251d7bc07645491f81b8a41db01d7903d1f61a2bd4221bb235
Search Googleby EAN or by Title
Query Time0.0213358

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