Email: A Communication Archive Engine

Email is slow according to today's high expectations of immediate response and feedback. However, it is considered the more formal mode of communication, especially for employers. Email etiquette is synonymous with writing a hand-written note and sending it via USPS. To understand and perform the sweet science of emailing, you can purchase any number of books or for free via articles/blogs on the subject, e.g., "The Art of Email Writing" by P. Vassallo. Nevertheless, email writing rules mimic those of letter writing: greeting, body introduction, body content, closing, signature. 

Email writing and responding, circa 2014, is a necessary evil. Admittedly, I have a love-hate relationship with email. I have two big pet peeves. The first irritation is receiving an email indicating that another email is en route in the near-future. I mean, why even bother sending the email in the first place? I just don't get it. I wish the sender would just wait and send me all the information in one email. Or better yet, call me or tell me in a face-to-face conversation. Woah, crazy talk. It sounds too much like right. Let me just move on. The second irritation is the inappropriate use of the "reply all" feature. The situation is all too common: an email with a list of recipients is sent and the recipients respond to all on the original email rather than just the proper individual, e.g. congratulatory notes, e-introductions, etc.

Quick "Reply All" usage tip: do not "reply all" UNLESS one of these conditions holds true: you are sharing common information to a group e.g., reporting up your chain of command (cya/cyoa), you are eliciting a group-email discussion, e.g., when/where to meet, or you are attempting to resolve some sort of small miscommunication. 

Email has unfortunately been used as a replacement for, rather than to augment, face-to-face conversations. Misinterpretation, miscommunication and downright rudeness are the bad effects. Hence, my love-hate relationship with this technological advance. In recent months, many strive to obtain the inbox zero status - an email management effort to have as few (optimally zero) messages in your email inbox. Effective organization of folders and email deletion rules can help achieve the zero inbox. The benefits purported as less clutter, less stress and focusing your attention on important things. I'm marching toward the zero inbox, but I ran into a hiccup on my Apple devices. The Apple folder structure doesn't exist (essentially you must create another mailbox), which is not viewable to the root mailbox. I rely on email deletion rules, Evernote and leveraging my laptop's folder structure. I've reduced my professional email box count from ~2000 to ~1000 messages.

The introduction of other digital communication mediums (messaging, texting, FB inbox, tweeting and all other social media) has rendered email archaic. But I've discovered a revived appreciation for email during this zero inbox experience. Email has one last stand, one significant advantage that those other digital communication mediums. Conversation archiving. I have found myself in situations over the past few months where being able to quickly access (and then forward) the original email or email exchange has circumvented additional emails and stress. I no longer desire the zero inbox instead I strive for periodically identifying and archiving relevant email conversations.

Quick email tip: some individuals are more comfortable using email, rather than face-to-face or phone conversations. When I encounter this situation, I sculpt my email to elicit a response from them, usually by ending my email with a question.   

Here's a few of my email inbox management tricks. To better understand my tricks, I receive email from the following groups as a college professor: my institution's administration, colleagues/peers, graduate students, undergraduate students and prospective graduate students. 

I classify email messages into three bins:

• Informational: These messages are meant to keep you in the loop. You must decide if being in the loop is what you want. If so, you can note the information. Regardless, simply delete the email. Disclaimer: Email responses are not warranted. Depending on the email culture, a corresponding acknowledgement message may be considered the proper rules of engagement.
• Discussion: These messages are meant to help minimize miscommunication and misinterpretation of the email recipients. The sharing of ideas and solutions tends to ensue as the different perspectives reveal themselves. In my discipline of computing, we call this sentiment analysis or opinion mining. It's very hard to accomplish through email exchanges. I prefer to handle these situations either face-to-face or over the phone. If a resolution has not been reached, then keep the most recent email, which should include the entire email chain. You avoid information loss and you can delete the other intermediary emails. Disclaimer: email responses are expected but not required.
• Decision: These messages are an attempt to reach a consensus of a group. Most recipients elect to use the Reply All feature in an effort to come to a consensus quicker. In the professional environment, a decision maker is met with either joy or dislike. Joy to those who are indecisive or prefer not to make a decision. Disliked by those who don't agree with the decision rendered. In most cases, it's email polite to state your decision clearly. As with the discussion emails, keep the most recent email, which should include the entire email chain, and delete the rest. Disclaimer: You may not actually care about the topic in which your decision is required. But the decisive trait and making good decisions reveals your potential for future promotions.

Now, go forward and conversation archive! 

Timely Data Acquisition for the Aviation Industry

originally posted on March 30, 2014 on csdoctorsister.blog.com

In the wake of #MH370 (classified as missing since March 8th), I posted to FB on March 13th: How do you LOSE A PLANE with all these technological mediums?!? Where the freak’n frack is Malaysian Airlines Flight 370?!? #hearthurts #disappointed

The fact that a plane carrying 227 passengers and 12 crew goes missing is unimaginable and unacceptable. As a #datahead, I immediately think about what data was available and not captured that could be useful in finding this plane. Unfortunately, #MH370 is a recent example of aviation’s need for better data understanding.

Here’s another recent example: in April 2011, an EF4 tornado ripped through St. Louis, right passed the Lambert-St. Louis International Airport, with at least one airplane reported as  landing due to the Air Traffic Control (ATC) being unaware that the tornado was on the ground. In light of the April 2011 EF4 tornado, my colleague, Mary Johnson, and I are working on ways to assist the aviation industry in handling their data.

Our efforts, approach and prior works are given below.

Unknown to most commercial airline passengers, extensive information is reviewed by the pilot and the dispatcher who must both sign off and agree that the flight is ready for take-off. Both the pilot and the dispatcher must be FAA certificate holders to perform their jobs. Information is aggregated by ATC from sources such as the National Weather Service (NWS), flight tracking websites, airport changes, official notices, pilots, FAA or similar agencies, in an effort to inform air transport personnel about flight scheduling viability. These data may not arrive in a timely manner to make decisions regarding flight dispatch which has a role at take-off, in-flight, and landing to ensure safety and operational control. Twitter may provide a mechanism to improve the timeliness of accessing accurate data, and data not normally available to ATC, dispatch services and/or pilots. Since twitter is publicly accessible and contains user-generated content, the vulnerability, reliability and trustworthiness of its data must be assessed before introducing this information stream into the aviation industry that requires accurate and timely information. This project investigates the use of twitter to improve the data timeliness and possibly increase the data coverage to ATC for air transport personnel, pilots, aircraft dispatchers, airline managers, and airport managers.  As part of the investigations, this project seeks to assess twitter’s vulnerability, reliability and trustworthiness for use in Federal Aviation Administration controlled airspace to augment the data currently available and used by aircraft dispatchers.

We have begun our inquiry by implementing a twitter-based prototype (Marshall, Johnson et al., 2012) that considers 4 major commercial airline carriers and 30 US airports during Hurricane Sandy in October 2012 that captured up-to-the-minute aviation conditions via airport ICAO and IATA codes and keyword analysis (Marshall, Johnson et al., 2013). We implemented K-means clustering and computed the 2 mutual information evaluations. Of the collected tweets’ containing airport codes during Hurricane Sandy, we observe in the largest cluster of the airport codes are not directly located in Hurricane Sandy’s path, indicating that intermediate airports that were affected due to lack of aircrafts and air transport system personnel. The second experiment dealt with keywords. Sample keywords and phrases include jet blue, delta, united, southwest, flight, cancel, flood, storm, weather, sandy, nor’easter, new york, new jersey, philadelphia, washington, west virginia, maryland, food shortage and electricity. Of the collected tweets’ containing these types of keywords, we noticed 2 relatively large groupings including the airline keywords. As expected, the keywords related to Delta Airlines and aviation/flight appear in nearly all the clusters. Surprisingly, the keywords related to Hurricane Sandy only appeared in one cluster implying the tweets centered on the consequences of the storm — not the progression or status of the storm itself.

The current prototype system is written on Chrome’s JavaScript runtime node.js platform for easily building fast, scalable network applications. Between the end of October 2012 to the beginning of November 2012, about 13,000 tweets were collected using the twitter REST API. Our database contains three types of clusters namely Airport, Airlines and, Path.Airport. For our selected airlines, they generally provide flight schedules in one month increments in the form of downloadable PDF and require data format conversion to JSON.

References

1. Marshall, B., Johnson, M., Magikar A., Ghanekar A., Mathew I., Delaveau L., Budhiraju R., Chapparala R. (2012). Flight Data Analyzer using Twitter.  Journal of Emerging Trends in Computing and Information Sciences, 3(8):1226-1234.
2. Marshall, B., Johnson, M. and Chunduru, N. (in press). Towards general aviation using Twitter as a virtual aircraft dispatcher. Proceedings of the Conference on Telecommunications and Information Technology. Murray, Kentucky: Information and Telecommunications Education and Research Association.