Archiving social media | The National Archives blog We decided to archive the content presented through Twitter’s Application Programming Interface (API). The API presents the “raw” data behind each tweet – the tweet’s visible textual content – along with metadata associated with it (date, time, user account, users mentioned and so on). This machine-readable code we then used to provide access. Those familiar with the code will be able to write applications to query it, or integrate it with other data in the future. This also solves the scalability problem as the API provides access to up to 3,200 tweets in one go. http://bit.ly/1hzEiJk Source: http://blog.nationalarchives.gov.uk/blog/archiving-social-media/ See if people are clicking on this link: http://bit.ly/1hzEiJk+ Try the bitly.com sidebar to see who is talking about a page on the web: http://bitly.com/pages/sidebar -- Peter Kurilecz CRM CA IGP [log in to unmask] Dallas, Texas Save our in-boxes! http://emailcharter.org http://twitter.com/RAINbyte http://tech.groups.yahoo.com/group/RAINbyte/ http://paper.li/RAINbyte/rainbyte http://pinterest.com/pakurilecz/archives/ http://pinterest.com/pakurilecz/records-management/ http://www.linkedin.com/in/peterakurilecz Information not relevant for my reply has been deleted to reduce the electronic footprint and to save the sanity of digest subscribers List archives at http://lists.ufl.edu/archives/recmgmt-l.html Contact [log in to unmask] for assistance To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message. mailto:[log in to unmask]
