Message-ID: <1463632700.2058.1556113514019.JavaMail.javamailuser@localhost> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2057_696195308.1556113514018" ------=_Part_2057_696195308.1556113514018 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Media Monitoring with SwiftRiver

Media Monitoring with SwiftRiver

This is is a working document to document media monitoring workf= lows utilizing SwiftRiver and Ushahidi/Crowdmap. (Note this document was cr= eated by =EF=BB=BFJuliana Rotich

This is a proposed draft for media monitors using SwiftRiver in their w= orkflow. E.g Standby Task Force activations. This draft is based on the so= cial media monitoring that was done during the simulation of Kenya electio= ns.

**This is to be reviewed by SBTF for feedback and improvement.

Media Monitoring Leads need to be identified. Once identified, they sho= uld sign up for SwiftRiver login. If you do not already have a login, sign= up on http://www.swiftly.org/beta/

If you are lead, do the following

If you are not lead on the media monitoring team:

Tech Team

Integration of SwiftRiver= bucket RSS to Crowdmap/Ushahidi reports is yet to be completed. Th= is page will be updated once that is completed and this workflow diagram updated.

Integration of SwiftRiver into Crowdmap/Ushahidi has been completed via = a plugin. This plugin is downloadable on = Github or search for it in Crowdmap plugin tab in settings.

TBD: Updating Workflow diagram teed up for StandbyTaskforce.

------=_Part_2057_696195308.1556113514018--