Skip to end of banner
Go to start of banner

Validation Connectors

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 10 Next »

This optional feature is part of version 25.2 and subject to change

Introduction

The purpose of validator connectors is to allow for selective validation of certain /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 https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4438884395/Module+Plugins#Properties

Property

Description

Default

Required

Example

Formats

  • The list of pronom formats for which to call this validator

  • An empty list implies all formats

[ ]

No

[“x-fmt/387”, “x-fmt/388”, “x-fmt/399”]

Premis event type

The premis event type to generate for finished validation

VALIDATION

No

VALIDATION.PDF

Workflow

During the Ingest Flows of the object, a new validation step is added that does the following

  1. 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)

  2. For each validator

    1. Call the validator using the connector https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4763779092/Validation+Connectors#API-Contract asynchronously

  3. For each validator

    1. Asynchronous wait for the validation to complete

    2. Collect the response of the validator connector

    3. Log the result of the validator as one of the Events (include both positive and negative evaluations)

  4. 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

POST /validate

Starts the asynchronous validation of the object. Instantly returns the 200 OK to confirm the reception of the validation request.

  • The execution ID of the ingest workflow that is suspended

  • The metadata of an object

  • The URL of the original representation

Engine workflow API

POST /asynchronous/<execution-id>

Resume the asynchronously paused workflow and provide the validation result

  • The message (the validation message)

  • The job status (the validation result)

  • Custom properties

  • No labels