April 19, 2013

posted Feb 6, 2014, 12:11 PM by William Matson   [ updated Feb 6, 2014, 12:19 PM ]
Attendees

Rodger Huang, Eric Jahn, Tony Zhang, Bob Lenhard

Action Items
  • API Status - Eric reported he had squashed client get and update bugs (tickets 19 and 20). Verification was still needed on these. The search bug in ticket 21 had been verified fixed. The bug described in ticket 23 had been addressed but the fix needed to be verified. Several enhancements tickets were still in the queue but Eric said they did not appear to be critical. Work on the shelter occupancy API was to begin next. So, in summary, we are waiting on verification from Beini that items 19, 20, and 23 are squashed. Eric said that as of this date, known API issues are resolved, so he is looking at occupancy to be the next API task to complete. Eric mentioned possible Oracle Open-XDS interoperability testing with our completed occupancy API.
  • OPENHMIS Schema - The team was waiting for Bob’s ERD to look at the occupancy application. Rodger agreed to review tables. He would pass his questions back to Bob. After that the ERD would be shared with Eric, who would add the ERD to the wiki and see what comments would come in. Bob said he is releasing the ERD soon, as an ER Master (.erm) file and as an image file (.jpeg or .png) to Eric and Dave. Eric wanted to be sure the ERD does not contain any proprietary information and that its publication had internal signoff. Rodger responded that OpenHMIS' objective is to support the HMIS standards (only) in an open environment. Since standards are public, there was, by definition, no proprietary information in the ERD. Eric said he's not so concerned with it being perfect, as this is just an initial release for wider public review/modification over time, and so we can start using it. Only consideration is that once it's released, its in the public domain. Bob said this shouldn't be a concern since it's just HUD mandated data standard fields, but he'll verify with Bill before releasing. note: in MySQL, if a view is based on two tables, you can not update/insert/delete this view, MySQL doesn’t support this, this is a critical issue, we need verify and need re-design our OpenHMIS approach?