|Product Name||Copag Poker Size Magnum Index - Blue-Red Set Of 2|
|Category||Sports / Exercise|
|Short Description||Weight:0.77 pounds|
|Amazon.com||Buy on Amazon ~ B0061N8KBQ|
|Price New||45.48 US Dollars (curriencies)|
|Long Description||100% plastic, Copag playing cards will outlast paper cards by many years. Poker sized (2.5 x 3.5 inches), this is a 4 deck set-up with a Classic Blue and Red design, and easy to read MAGNUM index. COPAG plastic playing cards are made from a exclusively engineered PVC plastic. These cards can handle the wear and tear of normal games, outlasting paper cards up to 500 times. Completely washable, you don't need to worry about soiled cards. A quick wipe with a damp washcloth, then dry and they are ready to go. Whether you play solitaire, have a kitchen table game or manage a card room - once you try COPAG you will never use any other cards again. Copag is compared to KEM cards at 60% of the cost. Try them, they will convince you there are no other reasonable options for quality 100% plastic cards. The history of COPAG is directly linked to the history of card games in Brazil. Pioneer in the manufacturing of decks, COPAG has been in this market since the beginning of the 20th century. Albino Gonalves, a graphics designer, founded the company in 1908 in the city of So Paulo and ever since COPAG has kept its position as the absolute leader in its market segment. Today, from its modern and large industrial facilities located in Manaus, in the state of Amazonas, COPAG sends part of its production to the international market, exporting decks to the United States as well as to different countries in Latin America. Most recently, Copag cards were the official cards in the 2006 World Series of Poker.|
|Search Google||by EAN or by Title|
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:
- extra_group - The text name representing the type of information the extra value represents. The extra elements are associated with this group.
- field_name - The field that this extra information is attached to. Multiple fields can be attached to the same extra_group.
- id - This is the unique id that identifies the specific extra element. It is unique across all extra groups.
- extra_short - The short text used to enhance the main data item.
- extra_long - The long text used to enhance the main data item.
- seq - The sequence that we use to display this element in a list. When two sequence numbers are the same we sort by the extra_long value.
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:
- 12 pounds
- 15.25 US Dollars
- 354 grams
- 12.4 ounces
- 12 lbs
- 15.25 USD
- 354 g
- 12.4 oz
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.