This page describes the setup of a Google Cloud based OCR setup for use with the Extended DMS environment. DMS will issue commands so that documents to be OCR'ed are uploaded to Google Cloud, OCR is performed there, and the result is returned. The advantage is that the DMS appliance's resource (CPU, RAM) is not consumed by the OCR processing and that OCR takes advantage of the high accuracy and potential speed of the Google Cloud Vision technology.
Note that the Google Cloud service is not free of charge an requires an active Google Cloud account. See: https://cloud.google.com/vision/pricing
The below instructions describe the setup of the DMS host machine. Using this OCR method will not affect performance of the DMS service in a significant way; the scripts involved are only making calls to the Google Cloud API and relay documents/return information, however, they do not perform any processing of the documents.
Create 2 permanent environment variables. For example, add the following 2 lines to /etc/environment
:
GCLOUD_OCR_BUCKET=<$gcloud_storage_bucket_name> GOOGLE_APPLICATION_CREDENTIALS=<$path_to_json> |
replace <$gcloud_storage_bucket_name> and <$path_to_json> with their resective values.
Download pi-gcloud-ocr.jar (Link will be provided after successful testing) and copy it to /opt/pi-gcloud-ocr.jar
of the DMS VM host machine.
Copy the below "pi-google-ocr" script to /usr/bin/
of the DMS VM host machine and make it executable (chmod +x). This script contains the commands to drive the OCR process for each file.
/<storagepath>/nuxeo/scripts/
and make it executable (chmod +x). This script contains the commands to access pi-google-ocr script from inside the DMS.<<adminuserhome>>/.ssh/authorized_keys
file of DMS host vm~/.ssh/
to /<storagepath>/nuxeo/ssh/
~/deploy/config/
)#!/usr/bin/env bash gsutil cp "$2" gs://${GCLOUD_OCR_BUCKET} input_filename=$(basename $2) output_filename=$(basename $1) json=$(java -jar /opt/pi-google-ocr.jar gs://${GCLOUD_OCR_BUCKET}/${input_filename} gs://${GCLOUD_OCR_BUCKET}/${output_filename}) echo "$json" > "$1" gsutil rm "gs://${GCLOUD_OCR_BUCKET}/${input_filename}" gsutil rm "gs://${GCLOUD_OCR_BUCKET}/${output_filename}output-1-to-1.json" |
piocr script
#!/bin/bash echo "variables $1 $2" ssh <<adminuser>>@<<dms.host.name>> "pi-google-ocr $1 $2" |
$1 is the path and filename of the output file, $2 is the path and filename of the input file that are handed over when the DMS calls the piocr script. The command in piocr script must be such that the OCR engine reads the input file (pointed to by $2) and writes to the output file (pointed to by $1).
Make sure you replace <<adminuser>> with correct user name of an administrative user in OCR appliance, and <<dms.host.name>> with proper FQDN or IP address.
"elif [ ${1} = "NUXEO" ] then"
) so as to be added the container run command.:add_volume "/<storage_path>/nuxeo/ssh" "/home/nuxeo/.ssh" add_volume "/<storage_path>/nuxeo/scripts/piocr" "/usr/local/bin/piocr" |