The basic recipe for testing the import/export utility and import/export verification tool follows:
- Start up an empty Fedora
- Load or /fcr:restore a dataset
- Export the all or some of the dataset with the import/export utility
- Verify the export with the verification tool
- Start up a new Fedora (same or different port and context)
- Import the exported resources with the import/export utility
- Verify the import with the verification tool
Variations
The above recipe can be varied in the following ways:
- For #2: In addition to custom, scripted ingest datasets, the "additional_datasets" are available for /fcr:restore
- For #3: All of the configuration options should be tested
- With and without binaries (-b)
- Using
defaultandaptrustbagit profiles - Using inbound references (-i)
- Using membership predicates (-p)
- Overwriting tombstones (-t)
- With authorization (-u)
- Exporting external content (-x)
- For #5: Start up the destination Fedora on a different port and with a different context, example
- For #6: Use both the command line options and the auto-generated config file
Tests
| Tester | Fedora Version | Import/Export Version | Verify Version | Dataset (detail below if custom) | Export Options | Export Verify Options | Source Fedora port & context | Destination Fedora port & context | Import Options | Import Verify Options | Success? | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Jim Coble | 4.7.2 | 0.1.1-SNAPSHOT-d4780ca2 | master branch at839cb8b | Small portion of production-like data loaded locally via Hydra framework | -c (config file contains -m export, -b, -p ldp#contains, -r, -d, rdfLang text/turtle) | none except config file | 8984/rest | 8984/rest | -c (same config file as used for export except for -m import) | none except config file | mixed – no errors on export or import - export verify successful, import verify mismatches (expected due to server-managed triples) | Exported entire repo; wiped repo; imported entire repo |
