Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!tut.cis.ohio-state.edu!ucbvax!VTVM1.CC.VT.EDU!VALDIS
From: VALDIS@VTVM1.CC.VT.EDU (Valdis Kletnieks)
Newsgroups: comp.protocols.iso.dev-environ
Subject: Re: How Serious are we about running quipu?
Message-ID: <9004122051.AA21818@ucbvax.Berkeley.EDU>
Date: 11 Apr 90 17:20:31 GMT
References: <uhccux!munnari.oz.au!metro!news@ames.arc.nasa.gov>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: Virginia Polytechnic Institute
Lines: 27

On 11 Apr 90 02:58:37 GMT you said:
>How serious are you about running quipu?

Here at Virginia Tech, we are quite serious about running quipu.
We are in the process of loading our entire personnel file into it,
and are putting into place mechanisms for timely update of the data
(Probably will be once-a-week updates for now, we are aiming for
real-time online updates in the future.

Eventually, we plan to have some 6,000 employee entries and some
23,000 student entries in our quipu database, and to use this as the
central "people" database for all functions.

One of our major problems is that we have a fairly large number of
locally defined attributes that we had to add to make it fly politically
(Using quipu as "just a phone book" didn't sell), and most of these
attributes have fairly long ACL lists defining which offices and
users can read/compare/etc the entry.  The end result is that we end up
with 70-line EDB entries, 45 lines of which are ACL lists.  It would be
*quite* helpful if it were possible to "default" an ACL list for a given
attribute, which would cut the size of our EDB entries down by literally 60%.
Steve Kille has informed me that he's considering the problem, but I
have no idea if/when we will see C code to implement a solution.

                                  Valdis Kletnieks
                                  Computer Systems Engineer
                                  Virginia Tech