Disable All Advertising
EAN-139780582234154   EAN-13 barcode 9780582234154
Product NameThe Russian Empire: A Multi-Ethnic History
CategoryBook / Magazine / Publication
Short DescriptionHeight:9.06 inches / Length:1.1 inches / Weight:1.56 pounds / Width:6.14 inches
Amazon.comA Buy on Amazon ~ 0582234158
Price New45.80 US Dollars    (curriencies)
Price Used34.01 US Dollars    (curriencies)
Width1 inches    (convert)
Height9.3 inches    (convert)
Length6.1 inches    (convert)
Weight24.96 ounces    (convert)
AuthorAndreas Kappeler
Page Count480
Long DescriptionThe "national question" and how to impose control over its diverse ethnic identities has long posed a problem for the Russian state. This major survey of Russia as a multi-ethnic empire spans the imperial years from the sixteenth century to 1917, with major consideration of the Soviet phase. It asks how Russians incorporated new territories, how they were resisted, what the character of a multi-ethnic empire was and how, finally, these issues related to nationalism.  
Similar Items9780253204455: Russia And The Golden Horde: The Mongol Impact On Medieval Russian History
9780253001832: Russia's People Of Empire: Life Stories From Eurasia, 1500 To The Present
9780198221524: The Russian Empire 1801-1917 (Oxford History Of Modern Europe)
9780195368635: Armageddon Averted: The Soviet Collapse, 1970-2000
9780195341973: A History Of Russia
9780195305463: Ukraine: Birth Of A Modern Nation
9780195153927: A History Of Russia
9780195109276: The Russian Empire And The World, 1700-1917: The Geopolitics Of Expansion And Containment
9780140185850: We
0619659082338: Sandisk Cruzer Glide 128 Gb Usb Flash Drive Sdcz60-128g-B35
View 29 more similar items
Created02-26-2012 10:31:12pm
Modified07-01-2017 10:17:11am
Search Googleby EAN or by Title
Query Time0.0226841

Article of interest

The data feed API is URL based, but if you prefer to use the REST interface, you can do most things using that method.

Your API key should be in the request header "x-api-key" but will also work on the URL if you prefer using keycode=????????

When accessing the API using REST, the URL needs to be in this format:


version: The API version you are trying to access starting with the letter "v" followed by the version number as an integer. (ie: v3 or v2)

action: The action you wish to perform. Not all actions are currently available using the API. The ones that work currently are:

dataID: This is the data you are searching for. For "find" this is an EAN or UPC code. For "search" this can be any text properly encoded for he URL.

To get your data back as XML, put "application/xml" in your "accept" header. If you prefer JSON (the default format) you can leave off the "accept" header or send "application/json". You can also include your preference on the URL using mode=json or mode=xml but using the request header is the preferred method.

We will continue to add more REST interface features in the future so be sure to check back on this page every once in a while.

*** Updating data via the REST interface is not ready yet but will require test=1 on the URL as the first variable if you are testing your application to prevent actual data updates. Placing it later on the URL could cause this variable to be skipped if you have errors in your URL.