|Product Name||In Lady Audley's Shadow: Mary Elizabeth Braddon and Victorian Literary Genres (Edinburgh Critical Studies in Victorian Culture)|
|Category||Book / Magazine / Publication|
|Amazon.com||Buy on Amazon ~ 0748641157|
|Price New||87.50 US Dollars (curriencies)|
|Price Used||78.83 US Dollars (curriencies)|
|Width||0.9 inches (convert)|
|Height||6.3 inches (convert)|
|Length||9.3 inches (convert)|
|Features||Used Book in Good Condition|
|Long Description||This book is devoted to Mary Elizabeth Braddon's complex relationship with the three main Victorian literary genres: the Gothic, the Detective and the Realist novel. Using Braddon's bestselling sensation fiction Lady Audley's Secret as a paradigmatic novel and as a 'haunting' textual presence across her literary career, this study provides a fertile critical reading of a wide range of Braddon's novels and short stories. Through an analysis of Braddon's negotiations with Victorian narrative, ideological and cultural issues, this monograph offers readers a refreshing view of gender, female identity and subjectivity, the treatment of insanity, questions related to technology and progress, the impact of evolutionism and Darwinism, the intersemiotic dialogue between pictorial art and novel-writing, the role of the (female) writer in the new literary market and the changing notion of capital in an increasingly fluid social context. Braddon's manipulation of Victorian literary codes and conventions proves that she was something more than a mere sensation writer and that her primary role in the nineteenth-century literary scene has to be reaffirmed. Drawing on a wide range of textual materials and literary sources, the book foregrounds Braddon's constant and sometimes ambivalent dialogue with her times, and with ours as well.|
|Search Google||by EAN or by Title|
Article of interest
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.