DSpace 5.0 ships with a number of new features. Certain features are automatically enabled by default while others require deliberate activation.
The following non-exhaustive list contains the major new features in 5.0 |
 | Easier Upgrading to 5.x from ANY previous DSpace version (1.x.x, 3.x or 4.x). - Your underlying DSpace database now upgrades itself automatically when you first run a newer version of DSpace (see DS-2167, by Tim Donohue with support/feedback from 5.0 Release Team).
- Solr/Lucene indexes now upgrade automatically during the "ant update" step of the Upgrade process (see DS-2297 by Tim Donohue, with support/feedback from Ivan Masár and 5.0 Release Team).
|
 | Perform Batch Imports from the User Interface (in both XMLUI and JSPUI) |
| XMLUI new features |
| JSPUI new features |
 
| REST API new features |
 | RDF Interface to support Linked (Open) Data (NEW) - DSpace can now provide its content as Linked (Open) Data via a new RDF interface (provided as an "rdf" webapp), see DS-2061 by Pascal-Nicolas Becker
|
 | OAI-PMH interface enhancements / bug fixes - OpenAIRE v3 compliance (operators over filters)
- OAI respects item READ rights
- /oai displays the list of available contexts; contexts have descriptions
See DS-1649 by João Melo |
| Enhanced Thumbnail Quality (disabled by default) See DS-2105 by Terry Brady with the support of Georgetown University |
| Bug fixes / improvements to Biblio-Transformation-Engine (BTE) Kindly contributed by the Greek National Documentation Centre/EKT |
| Enhancements to DOI Support (disabled by default) - Enhanced EZID IdentifierProvider Metadata Mapping via XSLT, see DS-2119 by Mohamed Mohideen Abdul Rasheed
|
| Apache Solr libraries were upgraded for all interfaces (JSPUI, XMLUI, and OAI) See DS-2253 by Roeland Dillen with the support of @mire |
 | Add a place for third-party JARs / plugins to be "found" by DSpace (disabled by default) - DSpace will now look for JARs / plugins in the locations specified by "plugin.classpath" value specified in dspace.cfg.
See DS-2107 by Mark H. Wood with the support of IUPUI University Library |
 | All objects now have metadata support - All DSpace objects (Communities, Collections, Items, EPeople, Groups) now have metadata, and most now use the default "dc" (Dublin Core) metadata schema.
- NOTE: The only exception is EPeople metadata, which is stored in a new "eperson" metadata schema.
- The User Interfaces don't yet take advantage of this enhancement in DSpace 5.0. Instead, this is an internal restructuring of data within DSpace. In the future, this provides the potential to create more enhanced metadata (or even more configurable metadata) on all objects
See DS-1582 by Mark H. Wood with the support of IUPUI University Library and Kevin Van de Velde with the support of @mire |