Add API/Backend for handline data sources

[rjmackay]

Enable pulling posts from SMS and Twitter

• Messages will be created as posts, with status = 'incoming'
  • We may need to create a static post form to receive these..
• Add a listing of 'incoming' posts as a link in the workspace. Admin only?
• Reuse SMS plugins from Ping
• End points for at least
  • FrontlineSMS
  • SMSSync
• Pull data from at least
  • twitter

Mapping a message to a post: Date -> ? (add a post_date field?) Title (email subject, rss title) -> Title Message Detail (twitter msg, email body, sms) -> Content Location -> custom field..

Extra details in 'message' table: Service: Twitter/SMS/RSS/Etc ServiceMsgId: ie. twitter message id. ToContactID : Join to contact table FromContactID : Join to contact table

Contact table: Service: Twitter/SMS/RSS/Etc Detail: Phone number/Twitter Username/ Email Address User ID: Null or associated user.

[rjmackay]

To do

• [x] Messages API
• [ ] Contacts API
• [x] Message Model
• [x] Contact Model
• [x] Data Feed Model
• [x] Basic Messages UI
• [x] Messages listings by various status/ source
• [x] Data Provider module
• [x] SMS Sync data provider
• [x] Email data provider
• [ ] Twitter data provider
• [ ] Docs on configuring data provider
• [ ] Permissions check before displaying message listing
• [ ] Figure out how to handle required field failures when creating a post from message

Later / Non essential

• [ ] Allow data provider to hook into message -> post conversion
• [ ] Geolocate message
• [ ] copy date of message to post
• [ ] copy location of message to post
• [ ] UI to configure twitter feed
• [ ] Data feed API

Additional Data providers

• [x] Twillio data provider
• [x] Nexmo data provider
• [ ] FrontlineSMS data provider
• [ ] RSS data provider