= Results = We reached our goals (sort of, and only one day late)! * 'RIFF' is integrated in the ingest package and referential checking is activated. * The object specifications have not been updated, but [[Ingest 2 experiences]] contains the experiences and questions that was a result of sample object creation. * Three packages with sample objects have been created. See below. == Example Ingest Objects == The directory [[http://hera.statsbiblioteket.dk/cgi-bin/viewcvs.cgi/DOMS/Ingest/test/dk/statsbiblioteket/doms/ingest/data/ingest2Test/|ingest2Test]] contains three example ingest directories: The directory [[http://hera.statsbiblioteket.dk/cgi-bin/viewcvs.cgi/DOMS/Ingest/test/dk/statsbiblioteket/doms/ingest/data/ingest2Test/logo1/|logo1]] contains a 'complete' ingest example, i.e. this example can be ingested into an empty Fedora repository, as no objects are assumed to exist. The directory [[http://hera.statsbiblioteket.dk/cgi-bin/viewcvs.cgi/DOMS/Ingest/test/dk/statsbiblioteket/doms/ingest/data/ingest2Test/logo2/|logo2]] contains a 'dependant' ingest example, i.e. the logo1 example is assumed to be in the Fedora repository, as the objects in logo2 have relations to objects from logo1. The directory [[http://hera.statsbiblioteket.dk/cgi-bin/viewcvs.cgi/DOMS/Ingest/test/dk/statsbiblioteket/doms/ingest/data/ingest2Test/logo3/|logo3]] contains an invalid dependant ingest example and should fail the RIFF check (the file object contains an 'isFiletype relation' to a non-existing 'png filetype object'). == JUnit Test == The methods 'testIngest2Success', 'testIngest2RIFFFailure' and 'testIngest2FedoraFailure' in [[http://hera.statsbiblioteket.dk/cgi-bin/viewcvs.cgi/DOMS/Ingest/test/dk/statsbiblioteket/doms/ingest/IngestTest.java|IngestTest.java]] should test that the two first directories above can be ingested (in the right order), and that the third directory fails the RIFF check, and demonstrate that passing the RIFF check does not guarantee a consistent repository as the repository may fail 'at the wrong time' (the 'setUp' method sets up the test files and removes any test objects from the Fedora repository; the 'tearDown' method tears down the test files and also removes test objects from the repository).