I am going to offer you advice about how to run an online community for an alumni association: simplify. Complexity is intoxicating, but simplicity is useful.
I set up an alumni association website, isu-usa.org, to have ISU alumni share their contact info with each other. Our mother institution, ISU, had set up a site in 2007 to do this, but... let's say... that... it is not the most useful... thing. (See that? Restraint. /twitch)
My initial take on setting up isu-usa.org profiles was to request the same data that the ISU site requested. Add to that a request from an alumna to also share our educational backgrounds, and ISU*USA profiles collected data from 42 fields. (Fields such as first name, last name, email address, etc.)
What a waste. Who cares? On Friday I overhauled the profiles. Goodbye, useless data. I didn't tell anyone. They didn't care. Who is "they?" Alumni weren't using the site. It was like a personal site, but sadder since it was meant to be used by others.
First I decided which fields were being transferred to the new profiles. Friends, let me tell you: 42 is the answer to everything except keeping alumni connected. Now the magic number is 14 fields. This accomplishes all of the professional and social networking that is needed.
Then came manually transferring the information to the new profile database. This can be done automatically, but I wanted to verify that the transfer happened correctly, that fields which alumni requested to be private would remain private -- or in this case, deleted, since there is no such thing as private contact info anymore. Either a phone number is posted for all alumni to see, or it isn't posted.
Next up is inviting the alumni back. I think they will appreciate the new simplicity -- not that they'll appreciate it outright, but it will be less distracting.
The lesson here is that unnecessary complexity is unnecessary. Decide what you need to know. Stop there.
That site still has 99 problems, but at least profiles ain't one.