RoadMap

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

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

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

Goal 2: Lean and flexible

x

Low

Single built-in Statistical Engine (SOLR Statistics)

Move Elasticsearch Usage Statistics to external "module"? Possibly dependent on "Module Framework"

Goal 2: Lean and flexible

x

Low

Candidate Features for DSpace 7.0 - Priority 1

Priority 1 Features	Design / Notes	Related Technical Strategic Goal(s)	Core?	Complexity	Use Cases
Single User Interface	(Rough) Brainstorms on a Future UI	Goal 2: Lean and flexible	x	High	For reference: End User Use Cases Admin UI Use Cases
Configurations in Admin User Interface	Dependent on / related to "Single User Interface"	Goal 5: Low cost, "just works"	x	High	Page: Admin UI - Configurations in the admin UI Page: Admin UI - Changing / Editing OAI crosswalks Page: Structure - Associate Separate Properties with Each DSpace Community Page: Admin UI - Configure and manage browse indexes Page: Admin UI - Rebuild the discovery index Page: Integration - Integration with external authentication / authorisation system Page: Integrations - Authentication through Multiple Mechanisms Page: Admin UI - DSpace should accommodate basic index normalization Page: Structure - Format checking of data entry in input forms Page: Structure - Check Bitstream names against allowed file name pattern Page: Admin UI - System Alerts via Admin UI Page: Admin UI - Customise which metadata fields to facet upon, search upon Page: Admin UI - Alter messages easier Page: Admin UI - Apply an input-form to the collection through the GUI Page: Admin UI - Manage input forms Page: Structure - Manage Lists, Controlled Vocabularies and Authority Control Page: Admin UI - Manage controlled vocabularies Page: Admin UI - Approval workflows
Easy and Intuitive Deposit Interface	Dependent on / related to "Single User Interface" Primary use case description: Easy and Intuitive Deposit Interface	Goal 1: Fundamentals of IR	x	Medium	Page: End User - Email Deposit of bitstream for automatically captured metadata Page: Admin UI - Generate Handle before commiting Item Page: End User - Curated thumbnails Page: Admin UI - Undo a bulk import from the User Interface Page: Structure - Manual Submission of New Items Page: End User - Flexible licensing Page: End User - Easy and Intuitive Deposit Interface Page: End User - Email Deposit of bitstream for archived metadata-only item Page: End User - Deposit entire item by email Page: Structure - Format checking of data entry in input forms Page: Structure - Check Bitstream names against allowed file name pattern Page: Integrations - importing large files into repositories using an external system Page: Integrations - Importing data from discipline-specific systems into DSpace Page: Admin UI - Apply an input-form to the collection through the GUI Page: Admin UI - Updating a Workflow group Page: Admin UI - Workflow Overview Rejection Page: Structure - Create / manage files and metadata (as an Item) Page: Admin UI - Manage input forms Page: Structure - Manage Lists, Controlled Vocabularies and Authority Control Page: Structure - Automated Update of Existing Items
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	Page: Structure - Community and Collection hierarchy (or generic containers) Page: Admin UI - Change community/collection parent/child relationship Page: Give Collections/Communities short names/acronyms Page: Admin UI - Simplify Collection Creation Based on Template Page: Structure - Create the ability to place "dynamic collections" (pre-faceted view of a collection) within the community hierarchy. Page: Structure - purpose of bundle layer Page: Structure - Relationships between objects Page: Structure - Create / manage files and metadata (as an Item) Page: Structure - Support for hierarchical metadata formats (e.g. METS / MODS) Page: Structure - Metadata for all levels of object hierarchy Page: Structure - Support for derivative objects Page: Structure - Describe Individual Bitstream within an Item Page: Structure - Apply licenses to bitstreams
Enhance Basic Statistical Reporting	Primary use case description: Basic Statistics	Goal 1: Fundamentals of IR	x	Medium	Stats/Metrics - Basic Statistics (and all child pages)
Enhance Basic Preservation		Goal 1: Fundamentals of IR	x	Medium	Admin UI - Basic Preservation - Fixity Checking Admin UI - Basic Preservation - Format identification Admin UI - Basic Preservation - Format validation Admin UI - Format reporting

Priority 2 Features

Priority 2 Features	Design / Notes	Related Technical Strategic Goal(s)	Core?	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	Page: Structure - Automated Retention of All changes to Items Page: Structure - Manual Edit of Existing Items Page: Structure - Manual Creation of "New Editions" of an Item Page: Structure - Generated provenance for all added bitstreams
Enhance Search / Browse System			x	Page: End User - Enhanced access to related items Page: End User - Search for items Page: End User - Browse Page: End User - Intelligent rendering of URL's in item Metadata Page: End User - Clear distinction between different types of contributor involvement Page: Admin UI - Trigger the re-index of a collection Page: End User - Discovery and retrieval of content on mobile devices Page: Admin UI - Configure and manage browse indexes Page: Admin UI - Rebuild the discovery index Page: Admin UI - DSpace should accommodate basic index normalization Page: Structure - Create the ability to place "dynamic collections" (pre-faceted view of a collection) within the community hierarchy. Page: Admin UI - Customise which metadata fields to facet upon, search upon Page: Admin UI - Clear the OAI Cache Page: Admin UI - Rebuild the OAI index Page: Admin UI - Run media filters
Enhance Access Control	Unable to locate Jira server for this macro. It may be due to Application Link configuration.		x	Page: Admin UI - Change permissions of all the bitstreams in a bundle Page: Admin UI - Configure hidden communities and collections Page: Admin UI - Access Rights on all levels of objects within the system Page: Integration - Integration with external authentication / authorisation system Page: Integrations - Authentication through Multiple Mechanisms Page: Admin UI - Updating a Workflow group Page: Admin UI - Embargo functionality Page: Admin UI - Approval workflows

Unscheduled Features