Candidate Features for DSpace 6.0Because of tight timelines for 6.0, the 6.0 release will be a "bring us what you have" release (similar to 3.0, 4.0 and 5.0 in the last three years). Therefore, most of the features in 6.0 will be determined from community contributions which align well with the overarching Strategic Plan and Roadmap (see below).
Therefore, 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.
| Priority 1 Features | Design / Notes | Related Technical Strategic Goal(s) | Core? | Complexity | Use Cases | Volunteers |
|---|
| Anchor |
|---|
| Single Search / Browse System |
|---|
| Single Search / Browse System |
|---|
|
Single Search / Browse System (SOLR) | While the default Search/Browse system is now based on Apache Solr, DSpace continues to maintain outdated code which supports the Traditional Lucene / Database system.
- Lucene and old DB browse system are already deprecated. Just need removal
| Jira |
|---|
| server | DuraSpace JIRA |
|---|
| serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
|---|
| key | DS-2160 |
|---|
|
| Goal 2: Lean and flexible | x | Low | | | | Anchor |
|---|
| Single built-in Statistical Engine |
|---|
| Single built-in Statistical Engine |
|---|
|
Single built-in Statistical Engine (SOLR Statistics) | DSpace currently has two built-in statistical engines, one based on Apache Solr (default) and another based on ElasticSearch. DSpace should only provide one out-of-the-box, built-in statistical engine (Solr Statistics), and the ElasticSearch codebase should be migrated into an optional "module" or add-on.
- Move Elasticsearch Usage Statistics to external "module"? Possibly related to "Module Framework" project however (so it may or may not need to wait for 7.0)
| Goal 2: Lean and flexible | x | Low | | | | 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 1The DSpace 7.0 release is tentatively scheduled for late 2016 2017 or early 20172018. The below candidate features are ordered in terms of importance to the 7.0 release. As such, the goal is to achieve each feature in the order that they appear. 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. | Info |
|---|
| title | DSpace 7 plans presented at OR16 |
|---|
| At OR16, the plans for DSpace 7 were presented as part of the "Introducing the New DSpace User Interface" talk. |
| Priority 1 Features | Design / Notes | Related Technical Strategic Goal(s) | Core? | Complexity | Use Cases | Volunteers |
|---|
| Anchor |
|---|
| Single User Interface |
|---|
| Single User Interface |
|---|
|
Single User Interface | DSpace currently maintains two user interfaces in parallel (JSPUI and XMLUI). We want to "converge" on a single, out-of-the-box user interface for DSpace. | Goal 2: Lean and flexible | x | High | For reference: | Cineca | | Anchor |
|---|
| Configurations in Admin User Interface |
|---|
| Configurations in Admin User Interface |
|---|
|
Configurations in Admin User Interface | DSpace should support the modification of most configurations/settings from the Administrative User Interface, instead of requiring such configurations be tweaked from command line.
- Dependent on / related to "Single User Interface"
| Goal 5: Low cost, "just works" | x | High | | Expand |
|---|
| title | Configuration Use Cases |
|---|
| | Content by Label |
|---|
| showLabels | false |
|---|
| max | 30 |
|---|
| spaces | DSPACE |
|---|
| showSpace | false |
|---|
| cql | label = "uc-configuration" and space = "DSPACE" |
|---|
| labels | uc-configuration |
|---|
|
|
| Cineca | | Anchor |
|---|
| Module Framework and Registry |
|---|
| Module Framework and Registry |
|---|
|
Non-functional: Module Framework and Registry | DSpace needs a clear definition of what constitutes a "DSpace module", so that third-parties can create, maintain and distribute their own "modules" as add-ons to DSpace, and distribute them via a public "registry". | Goal 3: Can be "extended" | x | High | | Cineca (interested) | | Anchor |
|---|
| Simplify Community and Collection Hierarchy |
|---|
| Simplify Community and Collection Hierarchy |
|---|
|
Simplify Community and Collection Hierarchy | DSpace's required hierarchy of Communities and Collections should be replaced with a more flexible module of supporting Collections & Sub-Collections. | Goal 2: Lean and flexible | x | High | | | | Anchor |
|---|
| Lower the effort to deposit content |
|---|
| Lower the effort to deposit content |
|---|
|
Lower the effort to deposit content (via integrations) | The DSpace deposit process should integrate more closely with external data sources, in order to automatically populate (or suggest) data on deposit. We should also investigate whether some integrations may allow opportunities for Administrator's to autopopulate DSpace from trusted, external content sources. | Goal 1: Fundamentals of IR Goal 4: Integration with external services | x | Medium | | Cineca (interested) |
Candidate Features for DSpace 7.0 - Priority 2The DSpace 7.0 release is tentatively scheduled for late 2016 or early 2017. As "priority 2" features, these features are not guaranteed for the DSpace 7.0 release, but we'd encourage community members to volunteer to help achieve any of these features. If there is community interest in moving one or more of these features forward, that feature may be moved up to "priority 1" for the 7.0 release. These features are ordered in terms of importance, but are all considered to be lower importance than the "priority 1" features listed above. | Priority 2 Features | Design / Notes | Related Technical Strategic Goal(s) | Core? | Complexity | Use Cases | Volunteers |
|---|
| Anchor |
|---|
| Hierarchical Metadata Support |
|---|
| Hierarchical Metadata Support |
|---|
|
Hierarchical Metadata Support | DSpace should support hierarchical metadata formats (e.g. MODS) | Goal 1: Fundamentals of IR | x | High | | Cineca | | Anchor |
|---|
| Relationships between Objects |
|---|
| Relationships between Objects |
|---|
|
Relationships between Objects | DSpace should support defining relationships between objects (especially at the Item and Bitstream level). Some object relationships may be definable via metadata, but should be respected by the DSpace UI. But, in other situations, it may also necessitate the creation of new types of Objects (e.g. Author objects as Authors of an Item rather than simply textual metadata) | Goal 1: Fundamentals of IR | x | High | | Cineca | | Anchor |
|---|
| Enhance Basic Statistical Reporting |
|---|
| Enhance Basic Statistical Reporting |
|---|
|
Enhance Basic Statistical Reporting | DSpace's existing Statistical Reporting user interfaces are rudimentary and do not provide enough useful views/reports/exports of the underlying captured data. These should be enhanced based on modern use cases/needs.
- Primary use case description: Basic Statistics (and all child pages)
- This would likely be depending on the "Single User Interface" project for much of the enhancements, as many of these reports are UI related.
| Goal 1: Fundamentals of IR | x | Medium | | | | Anchor |
|---|
| Enhance Basic Preservation |
|---|
| Enhance Basic Preservation |
|---|
|
Enhance Basic Preservation | DSpace's existing basic preservation functions (format identification, checksum verification, etc) could use enhancement based on modern tools and services.
- See linked use cases for more details of possible enhancements to existing basic preservation functionality
| Goal 1: Fundamentals of IR | x | Medium | | | | Anchor |
|---|
| Easy and Intuitive Deposit Interface |
|---|
| Easy and Intuitive Deposit Interface |
|---|
|
Easy and Intuitive Deposit Interface | DSpace's deposit interface could use enhancement for a better overall user experience with regards to usability and accessibility.
- Dependent on / related to "Single User Interface"
- Primary use case description: Easy and Intuitive Deposit Interface
- May need further definition around what sorts of changes will make deposit easier?
| Goal 1: Fundamentals of IR | x | Medium | | Expand |
|---|
| title | Other Deposit Use Cases |
|---|
| | Content by Label |
|---|
| showLabels | false |
|---|
| max | 20 |
|---|
| spaces | DSPACE |
|---|
| showSpace | false |
|---|
| cql | label = "uc-deposit" and space = "DSPACE" |
|---|
| labels | uc-deposit |
|---|
|
|
| Cineca (interested) |
|