+++ FOR TESTING PURPOSES - NOT YET RELEASED FOR PRODUCTION +++
In order to ensure that an electronic submission can be technically processed a technical validation of an electronic submission is recommended. ECPA supplies a validation engine called eSubmission validator that is capable of validating both CADDY-xml and GHSTS dossiers.
The validation engine can process predefined test configurations that are loaded into the validation engine and can be selected by the user.
- Download page for current eSubmission Validator version
- Download page for outdated eSubmission Validator versions
Test configurations for technical validation
A test configuration is a set of tests to be performed on a submission package. There are different test types than can be part of a test configuration:
- Tests on the XML backbone of the submission
- Tests of the submission package structure
- Tests on the content (MD5 checksum and PDF/A-1b validation)
Please open the eSubmission validator for more details about the available technical test configurations. By default the eSubmission validator will check online for newly available technical test configurations. If you work from an Intranet you may need to provide proxy settings to run the update. Please contact your local IT support.
CADDY-xml test configurations (as of February 2019)
|Test configuration Name||Version||Description|
|Complete||01.01.00||Complete check - Consists of the checks ob the XML backbone, file system, MD5 and PDF/A checks (using Apache PDFBox for validation)|
|Partial||01.01.00||Partial check - same as "Complete" test configuration, but without PDF/A-1b validation|
|01.01.00||Partial check - checks all attached PDF for PDA/A-1b compliance (using Apache PDFBox for validation)|
As PDF/A-1b validation is by far the most time-consuming part of a validation, there is the possibilty to do either a Partial check without PDF/A validation or only check for PDF/A compliance, when e.g. rechecking with modified PDF content only.
GHSTS test configurations
As of now (12/2018) there are not yet any agreed technical validation rules for GHSTS available. Some test validation rules are available for demonstration purposes, please contact the technical support if you are interested.
Proprietary test configurations
Industry and authorities may define additional validation rules that control specific business constraints. The test configurations use the standard validation language Schematron. Industry and authorities can adapt and extend the existing test configurations to test additional business constraints and put those validation rules on own intranet test configuration repositories. If you want to use the eSubmission validator for such business validation purposes please contact the technical support.
The eSubmission validator has the following main functionality:
- Select applicable test configuration and run validation
- Save a validation report in HTML, PDF or XML format
- Get detailled validation error information on test level and issue level
- Check for and download available test configurations from the online test configuration repository
- Possibility to supply test configurations as ZIP files in case when no internet connection is available
- Saving information from grid for test and issue information to CSV
- Configuration of different user settings
Installation and runtime requirements
The eSubmission validator runtime does not need adminsitrative installation rights. Please download the zip file, extract at an appropriate location and click on "eSubmissionValidator.exe" to start the program. The program requires a 32bit Java runtime (JRE 8 or above) to be installed on your system.
The eSubmission validator is also available as a server-side component without GUI that can be integrated into publication and ingestion workflows. If you want to integrate the validator into an existing environment please contact the technical support.
PDF/A-1b validation components
The eSubmssion validation engine can use one of two PDF/A-1b validation components:
The two validation components have a different validation model and hence can produce different errors. There are currently Pro's and Cons for the validation engines. The Apache PDFBox component has proven to be more stable, with better runtime and fewer memory consumption.
Please see e.g. https://github.com/veraPDF/veraPDF-library/issues/956 for a discussion of difference. For details on how to use the two validation components please contact the technical support.