adriansmalley/eventflex

EventFlex

• Task 1
• Task 2
  • Task 3
• Task 4 - Marko

eventflex's Issues

Build the Schedule Page

Twitter integration - scheduled fetching of tweets

For now, every 15 mins with the ability to initiate it manually.

Twitter API limits can be found here: https://dev.twitter.com/docs/rate-limiting/1.1

Twitter integration - linking tweets to sessions and extracting session score

Example: Great session! #session1 #score_5

session1 is linking Social Post record to a session using Session_Hashtag__c field on session record.

Hashtag that begins with "score" will be used to store the score in Session_Score__c on social post record. Recommended approach: fetch all following characters after word "score" until either space char or special (!, #, :. ;...) char is reached, remove all alpha and "_" and that leaves the score.

Twitter integration - linking of Tweets to attendees and contacts

Based on who is tweeting SocialPost can be linked to SFDC records.

Contacts are searched and first matching twitter handle (Twitter_User__c on Contact) links that contact to the Social Post record (Social_User__c). Then, that contact's Attendee record is linked to the social post record (Attendee__c) by matching event's twitter handle (Twitter_User__c) and social post's @username. That is also how Event lookup on social post record (Event__c) is populated.

Twitter integration - assigning sentiments to Tweets

Using http://www.alchemyapi.com/products/demo/alchemylanguage/ (free for up to 1000 API calls a day and for up to 5 concurrent calls) assign sentiment to Social Post and store it in:

Sentiment_Type__c (positive, negative, neutral)
Sentiment_Score__c (x.x)

http://www.alchemyapi.com/api/sentiment/textc.html

Case Raise - GPS coordinates

Conversation capture - ad hoc link attendees to conversation topics

Page that will allow linking of Attendee records with conversation topics.

Conversation topics are modeled using Campaigns and Campaign Hierarchies:
Umbrella Campaign -> Sponsor -> Conversation Topic
Example can be found here: https://ng-dev-ed.my.salesforce.com/70120000000bHuN

For the PoC we can use just one sponsor for the sake of simplicity.

Idea: add hoc topics if they do not exist?

Images for Schedule Page

Case raise - Salesforce1 notification

Placeholder issue - to be reused