Skip to main content

Preserving data for centuries

When our Data Protection Officer, Susan Graham, offered to review the draft set of Data Architecture Principles, I was expecting her to comment on legal requirements to minimise access to personal data, or similar concerns.  I wasn't expecting a recommendation to preserve data for centuries, but one of her suggestions addresses exactly that.  In her words,
The University has an excellent collection of historic records, from the time of the University's foundation onwards.  This archive is a valuable resource for research, public relations and corporate memory.  Information previously recorded in written records is now being recorded in information systems.  For example, the archive contains a register of every matriculated student from 1627 to 1980.  It would be regrettable if the transition to digital meant that the modern equivalent of these records was not preserved for posterity.
So I have modified our principle that projects should understand the data life cycle from creation through update to deletion, so that it now allows the possibility of permanent preservation as an alternative to deletion.

By coincidence, this message was reinforced by a session I attended last week about the Digital Strong Room project, given our Digital Preservation Curator, Kirsty Lee.   This project aims to preserve records for up to a hundred years.  This is no mean task, as we don't know what data formats the future will bring, nor which systems people will use to read them.  (By the way, the history of data preservation is fascinating - if you get the chance, it's well worth reading about).

As Kirsty explains, digital preservation is not about storing a document on a disk and forgetting about it.  Digital preservation requires the active management of digital material to ensure ongoing access to the information it holds.  We are using Archivematica, a collection of open-source tools that handle aspects of preservation from ingest to access.  The project will first instantiate this for preserving records of the University Court, and will then extend this to other documents. 

This project doesn't impact the enterprise architecture directly, but the need to consider long-term preservation needs to be built into our project methodology, and people need to be aware of this possibility.

Comments

Popular posts from this blog

Webinar: Powering your business with Cloud Computing

On October 14th, I will be hosting a Grid Computing Now! web seminar on the topic of Cloud Computing. We have lined up two very interesting speakers who are using Cloud now to make businesses work. Ross Cooney had a good technological solution to sell but couldn't make it economic until Cloud Computing allowed him to pay for his computation only when he needed it. He will discuss the instant benefits and long term impact of cloud computing to the development, competitiveness and scalability of your application. Alan Williamson created the BlueDragon Java CFML runtime engine that powers MySpace.com. He advises several businesses and will give an overview of the different types of services available and how to avoid being locked-in to a single supplier. You can register for this event here .

Business Model Canvas

A Business Model Canvas is a tool for mapping the core functions and capabilities of an organisation.  Compared to the Core Diagrams that I described in an earlier post , the business model canvas attempts to present more aspects of the business, starting with the value proposition – a statement of what the organisation offers to its users (in the business world, to its customers).  It shows the activities and resources, as Core Diagrams do, but also shows user relationships & channels, and also benefits and costs.  I’m not aware of any universities that have used this tool but you can find examples from elsewhere on the web. We are considering business model canvases as a tool for mapping the strategic capabilities of units at the University of Edinburgh.  Phil Taylor, our EA contractor, sketched an outline of what a business model canvas might begin to look like for HR: This is only intended to be suggestive: the real canvas would need to result from in-de...

"Just enough" Enterprise Architecture

I spent an informative and enjoyable day with a proto-community of people pursuing Enterprise Architecture in UK Higher Education.  Many of the participants had been previously involved in JISC projects and have enjoyed similar events in the past, so I began the day as a bit of an outsider.  In the University of Edinburgh, our progress in adopting "architectures" is mainly on the IT side, via our Applications Architecture and our use of Service-Oriented Architecture .  Enterprise Architecture would integrate all this IT activity with the business processes and goals of the University (or what I sometimes call the administrative processes, for those readers who are unhappy with calling a university a "business"). I've tended to be a little sceptical of fully-fledged enterprise architecture (EA) because it sounds like a mammoth undertaking and the organisations doing it have often been very large corporations.  The two main outcomes of the JISC experiences ar...