Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
dev:sahana_gsoc10_ideas [2010/03/10 17:05] greg |
dev:sahana_gsoc10_ideas [2010/05/10 19:02] (current) glenn |
||
---|---|---|---|
Line 191: | Line 191: | ||
SKILLS REQUIRED: | SKILLS REQUIRED: | ||
+ | ====Sahana Module Manager==== | ||
+ | by Greg Miernicki | ||
+ | Sahana features a framework that allows new sections of the site to be written in the form of modules. Currently, this framework identifies and installs all modules that reside in the /mod folder of the site's installation. This is far from optimal as most instances of Sahana 'in the wild' do not use all of these modules. So, for example, a typical installed instance of Sahana may choose to utilize only 5 of the (currently 40) modules that come with it. The way to do this would be to uninstall/ | ||
- | ====Sahana Module | + | Preliminary work has already been done for this effort in the form of : \\ |
+ | - Module Manager interface (not completed) built into the Admin Section of Sahana \\ | ||
+ | - The specification of what constitutes a ' | ||
+ | - Aggregation of this information on the wiki will be performed by the Mentor previous to the GSoC student discussing the points, fully spec' | ||
+ | |||
+ | If the above work is completed, additional research/ | ||
+ | |||
+ | For more see [[dev: | ||
+ | |||
+ | ====Integration with Usahidhi ==== | ||
+ | by Chamindra de Silva | ||
+ | |||
+ | Ushadihi and Sahana | ||
+ | |||
+ | ==== Referential Integrity ==== | ||
+ | by Glenn Pearson | ||
+ | |||
+ | Referential integrity within a database is the defining of foreign key relationships between database tables. | ||
+ | |||
+ | It would be helpful to create an experimental instance of Sahana with (for example) MySQL, where foreign keys are defined, and any parts of now-redundant business rules are conditionally disabled. | ||
+ | |||
+ | ==== A New Protocol for Missing Person/ | ||
+ | by Glenn Pearson | ||
+ | |||
+ | In response to the Haitian earthquake, Sahana PHP has been developing capabilities to import and export missing person records in PFIF 1.1/1.2 formats, e.g., for interchange with Google and other aggregators and sources. | ||
+ | |||
+ | But this is not the only potential format. | ||
+ | |||
+ | The Phase II work, originally called " | ||
+ | |||
+ | For more, the starting point is [[http:// | ||
+ | |||
+ | Pertinent documents (both overview and technical) are [[http:// | ||
+ | |||
+ | Desirable results - | ||
+ | |||
+ | * At a technical level, a Sahana module that imported/ | ||
+ | |||
+ | * At a policy level, suggestions for what TEC should look like to support Sahana and non-US deployments (with potentially different legal/ | ||
+ | |||
+ | |||
+ | ==== Passive Synchronization of Global Unique IDs Over a RESTful Interface | ||
+ | |||
+ | If every module has a well-defined, | ||
+ | |||
+ | As an example, the " | ||
+ | |||
+ | The Sahana Foundation has been discussing synchronization of data across multiple instances. If someone were willing to define a vocabulary, a RESTful API, and methodology for exposing Consumer-Aggregator-Syndicator services it will benefit the community towards this end. | ||
+ | |||
+ | With that goal in mind, we would like to mentor a bright and motivated student who groks web service oriented architecture. In particular we seek a student who can implement passive synchronization of global, unique IDs over a restful interface. | ||
+ | |||
+ | The implementation should: | ||
+ | *Be resilient to connection failure. | ||
+ | *Be able to perform at 4K records (number of 4K records per sec on X-type-pipe) (What' | ||
+ | *Does not need to be a text based API. Binary acceptable. | ||
+ | *Function in multiple pipes, such as: | ||
+ | * Cellular | ||
+ | * dialup | ||
+ | * WiFi | ||
+ | * Cable | ||
+ | * DSL | ||
+ | * T1 | ||
+ | * T3 | ||
+ | * 10 Gigabit Ethernet | ||
+ | |||
+ | |||
+ | ==== Talking Papers, OCR and a world without data entry ==== | ||
+ | by Chamindra de Silva: | ||
+ | |||
+ | Rather than elaborate here, I would like to point to the excellent blog post by Robert Kirckpatrick that captures this idea http:// | ||
+ | ==== ORM for Sahana Phase II ==== | ||
+ | by Chamindra de Silva | ||
+ | |||
+ | Sahana requires a good ORM. Incorporate the doctrine ORM into the Sahana framework. | ||
+ | ==== Interoperability with InSTEDD RIFF ==== | ||
+ | by Mark Prutsalis | ||
+ | |||
+ | Build two-way interoperability between Sahana' | ||
+ | |||
+ | ==== Auto-Assignment of Resources | ||
+ | by Charles Wisniewski and Darlene McCullough | ||
+ | |||
+ | __Introduction__ | ||
+ | |||
+ | Upon the creation or activation of a shelter system, the essential administrative task of adequately provisioning these centers becomes pressing. | ||
+ | |||
+ | As part of the logistics module, a dispatch sub-function could be created to automatically distribute and allocate resources; both human and material. | ||
+ | |||
+ | __Proposed Wireframe__ | ||
+ | This is a first pass at a potential wireframe, intended to provide structure and facilitation brainstorming; | ||
+ | * At the starting screen you can select what you want to provision. | ||
+ | * To ensure scalability for larger activations: | ||
+ | * Shelters can be activated by group or individually | ||
+ | * Resources can be provisioned either as groups or individually. | ||
+ | * Shelters can be customized to provide special needs: | ||
+ | * Resources can be categorized to be allocated to these customized shelters | ||
+ | * // | ||
+ | * // | ||
+ | * For deploying resources, the originating location of volunteers and other resources influences the distribution algorithm. | ||
+ | * // | ||
+ | * Quality of resources is considered during allocation: | ||
+ | * // | ||
+ | * // | ||
+ | * The ability to consume information from a third party logistic information providers. | ||
+ | * // | ||
+ | * // | ||
+ | * At the end of the assignment process a report should be generated on-screen indicating where resources have been allocated and the remaining resource pool to be allocated at a later time. |