Probably best to review #19 first (the Twitter processor), as this processor has a similar structure, and builds on top of it.
[x] I've added tests to cover the proposed changes
Changes proposed in this pull request:
Adds the Facebook processor to the socialmedia.py pipeline
Retrieves Facebook metrics
interactions
impressions
mentions
followers
Writes Facebook metrics to socialmedia database table.
Processor retrieves two types of metrics, 'lifetime' metrics, such as followers, that are retrieved from the api, and used as-is without processing, and 'cumulative' metrics, such as impressions,mentions, andinteractions` that are retrieved for a specific time-frame, then added to the latest stored result.
This pull request fixes #18. Connected to #3.
Probably best to review #19 first (the Twitter processor), as this processor has a similar structure, and builds on top of it.
Changes proposed in this pull request:
interactions
impressions
mentions
followers
socialmedia
database table.Processor retrieves two types of metrics, 'lifetime' metrics, such as
followers
, that are retrieved from the api, and used as-is without processing, and 'cumulative' metrics, such asimpressions,
mentions, and
interactions` that are retrieved for a specific time-frame, then added to the latest stored result.