EAN-130782009237938   EAN-13 barcode 0782009237938
UPC-A782009237938   UPC-A barcode 782009237938
Product NamePokmon Indigo League - Season One, Part 3
CategoryElectronics / Photography: A/V Media: Movie / TV
Short DescriptionWeight:1.25 pounds
Amazon.comA Buy on Amazon ~ B000WW1YOM
Price Used24.50 US Dollars    (curriencies)
Run Time650 minutes
Aspect Ratio1.33:1
CastEric Stuart, Ikue Ohtani, Mayumi Iizuka, Rachael Lillis, Veronica Taylor
GenreKids & Family
Run Time650 minutes
Width5.5 inches    (convert)
Height2 inches    (convert)
Length7.5 inches    (convert)
Weight68 hundredths pounds    (convert)
FormatMultiple Formats, Animated, Box set, Color, NTSC
Run Time650 minutes
Similar Items0782009244820: Pokemon Advanced Challenge Complete Collection
0782009243984: Pokemon Master Quest - The Complete Collection
0782009243991: Pokemon Johto League Champions - The Complete Collection
0782009244004: Pokemon The Johto Journeys - The Complete Collection
0782009243854: Pokemon Adventures in the Orange Islands - The Complete Collection
0782009237945: Pokemon Season 1 V04-Orange Island (Dvd)
0782009236863: Pokemon Season Part 2 Box Set (Dvd) (3discs)
9780790748276: Pokemon The First Movie - Mewtwo Vs. Mew
Modified06-01-2019 6:45:38am
Search Googleby EAN or by Title
Query Time0.0184190

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.


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.