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

« Previous Version 26 Next »

Work in Progress

May 8, 2015: This is an active document. It is not finalized, and may change in the coming month as the DSpace RoadMap Working Group and Steering Group create a final draft for presentation at OR15.

This Technical RoadMap is based on the DSpace 2015-18 Strategic Plan - Technology and the Use Case Analysis produced by the DSpace RoadMap Working Group in April/May of 2015.

Candidate Features for DSpace 6.0

(NOTE: This list is incomplete, and does not represent a list of ALL features to be added into DSpace 6.0 in late 2015.  It just notes a few smaller features / goals from the 2015-18 Strategic Plan for Technology which will be targeted towards the 6.0 release. Based on the tight timeline for 6.0, most major features/goals from the Strategic Plan for Technology are scheduled for the 7.0 release in late 2016.)

Priority 1 FeaturesDesign / NotesRelated Technical Strategic Goal(s)Core?ComplexityUse Cases
Single Search / Browse System (SOLR)
  • Lucene and old DB browse system are already deprecated. Just need removal

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Goal 2: Lean and flexiblexLow

 

Single built-in Statistical Engine (SOLR Statistics)Goal 2: Lean and flexiblexLow

 

NOTE: More features will be discussed on the DSpace Release 6.0 Status page, and added to this list as they are finalized. Work on the 6.0 release is proceeding in parallel to the development of this RoadMap, and therefore, this RoadMap primarily represents the goals/candidate features for the 7.0 release in 2016.)

Candidate Features for DSpace 7.0 - Priority 1

(NOTE: The DSpace 7.0 release is tentatively scheduled for late 2016. The below candidate features are ordered in terms of perceived importance to the 7.0 release. However, if you or your institution would like to drive or lead the development of a specific feature, you are welcome to volunteer your time towards any of the candidate features listed, no matter where that feature ranks in the listing.)

Priority 1 FeaturesDesign / NotesRelated Technical Strategic Goal(s)Core?ComplexityUse Cases
Single User InterfaceGoal 2: Lean and flexiblexHigh

For reference:

Configurations in Admin User Interface
  • Dependent on / related to "Single User Interface"
Goal 5: Low cost, "just works"xHigh
Easy and Intuitive Deposit InterfaceGoal 1: Fundamentals of IRxMedium
Non-functional: "Module" Framework and Registry
  • Define a family of specifications/interfaces for functional extensions to 'core' DSpace ( working title: 'modules'), and refactor existing bundled code to conform to new model (if appropriate/cost-effective)
  • Provide infrastructure/tools for a module registry, where users can discover, and install modular extensions. Likely include both modules maintained by committers and community contributions.
Goal 3: Can be "extended"xHigh 
Enhance Content Model / Metadata
  • Need split this (and associated use cases) up into several small features/projects. Otherwise, it is too large to easily manage. For example:
    • Remove "Bundle" object
    • Community & Collection refactoring (into just Collection)
    • Hierarchical Metadata Support
Goal 2: Lean and flexiblexHigh
Enhance Basic Statistical ReportingGoal 1: Fundamentals of IRxMedium

 

Enhance Basic Preservation Goal 1: Fundamentals of IRxMedium
      

Priority 2 Features

Priority 2 FeaturesDesign / NotesRelated Technical Strategic Goal(s)Core?ComplexityUse Cases
Non-functional: Easier Installation
  • Dependent on some Priority 1 features (e.g. Single UI, Configs in Admin UI)
Goal 5: Low cost, "just works"x  
Non-functional: Easier Upgrade Process
  • Dependent on some Priority 1 features (e.g. Single UI, Configs in Admin UI
  • Could be helped by "Theme management in Admin UI"
Goal 5: Low cost, "just works"x 

 

Theme management in Admin UI
  • Ranked lower in 2013 Vision Survey
Goal 5: Low cost, "just works"x 
  • NEED a "label" for theme related use cases
Enhance Versioning
  • Ranked lower in 2013 Vision Survey
 x 
Enhance Search / Browse System  x 
Enhance Access Control Unable to locate Jira server for this macro. It may be due to Application Link configuration.  x 

 

Unscheduled Features

(NOTE: While these features are "unscheduled" at this time, we still encourage volunteers to begin to analyze or tackle them.  If there is interest in moving one or more of these features forward in the nearterm, we can immediately move it up into a scheduled release.)

Unscheduled FeaturesDesign / NotesRelated Technical Strategic Goal(s)Core?ComplexityUse Cases
Advanced Usage Statistics
  • Likely a module or external integration, therefore it may be dependent on a "Module Framework" being developed
   

 

Advanced Preservation
  • Likely a module or external integration, therefore it may be dependent on a "Module Framework" being developed
   
      
 

 

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.