...
A HypatiaDiskImageItem has a payload file that we store in the "content" datastream of a FileAsset object. However, it also has several other files. Here you can see a datastream called "front" that contains a photo of the disk in question. If the back of the disk had also been photographed, there would also be a datastream called "back." I'm also planning to put the .csv and .txt files that FTK generates as datastreams here. That seems more appropriate (and easier) to me than handling them as separate FileAssets, but we may want to re-examine this in later phases of the project.
Next steps:
- Adding relationships to the collection object, so we can easily see all of the files connected to a collection.
- Running this processing against other FTK collections.
- Creating HypatiaItem objects for files described in EAD, which will follow the same datastream patterns described here, but will probably need some customization.
Questions:
- Do we want to pull information from the collection into any of these objects. I notice there's nothing in these that says they're from the Stephen Jay Gould archive. Of course that can show up in the interface without the data being in the object. On the one hand, including that information is more work and creates a dependency on having a collection object first before the FTK objects are created. On the other hand, it seems like a good idea to provide a bit of context in these objects, but I don't have a sense of how important that is.