Projectdb: Difference between revisions

From OLPC
Jump to navigation Jump to search
(..)
(..)
Line 3: Line 3:
It is currently being used as our live [[contributors program]]/developers-program interface. Over the past week it has processed 100 applications from LinuxTag.
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; [[user:AaronKaplan|AaronKaplan]] and [[user:Crazy-chris|Chris Hager]] are the two current project maintainers. The codebase is currently partly open; git access is not generally available yet. The code is being cleaned up this week to accomodate important feature requests.
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, --[[User:Sj|Sj]]&nbsp;[[User talk:Sj|<font style="color:#f70; font-size:70%">talk</font>]], [[user:femslade|femslade]] and [[user:Erik Garrison|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).
The first weekend in June, --[[User:Sj|Sj]]&nbsp;[[User talk:Sj|<font style="color:#f70; font-size:70%">talk</font>]], [[user:femslade|femslade]] and [[use:erikgarrison|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).


== Roadmap & Feature Requests ==
== general db ==
A further extension of a shared database should cover information about all the data that is core to OLPC:
=== Bugfixes ===
* Make all entries editable by admins
* Fix quote/slash escaping
* Show name of requestor on the requestor-view page
** Show requestor & project info side by side on same page
* Add status options : "submitted", "shipped", "received"
* Support post-to-wiki on submission
* Support creation of new accounts / granting admin status to accounts by admins
* Basic duplicate-catching for project submissions


* projects - iedeas, development, creation; initiatives, trials, research
===Features ===
* parts - XOs, spares, peripherals, power
* Make tables sortable by column
* places - countries, cities, schools
* Support compressed view of main page, one line per entry
* people - individual teacher, developers; organizations, partners; chapters, interest groups
* Add export to csv (and xls?) of main tables/views
* Add filtering/viewing by country (for export by country)
* Add filtering/viewing by submitter / by duplicate submissions
* Separate list of all account-holders from list of project submitters
* Editing : add a "last edited/updated" field and track which admin last updated an entry.
* Backups : make a nightly backup; confirm backups b/t olpc.at and d.l.o.


=== roadmap ===
''.''


== general db ==
== 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.
A further extension of a shared database should cover information about all the data that is core to OLPC:

== 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


* Projects - ideas, development, creation; initiatives, trials, research
* Parts - XOs, spares, peripherals, power
* Places - countries, cities, schools
* People - individual teacher, developers; organizations, partners; chapters, interest groups


=== 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.


== current Use ==
A half-dozen people are reading data from the current temporary interface and hand-parsing it into xls formats to satisfy a changing process; this will later be done via xml (with xml export to B* and xml import from them for confirmation of receipt and shipping). We are working on better export formats to support the interim process.




=== Data specification for processing projectdb requests ===
The process of requesting XOs currently is passed on to B* via spreadsheet. They are working on an xml solution that will accept and generate XML lists to automate the process.
Core feature requests above aim to use the db to process a # of requests similar to those @ linuxtag, while avoiding a repeat of the usability issues found there : particularly the dup submissions, lack of wikipresence, and lack of clear timestamping or admin-updating of reqs, which makes it hard to mark all LT08 reqs as coming from that group. --[[User:Sj|Sj]]&nbsp;[[User talk:Sj|<font style="color:#f70; font-size:70%">talk</font>]] 16:26, 7 June 2008 (EDT)


{{Stub}}
{{Stub}}

Revision as of 16:18, 8 June 2008

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.



This article is a stub. You can help the OLPC project by expanding it.