Brief outline of specifications to validate a Fedora 3 to OCFL migration. The validationv validation tool should begin with coarser tests, then progressively handle finer-grained tests.
Valid: number of objects in the OCFL repository is equal to the number of objects in the Fedora 3 repository
Validate: object IDs
Valid: every object in the OCFL repository has the same ID as its corresponding object in the Fedora 3 repository.
- label state (lower priority if it is not trivial)
Note that Fedora 3 content models will be verified as part of the examination of the RELS-EXT datastream (lower-level validation).
F3 Type Key = ("I" - Inline, "M" - managed "E" - external, "R" - redirect)
- size : M only (certainly)
- mimeType (* hold off on this one)
- state (lower priority if it is not trivial)
- identifier (DSID)
- externally referenced content (URI) (Type E and R only)
Validate: datastream size size
F3 managed (type "M") datastreams ONLY ((ie not inline XML):
Valid: the size of the version of the datastream in OCFL matches the size of the datastream on disk in the Fedora 3 repository repository
Valid: the size of the version of the datastream in OCFL recorded in
<DSID>.nt matches the size of the OCFL file on disk
Validate: datastream checksum
Only validate the most recent version
Command line flag for disabling non-head version checks.