Comments on: Episode 55 – Social History https://digitalcampus.tv/2010/04/episode-55-social-history/ A discussion of how digital media and technology are affecting learning, teaching, and scholarship at colleges, universities, libraries, and museums. Wed, 28 Apr 2010 02:03:45 +0000 hourly 1 https://wordpress.org/?v=5.4.2 By: Briefly Noted for April 27, 2010 : Found History https://digitalcampus.tv/2010/04/episode-55-social-history/#comment-231 Wed, 28 Apr 2010 02:03:45 +0000 http://digitalcampus.tv/?p=269#comment-231 […] will already know my take on the Library of Congress Twitter announcement. But for those who missed our most recent podcast, I was also quoted on the matter in an article in Read Write Web entitled “Twitter Archive is […]

]]>
By: Tom Scheinfeldt https://digitalcampus.tv/2010/04/episode-55-social-history/#comment-230 Fri, 23 Apr 2010 17:42:11 +0000 http://digitalcampus.tv/?p=269#comment-230 Thanks for the links, Bryan and Boone. No shame in self-promotion. In fact, I’ll link to a Read Write Web piece on the Twitter/LC deal which quotes me pressing again my case for adequate funding for the new archival methods and tools necessary to make sense of social media archives.

]]>
By: Bryan Alexander https://digitalcampus.tv/2010/04/episode-55-social-history/#comment-229 Fri, 23 Apr 2010 17:06:36 +0000 http://digitalcampus.tv/?p=269#comment-229 One article agrees about LoC/Twitter and social history:
http://www.slate.com/id/2251429/

]]>
By: Boone Gorges https://digitalcampus.tv/2010/04/episode-55-social-history/#comment-228 Fri, 23 Apr 2010 16:22:13 +0000 http://digitalcampus.tv/?p=269#comment-228 At the risk of gratuitous self-promotion, here’s the Ning-to-BuddyPress importer authored by yours truly: http://teleogistic.net/code/wordpresswordpress-mu/import-from-ning/

It’s very incomplete, as Ning offers easy exporting of user and profile data, but not of user-produced content. And really, you can’t blame them to a certain extent. Beyond the obvious financial incentive for not allowing an easy export, there are also the technical challenges of exporting to a format that will actually be useful. We aren’t even really at the point where we have universal export formats for the relatively mature medium of *blogs*, much less the younger and more complex beasts that are *social networks*. Until such standards are agreed up and implemented in a variety of platforms, the only way communities can ensure the exportability of their valuable content is to have the ability to do a direct dump of the database, and access to the skills required to translate it into another usable format.

It’s too bad that this is the case. The situation requires a pretty drastic trade-off between control and ease of use.

]]>