On 10/17/06, Emily Lynema <[EMAIL PROTECTED]> wrote:
We have a roller (version 2.1) site for faculty and students at our university. After students leave the university, they will no longer be able to manage/edit/post to any blogs they have created. Has anyone found a good way to export the content from a specific blog (aside from doing a direct database dump)? Has there been any talk about future developments in this area?
We started a blog export feature a while back but never finished it. The idea was to save the entire blog as a RSS or Atom feed, adding some feed extensions so we can save comments, bookmarks, etc. Then we'd package that feed along with all uploaded files into a nice tidy ZIP file available in the downloads area of your blog. Unfortunately, there is no standard blog export / import format. So would you import that data to your new blog server/service? Another approach is to use web services. Currently, Roller supports the standard MetaWeblog API, so you can use a blog client to fetch all of your blog entries to your machine -- unfortunately, you can't get comments or bookmarks or uploads that way. If just entries is OK, then check out w:bloggar, Ecto, MarsEdit (on Mac) and see if they can archive a blog -- they are all compatible with Roller's MetaWeblog API interface. Or, if you've got programming skills you can write a blog-entry-fetcher program pretty easily. Soon Roller will support Atom protocol and its possible that we could expose all collections (bookmarks, categories, tags, file uploads) as Atom collections with create, retrieve, update and delete. But we still need a standard import/export format/protocol -- exporting your blog from Roller is only half of the story. Any other ideas? - Dave
