This "Product Plan" is more of an analysis of possible feature or use case gaps within the DSpace platform (based on the 2014 Vision Survey). It is NOT a true "Product Plan". |
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 highest importance to our community. 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 explanations).
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.
|
Features have been grouped into rough "categories" as follows:
|
- Arguably, DSpace meets most major use cases already. (However, there still may still be areas for improvement or enhancement.) - DSpace meets some of the major use cases, but there are other major use cases which it does not yet meet. - DSpace does not really meet these use cases, yet. |
The "Survey Average Importance" represents average importance ranking of all respondents for a single feature from the 2013-14 DSpace Vision Survey (Survey results linked off of: DSpace 2013 Vision Discussions)
So, for example, "Community and Collection Hierarchy" had 50 respondents rank it "Very important" (10 points each), 37 rank it "Moderately important" (5 points each), and 6 rank it "Not important" (0 points). This is an average score of ((10 x 50) + (5 x 37)) / (50 + 37 + 6) = 7.37 average (which is midway between a "moderately important" and "very important" ranking) A spreadsheet was used to calculate all average scores. See the attached DSpace_Vision_Survey_Feature_Rankings.xls |
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 Goal | Use Cases / Details |
---|---|
Easy to install / deploy |
|
Easy to upgrade |
|
Scalability / Performance | Some Suggestions:
|
Attractive to new developers |
|
Attractive to new Repository/Content Managers |
|
Avoid centrally maintaining duplicative codebases/functions |
|