What is a Source?¶
Sources are the social media platforms such as Twitter, Crowdtangle, Ushahidi, and RSS feeds that Aggie crawls through to aggregate reports relevant to the event being monitored.
Adding Sources to Aggie¶
Click on Sources on the Header Menu of Aggie’s main page.
Click on the blue Create Source button on the left.
Choose the Source Media.
Enter a Name for the source.
Copy and Paste the URL of the source page and click Submit.
As the application pulls in data, the app may encounter warnings. These warnings help determine whether or not a feed is pulling in data correctly.
- Go to
- In the
Namecolumn, click the appropriate source.
Recent Events, you can see recent warnings for the source.
Reports Page Activities¶
What is a Report?¶
A report is any post collected from a source. Examples include tweets, Facebook posts and blog posts.
The Reports Page¶
From your Aggie header bar, click the Reports Tab. This will show you the reports page as indicated below.
Actions on the Reports Page¶
There are several actions you can take on the reports page of Aggie. You can Read reports, Create Incidents,Filter reports or add a report to an Incident. Besides the filter bar and the action and navigation buttons, there are eight columns on the Reports Page of Aggie.
Sections of the Reports Page¶
- The Checkbox column: This is used to select one or more reports that some actions can be applied to.
- The Time column: This indicates the time the report was published on the source feed that Aggie collected the report from.
- The Media column: This indicates the platform where the report was published.
- The Source column: This column indicates the name of the source, as set in the Sources tab In the case of Twitter, they all originate from Twitter search but, for example, each Facebook group or page is a separate source. Advisably, the source name should be set the same name as the social media account name.
- The Author column: This indicates the social media account of the person who authored the report.
- The Content column: This column shows the exact content of the report published by the author.
- The Incident column: This column is used to add a report to an existing incident or create a new incident.
There are two ways to read reports in Aggie. One way is to grab a batch using the “Grab Batch” button. The other is to go through reports on the reports page, navigating from one page to another using the navigation buttons on the reports page. Grabbing a batch is a faster and a more efficient way of reading reports in Aggie.
Marking Reports as Read¶
A report can be manually marked as read. More than one reports can be marked as read by checking their respective checkboxes or with the “Mark all Read” button. When a tracker grabs a new batch, it is recommended that the tracker selects either “Mark All Read & Grab Another” or “Mark All Read & Done”. If the batch was accidentally grabbed, the tracker should click the “Cancel” button.
Adding a report to an existing Incident¶
When trackers come across reports that, if verified, require action, they create an incident from that report. Or, if the report is associated with an already existing incident, the tracker may add the report to the existing incident.
Creating a New Incident¶
Select the report(s) you are creating the Incident for by checking its/their checkbox(es) on the first column to the left fo the reports page.
Click the Add to Incident button beneath the filter bar.
Select the related category of an existing incident to add the report to that incident or… If it’s a new Incident;
Click on the blue Create a new Incident link to create the new incident.
Type in the Title of the incident (e.g. Polling station not open, Voter intimidation etc), the Location of the incident and a brief note describing the incident. Leave out the veracity and assignment fields for the veracity team and click submit to create a new incident. The verification and escalation team will be using the note field to keep track of the verification and escalation steps taken.
The Public and Public Description fields are used by the escalation team to add the incident to the list of public incidents. The Public Description will appear attached to the incident, for example, in the Public Incident Map.
The Filter Bar¶
With the filter bar, trackers can narrow down their search for specific types of reports. The screenshot below shows the filter bar and a number of filters that can be used.
Filtering by Date/Time¶
Click on Date/Time button on the right end of the filter bar.
Select a Date/Time range by specifying the From and To fields.
Click Submit to filter and display reports aggregated within that date and time range.
Filtering by Date/Time
Filtering by Incident¶
Click on the Linked Incident tab and select an incident to view all related reports tagged to that incident.
In this example, selecting the incident Hate Speech shows the three reports which have been linked to that incident.
Filtering by Incidence
Filtering by Source¶
Click the Source menu from the header bar.
Select the Source type (e.g. Twitter Search) to filter and display only reports from that source.
Filtering by Incidence
Filtering by Media Type¶
From the header bar, click the Media menu.
Select the Media type (e.g. Twitter, RSS) to filter and display reports from sources of that media type.
Filtering by Media
Filtering by Status¶
From the Header Bar, click the Status menu.
Select the report Status (e.g. Unread, Read) to display the reports of that status.
Filtering by Status
Filtering by Keywords¶
Type in a query keyword, term or set of terms separated by commas, quotations or operators in the Enter keywords space on the Filter bar.
Click Go or the return key to display all reports that include the keyword or set of terms. For example, by searching the keywords, Ghana, ECG and Free n Fair Election, there is a display of all reports containing one or more of the keywords.
Filtering by Keywords
What does Batch Mode do?¶
Batch mode provides a method of distributing work to multiple users to prevent one user from doing the work another user has already completed. In Aggie, batch mode assigns reports to any user that clicks “Grab Batch” on the reports page.
This marks those reports as that user’s and prevents any other user from seeing those reports on their respective batch modes. This means that a report in one user’s batch mode cannot show up in another user’s batch mode. In addition, Batch Mode has NLP functionality and displays reports that are highly scored near the top of the screen and adds a warning icon to reports that meet a certain threshold.
How do I use Batch Mode?¶
On the Reports screen, click the Grab Batch button. This button is in blue.
From the Batch Page, go through reports and triage those that are relevant.
Batch Page Once you are completed with a batch of reports, click either “Mark All Read & Grab Another” to mark all the reports in that batch read and grab another batch, or “Mark All Read & Done” which marks all the reports in the batch read then returns to the report screen. “Cancel” will simply return to the reports screen.
NLP Indication and Ordering¶
According to the NLP classifier linked with Aggie, Batch mode will order reports based on the likelihood a report is hate speech. This will appear in two ways: the higher scoring (more likely hate speech) reports will appear on the top of the page and reports that meet a threshold will show a warning indication in the Source Info column of the report. You can see the icon attached to several reports below. These orderings and icons will not appear in the reports page, only the batch mode.
Batch Page Hate Speech Indication
Incidents Page Activities¶
What is an Incident?¶
Incidents are groups of one or more reports that, once verified, require an action. As Aggie aggregates reports from different sources, tracking team members in the SMTC collect reports into incidents.
The Incidents Page¶
From your Aggie header page, click the Incidents Tab. This will show you the incidents page as indicated below.
Incidents Main Page
Sections of the Incidents Page¶
- The Checkbox column: This is used to select one or more incidents that some actions can be applied to.
- The ID# column: This column indicates the unique identification number generated for each incident created. This example starts with 003 because incident 001 and 002 have been deleted.
- The Title column: This column shows the name given to the incident and the number of reports associated with the particular incident.
- The Location column: This column shows the place where the incident occurred.
- The Assigned to column: This column indicates the veracity team member who has been assigned to verify the incident for confirmation (and then escalation) or closure.
- The Status column: This column shows whether the incident has been escalated or confirmed false, and closed, or is still open and thus needs to be verified or escalated.
- The Veracity column: This shows the verification status of the incident. Whether the investigations confirmed the incident to be true or false.
- The Escalated column: This column show whether a confirmed incident been reported to stakeholders and embeds for management and resolution.
- The Last Updated column: This column tracks and indicates the time of the last activity such as editing or updating on the incident.
- The Edit/Delete Column: This column contains two tools for editing or deleting an incident; to edit the incident, click the blue Pencil Icon or to delete the incident click the blue small bin.
Creating an Incident¶
Normally, incidents are created by Trackers. However, should the need arise, verifiers can create incidents from the incidents page. To do this, refer to Creating a New Incident section.
Click the Incidents tab from the header bar.
From the incidents page, click the blue colored Create Incident tab.
Creating an Incident
Type in the Title of the incident (e.g. Polling Station not open, Voter Intimidation etc), the Location of the Incident and a brief note describing the incident. Set the veracity and status fields as applicable.
Editing an Incident¶
Verifiers can always update the status of incidents by editing them. It is recommended that you keep a log of the actions taken while confirming or denying veracity in the notes section of an Incident. To do this:
From the incidents page, click the blue edit pencil at the end of the incident row (last column).
Editing an Incident
Update the incident by editing appropriate sections. For example, you can edit the veracity and status of the incident, add any helpful notes or escalate the incident.
Deleting an Incident¶
If a veracity team member notices a redundancy in incidents, they may delete an incident from the Incidents page. To do this:
Select the incident(s) you wish to delete by checking its/their respective checkbox(es).
Click the Delete button below the filter bar to the left.
Click Confirm to delete the selected incident(s).
Alternatively, you can delete an incident by clicking the little bin on the last column of the incident row.
The Incident Filter Bar¶
With filters, verifiers can narrow down their search. In some cases, there might arise the need to search for specific types of incidents. Filters are the best way to achieve this. Below are a number of filters that can be used.
Filtering by Assigned User¶
From the incidents page, click the Assigned To menu on the filter bar.
Select an assignee (username) to display only the incidents assigned to that verifier.
Filtering by Assigned User
Filtering by Status¶
Click the Status menu on the filter bar.
Select Open or Closed to view incidents in these categories.
Filtering by Status
Filtering by Veracity¶
Click the Veracity menu on the filter bar.
Select the veracity status (unconfirmed, confirmed, confirmed true etc.) to display all incidents associated with that veracity status.
filtering by Veracity
Filtering by Escalation¶
Click the Escalated? menu on the filter bar
Select the escalation status (Escalated or Unescalated) to display incidents accordingly.
Filtering by Escalation
Filtering by Title Search¶
Type in an incident title in the Enter title space on the filter bar.
Click Go or hit the return key to filter and display only incidents that include the entered title.For example by searching the incident title “attacks”, there is a display of all incidents containing this keyword.
Filtering by Tittle Search
Filtering by Location Search¶
Type in the name of a location (town, polling station etc.) in the Enter Location text box on the filter bar.
Click Go to display all incidents associated with that location. For example, typing in Ghana in the Location Text box, display all incidents whose location was entered as “Ghana”.
Filtering by Location Search
Trend analysis give snappy and easy graphical visualizations of the occurrences of incidents using keywords, social media type, the Twitter handles, or Facebook groups/pages to build trends.
What is an Analytic Trend?¶
An analytic trend is a graphical visualizations of incidents as bar charts or stacked lines.
Creating a Trend¶
To create a trend visualization:
Click the Analysis tab from the header bar.
Trends Main Page
Click the blue Create Trend button.
Creating a Trend
Enter the keyword(s) you want to create the trend for. For example NDC, NPP.
Choose a Social Media Source for the trend e.g. Twitter, RSS or Facebook.
Trend Media Type
Choose the Source of the trend i.e. the social media account been followed.
Choose the Incident for the trend e.g. 233liveOnline Reports
Submit and view the analytics by Trend (Lines or Bars) and Incident Maps.