GmManualDocManagementCfg < Gnumed < Foswiki
Description: GmManualDocManagementCfg

## Configuring the document management system

### Document sources

Device detection for image scanning/digitizing devices is handled transparently by a GNUmed module (gmScanBackend). This module wraps the access to the hardware depending on your operating system of choice.

#### GNU/Linux

You need to install and configure XSane. On Debian you will have to install the package `xsane`.

#### MS/Windows

You will have to install and configure the python/Twain bridge as well as the Python Imaging Library.

### Document identifier display (on/off )

After saving a newly aquired document along with its metadata to the database you will by default be presented with a unique identifier for this document. If you don't care about this identifier you might want to turn that off. This can be accomplished by selecting the corresponding option inside GNUmed's setup plugin.

### Printing, faxing, and emailing documents or parts thereof

Printing can be achieved by viewing a part of a document and printing from the appropriate viewer. This will most likely give best results and the widest range of choices in printing options, possible including print-to-fax and print-to-email, depending on the capabilities of the viewer. This, however, becomes rather tedious if you want to print more than one document part at a time.

Those actions can be invoked directly from within GNUmed, too, which can be particularly convenient for processing all parts of a document or even a range of documents at once.

When the user invokes the respective menu items from the document tree GNUmed exports the relevant document's parts into temporary files. The hooks `before_print_doc[_part]`, `before_fax_doc[_part]`, or `before_mail_doc[_part]` are called just before GNUmed executes the shell scripts `gm-print_doc/.bat`, `gm-fax_doc/.bat`, and `gm-mail_doc/.bat` respectively. The scripts are passed a type tag and the names of the temporary files on the command line. It is entirely up to them to take proper action (which also means you can abuse them for whatever purpose you want ). GNUmed does not even delete the temporary files itself (because it knows neither what a script is going to do with a particular file nor when) so your scripts may want to take care of that. The aforementioned shell scripts must be executable and must be found in the PATH of your operating system.