Forum OpenACS Development: What we telll other users about you
You're right, it should be on our to-do list to make this page make sense again.
I argue that having this information about users is the most valuable part of OpenACS (although I agree that the output you use as an example is very verbose and not very useful unlinked... which can be changed). You should look at the page "what we tell other users about you" as a resource for community builders that can be tapped as needed to tell more about individuals of the community. We are talking community software Ben... removing the links between user and contributions for the sake of simplicity would be a major mistake. To promote community there must be a way for members to get to know one another and what a better way to get to know one another online than over contributions? Supporting ways for individuals to get to know other members of the group is important. A community suffers otherwise. Of course in some situations you must be careful about what you (as a community builder) share about your users (which makes the fact that the data is unlinked a safe default). I would like to point you to the "Community building vs. privacy in online learning(1)" discussion on the dotLRN boards as an example of such a situation. My conclusion: I think what you are looking for is an option to modify the display of this data without having to modify code, I am correct?
I think Ben's point (and a good one) is that the actual implementation was shite.... I think we agree there's value in the idea.. its just that at the moment all it provides is a long list of (largely) useless pap....
Some kind of interface that allows admins to decide what kinds of linked info should be shown sounds more sensible.
We should "make this page make sense".
Leave it to Lars outline the essence of and the solution to the problem with five words or less.
Kewl.. we're all in agreement then.... bloody hell.... is that a first in these forums... ;)
When I try to tell people about what community software is, I use Amazon.com's functionality (which is actually a suggesion of Philip's). I would not be surprised if Amazon's db servers have as much if not more user contributed content as editorial content. More than once I've ended up purchasing a book that I learned about from an entirely unrelated review of another book. This was because I was able to follow a trail of user contributed content.
This functionality is, of course, the same that exists at photo.net and at here. The problem, as Simon says, is that in oacs4 it's total crap.
Perhaps this should be another item that use-case experts should take on as a design task?
So the TODO item should be something along the lines of working towards fleshing out the service contract used by profile provider and user profile and adding code to packages to supply the necessary items.