December 2006


This is a Historical Podcast to describe Pickett’s Charge at Gettysburg. The First part should be played on Seninary Ridge, near the Virginia or North Carolina Monuments.

The Second part should be played as the listener walks the 1 mike path from Semninary Ridge to Cemetary Ridge, from the Virginia Monument to “the Angle” 

http://www.oncombat.org/Clio%20Wired/gettysburg1.mp3

http://www.oncombat.org/Clio%20Wired/gettysburg2.mp3

For a map, please refer to the West Point Atlas of American Wars at:

http://www.dean.usma.edu/HISTORY/web03/atlases/american%20civil%20war/acw%20pages/acw37.html

I hope you make the trip: Enjoy!

A very promising approach to my digital archive would be the use of a database to store primary sources and metadata from the contributors. The advantages of a database over a wiki are promising: the database would be structured, allow sorting, and with work–allow exporting to mashups. The use of  chronological and geographical mashups would enable integration of all the materials on a map and timeline. These resources would make browsing more effective and intuitive vs a “hunt and peck” approach to searching the database.

Here are the Desired Data Fields:

  • Date of Mission

  • Type aircraft

  • Position in formation (lead/wingman/solo)

  • Other aircraft in the mission

  • Unit (squadron/Wing)

  • Location of action (geo-tag)

  • Takeoff base/landing base

  • Mission type

  • Narrative/description of the mission

  • Resources: cockpit video/audio/photos/map

I built a database with most of these fields in lazybase to learn how the database might work. I input a few missions I flew in Desert Storm to test it.

http://lazybase.com/dbhome?a=797442748 I suggest you search for “F-16”

I quickly found Lazybase was very limited in its field choices–I wanted to put latitude/longitude formatted to use in a mashup, but had to enter it as text. This will lead to format problems with the geo mashup, indicating a more capable database is needed (until lazybase adds geo-tags).

The second learning point I encountered was I need to decide if the artifacts will reside inside the database (uploaded there) or linked from the database. Lazybase doesn’t accept files, so I uploaded the files to my server space and included links.

I found that a few additional fields that might help include: a short description of main mission events (to help search/browse), names of other aircrews on the mission.

Another limitation of Lazybase that would have to be adjusted with a more capable database is that editing privileges are “all or nothing” Either you have editing privileges and can change all the records, or you can only view them. Ouch. If I give you the opportunity to put in your mission, I have to give you the option to delete the whole database.

In the end, the database exercise was an excellent learning opportunity, but makes the case to go for a more capable database.