Skip to end of banner
Go to start of banner

Validator 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 2 Next »

This optional feature is part of version 25.2

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.VERA-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/Validator+Connectors#API-Contract

    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)

  3. If at least 1 validator declared the object invalid, reject the object as a whole

API Contract

TBC

  • No labels