Support for Gnip 2.0 Data


#1

Today we have enabled support for Gnip 2.0 data for all our current ODP (Open Data Processing) customers who pass their Twitter data from Gnip to DataSift.

What’s changed?

  • The output data format on a Gnip 2.0 streams is a little different to the 1.0 data. We make this transparent, and map the Gnip interaction into the same interaction.* namespace for both versions of the Gnip feed
  • The unmapped.gnip.* namespace has been transitioned to the gnip.* namespace in the resultant output interactions
  • The unmapped.* namespace will continue to exist, but only for fields and Gnip enrichments that DataSift is not familiar with
  • The value of the interaction.type field will continue to be twitter_gnip for Gnip 2.0 feeds

How do I send a Gnip 2.0 feed to DataSift?

In the same way as you send data to a Gnip 1.0 feed. The only difference here is that you will need to create a “Gnip 2.0 Data” Managed Source. Access to this source has been granted to all active DataSift customers with access to ODP for Gnip

Klout

In order to use Klout data, you will need to enable the Klout enrichment on your Gnip feed. This data will be mapped to the klout.* namespace within your resultant output interactions. You will still be able to perform filtering on the Klout Score of an interaction using the klout.score CSDL target.

If you have any questions, please get in touch with our Support Team who will be happy to assist