You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Stanford directory output for Gould collection contains a locally transformed version of the FTK output:

  • M1437 Gould
    • Computer Media Photo
      • CM001.jpg
      • (etc)
    • Disk Image
      • CM001.001
      • CM001.001.csv
      • CM001.001.txt
      • (etc)
    • Display Derivatives
      • {filename}.htm
    • EAD
    • FTK xml
      • files
        • {filename}
      • Report.fo
      • Report.xml
      • Report_transformed.xml
      • Disk Image

The Import/conversion process will produce this hierarchy of objects in DOR:

  • Collection object
    • Series set -- Series 1 ..."
    •    :
    • Series set -- "Series 6: Born Digital Materials"
      • Media object 1
      • Media object 2
      •    :
      • File object 1
      • File object 2
      •    :

Sample of the starting lines of the .txt file describing the media object.

Created By AccessData® FTK® Imager 3.0.1.1467 110406

Case Information:
Acquired using: ADI3.0.1.1467
Case Number: M1437
Evidence Number: CM004
Unique Description:
Examiner: Peter Chan
Notes: 5.25 inch Floppy Disk

Sample of transformed FTK file available as input:

<ftk_report xmlns:fo="http://www.w3.org/1999/XSL/Format">
    <series>Series 6: Born Digital Materials</series>
    <collection_title>Stephen Jay Gould papers</collection_title>
    <callnumber>M1437</callnumber>
    <file>
        <filename>BU3A5</filename>
        <item_number>1004</item_number>
        <filepath>CM006.001/NONAME [FAT12]/[root]/BU3A5</filepath>
        <disk_image_no>CM006</disk_image_no>
        <filesize>35654</filesize>
        <filesize_unit>B</filesize_unit>
        <file_creation_date>n/a</file_creation_date>
        <file_accessed_date>n/a</file_accessed_date>
        <file_modified_date>12/8/1988 6:48:48 AM (1988-12-08 14:48:48 UTC)</file_modified_date>
        <md5_hash>976EDB782AE48FE0A84761BB608B1880</md5_hash>
        <restricted>False</restricted>
        <access_rights>Public</access_rights>
        <medium>5.25 inch Floppy Disks</medium>
        <title>The Burgess Shale and the Nature of History </title>
        <filetype>WordPerfect 4.2</filetype>
        <duplicate_File> </duplicate_File>
        <export_path>files\BU3A5</export_path>
    </file>

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.

Information from: Disk Image // CMnnn.001.txt

maps to

notes

<collection_title>Stephen J. Gould Papers

Collection object
   descMetadata
      <mods:title>
Series & item objects
   descMetadata
      <mods:location> (1)

Equivalent to EAD <archdesc><title>

<series>Series 6: Born Digital Materials

Series set object
   descMetadata
      <mods:title>
Item objects
   descMetadata
      <mods:location> (1)

Equivalent to EAD series <c><unittitle>

<note>5.25 inch Floppy Disks</note>

Series object
   descmetadata
      <mods:physicalDescription>
          <mods:extent>

Corresponds to EAD <physdesc>
Value will be the same as "Medium" at the file level.

<callnumber>M1437</callnumber>

Collection object
   descMetadata
      <mods:identifier type="unitid" displayLabel="Call Number:">

Corresponds to EAD <archdesc><did><unitid>


Information from: FTK xml // Report_transformed.xml

maps to (all 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 reference only, to disambiguate reference in the FTK report

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="a8bd4fac-c9a1-4609-a529-25fb876f01eb"><ac:plain-text-body><![CDATA[

<filepath>CM006.001/NONAME [FAT12]/[root]/BU3A5</filepath>

 

original file in FTK xml // files
]]></ac:plain-text-body></ac:structured-macro>
display derivatives in Display Derivatives named using <item_number>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="2ce0286e-eef9-4c11-9734-f85e6cd6c872"><ac:plain-text-body><![CDATA[take object filepath for fully qualified object filename from portion after [root], up to but not including the final filename token

]]></ac:plain-text-body></ac:structured-macro>

<disk_image_no>CM006</disk_image_no>

descMetadata
   <mods:location> (1)

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

<restricted>False</Restricted>

 

true=visible staff only, not discoverable .... Hypatia only

<label name="Medium">5.25 inch Floppy Disks</label>

 

Part of <location> (1)

<label name="Type">Books</label>

 

tag

<label name="Title">The Burgess Shale and the Nature of History</label>

descMetadata
   <mods:title>

 

<filetype>WordPerfect 4.2</filetype>

note?

 

<Duplicate_File> </Duplicate_File>

 

* blank, null value or empty string - original file, not a duplicate
* "Primary" - possibly indicates Primary file to keep/store
* "Secondary" - indicates a duplicate file to be ignored
--> ignore for now

<export_path>files\BU3A5.wp</export_path>

 

The file as available for the DOR object. Note it may have a file extension added by FTK.

(1) Location/container information -- for every file object created, create a <mods:location> description that places the resource in the context of the collection by combining collection name, intermediate series/group/etc name(s), and the ID+description of the media on which the file resides, e.g.,

      <location>Stephen J. Gould Papers - Series 6: Born Digital Materials - CM006 (5.25 inch Floppy Disks)

  • No labels