EAN-139780192629302   EAN-13 barcode 9780192629302
Product NameMapping Fate: A Memoir Of Family, Risk, And Genetic Research
CategoryBook / Magazine / Publication
Short DescriptionHeight:7.56 inches / Length:0.39 inches / Weight:0.37 pounds / Width:5.12 inches
Amazon.comA Buy on Amazon ~ 0520207416
Price New8.00 US Dollars    (curriencies)
Price Used2.00 US Dollars    (curriencies)
Width1 inches    (convert)
Height8.25 inches    (convert)
Length5.5 inches    (convert)
Weight16.96 ounces    (convert)
AuthorAlice Wexler
Page Count319
Long Description
In Mapping Fate, Alice Wexler tells the story of a family at risk for a hereditary, incurable, fatal disorder: Huntington's disease, once called Huntington's chorea. That her mother died of the disease, that her own chance of inheriting it was fifty-fifty, that her sister and father directed much of the extraordinary biomedical research to find the gene and a cure, make Wexler's story both astonishingly intimate and scientifically compelling.

Alice Wexler's graceful and eloquent account goes beyond the specifics of Huntington's disease to explore the dynamics of family secrets, of living at risk, and the drama and limits of biomedical research. Mapping Fate will be a touchstone for anyone with questions about genetic illness and the possibilites and perils of genetic testing.
Similar Items9780300105025: The Woman Who Walked Into The Sea: Huntington's And The Making Of A Genetic Disease
9780965739696: Dna: The Secret Of Life
9781573226578: Dying Well: Peace and Possibilities at the End of Life
9780710039569: Dying Well: Peace and Possibilities at the End of Life
9780805075199: Enough: Staying Human In An Engineered Age
9780520088368: The Worth Of A Child
9780671732905: What Kind Of Life: The Limits Of Medical Progress
9780300158618: The Woman Who Walked Into The Sea: Huntington's And The Making Of A Genetic Disease
9780878405732: What Kind Of Life?: The Limits Of Medical Progress
9780520242814: Skin: A Natural History
View 20 more similar items
Created02-26-2012 8:54:49pm
Modified08-27-2017 1:25:09pm
Search Googleby EAN or by Title
Query Time0.0063231

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.

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.