This section is intended to introduce the reader to various aspects of art, which may be related to various aspects of the present invention that are described or claimed below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present invention. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.
The success of many organizations, including businesses, depends upon collaboration between numerous members of the organization. This is particularly true for large corporations. For example, the successful introduction of a new product line by a large corporation will often depend on a number of disparate groups working together to design, manufacture, market, and distribute the products. In another corporate context, various representatives from different departments will meet to discuss an issue that affects their respective departments.
In many cases, a person at such a meeting is placed in an unfamiliar context, having to cross organizational boundaries and interact with people from multiple departments that could have different concerns, perspectives, or goals than the person is accustomed to considering. In some instances, the individual will not even know in which department or departments the meeting participants work. Further, even if the departments of the participants are known, the individual could lack a complete understanding of the structure of those departments or other information that would be helpful in tailoring a discussion or presentation to the participants. Still further, merely receiving the names of the participants and their respective departments does little, from the individual's perspective, to indicate the interrelationships between the participants or to learn about the personalities of the persons attending the meeting.
One or more exemplary embodiments of the present invention will be described below. In an effort to provide a concise description of these embodiments, not all features of an actual implementation are described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.
The present techniques address the information need highlighted above. In the case of corporate meetings, it could be advantageous for an employee entering such unfamiliar territory to gain an understanding of how the different participants interrelate. For instance, it would be helpful for a product engineer attending a meeting to know whether the participants are from a marketing department, a manufacturing department, some other department, or some combination thereof, and how the participants are related to one another. By way of further example, it would generally be desirable for an individual in the meeting to realize that all of the other participants are from the same department and report to the same manager, or that one participant in particular has managerial authority over the other participants. Such knowledge would facilitate more efficient discourse and allow the employee to tailor a presentation or statements in view of the perspective of the other participants. Additionally, it could also be helpful for an employee to learn that a participant works in the same department as someone else that the employee already knows, thereby providing supplemental context to aid in understanding the participant's role and goals.
Turning now to the figures,
The process 100 also includes receiving relationship data (block 104). In the present embodiment, the relationship data includes a plurality of persons and a set of connections representing relationships between two or more of the persons. In one embodiment, the relationship data includes various contacts of an individual. These associated contacts can be entered manually, such as by a user; can be collected from an electronic address book; or can be collected in some other manner. Further, this relationship data can either be kept privately, such as on a user's computer, or kept in a central location.
In the present embodiment, each user has a distinct set of relationship data containing their own contacts. However, in a second embodiment, the relationship data includes not only a user's contacts, but also the contacts of other individuals. Thus, in the second embodiment the relationship data could also include the contacts of the user's contacts, contacts of the user's contacts, and so on. This centralized relationship data could be entered manually, gathered from the internet web or email logs of the organization, or collected in some other fashion. Further, in one embodiment, the centralization of relationship data for a plurality of persons in a central, public database adds further synergy by providing additional contacts and links from which to determine interrelationships and aiding the probability that additional associations will be discovered, as described in further detail below.
Process 100 further includes querying the organizational directory and relationship data (block 106) to identify a member of the organization. In the present embodiment, identifying the member includes determining a short path between the member and another person in an association network (block 108). As would be appreciated by one skilled in art, an association network includes a set of persons and associations or connections between individual persons of the set. For example, in the present embodiment, the association network includes one or more members listed in the organizational directory, one or more persons included in the relationship data, and various links between these persons. These links can include hierarchical connections, associative connections such as those contained in the relationship data, or some combination of these two. Short paths are discussed in greater detail below with reference to
An exemplary display 200 of output data generated by the process of
The second portion 204 of display 200 provides hierarchical information related to the Targets A-D. Notably, portion 204 provides a management chain for each of the query targets. These management chains include Persons N-Y. Display 200 also includes third portion 206 which provides various interconnections between any persons in the group including the user and Targets A-D. As used herein, the term “interconnections” is employed to denote the existence of an intermediate contact common to two members of this group. For instance, in the present example, person J is a common contact for both the user and Target C, and Persons N and Z are contacts common to both Target A and Target B. In other words, the existence of an interconnection between two persons indicates the existence of a short path between these persons that includes only the interconnection and the two persons. The social network including persons contained in the organizational directory and relationship data can be visualized or graphed, as illustrated in
A visual representation 300 of the association network provided by the data of display 200 is illustrated in
However, as will be appreciated by one skilled in the art, in other instances short paths can include links provided via the relationship data as well as those provided by the hierarchical structure. For instance, in an alternative embodiment, one could consider the path from User 302 to Target D, via Person A, Person D, and Target A, to be a short path. As can be seen in graph 300, this path, including both the hierarchical links and contact links, is considerably shorter than the path obtained through sole reliance on the organizational structure, in which the path would include Target A, Persons N-T, and Persons AA-FF.
It should also be noted that while various persons of any discovered short path could be members of the organization whose directory is queried by process 100, other persons in the short path could be external to the organization. Particularly, in one embodiment, the user or other identified starting point for the process is a member of the organization, as are one or more of the associated individuals in the relationship data. However, in alternative embodiments, the user or other individual identified as the origin for the short paths, the one or more associated contacts of the relationship data, or some combination thereof are external to the organization. The present techniques are thus broadly applicable regardless of whether the user or other identified starting point or any intermediate persons are members of the organization.
An alternative process 400 for information management is depicted in
Once a short path including one or more of the user's contacts is discovered, it is displayed (block 412). The process 400 also includes displaying interconnections (block 414) between any of the user and the search targets. As will be appreciated, process 400 can be employed to determine short paths between a user and a single search target as well as a user and multiple search targets. In further embodiments, short paths between various search targets themselves can be determined. Additionally, as in process 100, the results of the query can be displayed in a graph illustrating various short paths and hierarchical links of the social network.
Another exemplary process 500 for information management is provided in
The process 500 also includes querying the organizational directory and relationship data (block 506) to identify a member of the organization. In particular, identifying such a member includes determining a management chain (block 508) containing both the search target and at least one of the user's contacts that is also a member of the organization. Once this chain is determined, it is displayed (block 510). In one embodiment, additional queries are performed for the user's contacts to determine how close these people are to the target individual in the management chain. Those contacts closer than some defined threshold from the target individual, such as four steps, are added to the displayed management chain.
An exemplary display 600 of such a management chain is provided in
Yet another alternative process 700 for information management is illustrated in
As will be appreciated, one or more of the present embodiments can be implemented through use of a computer or other electronic device. The functional aspects of certain embodiments could be encoded as a computer program or application instructions onto a computer-usable medium. It should be noted that such a computer-usable medium could include, but is not limited to, a compact disc, a floppy disc, a flash memory device, a hard drive, random-access memory, other memory resources, and the like. Application instructions for implementing the disclosed functionality can be stored on one or more of these or other computer-usable media in full accordance with the present techniques.
While the invention may be susceptible to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and will be described in detail herein. However, it should be understood that the invention is not intended to be limited to the particular forms disclosed. Rather, the invention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the invention as defined by the following appended claims.
Number | Name | Date | Kind |
---|---|---|---|
5802515 | Adar et al. | Sep 1998 | A |
6415368 | Glance et al. | Jul 2002 | B1 |
6470269 | Adar et al. | Oct 2002 | B1 |
6493702 | Adar et al. | Dec 2002 | B1 |
6591257 | Martinka et al. | Jul 2003 | B1 |
6603485 | Forman | Aug 2003 | B2 |
6631451 | Glance et al. | Oct 2003 | B2 |
6701333 | Suermondt et al. | Mar 2004 | B2 |
6728692 | Martinka et al. | Apr 2004 | B1 |
6757669 | Adar et al. | Jun 2004 | B1 |
6772374 | Forman et al. | Aug 2004 | B2 |
6802586 | Forman | Oct 2004 | B2 |
6823323 | Forman et al. | Nov 2004 | B2 |
6915284 | Adar et al. | Jul 2005 | B2 |
6947936 | Suermondt et al. | Sep 2005 | B1 |
7136876 | Adar | Nov 2006 | B1 |
7860889 | Martino et al. | Dec 2010 | B1 |
8335785 | Adar | Dec 2012 | B2 |
20030018637 | Zhang et al. | Jan 2003 | A1 |
20030050824 | Suermondt et al. | Mar 2003 | A1 |
20030101024 | Adar et al. | May 2003 | A1 |
20030120733 | Forman | Jun 2003 | A1 |
20030138085 | Forman et al. | Jul 2003 | A1 |
20030139901 | Forman et al. | Jul 2003 | A1 |
20030145009 | Forman et al. | Jul 2003 | A1 |
20030158855 | Farnham et al. | Aug 2003 | A1 |
20030172067 | Adar et al. | Sep 2003 | A1 |
20030174179 | Suermondt et al. | Sep 2003 | A1 |
20030186243 | Adamic et al. | Oct 2003 | A1 |
20030204581 | Adar et al. | Oct 2003 | A1 |
20030204604 | Adar et al. | Oct 2003 | A1 |
20030217106 | Adar et al. | Nov 2003 | A1 |
20040024718 | Adar et al. | Feb 2004 | A1 |
20040024719 | Adar et al. | Feb 2004 | A1 |
20040024769 | Forman et al. | Feb 2004 | A1 |
20040030882 | Forman | Feb 2004 | A1 |
20040059697 | Forman | Mar 2004 | A1 |
20040064464 | Forman et al. | Apr 2004 | A1 |
20040068499 | Adar et al. | Apr 2004 | A1 |
20040111431 | Zeller et al. | Jun 2004 | A1 |
20040148266 | Forman | Jul 2004 | A1 |
20040148267 | Forman | Jul 2004 | A1 |
20040158628 | Forman | Aug 2004 | A1 |
20040169695 | Forman | Sep 2004 | A1 |
20040172374 | Forman | Sep 2004 | A1 |
20040203645 | Forman et al. | Oct 2004 | A1 |
20050024826 | Bash et al. | Feb 2005 | A1 |
20050055373 | Forman | Mar 2005 | A1 |
20050102368 | Forman et al. | May 2005 | A1 |
20050131855 | Forman et al. | Jun 2005 | A1 |
20050165715 | Farnham et al. | Jul 2005 | A1 |
20050182780 | Forman et al. | Aug 2005 | A1 |
20050187664 | Bash et al. | Aug 2005 | A1 |
20050228789 | Fawcett et al. | Oct 2005 | A1 |
20050246337 | Forman et al. | Nov 2005 | A1 |
20050272087 | Adamic et al. | Dec 2005 | A1 |
20060009994 | Hogg et al. | Jan 2006 | A1 |
20060064436 | Fowler et al. | Mar 2006 | A1 |
20060136419 | Brydon et al. | Jun 2006 | A1 |
20070136429 | Fine | Jun 2007 | A1 |
Entry |
---|
www.netlingo.com/dictionary/l.php, log, downloaded on Apr. 21, 2014 (1 page). |