Date: Thu, 28 Mar 2024 07:26:56 -0400 (EDT) Message-ID: <550347702.27491.1711625216316@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_27490_1274765940.1711625216316" ------=_Part_27490_1274765940.1711625216316 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Work in progress
=Under construction
ECM documentation
needs migrating from SourceForge to here
Fedora validates objects on ingest using XSD schema validation and Schem= atron validation.
Fedora's validation mechanism is configurable, allowing the implementati= on of custom validation mechanisms for objects being ingested, and for vali= dating Fedora objects when they are modified.
XSD schema and Schematron validation is performed on all objects when th= ey are ingested. By providing your own implementation of the DOValidator mo= dule and specifying this in fedora.fcfg it is possible to implement custom = XML validation mechanisms.
By default both XML schema and Schematron validation is performed. This = is configurable. To alter the validation performed on ingest add a paramete= r to the DOManager module configuration in fedora.fcfg:
<= ;param name=3D"ingestValidationLevel" value=3D"0"/>
The value of this parameter specifies the type(s) of validation to perfo= rm on ingest:
If this parameter is not specified the default level is 0.
Use with care!
= span>Fedora's XML ingest validation is designed to help ensure the integrity = of your repository. Exercise caution if you are implementing your own valid= ation mechanisms, and only change the validation level from the default if = you can ensure that objects are valid prior to ingesting them.
If Fedora's logging level is set to DEBUG, Fedora also validates the XML= object representation before committing it to permanent storage using both= XSD and Schematron validation. This feature is intended to be used for tes= ting Fedora.
Fedora Object validation is carried out prior to any object modification= s being committed to permanent storage - if a modification would result in = an invalid object according to the configured validators, the modification = is not made and an error is reported.
By default, Fedora's configuration is to perform no object validation up= on modification operations.
In addition, objects can be validated on demand using the validate API m= ethod. This will validate objects according to their specification using Enhanced Content Models.<= /p>
Digital Object validation is configured using Spring, in the file =
$FEDORA_HOME/server/config/spring/doobjectvalidator.xml
.
Digital Object validation can be used to ensure that repository content = conforms to the rules specified using Enhanced Content Models, which allows specification via an o= bject's content model of XML datastream schema and relationships that shoul= d exist between objects.
To enable ECM object validation for every modification made to an object= , uncomment the relevant sections in this file.
You can define your own validators for objects by writing Java classes t=
hat implement the org.fcrepo.server.validation.DOObjectValidator interface, and then adding these to the
doobjectvalidator.xml Spring configuration file.
Extra validation will impair performan= ce
Although performing validation of Fedora objects on every modification c= an be used to help ensure the integrity of your repository, adding such val= idation operations will incur an overhead every time an object is modified.=