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’m interested in how libraries can better serve digital humanities researchers as providers of data and source material. Specifically, as we make determinations for digitization, metadata, and interfaces, how can we optimize the content for discovery and use by digital humanities researchers? I’ve been thinking about this for archives/special collections in particular. I’m also aware of an RFP that the HathiTrust Research Center has put out that’s along these lines (www.hathitrust.org/htrc).

Has anyone else been thinking about how to boost discovery, access, and use of library resources (of any types and formats) for DH scholars? What have you been doing to connect these researchers to collections at your own institutions, and what more could we be doing collaboratively and/or at network scale?

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’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!

For the majority of the life Clemson University Libraries’ digital imaging lab we’ve been concentrating on a large IMLS grant and digitizing over 150,000 items from the national and state park systems, compared to the meager 10,000 items we have digitized of our own collections and for our partner institutions in the South Carolina Digital Library.

The grant is now winding down and we will soon be seeking to digitize many of the collections within our Special Collections’ archives.

As an academic library, what methods can we employ that will generate interest and traffic of the digital items? How can we use technology to engage students in our other library collections besides the available study spaces?