intranda TaskManager (English)
Documentation overview
  • intranda TaskManager Documentation
  • 1. Introduction
  • 2. What is the intranda TaskManager
  • 3. User interface
    • 3.1. Dashboard
    • 3.2. Searching
    • 3.3. Plugin sections
  • 4. Job plugins
    • 4.1. JPEG-2000-Generation with Lurawave
    • 4.2.Image conversion with ImageMagick
    • 4.3.Generating JPEG 2000 using Open JPEG
    • 4.4.Validation of JPG2000 images with jpylyzer
    • 4.5. Full-text recognition - OCR
    • 4.6. Archiving with Tessella Preservica
    • 4.7. Internet Archive download
    • 4.8. Using intranda AltoConvert to generate ALTO files from ABBYY xml files
    • 4.9. Downloading multi-volume source works from the Internet Archive
    • 4.10. Importing multi-volume source works from the Internet Archive (J-import)
    • 4.11. Validating TIFF images using JHOVE
    • 4.12. Analysing images using intranda LayoutWizzard
    • 4.13. Distributed storage using Storage Balancer
    • 4.14. Generating ebooks in EPUB format
    • 4.15. PDF generation for the Goobi viewer
    • 4.16. Creation of a PDF document for an entire work
  • 5. Further details
Powered by GitBook
On this page
  • Starting the plugin
  • Parameters
  • Operation of the plugin

Was this helpful?

  1. 4. Job plugins

4.1. JPEG-2000-Generation with Lurawave

This plugin sends data to the Lurawave JPEG 2000 converter service.

Starting the plugin

To start the plugin, Goobi issues a command such as the one shown below:

/usr/bin/java -jar /opt/digiverso/taskmanager/bin/TaskClient.jar 
    -itm http://localhost:8080/itm/service 
    -d {imagepath} 
    -s {origpath} 
    -e -i {stepid} 
    -T {processtitle} 
    -t LURAWAVE 
    -n config_rate10.xml 
    -gid {processid}

Parameters

The command parameters are explained in the following table:

Parameter

Possible Goobi variable

Meaning

-itm

http://localhost/itm/service

URL to the intranda TaskManager interface

-e, --returnError

-

If entered, the TaskClient will end with an error code to prevent theworkflow from continuing automatically

-p

0 – 10

Priority to execute this job

-gid

{processid}

Goobi process ID

-i

{stepid}

ID for the workflow step that launches the call

-T, --title

{processtitle}

Goobi process title for which the call is launched

-t, --jobtype

LURAWAVE

Job type

-n, --templatename

config_rate10.xml

Name of the configuration file to be used

-s, --source

{origpath}

Path to the master directory for the process

-d, --destination

{imagepath}

Path to the images directory for the process

Operation of the plugin

When a Lurawave job is generated, the system creates a new folder in the Lurawave service input folder. This new folder is mounted locally (e.g. under /mnt/lurawave/) with the name _temp_(internal ID)_{processtitle}. The configuration file and all TIFF images are copied to the folder. Next, the _temp_ prefix is removed from the folder name. This tells Lurawave to begin the conversion process.

The intranda TaskManager now monitors the Lurawave output folder for a folder of the same name. If it finds this folder, the JP2 images produced are placed in the corresponding sub-folder of the destination folder during the download phase.

Previous4. Job pluginsNext4.2.Image conversion with ImageMagick

Last updated 6 years ago

Was this helpful?