Image
EAN-139780810922976   EAN-13 barcode 9780810922976
Product NameHow To Visit A Museum
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionPaperback
Amazon.comA Buy on Amazon ~ 0810922975
SKUEASY63628
Price New6.24 US Dollars    (curriencies)
Price Used0.25 US Dollars    (curriencies)
Width0.5 inches    (convert)
Height9.75 inches    (convert)
Length6.75 inches    (convert)
Weight13.6 ounces    (convert)
AuthorDavid Finn
Page Count135
BindingPaperback
Published09/30/1985
Long DescriptionHow to Visit a Museum conveys the real excitement of visiting a museum for children and adults in a personal and informal manner. Museum educators will find this book a useful tool for developing programs that help visitors obtain a more rewarding experience from their museum visits.
Similar Items9780226791548: Learning To Look: A Handbook For The Visual Arts (Phoenix Books)
9780070387317: The Mcgraw-Hill Museum-Goer's Guide
9780810927261: How To Look At Everything
9780500203125: The Theatre: A Concise History (Third Edition) (World Of Art)
9781606060582: Teaching In The Art Museum: Interpretation As Experience
9781566915168: Rick Steves’ Europe 101: History And Art For The Traveler
9781566913454: Rick Steves' Mona Winks: Self-Guided Tours Of Europe's Top Museums
9780953443833: The Pocket Guide To Oxford: A Guidebook To The Architecture, History, And Principal Attractions Of Oxford, With Help From Our Knowledgeable Friend, The Oxford Dodo
9780810924123: How To Look At Sculpture
9780140137705: England In The 19th Century, 1815-1914: Volume 8 (Hist Of England, Penguin)
9781562612467: Rick Steves' Europe 101 (Europe 101: History And Art For The Traveler (Rick Steves))
9781562615352: Rick Steves' Europe 101: History And Art For The Traveler
Created05-20-2012 1:05:00am
Modified04-29-2017 12:16:33pm
MD5c4ddd25c57d4a3cd2861b1b16aec1ecc
SHA2564921718ce03513d672dad42c28d2a39ce8fd6dc59eaa449047b2c8ed9dd8badb
Search Googleby EAN or by Title
Query Time0.0233340

Article of interest

This describes how to use version 3.x of the data feed. Version 2.x of the feed is still supported. Version 1.x of the feed is no longer supported in any way.

IMPORTANT: Starting with version 3.2, we have a new property and a new way of dealing with product images. Read about it here.

Accessing the data requires your account to have an active data feed. This switch can be turned on or off on the data feed page. This is also where you will be able to view your KEYCODE which is required to make calls to the feed.

Main changes from version 2.x to 3.x include (but not limited to)...

Calls to the data feed are made via HTTP GET or HTTP POST requests. There are only a few required parameters when making a call.

Most other parameters are optional and they will alter the way data is returned to you and how your request is processed. You can also pass in your own values that you need carried through. Any parameter that the system doesn't recognize will be returned AS-IS in the status block. This can be handy in situations where you are pulling the data in an asyncronus manor and need extra information passed into your callback routine.

When performing a lookup...

When updating data...

When deleting data...

There are some special "get" operations that need no other parameters. You would not use "find" or "update" when using these. Only use the "keycode", "mode" and "get" for these items. These operations are important because many of our elements are data driven and that data changes over time. We normally don't remove attributes or categories but we do often add to the collection.

The returned data can come back in JSON or XML format. In either case the structure of the data is the same. Because it is easier to read, we will be using XML to demonstrate the layout of the result. Here is the data layout. Notice that this is a complex object and some elements have child elements and some elements may be arrays with repeating content.

The easiest way to get the feel of the data is to make several requests using your web browser and ask for the data in XML format. Although JSON is often easier to work with in code, the XML output is often easier for people to read because of the nice markup tags that wrap around each element and the web browser will usually do a nice job of indenting to make it clear which elements are stored within other elements.

Close

Search

Close

Share