| Image |  |
| EAN-13 | 9789056627621  |
| Product Name | Russia's Unknown Orient: Orientalist Painting 1850-1920 |
| Category | Book / Magazine / Publication |
| Short Description | Height:11.81 inches / Length:9.84 inches / Weight:3.2 pounds / Width:0.71 inches |
| Amazon.com |  Buy on Amazon ~ 9056627627 |
| SKU | ACOMMP2_BOOK_USEDVERYGOOD_9056627627 |
| Price New | 16.01 US Dollars (curriencies) |
| Price Used | 35.00 US Dollars (curriencies) |
| Width | 9.75 inches (convert) |
| Height | 0.72 inches (convert) |
| Length | 11.58 inches (convert) |
| Weight | 51.2 ounces (convert) |
| Author | Olga Atroschenko, Vladimir Bulatov, Inessa Kouteinikova, Karina Solovyeva, David Schimmelpenninck van der Oye, Irina Bagdamian |
| Page Count | 224 |
| Binding | Paperback |
| Published | 03/31/2011 |
| Long Description | Russia's Unknown Orient tells the story of Russia's artistic and historical ties with its southern neighbors: Uzbekistan (former Turkistan), the countries of the Caucasus (Georgia and Armenia) and the Crimea. The bond between Russia and these culturally distinct lands was marked by a deep fascination with Oriental traditions and a succession of wars and imperialist maneuvers, themes which found their way into the art of the nineteenth century. Perhaps the most important artist in this context was Vasily Vereshchagin (1842-1904), who traveled with the Russian army on campaigns to the south and served as the painterly equivalent of a war photographer, depicting both the cruel reality of war and the riches of the Oriental cultures. The works of such artists are presented here alongside the output of indigenous contemporary artists from these Central Asian lands--practitioners who offered personal interpretations of the rich traditions of their homelands that continued to develop even under Russian dominion. The historical and art-historical context of this diverse group of artists is taken up by a range of authors in this lush, generously illustrated volume, which includes more than 130 works by Vereshchagin, Martiros Saryan, Vasily Polenov, Niko Pirosmanishvili, Pavel Kuznetsov, Evgeny Lanseray and others. |
| Similar Items | 9780701202033: Edwardian Opulence: British Art At The Dawn Of The Twentieth Century (Yale Center For British Art) 9780582234154: The Russian Empire: A Multi-Ethnic History 9780374949365: Russian Orientalism: Asia In The Russian Mind From Peter The Great To The Emigration 9780300138986: The Lure Of The East: British Orientalist Painting |
| Created | 01-25-2013 1:20:34am |
| Modified | 05-01-2020 9:37:06pm |
| MD5 | dbb9f5962ced5f51d2ab0f6d71c50474 |
| SHA256 | df332dd84764655708e5b07b0e58d02ce72d19df4db0035a5574ad98def6ffba |
| Search Google | by EAN or by Title |
| Query Time | 0.0153360 |
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:
https://eandata.com/feed/{version}/{action}/{dataID}/
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:
- find: perform a data lookup
- search: perform a text search
- asin-to-ean: convert an Amazon ASIN into an EAN
- imdb-to-ean: convert and IMDB ID into an EAN
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.