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. However, the gathered use cases still need further analysis, cleanup and prioritization
Goal 2: DSpace will be "lean", with agility and flexibility as primary goals
[summary of goal]
- Action 2A: To be "lean", the DSpace technology platform should avoid duplicative functionality except where necessary to meet use cases. Where unnecessary duplicative functionality already exists, the technology team should choose a "best option" solution, or propose building a new solution when a "best option" does not exist.
- Examples of unnecessary duplicative functionality
- maintaining multiple User Interfaces (JSPUI vs. XMLUI)
- maintaining multiple search/browse systems (Solr vs. Lucene)
- maintaining multiple built-in statistics engines (Solr vs Elastic Search)
- Examples of necessary duplicative functionality
- supporting multiple database backends (PostgreSQl, Oracle, etc)
- supporting multiple interfaces for deposit (SWORD, REST, etc)
- Examples of unnecessary duplicative functionality
- Action 2B:
Goal 3: DSpace will include a "core" set of functionality that can be "extended" (think plugins) or have "hooks" (integration points) to complimentary services/tools
...
Overview
Content Tools