Page History

...

Action 1A: Verify and validate the needs of a "modern institutional repository". This is instrumental in formalizing the value proposition of DSpace.
- This activity has already begun part of the 2014 Vision Survey and Use Case gathering by DCAT. However, the gathered use cases are still being analyzed and prioritized.
Action 1B: Survey the community on Technology Roadmap / drafted feature rankings
- Ranking of features or validation of our Technology Roadmap
- Also an opportunity to possibly gather volunteers for specific feature projects
Action 1C: Identify minimum set of functionality/features for 'IR-core' and refactor codebase to provide this. This core may not be functional as-is, since it may require plugins that aren't extensions (e.g. authN)

Related Sustainability Action (This needs to be eventually moved to a "Strategic Plan - Sustainability", to be created)

Action: Clarify and improve the DSpace value proposition. Enhance our message and goals of the project going forward. The DSpace Steering Group is working towards establishment of a new "DSpace Marketing Working Group" to help with this effort

Goal 2: DSpace will be "lean", with agility and flexibility as primary goals

...

Action 2A: Converge on a single, out-of-the-box user interface (UI). DSpace will no longer be released with multiple User Interfaces (JSPUI vs XMLUI). A single user interface should be developed as DSpace's out-of-the-box UI. Early discussions on the requirements of this single UI (and some brainstormed candidates) are at Brainstorms on a Future UI.
Action 2B: Converge on a single, out-of-the-box search/browse system. DSpace will only support Apache Solr for search/browse, and the older, deprecated Lucene and DB search/browse system should be removed.
Action 2C: Converge on a single, built-in statistical engine. DSpace will only support a single, built-in statistical engine (based on Apache Solr), and support for Elastic Search statistics should removed or migrated to an optional module. Support for Google Analytics will be retained, as it's an optional integration with an external statistics engine.
Action 2D: Develop a basic User Interface "style / layout guide". In order to ensure a consistent user experience across all pages/features within the User Interface, we should provide basic guidelines for layout and styling of common page elements, etc. Examples may include basic guidelines for how errors/warnings/notices should be displayed, what class(es) to use for types of buttons, etc.

Related Community Action (This needs to be eventually moved to a "Strategic Plan - Community", to be created)

...

...