EAN-139780811862684   EAN-13 barcode 9780811862684
Product NameThe Ultimate Book Club Organizer: A Planner For Your Reading Group
CategoryBook / Magazine / Publication
Short DescriptionSpiral
Amazon.comA Buy on Amazon ~ 0811862682
Price New18.17 US Dollars    (curriencies)
Price Used0.01 US Dollars    (curriencies)
Width1.25 inches    (convert)
Height9.5 inches    (convert)
Length7.75 inches    (convert)
Weight20 ounces    (convert)
AuthorChronicle Books
Page Count104
FeaturesUsed Book in Good Condition
Long DescriptionBook group enthusiasts rejoice! This one-of-a-kind organizer keeps book club information in one easily accessible place, with pages for jotting down reading notes and group members' contact info, a book log, and a meeting calendar. There are also fun extras like book-rating stickers, adhesive bookplates, a pocket for storing clippings and reviews, and handy bookmarks that double as a place for taking notes and recording the next meeting date while reading.

36 perforated bookmarks
36 adhesive bookplates
90 stickers
pencil pouch
pocket for storage

Similar Items9780140283709: The Readers' Choice: 200 Book Club Favorites
9780688174354: The Readers' Choice: 200 Book Club Favorites
9780876857786: The Readers' Choice: 200 Book Club Favorites
9780316313087: The Readers' Choice: 200 Book Club Favorites
9781931868839: Recipe For A Book Club: A Monthly Guide For Hosting Your Own Reading Group
9781585429240: The Book Club Cookbook, Revised Edition: Recipes And Food For Thought From Your Book Club's Favoritebooks And Authors
9781441304827: The Book Lover's Journal (Reading Journal, Book Journal, Organizer)
9780425210093: The Book Club Companion: A Comprehensive Guide To The Reading Group Experience
9780307591661: Reading Journal: For Book Lovers
9780786883240: The Reading Group Handbook: Everything You Need To Know To Start Your Own Book Club
Created11-16-2012 10:07:08am
Modified09-13-2017 5:19:26am
Search Googleby EAN or by Title
Query Time0.0251851

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...

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.