Planning checklist

The planning checklists to be found in each key section of the RSP web site are offered as a series of key questions designed to ‘make you think'. Please note that we have not crowded presentation by trying to offer answers to the questions, many of which may be local or specific to each institution.

This planning checklist covers resourcing repositories for sustainability. Here are the questions to ask yourself:

  • Have you properly and fully specified the requirements of your repository?
  • Where and who will host the repository?
  • What are the pros and cons of using open source software and is it for you?
  • Have you considered buying in the software and/or the support?
  • What is the anticipated growth of your repository? Does your technical architecture support that growth?
  • Have you considered a service level? Will the repository be available 24/7? Will the users expect it to be?
  • How much do you want to customise the software - look and feel, metadata store & Web interfaces?
  • Are you running a pilot project or a production service? If the former, who, when, if and how will it transfer to a production service?
  • Who will answer support/help desk queries relating to the repository?
  • How will you get data out of the repository when the next best thing comes along?
  • Have you considered how your repository may grow over the next year, 3 years, 5 years, 10 years, and do you have sufficient storage space for such growth, or a means to acquire new storage?
  • Do you have sufficient backup capability and capacity for your repository?
  • Have you considered who has suitable skills to perform a repository installation?
  • Have you considered who has suitable skills to perform a repository customisation (metadata, input forms, collection creation etc)?
  • Have you considered who has suitable skills to perform repository look and feel customisation (graphic skills, corporate branding)?
  • Do you know who has access to the systems that you might want to integrate with (for example local password and authentication systems)?
  • Have you considered how you will document and store your installation and customisation details for future reference?
  • Have you budgeted maintenance time for staff to maintain your repository technical infrastructure?
  • Do you know who will look out for announcements of new versions to test and upgrade?
  • Who will provide ongoing technical support for day to day technical issues that might arise?
  • Which digital formats can the repository commit to preserve in the longer-term? Is the repository collecting author source formats?
  • Is there a viable action plan for monitoring the formats stored in the repository and the preservation risks associated with those formats? Do you know which tools are available to do this?
  • Should the repository look to outsource preservation action services?
  • Does the budget for the repository support all requirements identified for sustainability?