Re: [Phpgroupware-developers] integration of admin-addressbook-calendar-HR

[Alex (LEX) Borges]

I think this is good too, i also dont see the posibility to have a
many-one relationship on that one. The point is, the account's backend
is something you may not want to go and change that lightly since it can
be LDAP, IMAP-SQL, SQL ... i dont know, it sounds like your position is
the straightforwardest, but not necesarily the simplest to implement. 

DISCUSS EVERYONE!

In any case, i think this is a critical feature, i think it can open so
many posibilities for all apps, at last, a central repository for user
data -all of the users data!, GROUPWARE user data, such as department,
phones...etc.- AND it will simplify the entry of phpgw to other's suites
markets that use this feature as their gratest leverage. I mean, the #1
bitching i get is that when MSCE Admin #1 added a user to their
exchange, that data was organizational and automatically deployed to all
apps (that is, outlook, samba access, proxy, accesible in word....etc.).

The simplest thing, like having the addition of users tied into putting
in all their organizational data (also deleting when the user is
deleted...etc.), will shut them up.

Other things to think about, INSIDE phpgw is that, finaly, at the
calendar we could invite ppl from the inside of the organization (phpgw
users) and from the outside of the organization (any addressbook entry)
all this GREATLY simplified by having a way to differentiate both kind
of addressbook entries (system, non-system) in the api. 

Another goal that jarg is trying to achieve is the org-person separation
as is in the DCL schema and as proposed in bjonsohn's entry in the
wikii. Im not shure weve compared them but id be delighted if bjonsohn
took a look into the DCL schema and tell us if it works for him.We all
should!


So, we are killing all birds from one shot, we just need a little bit
more involvement. Jarg is here to implement this features, he has the
time and good experience in professional development, u guys please help
him out.



El vie, 13 de 06 de 2003 a las 19:34, Michael Dean escribió:
> Perhaps I'm misunderstanding you, but I believe you should achieve the
> relationship by placing a reference to the contact record on the user
> account record (i.e., user has a contact record).  In doing that, you
> guarantee a user has only one contact record.  Going the other way, a
> user could have multiple contact records, which is not desired.
> 
> Also, I have posted a link to the DCL contact schema that is used by GNU
> Enterprise and will be supported by DCL in version 1.0.  I believe the
> FSF is using tools created by GNUe developers that rely on the schema as
> a base for their contact management as well.
> 
> I think it really needs serious consideration by phpGW for adoption as
> we can share the same base schema across all of these wundebar projects.
> 
> On Thu, 2003-06-12 at 23:51, Jonathan Rivera wrote:
> > Hello guys,
> > 
> > talking with lex, i have been thought that we can have a good system of
> > handling of users, who allows us to integrate the users of the system to
> > addressbook and that also it allows us to use those same contacts in
> > calendar.
> > 
> > For example, it would be very useful to be able to say in calendar,
> > invites to this event to the members of this group and that included all
> > the members or can to do that same one in the mail,
> > 
> > I believe that if we modified a little the API of PHPGW this would
> > facilitate much the things.
> > 
> > What I have thought to do is:
> > 
> > 1.Add a new field to the table of addressbook
> > 
> > - account_id: would be the same of phpgw_accounts, in order to  be able
> > to relate the contact information to its user of the    system, you go of
> > phpgw_addressbook would continue being the key  in that used table and
> > this would be one for when a contact is         not a user of the system.
> > 
> > 2.Add a new table with two fields,
> > 
> > - id: would be the same of phpgw_accounts
> > - id_addbook_entry: would be the same of phpgw_addressbook this table
> > would use it to be able to define and to personalize who I want that
> > they appear like my contacts, and of being able to relate easily
> > when it wants to use the groups.
> > 
> > 3.Modify the code so that it is possible to have this integration, this
> > would imply to modify the API, so that all this works in calendar,
> > addressbook and the module of admin that it registers to the system
> > users.
> > 
> > 4.Modify the part of addressbook, i could implement the suggestions that
> > are in wiki on separating the table of phpgw_addressbook.
> > 
> > The advantages that I see are that really we would have a system of
> > users and contacts, and the HR application would be only a front end of
> > these tables.
> > 
> > I think also to make the support for LDAP, but in this moment i only think
> > on the database module, any suggestion are welcome.
> 
> 
> 
> 
> _______________________________________________
> Phpgroupware-developers mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/phpgroupware-developers