<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Verdana;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Garamond;
        panose-1:2 2 4 4 3 3 1 1 8 3;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal;
        font-family:"Garamond","serif";
        color:windowtext;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><span style='color:#1F497D'>The AMX system will work for
that, but it is cumbersome as well, as you have to enter all the data.  I think
no matter what you come up with, you are going to have a cumbersome system.<o:p></o:p></span></p>

<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>

<p class=MsoNormal><span style='color:#1F497D'>I am keeping simple records in
an excel database, it seems to work for us.  My conversion clerks write down
how much time they spend on each particular aspect (scanning, ocr,
text-cleanup) to the nearest 15-minutes.  It gives me a pretty good read on how
long it takes to convert things, although I don’t really care as much about the
little parts as I do the big picture.  Our goal here is a 4-day turnaround, and
if we make it within four days I’m happy, five days I’m satisfied, any more
than that and I’m looking to see where we can improve.<o:p></o:p></span></p>

<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>

<p class=MsoNormal><span style='color:#1F497D'>I will be presenting a lot of the
information on how we do this here at the Accessing Higher Ground conference in
Boulder in November.  Hope you can make it, it will be a worthwhile lecture.<o:p></o:p></span></p>

<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>

<div>

<p class=MsoNormal><i><span style='color:#1F497D'>Susan Kelmer<o:p></o:p></span></i></p>

<p class=MsoNormal><i><span style='color:#1F497D'>Adaptive Technology
Specialist/<o:p></o:p></span></i></p>

<p class=MsoNormal><i><span style='color:#1F497D'>Lab Coordinator, Campus Labs
and Classrooms<o:p></o:p></span></i></p>

<p class=MsoNormal><i><span style='color:#1F497D'>St. Louis Community College -
Meramec<o:p></o:p></span></i></p>

<p class=MsoNormal><i><span style='color:#1F497D'>314-984-7951<o:p></o:p></span></i></p>

</div>

<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>

<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>

<div>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
athen-bounces@athenpro.org [mailto:athen-bounces@athenpro.org] <b>On Behalf Of </b>Balen,
Tim<br>
<b>Sent:</b> Thursday, August 14, 2008 8:33 PM<br>
<b>To:</b> athen@athenpro.org<br>
<b>Subject:</b> [Athen] Information on E-Text Production Database?<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p> </o:p></p>

<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif"'>Colleagues,<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif"'><o:p> </o:p></span></p>

<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif"'>I’m
looking for advice or suggestions on creating a database for tracking e-text
production.  We are working on one now within our office, but I am
concerned it is becoming cumbersome and labor intensive.  Essentially we
are looking to record and store, completed text conversions, conversions in
progress, time spent per conversion & per editor.  Any information
would be appreciated on or off the list.<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif"'><o:p> </o:p></span></p>

<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif"'>Thank
You!<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif"'><o:p> </o:p></span></p>

<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana","sans-serif"'>Tim
Balen<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:8.0pt;font-family:"Garamond","serif"'><o:p> </o:p></span></p>

<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana","sans-serif"'>Washington
State University<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana","sans-serif"'>509-335-7904<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Verdana","sans-serif"'>www.drc.wsu.edu<o:p></o:p></span></p>

<p class=MsoNormal><o:p> </o:p></p>

</div>

</div>

</body>

</html>