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 Features | Design / Notes | Related Technical Strategic Goal(s) | Core? | Complexity | Use Cases |
|---|
| Single Search / Browse System (SOLR) | - 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 | | | Single built-in Statistical Engine (SOLR Statistics) | | 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 1(NOTE: The DSpace 7.0 release is tentatively scheduled for late 2016 or early 2017. 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 Features | Design / Notes | Related Technical Strategic Goal(s) | Core? | Complexity | Use Cases |
|---|
| Single User Interface | | Goal 2: Lean and flexible | x | High | For reference: | | Configurations in Admin User Interface | - 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 |
|---|
| labels | uc-configuration |
|---|
|
|
| | Easy and Intuitive Deposit Interface | | Goal 1: Fundamentals of IR | x | Medium | | Expand |
|---|
| title | Other Deposit Use Cases |
|---|
| | Content by Label |
|---|
| showLabels | false |
|---|
| max | 20 |
|---|
| spaces | DSPACE |
|---|
| showSpace | false |
|---|
| labels | uc-deposit |
|---|
|
|
| | 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" | x | High | | | 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 flexible | x | High | | Expand |
|---|
| title | Content Model Use Cases |
|---|
| | Content by Label |
|---|
| showLabels | false |
|---|
| max | 30 |
|---|
| spaces | DSPACE |
|---|
| showSpace | false |
|---|
| labels | uc-content-model |
|---|
|
|
| | Enhance Basic Statistical Reporting | | Goal 1: Fundamentals of IR | x | Medium | | | Enhance Basic Preservation | | Goal 1: Fundamentals of IR | x | Medium | | | | | | | | |
Priority 2 Features| Priority 2 Features | Design / Notes | Related Technical Strategic Goal(s) | Core? | Complexity | Use 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 | | | Expand |
|---|
| title | Versioning Use Cases |
|---|
| | Content by Label |
|---|
| showLabels | false |
|---|
| max | 30 |
|---|
| spaces | DSPACE |
|---|
| showSpace | false |
|---|
| labels | uc-versioning |
|---|
|
|
| | Enhance Search / Browse System | | | x | | | Expand |
|---|
| title | Search / Browse Use Cases |
|---|
| | Content by Label |
|---|
| showLabels | false |
|---|
| max | 20 |
|---|
| spaces | DSPACE |
|---|
| showSpace | false |
|---|
| labels | uc-browse-search |
|---|
|
|
| | Enhance Access Control | | Jira |
|---|
| server | DuraSpace JIRA |
|---|
| serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
|---|
| key | DS-1566 |
|---|
|
| | x | | | Expand |
|---|
| title | Access Control Use Cases |
|---|
| | Content by Label |
|---|
| showLabels | false |
|---|
| max | 20 |
|---|
| spaces | DSPACE |
|---|
| showSpace | false |
|---|
| labels | uc-access-control |
|---|
|
|
|
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 Features | Design / Notes | Related Technical Strategic Goal(s) | Core? | Complexity | Use 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
| | | | | | | | | | | |
|