DSpace 1.6 released!
As you will have hopefully read in the publicity that has gone out – DSpace 1.6 is finally released! It has been 9 or 10 months in the making, has involved and benefited from a lot of input from dozens of developers, users, and testers, and contains some fantastic new features. It has been a privilege to co-ordinate the release, and I hope it proves a useful upgrade to current users, and a useful product to new users.
But progress waits for no one – the community is already thinking about what comes next! We’ve seen changes in the way development has taken place for 1.6 (see: ‘On DSpace Development‘) and we want to continue to innovate both in terms of the way development is steered, and how it takes place. We’ve got some ‘special meetings’ planned to look at this: how to manage releases and how to manage the release cycle. Exciting times. If you’ve got any interest in DSpace, keep an eye out for these meetings and join in. Associated with this is the call for more committers. If you’re interested in developing DSpace, read the call.
[A small errata from the DSpace newsletter: It states that the ability for item exports to take place via the user interfaces has been added in 1.6. This facility has been there since 1.5.1 and was written by Scott Philips. What has been added in 1.6 is the ability (making use of some of Scott's code) for the command line version of the batch importer and exporter to handle zip files of multiple items. This means you can export multiple items to just one zip file, transfer the single file to a new server, and re-import it.]
In: Uncategorized · Tagged with: dspace, repositories



on April 8, 2010 at 11:14 am
Permalink
DSpace 1.6
There is NO “Add ability to export/import entire Community/Collection/Item structure (for backups, for entire content migrations)”
on April 8, 2010 at 11:37 am
Permalink
That feature is scheduled for 1.7: http://jira.dspace.org/jira/browse/DS-466
on June 7, 2010 at 8:56 am
Permalink
Hello Stuart,
My name is Victor, I am working in Dspace project in Peru, I want to migrate dspace 1.4.2 to 1.6 version. What is the best way to migrate? Any code to migrate the data base?
Appreciate your help.
on June 9, 2010 at 12:35 pm
Permalink
Hi Victor,
When migrating you need to migrate the database for each major release (1.4, 1.5, 1.6 etc). The upgrade instructions in the DSpace documentation explain how to do this. You don’t however have to upgrade the application for each version, you can skip straight to the latest version.
So for your case, you need to run the 1.4 to 1.5 database upgrade script, and the 1.5 to 1.6 database upgrade script. You can then install and run the latest DSpace version. The latest version is currently 1.6.1 however we will shortly be releasing 1.6.2.
Of course always remember to take backups before any upgrade!
I hope that helps,
Stuart
on July 19, 2010 at 10:49 pm
Permalink
Hi Stuart.
I need to do the same. If I understand correctly I only need to run for both 1.4 -> 1.5 -> 1.6:
For PostgreSQL:
psql -U [dspace-user] -f [dspace-source]/dspace/etc/postgres/database_schema_15_16.sql [database name] (Your database name is by default ‘dspace’).
And
For PostgreSQL
psql -U [dspace-user] -f [dspace-source]/dspace/etc/database_schema_14-15.sql [database-name]
I hope it is this easy!
Thanks for your continued help.
Barrie
on July 20, 2010 at 10:48 am
Permalink
Hi Barrie,
Yes – that is right. First perform the 1.4 to 1.5 database upgrade, then the 1.5 to 1.6 upgrade. With the code, that can be upgraded directly from 1.4 to 1.6.
Thanks,
Stuart