Sample data is available to use as you try out the service. In some cases samples such as manifest and erc files may be useful as examples for formatting your own Merritt files. All of the sample files below are available as a zip file from http://merritt.cdlib.org/samples/samples.zip
|Sample type||File name|
|Container file objects||
huskyChicken.zip (object has 3 files)
outdoorStore.zip (object has 8 files)
souvenirs.zip (object has 2 files)
brain_v1.zip (object has 4 files)
brain_v1.tar (object has 4 files)
brain_v1.tar.gz (object has 4 files)
brain_v2.zip (object has 5 files)
brain_v2.tar (object has 5 files)
brain_v2.tar.gz (object has 5 files)
jazzbears.zip (object has 2 files)
(pointing to multi-file objects)
Using the Sample Files to Demonstrate Manifests
The merrittManifest.xls file that contains the macros needed to generate a manifest also contains sample worksheets for objects and each kind of manifest. The objects referenced in those worksheets are all included in the samples.zip file and are posted on Merritt for you to use. (If you run the macro to produce a manifest from the sample worksheets, the sample objects are already posted on a server to add).
Using the Sample Files to Demonstrate ERC files
The jazzbears.zip file contains both a .tif image and a mrt-erc.txt file. The mrt-erc file contains the following metadata:
erc: who: (:unkn) unknown what: Jazz for the bears when: 1920-1932 where: 2001697390
Submit this object as a container file to see that Merritt extracts the mrt-erc-txt metadata.
Using the Sample Files to Demonstrate Versioning
The "brain_v1" and "brain_v2" sample files will demonstrate both object versioning and will show you how different kinds of container files can be used to submit content to Merritt. The .tar, .zip and .tar.gz file sets are independent of one another; they each include the same files:
v2 of the tar, gz and zip containers add another file: brain.tif
To demonstrate container formats, submit any of the files to see that they are unpacked upon ingest.
To test versioning, be sure to provide a local identifier, for version 1, then provide the same local identifier for version 2.