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 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.

When the James B. Hunt Jr. Library at North Carolina State University was planned, NCSU Libraries made the strategic decision to build immersive visualization spaces throughout the building, including four large, public, architecturally-integrated video walls. These visualization displays allow the Hunt Library to be a storytelling building: a building that provides a narrative window for the teaching, research, and learning activities on campus.

Video walls and immersive digital environments are creating new opportunities for digital humanities research and pedagogy. In this session, you can learn a little bit about our walls, but more importantly, we’ll brainstorm about potential DH applications for this kind of technology and discuss the challenges around implementing projects and services.

Who else does DH or DH-like activities on campus? From the isolated faculty in a corner, to pockets of activity in specific schools, academic departments, or other campus units, all the way to a full fledged “DH Center” elsewhere on campus: how do you map out that activity, and start developing connections and partnerships? What works, what does not? Have you encountered administrative barriers? Institutional sub-cultures that need to be bridged? Let’s talk about our experiences, good or bad, and discuss our developing plans in that area.

I’m proposing this as a ‘talk’ session. I’m sure I don’t have much to add, but I’m wondering what considerations for digital preservation (security, metadata) may be unique to DH. Any roadblocks, requirements that others have found, particularly when working with an IR or non-DH folks.

This may not make sense, help me out if you have any thoughts. I’m hoping to get some digital preservation insight on Thursday!