Disable All Advertising
Image
EAN-139781166078645   EAN-13 barcode 9781166078645
Product NameHistory Of The Ely Reunion: Held At Lyme, Connecticut, July 10, 1878 (1879)
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionHardcover
Amazon.comA Buy on Amazon ~ 1166078647
SKU9781166078645ING
Price New26.60 US Dollars    (curriencies)
Width8.88 inches    (convert)
Height5.91 inches    (convert)
Length0.49 inches    (convert)
Weight14.4 ounces    (convert)
AuthorMargaret Elizabeth Dunbar Stuart
Page Count162
BindingHardcover
Published09/10/2010
Long DescriptionThis scarce antiquarian book is a facsimile reprint of the original. Due to its age, it may contain imperfections such as marks, notations, marginalia and flawed pages. Because we believe this work is culturally important, we have made it available as part of our commitment for protecting, preserving, and promoting the world's literature in affordable, high quality, modern editions that are true to the original work.
Created11-15-2012 9:05:54am
Modified01-19-2014 2:38:22am
MD513c375910fb7576a10a4efae0f946592
SHA256c1a7d09af45826cbbdd4d649a201f4ad7c80e0a941e6e0e871ffbec9c1ddbffc
Search Googleby EAN or by Title
Query Time0.0078590

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.