...
Panel |
---|
Born-digital collections present a challenge to traditional ways of describing content and making it discoverable. Disks, drives, directories, etc. may contain many thousands of files which would be difficult to describe in detail in an EAD. The approach described here starts with an EAD that contains only a single reference to the born-digital portion of a collection, expressed as a specific Series within the larger collection. The Forensic Toolkit (FTK) software is used to produce both disk images and related analysis files, plus detailed technical information about individual files on the media. The output of this process is augmented, transformed, and eventually transformed translated into a set of digital objects in DOR (Stanford's Fedora-based Digital Object Registry) and shared objects for Hypatia. A separate process is used for converting the Collection EAD into metadata objects representing the full context of the born-digital and other materials, with links made between the containers and the detailed objects. |
Section | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Sample of the starting lines of the .txt file describing the media object.
...
Each <file> segment will be a the basis of a separate Hypatia Digital Object. This is an example where the atomistic model adds overhead (separate metadata and content objects) and an integrated object combining commonMetadata and genericContent could be considered.
Collection and Series objects
The Collection and Born-Digital Series objects themselves are created first, ahead of FTK processing. All FTK processed materials for a collection are processed together and are members of the Born-Digial Series set. The following information is also contained in a CMnnn.txt file describing a specific disk image
Information from: Disk Image // CMnnn.001.txt | maps to | notes |
---|---|---|
<collection_title>Stephen J. Gould Papers | Collection object | Same as EAD <archdesc><title> |
<series>Series 6: Born Digital Materials | Series set object | Same as EAD series <c><unittitle> |
<note>5.25 inch Floppy Disks</note> | Series Media object | Would correspond to EAD <physdesc> in a node describing the media. |
<callnumber>M1437</callnumber> | Collection object | Same as EAD <archdesc><did><unitid> |
...
Information from: FTK xml // Report_transformed.xml | maps to (within item objects) | notes | ||
---|---|---|---|---|
<filename>BU3A5</filename> | n/a | this is the original file name as it appeared on the original media. | ||
<Item_Number>1004</Item_Number> | n/a | internal FTK reference only, to disambiguate references in the FTK report | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="49b5ead78f8663f8-05882171-4b074f03-a207a3ea-d782d177d5183c3b74aa44b3"><ac:plain-text-body><![CDATA[ | <filepath>CM006.001/NONAME [FAT12]/[root]/BU3A5</filepath> |
| location of file on original media | ]]></ac:plain-text-body></ac:structured-macro> |
<disk_image_no>CM006</disk_image_no> | descMetadata | This token, taken from the head of the <filepath>, is the only data link between the FTK output for a file object and the corresponding media object. We want a data link in descriptive metadata as well as an RDF link to the corresponding object. | ||
<filesize>35654</filesize> |
| Could be used by conversion to compare against the file size as computed locally, a quick check prior to checksum validation? | ||
<filesize_unit>B</filesize_unit> |
| Needed to correctly interpret <filesize>, if used | ||
<file_creation_date>n/a</file_creation_date> | note? |
| ||
<file_accessed_date>n/a</file_accessed_date> | note? |
| ||
<file_modified_date>12/8/1988 6:48:48 AM (1988-12-08 14:48:48 UTC)</file_modified_date> | note? |
| ||
<MD5_Hash>976EDB782AE48FE0A84761BB608B1880</MD5_Hash> |
| Used for checksum validation of a file during processing. This value will eventually be part of contentMetadata, but probably not as a value transferred from here. | ||
<restricted>False</Restricted> |
| true=visible staff only, not discoverable .... Hypatia only | ||
<type>Books</type> | descMetadata | <topic? or <genre>? authority? | ||
<title>The Burgess Shale and the Nature of History</title> | descMetadata |
| ||
<filetype>WordPerfect 4.2</filetype> | descMetadata |
| ||
<Duplicate_File> </Duplicate_File> |
| * blank, null value or empty string - file is unique in collection, no duplicates | ||
<export_path>files\BU3A5.wp</export_path> |
| The file as saved by FTK for further processing. |
...