Content Management/Vision Statement

From OLPC

< Content Management
Revision as of 20:57, 21 January 2009 by Cjl (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

Vision Statement

Executive Summary

OnLine Processing of Content (codename: sara) is a content management system that accepts and catalogs media and makes it accessible to users of the OLPC Project laptops in an organized manner. The system will be simple and easy to use, store relationship information between content, and be language-portable. Content submitters can log in using OpenID to submit a wide variety of media such as images, videos, audio clips, articles, or translated versions of existing content, which will then be made available to users. All content is tagged to make it easy for users to browse related items, or find the same item in an alternate language.

Feature List

  • Accept media and files
  • View/Manage files
  • Searchable interface
  • Ontology
  • User privileges
  • File classification by tags
  • Easily mirrored onto other servers
  • Language portability

Business Case

Our product is a content management system for a non-profit organization distributing laptops to children in developing countries. There is currently no direct competition for this goal. Other content management systems may not accept content so easily, present it so simply, or be so flexible in terms of the type of content they can accept.

Schedule Overview

  • Inception Deliverables due by September 24, 2007
  • Elaboration Deliverables due by October 11, 2007
  • First Iteration to be completed by November 1, 2007
  • Second Iteration to be completed by November 9, 2007
  • Third Iteration to be completed by November 18, 2007
  • Construction Deliverables due by November 19, 2007
  • Fourth Iteration to be completed by December 5, 2007
  • Transition Phase deadline by December 6, 2007


First Iteration Use Cases - Basic Functionality (Alpha)

Search for content (End User), Download content (End User), Submit content via web interface (Content Submitter), Log in/out (Administrator, Content Submitter), Tag content (Content Submitter), and CRUD content (Administrator).

Second Iteration Use Cases - Feature-Complete (Alpha 2)

CRUD users (Administrator), Administrative search for content (Administrator), Implement ontology (System), and Browse Content (User).

Third Iteration Use Cases - Release Candidate (Beta)

Joining pieces together (better), interface work, and bug fixing.

Fourth Iteration - Final Release

Internationalization, unit testing, and bug fixing.

Budget

All resources are provided by the OLPC Project except for development machines and time. Machines are provided by us or RPI and time is donated to the project. Development machines: 4 Laptops x $2,000 = $8,000 Time: 10 Hours/Week/Person x 4 People x 15 Weeks x $28/Hour = $16,800

Note: Entirely theoretical, not actual. Class requirement.

Stakeholders

  • Our development team
  • The OLPC community

Risks

  • We aren't familiar with Python.
  • We aren't well-versed with source management tools.
  • Some lag between requests for resources and receiving the resources since the OLPC project is supplying most of them.
  • We only have one direct contact with the OLPC project so communication may be a challenge and we may not have a complete understanding of their needs.
Personal tools
  • Log in
  • Login with OpenID
About OLPC
About the laptop
About the tablet
Projects
OLPC wiki
Toolbox
In other languages