Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

Collection Name / Institution

All Files on SUL-BRICK

Analysis Complete

RELS-EXT Created

Fedora Objects Created

Analysis 

Prototype Fixture Objects
(coll, set, item, file ...)

Hooks from item to file objects
addressed

Ingest Processor Outputs
Tested and Approved

Hypatia App
Tests Fixture Objects

Collection Processed into
Staging Fedora

Collection Processed into
Production Fedora

Hypatia App Has Data

Xanadu / Stanford

  • EAD (collection and item / no FTK)

(tick)

(tick) Xanadu / Stanford

(tick)

(tick)

 

Stanford

Stanford

Stanford

Stanford

Stanford  

Gould / Stanford

  • EAD (collection) / FTK

(tick)

(tick)

 

(wink)

(tick)

Stanford

Stanford

Stanford

Stanford

Stanford  

Koch / Stanford

  • EAD (collection) / FTK

(tick)

 

 

 

Stanford

Stanford

Stanford

Stanford

Stanford

Stanford

Stanford  

Creeley /Stanford

  • EAD (collection) / FTK

(tick)

 

 

 

Stanford

Stanford

Stanford

Stanford

Stanford

Stanford

Stanford  

Gallagher / Hull

  • EAD (collection and item) / no FTK

(tick)

 

Uva

 

Uva

Stanford

 

 

 

Socialist Health / Hull

  • EAD (collection and item) / no FTK

(tick)

 

Uva

 

Uva

Stanford

 

 

 

Tobin / Yale

  • EAD (collection and item) / no FTK

(tick)

(tick)

(wink)

 

Uva

Stanford

 

 

 

Turner / Yale

  • EAD (collection and item) / no FTK

(tick)

 

Uva

 

Uva

Stanford

 

 

 

Cheuse / UVa

  • EAD (collection and item), FTK

(tick)

(tick)

Uva

 

Uva

Stanford

 

 

 

General conversion and data mapping

Stanford

Collection Name

Estimated Size of Collection in Hypatia

M1437 Gould

2.5 GB

M1292 Xanadu

5.0 GB

M0662 Creeley

3.0 GB

M1584 Koch

35 GB

...

The collection was re-processed due to a change in storage location and new ideas on relationships between files and EAD.

Stanford FTK to Hypatia object mapping

Processed files are currently stored in

...

Contents of the collection are currently stored on \\sul-wallaby\ForensicsLab\01-OBJECT_POOL\M1292 Xanadu

Xanadu EAD and Hypatia fixture objects

...

  • Assets loaded on sul-brick; in directory /home/sulguest3/Yale/mssa.ms.1691 - there are only 2 files.
  • Each file asset is associated with a specific component; in other words, only two components have assets associated with them. The assets are a Microsoft Access database and a FileMaker Pro database.
  • The components that have an asset associated with them contain a dao element. This element's xlink:href attribute is a file URI that points to the location on sul-brick (this is a hack, but it should be sufficient)

Virginia

I have finally been able to image the floppy disks and use FTK to do some basic processing. The EAD remains unchanged.

There are 7 disk images. The physical disks themselves were numbered with a different schema than the <c0n> elements in the EAD. The physical disk numbers were used to create the filenames for the disk images.

<c02 level="item" id="d1e560"> corresponds to disk images: 10726-p-q002001, 10726-p-q002002, 10726-p-q002003, and 10726-p-q002004b

<c02 level="item" id="d1e571"> corresponds to disk image: 10726-p-q002005
<c02 level="item" id="d1e582"> corresponds to disk image: 10726-p-q002006
<c02 level="item" id="d1e594"> corresponds to disk image: 10726-p-q002007

I have bookmarked the files within the images using FTK. The bookmarks correspond to the <c02> "id" attributes (so, files belonging to <c02 id="d1e582"> are bookmarked "d13582"). The files should be arranged within those containers in the collection. There are other files on the disks bookmarked "ignore" which do not need to be added to Hypatia. So, we would like to have the individual documents added in addition to the disk images. Is this possible? 

The FTK html report and XML report are included in the "report1" folder. These include the technical metadata drawn from the disk images. The disk images are in the folder "diskImages" and photographs of the physical disks are in the folder "photos." These jpeg images are named to correspond with the disk image file name and should also be available along with the disk images.

The file sizes are as follows:

  • 5 MB    report1/files folder
  • 36 MB  diskImages folder
  • 26 MB  photos fp;der

Please let me know any specific questions.

-Gretchen

What I have to submit is some EAD for the Cheuse collection, and 4 zip files which match the id number of <co2> elements in the EAD. The zip files contain images of each disk and pdf files. I can't actually image the disks...I don't have the hardware yet. For the purposes of the tests, what I did was: 

  1. Took pictures of the floppies
  2. Created a  directory structure that matched the structure in the EAD and put the images of each disk in the appropriate folder
  3. Added a dummy pdf to each folder
  4. Zipped up each folder and ran it through Rubymatica which:
    1. unzips
    2. Creates some technical metadata within a METS.xml file
    3. Rezips

...

Summary

Collection title

Number of files/objects

Total Extent in (mega/giga)bytes

Extent to be transferred for development

EAD filename

Level of description of born-digital material

Alan Cheuse papers

EAD + FTK output (metadata, plus approx 1,400 files)

approx 55 MB

approx 55 MB

uva10726.xml

disk images were processed using FTK. Labels assigned to FTK objects correspond with values in <unitid> tags. those <unitid>s are listed below.

unitids:

  • e002001
  • e002002
  • e002003
  • e002004
  • e002005
  • e002006
  • e002007
  • e002007b
  • e007
  • e0100 – e0144
    • EXCEPT e0136…this disk is unreadable, no FTK content
  • e0557-- e0557t
    • EXCEPT e0557r…the disk is unreadable
  • e0422 – e0429
    • EXCEPT e0421, e0421a and e0423…unreadable disks

Hull

Files transferred via external hard drive/USB pen drive so no physical media to photograph 

...