|Social Prototyping Project Index edit|
* LDSTech Conference 2011 projects
The Social Dashboard is a centralized platform to administer official Church accounts on a variety of social networks. This should be a secure way for authorized LDSAccount users to manage these official accounts without using personal social network accounts.
|To Do: Reorganize this page into more smaller, more intuitive sections|
This is an LDS Java Stack project. If you want to learn to use Facebook and/or Twitter APIs, we want your help. The presentation layer is web 2.0 using ajax (jquery/jqueryui).
When someone is an administrator on a Facebook page, for example, they must use their personal Facebook account to login and manage the Facebook page. If their personal account is hacked, the hacker can use that account to deface whatever Facebook pages that user could administer. That poses a significant risk for official Church Facebook pages. The social dashboard aims to prevent this situation.
First, LDSAccount users will have to be given the permissions as to which Facebook pages, Twitter accounts, etc, they can access, and what they can do on those pages/accounts. When a user logs in to the Social Dashboard with their LDSAccount, they should be able to do some combination of the following (based on their permissions):
- post updates/links/etc
- moderate comments
We'll need to create an interface to administer ACLs for social accounts. We'll need to be able to grant granular permission per social account to particular LDSAccounts. We might be able to auto provision some permissions based on calling as well. Right now, only church employees can touch the Church's social accounts. But, by using LDSAccount, we'll be able to open up the moderation/administration of the Church's social accounts to volunteers as well. Then, if someone does something stupid, Correlation will catch it, and they're rights will be revoked without having to change the password on the social account and impact all of the other people that access it.
We'd also like to create an email/sms(/anything else?) backend that makes it easy to do the comment moderation (and perhaps other features) via email/sms. For example: Jane is a comment moderator. When Billy posts the comment "This !&#@ page sucks. Check out my page here..." on one of the Church's Facebook pages, she gets an email with the text of Billy's comment. When she sees his harsh choice of spammy comment, she sends a quick email response: "Spam". End of story. Jane won't have to login to see and moderate the comments. Jane is happy to save the time.
Another important feature of the Social Dashboard is the integration with correlation processes. When Maria tweets on @ldschurch about the International Video contest, her tweet is passed through correlation before appearing on twitter. There are already a couple of internal church services to speed the correlation approval process, and the Social Dashboard should make sure to leverage them to ensure social interaction can occur as quickly as possible.
Some of the social network channels that should be administered via the Social Dashboard include:
- Facebook pages
- Twitter accounts
- YouTube channels
Ideally the Social Dashboard isn't just a destination for administering the Church's social accounts. The goal is to create a relationships platform. This platform should allow other projects (internal and community) to interact with these Church social pages/accounts. In creating this platform, we'd like to leverage the open source APIs that are already available like OpenSocial.
Benefits of a church social platform/API:
- This platform will allow Church entities to easily adapt "social" technology, build social experiences into their technology, and will provide an API for them to, in a standard format, access the various relationships available to the Church (Facebook, Twitter friends, Ward & Stake memberships, Family members).
- Enable community members to easily, using Google Gadget formats supported by OpenSocial, build their own widgets and applications that can easily be adapted by the Church entities that utilize this platform.
- This has the potential to truly be something that powers many of the relationship technologies that the Church is currently considering.
We are looking for developers, architects, designers, QA engineers, project leads, and support helps that can all help us embark on this project.
- Sign up to help!
- test site (nothing here yet) - checks out a copy of trunk every 5 minutes.
- JIRA: Used for bug/issue tracking
- SVN repository (we will move to git once it's available for LDSTech projects)
- CIA.vc (tracks SVN changes)