EAN-139780806349640   EAN-13 barcode 9780806349640
Product NameVirginia Migrations : Hanover County. Volume I (1723-1850) : Wills, Deeds, Depositions, Invoices, Letters, and Other Documents of Historical and Genealogical Interest. Volume II (1743-1871) : Wills, Deeds, Depositions, Letters, Marriages, Obituaries,
CategoryBook / Magazine / Publication
Short DescriptionHeight:8.5 inches / Length:5.51 inches / Weight:0.76 pounds / Width:0.59 inches
Amazon.comA Buy on Amazon ~ 0806349646
Price New27.08 US Dollars    (curriencies)
Price Used12.95 US Dollars    (curriencies)
Width0.62 inches    (convert)
Height8.5 inches    (convert)
Length5.51 inches    (convert)
Weight13.28 ounces    (convert)
AuthorEugenia G. Glazebrook
Page Count296
Long DescriptionHanover County, one of the Tidewater counties of Virginia, was formed from New Kent County in 1720. Hanover would become the parent of Louisa County, which was partitioned from Hanover in 1742, and much of present-day Albemarle County, which was formed in 1744 from Louisa and Goochland counties. Hanover's most famous son, of course, was the patriot Patrick Henry. In this very scarce two-volume work, Mr. and Mrs. Glazebrook succeeded in extracting those documents pertaining to Hanover County that survived the burning of Richmond in April 1865 and that were not published in William Ronald Cocke's Hanover County Chancery Wills and Notes. The surviving materials consist of a great many deeds, wills, inventories, accounts, letters, depositions, etc., pertaining to Hanover County for the colonial and early Federal periods. Many of the suits, in particular, stem from the period prior to the French and Indian War. One of the richest sources examined by the Glazebrooks were the files of the United States District Court at Richmond. Other sources included early newspapers, an extensive list of Hanover marriages discovered at the Library of Virginia, and a list of non-resident land owners in Hanover County taken from the Land Books for 1814-1815. Both volumes feature extremely informative, annotated Introductions prepared by Leon M. Bazile, a leading authority on Hanover County history and genealogy, and complete name indexes at the back. With references to nearly 5,000 early inhabitants of Hanover County, this hard-to-find sourcebook will unquestionably be in great demand among researchers.
Similar Items9780893088293: (Hanover County, VA.) Vestry Book of St. Paul's Parish, Hanover County, VA., 1706-1786.
9780806348476: The Vestry Book Of St. Paul's Parish, Hanover County, Virginia, 1706-1786
9780806315782: Tidewater Virginia Families: Generations Beyond Adding The Families Of
9780806308364: Marriages Of Goochland County, Virginia, 1733-1815
9780806308241: Hanover County Chancery Wills And Notes
9780788403361: Vital Records of Three Burned Counties: Births, Marriages, and Deaths of King and Queen, King William, and New Kent Counties, Virginia, 1680-1860
Created02-26-2012 9:47:52pm
Modified05-01-2020 2:32:46am
Search Googleby EAN or by Title
Query Time0.0149319

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.


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:

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:

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.