Page History
...
Features | Design / Notes | Related Technical Strategic Goal(s) | Core? | Complexity | Use Cases | Volunteers | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Non-functional: Easier Installation | While DSpace's installation process continues to improve, it is still highly manual in nature. We should investigate ways to provide an "easy installer" which could potentially even auto-install and configure prerequisites such as Tomcat, Postgres, etc.
| Goal 5: Low cost, "just works" | x |
| |||||||||||||||||||||||||||
Non-functional: Easier Upgrade Process | While DSpace's upgrade process continues to improve, it is still complex with regards to local customizations or theme changes. We should investigate of simplifying the upgrade process, by alleviate the manual process of merging in local changes/tweaks where possible.
| Goal 5: Low cost, "just works" | x |
| |||||||||||||||||||||||||||
Advanced Usage Statistics | DSpace currently only provides basic statististical reporting functionality. We should investigate ways to provide enhanced, highly detailed reports for users who need them. Likely, this will be implemented as an optional module available via a module registry.
| Goal 3: Can be "extended" | High |
| |||||||||||||||||||||||||||
Theme management in Admin UI | 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.
| Goal 5: Low cost, "just works" | x | High |
| ||||||||||||||||||||||||||
Enhance Versioning | DSpace provides an optional, basic Item versioning capability. However, this versioning capability is limited in nature, and not yet fully integrated into all DSpace tools and interfaces. We should find a way to enhance item versioning, and make it more embedded into the system (and API) overall.
| x |
| Cineca | |||||||||||||||||||||||||||
Replace "Bundle" object with Metadata or similar | 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).
| Goal 2: Lean and flexible | x | Medium | |||||||||||||||||||||||||||
Advanced Preservation | DSpace currently only provides basic preservation tools (format identification, checksum verification, etc) out-of-the-box. We should investigate providing enhanced preservation options (or integrations) for users who need it. Likely, this will be implemented as an optional module available via a module registry.
| Goal 3: Can be "extended" | High | ||||||||||||||||||||||||||||
Enhance Search / Browse System | While DSpace's search/browse system continues to improve, there are still ways we can improve the user experience of finding items within DSpace.
| Goal 1: Fundamentals of IR | x |
| |||||||||||||||||||||||||||
Enhance Access Control | DSpace's access control system (which manages authentication and authorization) is a custom solution that is now nearly as old as the software platform itself. While it functions well enough as-is, replacing it with a comparable third-party, open source AuthN/AuthZ system would simplify our codebase and ongoing maintenance.
| Goal 1: Fundamentals of IR | x |
| Cineca | ||||||||||||||||||||||||||
Single Approval Workflow system | DSpace currently has two approval workflow systems:
We should consolidate on a single Approval Workflow system, likely the Configurable Workflow, with sane defaults | Goal 1: Fundamentals of IR | x | ||||||||||||||||||||||||||||
Enhance Approval Workflow capabilities | 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.
| Goal 1: Fundamentals of IR | x |
|
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.
...