Image
EAN-13	9780745319650
Product Name	Bookchin: A Critical Appraisal
Language	English
Category	Book / Magazine / Publication
Short Description	Hardcover
Amazon.com	Buy on Amazon ~ 0745319653
SKU	PLUTO-BWS-687-SAA42
Price New	85.47 US Dollars    (curriencies)
Price Used	57.80 US Dollars    (curriencies)
Width	0.8 inches    (convert)
Height	8.5 inches    (convert)
Length	5.33 inches    (convert)
Author	Damian F. White
Page Count	256
Binding	Hardcover
Published	12/20/2008
Features	Used Book in Good Condition
Long Description	This is the first comprehensive overview of the work of Murray Bookchin, the left-libertarian social theorist and political ecologist who is widely regarded as the visionary precursor of anti-corporate politics. Bookchin's writing spans fifty years and engages with a wide variety of issues: from ecology to urban planning, from environmental ethics to debates about radical democracy. Weaving insights from Hegel and Marx, Kropotkin and Mumford, Bookchin presents a critical theory whose central utopian message is 'things could be other than they are'. This accessible introduction maps the evolution of Bookchin’s project. It traces his controversial engagements with Marxism, anarchism, critical theory, postmodernism and eco-centric thought. It evaluates his attempt to develop a social ecology. Finally, it considers how his thinking relates to current debates in social theory and environmentalism, critical theory and philosophy, political ecology and urban theory. Offering a clear account of Bookchin's key themes, this book provides a critical but sympathetic account of the strengths and weaknesses of Bookchin's writing.
Created	11-09-2012 2:05:50pm
Modified	09-09-2018 9:41:43am
MD5	42d3c2b9383ebea4ea7a84efba533e97
SHA256	754acccbdb2a580a03681fc259746fb4c576345b5cc6f3ec3584f42428aa95ff
Search Google	by EAN or by Title
Query Time	0.0052869

The extra items are numerically indexed and provide extra text to go along with numeric values such as weights or distances or even currencies. The attributes that use these extra indexes are all numeric and take two fields. You can send the data in a single field as long as you use the same short or long text that we keep in our database.

Although the data feed API can deliver information as JSON or XML, we are using XML here because it is easier to read.

<attribute>
   <extra_group>Distance</extra_group>
   <field_name>depth</field_name>
   <extra>
      <id>501</id>
      <extra_short>in</extra_short>
      <extra_long>inches</extra_long>
      <seq>10</seq>
   </extra>
   <extra>
      <id>503</id>
      <extra_short>ft</extra_short>
      <extra_long>feet</extra_long>
      <seq>20</seq>
   </extra>
   <extra>
      <id>505</id>
      <extra_short>yrd</extra_short>
      <extra_long>yards</extra_long>
      <seq>30</seq>
   </extra>
</attribute>

Looking at this example, you can see that the EXTRA portion is an array of values each with their own properties. Here is what each section means:

• extra_group - The text  name representing the type of information the extra value represents. The extra elements are associated with this group.
• field_name - The field that this extra information is attached to. Multiple fields can be attached to the same extra_group.
• id - This is the unique id that identifies the specific extra element. It is unique across all extra groups.
• extra_short - The short text used to enhance the main data item.
• extra_long - The long text used to enhance the main data item.
• seq - The sequence that we use to display this element in a list. When two sequence numbers are the same we sort by the extra_long value.

This extra information is normally used in a drop down box next to the numeric data field that we want to enhance. Some examples might be:

• 12 pounds
• 15.25 US Dollars
• 354 grams
• 12.4 ounces

• 12 lbs
• 15.25 USD
• 354 g
• 12.4 oz

You see we can display the long or short version of the extra code by using the ID index.

Fields that make use of this extra information require it when pushing data back to us in the feed. You can either send the data in two fields (value and extra_id) or in a single field (value) as long as the text following the numeric portion matches the long or short version of the extra data we store for the field.

For example, if you wanted to update a field that represented distance with the value "100 yards", you could either send that data just like that in the value field value=100+yards or in two seperate fields value=100&extra_id=505 and you would get the same results. If you send an invalid extra_id or text after the number that doesn't match our accepted list, your update would be rejected.