We’ve chosen DSpace as the repository to hold our research data. Much of the work to date has been involved around the issue of submitting large datasets to the respository.
We’re looking at using SWORD, and possibly SWORD 2.0. We’ve also taken the opportunity to update our current DSpace installations to the latest version of DSpace (1.8.2) and switched to an Oracle database, from Postgres. This gives us 24/7 support and allows us to use the latest version of SWORD, which only works on DSpace 1.8. We would also have had to upgrade our version of postrges to allow us to use the latest version of DSpace, which helped toward our decision to move to oracle.
For you techies out there, this process of updating has not been straightforward and is full of pitfalls. There is currently no process of easily cloning a postgres database and creating an oracle version so it all has to be done by hand to ensure the database integrity remains high. However, once the database is switched over, upgrading from 1.6.2 to DSpace 1.7.2 is quite straightforward.
BUT, DSpace 1.8.2 has some important differences to 1.7, most notably the devolvement of the main dspace.cfg file into several smaller configs.
So, a long winded process but we are near the end now. The test DSpace install is fully functional and so we now have the capability to upgrade the live version.
Ian – Technical Developer
Posted under Technical development
This post was written by Ian Wellaway on May 25, 2012