4.8. Using intranda AltoConvert to generate ALTO files from ABBYY xml files

The intranda TaskManager allows Goobi to outsource the CPU-intensive job of generating ALTO files (including recognition of running heads and page numbers) to external servers.

Starting the plugin

The following instruction is required if you wish to call intranda AltoConvert from an individual step in the workflow:

/usr/bin/java -jar /opt/digiverso/itm/bin/TaskClient.jar 
    -itm http://localhost:8080/itm/service 
    -s {tifpath} 
    -d {processpath}/ocr/{processtitle}_alto/ 
    -gid {processid} 
    -i {stepid} 
    -T {processtitle} 
    -n altoconvert


The command parameters are explained in the following table:


Possible Goobi variable




URL to intranda TaskManager interface

-e --returnError


If this parameter is met, the TaskClient will end with an error code to prevent the workflow from continuing automatically


0 – 10

Priority to execute this job



Goobi process ID



The workflow step ID that launches the call

-T, --title


The Goobi process title for which the call is launched

-t, --jobtype


Job type

-n, --templatename


Name of previously generated configuration file

-s, --source


Path to media directory for the process

-d, --destination


Path to the ALTO directory to be created in the process

Operation of the plugin

Once the ALTO files have been generated, TaskManager will move them automatically to the target directory specified in the instruction to the TaskClient. Successful completion of the job is recorded in the process log, and the automated workflow step is concluded via API..

Last updated