Abstract

The Fedorazon project is first and foremost the experiences of a small HE/FE team running and maintaining a Repository in the Cloud for one year. Being early adopters we provide both technical, fiscal and practical advice for both our successes and failures in this endeavour. We hope this report provides insight for other institutions wishing to utilise the Cloud for their Repository instance which we wholeheartedly recommend given they read this report first and prepare accordingly. The Fedorazon project has discovered that a 'Repository in the Cloud' is easy to get up and running (both figuratively and literally); after that, all the complexity of hardware management, political costings and human resource allocation are still right where you left them. None the less we think there are significant cost savings in the Cloud that will only increase over time. We also believe that utilising the 'network effect' of the Cloud institutions can relieve the burden of having a local hardware expert to manage the repository instance. Finally, we believe that Cloud will lead to a significant change in the way we view repository architectures, especially in regards to how a 'preservation architecture' is achieved.