To experience this website in full, please enable JavaScript or upgrade your browser.

Tag Archives: AIDA

The AOR Toolkit

The AOR toolkit cover

The Assessing Organisational Readiness toolkit was published in May 2016 and is available as a free download.

The Toolkit will help you measure your organisational readiness for managing digital content.

This process can be useful for making effective decisions about how to create, manage, store and preserve your digital content. Likewise, understanding future requirements is necessary to enable your organisation to decide whether specific actions need to be taken in regard to particular content, or when and how it is desirable to improve on current capabilities.

“It’s about measurement, not improvement; you don’t need to supply ‘evidence’ that you are doing anything.”


How it works

The toolkit is structured as a number of elements, each one describing an aspect of digital content management and covering three discrete areas (organisational, technology and resource) also known as ‘legs’. This will allow users to:

  • Assess current capabilities from an organisational, technological and resource point of view
  • Assess individual, departmantal and organisation-wide readiness
  • Use toolkit examples to easily match existing capabilities
  • Populate our AOR scorecard template

Who is it for?

One key aim of re-launching the AOR toolkit was to widen its possible use beyond the use by education institutions and develop an easy to use reference guide that can be used by any organisation which needs to manage digital content. Here are some job titles we think would have an interest:

  • Archivists
  • Data Curators
  • FOI Officers
  • Librarians
  • Records Managers
  • Repository Managers


The AOR toolkit cover

DART Podcast – The AOR Toolkit

In episode 7 of our DART podcast I sat down with Ed and Steph to discuss the work they’ve both done on updating the AIDA (Assessing Institutional Digital Assets) which we will soon relaunch under its new name – The AOR Toolkit (Assessing Organisation Readiness).

Origins of The AOR Toolkit

Initially Kevin Ashley and Ed completed the JISC-funded AIDA project in 2009, and the idea was it could be used by any University – i.e. an institution – to assess its own capability for managing digital assets.

In this episode we talk about AIDA origin, examples of how people have used it, the changes we made and why, how the AOR toolkit can be used, and what next steps people can take once they have run through the self-assessment.

Read more

self-assessment image

Self-assessment as digital preservation training aid

On the Digital Preservation Training Programme, we always like to encourage students to assess their organisation and its readiness to undertake digital preservation. It’s possible that AIDA and the new AOR Toolkit could continue to have a small part in this process.

Self-assessment in DPTP

We have incorporated exercises in self-assessment as digital preservation training aid in the DPTP course for many years. We don’t do it much lately, but we used to get students to map themselves against the OAIS Reference Model. The idea was they could identify gaps in the Functional Entities, information package creation, and who their Producers / Consumers were. We would ask them to draw it up as a flipchart sketch, using dotted lines to express missing elements or gaps.

Read more

AIDA’s new name: AOR Toolkit

The hardest part of any project is devising a name for the output. The second hardest thing is devising a name that can also be expressed as a memorable acronym.

I think one of the most successful instances I encountered was the CAMiLEON Project. This acronym unpacks into Creative Archiving at Michigan and Leeds Emulating the Old on the New. It brilliantly manages to include the names of both sponsoring Institutions, and accurately describes the work of the project, and still end up as a memorable one-word acronym.

Read more

AIDA toolkit use cases

The AIDA toolkit: use cases

There are a few isolated uses of the old AIDA Toolkit. In this blog post I will try and recount some of these AIDA toolkit use cases.

In the beginning…

In its first phase, I was aided greatly in 2009 by five UK HE Institutions who volunteered to act as guinea pigs and do test runs, but this was mainly to help me improve the structure and the wording. However, Sarah Jones of HATII was very positive about its potential in 2010.

Read more

Reworking AIDA: Storage

In the fourth of our series of posts on reworking the AIDA self-assessment toolkit, we look at a technical element – Managed Storage.

Reworking AIDA Storage

In reworking the toolkit, we are now looking at the 11th Technology Element. In the “old” AIDA, this was called “Institutional Repository”, and it pretty much assessed whether the University had an Institutional Repository (IR) system and the degree to which it had been successfully implemented, and was being used.

For the 2009 audience, and given the scope of what AIDA was about, an IR was probably just the right thing to assess. In 2009, Institutional Repository software was the new thing and a lot of UK HE & FE institutions were embracing it enthusiastically. Of course your basic IR doesn’t really do storage by itself; certainly it enables sharing of resources, it does managed access, perhaps some automated metadata creation, and allows remote submission of content. An IR system such as EPrints can be used as an interface to storage – as a matter of fact it has a built-in function called “Storage Manager” – but it isn’t a tool for configuring the servers where content is stored.

Storage in 2016

In 2016, a few things occurred to me thinking about the storage topic.

  1. I doubt I shall ever understand everything to do with storage of digital content, but since working on the original AIDA my understanding has improved somewhat. I now know that it is at least technically possible to configure IT storage in ways that match the expected usage of the content. Personally, I’m particularly interested in such configuration for long-term preservation purposes.
  2. I’m also aware that it’s possible for a sysadmin – or even a digital archivist – to operate some kind of interface with the storage server, using for instance an application like “storage manager”, that might enable them to choose suitable destinations for digital content.
  3. Backup is not the same as storage.
  4. Checksums are an essential part of validating the integrity of stored digital objects.

I have thus widened the scope of Element TECH 11 so that we can assess more than the limited workings of an IR. I also went back to two other related elements in the TECH leg, and attempted to enrich them.

To address (1), the capability that is being assessed is not just whether your organisation has a server room or network storage, but rather if you have identified your storage needs correctly and have configured the right kind of storage to keep your digital content (and deliver it to users). We might add this capability is nothing to do with the quantity, number, or size of your digital materials.

To assess (2), we’ve identified the requirement for an application or mechanism that helps put things into storage, take them out again, and assist with access while they are in storage. We could add that this interface mechanism is not doing the same job as metadata, capability for which is assessed elsewhere.

To address (3), I went back to TECH 03 and changed its name from “Ensuring Availability” to “Ensuring Availability / Backing Up”. The element description was then improved with more detailed descriptions concerning backup actions; we’re trying to describe the optimum backup scenario, based on actual organisational needs; and provide caveats for when multiple copies can cause syncing problems. Work done on the CARDIO toolkit was very useful here.

To incorporate (4), I thought it best to include checksums in element TECH 04, “Integrity of Information”. Checksum creation and validation is now explicitly suggested as one possible method to ensure integrity of digital content.

Managed storage as a whole is thus distributed among several measurable TECH elements in the new toolkit.

In this way I’m hoping to arrive at a measurable capability for managed storage that does not pre-empt the use the organisation wishes to make of such storage. The wording is such that even a digital preservation strategy could be assessed in the new toolkit – as could many other uses. If I can get this right, it would be an improvement on simply assessing the presence of an Institutional Repository.

Reworking the AIDA toolkit: why we added new sections to cover Depositors and Users

Why are we reworking the AIDA toolkit?

The previous AIDA toolkit covered digital content in an HE & FE environment. As such, it made a few basic assumptions about usage; one assessment element was not really about the users at all, but about the Institutional capability for measuring use of resources. To put it another way, an Institution might be maintaining a useless collection of material that nobody looks at (at some cost). What mechanism do you have to monitor and measure use of assets?

Read more

Updating the AIDA toolkit

AIDA cover by ULCC; "Needs Assessment" graphic by OCHA Visual Information Unit, US, Public Domain. Source:

AIDA cover by ULCC; “Needs Assessment” graphic by OCHA Visual Information Unit, US, Public Domain. Source:

This week, I have been mostly reworking and reviewing the ULCC AIDA toolkit. We’re planning to relaunch it later this year, with a new name, new scope, and new scorecard.

AIDA toolkit – a short history

The AIDA acronym stands for “Assessing Institutional Digital Assets”. Kevin Ashley and myself completed this JISC-funded project in 2009, and the idea was it could be used by any University – i.e. an Institution – to assess its own capability for managing digital assets.

At the time, AIDA was certainly intended for an HE/FE audience; and that’s reflected in the “Institutional” part of the name, and the type of digital content in scope. Content likely to have been familiar to anyone working in HE – digital libraries, research publications, digital datasets. As a matter of fact, AIDA was pressed into action as a toolkit directly relevant to the needs of Managing Research Data, as is shown by its reworking in 2011 into the CARDIO Toolkit.

I gather CARDIO, under the auspices of Joy Davidson, HATII and the DCC, has since been quite successful and its take-up among UK Institutions to measure or benchmark their own preparedness for Research Data Management perhaps indicates we were doing something right.

A new AIDA toolkit for 2016

My plan is to open up the AIDA toolkit so that it can be used by more people, apply to more content, and operate on a wider basis. In particular, I want it to apply to:

  • Not just Universities, but any Organisation that has digital content
  • Not just research / library content, but almost anything digital (the term “Digital Assets” always seemed vague to me; where the term “Digital Asset Management” is in fact something very specific and may refer to particular platforms and software)
  • Not just repository managers, but also archivists, records managers, and librarians working with digital content.

I’m also going to be adding a simpler scorecard element; we had one for AIDA before, but it got a little too “clever” with its elaborate weighted scores.

Readers may legitimately wonder if the community really “needs” another self-assessment tool; we teach several of the known models on our Digital Preservation Training Programme, including the use of the TRAC framework for self-assessment purposes; and since doing AIDA, the excellent DPCMM has become available, and indeed the latter has influenced my thinking. The new AIDA toolkit will continue to be a free download, though, and we’re aiming to retain its overall simplicity, which we believe is one of its strengths.

A new acronym

As part of this plan, I’m keen to bring out and highlight the “Capability” and “Management” parts of the AIDA toolkit, factors which have been slightly obscured by its current name and acronym. With this in mind, I need a new name and a new acronym. The elements that must be included in the title are:

  • Assessing or Benchmarking
  • Organisational
  • Capacity or Readiness [for]
  • Management [of]
  • Digital Content

I’ve already tried feeding these combinations through various online acronym generators, and come up empty. Hence we would like to invite the wider digital preservation community & use the power of crowd-sourcing to collect suggestions & ideas. Simply comment below or tweet us at @dart_ulcc and use the #AIDAthatsnotmyname hashtag. Naturally, the winner(s) of this little crowd-sourcing contest will receive written credit in the final relaunched AIDA toolkit.

Synergies abound

Yale/SOAS Islamic Manuscripts Gallery (postcard) Some days it all seems worthwhile, and last Friday was such a day. I spent most of it at SOAS listening to accounts of the many digitisation projects of the Centre for Digital Africa, Asia and the Middle East (CeDAAME), including the Fürer-Haimendorf photographic collection, Islamic manuscripts (in partnership with Yale) and other justly named “Treasures of SOAS”. What Malcolm, Stuart, Julie and the rest of the SOAS team have achieved is extremely impressive. And of course I was also there to admire the fantastic work Rory has done making an attractive and accessible online showcase for them out of EPrints. (There are some rough edges still to polish, but by-Friday was a tough deadline! 😉 )

Friday’s CeDAAME dissemination event was also an opportunity to be reminded that ULCC’s Digital Archives team has contributed in other ways to the success of SOAS’s team, directly and indirectly. Julie Makinson described how SOAS used the AIDA digital asset assessment toolkit in developing their strategic approach; and many of the SOAS team are alumni of the DPTP: so Ed and Patricia have also had their part to play in supporting SOAS’s digitisation efforts.

The presentations at SOAS were extremely interesting, describing the full range of activities of a multi-faceted digitisation programme, from the development of the strategy (using the aforementioned AIDA) to the many challenges of digitising Islamic manuscripts and related materials.

How, for example, do you reliably OCR pages of centuries-old text with mixtures of Arabic and Latin/English/French? The answer is that sometimes rekeying is unavoidable. We learned, too, that Yale used UKOLN’s DC Dot Dublin Core editor to create their metadata for Islamic collections (and then convert to TEI). Thanks to the native DC and Unicode support in EPrints, SOAS metadata (in English and Arabic) was created and managed directly in the repository. Metadata exchange between Yale’s Fedora-based system and SOAS’s EPrints system seems to have been achieved effectively – I know Rory worked closely with SOAS and Yale on this.

And I sensed genuine excitement in the room when the page-turning interfaces for viewing the books online were unveiled: both very impressive. (For SOAS Rory has been working long and hard on adapting the open source book viewer used by the Internet Archive, and ensuring that the right-to-left reading and page-turning functionality works smoothly.) We also learned about a variety of different approaches to the issues of managing and funding digitisation and cataloguing activities: with my work on the Mediawiki-based Transcribe Bentham project in mind, it was particularly interesting to hear about University of Michigan’s Collaborative Cataloguing initiative.

All in all an exciting day, and particularly satisfying to see close-up the kind of synergies that exist across all of the activities of ULCC’s Digital Archives and Repositories Team. In addition to further enhancing the SOAS Digital Archives system, we are also looking forward to working with them on their JISC-funded Engaging Overseas Communities project, which is going to involve hooking EPrints up to mobile phones in Africa and Asia.

As if that wasn’t enough, at lunchtime I also dashed over to the School of Pharmacy, where Jean, Neroli and Michelle had kindly organised a lunchtime meeting for the University of London repository managers in the LEAP consortium. It was an opportunity for me to unveil a preview of the new SHERPA-LEAP website (with added social networking goodness, courtesy of WordPress/BuddyPress) that we expect to launch very shortly.

It was a nice way to round off a week in which the Team also achieved significant milestones in our work on preservation metadata for the Parliamentary Archives and strategic development for The Women’s Library, began planning for the next DPTP course, and we received news that the FP7 BlogForever project, which will see us collaborating with Warwick, HATII, CERN and others until 2013, has received its final sign-off from the European Commission.