Risk Description |
(P) |
(S) |
Risk |
Detail of action to be taken (mitigation / reduction / transfer / acceptance) |
1) Failure to complete the project on time due to the large number of artefact records and the process of aggregating the metadata |
3 |
5 |
15 |
Prioritising across collections: - artefacts with the maximum data already available will be selected first - finds whose data requires enhancement will be included in the second phase of the project - as the database will continue to evolve over time, additional data will be ongoing |
2) Failure to achieve engagement from a wide community of users: conservators, metallurgists, ethno-graphers, pre-historians, experi-mental archaeologists |
2 |
5 |
10 |
Creating a user-friendly platform and exposure through conferences, launch events and information in key publications |
3) Problems of data compatibility between three disparate repositories |
2 |
5 |
10 |
Preliminary investigations have shown that the keys needed to achieve this integration do exist |
4) Technology not working in time to support users |
2 |
5 |
10 |
By focussing on integrating existing technology, an early prototype will be produced within 3 months of the start of the project. Other enhancements will then be incrementally added |
5) Damage to artefacts as they are moved |
2 |
3 |
6 |
All handlers will be trained and photography conducted at TWAM studio to minimise carriage |
6) Project outcomes become unsustainable |
2 |
3 |
6 |
The website and database will be integrated into new developments of the GNM website, with ongoing support by both University and TWAM |
7) Loss of key project staff during the project |
1 |
3 |
3 |
Unlikely with a broad project team. Others able to backfill. |
(P) : Probability 1-5 (1 = low 5 = high)
(S) : Severity 1-5 (1 = low 5 = high)
Risk : Risk score (P) x (S)