Image
EAN-130010173000080   EAN-13 barcode 0010173000080
UPC-A010173000080   UPC-A barcode 010173000080
UPC-E01017380   UPC-E barcode 01017380
Product NameRed Armband Carrying Case For Itouch 2nd And 3rd Generation, Ipod Touch 16gb 32gb 64gb + Screen Protector + Wristband
LanguageEnglish
CategoryElectronics / Photography
Amazon.comA Buy on Amazon ~ B002TG7RUE
SKUOS_APLAMB002SCR121STP777
Price New14.99 US Dollars    (curriencies)
BindingElectronics
FeaturesSafely carrying your cell phone or MP3 player with this Cellet Armband Neoprene Carrying Case. Use an Armband Carrying Case when you're working out, at the gym, jogging or running around. Clear front window lets you see your phone's screen so you can see who's calling you or check the time. Adjustable Velcro strap fits most arms. Inside lined with neoprene material. Suitable for phones, MP3 players and other devices no larger than 110mm tall x 56mm wide x 29mm thickness. High transparency and colors completely present. High wearability and anti-scraches, Utilize Exclusive MF Stamping Technology (details) for Perfect Fitment and Protection . Designed for Ipod touch 2nd and 3rd Generation, it has a good-fitting shape, easy stick and no remnant glue and is made by environment protection and recycle material. Manufactured from Ultra Thin Transparent Polymer Package includes SumacLife TM Wisdom*Courage Wristband
Long DescriptionThis package includes: . An Armband carrying case for ipod touch 2g and 3g . A Wristband . A Screen protector
Created05-22-2010
Modified04-28-2020 2:23:49pm
MD5a6814aac936ef0f49a9f7276daaf7086
SHA25653ec9b2e75ea2d29c1a95ac3a21c39549dbaf66728a014785a6038f8b7d65f34
Search Googleby EAN or by Title
Query Time0.0044029

Article of interest

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.

Close

Search

Close

Share

Close

Dialog