andrew said:
So where to go from here? With our current set-up, to merely generate a list of these and submit them as corrections would be somewhat overloading our volunteers.
sounds like you need some better tools. or, even better yet, a thorough revamping of your error-detection and error-correction processes... you need to have a system that runs a test like this, then automatically summons the scans and the e-text, side-by-side so you can make a decision on the matter -- one small matter here, you need to do the scans -- and then lets you click a button that will automatically make the change, and generate everything necessary, like an updated change-log, new derivative versions, a post message, e-mail to that e-text's listserve, etc. by the way, a subset of this system -- the part that calls up the scan and the text for a comparison -- is what the public can use to verify an error-report. although you'd want to do these tests proactively, it also never hurts to let end-users help you out... in a post to this listserve from maybe 6-9 months ago, i detailed the complete architecture for such a system. the message was ignored. perhaps it should be revisited. -bowerbird