Hi Bob, Thanks for your quick email response. Great to hear about the great work you've been doing and your approach to what has been a thorny issue.
My search for the launchpad blueprint has been futile. Please can you point me to that. Thanks. BTW: Does it mean OpenMRS is able to export to sdmx? If not, how can you try out your dhis funtionality? Thanks for your answers. Cheers, Ime --- On Wed, 4/28/10, Bob Jolliffe <bobjolli...@gmail.com> wrote: > From: Bob Jolliffe <bobjolli...@gmail.com> > Subject: Re: dhis-openmrs integration > To: "Ime Asangansi" <asanga...@yahoo.com> > Cc: "Dhis2" <dhis2-devs@lists.launchpad.net> > Date: Wednesday, April 28, 2010, 12:27 PM > Hi Ime > > The OpenMRS-DHIS "integration" is based around exchanging > datasets > using sdmx-hd. There has been a lot of work done on > the sdmx-hd > standard itself recently which has required some changes to > both the > openmrs module and our import export module. I hope > to be more or > less finished with our import module by Friday - the basics > are > already on launchpad, but will be more complete by then. > > The import module itself is fairly generic. The > substance of > importing lies in the transformation from an xml source to > dxf for > import. I'm still working on an appropriate place to > put those > transformations (xslt style sheets) but for the moment they > are > externally provided on the filesystem. > > So work is still on - but not complete. > > Regards > Bob > > On 28 April 2010 10:55, Ime Asangansi <asanga...@yahoo.com> > wrote: > > Hi Bob and all, > > > > Just a quick one, guys. > > Just wondering where we are on the OpenMRS-DHIS > integration. > > Is work still on? Or is it complete? > > Is there any place I could see code? > > > > Thanks :) > > > > Warm regards, > > Ime > > > > --- On Mon, 4/26/10, Bob Jolliffe <bobjolli...@gmail.com> > wrote: > > > >> From: Bob Jolliffe <bobjolli...@gmail.com> > >> Subject: [Dhis2-devs] Front end engineering ... > >> To: "dhis2-devs" <dhis2-devs@lists.launchpad.net> > >> Date: Monday, April 26, 2010, 1:59 PM > >> Looking at our ajax stuff while > >> tracking ognl issues I notice that we > >> have two copies of request.js: > >> > >> > ./dhis-web-maintenance/dhis-web-maintenance-dataset/src/main/webapp/dhis-web-maintenance-dataset/javascript/request.js > >> > ./dhis-web-commons-resources/src/main/webapp/request.js > >> > >> It looks like the dhis-web-maintenance-dataset > version was > >> "forked" > >> off the original and a few changes made. I > noticed > >> this because I was > >> trying to set the content type on a request header > only to > >> find that > >> it wasn't supported in our (two!) homegrown ajax > request > >> components. > >> Two suggestions [which are somewhat contradictory > :-) ]: > >> > >> 1. We should merge the request.js changes back > into > >> web-commons-resources taking care not to break the > many > >> dependencies > >> 2. We are already using jquery quite extensively > in > >> the frontend, > >> which has well developed and widely used ajax > >> components. Perhaps we > >> should simply retire request.js entirely. > >> > >> Thoughts? > >> > >> Bob. > >> > >> _______________________________________________ > >> Mailing list: https://launchpad.net/~dhis2-devs > >> Post to : dhis2-devs@lists.launchpad.net > >> Unsubscribe : https://launchpad.net/~dhis2-devs > >> More help : https://help.launchpad.net/ListHelp > >> > > > _______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
