...
Section | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Each <file> segment will be a the basis of a separate DOR/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. Media objects must be linked to the appropriate series via an isMemberOf relationship.
Media objects
The FTK processing must first create a set of media objects representing the physical media (hard drive, diskette, etc) on which the files were found. This has been described as a view of the "unprocessed" collection, meaning it has not been processed down to the individual units of content, the separate files. The following information is also contained in a CMnnn.txt file describing a specific disk image:
Sample of the starting lines of the .txt file describing the media object.
Panel |
---|
Created By AccessData® FTK® Imager 3.0.1.1467 110406 Case Information: |
Note that some of this information is repeated as header information in the file-level FTK report below.
From: Disk Image // CMnnn.001.txt | maps to | notes |
---|---|---|
Evidence Number: CM004 | descMetadata | Would correspond to EAD <c><unittitle> |
Notes: 5.25 inch Floppy Disks | descmetadata | Would correspond to EAD <physdesc> in a node describing the media. |
(implied) | RELS-EXT | A link to the Collection object |
(implied) | RELS-EXT | A link to the Series object |
File objects
Sample of transformed FTK file available as input:
Panel | ||
---|---|---|
|
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> | 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="57433a017cea736a-c3fe971b-40644f66-a3979b29-f84b5db6c3517d11a8454b8b"><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. |
...