Members of the Digitizers group digitize score pages, create encoded derivative files, generate metadata, and load it into Variations. To turn on the Digitizer interface (if authorized to do so) set the property dml.login.digitizerMode to true in the client's dml.conf. The filenaming scheme used by Variations can be configured in dmlserver.xml.
There are three options for server processing of incoming score images: minimal, djvu processing, and none. Minimal score processing will copy the files from the incoming directory to where Variations can use them and update necessary metadata. This approach requires the derivative files placed in the incoming directory to already be djvu files that can be opened in Variations. DjVu processing will convert the incoming tiff file to a pbm and then encode those to djvu files that are useable by Variations. This mode should be used if the DjVu Encoder described below is not used. Enabling djvu processing requires the djvuProcessing attribute be set to true in dmlserver.xml. If the DjvuProcessing tag is not present, then no processing will be done by the server (this approach is not supported for test sites). outputDir, an optional attribute, is the path to the directory where Variations will place the deliverable files. If an output directory is not specified, Variations will determine this location by looking at the filesystem usage statistics for each LeaseManager's ContentDir of a LeaseResource that matches the contentType "score".
<ScoreProcessing incomingDir="/home/dmlserv/content/loader/score/incoming/" tempDir="/home/dmlserv/content/loader/score/temp/" djvuProcessing="false" />
The filename scheme used by Variations is specified through the FilenameScheme tag in dmlserver.xml. See Filenaming Schemes for more information on possible settings.
More information the standalone GUI encoder that uses DjVuLibre's djvu encoder can be found here.
An overview of the entire digitization process can be found here