Disable All Advertising
Image
EAN-139781609050320   EAN-13 barcode 9781609050320
Product NameHow The Sphinx Got To The Museum (How The . . . Got To The Museum)
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionHardcover
Amazon.comA Buy on Amazon ~ 1609050320
Price New8.21 US Dollars    (curriencies)
Price Used0.50 US Dollars    (curriencies)
Width0.5 inches    (convert)
Height11.25 inches    (convert)
Length9.25 inches    (convert)
Weight18.4 ounces    (convert)
Page Count40
BindingHardcover
Published09/01/2010
FeaturesUsed Book in Good Condition
Long DescriptionAcclaimed author and illustrator, Jessie Hartland, beautifully presents this informative and fascinating history of the Hatshepsut sphinx: from its carving in ancient Egypt to its arrival in the hallowed halls of New York City’s Metropolitan Museum of Art. This is essential reading for junior Egyptologists!
Similar Items9780981915913: National Geographic Kids Everything Ancient Egypt: Dig Into A Treasure Trove Of Facts, Photos, And Fun
9780226901527: National Geographic Kids Everything Ancient Egypt: Dig Into A Treasure Trove Of Facts, Photos, And Fun
9780226321028: National Geographic Kids Everything Ancient Egypt: Dig Into A Treasure Trove Of Facts, Photos, And Fun
9780698114012: Bill And Pete Go Down The Nile
9780618333455: Library Book: Seeker of Knowledge: The Man Who Deciphered Egyptian (Rise and Shine)
9780792297529: The 5,000-Year-Old Puzzle: Solving A Mystery Of Ancient Egypt
9780778741718: The 5,000-Year-Old Puzzle: Solving A Mystery Of Ancient Egypt
9780374323356: The 5,000-Year-Old Puzzle: Solving A Mystery Of Ancient Egypt
9781609052522: How The Meteorite Got To The Museum (How The . . . Got To The Museum)
9781609050900: How The Dinosaur Got To The Museum (How The . . . Got To The Museum)
View 14 more similar items
Created10-08-2012 4:06:04pm
Modified05-01-2020 6:45:09pm
MD52ab18e9a39d8517ea7176621f55c7cb7
SHA2563e3db57cb39a6ddf143aba2ff432cfc4875ed7ef68bbd1c80c2c1974725f9a90
Search Googleby EAN or by Title
Query Time0.0267892

An article of interest

Making use of the tools we offer

Data Feed API - Extra

The extra items are numerically indexed and provide extra text to go along with numeric values such as weights or distances or even currencies. The attributes that use these extra indexes are all numeric and take two fields. You can send the data in a single field as long as you use the same short or long text that we keep in our database.

Although the data feed API can deliver information as JSON or XML, we are using XML here because it is easier to read.

<attribute>
   <extra_group>Distance</extra_group>
   <field_name>depth</field_name>
   <extra>
      <id>501</id>
      <extra_short>in</extra_short>
      <extra_long>inches</extra_long>
      <seq>10</seq>
   </extra>
   <extra>
      <id>503</id>
      <extra_short>ft</extra_short>
      <extra_long>feet</extra_long>
      <seq>20</seq>
   </extra>
   <extra>
      <id>505</id>
      <extra_short>yrd</extra_short>
      <extra_long>yards</extra_long>
      <seq>30</seq>
   </extra>
</attribute>

Looking at this example, you can see that the EXTRA portion is an array of values each with their own properties. Here is what each section means:

This extra information is normally used in a drop down box next to the numeric data field that we want to enhance. Some examples might be:

You see we can display the long or short version of the extra code by using the ID index.

Fields that make use of this extra information require it when pushing data back to us in the feed. You can either send the data in two fields (value and extra_id) or in a single field (value) as long as the text following the numeric portion matches the long or short version of the extra data we store for the field.

For example, if you wanted to update a field that represented distance with the value "100 yards", you could either send that data just like that in the value field value=100+yards or in two seperate fields value=100&extra_id=505 and you would get the same results. If you send an invalid extra_id or text after the number that doesn't match our accepted list, your update would be rejected.