Page History
Info | ||
---|---|---|
| ||
This Roadmap was presented during the DSpace Interest Groups sessions at both OR15 (week of June 8), and OAI9 (week of June 15).
|
Info |
---|
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. The DSpace RoadMap Working Group consists of the members of DCAT, Committers and Steering Group: Tim Donohue (Lead, DuraSpace), Stuart Lewis (Edinburgh), Bram Luyten (@mire), Jonathan Markow (DuraSpace), Michele Mennielli (CINECA), Richard Rodgers (MIT), Ryan Steans (Texas Digital Library), Maureen Walsh (Ohio State) Feedback on this RoadMap is welcome via comments on this wiki page or via the Twitter hashtag #dspaceplan. |
Note | ||
---|---|---|
| ||
If you are looking for information regarding specific releases of DSpace, especially past releases, also see our Releases page. |
...
Table of Contents |
---|
DSpace 7.6.
...
Because 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.
...
- Lucene and old DB browse system are already deprecated. Just need removal
Jira | ||||||
---|---|---|---|---|---|---|
|
...
...
- 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)
...
...
Candidate Features for DSpace 7.0 - Priority 1
The DSpace 7.0 release is tentatively scheduled for late 2017 or early 2018. 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 | ||
---|---|---|
| ||
At OR16, the plans for DSpace 7 were presented as part of the "Introducing the New DSpace User Interface" talk.
|
...
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.
- Introducing the New DSpace User Interface (at OR16)
- DSpace UI Prototype Challenge
- Design - Single UI Project
...
For reference:
...
- Dependent on / related to "Single User Interface"
...
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
...
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".
...
DSpace's required hierarchy of Communities and Collections should be replaced with a more flexible module of supporting Collections & Sub-Collections.
- Design - Simplify Community and Collection Hierarchy
- Also see alignment with PCDM, which simply has hierarchical Collections
...
...
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
...
- Integrations - Integrations that significantly lower the effort to fill DSpace with content, both from in house systems and third party content
- Integrations - Linking to other data sources search for available data
- Integrations - Importing data from discipline-specific systems into DSpace
- End User - Email Deposit of bitstream for automatically captured metadata
...
Candidate Features for DSpace 7.0 - Priority 2
The 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.
...
...
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)
- Primary use case description: Structure - Relationships between objects
- This feature should also investigate whether there are opportunities to better integrate or utilize the new RDF-based interface to describe / define object relationships within DSpace.
...
...
- 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.
...
- Stats/Metrics - Basic Statistics (and all child pages)
...
- See linked use cases for more details of possible enhancements to existing basic preservation functionality
...
- Admin UI - Basic Preservation - Fixity Checking
- Admin UI - Basic Preservation - Format identification
- Admin UI - Basic Preservation - Format validation
- Admin UI - Format reporting
...
- 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
...
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
...
Post-7.0 Features
While these features are scheduled as "post-7.0" 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 we can immediately schedule it for an upcoming release. These features are unordered, but are all considered priorities for DSpace moving forward.
...
- Dependent on some Priority 1 features (e.g. Single UI, Configs in Admin UI)
...
- There was an older Installer Prototype which attempted some of this, but was not successful. It may be worth revisiting that prior work/experience, if just for use cases.
- Ability to perform an installation from a CD/DVD or offline is also of importance to institutions where network speeds are lower (mentioned at OAI9 in Geneva in 2015)
- Vision: Installing DSpace could mean simply installing its UI. Once the UI is installed, you would be prompted to optionally install plugin(s) which enable OAI, SWORD, REST, etc.
...
x Maintenance
Info |
---|
The history of 7.x releases is captured on our DSpace Release 7.0 Status page. |
With the release of DSpace 7.6 in June 2023, the 7.x platform has moved into maintenance mode. This means that all future 7.x releases will only include bug or security fixes. (Improvements to existing translations or user interface accessibility are also accepted as that are considered bugs.)
- Release Numbering: Because 7.x releases all included new features (as described in DSpace Release 7.0 Status), Steering and Developers have agreed that future 7.x releases should all use the "7.6.x" number scheme (e.g. 7.6.1, 7.6.2, etc). This clarifies that 7.6 was the final release which will include new features. Starting with 8.0, we will revert to our usual numbering scheme where 8.0 will accept new features, but 8.1, 8.2, and 8.3 will only include bug fixes.
- Support plan: DSpace 7.6.x will be under support until it is no longer one of the most recent three (3) major releases per our DSpace Software Support Policy. As DSpace is moving back to a release schedule of one major release per year, this means that 7.6.x will be supported until DSpace 10.0 is released (tentatively scheduled for 2026).
- Release Schedule: DSpace 7.6.x bug-fix releases will occur whenever major issues require immediate resolution or a larger number of smaller issues are ready for immediate release. They have no fixed timeline, but will be announced on mailing lists when available.
- Development Activities: DSpace 7.6.x development activities occur on our DSpace 7.6.x Maintenance Project Board.
- Development discussions related to DSpace 7.6.x occur in our weekly Developer Meetings
DSpace 8.0 Development
Info |
---|
Additional information on 8.0 can be found at DSpace Release 8.0 Status |
DSpace Steering Group finalized the roadmap / plans for 8.0 in their meeting on June 28, 2023 (immediately after the 7.6 release). This plan was presented to the Leadership Group on August 9, 2023 (notes are public).
8.0 Release Goals
These are the main priorities for the 8.0 release as decided by the DSpace Steering Group. The overarching goal is to keep the 8.0 release smaller in size (in terms of new features), and find ways to help the community more easily upgrade to 7.x or 8.x.
- Attempt to include all (in progress) major features which missed the 7.x series of releases. Specifically, this includes these four features:
- COAR Notify support (4Science & Harvard): Implementation of the COAR Notify protocol in DSpace 8
- Correction service to enhance data quality via OpenAIRE Graph (4Science): https://4science.github.io/oaire-eld/ and https://github.com/DSpace/DSpace/pull/8184
- Porting "REST-Based Quality Control Reports" from old REST API to new one. (U of Laval, Canada): https://github.com/DSpace/DSpace/issues/7641
- Duplicate Detection in Submission ported from DSpace-CRIS (The Library Code): https://github.com/DSpace/dspace-angular/pull/1732 and https://github.com/DSpace/DSpace/pull/8415
- Accept new features which empower users in the Admin User Interface. In other words, any new features which make things easier for administrators would be accepted. However, at this time, this work is unfunded and would need to be provided by volunteers.
- Accept community contributions of any 6.x features which missed the 7.x series of releases. At this time, this work is unfunded and would need to be provided by volunteers
- Improve documentation, training to allow for greater community contributions. This also may include easing the setup/installation/customization or maintenance of DSpace.
8.0 Release Schedule
8.0 will be released in June 2024. 8.1, 8.2, 8.3 will be bug-fix only releases (with release dates to be determined later)
DSpace Steering has set a goal of having all future DSpace major releases in April of each year. For example, 9.0 would be in April 2025, 10.0 in April 2026, etc.
8.0 Development Activities
DSpace 8.0 development activities occur on our DSpace 8.0 Project Board.
Development discussions related to DSpace 8.0 occur in our weekly Developer Meetings
Future Research / Planning
In parallel to the 8.0 release, the Developer team (via Developer Meetings) will work on some early proof of concepts which may be included in 9.0 or later. Some of these early proof-of-concepts currently include work to modularize DSpace (e.g. DSpace Angular : library-based architecture proposal) and improve the storage layer (e.g. via OCFL or similar). To take part in these discussions, please join future Developer Meetings.
How to help
DSpace is a global collaboration and most of our activities are entirely volunteer based (including code development).
- To help with development activities (claiming/prioritizing tickets, testing new fixes, etc) please consider joining future Developer Meetings, or getting in touch via Slack or GitHub. We welcome anyone and everyone to contribute. Contributions can be in writing code, reviewing others code, or even simply testing someone else's code works properly.
- To help with documentation (e.g. https://wiki.lyrasis.org/display/DSDOC7x), please create a Wiki account (email wikihelp@lyrasis.org) and get in touch with Tim Donohue (via Slack or email) to ask for edit access to the documentation.
- To help brainstorm/suggest new features, consider joining the DSpace Community Advisory Team meetings or mailing lists. This is our interest group for repository managers and they help suggest future features to DSpace Steering and developers.
- To help others (and perhaps yourself), consider joining our Mailing Lists and Slack. These are the primary ways that people ask questions and support one another in using DSpace
- Additional Support options are documented on our Support page.
...
- Dependent on some Priority 1 features (e.g. Single UI, Configs in Admin UI
- Could be helped by "Theme management in Admin UI"
...
...
- Likely an optional module or external integration, therefore it may be dependent on a "Module Framework" being developed
- Ranked very highly in 2013-14 Vision Survey
...
...
While DSpace currently supports some basic theming in the XMLUI interface, management of such themes is performed via command-line configurations and tweaks. We should find a way to make Themes selectable and tweakable via the Admin UI, like other modern web facing systems.
- Dependent on "Single User Interface"
- Could be highly beneficial to "Easier Upgrade Process" in that theme management is a huge pain point of the existing upgrade process
- Ranked lower in 2013-14 Vision Survey
...
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
...
- Ranked lower in 2013-14 Vision Survey
...
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
...
In DSpace, a "Bundle" object is just a simple grouping of Files (Bitstreams) (e.g. "THUMBNAIL", "TEXT"). Rather than being its own object, a "bundle" could be more easily replaced with metadata on individual Bitstreams (e.g. dc.type="thumbnail"), or even relationships between Bitstreams (i.e. derivative objects).
- Primary use case description: Structure - purpose of bundle layer
- May also be dependent on or related to "Relationships between Objects" project
- Also see alignment with PCDM, which simply uses metadata on files
...
- Structure - purpose of bundle layer
- Structure - Describe Individual Bitstream within an Item
- Structure - Support for derivative objects
...
- Likely an optional module or external integration, therefore it may be dependent on a "Module Framework" being developed
- Ranked lower in 2013-14 Vision Survey
...
- Admin UI - Advanced Preservation - Format Migration
- Admin UI - Advanced Preservation - Format characterization
- Others under "uc-preservation" label
...
- See various unmet use cases labeled "Search/Browse"
- Dependent on "Single Search / Browse System" feature being completed, to ensure we can more easily implement new Search/Browse use cases
- Some use cases also dependent on "Single User Interface" being completed
...
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
...
- See various unmet use cases regarding "Access Control"
- Also see
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-1566
...
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
...
DSpace currently has two approval workflow systems:
- Basic/Traditional Approval Workflows. These are enabled by default, and provide up to three approval steps: "Approve/Reject", "Approve/Reject/Edit", or "Edit". These are described in more detail in the Functional Overview#WorkflowSteps
- Configurable Workflow (XMLUI only, and requires migrating all Basic/Traditional workflows)
We should consolidate on a single Approval Workflow system, likely the Configurable Workflow, with sane defaults. See this ticket for more details:
Jira | ||||||
---|---|---|---|---|---|---|
|
...
While directly related to the "Single Approval Workflow system" feature (above), DSpace's workflow system(s) do not yet meet all community use cases for approval workflows.
This feature is a placeholder for enhancing the Approval Workflow system based on the Workflow Use Cases (see list in the "Use Cases" column). However, it is likely somewhat dependent on standardizing on a single Workflow system.
...
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
...
Integrations
While integrations are very important to DSpace, these integrations projects are "unscheduled" as of yet. Some of these integrations are "ongoing activities" (e.g. search engine optimization), while others require further definition, or their design may be affected by one or more of the candidate features listed above. Nonetheless, if there is interest in moving one or more of these features forward in the nearterm, we can immediately schedule it for an upcoming release. These integrations are unordered, but are all considered priorities for DSpace moving forward.
...
- Also related to Integrations - Authentication through Multiple Mechanisms
- Already exists to some extent (LDAP, Shibb, etc). But, would be nice to move to a third-party, standardized AutN/AuthZ solution.
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-1566
...
...
- Related to Integrations - Use of multiple sorts of Direct Object Identifiers
- Also related Integrations - Handle System Identifiers
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-2153
...
- Related to Integrations - Support external authorities (ORCID) in Authority Cache
- Also related Integrations - Support for external identifiers (ORCID) in the CSV Batch edit
- ORCIDs exist in DSpace 5.x, but these use cases suggest enhancements to that system
...
- Provide an ability to stream video in-browser (likely using third-party integrations or tools)
- Related to End User - Visitor can play media hosted on an external streaming media server
...
- Provide an ability to stream/view (textual) documents (e.g. PDF) in-browser
...
- Provide an ability to stream/view/zoom/pan images in-browser
- Related to End User - Image file display (pan, zoom, size options)
...
- Search Engine Optimization
- While this exists in DSpace, SEO is an ongoing activity and can always be improved upon
...