Page History

• 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.

• 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

• Stats/Metrics - Advanced Statistics
• Others under "uc-stats-metrics" label

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

• Ranked lower in 2013-14 Vision Survey

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

• See various unmet use cases regarding "Access Control"
• Also see
  

  Jira
  server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-1566

DSpace currently has two approval workflow systems:

1. 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
2. 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:

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.