« Upgrade
Once more, with chip clips »

Good migrations

Tue Aug 12, 2008 15:52 (UTC -5)

More metablogging: in my last post, I mentioned that “for reasons that are outside the scope of this entry, my posts from 2003 and 2004 have never been loaded into WordPress.” It’s a topic I want to go into a little more, so it’s the scope of this entry.

Before I moved to WordPress on January 2, 2005, I wasn’t using any particular blogging software to blog. I was manually writing posts on the main page, moving old posts to the archives, and adding items to the RSS feed one by one. It got tedious after a while, which is why I made the switch. But I never moved my old posts (except the post of January 1, 2005) to WordPress, where they could each have an individual URL and be tagged and commented on. That left 346 posts from 2003 and 2004 that don’t quite fit in with the rest.

The most obvious reason for not adding the Original 346 was the issue of permalinks. They are supposed to be, as the name implies, permanent. Back then, I found it most convenient to use a permalink scheme unlike any known to man. Each monthly archive was on a single page (for example, /archives/200312.html) with each post’s “permalink” being specified by a different fragment (the part after the #). The fragment was originally in the numeric format YYYYMMDDHHMM, but I later changed it to dDDHHMM. The letter “d” was added to the beginning because fragments should be specified by unique element IDs, and IDs may not begin with a number. I updated all the old permalinks and the posts that linked to others. Sounds pretty impressive, but it was just a matter of doing search-and-replaces in HTML files.

Anyway, to move the old posts to WordPress, I’d have to change these permalinks a second time, and it seems like the best way to do this would be to do 346 find-and-replaces on the database with PHPMyAdmin, a la these instructions. That doesn’t sound too hard. I’ve done more tedious things. As for redirecting the old links, I wouldn’t create hundreds of complex .htaccess rules to redirect old posts to their new permanent (?) URLs, but it would be simple to redirect them to their new monthly archive pages.

Those issues are technical. They can be solved relatively easily. But there’s an editorial consideration that arises from technical conditions. WordPress allows you to set a single time zone for your blog. I have it permanently set to Eastern Standard Time, UTC -5. In the pre-WordPress days, things were different. From April 2003 to October 2004, I dated my posts with UTC because I was dumb. This means that I had a different definition of “today” than my environs indicated. I would write a post just after “midnight” describing the events of yesterday, but yesterday was actually that same day because “midnight” was 7:00 P.M. I thought that people in other time zones wouldn’t understand EST but would understand their offset from UTC. Yeah, really.

The question remains: should I edit my old posts to reflect my local time? Should I change those old yesterdays to todays and the todays to tomorrows? This could have interesting consequences, such as having posts move from one month to another. It would also throw my old flashback “One year ago, two years ago” links out of whack. But it would make the old posts consistent and less confusing for readers.

There are a few other issues associated with moving the Original 346 to WordPress. The only one I can think of off the top of my head is that I’d have to remove the occasional formatting from post titles (example) as well as the “Plus:” subtitles that I used to use. No big loss there.

If I do move the Original 346, which sounds increasingly likely, I’ll probably convert the blog’s categories to tags and re-tag each of my posts. Categories are pretty hierarchical, and you tend not to create new ones except once in a great while. Tags are created on the fly and can be for the nonce, although they’re most useful if they’re used at least a few times. They can touch upon things that would be too trivial to merit creating a category. For example, if I wrote a post about going to a steakhouse with my friends, I could tag the post “friends,” “dinner,” “steak,” the name of the restaurant, and so on. It sure would be interesting to look back on all my old posts that had to do with steak.

From the BBC: How not to do an American accent.

Here’s a recipe for chocolate cake in 5 minutes. I haven’t tried it. It might be disgusting.

More about Legos: A rare glimpse inside the Lego factory.


Leave a Comment

Feel free to join in on the discussion of this post. Keep the following in mind:

  • Don't include links to your commercial web site, or your comment will be summarily deleted. Advertising is not allowed here, so don't waste your time.
  • You can enter your e-mail address if you'd like me to contact you via e-mail. It is never disclosed to anyone else.
  • You can use the following HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> . (Your line breaks will be converted automatically.)
  • Comments will generally be visible immediately. However, if your comment contains spam-like keywords or an unusual number of links, it will be subject to approval before appearing.


Follow the Discussion

Web feed icon Subscribe to the comment feed for this post.

« Upgrade
Once more, with chip clips »

Get E-mail Updates

Sub­scribe now, get an e-mail for every new post. No spam, I pro­mise.

Recently on Twit­ter

“It's a beau­ti­ful day, and Kate is here!” (5 days ago)

Fol­low @the­world­of­stuff

RSS

Sub­scribe in your favor­ite reader.

Blog­roll

Stan­dards Com­pli­ance

This page con­sists of valid XHTML + RDFa with valid CSS 3.