WO2007057898A2

WO2007057898A2 - A system and method for navigation in semantic networks

Info

Publication number: WO2007057898A2
Application number: PCT/IL2006/001325
Authority: WO
Inventors: Yair Dembinski; Jacob Katz
Original assignee: Rafael Armament Development Authority Ltd.
Priority date: 2005-11-16
Filing date: 2006-11-16
Publication date: 2007-05-24
Also published as: IL171995A0; WO2007057898A3

Abstract

An information system that includes a plurality of object types each being associated with an intra data source. Each object type includes a plurality of objects each including object selected data and at least one link to other objects.

Description

A SYSTEM AND METHOD FOR NAVIGATION IN SEMANTIC NETWORKS

FIELD OF THE INVENTION

This invention relates to the general field of navigation in semantic networks.

BACKGROUND OF THE INVENTION

The ever-increasing reliance on data sources in managing enterprise organizations on the one hand and the availability of incompatible data sources (e.g. distinct data sources provided from various vendors) on the other hand, triggered the need to provide a consolidated solution which integrates data from distinct sources/domains based on various types of contents. Data Warehouse (DWH) is a typical solution which copes with this need. The term data warehouse generally refers to the combination of many different data sources across an entire enterprise.

Numerous data warehouse and data warehouse related products are commercially available from companies such as Cognos Corp., Computer Associates (CA), Informatica Corp., NCR, Oracle Corp., PeopleSoft and others.

One of the main shortcomings of the DWH solution is that it affords data manipulation which complies with a pre-defined form and does not allow associative navigation according to the user's needs. For instance, one of the forms of data manipulation is using the so called Online Analytical Processing (OLAP) which facilitates application of a pre-planned query to the DWH. Typically, OLAP tools enable users to analyze different dimensions of multidimensional data, such as in the DWH.

There is thus a need in the art to provide for an enterprise an information system based on different sources and contents and to enable an associative navigation of users through data of the enterprise information system. There is a further need in the art to provide an overall data picture of an object and its relation to other objects, based on unified web interface. SUMMARY OF THE INVENTION

The present invention provides an information system comprising at least two object types each being associated with at least one intra data source; the object type includes a plurality of objects each including object selected data and at least one link to at least one other object.

The present invention further provides an information system comprising at least two object types each being associated with at least one intra data source; the object type includes a plurality of objects each including object selected data and at least one link to at least one other object; and wherein the system includes at least two views associated with the object type such that each view is associated with a different subset of said object type.

Further provided by the present invention is an information system comprising at least two object types, each being associated with at least one intra data source; the object type includes a plurality of objects each including object selected data and at least one link to at least one other object, a method for graphically implementing associative navigation, comprising: displaying in an interface a desired object; selecting in the interface a link of the object; said link leading to a target object; navigating through said link to the target object and displaying in the interface said target object.

The invention still further provides a computer program product comprising a storage storing computer code capable of graphically implementing associative navigation, comprising: computer code portion for providing at least two object types, each being associated with at least one intra data source; the object type includes a plurality of objects each including object selected data, and at least one link to at least one other object; computer code portion for displaying in an interface a desired object; computer code portion for selecting in the interface a link of the object; said link leading to a target object; and computer code portion for navigating through said link to the target object and displaying in the interface said target object. BRIEF DESCRIPTION OF THE DRAWINGS

In order to understand the invention and to illustrate how it may be implemented, a preferred embodiment will now be described, by way of non-limiting example only, with reference to the accompanying drawings, in which:

Fig. 1 illustrates a generalized system architecture, in accordance with an embodiment of the invention;

Fig. 2 illustrates, graphically, objects associated with data sources in an information system, according to an embodiment of the invention; Fig. 3 illustrates a screen layout of an object in an information system, according to an embodiment of the invention;

Figs. 4A-B illustrate, graphically, a sequence of associative navigation, in accordance with an embodiment of the invention;

Fig. 5 is a flow diagram of the operational stages using an information system, in accordance with an embodiment of the invention;

Figs. 6A-B illustrate search screen layout, in accordance with an embodiment of the invention;

Fig. 7 illustrates higher order links in an information system, according to an embodiment of the invention; Fig. 8 illustrates a screen layout of higher order links in an information system, according to an embodiment of the invention;

Fig. 9 illustrates a screen layout of higher order links in an information system, according to an embodiment of the invention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

In the context of certain embodiments of the invention, the following terms will be used:

Object - is a specific topic of interest or real life object, such as person X, organization Y, etc. An object includes object selected data and at least one link. The object selected data is data extracted from at least one external data source. The object selected data can be, for example, selected fields from a given table or tables of a - A -

relational database or databases. By way of another example, the object selected data can be data extracted from one or more data sources by applying simple or complex query to the data of the external data source(s). By way of another example, object selected data can be XML selected tags from external XML file or files. By still another example, the object selected data can be a URL to a selected Internet page. The invention is of course not bound by the specified examples of object selected data. Object type (referred to occasionally also as object class) - Class of objects. Link - a link between two objects.

Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions, utilizing terms such as "processing", "computing", "calculating", "determining", "managing", "controlling" and "executing" "retrieving" or the like, refer to the action and/or processes of a computer or computing system, or processor or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities within the computing system's registers and/or memories into other data similarly represented as physical quantities within the computing system's memories, registers or other such information storage, transmission or display devices.

Embodiments of the present invention may use terms such as processor, computer, apparatus, system, sub-system, module, unit and device (in single or plural form) for performing the operations herein. This may be specially constructed for the desired purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer-readable storage medium, such as, but not limited to, any type of disk including: optical disks, CD-ROMs, magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs) electrically programmable read-only memories (EPROMs), electrically erasable and programmable read only memories (EEPROMs), magnetic or optical cards, or any other type of media suitable for storing electronic instructions, and capable of being coupled to a computer system bus.

The processes/devices (or counterpart terms specified above) and displays presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct a more specialized apparatus to perform the desired method. The desired structure for a variety of these systems will appear from the description below. In addition, embodiments of the present invention are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the inventions as described herein. In addition, the invention is not bound by any specific form of data source and its implementation. By way of non-limiting example a data source may be a relational database implemented in one of a wide range of known per se implementations. Bearing this in mind, attention is drawn to Fig. 1, illustrating a generalized system architecture, in accordance with an embodiment of the invention.

Fig. 1 shows a plurality of external data sources of which, for instance, projects 11, Organizations 12 Deals 13, Products 14 and Events 15 are shown. The external data sources may partially or fully be incompatible one with respect to the other, e.g. they may employ different technology and other variants and/or may not facilitate navigation from one source to the other. For instance, certain data sources may be implemented in SQL™ server and other(s) in Oracle™.

Note that some or all of the external sources are interlinked. For instance, Deals 13 may specify, among the others, the deal number, the identification of the client (client ID) and identification of the products (product ID) that were sold. The client ID is a key in the organization data source 12. The organization data source elaborates the relevant details of the client, e.g. client name, country and others. The product ID is a key in the product data source 14 (that may, likewise, be incompatible with the deals data source). The product data source 14 elaborates the relevant details of the product, e.g. product name, and description, etc. Note that the inter-link between the data sources is not necessarily accomplished through keys. Note also that the invention is not bound by the number of data sources, and any specific characteristics thereof.

Those versed in the art will readily appreciate that the invention is not bound by any specific structure or contents of external sources. For instance an ERP external source may include some of the data of deals, products, projects etc.

The data from the external sources is imported to the information system 16 and stored in storage 18 using, e.g. Application Programming Interfaces(API) generally designated 17 and using predetermined criteria (which data to extract). This is achieved, for instance, in a manner similar to the construction of Data Warehouse (DWH) and as is generally known per se.

Also shown in Fig. 1 is a group of views designated generally as 19 as will be further explained below. Also shown in Fig. 1 is a processor 100 configured to perform the general processing, as will be explained in greater detail below. Also shown is a

Web based interface, facilitating access to the data of the system 16.

Turning now to Fig. 2, it illustrates graphically objects associated with data sources in an information system, according to an embodiment of the invention. As shown, the information system includes storage (18 in Fig. 1) which includes intra data sources 21 to 25 which, in turn, correspond to external data sources 11 to 15. The overall data sources 18 may be regarded intuitively as a kind of DWH.

Note that whilst in the specific embodiment of Fig. 2, the storage 18 is composed of distinct data sources that have one-to-one correspondence to the external data sources; this is by no means binding. Thus, there may be other manners of organizing the intra- data source of the information system. By way of another example, an intra data source may extract data from two or more external data sources. Note also that the invention is not bound by the number of internal/external data sources and other specific characteristics thereof.

Also shown in Fig. 2, is an object class (in this particular example the object class "Deals" which is a class of "Deal" objects). In Fig. 2, a few of these objects are shown (designated generally as 26) and more specifically two objects are shown 27 and

28.

The description below in respect of a distinct object refers specifically to object

27 which is provided for illustrative purposes only and is by no means binding. Generally speaking, an object includes an object selected data extracted from an intra-data source and at least one link to at least one other object. In the Example of object 27, there is shown object selected data (designated in Fig. 2 as "Main Details"

29) that is extracted from data source deals 23. Note that the data in the intra data source 23 is in turn extracted from one or more external data sources. In accordance with certain embodiments, by the term object selected data it is meant mat selected data of a specific deal (in deals data source) is included in the object

27. Tins will be further exemplified below. Also shown in object 27 are four links, i.e. customers, products Events and Projects (200 to 203, respectively). By this particular example, the links lead to respective objects. For example, the customer link 200 leads to a customer object (or objects). The latter objects are extracted from intra- data source 22. By this example, the "customers" constitutes an object class that includes distinct customer objects. As shown in Fig. 2, the deal is linked to one or more customers (through link

200 and concerns one or more products through link 201. The deal may also be related to zero or more business events through link 202 and related to one or more projects (through link 203). The links may be realized through a common key (e.g. the deal details include a key identifying a customer whose further details are "elaborated" in the customer (organizations) data source.

The structure of the object in the manner described in a non-limiting manner with reference to Fig. 2 above facilitates associative navigation, as will be exemplified in greater detail below.

For a better understanding of the foregoing, attention is drawn to Figs. 3 and 4A-B, illustrating a screen layout of an object in an information system, and a sequence of associative navigation stages, in accordance with an embodiment of the invention. The screen layout forms an interface 30 in accordance with an embodiment of the invention, facilitating the associative navigation.

As shown by this example, a deal selected data (31) includes selected details of the intra-deals data source, such as the deal name (32) status (33) the total amount (34) (in $ US), etc. Section 31 corresponds to the section of main details (29 of Fig. 2). Note that the intra data sources are depicted schematically on the bottom right side of the screen (35). The processing of the data instances from the source is performed using processor 100 (see Fig. 1). The lower part of the screen 36 illustrates the link's part of the object. As shown, link 37 illustrates the customer organization (corresponding to the link 200 of Fig. 2) and by this particular embodiment there is further indicated (in parenthesis) the number of linked objects, namely in this particular example 3. This means that there are three customer objects that are "related" to this particular deal. By the same token, other related links are depicted, e.g. related events 38 (in this example 1 related event).

Also shown in Fig. 3 is a list of object Classes 39. Selecting a desired object Class (say Deals 300) would allow to browse (not shown) through the distinct deals that constitute the deals class. This search mode will be further elaborated with reference to Fig. 5.

Fig. 3 also shows a list of related documents 301. The list is associated to the particular object. For instance, all documents that relate to the specified deal, possibly broken down by topics, such as meetings (storing all documents that relate to meetings that pertain to this particular deal - under the meetings folder 302) , proposals which, likewise, stores all documents that relate to proposals that pertain to this particular deal (under the proposals folder 303), etc.

Note that in accordance with certain embodiments, the related documents may be implemented as objects and links. For example, the object may be the document or selected portions thereof (say, the summary) and the links can lead to other objects that are related to this object, say the author (where the author constitutes a different object), etc. It is accordingly appreciated that constituting an object can be implemented by applying any desired query to the external data source (or sources), internal data source and/or combination thereof. For instance, an object may be constituted by all documents that pertain to all deals in a given country, say Japan.

Note that the invention is not bound by the specified interface, its layout and/or its contents, and accordingly, many others which realize objects may be implemented, all as required and appropriate. Moreover, whenever required, additional data may be incorporated in the screen layout (e.g. instead or in addition to the list of entities 39).

Bearing this in mind, attention is drawn to Figs. 3, 4A and 4B, which will assist in understanding an associative navigation in accordance with certain embodiments of the invention. Thus, assuming that the customer's link 37 (see Fig. 3) was selected (e.g. similar to selection of hyper link in an Internet Web page), the list of three objects are expanded (see 40 in Fig. 4A). Now the user can select the (customer) link of interest, say 41 "Astro Solutions". Having selected the specified link, the link leads to the customer object illustrated (by way of non-limiting example) by means of the interface 43 of Fig. 4B. Note that the layout of the interface that includes object 43 is very similar to that depicted in Fig. 3 which illustrated the deal object 30. Reverting to Fig. 4B, the object selected data 44 includes details that pertain to the customer data source. For instance, organization name 45 telephone number 46, etc. By this particular example, the object selected data details that are displayed are selected from those available in the customer (organization) intra data source. Note, incidentally, that the object selected data can be selected from one or more external data sources.

The navigation process from the deal's object to the customer object is realized using also processor 100 (Fig. 1). Next, the list of links that pertain to this object are displayed. For instance, Fig. 4B shows a link 47 to (3) events that are related to this customer. The object selected data of the specified events are detailed in the corresponding event objects and can be viewed by navigating to the desired event object in the manner described in detail above, with reference to Figs. 4A-B.

Also shown in Fig. 4B are additional links, such as the products link 48 (showing that no such products exist as indicated by the digit (0), and "related Rafael Employees" link (49). The detailed data of the related "Rafael Employees" can be extracted from the (external) Human resource data source, etc. Note that object selected data whilst illustrated as retrieved from a distinct data source (e.g. the deals source in Fig. 3, or organization source in Fig. 4B) is an example only and accordingly those versed in the art will readily appreciate that other variants are applicable. For instance, in certain embodiments the object selected data may be derived from more than one external or internal source.

It is accordingly noted that navigating through the links (as shown with reference to Figs. 3 and 4A-B above) afford associative navigation (which in accordance with certain embodiments provide similar experience as surfing in the Internet from one page to the other using Hyper-links).

This is in clear contrast to conventional query tools in, say DWH, such as OLAP which provides a pre-defined set of options and does not allow for associative navigation. In accordance with certain embodiments of the invention, there is provided a graphic interface which facilitates associative navigation by navigating through the objects and links thereby implementing a desired query or report. The associative navigation is realized in that the user can determine on the fly (in a graphic manner) which "route" (link) to choose and navigate to other objects or viewing the desired information.

For instance, in the latter example illustrated with reference to Fig. 3 and 4A, the associative navigation has, in fact, implemented a query (or report) seeking in this particular example for selected data of a given customer (Astro Solutions) which is related to the launcher propulsion components deal. This query has been implemented by associative navigation through graphic interface by navigating from an object (deal) to a "neighboring" object (customers) through a link. This query could have been implemented using known per se querying means (say by using appropriate SQL syntax). The latter approach is not only cumbersome, requiring formulation of a query on-the-fly, but is also not feasible for most of the common users who are simply not familiar with the query's language syntax.

An alternative known per se solution would be to formulate in advance a set of reports that include also the specified query. Note that formulating, in advance, a set of reports which would embrace a similar scope of queries that are applicable using the specified associative navigation would amount to numerous reports. The reports in accordance with known per se techniques are arranged, as a rule, in a distinct screen (or screens) in a given order, say alphabetically, or by date, or in accordance with another pre-defined arrangement. This pre-defined arrangement does by no means correspond to the associative navigation, since the latter is dynamically determined according to the specific "route" of navigation selected by the user.

Bearing this in mind, assume that there are numerous pre-defined reports covering all possible queries that correspond to all possible routes of the associative navigation. A user who wishes to apply the specified query "select data of a given customer (Astro Solutions) which is related to the specific deal of launcher propulsion component would be compelled to switch to the reports screen(s) and search among the numerous reports (arranged, say in an alphabetic order) for this particular report. This is not only a non-friendly solution (requiring switching to the report screen(s)) but also very tedious until the desired report is found and activated. Having eventually identified and invoked the specified report, if the user now wishes to obtain additional data (that correspond to further navigating in the system), this would require re-invoking the tedious task of identifying the appropriate (other) report. In other words, the "report solution" would require launching another exhaustive effort for identifying (among the numerous reports) the one that matched the new query. In contrast, as readily shown in the description above (with reference to certain embodiments of the invention), if the user would now like to continue his associative navigation and browse to objects linked to the specified customer (hereinafter the new query), this is readily realized by simply moving along the link(s) and arriving at the sought object for viewing the desired data instance thereof, all using the same graphic interface.

As specified above, in accordance with certain embodiments the associative navigation is implemented by browsing through hyperlink like links, for moving from one object to another object.

The solution in accordance with certain embodiments of the invention offers, thus, a significant advantage.

Note that in accordance with certain embodiments, the system may employ in addition to the associative navigation approach also known per se "report solution" and possibly other known _pβr se querying schemes.

Note also that in accordance with certain embodiments, known per se querying tools, such as OLAP may also be applicable, all as required and appropriate.

Having described a sequence of associative navigation in accordance with certain embodiments of the invention, there follows a description of a generalized flow diagram of the operational stages using an information system, in accordance with an embodiment of the invention, with reference to Fig. 5. At the onset, the user invokes a search for a desired object of interest. This can be through general (known per se) search techniques, such as keyword search (51), reviewing the search results (52), and selecting an object of interest (53). Assuming, for instance, that the sought object is "deal X", the result would then be (after selecting deal X in 53) displayed, for instance, the screen layout of Fig. 3 (54). The invention is not bound by any particular search technique and accordingly other search techniques may be used, all as required and appropriate. Another non-limiting search approach (by this example an advanced search example) would follow the sequence designated generally as 500. This route will be described with reference also to Fig. 3 using the object class section 39. Thus, after having reviewed the list of available object classes 501, the user selects a desired object class of interest 502 (say deals 300) and thereafter feeds-in the specified constraints for the specific deal (or deals) of interest (503). The list of objects (if any) that comply with the specified constraints are displayed (504) and the user selects the object (e.g. "deal") of interest (53), (not shown in Fig.3).

The user can then apply associative navigation in the manner described above by navigating to a selected object through selection of the desired link (55), e.g. in the manner described above by way of non-limiting example with reference to Figs. 3 and 4A-B.

In accordance with certain embodiments of the invention, the user can extend the associative navigation by navigating also to data in the external data source (56). This is illustrated for example in the screen layout of Fig. 3, where, as shown, the name of the external data source is displayed (302) and the user can navigate to the external data source (thereby, obviously, exposed to a larger volume of pertinent data), by invoking the external source navigation button 303. The implementation of the external source navigation is generally known per se. If desired, in response to hitting the external source navigation button 303, the user can be routed to the external data source interface and view the desired information, using the external data source's viewing/navigation tools. In accordance with another embodiment, once hitting the external source navigation button 303, a navigating will take place directly to the details regarding the specific source object, in the external data source. As may be recalled, the data sources of the information system (e.g. 21 to 25 of

Fig. 2) include data of interest which is imported (in accordance with certain criteria) from external data sources. The external data sources include, as a rule, larger volumes of data and it may well be the case that the user, while navigating through the data objects of the information system as described above, would like to review data residing in the external source(s). As may also be recalled, in accordance with certain embodiments of the invention there is a correspondence (possibly, although not necessarily, one-to-one correspondence) between the data sources of the information system of the invention and the external data sources.

Thus, reverting to step 55 (in Fig. 5) and assuming that the user navigated in the information system of the invention and reviewed objects that include object selected data that pertain to deals, it may well be the case that the user wants to review additional details that pertain to deals which details are not available in the data source of the information system. The sought data may, however, be accessible in the external data source, and, hence, by these particular embodiments the user can continue and navigate using external links from the data source of deals into the external data source of deals (56), as described above. Using this external navigation extends associative navigation not only to intra system navigation (as illustrated in the examples of Figs. 3 and 4A-B), but also to inter system navigation, allowing, for instance, access also to external data sources.

Note that the invention is not bound by any particular manner of navigation to external sources. As further shown, in accordance with certain embodiments, the user can navigate through the related documents (57), see also 301 of Fig. 3).

As was explained above, in accordance with certain embodiments, search options are applicable. Fig. 6A illustrates a certain screen interface for accomplishing a search in accordance with an embodiment of the invention. As shown, window (61) facilitates a general keyword search, where, for example, the user can feed-in an object name such as "customer X"' or "deal Y" and obtain the desired object of interest. In accordance with this particular example there is further provided an advanced search section for each specific object class (62). For instance, in the example of Fig. 6 A a specific search for "people" is provided. After having identified the object class of interest (say people in section 63 of the search screen), there is provided a list of fields which would form constraints for the sought object(s). Thus, after specifying the constraint of interest (say, given name and surname in fields 64 and 65, respectively), the list of object(s), if any, which complies with the specified constraint are displayed and can be browsed, for selecting the object of interest. By this example two results 66 are obtained, as shown in Fig. 6B.

Note that the invention is not bound by the specific search screen layout and/or contents as illustrated in Fig. 6. By way of non-limiting example in addition to the fields of the data instance (62), there may be additional fields for searching object's link of interest. In accordance with certain embodiments, the information system further provides one or more views in respect of one or more objects. The views may define the portions of the object. For instance, in respect of a given object class, say, "deal", a first view may specify a given object selected data (say, list of fields) and various link(s) of interest, whereas in a different view of the same object a different object selected data (say different list of fields) and/or different links may be viewed. In accordance with certain embodiments, the views may be represented, each e.g. in the form of XML file (see 19 in Fig. 1). View may be regarded also as Data picture template of an Object class.

For a better understanding of the foregoing, attention is drawn again to Fig. 4B (by way of example only). Thus, section 400 defines a view of interest, by this particular example "general view". In accordance with this example of the general view of the object class "customer" the specified object selected data 44 is shown and the specified links are shown. Other views may be defined according to the specific needs. For instance, an R&D manager may be interested in a different view of a customer compared to, say, a marketing person. Thus, for example, an R&D manager may not necessarily be interested in the "related events" link (47) which would be of principal interest to, say, a marketing manager. Accordingly, if a view is constructed for an R&D manager, the specified "related event" link (47) of the customer object can be omitted. Accordingly, for each particular view of interest, the specific data that constitutes the object selected data (e.g. 44) as well as the specific links of interest are defined.

In the specific interface depicted in Fig. 4B, the list of possible views may be displayed in the view section 400 and the user can select the view of interest. In accordance with certain other embodiments the appropriate view is displayed as a default, say, according to the identification of the user that logs into the system Whereas in the latter example the contents of the object selected data and/or the links may vary, depending upon the desired view, the invention is not bound by these constituents and accordingly other portions of the object may be configured differently for different views.

In accordance with certain embodiments, views may be associated with the security measures and privileges of authorized user. Thus, the privileges of a given view may prescribe the users that are allowed to access and view this particular view.

Note that the invention is not bound to use of objects in the manner specified. Thus, as illustrated above with reference to Figs. 3 and 4, certain embodiments utilize a so-called first order link, such a link being directly derived from an external data source (or data sources). Thus, for example, a link between a deal and competitor (where deal and competitor are both entities, such as records or field in records, in an external data source or sources) and the link therebetween is reflected also in the external data source and being "imported" to the information system, in accordance with certain embodiments of the invention.

In accordance with certain other embodiments, a so-called second order link is used. As may be recalled, an object includes object selected data, and at least one link to at least one object. For instance, the specific deal was related to the specific customer (through the link), as illustrated in the example of Figs. 3 and 4a-b, above. If the link is also reflected in the external data source (data sources) it is regarded in accordance with certain embodiments as a first order link.

In accordance with certain embodiments a second order or higher order links can be generated in the information system of the invention. The second or higher order links are links that do not directly exist in the external data source. Note that the second order links facilitate navigation in a similar manner to that described above.

For a better understanding, consider the following simplified example. Assuming that the external data source includes the entity "country" and is linked to another entity "deals" that were made in this country. Assume also that the external data source (or other external source) includes the entity "deals" and link to another entity of "competitors" (for this particular deal). There is no direct link from country to competitors (indicative of all competitors in respect of deals made with a country or countries). If such a link is generated in the information system, it is regarded, in accordance with certain embodiments, as second order link. The generation of the second order link can be implemented, e.g. by invoking a preliminary query applied to, say: the deal objects, country objects, competitor objects and the existing links between country and deal and deal and competitor. It is recalled that after generating the second order links they can be navigated through in an associative fashion, as was described in detail above.

Attention is now drawn to Fig. 7, illustrating a second order link in an information system, according to an embodiment of the invention. Fig. 7 illustrates the object class deal (designated generally 71) that consists of various specific objects such as object 72. Fig. 7 further depicts data sources 73 as described above with reference to Fig. 2. The object 72 includes deal object selected data that includes the country field (signifying the country of the customer) and link to the competitor object (signifying the list of competitors for this particular deal in the specified country). When viewing object 74 in Fig. 7- Country J - one can see its object selected data 75, and its links. One of the links is the link to competitors 76. TMs link is a second order link, because it was created in the following way: 71 - reflects all the deals that are connected to Country J. For each of these deals, the competitors are taken, and a new link is created between the country and the competitors. This link did not exist in the external or the intra data source - It was derived from two existing links: deal - country and deal-competitor. Note that the second order link is not bound by any specific manner of creation, but rather it reflects a link that did not exist in neither the intra data source nor in the external data source. Note, incidentally, that the object 74 was generated by applying a query in the manner exemplified above. Accordingly, it should be noted that in accordance with certain embodiments objects can be extracted not only as a portion of an external data source or sources, but, if desired, also by invoking a query to obtain a new object class. Fig. 8 illustrates a screen layout of a second order link in an information system, according to an embodiment of the invention, and with reference to the example of Fig. 7.

As shown the upper portion of the screen layout includes data instance 81 that pertains to the country (Japan). Also shown are links 82 to (aggregated) objects that are related to Japan. Link 83 leads to all competitor objects for all deals in Japan. As shown (indicated by the number (2)), there are two competitors. Fig. 9 illustrates more clearly the list of links of which link 91 leads to product objects (of Rafael that were sold in deals with Japan). Clicking the link would open a window illustrating the list of the three products sold to Japan. Clicking the selected product would lead to product object (not shown), all as explained in detail above.

In accordance with other embodiments, higher order to links can be used. For instance, a link can lead from the country Japan to Rafael employees that participated in a visit to a customer in Japan. This is an example for a 3rd order link between a Rafael employee and the country Japan (employee - visit - customer - country).

The construction of the query to realize the specified third order link is generally known per se and therefore will not be expounded upon herein. In a similar manner, higher level links may be constructed by querying links of lower level and possibly other data. Other data can be, for instance, data from the intra data source or sources and/or data from external source or sources. Note that the invention is not bound by the utilization of links of the n^lh order in the manner specified.

In accordance with certain embodiments, the relation between objects may be implemented directly, e.g. through common key, but this is not necessarily always the case.

It will also be understood that the system according to the invention may be a suitably programmed computer. Likewise, the invention contemplates a computer program being readable by a computer for executing the method of the invention. The invention further contemplates a machine-readable memory tangibly embodying a program of instructions executable by the machine for executing the method of the invention.

The present invention has been described with a certain degree of particularity, but those versed in the ait will readily appreciate that various alterations and modifications may be carried out, without departing from the scope of the following Claims:

Claims

1. An information system comprising at least two object types each being associated with at least one intra data source; the object type includes a plurality of objects each including object selected data and at least one link to at least one other object.

2. The system according to Claim 1, wherein said system includes interface configured to facilitate in a graphic manner associative navigation using said link from a source object to another object, constituting a navigated object, whereby said navigated object includes object selected data and at least one link to at least one other object which is related to the navigated object.

3. The system according to Claim 2, wherein said interface is configured to display the navigated object.

4. The system according to Claim 2, wherein said interface is configured to facilitate the following, repetitively: (i) displaying a source object, (ii) navigation from the source object to a selected target object, through a link associating the source and the target objects, and (iii) displaying the target object.

5. The information system according to Claim 1, wherein each intra-source is a derivative of at least one external data source and wherein at least two of the external sources are incompatible, one with respect to the other.

6. The information system according to Claim 2, wherein each link is displayed as a hyperlink like link, and wherein said interface is configured to facilitate in a graphic manner associative navigation from an object to an object by invoking a hyperlink .

7. The information system according to Claim 2, wherein said interface is further configured to display for each link a number of other objects which are related to the source object.

8. The information system according to Claim 1, wherein at least one of said links being of first order.

9. The information system according to Claim 1, wherein at least one of said links being of second order.

10. The information system according to Claim 1, wherein at least one of said links being of n⁽¹ order (n>2).

11. The information system according to Claim 4, further comprising at least one link to at least one external source.

12. The information system according to Claim 2, wherein said interface is further configured to display documents related to the object.

13. AIT information system comprising at least two object types each being associated with at least one intra data source; the object type includes a plurality of objects each including object selected data and at least one link to at least one other object; and wherein the system includes at least two views associated with the object type such that each view is associated with a different subset of said object type.

14. The system according to Claim 13, wherein said system includes interface configured to facilitate selection of a view and in respect of selected view, applying in a graphic manner associative navigation using said link from an object to another object, constituting a navigated object, whereby said another object includes object selected data and at least one link to at least one other object which is related to the navigated object.

15. The information system according to Claim 13, wherein at least one of said links being selected from a group that includes first order link, second link, n'¹ order link (n>2).

16. The information system according to Claim 13, wherein said interface is further configured to display documents related to the object.

17. In an information system comprising at least two object types each being associated with at least one intra data source; the object type includes a plurality of objects each including object selected data and at least one link to at least one other object, a method for graphically implementing associative navigation, comprising: a) displaying in an interface a desired object; b) selecting in the interface a link of the object; said HnIc leading to a target object; c) navigating through said link to the target object and displaying in the interface said target object.

18. The method according to Claim 17, wherein at least one of said links being selected from a group that includes first order link, second order link, n^th order link (n>2).

19. The method according to Claim 17, further comprising generating said n^th . order link (n>2) by applying a query to at least a lower order link.

20. A computer program product comprising a storage storing computer code capable of graphically implementing associative navigation, comprising: computer code portion for providing at least two object types, each being associated with at least one intra data source; the object type includes a plurality of objects each including object selected data, and at least one link to at least one other object; computer code portion for displaying in an interface a desired object; computer code portion for selecting in the interface a link of the object; said link leading to a target object; and computer code portion for navigating through said link to the target object and displaying in the interface said target object.