Image
EAN-139780747810438   EAN-13 barcode 9780747810438
Product NamePottery of the Southwest: Ancient Art and Modern Traditions (Shire Library USA)
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionHeight:8.27 inches / Length:5.87 inches / Weight:0.5 pounds / Width:0.31 inches
Amazon.comA Buy on Amazon ~ 0747810435
SKUY9780747810438
Price New6.41 US Dollars    (curriencies)
Price Used3.22 US Dollars    (curriencies)
Width0.19 inches    (convert)
Height8.23 inches    (convert)
Length5.89 inches    (convert)
Weight8 ounces    (convert)
AuthorCarol Hayes, Allan Hayes
Page Count64
BindingPaperback
Published02/21/2012
Long DescriptionFor almost two thousand years, the pottery made by the Indians of America's Southwest has remained a vital art. Today, more than twenty Pueblos and tribes make pottery within the tradition, each with a distinctive style. Many of those local styles have persisted for hundreds of years. In prehistory, beautiful pieces had high trade value, and the finest contemporary pieces command prices appropriate to fine art of any type. Potters like Nampeyo, Maria Martinez and Juan Quezada achieved worldwide fame. Yet despite its history and the skill of its artists, Southwestern Indian pottery remains surprisingly easy to collect. This book introduces the art from its beginnings to the present and displays examples that describe how America's first important art form grew into one of the world's most accessible treasures.
Similar Items9780826321374: Tradiciones Nuevomexicanas: Hispano Arts And Culture Of New Mexico
9780826314994: Fourteen Families In Pueblo Pottery
9780826304735: Anasazi Pottery
9780826303219: Santa Clara pottery today (Monograph series - School of American Research)
9780816523214: Nampeyo And Her Pottery
9780764328800: Pueblo Pottery Families (Schiffer Book for Collectors)
9780764318962: Pueblo And Navajo Contemporary Pottery: And Directory of Artists (Schiffer Book for Collectors)
9780764302336: Pueblo Pottery Families: Acoma, Cochiti, Hopi, Isleta, Jemez, Laguna, Nambe, Picuris, Pojoaque, San Ildefonso, San Juan, Santa Clara, Santo Dom (Schiffer Book for Collectors)
9780615639826: Canvas Of Clay: Seven Centuries Of Hopi Ceramic Art
9780486284767: Pueblo Pottery Designs (Dover Pictorial Archives)
View 17 more similar items
Created11-22-2012 2:06:03am
Modified10-07-2017 7:49:54am
MD552494dd025e6b5a68d7a7bfc8dd524d2
SHA256ca58ef4efb779092ec902da032bc0ad8934553d3a04aae2b1802ee2c142dc4b9
Search Googleby EAN or by Title
Query Time0.0202720

Article of interest

With version 3.2 comes a new way to handle product images. This should give you more control over the images you display.

Prior to version 3.2, you simply had to check for the existance of the product>image property. If it existed and was not blank, you could safely display the image. 

Starting with version 3.2, you may want to check one more field before you display the product image. Many API users wanted access to the pending images. The only reasonable way to do this was to add a new property named product>hasImage which can be one of four values.

If you are displaying the product images to your users and you DO NOT want to display pending images that have not been checked, you should only display the image if product>hasImage=Yes. If you want to show production and pending images, you can simply check the product>image property if you like. We suggest using product>hasImage as your main check and only display the image if it meets your needs. Here are samples of the JSON structure.

The property product>hasImage will always be regurned even if you specified a list of properties in the "get" string that does not include the image property. The main reason for this is that it is possible to calculate the image path on your side thereby saving the bandwidth of returning the image path.

If you want to calculate the path to the image on your end instead of requesting it from us, you can do this in two ways. 

  1. If product>hasImage=Pending then simply use the path https://eandata.com/image/pending/{13_digit_EAN}.jpg
  2. If product>hasImage=Yes then it gets a little more tricky. We split the images into subfolders because there are so many of them. To calculate the path start with the 13 digit EAN and split it up like this: https://eandata.com/image/product/{1st_3_digits}/{2nd_3_digits}/{3rd_3_digits}/{13_digit_EAN}.jpg

This should make interacting with product and pending images much easier for you. Look at the example JSON shown above for working exmples of image paths.

Close

Search

Close

Share

Close

Dialog