US20100121877A1 - Systems and Methods for Retrieving Data - Google Patents
Systems and Methods for Retrieving Data Download PDFInfo
- Publication number
- US20100121877A1 US20100121877A1 US12/622,184 US62218409A US2010121877A1 US 20100121877 A1 US20100121877 A1 US 20100121877A1 US 62218409 A US62218409 A US 62218409A US 2010121877 A1 US2010121877 A1 US 2010121877A1
- Authority
- US
- United States
- Prior art keywords
- entity
- entities
- information
- relationship
- relationships
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
- G06F16/288—Entity relationship models
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0282—Rating or review of business operators or products
Definitions
- This invention relates to computer-based methods and systems for retrieving, organizing, and distributing data and, more particularly, to computerized methods and systems for retrieving, organizing, and distributing financial research data.
- derivative influences might include information about a company's industry, a competitor, a supplier, a geographic region, or any subject that is somehow “related” to a primary investment.
- expanding the universe of relevant information to include these derivative influences often exponentially increases the volume of information an investment professional must review.
- investment professionals also expend an increasing portion of their research efforts discovering and exploring the derivative influences on investments.
- the rate at which a single investment professional can retain and recall the relationships among various research sources falls behind the rate the research information is produced and delivered.
- the invention relates to computer based tools that allow investment professionals to associate information with a particular entity upon receipt, and to further facilitate the retrieval, update, and distribution of that information, either upon request or in real-time.
- Such tools allow investment professionals, who can be responsible for providing investment advice and/or making investment decisions, to identify and record the derivative influences affecting an investment through the use of an entity/relationship model where the entities represent any topic on which research can be conducted, and the relationships represent the influences the topics exert on one another.
- the investment professional can classify information according to one entity (which, for example, may be a legal entity, an industry, a market grouping, a topic, or other area of interest) and define and modify relationships among the entities.
- the defined relationships allow an investment professional to query the tools for information about a first entity, and obtain in response “indirect” or “derivative” information associated with other entities that have defined relationships, (either direct or indirect) with the first entity.
- information relating to entities that are indirectly related to an entity having one or more degrees of separation may be returned.
- entities are identified that are not directly related to the first entity, where the set of direct or indirect relationships connecting the entities are such that information associated with a distant entity may still be relevant to the selected entity.
- the ability to quickly receive, retrieve, and evaluate the information associated with a relevant entity can help investment professionals make investment decisions.
- Such tools can facilitate the easy capture, storage, retrieval, and distribution of the great variety of information available to investment professionals in its various forms (e.g. email, instant message, document, newswire release, etc.) without an analyst having to remember or determine all of the numerous companies, industries, or entities to which the information might pertain.
- Such a system allows a user to quickly assign an information item to a primary entity (or other topic), and to use centrally stored relationships among the entities and rules governing the use of the relationship to determine if there are additional entities may be affected by the information.
- a system that stores the entities, the relationships, and the rules governing the use and creation of the relationships in a central database, while distributing access to view and modify the central entity/relationship model in real-time, can allow multiple users of the system to benefit from the combined knowledge and experience of all the current and previous users.
- an individual analyst with specific knowledge were unavailable, the knowledge of the relationships between entities remains available to other users.
- relationships become institutional knowledge, and can be leveraged into productivity enhancements and a strategic advantage over other competing investment houses.
- a plurality of entities and a plurality of relationships among the entities are provided, each entity having a entity type and each relationship having a relationship type and relationship direction.
- An entity-relationship network is created using the entities and the relationships.
- a plurality of information items is received, and each information item is associated with at least one corresponding entity.
- a request for information items associated with a selected entity is received.
- Based on the selected entity, the relationship types and relationship directions of the entity-relationship network a subset of the plurality of entities is determined. The information items associated with the subset of entities is then provided.
- the entities in the subset include (i) entities that have a direct relationship with the selected entity, the relationship having one of a number of predetermined relationship types and a direction; and (ii) entities that have an indirect relationship with the selected entity in which each relationship relating such an identified entity with the selected entity has the same predetermined type and direction.
- An entity can be any sort of topic.
- the entity can be, for example, a company, an industry, an index, a person or a subject.
- the relationships between the topics can have a direction or directions.
- a relationship can be unidirectional—e.g. from the first entity to the second entity or from the second entity to the first topic, bi-directional—e.g. from the first entity to the second entity and from the second entity to the first entity, or hierarchical—e.g. a parent entity can include one or more child entities.
- the relationship can represent a reciprocal relationship i.e., the creation of one relationship from a first entity to a second entity implies a second relationship from the second entity to the first, thus reducing the time needed to specify a set of relationships among many entities.
- the relationship can also include a strength indicator to indicate how closely related one entity is to another, for example, how strong of an influence exists between the entities.
- the relationship between the entities can have a relationship type.
- a legal relationship e.g., parent-subsidiary, or licensor-licensee
- a business relationship e.g., customer, supplier, distributor, competitor, or industry member/participant
- formal membership requirements e.g., a company that is part of particular stock market index
- informal e.g., a company that belongs to a standards consortium
- influential e.g., a political issue impacts the performance of a company.
- the relationships in the network can include both hierarchical and influential relationships.
- the information can be in any format that can be stored and/or identified. Examples include electronic messages, emails, instant messages, financial reports, voicemails, web pages, research reports, electronic documents, press releases, etc.
- the information can be received using one of more communications avenues, including electronic messaging, electronic mail, instant messaging, voice messaging, scheduled database query, or triggered database query.
- a first user of a first computer can associate information items with entities, and a second user of a second computer can request the information items associated with the association defined by the first user.
- the second user can request information associated with the selected entity, and in some embodiments, receive information associated with the subset of entities via email, voicemail, screen display, personal data assistant, and print.
- one such system for presenting information comprises a entity definition module for defining entities, a relationship definition module for defining relationships among the entities and attributing a relationship type and relationship direction to each relationship, a receiver for receiving information, an information management module for associating the received information with at least one of the entities, an information retrieval module for, upon receiving a request for information associated with the one of the entities, retrieving information associated with a subset of the entities, the subset based, at least in part, on the relationship types and relationship directions among the entities in the subset, and a display module for presenting the retrieved data.
- These modules can be implemented, for example, with computer software in conjunction with computer hardware (e.g., networked computers).
- the system can include a database module for storing one or more of the entities, the relationships, the information, and the association of information with entities.
- the system may also include a rules engine for governing the relationships between the entities.
- the system may further include a messaging module for distributing modifications to one or more of the entities, relationships, and rules. The messaging module can distribute the modifications asynchronously as the changes are made, or in some embodiments, upon demand by the user.
- the system may also include a permissions module for enforcing user access privileges to one or more of the entities, the relationships, and the information associated with the entities.
- FIG. 1 is a block diagram of an embodiment of a system according to the invention.
- FIG. 2 is a block diagram of an embodiment of a server in the system of FIG. 1 .
- FIG. 3 is a more detailed block diagram of an embodiment of the server of FIG. 2 .
- FIG. 4 is a block diagram of an embodiment of a client in the system of FIG. 1 .
- FIG. 5 is a block diagram of an embodiment of a system according to the invention.
- FIG. 5 a is a block diagram of an embodiment of a system according to the invention.
- FIG. 5 b is a flowchart of an embodiment according to the invention.
- FIG. 6 is a screen display of the work area in an embodiment of the client of FIG. 4 .
- FIG. 7 is a screen display of the join tool in an embodiment of the client of FIG. 4 .
- FIG. 8 a is a screen display of the entity finder module in an embodiment of the client of FIG. 4 .
- FIG. 8 b is a screen display of the create new entity module in an embodiment of the client of FIG. 4 .
- FIG. 8 c is a screen display of the notes module in an embodiment of the client of FIG. 4 .
- FIG. 9 is a screen display of the entity details module in an embodiment of the client of FIG. 4 .
- FIG. 10 a is a screen display of the relationship browser module in an embodiment of the client of FIG. 4 .
- FIG. 10 b a screen display of the add new relationship module in an embodiment of the client of FIG. 4 .
- FIG. 11 is a flowchart of an embodiment of a method according to the invention.
- FIG. 12 a is a screen display of the drop box module in an embodiment of the client of FIG. 4 .
- FIG. 12 b is a screen display of the drop box preferences module in an embodiment of the client of FIG. 4 .
- FIG. 13 is a flowchart of an embodiment of a method according to the invention.
- FIG. 14 is a screen display of the content browser module in an embodiment of the client of FIG. 4 .
- FIG. 15 a is a screen display of the calendar module in an embodiment of the client of FIG. 4 .
- FIG. 15 b is a screen display of the research wire module in an embodiment of the client of FIG. 4 .
- FIG. 16 is a flowchart of an embodiment of a method according to the invention.
- an information storage and retrieval system 100 includes at least one server 104 , and at least one client 108 , 108 ′, 108 ′′, generally 108 . As shown, the information storage and retrieval system 100 includes three clients 108 , 108 ′, 108 ′′, but this is only for exemplary purposes, and it is intended that there can be any number of clients 108 .
- the client 108 is preferably implemented as software running on a personal computer (e.g., a PC with an INTEL processor or an APPLE MACINTOSH) capable of running such operating systems as the MICROSOFT WINDOWS family of operating systems from Microsoft Corporation of Redmond, Wash., the MACINTOSH operating system from Apple Computer of Cupertino, Calif., and various varieties of Unix, such as SUN SOLARIS from SUN MICROSYSTEMS, and GNU/Linux from RED HAT, INC. of Durham, N.C. (and others).
- a personal computer e.g., a PC with an INTEL processor or an APPLE MACINTOSH
- operating systems e.g., a PC with an INTEL processor or an APPLE MACINTOSH
- MICROSOFT WINDOWS family of operating systems from Microsoft Corporation of Redmond, Wash.
- the MACINTOSH operating system from Apple Computer of Cupertino, Calif.
- Unix
- the client 108 could also be implemented on such hardware as a smart or dumb terminal, network computer, personal data assistant, wireless device, information appliance, workstation, minicomputer, mainframe computer, or other computing device that is operated as a general purpose computer or a special purpose hardware device solely used for serving as a client 108 in the information storage and retrieval system 100 .
- clients 108 are operated by users of the system to receive, review, store and retrieve data regarding investment opportunities.
- the client computer 108 includes client applications 122 , client software 120 , or both.
- client application 122 is a web browser application that allows the client 108 to request a web page (e.g. from the server 104 ) with a web page request.
- An example of a web page is a data file that includes computer executable or interpretable information, graphics, sound, text, and/or video, that can be displayed, executed, played, processed, streamed, and/or stored and that can contain links, or pointers, to other web pages.
- a user of the client 108 manually requests a web page from the server 104 .
- the client 108 automatically makes requests with the web browser.
- Examples of commercially available web browser software are INTERNET EXPLORER, offered by Microsoft Corporation of Redmond, Wash., and NETSCAPE NAVIGATOR, offered by AOL/Time Warner of Mountain View, Calif.
- the client 108 also includes client software 120 .
- the client software 120 provides functionality to the client 108 that allows a user to request and receive data using the methods described herein.
- the client software 120 may be implemented in various forms. For example, it may be in the form of a Java applet that is downloaded to the client 108 and runs in conjunction with one or more client applications 122 .
- the client software may be a standalone application written in C/C++, C#, Java or other appropriate client programming language.
- the client software 120 may be in the form of an application plug-in written in Visual Basic, C/C++, or C# that operates within a client application 122 .
- the client software 120 may be in the form of a standalone application, implemented in a multi-platform language such as Java, in a .Net Framework language such as C#, or in native processor executable code.
- the client software 120 if executing on the client 108 , the client software 120 opens a network connection to the server 104 over the communications network 112 and communicates via that connection to the server 104 .
- the client software 120 and the web browser may be part of a single client-server interface 124 ; for example, the client software can be implemented as a “plug-in” to the web browser.
- the web browser is but one possible example of a client application, and others may include word processors, spreadsheets, operating system extensions, email clients, as well as others.
- a communications network 112 connects the client 108 with the server 104 .
- the communication may take place via any media such as standard telephone lines, LAN or WAN links (e.g., T1, T3, 56 kb, X.25), broadband connections (ISDN, Frame Relay, ATM), wireless links, and so on.
- the network 112 can carry TCP/IP protocol communications, and HTTP/HTTPS requests made by the web browser and the connection between the client software 120 and the server 104 can be communicated over such TCP/IP networks.
- the type of network is not limited, however, and any suitable network may be used.
- Typical examples of networks that can serve as the communications network 112 include a wireless or wired ethernet-based intranet, a local or wide-area network (LAN or WAN), and/or the global communications network known as the Internet, which may accommodate many different communications media and protocols.
- LAN or WAN local or wide-area network
- Internet global communications network
- the server 104 is preferably implemented on one or more server class computers that have sufficient memory, data storage, and processing power and that run a server class operating system (e.g. SUN Solaris, GNU/Linux, MICROSOFT WINDOWS 2000, and later versions, or other such operating system).
- server class operating system e.g. SUN Solaris, GNU/Linux, MICROSOFT WINDOWS 2000, and later versions, or other such operating system.
- Other types of system hardware and software than that described here could also be used, depending on the capacity of the device and the number of users and the amount of data received.
- the server 104 may be part of a server farm or server network, which is a logical group of one or more servers.
- servers 104 there could be multiple servers 104 that may be associated or connected with each other, or multiple servers could operate independently, but with shared data.
- application software could be implemented in components, with different components running on different server computers, on the same server, or some combination.
- a server 104 includes a client file communication module 206 that is the interface for communication with clients 108 involving the transfer of files.
- files may be transferred from the client 108 to the server 104 , from the server 104 to the client 108 , or both.
- the client communication module 206 can be implemented as software running on one or more servers, or may be implemented as a stand-alone server.
- the client file communication module 206 can provide an interface both to client software 120 and to client applications 122 , so that, for example, a user can access investment performance information through a web browser, a word processing application, or to review other data, and so on, while the client software 120 can be used for requesting and receiving additional information, or for defining parameters of the system.
- the interface to each of the client software 120 and the client applications 122 can be implemented separately or in combination.
- the client file communication module 206 can also communicate using other protocols or mechanisms.
- the server 104 includes a client messaging communication module 208 that is the interface for communication with clients 108 involving HTTP/S requests and responses, Java messages, SMTP messages, POP3 messages, instant messages, RSS feeds, as well as other electronic messages.
- messages may be transferred from the client 108 to the server 104 , from the server 104 to the client 108 , or both.
- the client messaging communication module 208 can be implemented as software running on one or more servers, or may be implemented as a stand-alone server.
- the client messaging communication module 208 can provide an interface both to client software 120 and to client applications 122 , so that, for example, a user can send and receive e-mail, instant messages, and so on, while the client software 120 can be used for requesting and receiving additional information, or for defining parameters of the system.
- the interface to each of the client software 120 and the client applications 122 can be implemented separately or in combination.
- the client messaging communication module 208 can also communicate using other protocols or mechanisms.
- the client messaging communication module 208 communicates with the application server 212 , which provides the main programming logic for the operation of the system.
- the application server 212 is implemented as one or more application programs running on a server class computer, which may be the same or different computer as the client file communication module 206 or the client messaging communication module 208 .
- the application server 212 receives requests for data stored in a database (such as an email, the historical performance of an investment vehicle, etc.) from users via the client messaging communication module 208 , provides updated data to the client 108 , and enforces system, application, and user level rules.
- the server 104 also includes a database system 220 , which stores data related to the investment opportunities, user permissions, industry data, and the like in one or more databases.
- the database server 220 may store information relating to entities defined by the users of the system, relationships among the entities, stored content, user information, server availability, and web traffic information.
- the database server 220 may also contain separate databases for relationships 244 , entities 248 , contacts of the users 252 , user permissions and security information 256 , content metadata 260 , and others.
- the database server 220 provides data to the application server 212 .
- database server 220 is the MySQL Database Server by MySQL AB of Uppsala, Sweden, the PostgreSQL Database Server by the PostgreSQL Global Development Group of Berkeley, Calif., or the ORACLE Database Server offered by ORACLE Corp. of Redwood Shores, Calif.
- the server 104 also includes a file server 224 and a file storage system 216 , which stores static data files 232 related to investment opportunities such as web pages, word processing documents, spreadsheets, PDF files, and others.
- the file server 224 receives requests for static data files from the client 108 via the client file communications module 206 , transmits the request to the file storage system 216 , and manages the status of the file once it is sent to the client 108 .
- the file storage system 216 also stores application configuration information 236 , such as server names, communication protocols, directory structures, and other aspects of the application that may be customized at the application, server, or system level.
- the file server 216 can also store user configuration information 240 such as screen preferences, menu options, security and administrative information, and other functional aspects of the application that may be customized from user to user.
- user configuration information 240 such as screen preferences, menu options, security and administrative information, and other functional aspects of the application that may be customized from user to user.
- the file storage system 216 stores only data files, while file metadata such as the file location, the author, the creation date, file revision history and other metadata are stored in the content metadata DB 260 .
- the client 108 includes a message client module 322 , a web services client 326 , and file transfer client module 334 .
- the message client module 322 receives messages via the Java messaging service or other similar communications service from the application server 212 via the client messaging communications module 208 .
- the message client 322 Upon receiving a message from the client messaging communications module 208 , the message client 322 facilitates the display of the message on the user interface 124 .
- the web services client module 326 facilitates receiving data from the application server 212 via a web services server module 324 such as the Apache Axis Web Services software via HTTP or some similar protocol.
- Both the web services module 324 and the client message communication module 208 publish data, for example, in XML format such that data may be automatically received by the web services client 326 and displayed on the user interface 124 without user interaction.
- the file transfer client 334 may request and receive files from the file server 224 using a protocol such as the File Transfer Protocol (FTP), WebDAV or variant thereof via the client file communications module 206 .
- the server 104 may also include a contention resolution module 219 for managing user permissions and data privacy and contention issues when the application server 212 requests or updates data in the database system 220 .
- the server 104 includes connectivity architecture 229 comprising adapters for receiving, filtering, and formatting data feeds from sources external to the system.
- an on-site adapter 312 receives data from on-site services 314 , via the Java messaging service or other similar messaging service.
- a second, off-site adapter 316 can receive data from off-site data providers 318 such as FirstCall available from Thompson Financial and Street Events available from CCBN via a standard File Transfer Protocol (FTP) or other file transfer protocols or RSS feeds.
- FTP File Transfer Protocol
- different adapters may be employed for different data sources.
- the server 104 may also include, in some embodiments, a component container module 328 such as the Enterprise Java Beans container for storing application components which may be used by the application server 212 .
- a component container module 328 such as the Enterprise Java Beans container for storing application components which may be used by the application server 212 .
- the client 108 includes application plug-in adapters 404 and application function modules 406 .
- the application plug-in adapters 404 (“plug-ins”) facilitate the capture of data, files, content, and other information presented to the user in other commercially available or custom developed software applications that reside on the client 108 or the server 104 .
- Exemplary applications include, but are not limited to, spreadsheet application plug-ins 426 for software such as Microsoft Excel; postscript data format (PDF) viewer application plug-ins 428 for software such as Adobe Acrobat; word processing application plug-ins 430 for software such as Microsoft Word; instant messenger application plug-ins 432 for software such as AOL's Instant Messenger; web browser application plug-ins 434 for software such as Netscape Navigator or Microsoft Explorer; and email application plug-ins 436 for software such as Microsoft Outlook, Lotus Notes, Qualcomm Eudora; as well as adapters for other client-resident applications from which information may be captured.
- the plug-in adapters 404 may facilitate capturing information from applications that reside on the server, 104 .
- the plug-ins 404 are initiated by selections from a menu or buttons on a toolbar within a client application 122 , and in some cases may not require the client software 120 to be operational or to be invoked.
- a user may receive an electronic mail message with important information regarding a particular entity.
- the toolbar for the user's electronic mail client application has been updated with the email plug-in 436
- the user only needs to highlight the desired message (or portions thereof) and click or select the plug-in button.
- the email plug-in 436 captures the information, and sends it to the file system 216 via the file server 224 .
- data being viewed on a World Wide Web content page, as part of a newswire, or from other publicly or privately published documents may be captured and stored in the system using plug-ins adapted for the particular client application 122 used to receive and view the information.
- the application function modules 406 facilitate the review, creation, and manipulation of various elements of the system such as information items, personal display and security settings, application defaults, etc.
- some embodiments may include an interest list module 408 for maintaining one or more lists of topics that may be of particular interest to a user or group of users. Examples of topics that may be included in such a list include companies, financial markets such as the NASDAQ or NYSE, investment vehicles such as bonds or equities, geographic regions such as Japan or the European Union, industries such as computers or automobiles, political issues such as unions or healthcare reform, and the like.
- Some embodiments can include an entity finder module 422 for finding or creating an entity to which information may be attributed. For example, a user may be interested in the computer hardware industry, and create entities for the companies that manufacture and sell computer hardware.
- the list of entities is pre-populated with a list of companies based on membership in an industry group such as those companies that are listed on a particular stock exchange.
- the list of entries can be created by the users of the system.
- Some embodiments can include a relationship list module 410 for reviewing and defining relationships between entities. For example, if company A supplies raw materials such as steel or computer chips to company B that company B uses to make its products, a relationship may be defined indicating that company A supplies goods or services to company B. Similar relationships may be created for companies that are competitors, partners, subsidiaries, as well as other business and legal relationships.
- Some embodiments can include additional application modules such as a content list module 412 for reviewing information pertaining to one or more entities; a client administration module 414 for facilitating the customization of the user interface 124 for individual users; a drop box module 416 which allows users to easily associate a file or partial content from a file with a particular entity; a contact list module 418 for maintaining information about people from whom one or more users of the system receive information; a calendar module 420 for listing dated events pertaining to entities such as earnings announcements or product launches; a notes module 421 for allowing the creation, storage, and sharing of user-created notes; a research wire module 424 for reviewing information such as research reports published by financial analysts; and a client web services module 425 to facilitate the synchronous request/response of data on the server.
- additional application modules such as a content list module 412 for reviewing information pertaining to one or more entities; a client administration module 414 for facilitating the customization of the user interface 124 for individual users; a drop box module 416 which allows users to
- an asynchronous interface composed of a messaging client and a messaging server, for example a Java Messaging Service client/server pair, facilitate the asynchronous update of data residing on the client 108 as it is updated on the server 104 and exposed using the web services module 324 residing on the server 104 .
- a set of rules 505 govern the creation of the entities 510 , the type of entities 515 that can be created, the creation of the relationships 520 , the types of relationships 525 that can be created, and which relationships may be used to link entities of a given type.
- the rules 505 can describe the entity types 515 that can be created.
- the rules 505 can specify the entity types 515 as “corporate” entities representing companies, “index” entities representing groups of publicly held companies used to calculate a market statistic, “industry” entities representing a specific area of commerce, and “topic” entities representing subjects that may impact other entities.
- the rules 505 can specify the relationship types 525 that can be created.
- the rules 505 can specify the relationship types 525 as the relationship types listed in Table 1 below.
- the rules 505 govern the relationships that one entity type may have with other entity types.
- a corporate entity may have different relationships with other corporate entities than it would have with an index entity or a topic entity.
- Table 2 contains one possible listing of relationship types and the rules associated with how they can be used to relate different entity types. It should be noted, however, that these exemplary relationships represent one particular set of relationships that may be implemented in a specific embodiment of the invention. Additional relationships used to describe the associations of entities with each other may be obvious to those skilled in the art of analyzing the performance of a company, an industry, or other similar entity.
- the rules 505 may permit the user to create an “is in index” relationship to an entity of type “index” and a “distributes for” relationship to an entity of type “corporate.”
- the user may create an entity for an industry such as “healthcare” and a relationship to another industry such as “insurance.”
- the rules 505 may prohibit certain relationships based on the entity and relationship types—e.g. the rules 505 may prohibit an “is in index” relationship between an industry entity (healthcare) and an index entity (NYSE) because industries are not listed on stock exchanges.
- a system that allows users to create, modify, and delete entities and the relationships between them, and to have these changes distributed across multiple users in real time provides a greater degree of flexibility to analysts.
- Such a system can focus on those industries or aspects of investment opportunities that are important to a given organization, maintain knowledge when people leave, and evolve as industries, companies, and investment opportunities grow and change.
- both direct relationships entities connected by one or more relationships
- indirect relationships entities separated by one or more intermediate entities, but otherwise reachable through multiple “hops,” thus creating a chain of relationships
- Two possible categories of propagating relationships include hierarchical and influential.
- the relationships are reciprocal, i.e. a certain relationship type from entity A to entity B by definition implies a related or “reciprocal” relationship from B to A.
- a series of propagating hierarchical relationships may be used to describe a large industry, a sub-industry, and a further specialized market within the sub-industry using the “has industry member” relationship and its reciprocal relationship “is in industry” among the hierarchical industry entities.
- the automobile industry may have a “has industry member” relationship to a “truck industry” entity, which in turn may have the same “has industry member relationship with a “light truck industry” entity.
- trucks industry Moving back from “light truck industry” the relationships would indicate that the subordinate entity is related to the parent industry by an “is in industry” relationship.
- the “light truck industry” has an “is in industry” relationship with the “truck industry.”
- Similar hierarchies can be represented for indices, for example, where a company's stock is a component of a market index. For example, an analyst that follows a market index such as the NASDAQ index may be interested in information items associated with companies such as Microsoft, Cisco, and others.
- results of requests for information associated with NASDAQ can also include information associated with Microsoft.
- a particular equity or other investment vehicle can be directly or indirectly related to a mutual fund, hedge fund, or other actively or passively managed investment portfolio.
- an influential relationship type describes relationships among entities that can influence each other, and is also reciprocal.
- a first entity influences a second entity
- an “influences” relationship connects the two from the first entity to the second
- a reciprocal “is influenced by” relationship connects the same two entities in the opposite direction—e.g., from the second entity to the first.
- a series of influential relationships can be used to connect entities representing political issues, world leaders, legal issues, and geographic regions: in a particular example, an entity representing “Bush Administration” has an influential relationship with an entity representing “Energy Policy” which in turn has an influential relationship with a third entity representing “Middle East Policy.”
- the reciprocal nature of the influential relationships provides bi-directional relationships among the entities.
- the reciprocal “is influenced by” relationship can describe the relationship from the “Energy Policy” entity to the “Bush Administration” entity.
- the relationships may be further annotated with an “influence factor.” For example, an analyst may believe that the Bush Administration is highly influential on a Middle East Policy entity, but in contrast, only slightly influential on a “Tort Reform” entity.
- an exemplary entity-relationship network facilitates the identification of a set of entities that are related through one or more relationships.
- the entity-relationship network includes a set of entities, which can include companies such as GE 550 and Haliburton 552 , business topics that may influence the financial or operational performance of the company or market such as asbestos 554 and tort reform 556 , political topics such as the Bush Administration 560 and foreign policy 558 , and industries such as the oil industry 562 . Entities can also include individuals such as analysts 564 that comment on or cover certain companies, industries, or other topics. As an example, a user of the system may be researching a potential investment in Haliburton.
- the information items associated with the Haliburton entity 552 will be retrieved from the database and returned to the user.
- the information items associated with those entities that are direct neighbors of the Haliburton entity 552 e.g. the asbestos entity 554 and the oil industry entity 562 (because the asbestos entity 554 “influences” Haliburton and Haliburton has an “is in industry” relationship to the oil industry entity 562 .
- the user wishes to expand the scope of information being retrieved by the system even further, he can instruct the system to retrieve information items that are associated with entities that are indirectly related to the Haliburton entity 552 through multiple relationships.
- entities that are directly related to the entity of interest include those entities that can be reached by traversing only one relationship in the network.
- the system retrieves information items that are associated with entities that are connected, either directly or indirectly, to the entity of interest through both direct and indirect relationships and that have the same relationship type and direction linking previously identified entities.
- a first entity may be influenced by a second entity, and thus the system travels across an “influenced by” relationship from the first entity to the second.
- the second entity may in turn be influenced by a third entity, and the system can travel across a second “influenced by” relationship from the second entity to the third.
- entities that are separated from an entity of interest by more than one relationship can be included in the subset of entities for which information items are retrieved.
- the number of relationships needed to get from the entity of interest to another entity sometimes referred to as the “degree of separation” or “levels of indirection,” (one for direct relationships, more than one for indirect relationships), can vary, and in some cases may be limited by the user.
- the system identifies the relationship between the Haliburton entity 552 and the asbestos entity 554 .
- the relationship is a direct “is influenced by” relationship, and therefore the system determines if the asbestos entity 554 “is influenced by” any other entities not yet identified.
- an “is influenced by” relationship connects the Tort Reform entity 556 to the asbestos entity 554 , and further connects the Bush Administration entity 560 to the tort reform entity 556 .
- an “is influenced by” relationship connects the Foreign policy entity 558 to the oil industry entity 562 .
- Haliburton entity 552 increases the set of entities of interest from three (Haliburton 552 , asbestos 554 , and oil industry 562 ) to six (Haliburton 552 , asbestos 554 , and oil industry 562 , plus tort reform 556 , Bush Administration 560 , and foreign policy 558 ).
- influences on entities of interest can be traced through numerous intervening entities to the “root cause” entity, and information items associated with that entity can be reviewed for information that may be pertinent to investment decisions regarding the entity of interest.
- FIG. 5 b illustrates one example of a method for determining the entities to include in the subset of entities for which information items are to be retrieved.
- a focus identity is selected (STEP 570 ).
- the focus entity generally indicates the company, index, topic, or other subject area of interest being researched.
- Each neighboring entity is then treated as a focus entity, and any relationships that are of the same type (i.e., propagating hierarchical or influential relationships) are followed to the next set of neighboring entities (STEP 576 ).
- the system determines if there are any remaining relationships that have not be followed (DECISION STEP 578 ) and if so, repeats STEP 576 until there are no additional entities that can be reached.
- the set of entities is then defined as the subset of entities (STEP 580 ) for which information items will be returned.
- numerous relationships may be used to govern travel from the focus entity to another entity, and, as described above, certain relationships may be “stronger” i.e., the impact that one entity has on another may be much greater than others. For example, only relationships of a certain strength might be followed. In other cases, where an entity represents a company with diverse businesses and product offerings, a stronger “is in industry” relationship may be desired when describing the company's relationship to a core business, as opposed to a business that they are only tangentially related to.
- the user may indicate that the traversal process terminate after some number of iterations, or that entities that require the traversal of some number of relationships (e.g., more than four) are not included.
- an analyst may allow the system to traverse the entire network, but only follow those relationships that have a high strength indicator.
- a combination of degree or separation and relationship strength may be used to determine the subset of entities.
- a user may indicate that the set of identified entities includes all entities that are separated from the focus entity by three or fewer intermediate entities regardless of relationship strength, and subsequently follow only strong relationships to entities that are four or more degrees of separation from the focus entity.
- users may instruct the system to only follow a subset of the relationships emanating from the focus entity. For example, where one entity has a large number of immediate direct relationships, following every relationship may result in an unmanageable result set.
- the set or retrieved information items can be kept to a manageable number.
- the system provides a work area 600 on the client 108 .
- the work area 600 can include one or more of the application function modules 406 described above.
- the work area 600 can include a toolbar 610 allowing users to access functions of the system through a system of menus.
- the work area can also include the entity finder module 422 , the research wire module 424 , and the calendar module 420 .
- the application function modules can be positioned on the user interface 124 at different locations as determined by the user.
- the entity finder module 620 can be positioned along the left side of the screen, with the research wire module 630 and calendar module 530 to the right of the entity finder module 620 .
- the positions of each module, both relative to the user interface 124 and to each other may be saved to the user configuration file system 240 using the client administration module 412 such that each time an individual user access the system, the layout of the work area 600 is consistent.
- the configurations of the work area 600 may be saved at the application level, group level, or on an individual user basis.
- a join tool 700 may be used to group application function modules 406 together such that when a user selects data to be presented in one module the data presented in the joined application function modules 406 is updated.
- the join tool 700 can provide instructions to the user on how to join application function modules 406 . For example, if the entity finder module 422 and the research wire module 424 were grouped using the join tool 700 , and the user changed the selected entity in the entity finder module 422 from General Electric to IBM, the data presented in the research wire module 424 would be updated with data pertaining to IBM.
- the join tool 700 may also provide multiple join groups. For example, a user may select certain application function modules 406 to be part of a group and select from a drop down box 730 the color to be associated with the group and displayed along the band at the top of the application function modules 406 in each group. By identifying each group using the colors 720 , a user may easily identify those modules grouped together while looking at the work area 600 , which may contain numerous application function modules 406 , some of which may be grouped and others which may not. This provides the user with a work area 600 that is synchronized across application function modules 406 , to the extent desired.
- the join tool 700 also provides a listing of previously defined groups, and the colors associated with each group 720 .
- the entity finder module 422 includes a display window 810 , an entity list 820 , and a define new entity button 830 which is used to create new entities using the create new entity screen 840 .
- the display window 810 provides the user with the name of the current entity about which information is being displayed in other application function modules 406 that are grouped with the entity finder module 422 .
- the entity list 820 provides a listing of the entities about which information may be retrieved from the system. In some embodiments, the entity list 820 may be created by a central administrator, while in other embodiments the entity list may be created by individual users of the system.
- the entities listed in the entity list 820 may be restricted on a global level, group level, or an individual level. For example, if an individual analyst is responsible for the automobile industry, the entity list 820 may be limited to automobile manufacturers, their suppliers, and other topics related to the automobile industry such as oil futures, labor unions, and interest rates.
- the create new entity screen 840 includes an entity type data window 850 , an entity name data window 860 , a entity short name data window 870 , and an entity alias data window 875 .
- the values available to a user in the entity type data window 850 may be limited to values defined by a central administrator and stored in the database 220 , and in other embodiments the values may be user defined and stored in the user configuration files 240 .
- the list of entity types may be limited to corporations, indices (such as NASDQ or NIKKEI), industries (such as automotive or computer hardware), and topics (such as asbestos, war, or the environment).
- the topic entities may be either public or private. Public entities may be used throughout the application by multiple users of the system, while private topics may be limited to one individual user or a particular group of users.
- the entities may be predefined, with periodic updates available from vendors specializing in how entities are related and influence each other.
- a vendor can supply a pre-populated database or flat file containing lists of corporate entities listed on the NYSE and NASDQ, their parent and subsidiaries, and general industries.
- the same vendor, or in one embodiment another vendor may also supply the relationships among the entities.
- This data can be imported into the system.
- the data files can be appended or overwritten with files updated based on the passage of time, and such events as large mergers, delistings, bankruptcies, or initial public offerings.
- the create note details screen 880 includes a source field 855 , a sentiment field 890 , and a note text field 895 .
- the note details screen 880 allows a user to create free form text notes about a topic.
- the source field 885 identifies the source of the note, thus allowing users to see who created the note 895 . By providing this information, the system allows users to filter notes based on the source of the note 895 , or give greater weight to a note based on its author.
- the sentiment field 890 allows the author of the note 895 to provide an indication of whether the note 895 reflects positively or negatively on a topic or entity. For example, a first user may only want to see positive notes from a second user, but wish to see all notes from a third user. This feature allows users to customize and filter the information they receive when inquiring about an entity of interest.
- an edit entity details screen 900 includes one or more data fields in which detailed data may be entered describing an entity. For example, if an entity being described is a corporation, an address data field 910 may be used to enter the physical location of the corporation. Similarly, phone and fax data fields 920 may be used to capture the corporation's telephone number and facsimile number, respectively.
- entity details screen 900 for a corporate entity include an employee count data field 930 , an email data field 940 for storing the email addresses of one or more contacts at the corporation, a data table 950 of URL addresses representing web pages on the World Wide Web that may be relevant to the corporation, and a data table 960 containing the names and other descriptive information regarding the officers of the corporation, such as their titles, ages, educational backgrounds, previous employers, as well as other data.
- the relationship browser module 410 displays a current entity 1005 , other entities 1015 to which the current entity 1005 has been related, the currently selected related entity 1010 , the type of relationships 1020 , and provides the ability to create new relationships using the add a relationship option 1025 .
- the current entity 1005 may be a large retail chain.
- the relationship types 1020 that may be relevant to such an entity may be the “competes with,” distributes for,” and “relates to” relationships. More particularly, if a user is interested in a retail chain that sells toys, the entities listed under the “competes with” relationship type may include other large retailers that also sell toys.
- the entities listed under the “distributes for” relationship type may include toy manufacturers, and the entities listed under the “relates to” relationship type may include topics such as “dock strike” if the user determines such an event could potentially affect the financial performance of the current entity 1005 .
- the relationship browser may contain iconic representations for each entity called entity icons.
- entity icon may include a graphical representation of the entity's type, an activity number value representing the number of system notifications generated for that entity during some previous period of time (24 hours, 1 week, 1 month, etc.), as well as other information.
- the activity number can be calculated dynamically, and the formula employed to determine the activity number can be based on any system event for an entity and/or its related entities.
- New relationships may be created using the add a relationship function 1025 and the add a relationship screen 1030 , which includes data fields for selecting the relationship type 1020 and the related entity 1015 , and a check box 1035 for creating reciprocal relationships.
- the relationship types are limited to a fixed set of relationships defined by a central administrator and stored in the database 220 , as described above.
- the relationship types, the entity types, the direction and reciprocal nature of the relationships, and the rules governing the application of the relationships to the entities may be defined by individual users.
- the users have complete control over the creation of these objects, and how they are instantiated within the entity-relationship network, and in some cases an administrator retains some control over the rules governing the creation and use of the objects.
- the user-created objects can be shared with other users of the application, other members of particular groups of users, or kept private.
- FIG. 11 illustrates one embodiment of a method for defining entities and the relationships among the entities.
- a user, administrator, or other supplier of data builds an initial set of rules, entities, and relationship types (STEP 1103 ).
- a user may then determine if additional entities are necessary to adequately model the markets, industries, or topics of interest (STEP 1105 ).
- the user determines if the entities exist in the initial set (DECISION STEP 1110 ), for example, by using the entity finder module 422 described above. If one or more of the entities does not exist, the user then creates the entities (STEP 1115 ) using the create new entity screen 740 . Once the entities are created, the user then determines which entities are to be related (STEP 1120 ).
- the user determines the relationship type (STEP 1125 ) that best describes the relationship, and creates the relationship (STEP 1130 ) using the relationship browser module 410 .
- the data can be customized to the areas of interest of a particular firm, group, or individual. For example, if an analyst firm follows a particular investment strategy that runs contrary to widely-held principles, or has uncovered derivative influences on a company or industry that other analysts have not, the ability to create and modify the entities is valuable. In one exemplary case, an analyst or firm may have determined that certain weather patterns (exceptionally warm winters, for example) have a statistically significant impact on automobile sales during certain months.
- the relationship may be a unidirectional relationship—e.g. a company entity may have a “member of” relationship to an index entity.
- the user may determine that upon creating the first relationship, a second, reciprocal relationship is warranted, thus creating a bi-directional relationship. For example, if a user instructs the system to create a “sells to” relationship from company A to company B, and further instructs the system to create a reciprocal relationship, the system can automatically create a “buys from” relationship from company B to company A.
- the creation of the reciprocal relationships can be governed by the rules 505 .
- the rules 505 may limit the valid reciprocal relationships to “buys from.” By providing this option, the system provides a quick method for creating sets of relationships based on reciprocal associations between entities.
- the drop box module 1205 facilitates the saving of an information item to the file system 216 or database 220 without having to use the client applications software 122 .
- the drop box module 1205 remains active on the client 108 and visible on the user interface 124 , and allows a user to deposit a document, spreadsheet, or other file directly from one location on the client 108 or other computer connected to the client 108 over the network 112 to the file system 216 by “dragging and dropping” the file onto the drop box module 1205 .
- default values for characteristics of the information items may be set using the drop box preferences module 1210 .
- the user may be reviewing numerous information items about a particular entity, and set the drop box default fields 1215 to reflect the current entity, the type of data being reviewed, and the author of the information items, thus allowing the user to associate numerous items with a particular entity quickly.
- FIG. 13 illustrates one embodiment of a method for associating information with an entity.
- a user receives information relating to one or more of the entities of interest to the user (STEP 1305 ) and in some cases creates notes relating to an entity of interest (STEP 1307 ).
- the user captures the information (STEP 1310 ) using one or more of the methods described above.
- the user determines the proper entity to which the information should be associated (STEP 1315 ).
- the user determines if the entity to which the information should be associated exists (STEP 1320 ), and if the entity does not exist, creates the new entity (STEP 1325 ) using the methods described above.
- the user may then assign the information to the entity (STEP 1330 ), for example, using one of the application plug-in adapters 404 or the drop box module 1205 above. Because the applications into which the adapters 404 plug-in are already in use and the analysts are familiar with their operation, minimal additional training is necessary for an analyst to start using the system.
- a user may receive an email with a document attached to the mail message describing a company's product launch strategy for an upcoming software release.
- the client 108 may recognize the client application 122 needed to view the document, and launch the application 122 , if not already running.
- the user determines the entity with which the document should be associated, and highlights the relevant portion(s) of the document.
- the user selects the plug-in 430 in the client application 122 , and the information is saved to the file system 216 , with the associations provided by the user.
- the content browser module 412 facilitates requests for and review of information associated with a current entity 1005 and in some embodiments, entities related to a current entity.
- the content browser module 412 includes the current entity of interest 1005 , a select entity data field 1405 , a display related information toggle 1410 , summaries of each information item 1415 retrieved from the database system 220 or file system 216 , and an indication 1420 of who authored the information items 1415 , as well as other descriptive information about the item.
- the select entity data field 1405 allows a user to change the current entity 1005 to a new current entity, and thus review information items 1415 associated with a new current entity.
- the display related information check box 1410 allows the user to indicate whether the list of information items 1415 will include information items for the current entity 1005 only (unselected), or for the current entity 1005 and the entities related to it (selected). For example, if a user was interested in reviewing the information associated with a computer manufacturer, the user could select the entity name for that corporation from the select entity data field 1405 , and the summaries of each information item 1415 associated with that entity would be listed. In addition, a user may be interested in the derivative influences potentially affecting the computer manufacturer, e.g.
- the user selects the display related information check box 1410 and therefore receives information associated with the other corporations, industries, and topics that are related to the computer manufacturer. This allows the user to gain a broader perspective of the factors that may influence the company, and therefore affect its financial performance.
- the summaries of each information item 1415 may include information about the information items.
- the summaries may include a title, the type of file (voice clip, financial report, press release, as well as others), the author's name, the date on which the file was last modified, the size of the file, the format of the file (such as Word for Windows, Excel, PDF, HTML, as well as others), and comments about the file.
- this information is static and cannot be changed by individual users, where as in other embodiments, the ability to modify the summary information can be assigned to individual users or groups of users.
- the calendar module 420 and research wire module 424 further facilitate the review of information associated with a current entity 1005 and in some embodiments, entities related to a current entity.
- the current entity data selection window 1405 and display related information check box 1410 perform similar functions as on the content browser module 412 described above.
- the calendar module 420 further includes date navigation buttons 1505 , an unfiltered selection box 1510 , an action menu 1515 , and summaries of information items 1520 organized by date.
- the date navigation buttons 1505 allow a user to scroll to a previous week or subsequent week, and review the events scheduled during that time period.
- the time periods may be hours, days, months, quarters, years, or other periods of time into which events can be grouped.
- the unfiltered selection box 1510 allows a user to instruct the calendar module 420 to display all events for all companies (unchecked) or only those events related to the company or entity selected in the entity data selection window 1405 (checked).
- the research wire module 424 further includes summaries 1525 of information items received from either internal or external news and broadcast sources via the adapters 312 and 316 .
- the summaries 1525 include the date and time an information item was published, the company about which the item pertains, and a text summary of the item. By clicking on the summary 1525 of an information item, the user may then review the entire contents of the item.
- FIG. 16 illustrates one embodiment of a method for retrieving information associated with one or more entities.
- the user begins by selecting an entity of interest (STEP 1605 ) using the select entity data field 1405 on the content browser module 412 .
- the client software 120 requests (STEP 1610 ) the information associated with the selected entity from the server 104 , which retrieves the requested information (STEP 1615 ).
- the server determines (DECISION STEP 1620 ) if the display related information check box 1410 is selected. If the display related information check box 1410 is selected, the server 104 also retrieves the data (STEP 1625 ) associated with the entities related to the selected entity.
- the client 108 Once the complete set of information is retrieved from the file system 216 and database system 220 , it is received (STEP 1630 ) by the client 108 and presented to the user for review. Because the relationships were previously established and the information was associated with the first entity, the analyst needs no additional knowledge about the industry or entity to receive the derivative information. In some embodiments where updates to entities, relationships, rules, or information is asynchronously provided to the client 108 , the user receives updated information (STEP 1635 ) using one or more of the methods described above.
- an analyst may be following the semiconductor industry in general, and have a particular interest in the XYZ Semiconductor Company (“XYZ Co.”).
- XYZ Co. XYZ Semiconductor Company
- another analyst created a “supplier/customer” relationship between XYZ Co. and ABC Computer Company and a “relates to” relationship between XYZ Co. and a topic identified as “Trade with China.”
- the analyst selects XYZ Co. from the select entity data field 1405 .
- the analyst may be interested in information directly associated with XYZ Co., and also information associated with related entities. To receive this information, the analyst checks the display related information check box 1410 .
- the server 104 then retrieves the information associated with XYZ Co., ABC Computer Co, as well as any information associated with the topic “Trade with China.” This facilitates a more complete analysis of XYZ Co.'s current and future performance because an increase in demand for computers manufactured by ABC Co. may directly influence the demand for semiconductors manufactured by XYZ. Co. Likewise, political and economic events that may affect the importation of goods from China may also affect XYZ Co. if their manufacturing operations are located there.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Development Economics (AREA)
- Databases & Information Systems (AREA)
- Entrepreneurship & Innovation (AREA)
- Accounting & Taxation (AREA)
- Economics (AREA)
- Finance (AREA)
- Game Theory and Decision Science (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Human Resources & Organizations (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Operations Research (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- Educational Administration (AREA)
- Information Transfer Between Computers (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
This invention relates to a computer-based method and system for facilitating the retrieval, classification, and distribution of information. In one embodiment, a method for providing information comprises providing a plurality of entities, each having an entity type, providing a plurality of relationships among the entities, each relationship having a relationship type and direction, and constructing an entity-relationship network comprising the entities and relationships. The method further includes receiving a plurality of information items, facilitating the association of the information items with at least one corresponding entity, receiving a request for information items associated with a selected one of the entities, determining a subset of the entities based on the selected entity, the relationships, the relationship types and the relationship directions, and providing the information items associated with the subset of the entities.
Description
- This application is a continuation-in-part of co-pending U.S. patent application Ser. No. 10/712,076, entitled “Systems and Methods for Retrieving Data”, filed on Nov. 13, 2003.
- This invention relates to computer-based methods and systems for retrieving, organizing, and distributing data and, more particularly, to computerized methods and systems for retrieving, organizing, and distributing financial research data.
- The data available to individuals and institutions that monitor the global financial markets is wide-ranging. Investment professionals who may be responsible for monitoring a particular company or industry sector may receive thousands of individual information items each day. Some of these information items may be presented in well-formatted and categorized formats from reliable and well-known sources such as financial statements filed with a stock exchange or the Securities and Exchange Commission, whereas other information items may be in the form of informal correspondence such as email or instant message, phone conversations, or face to face meetings. Furthermore, the application of numerous internet communications technologies to the research and information publishing process over the last decade has increased the volume of information available for analysis and the speed at which it is delivered. Often, opportunities to take advantage investment opportunities based on such information, may exist for only a short time. Furthermore, the opportunity to act on information may not be concurrent with the arrival of the information itself. It is critical that investment professionals be able to monitor the numerous sources of information, discern pertinent information from irrelevant information, analyze it as quickly as possible and base decisions on the information as it arrives. Investment professionals must therefore be able analyze, in short periods of opportunity, historic information that is often difficult and time-consuming to recall or retrieve manually.
- In addition to being able to understand information relating to a primary investment of interest—e.g. information relating to a specific company or industry—an effective investment professional must also immediately understand and appreciate so-called “derivative influences.” Examples of derivative influences might include information about a company's industry, a competitor, a supplier, a geographic region, or any subject that is somehow “related” to a primary investment. However, expanding the universe of relevant information to include these derivative influences often exponentially increases the volume of information an investment professional must review. As a result, investment professionals also expend an increasing portion of their research efforts discovering and exploring the derivative influences on investments. As the breadth of derivative influences increases, the rate at which a single investment professional can retain and recall the relationships among various research sources falls behind the rate the research information is produced and delivered. Further complicating the process, when an investment professional receives information pertaining to a particular investment, there may be numerous other investments that are indirectly affected by the information. This universe of affected entities in which one can invest is constantly changing, as companies are bought and sold, enter new markets, and forge new partnerships.
- The same performance pressures apply to an investment firm as a whole. To be effective, all members of the firm want to share information in real time, and allow individuals to rapidly sort and distribute the massive amounts of information available. At the same time, the fundamental research basis of a firm's investment decisions are coming under greater scrutiny, and heightening the need for a clear research audit trail.
- Therefore, to be effective, an investment professional must become increasingly productive with respect to the receipt, review, and recording of information such that he can adequately support the investments made by the firm.
- In general, the invention relates to computer based tools that allow investment professionals to associate information with a particular entity upon receipt, and to further facilitate the retrieval, update, and distribution of that information, either upon request or in real-time. Such tools allow investment professionals, who can be responsible for providing investment advice and/or making investment decisions, to identify and record the derivative influences affecting an investment through the use of an entity/relationship model where the entities represent any topic on which research can be conducted, and the relationships represent the influences the topics exert on one another. The investment professional can classify information according to one entity (which, for example, may be a legal entity, an industry, a market grouping, a topic, or other area of interest) and define and modify relationships among the entities. The defined relationships allow an investment professional to query the tools for information about a first entity, and obtain in response “indirect” or “derivative” information associated with other entities that have defined relationships, (either direct or indirect) with the first entity. In some cases, information relating to entities that are indirectly related to an entity having one or more degrees of separation (with each degree of separation in this context denoting one direct relationship between two entities) may be returned. Thus, entities are identified that are not directly related to the first entity, where the set of direct or indirect relationships connecting the entities are such that information associated with a distant entity may still be relevant to the selected entity. The ability to quickly receive, retrieve, and evaluate the information associated with a relevant entity can help investment professionals make investment decisions.
- Such tools also can facilitate the easy capture, storage, retrieval, and distribution of the great variety of information available to investment professionals in its various forms (e.g. email, instant message, document, newswire release, etc.) without an analyst having to remember or determine all of the numerous companies, industries, or entities to which the information might pertain. Such a system allows a user to quickly assign an information item to a primary entity (or other topic), and to use centrally stored relationships among the entities and rules governing the use of the relationship to determine if there are additional entities may be affected by the information.
- Moreover, a system that stores the entities, the relationships, and the rules governing the use and creation of the relationships in a central database, while distributing access to view and modify the central entity/relationship model in real-time, can allow multiple users of the system to benefit from the combined knowledge and experience of all the current and previous users. In addition, if an individual analyst with specific knowledge were unavailable, the knowledge of the relationships between entities remains available to other users. Thus, relationships become institutional knowledge, and can be leveraged into productivity enhancements and a strategic advantage over other competing investment houses.
- While particularly useful for investment professionals, these collaborative research tools are not limited to that field, and can be used in many other areas with great advantage.
- In one aspect, a plurality of entities and a plurality of relationships among the entities are provided, each entity having a entity type and each relationship having a relationship type and relationship direction. An entity-relationship network is created using the entities and the relationships. A plurality of information items is received, and each information item is associated with at least one corresponding entity. Further, a request for information items associated with a selected entity is received. Based on the selected entity, the relationship types and relationship directions of the entity-relationship network, a subset of the plurality of entities is determined. The information items associated with the subset of entities is then provided.
- In some embodiments, the entities in the subset include (i) entities that have a direct relationship with the selected entity, the relationship having one of a number of predetermined relationship types and a direction; and (ii) entities that have an indirect relationship with the selected entity in which each relationship relating such an identified entity with the selected entity has the same predetermined type and direction.
- An entity can be any sort of topic. In the investment context, the entity can be, for example, a company, an industry, an index, a person or a subject. The relationships between the topics can have a direction or directions. For example, a relationship can be unidirectional—e.g. from the first entity to the second entity or from the second entity to the first topic, bi-directional—e.g. from the first entity to the second entity and from the second entity to the first entity, or hierarchical—e.g. a parent entity can include one or more child entities. Where the relationship is bi-directional, the relationship can represent a reciprocal relationship i.e., the creation of one relationship from a first entity to a second entity implies a second relationship from the second entity to the first, thus reducing the time needed to specify a set of relationships among many entities. The relationship can also include a strength indicator to indicate how closely related one entity is to another, for example, how strong of an influence exists between the entities. As non-limiting examples, the relationship between the entities can have a relationship type. For example, a legal relationship (e.g., parent-subsidiary, or licensor-licensee), a business relationship (e.g., customer, supplier, distributor, competitor, or industry member/participant), formal membership requirements (e.g., a company that is part of particular stock market index), informal (e.g., a company that belongs to a standards consortium) or influential (e.g., a political issue impacts the performance of a company). In some instances, the relationships in the network can include both hierarchical and influential relationships.
- The information can be in any format that can be stored and/or identified. Examples include electronic messages, emails, instant messages, financial reports, voicemails, web pages, research reports, electronic documents, press releases, etc. The information can be received using one of more communications avenues, including electronic messaging, electronic mail, instant messaging, voice messaging, scheduled database query, or triggered database query.
- A first user of a first computer can associate information items with entities, and a second user of a second computer can request the information items associated with the association defined by the first user. The second user can request information associated with the selected entity, and in some embodiments, receive information associated with the subset of entities via email, voicemail, screen display, personal data assistant, and print.
- In general, in yet another aspect, the invention relates to systems for providing the tools just described. For example, one such system for presenting information comprises a entity definition module for defining entities, a relationship definition module for defining relationships among the entities and attributing a relationship type and relationship direction to each relationship, a receiver for receiving information, an information management module for associating the received information with at least one of the entities, an information retrieval module for, upon receiving a request for information associated with the one of the entities, retrieving information associated with a subset of the entities, the subset based, at least in part, on the relationship types and relationship directions among the entities in the subset, and a display module for presenting the retrieved data. These modules can be implemented, for example, with computer software in conjunction with computer hardware (e.g., networked computers).
- The system can include a database module for storing one or more of the entities, the relationships, the information, and the association of information with entities. The system may also include a rules engine for governing the relationships between the entities. In some embodiments, the system may further include a messaging module for distributing modifications to one or more of the entities, relationships, and rules. The messaging module can distribute the modifications asynchronously as the changes are made, or in some embodiments, upon demand by the user. The system may also include a permissions module for enforcing user access privileges to one or more of the entities, the relationships, and the information associated with the entities.
- In the drawings, like reference characters generally refer to the same parts throughout the different views. Also, the drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the principles of the invention.
-
FIG. 1 is a block diagram of an embodiment of a system according to the invention. -
FIG. 2 is a block diagram of an embodiment of a server in the system ofFIG. 1 . -
FIG. 3 is a more detailed block diagram of an embodiment of the server ofFIG. 2 . -
FIG. 4 is a block diagram of an embodiment of a client in the system ofFIG. 1 . -
FIG. 5 is a block diagram of an embodiment of a system according to the invention. -
FIG. 5 a is a block diagram of an embodiment of a system according to the invention. -
FIG. 5 b is a flowchart of an embodiment according to the invention. -
FIG. 6 is a screen display of the work area in an embodiment of the client ofFIG. 4 . -
FIG. 7 is a screen display of the join tool in an embodiment of the client ofFIG. 4 . -
FIG. 8 a is a screen display of the entity finder module in an embodiment of the client ofFIG. 4 . -
FIG. 8 b is a screen display of the create new entity module in an embodiment of the client ofFIG. 4 . -
FIG. 8 c is a screen display of the notes module in an embodiment of the client ofFIG. 4 . -
FIG. 9 is a screen display of the entity details module in an embodiment of the client ofFIG. 4 . -
FIG. 10 a is a screen display of the relationship browser module in an embodiment of the client ofFIG. 4 . -
FIG. 10 b a screen display of the add new relationship module in an embodiment of the client ofFIG. 4 . -
FIG. 11 is a flowchart of an embodiment of a method according to the invention. -
FIG. 12 a is a screen display of the drop box module in an embodiment of the client ofFIG. 4 . -
FIG. 12 b is a screen display of the drop box preferences module in an embodiment of the client ofFIG. 4 . -
FIG. 13 is a flowchart of an embodiment of a method according to the invention. -
FIG. 14 is a screen display of the content browser module in an embodiment of the client ofFIG. 4 . -
FIG. 15 a is a screen display of the calendar module in an embodiment of the client ofFIG. 4 . -
FIG. 15 b is a screen display of the research wire module in an embodiment of the client ofFIG. 4 . -
FIG. 16 is a flowchart of an embodiment of a method according to the invention. - Referring to
FIG. 1 , in one embodiment, an information storage andretrieval system 100 includes at least oneserver 104, and at least oneclient retrieval system 100 includes threeclients clients 108. Theclient 108 is preferably implemented as software running on a personal computer (e.g., a PC with an INTEL processor or an APPLE MACINTOSH) capable of running such operating systems as the MICROSOFT WINDOWS family of operating systems from Microsoft Corporation of Redmond, Wash., the MACINTOSH operating system from Apple Computer of Cupertino, Calif., and various varieties of Unix, such as SUN SOLARIS from SUN MICROSYSTEMS, and GNU/Linux from RED HAT, INC. of Durham, N.C. (and others). Theclient 108 could also be implemented on such hardware as a smart or dumb terminal, network computer, personal data assistant, wireless device, information appliance, workstation, minicomputer, mainframe computer, or other computing device that is operated as a general purpose computer or a special purpose hardware device solely used for serving as aclient 108 in the information storage andretrieval system 100. - Generally,
clients 108 are operated by users of the system to receive, review, store and retrieve data regarding investment opportunities. In various embodiments, theclient computer 108 includesclient applications 122,client software 120, or both. One example of aclient application 122 is a web browser application that allows theclient 108 to request a web page (e.g. from the server 104) with a web page request. An example of a web page is a data file that includes computer executable or interpretable information, graphics, sound, text, and/or video, that can be displayed, executed, played, processed, streamed, and/or stored and that can contain links, or pointers, to other web pages. In one embodiment, a user of theclient 108 manually requests a web page from theserver 104. Alternatively, theclient 108 automatically makes requests with the web browser. Examples of commercially available web browser software are INTERNET EXPLORER, offered by Microsoft Corporation of Redmond, Wash., and NETSCAPE NAVIGATOR, offered by AOL/Time Warner of Mountain View, Calif. - In some embodiments, the
client 108 also includesclient software 120. Theclient software 120 provides functionality to theclient 108 that allows a user to request and receive data using the methods described herein. Theclient software 120 may be implemented in various forms. For example, it may be in the form of a Java applet that is downloaded to theclient 108 and runs in conjunction with one ormore client applications 122. The client software may be a standalone application written in C/C++, C#, Java or other appropriate client programming language. Theclient software 120 may be in the form of an application plug-in written in Visual Basic, C/C++, or C# that operates within aclient application 122. Further, theclient software 120 may be in the form of a standalone application, implemented in a multi-platform language such as Java, in a .Net Framework language such as C#, or in native processor executable code. In one embodiment, if executing on theclient 108, theclient software 120 opens a network connection to theserver 104 over thecommunications network 112 and communicates via that connection to theserver 104. Theclient software 120 and the web browser may be part of a single client-server interface 124; for example, the client software can be implemented as a “plug-in” to the web browser. The web browser is but one possible example of a client application, and others may include word processors, spreadsheets, operating system extensions, email clients, as well as others. - A
communications network 112 connects theclient 108 with theserver 104. The communication may take place via any media such as standard telephone lines, LAN or WAN links (e.g., T1, T3, 56 kb, X.25), broadband connections (ISDN, Frame Relay, ATM), wireless links, and so on. Preferably, thenetwork 112 can carry TCP/IP protocol communications, and HTTP/HTTPS requests made by the web browser and the connection between theclient software 120 and theserver 104 can be communicated over such TCP/IP networks. The type of network is not limited, however, and any suitable network may be used. Typical examples of networks that can serve as thecommunications network 112 include a wireless or wired ethernet-based intranet, a local or wide-area network (LAN or WAN), and/or the global communications network known as the Internet, which may accommodate many different communications media and protocols. - An administrator operates a
central server 104, which interacts withclients 108. Theserver 104 is preferably implemented on one or more server class computers that have sufficient memory, data storage, and processing power and that run a server class operating system (e.g. SUN Solaris, GNU/Linux, MICROSOFT WINDOWS 2000, and later versions, or other such operating system). Other types of system hardware and software than that described here could also be used, depending on the capacity of the device and the number of users and the amount of data received. For example, theserver 104 may be part of a server farm or server network, which is a logical group of one or more servers. As another example, there could bemultiple servers 104 that may be associated or connected with each other, or multiple servers could operate independently, but with shared data. As is typical in large-scale systems, application software could be implemented in components, with different components running on different server computers, on the same server, or some combination. - Referring to
FIG. 2 , in one embodiment, aserver 104 includes a clientfile communication module 206 that is the interface for communication withclients 108 involving the transfer of files. In some instances, files may be transferred from theclient 108 to theserver 104, from theserver 104 to theclient 108, or both. Theclient communication module 206 can be implemented as software running on one or more servers, or may be implemented as a stand-alone server. In some embodiments, the clientfile communication module 206 can provide an interface both toclient software 120 and toclient applications 122, so that, for example, a user can access investment performance information through a web browser, a word processing application, or to review other data, and so on, while theclient software 120 can be used for requesting and receiving additional information, or for defining parameters of the system. The interface to each of theclient software 120 and theclient applications 122 can be implemented separately or in combination. In other embodiments, the clientfile communication module 206 can also communicate using other protocols or mechanisms. - In another embodiment, the
server 104 includes a clientmessaging communication module 208 that is the interface for communication withclients 108 involving HTTP/S requests and responses, Java messages, SMTP messages, POP3 messages, instant messages, RSS feeds, as well as other electronic messages. In some instances, messages may be transferred from theclient 108 to theserver 104, from theserver 104 to theclient 108, or both. The clientmessaging communication module 208 can be implemented as software running on one or more servers, or may be implemented as a stand-alone server. In some embodiments, the clientmessaging communication module 208 can provide an interface both toclient software 120 and toclient applications 122, so that, for example, a user can send and receive e-mail, instant messages, and so on, while theclient software 120 can be used for requesting and receiving additional information, or for defining parameters of the system. The interface to each of theclient software 120 and theclient applications 122 can be implemented separately or in combination. In other embodiments, the clientmessaging communication module 208 can also communicate using other protocols or mechanisms. - The client
messaging communication module 208 communicates with theapplication server 212, which provides the main programming logic for the operation of the system. In one embodiment, theapplication server 212 is implemented as one or more application programs running on a server class computer, which may be the same or different computer as the clientfile communication module 206 or the clientmessaging communication module 208. Theapplication server 212 receives requests for data stored in a database (such as an email, the historical performance of an investment vehicle, etc.) from users via the clientmessaging communication module 208, provides updated data to theclient 108, and enforces system, application, and user level rules. - The
server 104 also includes adatabase system 220, which stores data related to the investment opportunities, user permissions, industry data, and the like in one or more databases. For instance, thedatabase server 220 may store information relating to entities defined by the users of the system, relationships among the entities, stored content, user information, server availability, and web traffic information. Thedatabase server 220 may also contain separate databases forrelationships 244,entities 248, contacts of theusers 252, user permissions and security information 256,content metadata 260, and others. Thedatabase server 220 provides data to theapplication server 212. An example of thedatabase server 220 is the MySQL Database Server by MySQL AB of Uppsala, Sweden, the PostgreSQL Database Server by the PostgreSQL Global Development Group of Berkeley, Calif., or the ORACLE Database Server offered by ORACLE Corp. of Redwood Shores, Calif. - The
server 104 also includes afile server 224 and afile storage system 216, which storesstatic data files 232 related to investment opportunities such as web pages, word processing documents, spreadsheets, PDF files, and others. Thefile server 224 receives requests for static data files from theclient 108 via the clientfile communications module 206, transmits the request to thefile storage system 216, and manages the status of the file once it is sent to theclient 108. Thefile storage system 216 also stores application configuration information 236, such as server names, communication protocols, directory structures, and other aspects of the application that may be customized at the application, server, or system level. Thefile server 216 can also storeuser configuration information 240 such as screen preferences, menu options, security and administrative information, and other functional aspects of the application that may be customized from user to user. In one embodiment, thefile storage system 216 stores only data files, while file metadata such as the file location, the author, the creation date, file revision history and other metadata are stored in thecontent metadata DB 260. - Referring to
FIG. 3 , in one embodiment, theclient 108 includes amessage client module 322, aweb services client 326, and filetransfer client module 334. Themessage client module 322 receives messages via the Java messaging service or other similar communications service from theapplication server 212 via the clientmessaging communications module 208. Upon receiving a message from the clientmessaging communications module 208, themessage client 322 facilitates the display of the message on theuser interface 124. The webservices client module 326 facilitates receiving data from theapplication server 212 via a webservices server module 324 such as the Apache Axis Web Services software via HTTP or some similar protocol. Both theweb services module 324 and the clientmessage communication module 208 publish data, for example, in XML format such that data may be automatically received by theweb services client 326 and displayed on theuser interface 124 without user interaction. Thefile transfer client 334 may request and receive files from thefile server 224 using a protocol such as the File Transfer Protocol (FTP), WebDAV or variant thereof via the clientfile communications module 206. Theserver 104 may also include acontention resolution module 219 for managing user permissions and data privacy and contention issues when theapplication server 212 requests or updates data in thedatabase system 220. - In some embodiments, the
server 104 includesconnectivity architecture 229 comprising adapters for receiving, filtering, and formatting data feeds from sources external to the system. In one embodiment, an on-site adapter 312 receives data from on-site services 314, via the Java messaging service or other similar messaging service. A second, off-site adapter 316 can receive data from off-site data providers 318 such as FirstCall available from Thompson Financial and Street Events available from CCBN via a standard File Transfer Protocol (FTP) or other file transfer protocols or RSS feeds. In some embodiments, different adapters may be employed for different data sources. - The
server 104 may also include, in some embodiments, acomponent container module 328 such as the Enterprise Java Beans container for storing application components which may be used by theapplication server 212. - Referring to
FIG. 4 , in one embodiment, theclient 108 includes application plug-inadapters 404 andapplication function modules 406. The application plug-in adapters 404 (“plug-ins”) facilitate the capture of data, files, content, and other information presented to the user in other commercially available or custom developed software applications that reside on theclient 108 or theserver 104. Exemplary applications include, but are not limited to, spreadsheet application plug-ins 426 for software such as Microsoft Excel; postscript data format (PDF) viewer application plug-ins 428 for software such as Adobe Acrobat; word processing application plug-ins 430 for software such as Microsoft Word; instant messenger application plug-ins 432 for software such as AOL's Instant Messenger; web browser application plug-ins 434 for software such as Netscape Navigator or Microsoft Explorer; and email application plug-ins 436 for software such as Microsoft Outlook, Lotus Notes, Qualcomm Eudora; as well as adapters for other client-resident applications from which information may be captured. In some embodiments, the plug-inadapters 404 may facilitate capturing information from applications that reside on the server, 104. - In some embodiments, the plug-
ins 404 are initiated by selections from a menu or buttons on a toolbar within aclient application 122, and in some cases may not require theclient software 120 to be operational or to be invoked. For example, a user may receive an electronic mail message with important information regarding a particular entity. In such cases where the toolbar for the user's electronic mail client application has been updated with the email plug-in 436, the user only needs to highlight the desired message (or portions thereof) and click or select the plug-in button. The email plug-in 436 captures the information, and sends it to thefile system 216 via thefile server 224. Similarly, data being viewed on a World Wide Web content page, as part of a newswire, or from other publicly or privately published documents may be captured and stored in the system using plug-ins adapted for theparticular client application 122 used to receive and view the information. - The
application function modules 406 facilitate the review, creation, and manipulation of various elements of the system such as information items, personal display and security settings, application defaults, etc. For example, some embodiments may include aninterest list module 408 for maintaining one or more lists of topics that may be of particular interest to a user or group of users. Examples of topics that may be included in such a list include companies, financial markets such as the NASDAQ or NYSE, investment vehicles such as bonds or equities, geographic regions such as Japan or the European Union, industries such as computers or automobiles, political issues such as unions or healthcare reform, and the like. - Some embodiments can include an
entity finder module 422 for finding or creating an entity to which information may be attributed. For example, a user may be interested in the computer hardware industry, and create entities for the companies that manufacture and sell computer hardware. In some embodiments, the list of entities is pre-populated with a list of companies based on membership in an industry group such as those companies that are listed on a particular stock exchange. In some embodiments, the list of entries can be created by the users of the system. - Some embodiments can include a
relationship list module 410 for reviewing and defining relationships between entities. For example, if company A supplies raw materials such as steel or computer chips to company B that company B uses to make its products, a relationship may be defined indicating that company A supplies goods or services to company B. Similar relationships may be created for companies that are competitors, partners, subsidiaries, as well as other business and legal relationships. - Some embodiments can include additional application modules such as a
content list module 412 for reviewing information pertaining to one or more entities; aclient administration module 414 for facilitating the customization of theuser interface 124 for individual users; adrop box module 416 which allows users to easily associate a file or partial content from a file with a particular entity; acontact list module 418 for maintaining information about people from whom one or more users of the system receive information; acalendar module 420 for listing dated events pertaining to entities such as earnings announcements or product launches; anotes module 421 for allowing the creation, storage, and sharing of user-created notes; aresearch wire module 424 for reviewing information such as research reports published by financial analysts; and a clientweb services module 425 to facilitate the synchronous request/response of data on the server. In addition, an asynchronous interface composed of a messaging client and a messaging server, for example a Java Messaging Service client/server pair, facilitate the asynchronous update of data residing on theclient 108 as it is updated on theserver 104 and exposed using theweb services module 324 residing on theserver 104. - Referring to
FIG. 5 , in one embodiment, a set ofrules 505 govern the creation of theentities 510, the type ofentities 515 that can be created, the creation of therelationships 520, the types ofrelationships 525 that can be created, and which relationships may be used to link entities of a given type. In one embodiment, therules 505 can describe the entity types 515 that can be created. For example, therules 505 can specify the entity types 515 as “corporate” entities representing companies, “index” entities representing groups of publicly held companies used to calculate a market statistic, “industry” entities representing a specific area of commerce, and “topic” entities representing subjects that may impact other entities. In another embodiment, therules 505 can specify the relationship types 525 that can be created. For example, therules 505 can specify the relationship types 525 as the relationship types listed in Table 1 below. -
TABLE 1 Relationship Types Relationship Type Buys from Competes with Distributes for Distributes through Has subsidiaries Is a subsidiary of Is in index Is in industry Is supplied by Partners with Sells to Has index member Has industry member Influences Relates to - In one embodiment, the
rules 505 govern the relationships that one entity type may have with other entity types. For example, a corporate entity may have different relationships with other corporate entities than it would have with an index entity or a topic entity. Table 2 below contains one possible listing of relationship types and the rules associated with how they can be used to relate different entity types. It should be noted, however, that these exemplary relationships represent one particular set of relationships that may be implemented in a specific embodiment of the invention. Additional relationships used to describe the associations of entities with each other may be obvious to those skilled in the art of analyzing the performance of a company, an industry, or other similar entity. -
TABLE 2 Relationship Rules Allowable Related Entity Type Relationship Type Entities Corporate Buys from Corporate Corporate Competes with Corporate Corporate Distributes for Corporate Corporate Distributes through Corporate Corporate Has subsidiaries Corporate Corporate Is a subsidiary of Corporate Corporate Is in index Index Corporate Is in industry Industry Corporate Is supplied by Corporate Corporate Partners with Corporate Corporate Relates to Topic Corporate Sells to Corporate Index Has index member Corporate Index Relates to Topic Industry Distributes through Industry Industry Has industry member Corporate Industry Is supplied by Industry Industry Relates to Topic Topic Influences Corporate Topic Relates to Topic - For example, if a user created an entity to represent a corporation which is listed on a particular stock exchange and that sells its products to another corporation, the
rules 505 may permit the user to create an “is in index” relationship to an entity of type “index” and a “distributes for” relationship to an entity of type “corporate.” In addition, the user may create an entity for an industry such as “healthcare” and a relationship to another industry such as “insurance.” However, to maintain the integrity of the system, therules 505 may prohibit certain relationships based on the entity and relationship types—e.g. therules 505 may prohibit an “is in index” relationship between an industry entity (healthcare) and an index entity (NYSE) because industries are not listed on stock exchanges. Unlike systems with static lists of entities, a system that allows users to create, modify, and delete entities and the relationships between them, and to have these changes distributed across multiple users in real time provides a greater degree of flexibility to analysts. Such a system can focus on those industries or aspects of investment opportunities that are important to a given organization, maintain knowledge when people leave, and evolve as industries, companies, and investment opportunities grow and change. - In some embodiments, the relationships that connect the entities propagate across multiple entities—that is the same relationship linking a first entity to a second entity also can be the same type of relationship that links the second entity to a third, and so on. By providing such a feature, both direct relationships (entities connected by one or more relationships) as well as indirect relationships (entities separated by one or more intermediate entities, but otherwise reachable through multiple “hops,” thus creating a chain of relationships) can be modeled. Two possible categories of propagating relationships include hierarchical and influential. In some cases, the relationships are reciprocal, i.e. a certain relationship type from entity A to entity B by definition implies a related or “reciprocal” relationship from B to A. For example, a series of propagating hierarchical relationships may be used to describe a large industry, a sub-industry, and a further specialized market within the sub-industry using the “has industry member” relationship and its reciprocal relationship “is in industry” among the hierarchical industry entities.
- As an illustration, the automobile industry may have a “has industry member” relationship to a “truck industry” entity, which in turn may have the same “has industry member relationship with a “light truck industry” entity. Moving back from “light truck industry” the relationships would indicate that the subordinate entity is related to the parent industry by an “is in industry” relationship. In this example, the “light truck industry” has an “is in industry” relationship with the “truck industry.” Similar hierarchies can be represented for indices, for example, where a company's stock is a component of a market index. For example, an analyst that follows a market index such as the NASDAQ index may be interested in information items associated with companies such as Microsoft, Cisco, and others. By creating an “is in index” relationship from a Microsoft entity to a NASDAQ entity, and a reciprocal “has member” relationship from NASDAQ to Microsoft, results of requests for information associated with NASDAQ can also include information associated with Microsoft. Likewise, a particular equity or other investment vehicle can be directly or indirectly related to a mutual fund, hedge fund, or other actively or passively managed investment portfolio. By creating hierarchical relationships that span multiple entities, information items that provide valuable information to an analyst but that are associated with entities that are three or four relationships removed from the focus entity can still be retrieved.
- Similarly, an influential relationship type describes relationships among entities that can influence each other, and is also reciprocal. Where a first entity influences a second entity, and an “influences” relationship connects the two from the first entity to the second, a reciprocal “is influenced by” relationship connects the same two entities in the opposite direction—e.g., from the second entity to the first. For example, a series of influential relationships can be used to connect entities representing political issues, world leaders, legal issues, and geographic regions: in a particular example, an entity representing “Bush Administration” has an influential relationship with an entity representing “Energy Policy” which in turn has an influential relationship with a third entity representing “Middle East Policy.” Like the hierarchical relationships, the reciprocal nature of the influential relationships provides bi-directional relationships among the entities. Using the above example, where the entity “Bush Administration” is related to the entity “Energy Policy” through an “influences” relationship, the reciprocal “is influenced by” relationship can describe the relationship from the “Energy Policy” entity to the “Bush Administration” entity. Furthermore, because some entities have stronger influences on other entities, the relationships may be further annotated with an “influence factor.” For example, an analyst may believe that the Bush Administration is highly influential on a Middle East Policy entity, but in contrast, only slightly influential on a “Tort Reform” entity. The ability to traverse across multiple relationships and include many entities in a set of entities that are potentially influential on a particular entity of interest can result in the retrieval of a larger collection of information items, including those that may not have been associated with the entity of interest, but valuable nonetheless. This large collection provides an analyst an exceptionally broad view of a market, an industry, and world events, which may in turn lead to better decisions regarding investments.
- Referring to
FIG. 5A , in one embodiment, an exemplary entity-relationship network facilitates the identification of a set of entities that are related through one or more relationships. The entity-relationship network includes a set of entities, which can include companies such asGE 550 andHaliburton 552, business topics that may influence the financial or operational performance of the company or market such asasbestos 554 andtort reform 556, political topics such as theBush Administration 560 andforeign policy 558, and industries such as theoil industry 562. Entities can also include individuals such asanalysts 564 that comment on or cover certain companies, industries, or other topics. As an example, a user of the system may be researching a potential investment in Haliburton. By focusing on theHaliburton entity 552, the information items associated with theHaliburton entity 552 will be retrieved from the database and returned to the user. In addition, if so configured, the information items associated with those entities that are direct neighbors of theHaliburton entity 552—e.g. theasbestos entity 554 and the oil industry entity 562 (because theasbestos entity 554 “influences” Haliburton and Haliburton has an “is in industry” relationship to theoil industry entity 562. However, if the user wishes to expand the scope of information being retrieved by the system even further, he can instruct the system to retrieve information items that are associated with entities that are indirectly related to theHaliburton entity 552 through multiple relationships. - As described above, entities that are directly related to the entity of interest include those entities that can be reached by traversing only one relationship in the network. In one exemplary embodiment, the system retrieves information items that are associated with entities that are connected, either directly or indirectly, to the entity of interest through both direct and indirect relationships and that have the same relationship type and direction linking previously identified entities. For example, a first entity may be influenced by a second entity, and thus the system travels across an “influenced by” relationship from the first entity to the second. The second entity may in turn be influenced by a third entity, and the system can travel across a second “influenced by” relationship from the second entity to the third. In this manner, entities that are separated from an entity of interest by more than one relationship can be included in the subset of entities for which information items are retrieved. The number of relationships needed to get from the entity of interest to another entity sometimes referred to as the “degree of separation” or “levels of indirection,” (one for direct relationships, more than one for indirect relationships), can vary, and in some cases may be limited by the user.
- In the example shown, the system identifies the relationship between the
Haliburton entity 552 and theasbestos entity 554. In this example, the relationship is a direct “is influenced by” relationship, and therefore the system determines if theasbestos entity 554 “is influenced by” any other entities not yet identified. Referring toFIG. 5 a, an “is influenced by” relationship connects theTort Reform entity 556 to theasbestos entity 554, and further connects theBush Administration entity 560 to thetort reform entity 556. Similarly, an “is influenced by” relationship connects theForeign policy entity 558 to theoil industry entity 562. As a result, expanding the search for information items that may be related, but not necessarily directly associated with, theHaliburton entity 552, increases the set of entities of interest from three (Haliburton 552,asbestos 554, and oil industry 562) to six (Haliburton 552,asbestos 554, andoil industry 562, plustort reform 556,Bush Administration 560, and foreign policy 558). By following the relationships having the same type and direction, influences on entities of interest can be traced through numerous intervening entities to the “root cause” entity, and information items associated with that entity can be reviewed for information that may be pertinent to investment decisions regarding the entity of interest. - More generally,
FIG. 5 b illustrates one example of a method for determining the entities to include in the subset of entities for which information items are to be retrieved. Initially, a focus identity is selected (STEP 570). The focus entity generally indicates the company, index, topic, or other subject area of interest being researched. To build the initial network of entities and relationships, relationships that indicate another entity may influence the focus entity or that indicate the focus entity is a member of a larger group are followed to the neighboring entities (STEP 572). Each neighboring entity is then treated as a focus entity, and any relationships that are of the same type (i.e., propagating hierarchical or influential relationships) are followed to the next set of neighboring entities (STEP 576). The system determines if there are any remaining relationships that have not be followed (DECISION STEP 578) and if so, repeatsSTEP 576 until there are no additional entities that can be reached. The set of entities is then defined as the subset of entities (STEP 580) for which information items will be returned. - In some cases, numerous relationships may be used to govern travel from the focus entity to another entity, and, as described above, certain relationships may be “stronger” i.e., the impact that one entity has on another may be much greater than others. For example, only relationships of a certain strength might be followed. In other cases, where an entity represents a company with diverse businesses and product offerings, a stronger “is in industry” relationship may be desired when describing the company's relationship to a core business, as opposed to a business that they are only tangentially related to. In addition, the user may indicate that the traversal process terminate after some number of iterations, or that entities that require the traversal of some number of relationships (e.g., more than four) are not included. In other cases, an analyst may allow the system to traverse the entire network, but only follow those relationships that have a high strength indicator. In some cases, a combination of degree or separation and relationship strength may be used to determine the subset of entities. As one such non-limiting example, a user may indicate that the set of identified entities includes all entities that are separated from the focus entity by three or fewer intermediate entities regardless of relationship strength, and subsequently follow only strong relationships to entities that are four or more degrees of separation from the focus entity. In some instances, users may instruct the system to only follow a subset of the relationships emanating from the focus entity. For example, where one entity has a large number of immediate direct relationships, following every relationship may result in an unmanageable result set. By allowing the user to limit the paths that are followed to some subset of paths (i.e., one or two paths, for example, up to the total number of direct relationships) the set or retrieved information items can be kept to a manageable number. These features provide the user with added flexibility with regard to the volume of information received, and the perceived relevance of the derivative information as it becomes more distant from the focus entity.
- Referring to
FIG. 6 , in one exemplary embodiment, the system provides awork area 600 on theclient 108. Thework area 600 can include one or more of theapplication function modules 406 described above. For example, thework area 600 can include atoolbar 610 allowing users to access functions of the system through a system of menus. The work area can also include theentity finder module 422, theresearch wire module 424, and thecalendar module 420. In some embodiments, the application function modules can be positioned on theuser interface 124 at different locations as determined by the user. For example, the entity finder module 620 can be positioned along the left side of the screen, with the research wire module 630 and calendar module 530 to the right of the entity finder module 620. In some embodiments, the positions of each module, both relative to theuser interface 124 and to each other may be saved to the userconfiguration file system 240 using theclient administration module 412 such that each time an individual user access the system, the layout of thework area 600 is consistent. In some embodiments, the configurations of thework area 600 may be saved at the application level, group level, or on an individual user basis. By allowing users to customize and maintain apersonal work area 600, the system facilitates the varied usage styles of different people—i.e. some analysts may prefer to see all of the information arranged on theclient 108, while other analysts may prefer to see only selected items such as thecalendar module 420. - Referring to
FIG. 7 , in one embodiment, ajoin tool 700 may be used to groupapplication function modules 406 together such that when a user selects data to be presented in one module the data presented in the joinedapplication function modules 406 is updated. In one embodiment, thejoin tool 700 can provide instructions to the user on how to joinapplication function modules 406. For example, if theentity finder module 422 and theresearch wire module 424 were grouped using thejoin tool 700, and the user changed the selected entity in theentity finder module 422 from General Electric to IBM, the data presented in theresearch wire module 424 would be updated with data pertaining to IBM. - The
join tool 700 may also provide multiple join groups. For example, a user may select certainapplication function modules 406 to be part of a group and select from a drop downbox 730 the color to be associated with the group and displayed along the band at the top of theapplication function modules 406 in each group. By identifying each group using thecolors 720, a user may easily identify those modules grouped together while looking at thework area 600, which may contain numerousapplication function modules 406, some of which may be grouped and others which may not. This provides the user with awork area 600 that is synchronized acrossapplication function modules 406, to the extent desired. Thejoin tool 700 also provides a listing of previously defined groups, and the colors associated with eachgroup 720. - Referring to
FIGS. 8 a and 8 b, in one embodiment, theentity finder module 422 includes adisplay window 810, anentity list 820, and a definenew entity button 830 which is used to create new entities using the createnew entity screen 840. Thedisplay window 810 provides the user with the name of the current entity about which information is being displayed in otherapplication function modules 406 that are grouped with theentity finder module 422. Theentity list 820 provides a listing of the entities about which information may be retrieved from the system. In some embodiments, theentity list 820 may be created by a central administrator, while in other embodiments the entity list may be created by individual users of the system. In some embodiments, the entities listed in theentity list 820 may be restricted on a global level, group level, or an individual level. For example, if an individual analyst is responsible for the automobile industry, theentity list 820 may be limited to automobile manufacturers, their suppliers, and other topics related to the automobile industry such as oil futures, labor unions, and interest rates. - Referring to
FIG. 8 b, the createnew entity screen 840 includes an entitytype data window 850, an entityname data window 860, a entity shortname data window 870, and an entityalias data window 875. In some embodiments, the values available to a user in the entitytype data window 850 may be limited to values defined by a central administrator and stored in thedatabase 220, and in other embodiments the values may be user defined and stored in the user configuration files 240. For example, to facilitate certain reporting or other functions, the list of entity types may be limited to corporations, indices (such as NASDQ or NIKKEI), industries (such as automotive or computer hardware), and topics (such as asbestos, war, or the environment). In one embodiment, the topic entities may be either public or private. Public entities may be used throughout the application by multiple users of the system, while private topics may be limited to one individual user or a particular group of users. - In one embodiment, the entities may be predefined, with periodic updates available from vendors specializing in how entities are related and influence each other. For example, a vendor can supply a pre-populated database or flat file containing lists of corporate entities listed on the NYSE and NASDQ, their parent and subsidiaries, and general industries. The same vendor, or in one embodiment another vendor, may also supply the relationships among the entities. This data can be imported into the system. In other embodiments, the data files can be appended or overwritten with files updated based on the passage of time, and such events as large mergers, delistings, bankruptcies, or initial public offerings.
- Referring to
FIG. 8 c, in one embodiment, the create note details screen 880 includes a source field 855, asentiment field 890, and anote text field 895. The note detailsscreen 880 allows a user to create free form text notes about a topic. Thesource field 885 identifies the source of the note, thus allowing users to see who created thenote 895. By providing this information, the system allows users to filter notes based on the source of thenote 895, or give greater weight to a note based on its author. Thesentiment field 890 allows the author of thenote 895 to provide an indication of whether thenote 895 reflects positively or negatively on a topic or entity. For example, a first user may only want to see positive notes from a second user, but wish to see all notes from a third user. This feature allows users to customize and filter the information they receive when inquiring about an entity of interest. - Referring to
FIG. 9 , in one embodiment, an edit entity details screen 900 includes one or more data fields in which detailed data may be entered describing an entity. For example, if an entity being described is a corporation, anaddress data field 910 may be used to enter the physical location of the corporation. Similarly, phone and fax data fields 920 may be used to capture the corporation's telephone number and facsimile number, respectively. Other data fields that may be included on the entity details screen 900 for a corporate entity include an employeecount data field 930, anemail data field 940 for storing the email addresses of one or more contacts at the corporation, a data table 950 of URL addresses representing web pages on the World Wide Web that may be relevant to the corporation, and a data table 960 containing the names and other descriptive information regarding the officers of the corporation, such as their titles, ages, educational backgrounds, previous employers, as well as other data. By allowing analysts to provide detailed information in theentity detail screen 900, the system facilitates the maintenance of significant amounts of very detailed data about entities and people. These contacts often can supply information that is the basis for investment decisions. - Referring to
FIGS. 10 a and 10 b, in one embodiment, therelationship browser module 410 displays acurrent entity 1005,other entities 1015 to which thecurrent entity 1005 has been related, the currently selectedrelated entity 1010, the type ofrelationships 1020, and provides the ability to create new relationships using the add arelationship option 1025. For example, thecurrent entity 1005 may be a large retail chain. The relationship types 1020 that may be relevant to such an entity may be the “competes with,” distributes for,” and “relates to” relationships. More particularly, if a user is interested in a retail chain that sells toys, the entities listed under the “competes with” relationship type may include other large retailers that also sell toys. Furthermore, the entities listed under the “distributes for” relationship type may include toy manufacturers, and the entities listed under the “relates to” relationship type may include topics such as “dock strike” if the user determines such an event could potentially affect the financial performance of thecurrent entity 1005. - The relationship browser may contain iconic representations for each entity called entity icons. Each entity icon may include a graphical representation of the entity's type, an activity number value representing the number of system notifications generated for that entity during some previous period of time (24 hours, 1 week, 1 month, etc.), as well as other information. In some embodiments, the activity number can be calculated dynamically, and the formula employed to determine the activity number can be based on any system event for an entity and/or its related entities.
- New relationships may be created using the add a
relationship function 1025 and the add arelationship screen 1030, which includes data fields for selecting therelationship type 1020 and therelated entity 1015, and acheck box 1035 for creating reciprocal relationships. In some embodiments, the relationship types are limited to a fixed set of relationships defined by a central administrator and stored in thedatabase 220, as described above. In some embodiments, the relationship types, the entity types, the direction and reciprocal nature of the relationships, and the rules governing the application of the relationships to the entities may be defined by individual users. In some embodiments, the users have complete control over the creation of these objects, and how they are instantiated within the entity-relationship network, and in some cases an administrator retains some control over the rules governing the creation and use of the objects. In some embodiments, the user-created objects can be shared with other users of the application, other members of particular groups of users, or kept private. -
FIG. 11 illustrates one embodiment of a method for defining entities and the relationships among the entities. Initially, a user, administrator, or other supplier of data builds an initial set of rules, entities, and relationship types (STEP 1103). A user may then determine if additional entities are necessary to adequately model the markets, industries, or topics of interest (STEP 1105). The user then determines if the entities exist in the initial set (DECISION STEP 1110), for example, by using theentity finder module 422 described above. If one or more of the entities does not exist, the user then creates the entities (STEP 1115) using the create new entity screen 740. Once the entities are created, the user then determines which entities are to be related (STEP 1120). The user then determines the relationship type (STEP 1125) that best describes the relationship, and creates the relationship (STEP 1130) using therelationship browser module 410. - Because users of the system are able to define entities and provide descriptive information about the entities, the data can be customized to the areas of interest of a particular firm, group, or individual. For example, if an analyst firm follows a particular investment strategy that runs contrary to widely-held principles, or has uncovered derivative influences on a company or industry that other analysts have not, the ability to create and modify the entities is valuable. In one exemplary case, an analyst or firm may have determined that certain weather patterns (exceptionally warm winters, for example) have a statistically significant impact on automobile sales during certain months. By creating a topic entity called “weather” and an “influences” relationship to an industry entity titled “automotive”, an analyst reviewing automobile manufacturers as investment opportunities would have the benefit of knowing that reports of the current weather pattern will appear along with other data that may influence the performance of companies in the auto industry.
- In some embodiments, the relationship may be a unidirectional relationship—e.g. a company entity may have a “member of” relationship to an index entity. In some embodiments, the user may determine that upon creating the first relationship, a second, reciprocal relationship is warranted, thus creating a bi-directional relationship. For example, if a user instructs the system to create a “sells to” relationship from company A to company B, and further instructs the system to create a reciprocal relationship, the system can automatically create a “buys from” relationship from company B to company A. In some embodiments, the creation of the reciprocal relationships can be governed by the
rules 505. In such a case, when a user creates a relationship from a first topic to a second topic, only the valid reciprocal relationships are provided. Using the example above, therules 505 may limit the valid reciprocal relationships to “buys from.” By providing this option, the system provides a quick method for creating sets of relationships based on reciprocal associations between entities. - Referring to
FIG. 12 , in one embodiment, thedrop box module 1205 facilitates the saving of an information item to thefile system 216 ordatabase 220 without having to use theclient applications software 122. Thedrop box module 1205 remains active on theclient 108 and visible on theuser interface 124, and allows a user to deposit a document, spreadsheet, or other file directly from one location on theclient 108 or other computer connected to theclient 108 over thenetwork 112 to thefile system 216 by “dragging and dropping” the file onto thedrop box module 1205. In some embodiments, default values for characteristics of the information items may be set using the dropbox preferences module 1210. - For example, the user may be reviewing numerous information items about a particular entity, and set the drop
box default fields 1215 to reflect the current entity, the type of data being reviewed, and the author of the information items, thus allowing the user to associate numerous items with a particular entity quickly. -
FIG. 13 illustrates one embodiment of a method for associating information with an entity. Initially, a user receives information relating to one or more of the entities of interest to the user (STEP 1305) and in some cases creates notes relating to an entity of interest (STEP 1307). For information received from another source, the user then captures the information (STEP 1310) using one or more of the methods described above. The user then determines the proper entity to which the information should be associated (STEP 1315). The user then determines if the entity to which the information should be associated exists (STEP 1320), and if the entity does not exist, creates the new entity (STEP 1325) using the methods described above. The user may then assign the information to the entity (STEP 1330), for example, using one of the application plug-inadapters 404 or thedrop box module 1205 above. Because the applications into which theadapters 404 plug-in are already in use and the analysts are familiar with their operation, minimal additional training is necessary for an analyst to start using the system. - For example, a user may receive an email with a document attached to the mail message describing a company's product launch strategy for an upcoming software release. By selecting the attached document, the
client 108 may recognize theclient application 122 needed to view the document, and launch theapplication 122, if not already running. The user then determines the entity with which the document should be associated, and highlights the relevant portion(s) of the document. The user then selects the plug-in 430 in theclient application 122, and the information is saved to thefile system 216, with the associations provided by the user. - Referring to
FIG. 14 , in one embodiment, thecontent browser module 412 facilitates requests for and review of information associated with acurrent entity 1005 and in some embodiments, entities related to a current entity. Thecontent browser module 412 includes the current entity ofinterest 1005, a selectentity data field 1405, a displayrelated information toggle 1410, summaries of eachinformation item 1415 retrieved from thedatabase system 220 orfile system 216, and anindication 1420 of who authored theinformation items 1415, as well as other descriptive information about the item. - The select
entity data field 1405 allows a user to change thecurrent entity 1005 to a new current entity, and thus reviewinformation items 1415 associated with a new current entity. The display relatedinformation check box 1410 allows the user to indicate whether the list ofinformation items 1415 will include information items for thecurrent entity 1005 only (unselected), or for thecurrent entity 1005 and the entities related to it (selected). For example, if a user was interested in reviewing the information associated with a computer manufacturer, the user could select the entity name for that corporation from the selectentity data field 1405, and the summaries of eachinformation item 1415 associated with that entity would be listed. In addition, a user may be interested in the derivative influences potentially affecting the computer manufacturer, e.g. the companies that supply the chip sets, the stock exchange on which it is listed, etc. In such a case, the user selects the display relatedinformation check box 1410 and therefore receives information associated with the other corporations, industries, and topics that are related to the computer manufacturer. This allows the user to gain a broader perspective of the factors that may influence the company, and therefore affect its financial performance. - In some embodiments, the summaries of each
information item 1415 may include information about the information items. For example, the summaries may include a title, the type of file (voice clip, financial report, press release, as well as others), the author's name, the date on which the file was last modified, the size of the file, the format of the file (such as Word for Windows, Excel, PDF, HTML, as well as others), and comments about the file. In some embodiments this information is static and cannot be changed by individual users, where as in other embodiments, the ability to modify the summary information can be assigned to individual users or groups of users. - Referring to
FIGS. 15 a and 15 b, in one embodiment, thecalendar module 420 andresearch wire module 424 further facilitate the review of information associated with acurrent entity 1005 and in some embodiments, entities related to a current entity. In both modules, the current entitydata selection window 1405 and display relatedinformation check box 1410 perform similar functions as on thecontent browser module 412 described above. Thecalendar module 420 further includesdate navigation buttons 1505, anunfiltered selection box 1510, anaction menu 1515, and summaries ofinformation items 1520 organized by date. In one embodiment, thedate navigation buttons 1505 allow a user to scroll to a previous week or subsequent week, and review the events scheduled during that time period. In other embodiments, the time periods may be hours, days, months, quarters, years, or other periods of time into which events can be grouped. In another embodiment, theunfiltered selection box 1510 allows a user to instruct thecalendar module 420 to display all events for all companies (unchecked) or only those events related to the company or entity selected in the entity data selection window 1405 (checked). - The
research wire module 424 further includessummaries 1525 of information items received from either internal or external news and broadcast sources via theadapters summaries 1525 include the date and time an information item was published, the company about which the item pertains, and a text summary of the item. By clicking on thesummary 1525 of an information item, the user may then review the entire contents of the item. -
FIG. 16 illustrates one embodiment of a method for retrieving information associated with one or more entities. The user begins by selecting an entity of interest (STEP 1605) using the selectentity data field 1405 on thecontent browser module 412. Theclient software 120 then requests (STEP 1610) the information associated with the selected entity from theserver 104, which retrieves the requested information (STEP 1615). The server then determines (DECISION STEP 1620) if the display relatedinformation check box 1410 is selected. If the display relatedinformation check box 1410 is selected, theserver 104 also retrieves the data (STEP 1625) associated with the entities related to the selected entity. Once the complete set of information is retrieved from thefile system 216 anddatabase system 220, it is received (STEP 1630) by theclient 108 and presented to the user for review. Because the relationships were previously established and the information was associated with the first entity, the analyst needs no additional knowledge about the industry or entity to receive the derivative information. In some embodiments where updates to entities, relationships, rules, or information is asynchronously provided to theclient 108, the user receives updated information (STEP 1635) using one or more of the methods described above. - For example, an analyst may be following the semiconductor industry in general, and have a particular interest in the XYZ Semiconductor Company (“XYZ Co.”). Prior to the analyst's inquiry for information about XYZ Co., another analyst created a “supplier/customer” relationship between XYZ Co. and ABC Computer Company and a “relates to” relationship between XYZ Co. and a topic identified as “Trade with China.” Using the
content browser module 412, the analyst then selects XYZ Co. from the selectentity data field 1405. Furthermore, the analyst may be interested in information directly associated with XYZ Co., and also information associated with related entities. To receive this information, the analyst checks the display relatedinformation check box 1410. Theserver 104 then retrieves the information associated with XYZ Co., ABC Computer Co, as well as any information associated with the topic “Trade with China.” This facilitates a more complete analysis of XYZ Co.'s current and future performance because an increase in demand for computers manufactured by ABC Co. may directly influence the demand for semiconductors manufactured by XYZ. Co. Likewise, political and economic events that may affect the importation of goods from China may also affect XYZ Co. if their manufacturing operations are located there. - Variations, modifications, and other implementations of what is described herein will occur to those of ordinary skill in the art without departing from the spirit and the scope of the invention as claimed. Accordingly, the invention is to be defined not by the preceding illustrative description but instead by the spirit and scope of the following claims.
Claims (17)
1.-28. (canceled)
29. A method of providing information items, the method comprising:
receiving, at a first computer, a plurality of information items;
facilitating the association of information with at least one entity, the information comprising a portion of a document rendered within the application and selected by a user;
storing the selected information and the association between the selected information and the at least on entity for subsequent retrieval;
receiving, at a second computer, a request for information associated with the at least one entity;
retrieving the selected information associated with the entity; and
displaying the retrieved data.
30. The method of claim 29 further comprising:
defining the at least one entity; and
defining one or more relationships between the at least one entity and other entities wherein each relationship comprises a relationship type and a relationship direction, thus facilitating the creation of an entity-relationship network comprising the at least one entity, the other entities, and the relationships therebetween.
31. The method of claim 30 wherein the entity comprises one of a company, an industry, an index, a person and a subject.
32. The method of claim 30 wherein the relationship direction is one of unidirectional and bi-directional.
33. The method of claim 32 wherein the relationship direction is bi-directional and the relationship type represents a set of reciprocal relationships between the entities.
34. The method of claim 29 wherein the information items comprise at least one of an electronic message, an email, an instant message, a financial report, a voicemail, a web page, a research report, an electronic document, and a press release.
35. The method of claim 29 wherein the information items are received via one or more of an electronic message, electronic mail, instant message, voice message, scheduled database query, or triggered database query.
36. A system for presenting information, comprising:
a collection of application plug-in adapters implemented as software stored on a client computer, each adapter comprising:
a receiver for receiving information from an application, the information comprising a portion of a document rendered within the application and selected by a user; and
an information management module for associating the selected information with at least one entity; and
a central server in communication with each of the application plug-in adapters and configured to receive therefrom the selected information, and further comprising;
a data storage server for storing the selected information and the association between the selected information and the at least on entity; and
an application server implemented as application software stored on the central server and configured to:
(i) receive a request for information associated with the at least one entity;
(ii) retrieve from the data storage server the selected information associated with the entity; and
(iii) display the retrieved data.
37. The system of claim 36 wherein the application plug-in adapters further comprises:
an entity definition module for defining the at least one entity; and
a relationship definition module for defining one or more relationships between the at least one entity and other entities wherein each relationship comprises a relationship type and a relationship direction, thus facilitating the creation of an entity-relationship network comprising the at least one entity, the other entities, and the relationships therebetween.
38. The system of claim 36 wherein the receiver receives one or more of an electronic message, an email, an instant message; a streaming data feed, a voice message, and a web page.
39. The system of claim 37 further comprising a rules engine for governing the permissible relationship types among the entities.
40. The system of claim 37 wherein the relationships between entities are one or more of unidirectional and bi-directional.
41. The system of claim 37 wherein the central server further comprises a messaging module for distributing modifications made to one of the entities, the relationships, and the rules to users of the system.
42. The system of claim 41 wherein the messaging module distributes the modifications asynchronously.
43. The system of claim 54 wherein the messaging module distributes the modifications on demand.
44. The system of claim 37 wherein the central server further comprises a permissions module for enforcing user access privileges to one or more of the entities, the relationships, and the information items associated with the entities.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/622,184 US20100121877A1 (en) | 2003-11-13 | 2009-11-19 | Systems and Methods for Retrieving Data |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/712,076 US20050108024A1 (en) | 2003-11-13 | 2003-11-13 | Systems and methods for retrieving data |
US10/987,375 US7644088B2 (en) | 2003-11-13 | 2004-11-12 | Systems and methods for retrieving data |
US12/622,184 US20100121877A1 (en) | 2003-11-13 | 2009-11-19 | Systems and Methods for Retrieving Data |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/987,375 Continuation US7644088B2 (en) | 2003-11-13 | 2004-11-12 | Systems and methods for retrieving data |
Publications (1)
Publication Number | Publication Date |
---|---|
US20100121877A1 true US20100121877A1 (en) | 2010-05-13 |
Family
ID=34573472
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/712,076 Abandoned US20050108024A1 (en) | 2003-11-13 | 2003-11-13 | Systems and methods for retrieving data |
US10/987,375 Active 2025-09-09 US7644088B2 (en) | 2003-11-13 | 2004-11-12 | Systems and methods for retrieving data |
US12/622,184 Abandoned US20100121877A1 (en) | 2003-11-13 | 2009-11-19 | Systems and Methods for Retrieving Data |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/712,076 Abandoned US20050108024A1 (en) | 2003-11-13 | 2003-11-13 | Systems and methods for retrieving data |
US10/987,375 Active 2025-09-09 US7644088B2 (en) | 2003-11-13 | 2004-11-12 | Systems and methods for retrieving data |
Country Status (5)
Country | Link |
---|---|
US (3) | US20050108024A1 (en) |
EP (1) | EP1687744A1 (en) |
CA (1) | CA2545446A1 (en) |
GB (1) | GB2424296A (en) |
WO (1) | WO2005050491A1 (en) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040006506A1 (en) * | 2002-05-31 | 2004-01-08 | Khanh Hoang | System and method for integrating, managing and coordinating customer activities |
US20060253475A1 (en) * | 2005-05-09 | 2006-11-09 | Cognos Incorporated | System and method for time dimension management for a data analyzing system |
US20070214179A1 (en) * | 2006-03-10 | 2007-09-13 | Khanh Hoang | Searching, filtering, creating, displaying, and managing entity relationships across multiple data hierarchies through a user interface |
US20090024589A1 (en) * | 2007-07-20 | 2009-01-22 | Manish Sood | Methods and systems for accessing data |
US20090182780A1 (en) * | 2005-06-27 | 2009-07-16 | Stanley Wong | Method and apparatus for data integration and management |
US20090327347A1 (en) * | 2006-01-03 | 2009-12-31 | Khanh Hoang | Relationship data management |
US8583687B1 (en) * | 2012-05-15 | 2013-11-12 | Algebraix Data Corporation | Systems and methods for indirect algebraic partitioning |
AU2010246536B2 (en) * | 2010-11-30 | 2014-01-23 | Finsuite Pty Ltd | Schematic Corporate Device and System |
US8832107B2 (en) * | 2012-03-21 | 2014-09-09 | Sap Ag | Collection and categorization of configuration data |
US20150046493A1 (en) * | 2013-08-07 | 2015-02-12 | Microsoft Corporation | Access and management of entity-augmented content |
US10255253B2 (en) | 2013-08-07 | 2019-04-09 | Microsoft Technology Licensing, Llc | Augmenting and presenting captured data |
US10339183B2 (en) | 2015-06-22 | 2019-07-02 | Microsoft Technology Licensing, Llc | Document storage for reuse of content within documents |
US10757142B2 (en) * | 2017-09-01 | 2020-08-25 | Financial Crime Intelligence Ltd | Assimilated economic crime intelligence system and method |
US20220100782A1 (en) * | 2018-10-23 | 2022-03-31 | Yext, Inc. | Knowledge search system |
Families Citing this family (229)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7000230B1 (en) | 2000-06-21 | 2006-02-14 | Microsoft Corporation | Network-based software extensions |
US10535049B2 (en) * | 2003-03-21 | 2020-01-14 | Paypal, Inc. | Payment transactions via substantially instant communication system |
US7805366B2 (en) * | 2003-03-21 | 2010-09-28 | Ebay Inc. | Method and system to facilitate payments to satisfy payment obligations resulting from purchase transactions |
US7415672B1 (en) | 2003-03-24 | 2008-08-19 | Microsoft Corporation | System and method for designing electronic forms |
US7370066B1 (en) | 2003-03-24 | 2008-05-06 | Microsoft Corporation | System and method for offline editing of data files |
US7913159B2 (en) | 2003-03-28 | 2011-03-22 | Microsoft Corporation | System and method for real-time validation of structured data files |
US7406660B1 (en) | 2003-08-01 | 2008-07-29 | Microsoft Corporation | Mapping between structured data and a visual surface |
US7334187B1 (en) | 2003-08-06 | 2008-02-19 | Microsoft Corporation | Electronic form aggregation |
US8225282B1 (en) | 2003-11-25 | 2012-07-17 | Nextaxiom Technology, Inc. | Semantic-based, service-oriented system and method of developing, programming and managing software modules and software solutions |
US7376912B2 (en) * | 2004-03-25 | 2008-05-20 | Morgan Stanley | Interactive user interface for displaying supply chain information |
US8972856B2 (en) | 2004-07-29 | 2015-03-03 | Yahoo! Inc. | Document modification by a client-side application |
US7962465B2 (en) | 2006-10-19 | 2011-06-14 | Yahoo! Inc. | Contextual syndication platform |
US20060168054A1 (en) * | 2004-12-13 | 2006-07-27 | Ebay Inc. | Messaging method and apparatus |
US20060271939A1 (en) * | 2005-05-11 | 2006-11-30 | Eric Joris | Enterprise-to-enterprise integration |
US20070174167A1 (en) * | 2005-05-20 | 2007-07-26 | Stefano Natella | Derivative relationship news event reporting |
US20060277087A1 (en) * | 2005-06-06 | 2006-12-07 | Error Brett M | User interface for web analytics tools and method for automatic generation of calendar notes, targets,and alerts |
US9104773B2 (en) * | 2005-06-21 | 2015-08-11 | Microsoft Technology Licensing, Llc | Finding and consuming web subscriptions in a web browser |
US8661459B2 (en) * | 2005-06-21 | 2014-02-25 | Microsoft Corporation | Content syndication platform |
US20070011665A1 (en) * | 2005-06-21 | 2007-01-11 | Microsoft Corporation | Content syndication platform |
US7590940B2 (en) | 2005-10-11 | 2009-09-15 | Morgan Stanley | Interactive user interface for displaying correlation |
US8001459B2 (en) | 2005-12-05 | 2011-08-16 | Microsoft Corporation | Enabling electronic documents for limited-capability computing devices |
US20070220585A1 (en) * | 2006-03-01 | 2007-09-20 | Farrugia Augustin J | Digital rights management system with diversified content protection process |
US8280843B2 (en) | 2006-03-03 | 2012-10-02 | Microsoft Corporation | RSS data-processing object |
US7979803B2 (en) * | 2006-03-06 | 2011-07-12 | Microsoft Corporation | RSS hostable control |
US20070226013A1 (en) * | 2006-03-07 | 2007-09-27 | Cardiac Pacemakers, Inc. | Method and apparatus for automated generation and transmission of data in a standardized machine-readable format |
US20100257160A1 (en) * | 2006-06-07 | 2010-10-07 | Yu Cao | Methods & apparatus for searching with awareness of different types of information |
WO2007143223A2 (en) * | 2006-06-09 | 2007-12-13 | Tamale Software, Inc. | System and method for entity based information categorization |
US8051128B2 (en) * | 2006-11-01 | 2011-11-01 | International Business Machines Corporation | Using feed usage data in an access controlled team project site environment |
US8213583B2 (en) * | 2006-11-22 | 2012-07-03 | Verizon Patent And Licensing Inc. | Secure access to restricted resource |
EP2108156A4 (en) * | 2006-12-22 | 2013-11-13 | Intel Corp | Enterprise knowledge management and sharing method and apparatus |
CA2717462C (en) * | 2007-03-14 | 2016-09-27 | Evri Inc. | Query templates and labeled search tip system, methods, and techniques |
US7664779B1 (en) * | 2007-06-29 | 2010-02-16 | Emc Corporation | Processing of a generalized directed object graph for storage in a relational database |
US7991910B2 (en) | 2008-11-17 | 2011-08-02 | Amazon Technologies, Inc. | Updating routing information based on client location |
US8028090B2 (en) | 2008-11-17 | 2011-09-27 | Amazon Technologies, Inc. | Request routing utilizing client location information |
CN101345718A (en) * | 2007-07-13 | 2009-01-14 | 阿里巴巴集团控股有限公司 | Method, system and apparatus for supporting topic classification in group |
US8594996B2 (en) | 2007-10-17 | 2013-11-26 | Evri Inc. | NLP-based entity recognition and disambiguation |
WO2009052308A1 (en) | 2007-10-17 | 2009-04-23 | Roseman Neil S | Nlp-based content recommender |
US8655876B2 (en) * | 2007-11-30 | 2014-02-18 | Red Hat, Inc. | Methods and systems for classifying data based on entities related to the data |
US20090150795A1 (en) * | 2007-12-11 | 2009-06-11 | Microsoft Corporation | Object model and user interface for reusable map web part |
US20090216588A1 (en) * | 2008-02-25 | 2009-08-27 | Brian Coyne | Return on investment analyzer |
US9268841B2 (en) | 2008-02-29 | 2016-02-23 | Red Hat, Inc. | Searching data based on entities related to the data |
US9418087B2 (en) * | 2008-02-29 | 2016-08-16 | Red Hat, Inc. | Migrating information data into an application |
US9430538B2 (en) * | 2008-02-29 | 2016-08-30 | Red Hat, Inc. | Providing additional information and data in cooperation with a communication application |
US8156243B2 (en) | 2008-03-31 | 2012-04-10 | Amazon Technologies, Inc. | Request routing |
US8533293B1 (en) | 2008-03-31 | 2013-09-10 | Amazon Technologies, Inc. | Client side cache management |
US7970820B1 (en) | 2008-03-31 | 2011-06-28 | Amazon Technologies, Inc. | Locality based content distribution |
US8606996B2 (en) | 2008-03-31 | 2013-12-10 | Amazon Technologies, Inc. | Cache optimization |
US8321568B2 (en) | 2008-03-31 | 2012-11-27 | Amazon Technologies, Inc. | Content management |
US8447831B1 (en) | 2008-03-31 | 2013-05-21 | Amazon Technologies, Inc. | Incentive driven content delivery |
US7962597B2 (en) | 2008-03-31 | 2011-06-14 | Amazon Technologies, Inc. | Request routing based on class |
US8601090B1 (en) | 2008-03-31 | 2013-12-03 | Amazon Technologies, Inc. | Network resource identification |
US20090248433A1 (en) * | 2008-04-01 | 2009-10-01 | Earley Jr J Michael | Method for automatically linking a data element to existing research |
KR100930617B1 (en) * | 2008-04-08 | 2009-12-09 | 한국과학기술정보연구원 | Multiple object-oriented integrated search system and method |
US20090276222A1 (en) * | 2008-05-01 | 2009-11-05 | Cybertech Information International, Inc. | Method and system for incorporating one or more inputs and defining and applying a plurality of rules for the different stages of speech and video analytics systems |
US9912740B2 (en) | 2008-06-30 | 2018-03-06 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US9407681B1 (en) | 2010-09-28 | 2016-08-02 | Amazon Technologies, Inc. | Latency measurement in resource requests |
US7925782B2 (en) | 2008-06-30 | 2011-04-12 | Amazon Technologies, Inc. | Request routing using network computing components |
US8521880B1 (en) | 2008-11-17 | 2013-08-27 | Amazon Technologies, Inc. | Managing content delivery network service providers |
US8732309B1 (en) | 2008-11-17 | 2014-05-20 | Amazon Technologies, Inc. | Request routing utilizing cost information |
US8065417B1 (en) | 2008-11-17 | 2011-11-22 | Amazon Technologies, Inc. | Service provider registration by a content broker |
US8073940B1 (en) | 2008-11-17 | 2011-12-06 | Amazon Technologies, Inc. | Managing content delivery network service providers |
US8122098B1 (en) | 2008-11-17 | 2012-02-21 | Amazon Technologies, Inc. | Managing content delivery network service providers by a content broker |
US8060616B1 (en) | 2008-11-17 | 2011-11-15 | Amazon Technologies, Inc. | Managing CDN registration by a storage provider |
US8756341B1 (en) | 2009-03-27 | 2014-06-17 | Amazon Technologies, Inc. | Request routing utilizing popularity information |
US8521851B1 (en) | 2009-03-27 | 2013-08-27 | Amazon Technologies, Inc. | DNS query processing using resource identifiers specifying an application broker |
US8688837B1 (en) | 2009-03-27 | 2014-04-01 | Amazon Technologies, Inc. | Dynamically translating resource identifiers for request routing using popularity information |
US8412823B1 (en) | 2009-03-27 | 2013-04-02 | Amazon Technologies, Inc. | Managing tracking information entries in resource cache components |
US20100268600A1 (en) * | 2009-04-16 | 2010-10-21 | Evri Inc. | Enhanced advertisement targeting |
US8782236B1 (en) | 2009-06-16 | 2014-07-15 | Amazon Technologies, Inc. | Managing resources using resource expiration data |
US8397073B1 (en) | 2009-09-04 | 2013-03-12 | Amazon Technologies, Inc. | Managing secure content in a content delivery network |
US8433771B1 (en) | 2009-10-02 | 2013-04-30 | Amazon Technologies, Inc. | Distribution network with forward resource propagation |
US9495338B1 (en) | 2010-01-28 | 2016-11-15 | Amazon Technologies, Inc. | Content distribution network |
US9600512B2 (en) * | 2010-02-25 | 2017-03-21 | Salesforce.Com, Inc. | Systems and methods for implementing customized drop-down menus |
US9710556B2 (en) * | 2010-03-01 | 2017-07-18 | Vcvc Iii Llc | Content recommendation based on collections of entities |
US8645125B2 (en) | 2010-03-30 | 2014-02-04 | Evri, Inc. | NLP-based systems and methods for providing quotations |
US8600979B2 (en) | 2010-06-28 | 2013-12-03 | Yahoo! Inc. | Infinite browse |
US8838633B2 (en) | 2010-08-11 | 2014-09-16 | Vcvc Iii Llc | NLP-based sentiment analysis |
US9405848B2 (en) | 2010-09-15 | 2016-08-02 | Vcvc Iii Llc | Recommending mobile device activities |
US10097398B1 (en) | 2010-09-28 | 2018-10-09 | Amazon Technologies, Inc. | Point of presence management in request routing |
US8468247B1 (en) | 2010-09-28 | 2013-06-18 | Amazon Technologies, Inc. | Point of presence management in request routing |
US8577992B1 (en) | 2010-09-28 | 2013-11-05 | Amazon Technologies, Inc. | Request routing management based on network components |
US9712484B1 (en) | 2010-09-28 | 2017-07-18 | Amazon Technologies, Inc. | Managing request routing information utilizing client identifiers |
US9003035B1 (en) | 2010-09-28 | 2015-04-07 | Amazon Technologies, Inc. | Point of presence management in request routing |
US10958501B1 (en) | 2010-09-28 | 2021-03-23 | Amazon Technologies, Inc. | Request routing information based on client IP groupings |
US8819283B2 (en) | 2010-09-28 | 2014-08-26 | Amazon Technologies, Inc. | Request routing in a networked environment |
US9779168B2 (en) | 2010-10-04 | 2017-10-03 | Excalibur Ip, Llc | Contextual quick-picks |
US8762411B2 (en) * | 2010-10-08 | 2014-06-24 | Sap Ag | Progressive exploration of data relationships |
US8725739B2 (en) * | 2010-11-01 | 2014-05-13 | Evri, Inc. | Category-based content recommendation |
US9378111B2 (en) * | 2010-11-11 | 2016-06-28 | Sap Se | Method and system for easy correlation between monitored metrics and alerts |
US8452874B2 (en) | 2010-11-22 | 2013-05-28 | Amazon Technologies, Inc. | Request routing processing |
US9391949B1 (en) | 2010-12-03 | 2016-07-12 | Amazon Technologies, Inc. | Request routing processing |
US20120197971A1 (en) * | 2011-02-01 | 2012-08-02 | Shiarng Llc | Enhanced web-browsing system and method |
US9116995B2 (en) | 2011-03-30 | 2015-08-25 | Vcvc Iii Llc | Cluster-based identification of news stories |
US10467042B1 (en) | 2011-04-27 | 2019-11-05 | Amazon Technologies, Inc. | Optimized deployment based upon customer locality |
US9176957B2 (en) | 2011-06-10 | 2015-11-03 | Linkedin Corporation | Selective fact checking method and system |
US9015037B2 (en) | 2011-06-10 | 2015-04-21 | Linkedin Corporation | Interactive fact checking system |
US9087048B2 (en) | 2011-06-10 | 2015-07-21 | Linkedin Corporation | Method of and system for validating a fact checking system |
US8185448B1 (en) | 2011-06-10 | 2012-05-22 | Myslinski Lucas J | Fact checking method and system |
US8813111B2 (en) * | 2011-08-22 | 2014-08-19 | Xerox Corporation | Photograph-based game |
US8904009B1 (en) * | 2012-02-10 | 2014-12-02 | Amazon Technologies, Inc. | Dynamic content delivery |
US10021179B1 (en) | 2012-02-21 | 2018-07-10 | Amazon Technologies, Inc. | Local resource delivery network |
US20130246449A1 (en) * | 2012-03-16 | 2013-09-19 | Research In Motion Limited | Methods and devices for identifying a relationship between contacts |
US10623408B1 (en) | 2012-04-02 | 2020-04-14 | Amazon Technologies, Inc. | Context sensitive object management |
US9015073B2 (en) | 2012-06-06 | 2015-04-21 | Addepar, Inc. | Controlled creation of reports from table views |
US9154551B1 (en) | 2012-06-11 | 2015-10-06 | Amazon Technologies, Inc. | Processing DNS queries to identify pre-processing information |
US9411327B2 (en) | 2012-08-27 | 2016-08-09 | Johnson Controls Technology Company | Systems and methods for classifying data in building automation systems |
US9525659B1 (en) | 2012-09-04 | 2016-12-20 | Amazon Technologies, Inc. | Request routing utilizing point of presence load information |
US9323577B2 (en) | 2012-09-20 | 2016-04-26 | Amazon Technologies, Inc. | Automated profiling of resource usage |
US9483159B2 (en) | 2012-12-12 | 2016-11-01 | Linkedin Corporation | Fact checking graphical user interface including fact checking icons |
US11003729B2 (en) | 2012-12-12 | 2021-05-11 | Google Llc | Providing search results based on a compositional query |
CN103020030A (en) * | 2012-12-13 | 2013-04-03 | 鸿富锦精密工业(深圳)有限公司 | Electronic device and method for quickly introducing mail into editing interface of notepad |
US9105062B2 (en) | 2012-12-13 | 2015-08-11 | Addepar, Inc. | Transaction effects |
US10205698B1 (en) | 2012-12-19 | 2019-02-12 | Amazon Technologies, Inc. | Source-dependent address resolution |
CN103929350B (en) | 2013-01-16 | 2018-05-22 | 阿里巴巴集团控股有限公司 | A kind of method, apparatus and system of information push |
US9294391B1 (en) | 2013-06-04 | 2016-03-22 | Amazon Technologies, Inc. | Managing network computing components utilizing request routing |
US9467411B2 (en) | 2013-07-31 | 2016-10-11 | International Business Machines Corporation | Identifying content in an incoming message on a social network |
US8886671B1 (en) | 2013-08-14 | 2014-11-11 | Advent Software, Inc. | Multi-tenant in-memory database (MUTED) system and method |
US10169424B2 (en) | 2013-09-27 | 2019-01-01 | Lucas J. Myslinski | Apparatus, systems and methods for scoring and distributing the reliability of online information |
US20150095320A1 (en) | 2013-09-27 | 2015-04-02 | Trooclick France | Apparatus, systems and methods for scoring the reliability of online information |
US9972055B2 (en) | 2014-02-28 | 2018-05-15 | Lucas J. Myslinski | Fact checking method and system utilizing social networking information |
US9643722B1 (en) | 2014-02-28 | 2017-05-09 | Lucas J. Myslinski | Drone device security system |
US8990234B1 (en) | 2014-02-28 | 2015-03-24 | Lucas J. Myslinski | Efficient fact checking method and system |
US9189514B1 (en) | 2014-09-04 | 2015-11-17 | Lucas J. Myslinski | Optimized fact checking method and system |
US9424333B1 (en) | 2014-09-05 | 2016-08-23 | Addepar, Inc. | Systems and user interfaces for dynamic and interactive report generation and editing based on automatic traversal of complex data structures |
US9244899B1 (en) | 2014-10-03 | 2016-01-26 | Addepar, Inc. | Systems and user interfaces for dynamic and interactive table generation and editing based on automatic traversal of complex data structures including time varying attributes |
US9218502B1 (en) | 2014-10-17 | 2015-12-22 | Addepar, Inc. | System and architecture for electronic permissions and security policies for resources in a data system |
US10091096B1 (en) | 2014-12-18 | 2018-10-02 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US10097448B1 (en) | 2014-12-18 | 2018-10-09 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US10033627B1 (en) | 2014-12-18 | 2018-07-24 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
US10225326B1 (en) | 2015-03-23 | 2019-03-05 | Amazon Technologies, Inc. | Point of presence based data uploading |
US9887931B1 (en) | 2015-03-30 | 2018-02-06 | Amazon Technologies, Inc. | Traffic surge management for points of presence |
US9819567B1 (en) | 2015-03-30 | 2017-11-14 | Amazon Technologies, Inc. | Traffic surge management for points of presence |
US9887932B1 (en) | 2015-03-30 | 2018-02-06 | Amazon Technologies, Inc. | Traffic surge management for points of presence |
US9832141B1 (en) | 2015-05-13 | 2017-11-28 | Amazon Technologies, Inc. | Routing based request correlation |
US10146853B2 (en) | 2015-05-15 | 2018-12-04 | International Business Machines Corporation | Determining entity relationship when entities contain other entities |
US10097566B1 (en) | 2015-07-31 | 2018-10-09 | Amazon Technologies, Inc. | Identifying targets of network attacks |
US9794281B1 (en) | 2015-09-24 | 2017-10-17 | Amazon Technologies, Inc. | Identifying sources of network attacks |
US9742795B1 (en) | 2015-09-24 | 2017-08-22 | Amazon Technologies, Inc. | Mitigating network attacks |
US9774619B1 (en) | 2015-09-24 | 2017-09-26 | Amazon Technologies, Inc. | Mitigating network attacks |
US10534326B2 (en) | 2015-10-21 | 2020-01-14 | Johnson Controls Technology Company | Building automation system with integrated building information model |
US10732810B1 (en) | 2015-11-06 | 2020-08-04 | Addepar, Inc. | Systems and user interfaces for dynamic and interactive table generation and editing based on automatic traversal of complex data structures including summary data such as time series data |
US11443390B1 (en) | 2015-11-06 | 2022-09-13 | Addepar, Inc. | Systems and user interfaces for dynamic and interactive table generation and editing based on automatic traversal of complex data structures and incorporation of metadata mapped to the complex data structures |
US10270878B1 (en) | 2015-11-10 | 2019-04-23 | Amazon Technologies, Inc. | Routing for origin-facing points of presence |
US10372807B1 (en) | 2015-11-11 | 2019-08-06 | Addepar, Inc. | Systems and user interfaces for dynamic and interactive table generation and editing based on automatic traversal of complex data structures in a distributed system architecture |
US10257307B1 (en) | 2015-12-11 | 2019-04-09 | Amazon Technologies, Inc. | Reserved cache space in content delivery networks |
US10049051B1 (en) | 2015-12-11 | 2018-08-14 | Amazon Technologies, Inc. | Reserved cache space in content delivery networks |
US10348639B2 (en) | 2015-12-18 | 2019-07-09 | Amazon Technologies, Inc. | Use of virtual endpoints to improve data transmission rates |
US10649419B2 (en) | 2016-06-14 | 2020-05-12 | Johnson Controls Technology Company | Building management system with virtual points and optimized data integration |
US11268732B2 (en) | 2016-01-22 | 2022-03-08 | Johnson Controls Technology Company | Building energy management system with energy analytics |
US11947785B2 (en) | 2016-01-22 | 2024-04-02 | Johnson Controls Technology Company | Building system with a building graph |
US10055114B2 (en) * | 2016-01-22 | 2018-08-21 | Johnson Controls Technology Company | Building energy management system with ad hoc dashboard |
AU2017214759B2 (en) * | 2016-02-01 | 2021-09-30 | Global Software Innovation Pty Ltd | Graph-based operations on an entity-relationship database |
WO2017173167A1 (en) | 2016-03-31 | 2017-10-05 | Johnson Controls Technology Company | Hvac device registration in a distributed building management system |
US10104152B2 (en) | 2016-04-28 | 2018-10-16 | TeamMate Licensing B.V. | Inter-application communication and integration broker |
US10417451B2 (en) | 2017-09-27 | 2019-09-17 | Johnson Controls Technology Company | Building system with smart entity personal identifying information (PII) masking |
US10505756B2 (en) | 2017-02-10 | 2019-12-10 | Johnson Controls Technology Company | Building management system with space graphs |
US11774920B2 (en) | 2016-05-04 | 2023-10-03 | Johnson Controls Technology Company | Building system with user presentation composition based on building context |
US10075551B1 (en) | 2016-06-06 | 2018-09-11 | Amazon Technologies, Inc. | Request management for hierarchical cache |
US10110694B1 (en) | 2016-06-29 | 2018-10-23 | Amazon Technologies, Inc. | Adaptive transfer rate for retrieving content from a server |
US9992086B1 (en) | 2016-08-23 | 2018-06-05 | Amazon Technologies, Inc. | External health checking of virtual private cloud network environments |
US10033691B1 (en) | 2016-08-24 | 2018-07-24 | Amazon Technologies, Inc. | Adaptive resolution of domain name requests in virtual private cloud network environments |
US10616250B2 (en) | 2016-10-05 | 2020-04-07 | Amazon Technologies, Inc. | Network addresses with encoded DNS-level information |
US10114815B2 (en) * | 2016-10-25 | 2018-10-30 | International Business Machines Corporation | Core points associations sentiment analysis in large documents |
US10831549B1 (en) | 2016-12-27 | 2020-11-10 | Amazon Technologies, Inc. | Multi-region request-driven code execution system |
US10372499B1 (en) | 2016-12-27 | 2019-08-06 | Amazon Technologies, Inc. | Efficient region selection system for executing request-driven code |
US11700258B2 (en) * | 2016-12-30 | 2023-07-11 | Ssh Communications Security Oyj | Access relationships in a computer system |
US10389722B2 (en) | 2016-12-30 | 2019-08-20 | Ssh Communications Security Oyj | Access relationships in a computer system |
US10684033B2 (en) | 2017-01-06 | 2020-06-16 | Johnson Controls Technology Company | HVAC system with automated device pairing |
US10938884B1 (en) | 2017-01-30 | 2021-03-02 | Amazon Technologies, Inc. | Origin server cloaking using virtual private cloud network environments |
US11900287B2 (en) | 2017-05-25 | 2024-02-13 | Johnson Controls Tyco IP Holdings LLP | Model predictive maintenance system with budgetary constraints |
US10452043B2 (en) | 2017-02-10 | 2019-10-22 | Johnson Controls Technology Company | Building management system with nested stream generation |
US10515098B2 (en) | 2017-02-10 | 2019-12-24 | Johnson Controls Technology Company | Building management smart entity creation and maintenance using time series data |
US11307538B2 (en) | 2017-02-10 | 2022-04-19 | Johnson Controls Technology Company | Web services platform with cloud-eased feedback control |
US11994833B2 (en) | 2017-02-10 | 2024-05-28 | Johnson Controls Technology Company | Building smart entity system with agent based data ingestion and entity creation using time series data |
US11764991B2 (en) | 2017-02-10 | 2023-09-19 | Johnson Controls Technology Company | Building management system with identity management |
US10169486B2 (en) | 2017-02-10 | 2019-01-01 | Johnson Controls Technology Company | Building management system with timeseries processing |
US20190095518A1 (en) | 2017-09-27 | 2019-03-28 | Johnson Controls Technology Company | Web services for smart entity creation and maintenance using time series data |
US11360447B2 (en) | 2017-02-10 | 2022-06-14 | Johnson Controls Technology Company | Building smart entity system with agent based communication and control |
WO2018175912A1 (en) | 2017-03-24 | 2018-09-27 | Johnson Controls Technology Company | Building management system with dynamic channel communication |
US11327737B2 (en) | 2017-04-21 | 2022-05-10 | Johnson Controls Tyco IP Holdings LLP | Building management system with cloud management of gateway configurations |
US10503613B1 (en) | 2017-04-21 | 2019-12-10 | Amazon Technologies, Inc. | Efficient serving of resources during server unavailability |
US10788229B2 (en) | 2017-05-10 | 2020-09-29 | Johnson Controls Technology Company | Building management system with a distributed blockchain database |
US11022947B2 (en) | 2017-06-07 | 2021-06-01 | Johnson Controls Technology Company | Building energy optimization system with economic load demand response (ELDR) optimization and ELDR user interfaces |
US11075987B1 (en) | 2017-06-12 | 2021-07-27 | Amazon Technologies, Inc. | Load estimating content delivery network |
WO2018232147A1 (en) | 2017-06-15 | 2018-12-20 | Johnson Controls Technology Company | Building management system with artificial intelligence for unified agent based control of building subsystems |
US10447648B2 (en) | 2017-06-19 | 2019-10-15 | Amazon Technologies, Inc. | Assignment of a POP to a DNS resolver based on volume of communications over a link between client devices and the POP |
EP3655826B1 (en) | 2017-07-17 | 2024-07-03 | Johnson Controls Tyco IP Holdings LLP | Systems and methods for agent based building simulation for optimal control |
US11422516B2 (en) | 2017-07-21 | 2022-08-23 | Johnson Controls Tyco IP Holdings LLP | Building management system with dynamic rules with sub-rule reuse and equation driven smart diagnostics |
US11182047B2 (en) | 2017-07-27 | 2021-11-23 | Johnson Controls Technology Company | Building management system with fault detection and diagnostics visualization |
US10742593B1 (en) | 2017-09-25 | 2020-08-11 | Amazon Technologies, Inc. | Hybrid content request routing system |
US10962945B2 (en) | 2017-09-27 | 2021-03-30 | Johnson Controls Technology Company | Building management system with integration of data into smart entities |
US10565844B2 (en) | 2017-09-27 | 2020-02-18 | Johnson Controls Technology Company | Building risk analysis system with global risk dashboard |
US11281169B2 (en) | 2017-11-15 | 2022-03-22 | Johnson Controls Tyco IP Holdings LLP | Building management system with point virtualization for online meters |
US10809682B2 (en) | 2017-11-15 | 2020-10-20 | Johnson Controls Technology Company | Building management system with optimized processing of building system data |
US11127235B2 (en) | 2017-11-22 | 2021-09-21 | Johnson Controls Tyco IP Holdings LLP | Building campus with integrated smart environment |
US10592578B1 (en) | 2018-03-07 | 2020-03-17 | Amazon Technologies, Inc. | Predictive content push-enabled content delivery network |
US11954713B2 (en) | 2018-03-13 | 2024-04-09 | Johnson Controls Tyco IP Holdings LLP | Variable refrigerant flow system with electricity consumption apportionment |
US10915649B2 (en) | 2018-09-10 | 2021-02-09 | Sap Se | Association-based access control delegation |
US11016648B2 (en) | 2018-10-30 | 2021-05-25 | Johnson Controls Technology Company | Systems and methods for entity visualization and management with an entity node editor |
US10713329B2 (en) * | 2018-10-30 | 2020-07-14 | Longsand Limited | Deriving links to online resources based on implicit references |
US10862852B1 (en) | 2018-11-16 | 2020-12-08 | Amazon Technologies, Inc. | Resolution of domain name requests in heterogeneous network environments |
US11927925B2 (en) | 2018-11-19 | 2024-03-12 | Johnson Controls Tyco IP Holdings LLP | Building system with a time correlated reliability data stream |
US11397770B2 (en) * | 2018-11-26 | 2022-07-26 | Sap Se | Query discovery and interpretation |
US11025747B1 (en) | 2018-12-12 | 2021-06-01 | Amazon Technologies, Inc. | Content request pattern-based routing system |
US11468408B2 (en) | 2019-01-18 | 2022-10-11 | Johnson Controls Tyco IP Holdings LLP | Building automation system with visitor management |
US10788798B2 (en) | 2019-01-28 | 2020-09-29 | Johnson Controls Technology Company | Building management system with hybrid edge-cloud processing |
US12099334B2 (en) | 2019-12-31 | 2024-09-24 | Tyco Fire & Security Gmbh | Systems and methods for presenting multiple BIM files in a single interface |
US12021650B2 (en) | 2019-12-31 | 2024-06-25 | Tyco Fire & Security Gmbh | Building data platform with event subscriptions |
AU2020417229A1 (en) | 2019-12-31 | 2022-08-25 | Johnson Controls Tyco IP Holdings LLP | Building data platform |
US11894944B2 (en) | 2019-12-31 | 2024-02-06 | Johnson Controls Tyco IP Holdings LLP | Building data platform with an enrichment loop |
US11769066B2 (en) | 2021-11-17 | 2023-09-26 | Johnson Controls Tyco IP Holdings LLP | Building data platform with digital twin triggers and actions |
US12100280B2 (en) | 2020-02-04 | 2024-09-24 | Tyco Fire & Security Gmbh | Systems and methods for software defined fire detection and risk assessment |
US11537386B2 (en) | 2020-04-06 | 2022-12-27 | Johnson Controls Tyco IP Holdings LLP | Building system with dynamic configuration of network resources for 5G networks |
US11874809B2 (en) | 2020-06-08 | 2024-01-16 | Johnson Controls Tyco IP Holdings LLP | Building system with naming schema encoding entity type and entity relationships |
US11350285B2 (en) | 2020-09-15 | 2022-05-31 | T-Mobile Usa, Inc. | Visual voicemail as service for authentication or account recovery of wireless devices in a wireless network |
US11546773B2 (en) | 2020-09-15 | 2023-01-03 | T-Mobile Usa, Inc. | Visual voicemail centralized authentication system for wireless networks |
US11397773B2 (en) | 2020-09-30 | 2022-07-26 | Johnson Controls Tyco IP Holdings LLP | Building management system with semantic model integration |
US11954154B2 (en) | 2020-09-30 | 2024-04-09 | Johnson Controls Tyco IP Holdings LLP | Building management system with semantic model integration |
US12063274B2 (en) | 2020-10-30 | 2024-08-13 | Tyco Fire & Security Gmbh | Self-configuring building management system |
US12061453B2 (en) | 2020-12-18 | 2024-08-13 | Tyco Fire & Security Gmbh | Building management system performance index |
CN117280291A (en) | 2021-03-17 | 2023-12-22 | 江森自控泰科知识产权控股有限责任合伙公司 | System and method for determining device energy waste |
US11899723B2 (en) | 2021-06-22 | 2024-02-13 | Johnson Controls Tyco IP Holdings LLP | Building data platform with context based twin function processing |
US11796974B2 (en) | 2021-11-16 | 2023-10-24 | Johnson Controls Tyco IP Holdings LLP | Building data platform with schema extensibility for properties and tags of a digital twin |
US11934966B2 (en) | 2021-11-17 | 2024-03-19 | Johnson Controls Tyco IP Holdings LLP | Building data platform with digital twin inferences |
US11704311B2 (en) | 2021-11-24 | 2023-07-18 | Johnson Controls Tyco IP Holdings LLP | Building data platform with a distributed digital twin |
US11714930B2 (en) | 2021-11-29 | 2023-08-01 | Johnson Controls Tyco IP Holdings LLP | Building data platform with digital twin based inferences and predictions for a graphical building model |
US12013673B2 (en) | 2021-11-29 | 2024-06-18 | Tyco Fire & Security Gmbh | Building control system using reinforcement learning |
US12013823B2 (en) | 2022-09-08 | 2024-06-18 | Tyco Fire & Security Gmbh | Gateway system that maps points into a graph schema |
US12061633B2 (en) | 2022-09-08 | 2024-08-13 | Tyco Fire & Security Gmbh | Building system that maps points into a graph schema |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010039546A1 (en) * | 2000-05-05 | 2001-11-08 | Moore Michael R. | System and method for obtaining and storing information for deferred browsing |
US20020128947A1 (en) * | 2001-03-07 | 2002-09-12 | The Vanguard Group, Inc. | Investment company that issues a class of conventional shares and a class of exchange-traded shares in the same fund |
US20030018616A1 (en) * | 2001-06-05 | 2003-01-23 | Wilbanks John Thompson | Systems, methods and computer program products for integrating databases to create an ontology network |
US20030131013A1 (en) * | 2002-01-07 | 2003-07-10 | Cameron Pope | Automated system and methods for determining relationships between information resources |
US20030236768A1 (en) * | 2002-04-22 | 2003-12-25 | Paul Sribhibhadh | Food tracing and tracking system and method |
US20050033583A1 (en) * | 2000-07-27 | 2005-02-10 | Bergeron Heather Ellen | Processing transactions using a structured natural language |
US20050071362A1 (en) * | 2003-09-30 | 2005-03-31 | Nelson Brent Dalmas | Enterprises taxonomy formation method and system for an intellectual capital management system |
US20060173672A1 (en) * | 2000-07-27 | 2006-08-03 | Bergeron Heather E | Processing health care transactions using a semantic network |
US7103607B1 (en) * | 2000-11-20 | 2006-09-05 | Cisco Technology, Inc. | Business vocabulary data retrieval using alternative forms |
Family Cites Families (47)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH06119393A (en) * | 1992-08-20 | 1994-04-28 | Ricoh Co Ltd | Electronic file device |
JP3457061B2 (en) * | 1994-06-28 | 2003-10-14 | 富士通株式会社 | Attribute mixed character string sorting device and attribute mixed character string sorting method |
US5682525A (en) * | 1995-01-11 | 1997-10-28 | Civix Corporation | System and methods for remotely accessing a selected group of items of interest from a database |
US5649182A (en) * | 1995-03-17 | 1997-07-15 | Reitz; Carl A. | Apparatus and method for organizing timeline data |
US5901214A (en) * | 1996-06-10 | 1999-05-04 | Murex Securities, Ltd. | One number intelligent call processing system |
US6055515A (en) * | 1996-07-30 | 2000-04-25 | International Business Machines Corporation | Enhanced tree control system for navigating lattices data structures and displaying configurable lattice-node labels |
US5787435A (en) * | 1996-08-09 | 1998-07-28 | Digital Equipment Corporation | Method for mapping an index of a database into an array of files |
US5842218A (en) * | 1996-12-06 | 1998-11-24 | Media Plan, Inc. | Method, computer program product, and system for a reorienting categorization table |
US5842221A (en) * | 1997-02-19 | 1998-11-24 | Wisdomware, Inc. | Dynamic frequently asked questions (FAQ) system |
JP3887867B2 (en) * | 1997-02-26 | 2007-02-28 | 株式会社日立製作所 | How to register structured documents |
US6023723A (en) * | 1997-12-22 | 2000-02-08 | Accepted Marketing, Inc. | Method and system for filtering unwanted junk e-mail utilizing a plurality of filtering mechanisms |
US6112209A (en) * | 1998-06-17 | 2000-08-29 | Gusack; Mark David | Associative database model for electronic-based informational assemblies |
US6233583B1 (en) * | 1998-09-10 | 2001-05-15 | International Business Machines Corporation | Report generator for use within a lotus notes database system |
US6005515A (en) * | 1999-04-09 | 1999-12-21 | Trw Inc. | Multiple scanning beam direct radiating array and method for its use |
US6493703B1 (en) * | 1999-05-11 | 2002-12-10 | Prophet Financial Systems | System and method for implementing intelligent online community message board |
US6546390B1 (en) * | 1999-06-11 | 2003-04-08 | Abuzz Technologies, Inc. | Method and apparatus for evaluating relevancy of messages to users |
US6618732B1 (en) * | 2000-04-11 | 2003-09-09 | Revelink, Inc. | Database query handler supporting querying of textual annotations of relations between data objects |
US6853997B2 (en) * | 2000-06-29 | 2005-02-08 | Infoglide Corporation | System and method for sharing, mapping, transforming data between relational and hierarchical databases |
WO2002006998A2 (en) * | 2000-07-19 | 2002-01-24 | Sentient Jet, Inc. | Method and apparatus for arranging flexible and cost-efficient private air travel |
US6687696B2 (en) * | 2000-07-26 | 2004-02-03 | Recommind Inc. | System and method for personalized search, information filtering, and for generating recommendations utilizing statistical latent class models |
US20050010394A1 (en) * | 2000-07-27 | 2005-01-13 | Bergeron Heather Ellen | Configuring a semantic network to process transactions |
US6452998B2 (en) * | 2000-07-31 | 2002-09-17 | Analogic Corporation | Tiltable gantry for x-ray tomography system |
EP1213898B1 (en) * | 2000-12-05 | 2004-11-03 | Inventec Appliances Corp. | Method of automatically providing the country code and area code of a phone number by selecting the city |
US20020174050A1 (en) * | 2000-12-27 | 2002-11-21 | James Eynard | Business capacity transaction management system |
US6925605B2 (en) * | 2000-12-28 | 2005-08-02 | International Business Machines Corporation | Collating table for email |
US7085773B2 (en) * | 2001-01-05 | 2006-08-01 | Symyx Technologies, Inc. | Laboratory database system and methods for combinatorial materials research |
US6658429B2 (en) * | 2001-01-05 | 2003-12-02 | Symyx Technologies, Inc. | Laboratory database system and methods for combinatorial materials research |
US6399471B1 (en) * | 2001-02-15 | 2002-06-04 | Chartered Semiconductor Manufacturing Ltd. | Assorted aluminum wiring design to enhance chip-level performance for deep sub-micron application |
US6633884B2 (en) * | 2001-04-03 | 2003-10-14 | Bmc Software, Inc. | System and method for analyzing a database for on-line reorganization |
US20030041050A1 (en) * | 2001-04-16 | 2003-02-27 | Greg Smith | System and method for web-based marketing and campaign management |
US20030009536A1 (en) * | 2001-07-06 | 2003-01-09 | Portris, Inc. | Method and system for collaborative knowledge management |
US7130861B2 (en) * | 2001-08-16 | 2006-10-31 | Sentius International Corporation | Automated creation and delivery of database content |
US20030187813A1 (en) * | 2002-03-26 | 2003-10-02 | Goldman Neal D. | System and method for identifying relationship paths to a target entity |
US7567676B2 (en) * | 2002-05-03 | 2009-07-28 | Harman International Industries, Incorporated | Sound event detection and localization system using power analysis |
US7165075B2 (en) * | 2002-07-20 | 2007-01-16 | Microsoft Corporation | Object graph faulting and trimming in an object-relational database system |
US7149733B2 (en) * | 2002-07-20 | 2006-12-12 | Microsoft Corporation | Translation of object queries involving inheritence |
US7412436B2 (en) * | 2002-07-20 | 2008-08-12 | Microsoft Corporation | System and interface for manipulating a database |
US7162469B2 (en) * | 2002-07-20 | 2007-01-09 | Microsoft Corporation | Querying an object for properties |
US7096216B2 (en) * | 2002-07-20 | 2006-08-22 | Microsoft Corporation | Performing operations on a set of objects in a database system |
US7082433B2 (en) * | 2002-07-20 | 2006-07-25 | Microsoft Corporation | Translation of object queries involving inheritence |
US7136873B2 (en) * | 2002-07-20 | 2006-11-14 | Microsoft Corporation | Dynamic filtering in a database system |
US7010542B2 (en) * | 2002-07-20 | 2006-03-07 | Microsoft Corporation | Result set formatting and processing |
US7254808B2 (en) * | 2002-07-20 | 2007-08-07 | Microsoft Corporation | Method for specifying and parsing expressions |
US7269795B2 (en) * | 2003-03-07 | 2007-09-11 | Microsoft Corporation | Dynamically generated user interface for business application integration |
US7313561B2 (en) * | 2003-03-12 | 2007-12-25 | Microsoft Corporation | Model definition schema |
US8122044B2 (en) * | 2003-03-12 | 2012-02-21 | Microsoft Corporation | Generation of business intelligence entities from a dimensional model |
US7275024B2 (en) * | 2003-03-12 | 2007-09-25 | Microsoft Corporation | Automatic generation of a dimensional model for business analytics from an object model for online transaction processing |
-
2003
- 2003-11-13 US US10/712,076 patent/US20050108024A1/en not_active Abandoned
-
2004
- 2004-11-12 GB GB0610958A patent/GB2424296A/en not_active Withdrawn
- 2004-11-12 WO PCT/US2004/038641 patent/WO2005050491A1/en active Application Filing
- 2004-11-12 US US10/987,375 patent/US7644088B2/en active Active
- 2004-11-12 EP EP04811368A patent/EP1687744A1/en not_active Withdrawn
- 2004-11-12 CA CA002545446A patent/CA2545446A1/en not_active Abandoned
-
2009
- 2009-11-19 US US12/622,184 patent/US20100121877A1/en not_active Abandoned
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010039546A1 (en) * | 2000-05-05 | 2001-11-08 | Moore Michael R. | System and method for obtaining and storing information for deferred browsing |
US20050033583A1 (en) * | 2000-07-27 | 2005-02-10 | Bergeron Heather Ellen | Processing transactions using a structured natural language |
US20060173672A1 (en) * | 2000-07-27 | 2006-08-03 | Bergeron Heather E | Processing health care transactions using a semantic network |
US7103607B1 (en) * | 2000-11-20 | 2006-09-05 | Cisco Technology, Inc. | Business vocabulary data retrieval using alternative forms |
US20020128947A1 (en) * | 2001-03-07 | 2002-09-12 | The Vanguard Group, Inc. | Investment company that issues a class of conventional shares and a class of exchange-traded shares in the same fund |
US20030018616A1 (en) * | 2001-06-05 | 2003-01-23 | Wilbanks John Thompson | Systems, methods and computer program products for integrating databases to create an ontology network |
US20030131013A1 (en) * | 2002-01-07 | 2003-07-10 | Cameron Pope | Automated system and methods for determining relationships between information resources |
US20030236768A1 (en) * | 2002-04-22 | 2003-12-25 | Paul Sribhibhadh | Food tracing and tracking system and method |
US20050071362A1 (en) * | 2003-09-30 | 2005-03-31 | Nelson Brent Dalmas | Enterprises taxonomy formation method and system for an intellectual capital management system |
Cited By (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8583680B2 (en) | 2002-05-31 | 2013-11-12 | Informatica Corporation | System and method for integrating, managing and coordinating customer activities |
US8200622B2 (en) | 2002-05-31 | 2012-06-12 | Informatica Corporation | System and method for integrating, managing and coordinating customer activities |
US20040006506A1 (en) * | 2002-05-31 | 2004-01-08 | Khanh Hoang | System and method for integrating, managing and coordinating customer activities |
US20060253475A1 (en) * | 2005-05-09 | 2006-11-09 | Cognos Incorporated | System and method for time dimension management for a data analyzing system |
US8434026B2 (en) * | 2005-05-09 | 2013-04-30 | International Business Machines Corporation | System and method for time dimension management for a data analyzing |
US8166048B2 (en) * | 2005-06-27 | 2012-04-24 | Informatica Corporation | Method and apparatus for data integration and management |
US20090182780A1 (en) * | 2005-06-27 | 2009-07-16 | Stanley Wong | Method and apparatus for data integration and management |
US8065266B2 (en) | 2006-01-03 | 2011-11-22 | Informatica Corporation | Relationship data management |
US20090327347A1 (en) * | 2006-01-03 | 2009-12-31 | Khanh Hoang | Relationship data management |
US8392460B2 (en) | 2006-01-03 | 2013-03-05 | Informatica Corporation | Relationship data management |
US20070214179A1 (en) * | 2006-03-10 | 2007-09-13 | Khanh Hoang | Searching, filtering, creating, displaying, and managing entity relationships across multiple data hierarchies through a user interface |
US8271477B2 (en) | 2007-07-20 | 2012-09-18 | Informatica Corporation | Methods and systems for accessing data |
US20090024589A1 (en) * | 2007-07-20 | 2009-01-22 | Manish Sood | Methods and systems for accessing data |
AU2010246536B2 (en) * | 2010-11-30 | 2014-01-23 | Finsuite Pty Ltd | Schematic Corporate Device and System |
US8832107B2 (en) * | 2012-03-21 | 2014-09-09 | Sap Ag | Collection and categorization of configuration data |
US8583687B1 (en) * | 2012-05-15 | 2013-11-12 | Algebraix Data Corporation | Systems and methods for indirect algebraic partitioning |
US20150046493A1 (en) * | 2013-08-07 | 2015-02-12 | Microsoft Corporation | Access and management of entity-augmented content |
US10255253B2 (en) | 2013-08-07 | 2019-04-09 | Microsoft Technology Licensing, Llc | Augmenting and presenting captured data |
US10776501B2 (en) | 2013-08-07 | 2020-09-15 | Microsoft Technology Licensing, Llc | Automatic augmentation of content through augmentation services |
US10817613B2 (en) * | 2013-08-07 | 2020-10-27 | Microsoft Technology Licensing, Llc | Access and management of entity-augmented content |
US10339183B2 (en) | 2015-06-22 | 2019-07-02 | Microsoft Technology Licensing, Llc | Document storage for reuse of content within documents |
US10757142B2 (en) * | 2017-09-01 | 2020-08-25 | Financial Crime Intelligence Ltd | Assimilated economic crime intelligence system and method |
US20220100782A1 (en) * | 2018-10-23 | 2022-03-31 | Yext, Inc. | Knowledge search system |
US12056164B2 (en) * | 2018-10-23 | 2024-08-06 | Yext, Inc. | Knowledge search system |
Also Published As
Publication number | Publication date |
---|---|
WO2005050491A1 (en) | 2005-06-02 |
GB0610958D0 (en) | 2006-07-12 |
EP1687744A1 (en) | 2006-08-09 |
GB2424296A (en) | 2006-09-20 |
CA2545446A1 (en) | 2005-06-02 |
US20050108024A1 (en) | 2005-05-19 |
US20050108262A1 (en) | 2005-05-19 |
US7644088B2 (en) | 2010-01-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7644088B2 (en) | Systems and methods for retrieving data | |
US10332132B2 (en) | Method and apparatus for colleting and disseminating information over a computer network | |
US20070038641A1 (en) | Systems and methods for automated application updating | |
US7379951B2 (en) | Support for real-time queries concerning current state, data and history of a process | |
US20060036641A1 (en) | System and method for using social networks for the distribution of communications | |
US7890405B1 (en) | Method and system for enabling collaboration between advisors and clients | |
US20020111922A1 (en) | Electronic markets business interchange system and method | |
US20020052862A1 (en) | Method and system for supply chain product and process development collaboration | |
US20060112130A1 (en) | System and method for resource management | |
US20050044149A1 (en) | System and methodology for facilitating the sale of goods and services | |
US20070299755A1 (en) | Purchase card performance system | |
US6983263B1 (en) | Electronic boardroom | |
Foster | What’s New: A Round-Up of New Products and Initiatives |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: TAMALE SOFTWARE, INC.,MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FAWCETT, JOHN;AKHNOUKH, NADER;DIAS, DANIEL;SIGNING DATES FROM 20061102 TO 20061106;REEL/FRAME:023628/0309 |
|
AS | Assignment |
Owner name: ADVENT SOFTWARE, INC.,CALIFORNIA Free format text: MERGER;ASSIGNOR:TAMALE SOFTWARE, INC.;REEL/FRAME:023694/0687 Effective date: 20081021 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |