I found this meme via Karen Schneider’s entry. Although I wasn’t explicitly tagged, I thought it was interesting enough to add an entry to the meme’s Flikr pool.

With all due respect to Karen — and I agree that a love of reading is important — but it is a sense of wonder that encourages a love of reading and all sorts of other critical character traits. This is a picture of my daughter when she was about three years old. She is on the back deck of our Connecticut house watching a caterpillar crawl up our gate. She loves to read (and now three years later is reading scores of books on horses and dolphins from the elementary school library), and as her father I hope the same sense of curiosity will sustain her love for reading, arts, sciences, and life.

Since I wasn’t tagged, I’m not inflicting the meme on anyone else.

The text was modified to remove a link to http://www.edsupport.cc/mguhlin/archives/2008/02/entry_6578.htm on January 28th, 2011.

I will never fly U.S. Airways again, if I have a choice. A competing airline’s ticket is going to have to be substantially more expensive for me to even consider U.S. Airways as an alternative.

This all started with a trip to Ithaca two months ago. There was a substantial weather system that move through the eastern seaboard area that screwed up traffic for a number of carriers. From my vantage point on the ground — watching the FAA’s National Airspace System Status Summary as well as various flight tracking services — everything seemed to be on time for a flight from Syracuse through Washington-Regan to Columbus. Washington-Regan was spared the brunt of the storm and was not having to de-ice aircraft, as I recall. Other major airports had closed various runways and were reducing traffic with ground-stop programs, but as the afternoon wore on the system was improving. The only abnormality was an odd message on the National Airspace System Status Summary was a message that the Philadelphia airport was closed to U.S. Airways traffic at the request of the airline due to “lack of ramp space.” The U.S. Airways website continued to show an on-time departure, so I figured the aircraft for my flight from Syracuse to Washington-Regan was coming from Washington-Regan or somewhere else that was not affected by the Philadelphia airline-requested ground stop. I headed to the Syracuse airport…

…where I found all hell had broken loose. In the 75 minutes it took me to drive from Ithaca to Syracuse, U.S. Airways canceled what looked to be all of their operations in the northeast. Based on past travel experience, I’ve found that it is often better to call the airline’s central toll-free number rather than wait in a customer service line at the airport. Wrong choice. U.S. Airways’ phone system had basically melted down. It took 23 dialing attempts just to get in the queue of people “waiting for the next available agent” and after 90 minutes on hold I hung up and got in line. The guy that got in line behind me said he held on the phone for five hours at his house before hanging up and driving to the airport, thinking that the service had to be better than that at the airport. Right?

Wrong. An hour and a half later plus two television reporters on a remote for the evening news talking about the long lines of customers in front of the U.S. Airways ticket counter at the Syracuse Airport, I finally got to the head of the line. The best the agent could offer was a flight 49 hours later. I asked about compensation based on the problems in Philadelphia. She said the problem was the FAA closing airports due to the weather. I told her about the message from the FAA’s status page about the problem only affecting U.S. Airways flights in Philadelphia. She told me she knew nothing about it, but that if I wasn’t on the flight 49 hours later that I could apply for a refund for the unused portion of the ticket.

So I rented a car and booked a hotel room for the night (neither of which U.S. Airways would pay for). After a good nights sleep I drove home and picked up my car from the airport parking lot 27 hours before any possibility that U.S. Airways could get me there.

In the middle of the following week, I submitted my request for a refund via some automated automated telephone system that no longer exists (800-363-2542 — it now gets routed to the “customer relations system” at 866-523-5333, but more on that in a minute). A week later I called a separate number (480-693-6735, as documented on the U.S. Airways Ticket Refund website) and keyed my ticket number into the automated system; it wasn’t found. So I faxed a copy of everything to the number suggested (800-892-3447). A week later I checked the automated system; nothing. So I sent a copy in the mail to the 4000 East Sky Harbor, Pheonix, AZ address. I just checked the automated system again; nothing.

So I’ve had it with the automated systems and I try to get someone on the line. I call the “Customer Relations” number (866-523-5333); option #2 is for ticket refunds and such. The recorded message tells me that to serve me better I should hang up and dial a 480-693-6735. Yes, if you’re keeping track, we’ve seen that number before. It is the automated check-the-status-of-your-request number. The voice prompts don’t give you a way to talk to a human, but after hitting enough garbage into the system you get routed to what the system claims to be is the queue of people waiting for the next available agent. I only spend 25 minutes on hold here before giving up — it’s my dime paying for the call, after all. Next I call the central number for U.S. Airways where an agent gives me all of the phone numbers I’ve already tried and says that is all she can do for me.

Here’s the real kicker — U.S. Airways is acting like it doesn’t care what you think. As a last resort, I call the “Customer Relations” number once more and pick option #3 — for a “complement or concern” — and after a few rings I am offered an apology for not being “personally available to take your call now…” (no queue of people on this option). Boy, it is a good thing I didn’t have a complement for the airline, right?

Now, I never expected it to be easy to get a refund for my ticket (it is, after all, money that they would want to keep for not doing any real work), but I do expect it to be possible. So, U.S. Airways, as your pilots say when we land, I do have an option in air carriers when I fly, and from now on I won’t be choosing U.S. Airways.

Update (20070601T0956): The New York Times has an article about the overbooking practice by airlines, focusing on U.S. Airways. A part: “Overbooking is one of many airline practices that are complicated by crowded planes. Airlines are running closer to capacity than at any point during the jet age — an expected 85 percent or so full this summer, which means all the seats on popular routes will be taken.”

Here is a bit of personal news to report. Tom Sanville, OhioLINK’s executive director, announced today that I am changing roles at OhioLINK. Here is what he said:

I’m pleased to announce that Peter Murray will assume the position of Assistant Director, New Service Development effective immediately. In light of the formation of 13 task forces to pursue investigation of our strategic priorities it is critical that we have a skilled OhioLINK staff member with primary responsibility to analyze, recommend, and coordinate plans for the introduction and use of new information technologies and services by OhioLINK and its member institutions. Through Peter’s tracking and contact with information and library hardware, software, and database vendors, he will provide leadership and support to the OhioLINK staff, committees, task forces and other planning groups.

OhioLINK has been engaged in strategic planning over the course of the last year and beginning this month has formed a dozen task forces to begin implementing some of the elements of that plan. A swath of technology, from ordinary to cutting edge, cuts through many of them. My job will be to understand what the community is trying to accomplish, synthesize recommendations and draft plans from the best of what is out there, present that to the community, and aid in moving the vision forward. It is as exciting an opportunity as it is daunting.

I don’t know, at the moment, what this means for the Jester’s blog. It is possible there may be more posted here because the synthesized information would be of use to a larger community. It is possible that such synthesized information would appear instead in a more official OhioLINK forum. Time will tell, but if this blog appears to drop off the face of the blogosphere, you’ll probably know why.

Long time readers of DLTJ know that I rarely post commentary outside the realm of disruptive library technology to this blog, much less reflections of personal, non-work life. This will be an exception, though, because it straddles that boundary between technology and family. It is called REST for toddlers and it comes to us from the “dive into mark” blog. By way of explanation, REST (as a technology term, not as used in the sentence “parents with young children often which they had a chance to rest.”) is an acronym for Representational State Transfer, a way of constructing URLs so that they are useful outside the context of your current web browsing session (e.g. bookmarkable and/or e-mailable to someone else). REST rides atop the HTTP protocol, of which section 10 of the specification talks about response codes from clients to servers. What Mark has done is offer a real-life explanation of some of those response codes in the context of child-rearing. A sample:

200 OK

“OK.”

201 Created

“You went pee-pee in the potty!”

202 Accepted

“Daddy will do it in a minute.”

204 No Content

“…”

300 Multiple Choices

“Do you want apple juice or do you want milk?”

So, it would seem to me, that I just need to teach my daughter the HTTP protocol, at which point I can make our challenge/response dialog much more efficient:

• Her: Can I go outside?
• Me:Sure! 200

• Her: Do you know where my bouncy ball is?
• Me: Sorry, 404. 302.

• Her: Well, then can I have that bucket and shovel?
• Me: 409.
• Her: Ple-e-e-s-e?!?
• Me: 304, and if you keep asking, 403!