You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 52
Next »
Version 6.0
DSpace 6.0 is under active development, and is tentatively scheduled to be released in May 2016.
Table of Contents:
New Features in DSpace 6.0
DSpace 6.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 6.0 |
<image?> | Major Java API refactor, supporting UUIDs and Hibernate. The DSpace Java API has been refactored significantly to make it more modular, and make it easier to achieve future RoadMap modularity goals. For more detailed information, see DSpace Service based api or DS-2701. This feature was contributed by Kevin Van de Velde of @mire, with support/help from the DSpace Committers. - Hibernate allows us more stability in our database layer (decreases the likelihood of database specific bugs), and potentially allows us to support additional database platforms in the future
- UUIDs provide all objects with stable, globally unique identifiers (instead of existing incremental, non-unique database identifiers). This simplifies the management of identifiers in our object model.
- The Java API itself is now split into three "layers" which are all now initialized via Spring
- Service layer, which contains DSpace business logic
- Database Access Object (DAO) layer, which contains specific Hibernate database queries to locate/find individual objects
- Database Object layer, which provides access to specific database columns, object properties via Hibernate
Most sites will not notice this major API refactor, as the upgrade is seamless. However, if you've performed major (Java-level) customizations, you may need to refactor your own customizations to use this newly refactored API. Some examples are on the DSpace Service based api page. |
| Enhanced (Reloadable) Configuration System. See Configuration Reference, Enhanced Configuration Scheme and DS-2654. This feature was contributed by Tim Donohue of DuraSpace. - Provides easier management of local configurations via a new
local.cfg file. Any configurations (from *.cfg files) can be overridden in DSpace by simply copying them into your local.cfg and changing the value. See Configuration Reference - Many configurations now automatically reload as soon as you save your
local.cfg file. This means you don't need to restart Tomcat every time you need to change a configuration.- Please note: Unfortunately, at this time, some configurations do still get cached in the XMLUI or JSPUI (or similar). So, while many will reload, not all of them yet support this feature.
|
| Enhanced file (bitstream) storage plugins, including support for Amazon S3 file storage. This feature was contributed by Peter Dietz of Longsight. |
| Configurable site healthcheck (i.e. repository status) reports via email. This feature was contributed by Jozef Misutka of Lindat. |
| XMLUI new features - New framework for metadata import from external sources (including an out-of-the-box plugin supporting PubMed, and hopefully more coming soon). This concept was previously only supported in JSPUI. Screencast example: http://screencast.com/t/QBImSGbAUZ. This feature was contributed by @mire.
- Extensible administrative control panel, allowing institutions to override or customize the XMLUI administrative "control panel" (see also DS-2625). This feature was contributed by Jozef Misutka of Lindat.
- Export of XMLUI search results to CSV for batch metadata editing. This feature was previously only supported in JSPUI. See also DS-1262. This feature was contributed by William Welling of Texas A&M
|
| REST API new features - REST Based Quality Control Reports for collection manager. See also DS-2583. This feature was contributed by Terry Brady of Georgetown University
- Support for all authentication methods via REST (e.g. Shibboleth, LDAP, etc)
|
| Features Removed or Replaced
- The
build.properties configuration file has been replaced by an enhanced local.cfg configuration file. The new local.cfg allows you to easily override any configuration (from dspace.cfg or modules/*.cfg files) by simply copying it into your local.cfg and specifying a new value. It also provides enhanced configuration options as detailed in the Configuration Reference documentation. The old build.properties file is no longer used nor supported.- WARNING: As part of adding this new configuration scheme, many of the configuration settings in DSpace (primarily those in
modules/*.cfg files) had to be renamed or prepended with the name of the module. This means that 5.x (or below) configurations are no longer guaranteed to be compatible with 6.x. If possible, we recommend starting with fresh configs (see below), and moving all your locally customized settings into the new local.cfg file.
- The PDF Citation Cover Page configuration file has been renamed (from
disseminate-citation.cfg to citation-page.cfg ). See this features documentation for more details. - The legacy search engine (based on Apache Lucene) and legacy Browse system (based on database tables) have been removed from DSpace 6.0 or above. Instead, DSpace now only uses Discovery (based on Apache Solr) for all Search/Browse capabilities.
The DSpace Lightweight Networking Interface (LNI), supporting WebDAV / SOAP / RPC API, has been removed from DSpace 6.0 or above. We recommend using REST or SWORD (v1 or v2) as a replacement. However, if you still require it, the old (unmaintained) LNI codebase is still available at https://github.com/DSpace/dspace-lni - Support for SRB (Storage Resource Broker) file storage has been removed from DSpace 6.0 or above. As it was unmaintained (and seemingly unused) for many years, this feature was removed along with its configurations. As a replacement, a new file storage plugin system was added, featuring a traditional local file storage option (default) and an Amazon S3 file storage option (see Storage Layer documentation, especially Configuring the Bitstream Store). For more information on the removal of SRB support, also see DS-3055.
- The user groups Administrator and Anonymous cannot be renamed or deleted. If you had renamed them, they will be renamed back to the stock names during the upgrade. DSpace is now dependent on these specific names due to internal changes.
|
The following is an (unordered) list of changes / new features that we'd like to see added to DSpace 6.0. If you have additional features to add, please feel free. We also NEED volunteers to make these features happen, so please do volunteer if you are willing to work on a particular change! Please note that we reserve the right to reschedule/reject any feature that may not align well with the longer term RoadMap.
Feature | Notes / Tickets | Priority | Volunteer(s) |
---|
Single Search / Browse System (SOLR) | - Lucene and old DB browse system are already deprecated. Just need removal. DB Browse is being removed by Services API
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
| High | Tim Donohue |
Service Based API / Hibernate | - See the wiki page: DSpace Service based api
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- The dspace-api refactor is complete and accepted into DSpace 6
- Note: this work also resolves the following tickets as "byproducts" of the refactor:
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Allows for support of additional Database types (e.g. MySQL) via Hibernate. This comes up as an occasional request
- Begins the development of a true "Business Logic Layer" (an often discussed topic in DSpace Developer Meetings)
| Medium/High | Kevin Van de Velde (Atmire) |
DSpace needs local object identifiers | UUIDs are provided as part of the Service Based API refactor (see above) | Medium | Mark H. Wood |
Enhance DSpace testing framework (for integration testing) |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
| Medium | |
AWS S3 Bitstream Storage | A refactor of the Bitstream Storage Manager to allow different implementations for file/bitstream storage. The primary motivation is leverage a cloud service, such as Amazon S3, which offers easy management, infinite scalability, and low pricing. Other storage implementations could be built off of this work. This follows the DSpace 2.0 goal of having a Pluggable Assetstore.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
| | Peter Dietz |
Make configurable which PI to show in JSPUI item view |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
| Low | Pascal-Nicolas Becker |
Framework to better support metadata import from external sources |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
| | @mire |
Pubmed integration into XMLUI submission
|
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
| | Netherlands Cancer Institute |
Import of ScienceDirect metadata including embargo and linking to or embedding of the final version |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
| | Letitia Mukherjee |
Extensible Control Panel
|
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Easier way to add custom tabs to control panel | | |
Reloadable / Dynamic Configurations |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
(Would also need a resolution to
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
) | | Tim Donohue |
Metadata registry via REST API |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
https://github.com/DSpace/DSpace/pull/1239 | | Terrence W Brady |
REST API extensions to support interactive reports |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
https://github.com/DSpace/DSpace/pull/1239 | | Terrence W Brady |
CSV export of search results in XMLUI |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
| | |
Indexing of right-to-left text in PDFs |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
| | |
Default search to boolean AND |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
| | Andrea Schweer |
OAI deletion mode correction | -
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- changes the declared OAI deletion mode to "transient" which corresponds to what DSpace actually does
| | |
REST API needs versioning |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
| | Peter Dietz |
Move LNI into a separate project | As LNI is not in wide use anymore, and it was disabled by default in 5.0, it probably would be best to migrate it to a separate GitHub Project. Anyone who wishes to still use LNI can still install it separately. But, it would no longer be provided out-of-the-box.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
| | Robin Taylor |
Changes to REST API | TODO: any changes go here
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
| | |
Full text searching of Excel spreadsheets |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
| | |
Pull Requests to review for possible inclusion
Changes
New Features in 6.0
key |
summary |
type |
created |
updated |
due |
assignee |
reporter |
priority |
status |
resolution |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
General Improvements in 6.0
key |
summary |
type |
created |
updated |
due |
assignee |
reporter |
priority |
status |
resolution |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Bug Fixes in 6.0
key |
summary |
type |
created |
updated |
due |
assignee |
reporter |
priority |
status |
resolution |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Organizational Details
Release Coordination
Instead of a single "Release Coordinator", the DSpace 6.0 release will be managed by a "Release Team".
Release Team Members
Please volunteer (by emailing Tim Donohue), if you are interested in joining the team!
Timeline and Processing
Your contributions are welcome now! Code and documentation need not be finished, so long as it is working and we can all see what it is for. Time is set aside for fixing, polishing, and integration. We have some general Code Contribution Guidelines available, but you are also welcome to ask questions on the dspace-devel mailing list.
Release Timeline
Please note that the dates below are estimates of when particular activities may occur. As there are many factors involved in a major release, these are subject to change.
Date | Milestone | What it means |
---|
November 12 | Deadline for feature pull requests | If you wish to contribute features to DSpace 6.0, you must submit a pull request by this date. |
November - January | Review, merger and conflict resolution between pull requests | The entire hour's meeting will be used to discuss proposed features submitted by the deadline. |
March, 2016 | Feature freeze | DSpace 6.0 is considered feature-complete on this date. Only bugfixes will be pulled between this date and final release. |
March 31st (estimated) | Release Candidate 1 tagged | A DSpace 6.0 Release Candidate will be available for wider testing. |
April 25 through May 6 | Testathon | Intensive public testing of the 6.0 Release Candidate is invited. The Release Team will focus on getting problems resolved. |
~May 12 | Release Candidate 2 tagged | An updated DSpace 6.0 Release Candidate will be available for wider testing. |
~May 26 | DSpace 6.0 is publicly released | DSpace 6.0 is released for download and general use. |
Release Process needs to proceed according to the following Maven release process: Release Procedure