[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] client menus GNUmed > Preferences vs GNUmed > Master
From: |
Jim Busser |
Subject: |
Re: [Gnumed-devel] client menus GNUmed > Preferences vs GNUmed > Master data |
Date: |
Wed, 21 Sep 2011 10:51:46 -0700 |
On 2011-07-25, at 4:47 PM, Karsten Hilbert wrote:
>>>> Is it correct to expect that all settings which would be set via
>>>>
>>>> GNUmed > Preferences
>>>>
>>>> would be user specific, whereas settings or alterations made via
>>>>
>>>> GNUmed > Master data
>>>>
>>>> would be praxis-wide (in common to all users)
>>
>> I think this is kind of separation would be helpful to users.
>>
>> if we determine that it is not correct, the exception could be a case to
>> relocate the option inside the other menu.
>>
>> Also it may be future-desirable (wishlist) that the stuff under Master
>> data be unalterable except by knowing gm-dbo password.
>
> Sounds fairly reasonable.
>
> Karsten
I am wondering whether per-user preferences should be confined to
GNUmed > Preferences > UI interface
whereas maybe
GNUmed > Preferences > List configuration
GNUmed > Preferences > Database
GNUmed > Preferences > Client parameters
GNUmed > Preferences > External tools
GNUmed > Preferences > EMR
should be praxis-level (if not already) and if so relocated (post 1.0) under
GNUmed > Master data
where authorization should require to supply the password for gm-dbo?
??
Would the above be orthogonal to workplace settings and configs, or do these
overlap (or can such configs over-ride what is in the backend) ?
-- Jim
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Gnumed-devel] client menus GNUmed > Preferences vs GNUmed > Master data,
Jim Busser <=