15 January 2009
- Darius Jazayeri
- Justin Miranda
- Ben Wolfe
- Burke Mamlin
- Mike Seaton
- Brian McKown
- Paul Biondich
- Hamish Fraser
- Follow-up about use of Joda Time
- Interested. Need some due diligence: what does it give us (benefits)? Does it play well with Hibernate? Does it play well with Spring? Are there reasonable alternatives with a larger community (e.g., Apache commons project)?
- Mike will create a ticket. archive:TRAC-1212
- Follow-up about separating resources within the API and web layers
- Ben will make a ticket for separate message bundles, so that API can be localized independently of the web layer.
- Should we switch to Java 1.6 (per this thread)? Discuss pros/cons.
- We got around this. No pressing need at this time.
- OpenMRS should develop and focus for Java 1.5 for the foreseeable future. We will reconsider moving to 1.6 or 1.7 in the future.
- Mike's start and stop date questions
- We agree that relationship should get attributes for effective dates and the API adjusted accordingly.
- For now, we will not put start/end dates on person addresses.
- Long discussion on whether or not to put effective dates (start/stop) on person attributes. Our feeling was that person_attribute was designed to allow implementation-specific extensions of person — i.e., effectively "adding column(s)" to the person table without changing the core data model. Putting date ranges on a person attribute would alter this notion, by making person attributes more than simple columns. We therefore turned to look for alternative ways to model/store patient clinic locations as obs or somewhere else other than person_attribute.
- Paul will write a follow-up/summary to the dev list
- Mike will create a ticket: archive:TRAC-1213
- Mike will make a ticket for hashing secret password
- Ben will make ticket for enabling SHA-2 - archive:TRAC-1218