Projectdb
The projectdb (alpha name) is a database designed to capture and track requests for XOs.
It is currently being used as our live contributors program/developers-program interface. Over the past week it has processed 100 applications from LinuxTag.
Current feature requests are listed below; Aaron Kaplan and Chris Hager are the two current project maintainers. The codebase is currently only partly open, as git access is not generally available. The code is being cleaned up this week to accomodate important feature requests.
The first weekend in June, --Sj talk, femslade and erikgarrison are working on extending the curent data model to cover further aspects of projects (including the stage of completion, idea through implementation, initiatives and trials, as well as projects that require new hardware to get underway).
general db
A further extension of a shared database should cover information about all the data that is core to OLPC:
- projects - iedeas, development, creation; initiatives, trials, research
- parts - XOs, spares, peripherals, power
- places - countries, cities, schools
- people - individual teacher, developers; organizations, partners; chapters, interest groups
current use
A half-dozen people are reading data from the current interface and hand-parsing it into xls formats to satisfy a partly in-flux Brightstar process; this will eventually be done via xml (with xml export to B* and xml import from them for confirmation of receipt and shipping). This could be massively improved by a few tweaks to the code.
roadmap
bug fixing
- List the proposer's name on the proposer detail page
- Make all tables sortable by column
- Provide exports of any viewed table to csv (or xls?) as well as B*-xml
- Show the date of application and of last update
- Fix the apostrophe- and slash-escaping bug in form data
features
- Let admins create new admins or new accounts by email
- Let admins see all users on the system; separate from the list of people who sign up and submit a project
- Show users their own profile with more active focus on the status of their applications (or the fact that they haven't submitted one yet!) and a visualization of the timelines they suggest'
- Ask users to define fixed dates, in addition to durations, for projects. Expand data model accordingly
- Add both personal and project mailing addresses and phone #s.
