250 likes | 372 Views
Donald G. Davis Collection. 392K Amy Baker, Megan Peck, Zach Vowell. Dr. Donald G. Davis. 1972 Doctorate, University of Illinois 1971 University of Texas at Austin 1977 Libraries and Culture Editor
E N D
Donald G. Davis Collection 392K Amy Baker, Megan Peck, Zach Vowell
Dr. Donald G. Davis • 1972 Doctorate, University of Illinois • 1971 University of Texas at Austin • 1977 Libraries and Culture Editor • Dr. Davis has written over 130 book chapters, articles, and reports, as well as more than 250 book reviews.
Technology Use • Typewriter • Office computer • PC • 1994 WordPerfect • 1996 Word
Donald G. Davis Collection • Project Outline • Problems encountered • Recommendations
Project Outline • Collection Development with Creator • File Capture • Creation of Inventories • Arrangement and Description • Administrative Decisions • Metadata schema • Standard series names • File Conversion • Ingest into DSpace
Collection Development with Creator • First meeting: • Board minutes, L&C working files, journals, mostly paper materials • Second meeting: • 32,742 Emails (1995-2005) • 39 Floppies (Classes, MSS, and Miscellaneous) • Desktop Folders (L&C, courses, and personal)
File Capture • Group server space requested (700+ MB) • Transfer of floppy files to server • Transfer of desktop folders to server • Email, a different story
Original naming scheme: Classes Miscellaneous MSS L&C Office File names: FP-ANN.95 HOW-GEN.T1A DSpace naming scheme: Learning Objects Professional Activities Publications Libraries & Culture Arrangement and Description
Administrative Decisions • Metadata schema • Author • Keyword (Correspondence, Learning objects etc.) • Original/Converted (file level) • Collection • Standard series names • Learning object • Publications (pre-print, post-print)
Conversion • Unknown text files to .rtf • Tools: FileMerlin, WordPort • WordPerfect 5.1 • Group members assigned workflow • MS Word batch conversion and manual conversion
Manual ingest Assign metadata Workflow sheets Batch ingest Arrange directories Develop Tool Ingest Process
Problems Encountered • Email IP questions • File Transfer (lost creation date, virus detected-Junk file) • Duplicates, naming convention, arrangement • Standard series names • Metadata (due to volume, couldn’t be specific) • Ingest (manual vs. bulk) • Incorrect date on computer
Email IP Questions • Correspondents’ IP • Over 20,000 emails “from” someone other than Dr. Davis • Attachments • Email preservation format • Non-proprietary • Database, instead of individual files
File Transfer • Free access to Dr. Davis’ computer • What now? • “Holding space” • Creation dates • Is “Last Modified” date good enough? • Viruses and junk files
Duplicates, Naming Convention, & Arrangement • Attachments, floppies, and the hard drive • Similar forms for different years • How to express Davis’ organization? • Build into intellectual arrangement? • Apply to naming convention? • Arrangement • By form • By original order
Metadata • Quantity limited precision • Need for further automation • From Davis’ PC to ingest • Transfer alters metadata • Visibility • Unreadable formats
Standard Collection Names • Need for standardization • Unique nature of Davis’ records • Forms • Prolific digital output • Are not all collections unique?
Ingest • Manual ingest • Determining a workflow • Subject keywords • Batch ingest • Automation of content & xml files • Quantity prevents close inspection • File names: Characters, DSpace, & Unix
Incorrect Date on Computer • Effect on authenticity • Any analogy to traditional archives? • Does it really matter? • Folder & content verification • Uneven
32,742 Emails • 4 .PST Files • Okay, we got ‘em, now what do we do? • Extraction and conversion utilities • Attachments • How to archive them • Who ‘owns’ them?
Recommendations • Maintain original order and file names • Switch from Project Muse to JSTOR • Digitization • JSTOR • Grant funded projects DLSD • Word batch conversion • CDWinder for inventory
Recommendations • Appraisal and processing by archives students • Have a systems/software expert on board • Create detailed procedural documentation
Going Forward • DON’T WAIT! • ARCHIVE NOW! • SYSTEMATIZE!