Forum OpenACS Development: ACS 4 Module Services: Whats New, Merging Users, etc
I see some similar issues with site-wide/group administration and searching. Are there some standards for making modules plug into site-wide/group-wide services?
I did a cursory check of the ACS4x Tcl documentation but couldn't come up with any answers. If not, perhaps there should be.
There's no real solution in ACS4.x. Jon Griffin and I have discussed the need to come up with one. Janine Sisk (of Furfly) will undoubtably track me down and strangle me with her bare hands if we don't.
Do you have any bright ideas? My life may depend on them! :)
The challenging part will be:
- figuring out what all services there needs to be
- figuring out what the interface should be.
This makes me suspicious of the admin interface for the ACS4 (okay, so I have been busy with client work and haven't looked at it yet... smack)
;) No, seriously, many of the admin pages in ACS 4.x are seriously
weak and un-scaleable. For example, many seem to use select boxes to
pick lists of users, where the select lists shows all users on the
system. For a real hoot, try going to the "/permissions/" page. Then
try going there again AFTER you've loaded the Places module. Trying
to display all 90000 Places objects on the /permissions/ page works
well only as a way to crash Netscape...
As a quick hack to avoid ever using the /permissions/ page, I've been
sticking links like:
"/permissions/one?object_id=0" site-wide admin permission
into the upper-right "out of flow" position in my admin pages.
Of course, none of the above sins against scaleability should be
particularly hard to fix - I just haven't had the time to do it yet on
my own projects. What Carl and Don are talking about above, on the
other hand, is a genuine design problem that'll probably take some
real thought to solve nicely.
Yet again I say that the admin interface problem points to the usefulness of integrating a usability testing module with the SDM.
I think something like this would be great, it's a matter of getting a couple of people interested in doing it.
1. Centralizing user maintainance:
- Proc to delete all rows referencing a user id
- Proc to change a user id to some other id (merging users)
- Proc to list all content a user has contributed in the module user contributions)
- Proc to list "tasks" for a user. Things they need to respond to.
Thats what I was thinking about today. cheers,