Validation Connectors
- Alexis Rombaut
This optional feature is part of version 25.2 and is subject to change
Introduction
The purpose of validator connectors is to allow for selective validation of certain https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4340187164 by checking their validity and optionally their adherence to certain profiles (for example a PDF validator that only allows PDF 1/A files).
Configuration
A validation connector has the following additional properties beyond the general Module Plugins | Properties
Property | Description | Default | Required | Example |
|---|---|---|---|---|
Formats |
| [ ] | No | [“x-fmt/387”, “x-fmt/388”, “x-fmt/399”] |
Premis event type | The premis event type to generate for finished validation |
| No |
|
Workflow
During the Ingest Flows of the object, a new validation step is added that does the following
Obtain the list of validation connectors that apply to the object (based on whether the module plugin is active for the organisation and applies to the source pronom format)
For each validator
Call the validator using the connector Validation Connectors | API Contract asynchronously
For each validator
Asynchronous wait for the validation to complete
Collect the response of the validator connector
Log the result of the validator as one of the Events (include both positive and negative evaluations)
If at least 1 validator declared the object invalid, reject the object as a whole
The validation connectors work asynchronously because the validation can potentially take a long time to complete.
Schematic
API Contract
API | Method | Purpose | Properties |
|---|---|---|---|
Validation Connector API |
| Starts the asynchronous validation of the object. Instantly returns the |
|
REST API |
with status Requires function TBD |
|
|