Workbook on Digital Private Papers > Digital repositories > Comparing repository software for preserving personal digital archives
Comparing repository software for preserving personal digital archives
Methodology
Defining requirements
The needs of managers, archivists, system administrators and developers should be considered when evaluating repository software. These needs are several, sometimes conflicting and overlapping between groups in such a way that it is challenging to produce a coherent model for comparison. Many needs can be characterised as functional requirements, but others which relate to extensibility of the software, sustainability of the user/developer community and usability are equally important. Paradigm drew on many sources to draw up evaluation criteria, including the archivists' experience of traditional archival principles, functions and activities; the OAIS model; other repository evaluations and the RLG/NARA Audit Checklist for Certifying Digital Repositories.
Evaluation methodology
The project did not adopt a formal methodology to evaluate the repositories. However the following were among the methods used:
- Examining the release documentation of both repositories.
- Installing and configuring the repositories (and some related tools) in a test-bed environment.
- Examining documentation from members of the user community, both on the project wikis and at institutional and project websites.
- Examining earlier comparisons of repository software.
- Monitoring the mailing lists for both repository communities.
- Talking to other users of the software.
- Testing the repositories with exemplar collections of born-digital archives - this included archivists preparing and submitting materials for ingest and researchers testing access mechanisms.
