Disable All Advertising
Image
EAN-139780060908805   EAN-13 barcode 9780060908805
Product NameLife in a Medieval City (Medieval Life)
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionPaperback
Amazon.comA Buy on Amazon ~ 0060908807
SKUU14347613
Price New5.92 US Dollars    (curriencies)
Price Used0.41 US Dollars    (curriencies)
Width0.65 inches    (convert)
Height8 inches    (convert)
Length5.31 inches    (convert)
Weight7.68 ounces    (convert)
AuthorJoseph Gies, Frances Gies
Page Count274
BindingPaperback
Published09/30/1981
FeaturesA detailed look at the life and work of people who lived in the Medieval Europe.
Long DescriptionFrom acclaimed historians Frances and Joseph Gies comes the reissue of their classic book on day-to-day life in medieval cities, which was a source for George R.R. Martin’s Game of Thrones series. Evoking every aspect of city life in the Middle Ages, Life in a Medieval City depicts in detail what it was like to live in a prosperous city of Northwest Europe in the twelfth and thirteenth centuries. The year is 1250 CE and the city is Troyes, capital of the county of Champagne and site of two of the cycle Champagne Fairs—the “Hot Fair” in August and the “Cold Fair” in December. European civilization has emerged from the Dark Ages and is in the midst of a commercial revolution. Merchants and money men from all over Europe gather at Troyes to buy, sell, borrow, and lend, creating a bustling market center typical of the feudal era. As the Gieses take us through the day-to-day life of burghers, we learn the customs and habits of lords and serfs, how financial transactions were conducted, how medieval cities were governed, and what life was really like for a wide range of people. For serious students of the medieval era and anyone wishing to learn more about this fascinating period, Life in a Medieval City remains a timeless work of popular medieval scholarship.
Similar Items9780521060059: The Time Traveler's Guide To Medieval England: A Handbook For Visitors To The Fourteenth Century
9780486414355: Medieval People
9780385091879: Great Cities Of The Ancient World
9780373222391: The Time Traveler's Guide To Medieval England: A Handbook For Visitors To The Fourteenth Century
9780060925819: Cathedral, Forge And Waterwheel: Technology And Invention In The Middle Ages
9780060923044: Women In The Middle Ages
9780060914684: Marriage And The Family In The Middle Ages
9780060162153: Life In A Medieval Village
9780060157913: Marriage And The Family In The Middle Ages
8601401131311: The Time Traveler's Guide To Medieval England: A Handbook For Visitors To The Fourteenth Century
View 25 more similar items
Created02-26-2012 9:03:39pm
Modified04-30-2020 3:04:18pm
MD5cdf109f541a0245a07762e9695638432
SHA256ad29c9dbf3227d0d35b64476b44d9d6f10dc8b2cd4ec01378c3d024989c58786
Search Googleby EAN or by Title
Query Time0.0277741

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