<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="2009" public="1" featured="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://reconstructingvirginia.richmond.edu/items/show/2009?output=omeka-xml" accessDate="2026-07-12T00:09:06+00:00">
  <collection collectionId="230">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="44639">
                <text>Wiroa-Week-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="44640">
                <text>This Week in Reconstruction, March 8-14, 1871</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="44641">
                <text>Megan Wiora</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="44642">
                <text>March 8-14, 1871</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="44643">
                <text>The Chesapeake and Ohio Railroad announced that they are building a railroad across states, something that the Virginia people should be happy about. Unfortunately, they are not, for, they cannot realize the benefits of this progress until it are materialized. Richmond and Virginia needs to understand the indication of this railroad for the progress of the Commonwealth, but due to the rocky path and manipulations the state has faced in the past, it is understandable that the people have felt "disappointment, hope low, deferred, [that] has dulled their sensibilities along with their expectations, and we question whether they will fully understand the great event until it is upon them. Still they must be gradually opening their eyes to what is coming." This is the beginning of a prosperous time, and the people must carry a passion and hope for the city if Richmond is to be a thriving metropolis.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="1">
    <name>Text</name>
    <description>A resource consisting primarily of words for reading. Examples include books, letters, dissertations, poems, newspapers, articles, archives of mailing lists. Note that facsimiles or images of texts are still of the genre Text.</description>
    <elementContainer>
      <element elementId="5">
        <name>Transcription</name>
        <description>Any written text transcribed from a sound</description>
        <elementTextContainer>
          <elementText elementTextId="62720">
            <text>The Free Bridge.'As the city of Richmond is believed to be'Interested in a free bridge between herself'and Manchester to a much greater extent'than many of her citizens think, it is well'to invite attention to the proposed meeting'advertised to be held soon in Manchester to'protest against, the erection of the bridge'which the bridge commissioners are now'about to let, if they have not already'done so.'1st. The trustees of the town of Manchester did, more than a year ago, appropriate money to be expended in the erection of a bridge.'2d. A prior set of trustees nominated'the present bridge commissioners of the'town of Manchester, with instructions to'obtain proper legislation and proceed to 'build the bridge.'3d. Such legislation was had, and the'plan of the law contemplated the corporation'of Richmond and Chesterfield in the'undertaking.'4th. Before the law was enacted its details'were submitted to a large meeting of'the town people, convened upon full notice''as to time, place, and purpose, and were'unanimously approved by said meeting.'5th. The City Council of Richmond has'agreed, by a large majority, to aid in the'erection of the bridge, and further, has'formally appropriated money for that pur-purpose.'6th. The joint commission has selected a'site for a bridge, guided by the report of a'competent engineer, and having been compelled to discard Mayo's bridge by the exorbitant price asked for that property by its'owners.'7th. The money needed by Manchester'has been obtained upon the mortgage which'the law authorized, and the bridge commissioners intend to use it in building the'bridge.'8th. That bridge, when built, will be very'much superior to to Mayo's bridge in durability and safety, and will accommodate'more citizens of Manchester, and a larger'area of the town.'Under this state of facts it is not seen'what good can come of the proposed meeting, though nobody can question the right'to hold it.'The interest of Richmond in the matter is'this : The erection of a free bridge will be'the first step, if Richmond is wise, to a'speedy annexation of Manchester; and it'will be well to withhold sympathy from'those whose action will delay, and perhaps'prevent, that consummation. That annexation will, in the present aspect of things,'more than double the wealth of Manchester in a very short time, and add very largely to the wealth of Richmond.'It is probable the friends of the free'bridge will not, as a general thing, take'part in the proceedings of the meeting:'though they entertain the firm belief that'the majority is largely on their side. They'are not afraid of the question, but they do'not care to argue in favor of a matter'which is already decided.'But what folly it is for anybody in Manchester to object to a free bridge between'Richmond and that town! There is not'one single argument against the bridge except that which might be made by the'mules and cows of the town against the'diminution of their commons for grazing.'These animals ought certainly to be admitted to any public meeting in Manchester'against a free bridge, for they are the only'inhabitants of the south side that can have'a good reason for opposing free intercourse'between Richmond and Manchester.'We trust that the good sense of our'Manchester friends will prevail, and that'the number found to favor so antiquated a'system of toll-gatherers on the highway'between the large populations residing on'both Bides of the James river will be not'more than a canoe-load. It should have'been ended forty years since. The impulse now given to the trade and intercourse of the locality leaves no doubt of the'success of the free bridge, and we regret'that any should be so wayward and impracticable as to place themselves on the'side of policies and ideas that should have'died a half century since.</text>
          </elementText>
        </elementTextContainer>
      </element>
      <element elementId="28">
        <name>URL</name>
        <description/>
        <elementTextContainer>
          <elementText elementTextId="62721">
            <text>virginiachronicle</text>
          </elementText>
        </elementTextContainer>
      </element>
    </elementContainer>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="62719">
              <text>1871-03-11</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="62722">
              <text>WioraMegan-18710311-TheFreeBridge.pdf</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="62723">
              <text>Richmond Daily Dispatch</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="62724">
              <text>The Free Bridge</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
