BK-L Archives

Archiver > BK > 2005-03 > 1111532478


From: "David" <>
Subject: Re: [BK] Attaching supportive documents to a BK DB
Date: Tue, 22 Mar 2005 16:01:18 -0700
References: <6.2.1.2.2.20050322095643.024404b8@pop.rcn.com> <424163da.1044765@smtp.schmerse.de> <6.2.1.2.2.20050322142538.02441350@pop.rcn.com>


Hi Paul;
If you want to save the scanned documents as a text file, you can use OCR
software to convert the picture to a text document. OCR (Optical Character
Recognition) software has gotten much better recently, however, it still is
far from perfect. After the document has been scanned and converted, you
then have to check the document with your word processor and make the
necessary corrections to the errors that OCR has created. Some times the
correction process can take more time than typing the whole document. It
depends on the quality of the original paper, your scanner, and your OCR
software.

After the whole process is complete, you can rename the document and put it
into the TEXT folder below your data folder and then attach it to the person
in your database.

Scanners sometimes come with OCR software included in the package.

Is this what you had in mind?

Good luck
DavidMcC

> The problem is that while photos can be scanned into "Pictures" files,
> using .jpg for .gif formats, text documents apparently cannot be scanned
> into BK's "text documents" folder using .tif or any other format. BK's
> definition of "text documents" appears to be restricted to texts which are
> TYPED from the keyboard (e.g."Notes"), not scanned from a scanner. Or if
> they indeed can be scanned (i.e. routed from the scanner to a particular
> file name), I'd like to know the exact procedure for attaching scanned
> .tif text documents to individuals in BK.
>
> What I want to avoid is seeing scanned text documents show up as
> "pictures" in the "pictures" folders, which I prefer to reserve for
> pictures of people. In short, keep separate scanned documents and scanned
> pictures, but have either attachable to specific persons.
>
> Thanks.
>
> Paul O'Bannon

This thread: