Version 4.1

...

Summary

DSpace 4.1 is a bug fix / security fix release to resolve any issues located within DSpace 4.0. As provides bug-fixes and minor improvements to the 4.x platform. 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 for DS-1536; see belowsee Fixing the effects of DS-1536).

This small bug fix release addresses a number of issues that have cropped up Issues which have been resolved in 4.x. These issues include:1 include:

• Fixed issue where having a period (.) in your handle prefix generated incorrect identifiers (DS-1536)
• Fixed broken quick build (from [dspace-src]/dspace) (DS-1867)
• Fixed a crash of DSpace during CSV import via BTE (DS-1857)
• Fixed collection harvesting to DSpace via ORE (DS-1848)
• Fixed deposit of new items via SWORD
• Several fixes to the XMLUI mobile theme
• (DS-1846)
• Fixed search hit highlighting in XMLUI (DS-1907)
• Fixed broken 'stat-initial' script (DS-1795)
• Other minor fixes. See Changes in 4.x section for a list of all fixes.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".

    Warning
    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.

    Code Block
    language sql title 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;

    Code Block
    language sql title Fix the affected items:
    UPDATE metadatavalue SET text_value = 'http://hdl.handle.net/14'||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;

    This is covered by the upgrading instructions linked above.

• 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

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 XXMarch 3, 2014

Release Process will proceed according to the following Maven release process: Release Procedure