Roughly weekly news and opinions from the Digital Preservation Coalition’s Head of Research and Practice, Paul Wheatley. Opinions are the opinions of Paul and those featured. Not the DPC. They’re just opinions, ok?

Excellent to see a little bit of digital preservation best practice moving out into the mainstream:

An initiative to develop a “collaborative approach to rights statements that can be used to communicate the copyright status of cultural objects…”.

Having recently explored a website that was being poorly crawled by web archives but well indexed by Google, this explains a lot:

Here’s a challenge focused on the digital preservation of outlook calendars, with lots of suggestions on how to proceed:

Celebrating DP across the pond:

Disposal doesn’t always get much of a look in, when the focus is on preservation but it can be critical. This blog post provides details of discussions from the Future Proof implementors group, including a small survey of current practices and experiences:

Stunning new tool from MoMa and Archivematica, called Binder:

Interview with Kam Woods who provides an update on the latest phase of BitCurator (here’s the direct link):

— ArchivesSpace (@ArchivesSpace) May 15, 2015

Loads of detail, including videos of sessions, on the recent IMLS meeting focused on national digital platforms in the US, that I briefly reported on last week:

Programme for the upcoming DPASSH conference:

And another piece on depressing attitudes to the legal issues around preservation for the games industry:

Version 1.1 of Siegfried hits the streets:

The story of FFV1 (lossless video codec for preservation) with some great lessons learned on how open source software (when done properly) can pay dividends for preservation. Although I’m not sure some of the obvious messages get enough emphasis here. Regardless, this is a must read. It’s slides, but meaningful ones to read out of context of the original presentation:

I usually like to end on a tweet quote of the week, but will have to instead settle for a blog post of the week with this rather awesome take on implementing open source software while all the time taking the lead from the cult of OAIS. Although I’m bemused by a couple of the OAIS points raised. Generating DIPs on the fly is perfectly OAIS compliant. And AIPs aren’t fixed, they grow as we build our metadata (and particularly our RI). Or at least that’s how it’s supposed to be. Or have my memories of what OAIS actually says and how I loosely interpreted it just blurred into one…?

But it was all right, everything was all right, the struggle was finished. He had won the victory over himself. He loved OAIS.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s