Versions Compared

Key

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

Table of Contents

Candidate Features for DSpace

Info
titleFeature Categories

 Features have been grouped into rough "categories" as follows:

  • Structure: Features that relate to the architecture/structure of content within DSpace
  • Administrative: Features which are mostly administrative functions/activities
  • End User: Features relating to how end users interact with the system (deposit, download, search)
  • Integrations: Features which are either used by external systems (or programs) or interact themselves with an external system
  • Stats/Metrics: Features relating to metrics or statistics around content and its usage

...

Note
titleFormula for "Survey Average Importance"

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)

  • Very Important = 10 points
  • Moderately important = 5 points
  • Not important = 0 points

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

 

Non-Functional Goals for DSpace

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

(needs better definition)

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 dev/tech 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.