Re: Is OpenGroupware the solution for me?

> >> My first real need is therefore for a calendar for each user (3
> >> physicians and 3 beds). The possibility for the secretary to enter
> >> patients appointments. Same for the users (sometimes the physician
> >> will take an appointment sometimes it will be the secretary).
> > There is one calender in OGo,  appointments have participants and  
> > access
> > permissions (actually a nicer model then multiple calendars once  
> > you get
> > used to it).  You should be able to accomplish what you want.
> So basically, what you see in the calendar depends on your  
> permissions and the participants you are interested in seeing?
> Nice concept.

Exactly.

> So it means I can decide to see "all events for user A" or "all  
> events for users A, B and C"

Yes,  you can even filter by user A, B, C, of event types X.

> >> It must be possible to display the day with the appointments of the 3
> >> physicians and maybe the 3 beds (ideally 6 columns).
> > Not certain what you mean.
> Well, if I show in the same column (for today for exemple) the  
> appointments for 3 users, they will obviously overlap making it a bit  
> confused. It is nicer to have (for a given day) one column for user  
> A, one column for user B, etc...

I'm not certain such a view is available natively (although you could
script one easy enough).

> >> 1)
> >> How long (easy) is it to setup an OpenGroupware server on MacOSX?
> >> (taking into account my profile)
> > No idea, we are a SuSe shop.
> So, for Linux, how long to compile, setup the module, etc... just the  
> time for compiling and seting some environment variables? This would  
> imply that in half a day I am up and running?

I've never compiled OGo,  I install from the packages.  From a clean box
to a working OGo instance on SuSe 10 is about 10 minutes.

> >> 4)
> >> I am not certain I understood what process exist: is it a  single
> >> process  (unix process) handling everything or is it a kind of Apache
> >> module?
> > The OGo daemon is accessed via an Apache module.
> So there is one OGo deamon (the equivalent of an WebObjects instance/ 
> process) and one Apache module to redirect HTTP requests correctly.  
> Correct? This means the OGo daemon handles user sessions in memory  
> (as WebObjects). The OGo daemon then connects to PostgreSQL via its  
> libraries.

Pretty much,  I'm not that familiar with WebObjects.  But this seems
correct from my experience.

> >> 7)
> >> Considering my previous questions and context, which version should I
> >> start with? and how easy is it to upgrade? (for example if I start
> >> with version 1, and then want to benefit or contribute to items in
> >> 1.1, is it easy to upgrade)? Put differently, is it better in my
> >> situation to start with the lastest stable build for MacOSX or go for
> >> a previous final release?
> > If you want roles for appointment particpants which are quite usefule
> > you need to use 1.1.x, otherwise you can use 1.0.x.
> Would you say the latest 1.1.x is stable enough for the small setup I  
> need to accomodate?

I use 1.1.x in production.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBEQ6/NLRePpNle04MRAmWAAJ9jlppLkRPovgPk1Uvi2/SFQfeEtACeJYrW
fx8myOZgb/B61GsDuU65iz4=
=Ibza
-----END PGP SIGNATURE-----