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

2016 has been a good year

So much has happened over the last year with our Enterprise Architecture practice that it's hard to write a succinct summary.  For my day-to-day experience as enterprise architect, the biggest change is that I now have a team to work with.  This time last year, I was in the middle of a 12-month secondment to create the EA practice, working mainly on my own.  Now my post has been made permanent and I have recruited two members of staff to help meet the University's architectural needs.

I have spent a lot of the year meeting people, listening to their concerns and explaining how architecture can help them.  This communication remains vital, the absolute core of what we do and we will continue to meet people in this way.  We also talk to people in other Universities in order to learn from what they are doing and to share our own experience back.  A highlight in this regard was my trip to the USA last January.

Our biggest deliverable for the past year was the design of the data wa…

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.


This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…

New staff for the EA team

I'm delighted to welcome Jason Murphy, who joins us as our CRM Architect, and Wilbert Kraan, our new Data Architect.  Both Jason and Wilbert have worked as consultants for several years and bring new skills and considerable experience to IS.  They both know more than I do about their respective fields, which is how I like to hire people.

So the Enterprise Architecture practice now comprises the three of us, instead of me working on my won, which means we have more capacty to guide the University's IT architecture.  We can offer a greater range of skills and can bring a wider range of experience to bear.  I'm really excited about the opportunities this presents.

As his job title implies, Jason will focus on contact relationship management, working to build a user community and to create a strategy for managing and improving the University's relationships with prospective students, research partners, community organisations, and other parties - to give them all a better …