Jim, can you add this to the Wiki under "data importers API" in say, devel-ref-misc ?
Thanks, Karsten On Mon, Feb 14, 2005 at 09:52:52PM +1100, Ian Haywood wrote: > > Karsten Hilbert wrote: > > >No it does not. LDT does not specify a coding system. In fact, > >no coding system is even used. > OK. The schema makes more sense now. > > Can I propose a super-simple API for data importers: > all importer modules in client/importers define two functions > > accept_file (file) > > this makes a Python file object, and returns > - True: I successfully imported this file (unmatched patients don't > mean > unsuccessful) > - False: I don't recognise this format, try another importer > - exception: I recognise the format, but there is a serious problem > (corrupted file or database error) > > and if this is a results format: > manual_match (person, fragment) > - person is a gmPerson object > - fragment is the file-fragment of unmatched data saved in > lab_result_unmatched > again, returns True/False/exception as above > > Then, Gnumed can respond to file drag'n'drop events (stupidly easy in > wxPython), and try to import it. > (plus a command-line version to run from procmail, fetchmail &c) > If no importer recognises it, we can pop up a dialogue to add it to the docs > server as an "opaque" file. > > Ian > > _______________________________________________ > Gnumed-devel mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/gnumed-devel -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346 _______________________________________________ Gnumed-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnumed-devel
