Content Management/Supplemental Specifications

From OLPC

< Content Management
Revision as of 03:30, 16 March 2008 by Cjl (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

Functionality

  • File Parser - Accept content and sort appropriately into database.


Reliability

  • Accurate search results - Brings up all results that contain search terms, ordered by relevance whenever possible.


Performance

  • Quick Load Times - 3 Seconds on a Broadband connection (for text and small images)


Supportability

  • Should be localizable - Localized language templates can be submitted to support multiple languages.
  • Install by copying files and running a script


Implementation Requirements

  • PostgreSQL Database - Developed with version 8.2.5. Anything newer should be fine.
  • Up to date Python Interpreter - Developed with version 2.5.1. Anything newer should be fine.


Priority

  1. Up to date Python Interpreter
  2. PostgreSQL Database
  3. Localization
  4. Accurate search results
  5. Quick Load Times
  6. File Parser
  7. Install by copying files and running a script

Number 1 and 2 are must-have functionalities. The rest will be implemented if there is enough time.


Rationale

Ranking of supplemental specifications was done with the user and development in mind. If the system is not developed the user has no product so the Implementation Requirements were given highest priority. The localization and performance aspects were given next highest priority since they are the interface between our product and the client. The parsing and installation script were given lowest priorities because they only make it easier on the backend.

Personal tools
  • Log in
  • Login with OpenID
About OLPC
About the laptop
About the tablet
Projects
OLPC wiki
Toolbox
In other languages