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.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Version 7.0

DSpace 7.0 is under active development, and is tentatively scheduled to be released in late 2016.

 

Table of Contents:

 

Wishlist for DSpace 6.0

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.

FeatureNotes / TicketsPriorityVolunteer(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.

 

HighKim Shepherd for Lucene
Single Embargo system
  • We have two ways of managing embargos, when we only need one
    Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Medium 
Single built-in Statistical Engine (SOLR Statistics)
  • Move Elasticsearch Usage Statistics to external "module"?
  • May be dependent on finding a better way to support optional add-ons/modules (which is on the RoadMap, but is unlikely to happen in time for 6.0)
Low 
(tick) Service Based API / Hibernate
  • See the wiki page: DSpace Service based api
  • Codebase is in this branch: https://github.com/KevinVdV/DSpace/tree/dspace-service-api
  • The dspace-api refactor is essentially complete (just a few outstanding Unit Tests).  But additional support will be needed to refactor/fix the various other modules to properly utilize the newly refactored API
  • If this is generally approved, @mire has promised to develop even more documentation & training materials to allow other developers to get up to speed quickly.
  • Note: this work also looks like it will resolve 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/HighKevin Van de Velde (Atmire)
(tick) DSpace needs local object identifiersUUIDs are provided as part of the Service Based API refactor (see above)MediumMark H. Wood
Enhance DSpace testing framework
(for integration / acceptance testing)

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.

Medium 
Enhanced Solr Statistical ReportsMedium 
(tick) 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
Enhancing Item Level Versioning

There was some discussion about the Item Level Versioning since it was introduced. This let to disable it by default ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. ). The discussion went on and we finally have PRs waiting for review and merge regarding the following tickets:

  • 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. (at least for JSPUI)
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration. (for JSPUI again)
  • 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.
MediumPascal-Nicolas Becker
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.

LowPascal-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

(tick) 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  
Oauth authentication pluginDryad (a fork of DSpace) has already implemented this, and reportedly is interested in contributing it to DSpace 6High 
(tick) 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

(tick) 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
(tick) 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
(tick) 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
REST API needs versioning Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Peter Dietz
(tick) Default search to boolean AND Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Andrea Schweer
(tick) Indexing of right-to-left text in PDFs Unable to locate Jira server for this macro. It may be due to Application Link configuration.   

Pull Requests to review for possible inclusion

 

New features in DSpace 6.0

  • 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

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 Leader

  • TBD

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.

DateMilestone

What it means

November 12Deadline for feature pull requestsIf you wish to contribute features to DSpace 6.0, you must submit a pull request by this date.
November 18Weekly developers' meeting devoted to review of feature pull requests for 6.0The entire hour's meeting will be used to discuss proposed features submitted by the deadline.
November 25Weekly developers' meeting devoted to review of feature pull requests for 6.0The entire hour's meeting will be used to discuss proposed features submitted by the deadline.

January 8, 2016 (tentative)

Feature freezeDSpace 6.0 is considered feature-complete on this date.  Only bugfixes will be pulled between this date and final release.
January 21Release Candidate 1 taggedA DSpace 6.0 Release Candidate will be available for wider testing.

January 25-February 5

Testathon Intensive public testing of the 6.0 Release Candidate is invited.  The Release Team will focus on getting problems resolved.
February 10Release Candidate 2 taggedAn updated DSpace 6.0 Release Candidate will be available for wider testing.
February/MarchDSpace 6.0 is publicly releasedDSpace 6.0 is released for download and general use.

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

 

 

 

 



  • No labels