I found a short blog post wherein someone expresses the same level of excitement about the semi-new archival standard for encoding authorities, EAC-CPF, that I have been buzzing with of late. (Be sure to check out the project links, so you can get as excited as I am!)

I have just started playing with EAC-CPF, and doubt I don’t know enough to “teach” it, but I’m happy to lead a discussion on the topic. In particular, I am interested in finding out how aware the DH community is of EAC-CPF, and whether anyone else (DH, archivist, or otherwise) has been exploring or using it.

I propose some hacky time!

I don't have a specific project in mind (though I have some ideas), but in the wake of the DLF Forum, I think a focus on ArchivesSpace &/or Hydra would be germane.

I see this going one of three ways:

• an install fest
• a play-with-Jennifer's-ArchivesSpace-tester (I'll bring my laptop running my test instance) session for n00bs and non-coders
• a more technical session for folks who know, or are interested in Ruby. (I'm a n00b, so I can't lead a super-technical session, so I'd need help for that.)

If the day fills up with talking, I'm not above facilitating a post-THATcamp hackfest at a nearby drinking establishment.

I am with St. Mary’s University School of Law in San Antonio.  The law library has been using Omeka to build a digital collection.  A critical missing piece of this as a repository platform is that Omeka does not have a preservation layer.

I have the idea that a universal preservation layer can be made to overlay any content management system, by making a program to run check sums on a static file structure.

For any CMS it is possible to find a plug in to modify file structure into a static meaningful file structure.  Daniel Berthereau’s Archive Repertory plug-in modifies the file structure in Omeka, so that files can be stored in meaningful directories and assigned meaningful names (the default is to rename files with a random alpha numeric string and put all in the same directory).  So, technological barriers are low for getting a good file structure, no matter what repository platform or CMS you are using, no matter what repository platform or CMS you are using.

Rather than make a plug in to do digital preservation, it would be possible to code something that lies on top of a static file structure. It looks at the file structure, makes a list of files, runs a check sum for each file and stores that check sum along with the file location, then at a later date reruns the check sums and gives a report of which files have a different check sum (ie. gives a report of which files have changed from bit rot).  This would not be like a plug in, which installs on a specific CMS and only works with that CMS, but instead is something that overlays files on any web server.

By overlaying any set of files on a web server, such a program could do digital preservation independent of repository platform or CMS. This would greatly lower technological barriers to smaller institutions performing digital preservation.

I am interested in talking with anyone who has worked with digital preservation, and would like to meet anyone who knows about coding automated check sum reports.  I understand conceptually how to do this, but want to connect with more experienced coders who are interested in similar software.

Ultimately, I would like to code this alone or, better, with others.

I am just becoming acquainted with digital humanities. I don’t have any resources to learn about it at my institution. I have a couple of projects that I am interested in doing. One has to do with a file of 2000 Victorian letters that are only cataloged in a card catalog. The other has to do with doing a digital edition of a book. I post a blog, so I know a little about html. I have a background working with Photoshop, Illustrator, and InDesign, and I know a little about Dreamweaver. I have downloaded OxYgen. Can anybody help me get started?