|
From: Lonny M. <lx...@nc...> - 2001-01-30 21:03:15
|
Hmmm, I'm not entirely sure the xml2ct won't choke if it doesn't find the info in the control bundle. As for the rest of the curation tool, I don't think it is used anywhere. Put up a the new control bundle download on genesoup, and I'll test the curation tool and let you know if we need to fix it before you commit the changes to genex. Lonny ----- Original Message ----- From: Jason E. Stewart <ja...@op...> To: <gen...@li...> Sent: Tuesday, January 30, 2001 10:04 AM Subject: [GeneX-dev] [Q]: GeneXML <==> Curation Tool > Hey, > > In the control-bundle we ship a list of the current groups in the > GroupSec table. With each groups comes a list of that groups > members. It turns out that this is a problem for the new XML API. > > I doubt that the CT is actually using this group information for > anything, is it? I would like to remove that information completely > from the control-bundle. Although it is not a security risk (we are > not giving out login names or passwords) it is not anyone's business > who is currently registered as a user with NCGR, and so it shouldn't > go out in the control-bundle. > > The problem that I would like to fix is that currently the group > members are listed by their contact fkey, and not by their usersec > fkey. I want to use the XML API to do updates of the DB, and I need it > to accurately reflect the state of the DB, so an update of the > GroupSec/UserSec information is only possible if that info is stored > in GeneXML. > > jas. > > _______________________________________________ > Genex-dev mailing list > Gen...@li... > http://lists.sourceforge.net/lists/listinfo/genex-dev > |