Summary of the Call - July 8, 2010

[Brian]

Summary of the Call - July 8, 2010

- Experimenting with Jasper Reporting.
- Group discussion on which Reporting framework to use.
Jasper Reports seems easier to configure and is built into Spring.
It also doesn't require deploying a separate war file and is
supported by Maven while Birt isn't.
Additionally, it's possible to use Java classes and SQL to generate
the report.
It was decided that we implement the Household Book and Mortality
Rates in both BIRT and Jasper to have a more clear understanding of
what the benefits and trade-offs are.
It may be a possibility that we use BIRT as our main reporting
framework and use Jasper for internal use.
- Internal InMigrations can now have an Unknown Id.
- The dependencies in the project have been updated to use the latest
releases which may result in refactoring some classes.
The main change in in the updated dependencies is that Hibernate now
calls class level constraints automatically.
- The Relationship form has been modified.
It was suggested that the Membership form should have a field for
specifying the Relationship to the Group Head which would have
Relationship types such as son, daughter, brother, sister, husband,
wife.
Also in the Relationship form, the only Relationship type available
will be marriage (for now).
- Continuing to research how to integrate openxdata into our project.
Suggestions on how to do this is to start investigating the MoTecH
project and see how it's integrated.

Work for next week

Start shifting towards mobile development in the next few days.
- Relationship and Death for Group Head should be fixed.
- Mortality Rates and Household Registration Book implemented in
Jasper Reports.
- Should have a more clear understanding of what the benefits of BIRT/
Jasper are.
- Continue to research openxdata and integrate it into our project.