Re: [Gnumed-devel] Data packs

[Karsten Hilbert]

On Mon, Aug 29, 2011 at 01:23:55PM -0700, Jim Busser wrote:

> >> should the menu be renamed
> >> 
> >>    Install / update data pack
> >> 
> >> ??
> 
> But as it currently stands, the menu says 'Install" but it
> is not GNUmed which makes the decision to run install, this
> is (via this menu) user-initiated.
> 
> Therefore it is completely reasonable that the way that a
> praxis would update an already-installed pack would be to
> re-run a (newer) installer.
> 
> Besides, you already answered that
> 
>       GNUmed > Master data > Update ATC
>       GNUmed > Master data > Update LOINC
> 
> are to be subsumed under
> 
>       Install
> 
> so it may as well be
> 
>       Install / update data pack
> 
> even as we know the data pack script is going to
> eventually need to be smart enough to add vs update existing
> vs how to "obsolete" previously-installed reference data.

So what you are suggesting is consoling the user by telling
them they can use this menu item to - at their discretion -
"install" or "update" data packs while in fact the only
action they can ever take is to "install" ?

The "Update ATC/LOINC" might just as well have been "Install
latest ATC/LOINC" and be no different. However, there may be
several data packs for ATC and/or LOINC now so the user can
opt to install one or more some of which install processes
will overwrite data while others will install additional
data (or in fact remove some).

When you hit "Update data pack" you'd expect to see a *list
of already installed packs* and be enabled to select from
among them in order to effect them being upgraded. No such
option exists. Once you installed a data pack there's a
cognitive disconnect as far as GNUmed is concerned. It keeps
no memory of what you installed (and thus cannot offer to
update).

There's no technical difference between a data pack you
already installed (you can install it again and GNUmed won't
care) and one you did not yet install.

That's what I mean by self-contained: packs need to be set
up in a way that they can be "installed" even if they
already exist in the target database (in which case they'll
mostly simply do nothing).

Karsten
-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346