Looking beyond the documentation?

Check out our help articles

Storing Dynamic and Static Metadata - Part 3

posted on 26 March 2015 by Jim Moffitt

Storing Dynamic and Static Metadata While much of Twitter metadata is dynamic in nature, changing tweet-by-tweet, other metdata can change more slowly or stay completely static for long periods of time. Twitter user accounts (stored in the ‘Actor’ object in the Activity Stream format) provides good examples of both ‘static’ and ‘slow’ metadata. An actor’s numeric ID and account creation time will never change. Their account-level language, timezone, location, display and handle names may rarely change. Meanwhile their status, followers and friends counts will surely change over time. Here are some example attributes that generally fall into these three categories:... keep reading

Storing Twitter Metadata Arrays - Part 2

Storing Twitter metadata in relational databases

03 March 2015

Storing Twitter Data in Relational Databases - Part 1

An introduction to Storing Twitter Data in Relational Databases

25 February 2015

Example Relational Database Schemas

Example Relational Database Schemas

01 January 2015

See More

Building your app?

Get going quickly with our code examples

PowerTrack / Firehose Stream

Connect to the PowerTrack and Firehose streams.

PowerTrack Rule Management

Add, delete, and list rules on the PowerTrack Rules API.

Compliance API

Request Compliance events for the data you have collected.

Historical PowerTrack

Create and manage Historical PowerTrack jobs.

Search API

Send Search and Counts requests to the Search API.

Data Collector Stream

Connect to the streaming endpoint of Data Collector streams.

Data Collector Polling

Retrieve data from your Data Collector with GET polling.

Data Collector Rule Management

Add, delete, and list rules on your Data Collector feeds.