Processing Service for the DSpace IIIF Search API

This service retrieves and pre-processes a DSpace Item's OCR files for indexing by the solr-ocrhighlighting Solr plugin. OCR files are retrieved from DSpace using the DSpace IIIF integration.

DSpace: https://wiki.lyrasis.org/display/DSDOC7x

solr-ocrhighlighting plugin: https://github.com/dbmdz/solr-ocrhighlighting.

Features

• Supports GET, POST, and DELETE methods
• Automatically detects the OCR format (ALTO, hOCR, MiniOcr)
• Supports "full" or "lazy" indexing as required by configuration.
• Converts hOCR and ALTO files to MiniOcr if required by configuration.
• Updates OCR page identifiers to align with canvas identifiers (based on DSpace Bundle order or METS file).
• For ALTO only, detects and converts inch1200 and mm10 units to pixels.
• XML-encoding of Unicode characters if required by configuration.
• Tests for whether OCR files for a DSpace Item have already been indexed via the GET method.
• Remove OCR files for a DSpace Item from the index, and from the file system if "lazy" indexing was used.

Configuration Options

• http_port: listen port of service
• ip_whitelist: IPs that are allowed access
• dspace_host: Base URL of the DSpace service
• manifest_base: Base URL used for Manifest ID (can be the same as the dspace_host)
• solr_url: Base URL of the Solr service
• solr_core: Solr core ("word_highlighting")
• miniocr_conversion: Convert OCR to MiniOcr format
• index_type: Full or lazy
• escape_utf8: XML-encoding of unicode characters
• xml_file_location: Path to OCR files (when "lazy" indexing used)
• input_image_resolution: The default DPI for ALTO unit conversion
• verbose_logging: Log additional information during processing
• log_dir: Path to the log directory

Requirements

• Go 1.16.15+ (if you are building your own binary and not using a distributed version)
• DSpace 7+
• Solr OCR Highlighting Plugin v0.7.2+

Overview

The service works in conjunction with DSpace 7.x IIIF support.

When indexing a new item, the service retrieves an IIIF AnnotationList of OCR files from the DSpace Item record. The OCR files are pre-processed based on configuration options and added to the Solr index. If "lazy" indexing is used, OCR files are written to disk.

Processing order is determined either by METS metadata or the order of OCR files in the DSpace bundle.

This service can be ran on the same host as Solr to support "lazy" indexing. If you are using "full" indexing or providing a shared file system by other means the service can run on a separate host

External Requirements

You must add the solr-ocrhighlighting plugin to Solr. See the instructions: https://dbmdz.github.io/solr-ocrhighlighting/installation/

You need an IIIF-enabled DSpace instance. Your DSpace Items must be individually enabled for IIIF and search via the metadata fields dspace-iiif-enabled and iiif-search-enabled. The Item's OCR files must be in the DSpace Item's OtherContent Bundle. If your processing order is determined by METS metadata, be sure to name your structural metadata file mets.xml. If this file does not exist or has not been correctly named, processing order is determined by the order of OCR files in the OtherContent Bundle.

See DSpace IIIF documentation: https://wiki.lyrasis.org/display/DSDOC7x/IIIF+Configuration

Installation

Solr Core

Add the word_highlighting plugin to your Solr cores. DSpace 7.x may eventually include a starter core for you to use. In the meantime, see the solr-ocrhighlighting documentation for more details.

Binary Executables files and Sample Configuration:

Archive files for various platforms are provided in the Release List.

You can also build from source.

go build -o /output/directory/<filename> main.go

For a specific platform:

env GOOS=<target-OS> GOARCH=<target-architecture> go build -o /output/directory/<filename> main.go

Using Docker

Pull from Docker Hub:

docker pull mspalti/ocr_processor:latest

Example of running the container with volumes (Linux).

docker run -d -u <host_user_GID> --network host --name ocr_processor -v /host/path/to/config:/processor -v /host/path/to/log:/var/log/ocr_processor -v /path/to/ocr_files:/var/ocr_files mspalti/ocr_processor

Note that you don't need to create a volume for the /var/ocr_files mount point if you aren't using "lazy" indexing.

If using SELinux security you may need to add :Z to your mount point paths, e.g. /indexer/logs:Z

On MacOS or Windows you can't use the --network host option. Instead, change DSpace and Solr URL's in config.yml to use the IP address of the host system rather than localhost. This appoach works only for "full" indexing.

Usage

POST, DELETE, or GET requests use the identifier of a DSpace Item as follows:

http://<host>:3000/item/413065ef-e242-4d0e-867d-8e2f6486be56

• GET returns 200 if the DSpace Item is in the Solr index and 404 if it has not yet been added.
• DELETE removes all Solr index entries for the DSpace Item and OCR files from disk for "lazy" indexing.
• POST adds all OCR files for the DSpace Item to the index.

DSpace command line tool (under development)

A DSpace CLI tool is being considered. That tool uses this service to add or delete OCR from the Solr index. The CLI tool allows batch updates at the Community or Collection levels, as well as individual Item updates.

Usage:

Add: ./bin/dspace iiif-search-index --add -e user@dspace.edu -i f797f6ee-f27f-4548-8590-45d6df8a7431

Delete: ./bin/dspace iiif-search-index --delete -e user@dspace.edu -i f797f6ee-f27f-4548-8590-45d6df8a7431