SUNScholar/Practical guidelines for starting an institutional repository (IR)
"Half the job is in the discovery; the other half is having the courage to present the findings.” -Galileo-
“The right to search for truth implies also a duty; one must not conceal any part of what one has recognized to be true.” -Albert Einstein-
These highly referenced guidelines are targeted at academic institutions in developing countries world wide, who want to start an open access research repository and who want to know in detail what is required and how to do it step-by-step. The focus during development of the open system has been long term research repository preservation, security, stability and interoperability on the internet using the self-hosting value proposition.
These guidelines are also an attempt to promote the use of a reference architecture and software release cadence as best practices, for the implementation of DSpace as a trusted institutional digital repository, as we did for our repository, SUNScholar. See link below.
In addition, Stellenbosch University Library has implemented open access journals and open access conferences. See the link below for more details.
Before beginning or continuing your institutional repository project, it is essential that you read the following written by Dorothea Salo:
This seems to be a symptom of many current institutional repositories which must be avoided if they are to succeed.
The symptom being... assigning the wrong people (unskilled or untrained and unrewarded) to manage open scholarly communications systems in the library.
It is assumed that, the institution is prepared to make provision for the following baseline requirements:
- A production and two backup data centers in different geophysical locations for the purposes of disaster recovery.
- Institutional internet access for the servers in the data centers.
It is also assumed that, the institution is aware of the critical importance of data sovereignty, especially in light of the following;
- Revelations about the American NSA
- The "takedown" campaign by Elsevier
- The "takedown" campaign by the Nature Publishing Group
- The "takedown" campaign by the American Chemical Society
- The "takedown" campaign by the American Civil Engineers Society
Step by step recommendations
After quickly reading all of the steps below and then carefully building a test system, it should be possible to derive a business plan/model to solicit funding or prepare a fairly comprehensive initial capital expenditure foundation budget and then an implementation plan/schedule.
Step 01 - Open Access Policy, Repository Preservation and Audit Step 02 - Marketing Friendly (Vanity URL), Persistent URL and Preservable Digital Objects Step 03 - Employ Repository Management Personnel Step 04 - Build Repository IT Infrastructure Step 05 - Install DSpace Repository Software Step 06 - Repository System Backup & Monitoring Step 07 - Repository Launch and Registration with Harvesters Step 08 - Capture Research Records and Submit Research Items Step 09 - Repository Self-Help and News Step 10 - Engage Research Partners Step 11 - Continuous System Improvement and Maintenance (Preserve forever) Step 12 - Repository Research, Support and Management Help
Latest information for installations
Use the online wiki when doing test/development/production/backup system installations because the wiki has the latest information. See the links below.
http://wiki.lib.sun.ac.za/index.php/SUNScholar/DSpace http://wiki.lib.sun.ac.za/index.php/SUNScholar/System_Admin http://wiki.lib.sun.ac.za/index.php/SUNScholar/Optimisations http://wiki.lib.sun.ac.za/index.php/SUNScholar/Customisation