Contribute to the DSpace Development Fund
The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.
Version 4.1
DSpace 4.1 was officially released to the public on February XX, 2014.
DSpace 4.1 can be downloaded immediately at either of the following locations:
SourceForge (Zip): https://sourceforge.net/projects/dspace/files/
GitHub: https://github.com/DSpace/DSpace (tag "dspace-4.1")
In addition, you are welcome to try out DSpace on http://demo.dspace.org/ and continue to provide any feedback you may have.
We recommend DSpace 4.x users upgrade to 4.1
Generally we recommend all DSpace 4.x users upgrade to DSpace 4.1 to receive several bug fixes. However, if you decide that none of the bug fixes are relevant for you then there is no urgent case for upgrading.
However, it is worth noting that DSpace 4.1 includes a security fix for the JSPUI. Therefore, we highly recommend anyone using the JSPUI upgrade to DSpace 4.1.
Summary
DSpace 4.1 is a bug fix / security fix release to resolve any issues located within DSpace 4.0. As it only provides bug-fixes, DSpace 4.1 should constitute an easy upgrade from DSpace 4.x for most users. No database changes or additional configuration changes should be necessary when upgrading from DSpace 4.x to 4.1 (except for DS-1536; see below).
This small bug fix release addresses a number of issues that have cropped up in 4.x. These issues include:
- Fixed broken quick build (from [dspace-src]/dspace)
- Fixed a crash of DSpace during CSV import via BTE
- Fixed collection harvesting to DSpace via ORE
- Fixed deposit of new items via SWORD
- Several fixes to the XMLUI mobile theme
- Other minor fixes (see below)
Upgrade Instructions
- For upgrade instructions for 4.x to 4.1, please see Upgrading From 4.0 to 4.x.
If you're affected by DS-1536, DSpace 4.1 fixes it, but you still need to fix the incorrect metadata generated by DSpace 4.0. To do so, execute the following SQL against the DSpace database. Replace XXXXX with your handle prefix before the dot; e.g. if your prefix is "10123.1", replace "XXXXX" with "10123".
The following code is believed to work (for Postgres), but hasn't been tested on an affected instance. Make sure to have a proper database backup before trying it and to verify whether it fixed the problem before moving on.
for PostgreSQL - List the affected items and metadata values:SELECT handle, text_value AS current, 'http://hdl.handle.net/'||handle as fixed FROM metadatavalue, metadatafieldregistry, handle WHERE text_value = 'http://hdl.handle.net/XXXXX' AND metadatafieldregistry.metadata_field_id = metadatavalue.metadata_field_id AND metadatafieldregistry.element = 'identifier' AND metadatafieldregistry.qualifier = 'uri' AND handle.resource_type_id = 2 AND handle.resource_id = metadatavalue.item_id;
for Oracle - List the affected items and metadata values:SELECT handle, text_value, 'http://hdl.handle.net/'||handle AS fixed FROM metadatavalue, metadatafieldregistry, handle WHERE to_char(text_value) = 'http://hdl.handle.net/XXXXX'; AND metadatafieldregistry.metadata_field_id = metadatavalue.metadata_field_id AND metadatafieldregistry.element = 'identifier' AND metadatafieldregistry.qualifier = 'uri' AND handle.resource_type_id = 2 AND handle.resource_id = metadatavalue.item_id;
for PostgreSQL - Fix the affected items:UPDATE metadatavalue SET text_value = 'http://hdl.handle.net/'||handle FROM metadatafieldregistry, handle WHERE text_value = 'http://hdl.handle.net/XXXXX' AND metadatafieldregistry.metadata_field_id = metadatavalue.metadata_field_id AND metadatafieldregistry.element = 'identifier' AND metadatafieldregistry.qualifier = 'uri' AND handle.resource_type_id = 2 AND handle.resource_id = metadatavalue.item_id;
for Oracle - Fix the affected items:SELECT 'UPDATE metadatavalue SET text_value = ''http://hdl.handle.net/'||handle||''' WHERE metadatavalue.metadata_field_id = '||metadata_field_id FROM metadatavalue JOIN metadatafieldregistry USING(metadata_field_id) JOIN handle ON handle.resource_id = metadatavalue.item_id WHERE metadatafieldregistry.element = 'identifier' AND metadatafieldregistry.qualifier = 'uri' AND handle.resource_type_id = 2 AND to_char(text_value) = 'http://hdl.handle.net/XXXXX' ; /* NOTE, you'll need to run this code in two stages: in SQL Developer, first run the above query, then cut/paste the results back into a new query, and run that query */
- If you are upgrading from 3.x to 4.1, please see Upgrading From 3.x to 4.x.
- For general upgrade instructions, please see Upgrading a DSpace Installation
No new features in DSpace 4.1
4.1 is a bug-fix / security-fix release. This means it includes no new features and only includes fixes for bugs which were found in the 4.0 release.
For a list of all new 4.x Features, please visit the DSpace Release 4.0 Notes.
Changes
The following fixes were released in 4.1.
Organizational Details
Release Coordination
- Release Coordinator: Committers Team (shared coordination) led by Mark H. Wood
Timeline and Proceeding
Release Timeline:
- Release Date: February 28, 2014
Release Process will proceed according to the following Maven release process: Release Procedure