I’m preparing to roll BuddyPress out on Blogs@Baruch later this month, and I’ve grown a little concerned about the implications of doing so. I thought I’d write up some of my concerns and see if the Internets has anything wise to say about them.
Our goal in using BuddyPress is to try to draw out and congeal an academic publishing network out of the various work that’s being done across the system. We hope to give students a platform to track their work over their careers at the College, to make connections with students with similar interests, and to cultivate a profile in a space they’re somewhat familiar with that we can support and that they can build as they desire. But I’m anxious about a few things.
First, we already have more than four thousand users on Blogs@Baruch, and the vast majority of those accounts were created for course-based blogging. I’m uneasy about turning on profile pages for users who never used the system for that purpose, without their knowledge. My current plan is to send an email out to all users when we turn on BP with instructions about granular control of profile pages. But, as far as I know, that control can only be so granular: with BuddyPress Profile Privacy you can set privacy on a field-by-field basis, but you can’t lock a whole profile page down. I’m hoping Jeff Sayre’s Privacy Component, which apparently is nearing a second beta, can help solve this problem. We’ll be registering incoming first year students for Freshman Seminar and instructing them on how to use the system beginning in August, and we’ll keep Profile pages set to “open” for new users from that point forward (we’ll be updating our woeful Terms of Service as well). I think it might make sense though to lock-down already existing accounts and outreach to those users with details about BuddyPress’s purpose and instructions on how to manage their profile privacy. I’m uncertain about this, though, both the ethics and how I’d manage this technically.
Second, I’d like for the primary engine of Blogs@Baruch to continue to be course-based blogging. BuddyPress, however, elevates the social networking function to equivalence with the blogging functionality of a WP-MS installation. We’re not building ePortfolios like our friends at Macaulay and don’t have the resources to closely support the development of profiles on a system as big as ours. And I certainly want to avoid the creepy treehouse factor, which is an issue with incoming Freshman. I just want students to use BuddyPress@Baruch to connect with each other around interests and academic work. So there are a few spots where I’d like to make some choices or changes that could nurture that understanding; for instance, I don’t think I’ll have a link to the members directory from the front page (but have it publicly accessible via internal links); I’ll hide the BuddyPress admin bar for logged out users; and, I’d like to hack BuddyPress so that upon log in, instead of landing at the front page of the home blog, users land at the Dashboard for their primary blog. Any other ideas?
Third, I have to revisit our registration process. In most classes, we use DDImportUsers to bulk register new users. Our most technologically capable faculty members can handle the intimidating two-step of a “self-registration” and the addition of Andre Malan’s “Add User to Blog” widget. Now, with BuddyPress functionality turned on, registration can become more complicated and require more information, which is fine for self-registering users but potentially problematic for those who are bulk-added. The bulk process also only creates new accounts, which I’ve been struggling with for some time; existing users need to be added to new sites individually, and to do so you need both a username and an email address (if I had my druthers, the DDImportUsers plugin would be able to check a list of newusernames|newemailaddress against the user_email field in the wp_users table and if a email address exists, add the user with that address to the individual site… and then to go on to register all the new users).
As the system grows, this is becoming a bigger problem since every semester a higher percentage of Baruch students have accounts on the system and find their way into new classes that use it. In an older version of WPMu you were able to add users to individual blogs simply with an email address, which was preferable because the cross-referencing is a pain. But that pain is balanced on the other side by the agita that would be caused if nervous first-time blogfessors are made to manage a multi-step registration process. In the past, I’ve taken the pain on in exchange for the benefit of drawing more users onto the system, and it’s been a good trade. I’m not sure yet how BuddyPress fits into this equation and how it will impact my overarching goal of easing the registration process, but wanted to get the issue out there. In the long term we’re looking at LDAP integration, but we’re not there yet. One solution is BP Group Blogs; but that creates additional steps in the registration process and we still want to make things as sleek and streamlined as possible.
These are my concerns for now, and I’m sure there’ll be more to come… any feedback, questions, and exchanges from out there in the wild are welcome and greatly appreciated.