Connecticut has a lot of historical documents of a kind that TEI mavens
have played around with.
My first suggestion would be for the staff of any project to see what they
can learn from the excellent TEI By Example project
(http://tbe.kantl.be/TBE/). I am pretty sure that members of the list
will be happy to answer concrete questions that arise from working through
the tutorials and examples.
I am aware of several projects that you may want to take a look at. The
Office of the Historian at the State Department uses the TEI to encode the
Foreign Relations of the United States. Joe Wicentowski, the man in charge
of this project, uses the eXist database and relies mainly on xquery and a
technology are found at http://en.wikibooks.org/wiki/Xquery and
I believe that the Minnesota Historical Society has played with this
The Colonial and State Records of North Carolina
(http://docsouth.unc.edu/csr/) are a massive, and, I believe, also eXist
based project of digitizing the early 20th-century multivolume print
edition of several centuries of records.
You may also want to look at your direct neighbour to the East, Rhode
Island, a state with a TEI support network second to none anywhere in the
world. Julia Flanders, the director of the Women Writers Project at Brown,
runs a lot of excellent workshops. Julia Flanders and Scott Hamlin, the
director of technology for research instruction at Wheaton College in
Massachusetts, have worked together on a project called TAPAS, which is an
acronym for TEI Archiving, Publication, and Access Service.
On 6/10/11 9:02 AM, "robert foley" <[log in to unmask]> wrote:
>Thanks for your response and assistance.
>I actually live in a large city, the biggest in the state and there is so
>much history! I mispoke by saying "town".
>There has been some work on history issues but not with the text encoding
>initiative and not organized enough and not utilizing digital humanities
>concepts and parameters. In addition, much needs to be investigated.
>Before going forward with reseach, for example, digitizing 18th and 19th
>century shipping logs, and putting historical writings on the TEI format.
>I wanted to get the main library and director involved. And he is on
>board. I meet with him today.
>I am seeking your advice on beginning such a start up.
>I am going to suggest a workshop to learn TEI, using the Oxygen program,
>and a workshop to learn basics of digital humanities, a call for
>archivists and people to encode, and a workshop on how to organize
>history documents and ideas. Please let me know what you suggest.
>On Thu Jun 9th, 2011 11:11 PM EDT Martin Mueller wrote:
>>Dear Robert Foley,
>>We'll be happy to help you, but you need to ask us some more specific
>>questions. I assume that a "town library" is a public library in a small
>>or mid-sized town. The TEI is about encoding texts in ways that will
>>strike many folks as extraordinarily fussy. So the TEI may not be the
>>starting point for getting your feet wet in the world of digital
>>On the other hand, if you have a lot of town history that you want to do
>>justice and you have local historians who want to get it right, the TEI
>>may be just the way to go, and if that is the case, we'll certainly be
>>willing to help.
>>But we need to know a little more about where you are coming from and
>>With best wishes
>>Chair, TEI Consortium
>>On 6/9/11 9:01 PM, "robert foley" <[log in to unmask]> wrote:
>>>Please advise where I can find info on how to begin a start-up digital
>>>humanities department for a town library.
>>>Also are there any issues to be awate of
>>>On Thu Jun 9th, 2011 11:17 AM EDT Kevin Hawkins wrote:
>>>>Let's say you want to create a project-specific schema with only those
>>>>elements needed for your project and as many validation constraints as
>>>>you see fit.
>>>>You could create a TEI customization for your needs using the ODD
>>>>language. One advantage to using the ODD language is that you apply
>>>>principles of literate programming and can easily create schemas and
>>>>documentation in various formats. Another advantage to a TEI
>>>>customization is that you could gain from future improvements made to
>>>>the TEI Guidelines. If your ODD references the TEI's modules and
>>>>classes, any changes made to these by the TEI would be inherited in
>>>>customization if you re-process your ODD using Roma. (Right?)
>>>>But here's where I see as a potential disadvantage to using the TEI's
>>>>modules and classes. If I want to modify my schema in the future, I
>>>>would revise the ODD file and reprocess it using Roma to create a new
>>>>schema. But if I process it with Roma, I risk picking up changes to
>>>>TEI Guidelines that I didn't intend to have included. (Right?)
>>>>To get around this and still get the advantages of literate
>>>>you could use the ODD language to express a tag set for your project
>>>>which does not inherit from the TEI's modules and classes. That is,
>>>>everything is expressed without reference to the TEI, even if you share
>>>>element names and content models for the sake of mutual
>>>>While this would inevitably lead to a divergence of content models over
>>>>time, it seems like a safer way to create a stable tag set.