Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Warning
titleRough Draft of Product Plan

 This "Product Plan" is a very rough draft. In fact, it's not yet even a fully realized "plan" (within with a timeline or schedule). It is still more of an analysis of possible feature or use case gaps within the DSpace platform. Once this analysis is completed and a DSpace Governance model is established, a Product Plan timeline and schedule will be developed by the forthcoming "Product Planning Group".

...

The following table represents a list of candidate features (and corresponding use cases) that DSpace software may wish to implement. They have been sorted by average ranking from the 2014 DSpace Vision Survey results (see Survey Average Importance), in order to show which features are of higher highest importance to our community members. Each feature has been grouped into a rough "Category" (see Category descriptions), based on the part of the overall system it relates to. Finally, we've performed a rough analysis (based on corresponding use cases) of whether each feature has been implemented/achieved within the current DSpace platform (see Status Explanationsexplanations).

Overall, this table provides a way to visualize many of the highly ranked "use case /or feature gaps" which have not yet been met within DSpace, and which likely should be prioritized for future software releases.

...

The following table describes high-level, non-functional goals which DSpace software should strive to achieve. These "non-functional" goals do not map directly to features or functions within DSpace, and in fact, some goals may be subjective in nature. However, they are perceived as highly important in order to continue to maintain and grow our active, open source community of users and developers.

Non-functional GoalUse Cases / Details
Easy to install / deploy
Easy to upgrade
  • "auto-upgrader" option? (script to upgrade, or it auto-upgrades data/configs when you load the new WAR, similar to Atlassian tools)
  • Store configuration properties/options in database
Scalability / Performance

Some Suggestions:

  • Uploading/Processing content in DSpace should not be bound to size of content
  • DSpace should strive to operate in with constant memory usage footprint during all operations.
  • DSpace user experience should not be performance limited by number of Communities, Collection, Items and/or Bitstreams
  • Support Alternative Assetstore Technologies
  • Support Many Database Vendors
Attractive to new developers
  • Opportunities to learn / contribute
  • Adopt Current and Industry Standard Technologies
  • Good developer and technical documentation
  • Supportive community
Attractive to new Repository/Content Managers
  • Good user documentation
  • Supportive community
  • Usage best practices / guidelines
  • More UI-Driven Admin Functionality
Avoid centrally maintaining duplicative codebases/functions
  • Standardize on a single out-of-the-box UI 
    • other third-party UIs may be offered, but would not be centrally maintained
  • Centralize common UI Actions / Commands and consolidate into Business Tier.