Friday, September 3, 2010

Google Summer of Code 2010: Code merged!

Been a bit since an update, most of my updates were sent to the mailing list.

My code has been since merged into sahana eden trunk.

The code in its current state is very buggy and has issues, but most issues were fixed prior to being pushed to trunk. Those issues are mentioned in the user guidelines. It needs to be updated to reflect current issues, those that have been fixed and those that are still outstanding.

Development will continue in my branch and once I feel the feature is complete and stable, it will be merged to trunk.

Monday, May 31, 2010

Weekly GSoC Survey Tool meeting summary

The weekly meeting was held in the #sahana-eden IRC channel on Present were: Mark, Gavin, Michael, and of course whatever spectators:

What was discussed:

  • We removed some of the question types from the functional specification to simplify things
  • Discussed how michael did the ADPC _next stuff and how it can be applied to this project
  • Gavin suggested localization -- a suggested implementation is specified -- this is a "Nice to Have" as it's outside the scope of this project for GSOC.
  • Will discuss on the mailing list how best to generically support "wizard" like uis within S3 elegantly.

What's on the agenda for the next couple weeks (this week will be scarce):

  • Noodle over ways to generically support "wizards" in S3 elegantly
  • Implement the "Template" stage (page 1 of the wizard) [first milestone as per my project plan timeline]

Resources relevant to this meeting for the purpose of this summary:

  1. The functional spec
  2. The project plan timeline
  3. Meeting log [meeting ends at 0109 as per the timestamp in the logs]

Monday, April 26, 2010

Accepted to Google Summer of Code 2010: HAT TRICK!!

I have been accepted to Google Summer of Code 2010 for the third year running! This summer I will be working with Sahana Eden.

The Sahana Free and Open Source Disaster Management System was conceived during the 2004 Sri Lanka tsunami. The system was developed to help manage the disaster and was deployed by the Sri Lankan government's Center of National Operations (CNO), which included the Center of Humanitarian Agencies (CHA). A second round of funding was provided by the Swedish International Development Agency (SIDA). The project has now grown to become globally recognized, with deployments in many other disasters such as the Asian Quake in Pakistan (2005), Southern Leyte Mudslide Disaster in Philippines (2006) and the Jogjarkata Earthquake in Indonesia (2006).

The project is now being ported to Python as an experimental fork a replacement for Sahana Agasti so that the software can be extended. Sahana Agasti is written in PHP.

I will be working with Sahana Eden to create a tool to create, enter, and manage surveys. This should be a lot of fun!

Sunday, March 28, 2010

Facility Data Module v1.0 released!

It is with great pleasure that I announce the release of version 1.0 of the Facility Data Module.

It is available for downloaded via the OpenMRS module repository.

Feedback is appreciated!

Wednesday, January 27, 2010

Google Summer of Code 2010 is a GO!

Great news! Google Summer of Code 2010 is a GO!! Read the initial e-mail and the follow-up e-mail for more information!

Be sure to subscribe to the Google Summer of Code Discussion list to keep yourself informed about the program and to receive updates as they become available.


Monday, January 18, 2010

Facility Data updates

It's been a while since I last updated on the progress of the Facility Data Module. So without farther adieu here we go:

  • The relation between the FacilityDataFormSchema and FacilityDataFormSection is now Many to Many meaning that sections can now be re-used between several form schemas (or reports).
  • It now runs without errors on OpenMRS 1.5.x
The first item was a big problem that was a sore spot for this project since it wasn't too intuitive, ideally a user should be able to re-use a section. The second item was a freebie since the errors were likely all due to the incorrect modeling.

What's next on my list is the following:
  1. Allow for sections to be re-ordered within the schema (this is currently not possible and is a show-stopper.
  2. Fix up the calendar management pages -- those are horribly ugly, but this is after all a first pass, so that is to be expected right?
  3. Currently, it does not validate inputs for Numeric data types -- It need to.
  4. There still needs to be the ability to analyze the data that exists in the system to submit to funding sources; those pages need to be implemented but that is phase two of the project.
  5. There are likely other sore spots that exist that I do not see at this point and time that will be fixed at a later date.
That is all for now.