Using text analytics, relationships between un-connected content can be inferred. From this connection, Enki could infer relationships between objects (people, topics, events) even though they are not directly related. The dashed red line in the graph to the right shows this inference.

A screenshot of Enki's person view running on the tablet. The lower half of the screen is reserved for written notes about the person. The only thing absent from the image is a toolbar along the bottom of the screen that let you navigate to other functions. A button to provide additional writing space was also provided.

Person View Features:

• Contact Information

Name, title, location, etc.

• Communication

The person's email was displayed, which launched the default email client when clicked. Clicking on the person's phone number fires up a VoIP softphone and calls the person on the tablet! You can also run a Google or w3 (IBM internal) search with a single click, which is pre-initialized with their full name.

• Events

Tying into Lotus Notes, we could find every meeting the user and the selected person were both invited to. Only the four closest meetings are shown (that's both forward and backward in time from the current date). Users can click the blue "more" button to see expanded meeting history. The first sentence or so of the meeting description was displayed along with the meeting name, date, and time. Clicking on an event forwards the user to the event view. Hovering the pen over an event shows the event's description.

• Emails

This section displayed the two most recent sent and received emails. The "more" button expanded the email history, and spit it into two columns: to and from. The first couple lines of the email were shown under the email subject and timestamp. Hovering over an email showed the body text of that email.

• Files

This section was intended to display files the user had associated with the selected person. How great would it be if you could pull up any person's resume, presentations, reports, etc. and view it right there? However, a mechanism for doing this was cut from the project due to time. Rather than scrapping this useful feature entirely, we decided to pull files that were sent to the user as emails attachments. The added bonus was that this could be done and updated automatically. Clicking on a file opened it.

• Fringe Artifacts

Stephen Farrell had been (and still is) working on a very clever social networking engine called Fringe. This automatically fetched, processed, and indexed information relating to people. Some of the information it could show about a person included patents, publications, blog entries, comments, projects/activities, management chain, colleagues, pictures, and more. Enki tied into Fringe, and displayed a few items (called artifacts) about that particular person.

Event View Features:

• Event information

The event name, time and location are shown in the header.

• People

This showed all of the people invited to the event. Clicking on a person takes the user to the person view of that person. Hovering the pen over a person's name or picture showed a abbreviated translucent person-view.

• Description

A description of the event (if provided).

• Files

Displayed the files that were attached to the event. These are probably things like meeting agendas and powerpoint presentations. Clicking on a file launches opened it.

Month View Features:

This was primarily used as a navigation screen to jump between days and months rapidly. Events that lasted all day were shown inside the "day boxes". Notes could be written about the month. Hovering with the pen over a day showed a mini schedule for that day. Clicking on day forwards the user to the day view.

Day View Features:

All the events for the day were displayed (one per row). These were sorted by time, earliest starting first. The title and location of the event were shown, as well as the first 6 people in the meeting. If there was more than 6 attendees, a small "more attendees" button was displayed. Clicking the latter button or the event title forwarded users to the event view. Clicking a person would lead to the person view.

There were several optional "markers" that could be attached to each event. This was to allow people to color-code or iconize their schedules. A few of the markers are shown below. Two automatic markers were the attachment icon, which was present if the meeting had attached files, and the ink icon, which appeared if event had associated written notes. Hovering over the ink marker showed a preview of the written text.

Log View Features:

The log view was one of the last significant features to make it into the Enki demo. Having built a relatively rich system to capture written (and audio) data about people and events (as well as months and days), a quick way to see all this data needed to be developed.

The result was the log view, which took all of the notes for a single day, both written and audio, and presented them in a chronological format. Now, at a glance, a user could scan over all of their notes at the end of the day (or jump back to past dates) and look for important items and remaining to-dos.

Users could jump back to the page the note was take on by clicking the title (located above each note). From there, they could make modifications (perhaps crossing out a to-do that was completed).

Another interesting thing Enki does is show the changes (deltas) between notes on the same item. For example, on John Smith's page, a user writes, "Knows a lot about computers". The ink would be red in color. When the user returns to John's page later that day, the previously written text would show up in black. Now when a new note is added, perhaps "Ask John about new laptops", only this shows up in red.

Although a nice side effect is that it increases the readability of the new text that is being added, the real importance is how this manifests in the log view. The user can easily see when notes were modified for a particular object; each change is timestamped and highlighted in red. An mock example is shown below.