Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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
  • Action 1B: (Do we want another, post OR15 survey of the community based on Strategic Plan, Tech Roadmap & Use Case gathering?)

...

  • Action 1C: Clarify and improve the DSpace value proposition. Enhance our message and goals of the project going forward.
    • Mention establishment of the new "Marketing Working Group"

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

...

  • Action 2A: To be "lean", the DSpace technology platform should avoid duplicative functionality except where necessary to meet use cases or achieve "flexibility" goals.  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 statistical engines (Solr vs Elastic Search)
    • Examples of necessary duplicative functionality. Each of these duplicative functions would be considered in line with use cases or supporting flexibility supportive of our goal for "flexibility" (of data import/export/storage).
      • supporting multiple database storage backends (PostgreSQL, Oracle, etc.)
      • supporting multiple interfaces for deposit (SWORD, REST, etc.)
      • supporting multiple interfaces for export (OAI-PMH, REST, RDF, etc.)
      • supporting multiple external identifier schemes (HandlesHandle system, DOI, etc.)
  • 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

...

[summary of goal]

  • Action 4A: Continue to track worldwide initiatives around open access (e.g. SHARE, OpenAIRE) and any guidelines/best practices for integration. DSpace should strive to meet the needs of open access initiatives from various regions around the world.
  • Action 4B: More detailed discussions with parallel projects and initiatives (e.g. Fedora, VIVO, Hydra, Islandora) to discuss possible collaboration points, or ways that our software platforms can share data / be installed together. Find ways to use "DSpace with Fedora/VIVO/Hydra/Islandora".

 

Goal 5: DSpace will support low-cost, hosted solutions and deployments (by featuring an easy, "just works" setup)

...