WO2002095626A1 - Integrated data sharing system - Google Patents
Integrated data sharing system Download PDFInfo
- Publication number
- WO2002095626A1 WO2002095626A1 PCT/SG2002/000092 SG0200092W WO02095626A1 WO 2002095626 A1 WO2002095626 A1 WO 2002095626A1 SG 0200092 W SG0200092 W SG 0200092W WO 02095626 A1 WO02095626 A1 WO 02095626A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user
- document
- data
- documents
- component
- Prior art date
Links
Classifications
-
- 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/25—Integrating or interfacing systems involving database management systems
Definitions
- the invention relates to the sharing of data between disparate computer systems, in particular to a data sharing system which simplifies the consolidation and control of information to create documents on disparate computer systems on a network.
- each of the separate stand-alone systems may require the same information for common fields.
- information like the "Sender” field and the "Addressee” field can be used in different systems, such as an export permit application system, goods description system and so on. There may thus be a number of systems that require the same information.
- the invention provides a system for allowing sharing of data from disparate sources, comprising a user interface that enables a user to access the disparate sources, an intermediary component operationally linked between the user interface and the disparate sources, and a knowledge component of the intermediary component adapted to allow bi- directional triggering of data flow between one or a plurality of sources and another of said sources.
- Figure 1 is an architectural overview of the major components of a preferred embodiment of a system according to the invention.
- Figure 2 is an overview of the process for populating data between different document types, the different document types essentially being used by different applications.
- Figure 3 is a system flowchart illustrating the navigation between document types in the system.
- Figure 4 is a flowchart illustrating the process of detecting any changes in the data and the provision of user alerts in the system.
- Figure 5 is a sample database definition table to indicate the field mappings between different applications.
- Figure 6 is a sample database definition table showing the relationships between data from different " documents and the auto-learning function of the system.
- Figure 1 is an architectural overview of the major components of the preferred embodiment of the invention.
- a user 1 is able to access a series of disparate computer systems or applications 40-48 through a user interface, via an intermediary component 5.
- the intermediary component 5 comprises the major functional components of the system, and preferably combines an alert component 10, a navigation component 20 and knowledge component 30 to integrate the distributed disparate applications 40-48.
- the alert component 10 detects changes in the data fields and preferably provides user alerts upon occurrence of the changes.
- the navigational component 20 navigates between different document types in the system and is capable of inferring a document flow, if any.
- the knowledge component 30 consolidates relationships between the various data fields and populates data for different document types in the system.
- the programming language is preferably an object-oriented language, such as Java programming language.
- the system preferably forms a single integrated entity on a web deployment environment comprising a web server and possibly multiple application servers.
- Figure 2 is an overview of the process for populating data between different document types, the different document types essentially being used by different applications.
- Document-related and field-related knowledge are consolidated at the knowledge component 30 outside the disparate applications 40-48 by the use of a table of field mappings (see Figure 5).
- the knowledge component 30 in Figure 1 separates the inter-document field relationships and related processing logic. It will be appreciated that different document types are still residing in the different applications 40-48.
- the knowledge component contains the mappings and dependencies between the various fields, and the transformation logic for each pair of document types. It allows mappings from one or multiple document types to another document type.
- the knowledge component 30 will first determine the type of target document from the input in the user session. It will then obtain the source documents, and retrieve the data relationships and dependencies from a table of field mappings (see Figure 5). Once relevant fields are identified, the target document is populated with data from the source documents.
- the system is implemented in a World-Wide Web based Internet environment.
- the target document may be put into a HyperText Transfer Protocol (HTTP) session on the Internet.
- HTTP HyperText Transfer Protocol
- URL Uniform Resource Locator
- the target application retrieves a populated document from the user session.
- the target application processes the data and allows the user to update the data.
- Figure 3 is a system flowchart illustrating the navigation between document types in the system. It demonstrates the navigational flexibility of the navigation component 20 in controlling the sequence of document flow.
- the system has the ability to branch out, if necessary, from pre-determined document flow sequences. It also has the ability to track a document sequence by the use of a definition table (see Figure 6).
- the navigation component 20 of the system first obtains the status of a sequence flow. If there is an available user-defined document flow, the system infers the next possible target document type based upon the user- defined document flow. Otherwise, the system will infer the next possible target document type based upon the past experience of the user, in accordance with the table in Figure 6 showing the relationships between data from different documents recorded based upon prior activity of the user working on the system. The user has the option to accept the suggested target document type. Otherwise, the user would select a target document type he requires.
- the status of the sequence flow is then updated for later reference in Figure 6. Thereafter, the workflow proceeds back to the knowledge component 30 (see Figure 2).
- the navigational component 20 of the system thus determines, where applicable, the next target document type in flow sequence, based on user-defined document flow or past transaction data.
- Figure 4 is a flowchart illustrating the process of detecting any changes in the data and the provision of user alerts in the system.
- the system will detect data changes in various document types in each of the applications once these changes occur. Thereafter, it will alert all users that have earlier made use of these data by reading the definition table (see Figure 6) which has recorded the previous target documents created by users of the system, and the source documents used to populate them.
- the application 40-48 would first inform the alert component 10 of data changes to any of the documents.
- the alert component 10 assesses the definition table listing the different documents to trace and locate other documents that contain data that was derived from the changed document.
- the alert component 10 then retrieves the associated user-ids from the table.
- the alert component 10 is capable of alerting the affected users via e-mails, messages or any other communication mechanisms.
- Figure 5 is a sample database definition table to indicate the field mappings between different applications.
- the values of the fields are preferably inserted by the system administrator before the system is used.
- Table 1A illustrates one of the ways in which the table may be used:
- Table 1A contains five hypothetical document field relationships. Assuming that the source document type is Doc A and target document type is Doc C (i.e. the user is populating Doc C with data from Doc A), the document field relationships between these 2 documents can be retrieved
- the system infers that Field C in Section D of Doc A is related to Field F in Section A of Doc C.
- the prefix "Single_" of SourceDocType 20 indicates that Field C is a single field (possibly a textbox) in Section A of Doc A. For such single fields, the system only needs to map a single value to the target document.
- the system infers that Field E in Group B of Doc A is related to Field M of Group D of Doc C. Since SourceDocType is not prefixed with the value "Single_", it implies Field E consists of a group of values (possibly a column of values in a table). For such group field, the system needs to map a group of values to the target document.
- the value of "Address" in SourceBindName of both row 1 and 5 indicates that values of Fields C and D in Section D of Doc A is to be joined to form a single value and be mapped to Field F of Section A in Doc C.
- the placement priority between Fields C and D in the joined result will be determined through the value in BindSeqNo. In this case, Field C has a value of 0 and Field D has a value of 1. This indicates that value of Field C should come before that of Field D. Thus, the result will be
- Figure 6 is a sample database definition table showing the relationships between data from different documents and the learning function of the system to aid the navigational component 30.
- the use of the definition table will now be illustrated for documents relationship and automatic learning with reference to the following sample table 2A, which illustrates one of the ways in which the table may be used.
- the values in table 2A are inserted by the system's computer program to record the activities of each user according to the target document created and the source document from which data had been exported.
- the table may be used by both the navigational component and the alert component according to the described embodiment.
- Table 2A illustrates some sample data of the document relationship table. From the data, the relationship module can form the following document relationships:
- R1 There are 2 sets of relationships, identified by R1 and R2.
- DoclD4 imports its data from DoclD3, DoclD3 imports its data from DoclD2 and DoclD2 imports its data from DoclDI .
- the system knows that DoclDI , DoclD2, DoclD3 and DoclD4 are related as they share the same relationship identifier.
- R2 consists of : DoclD ⁇ -> DoclD9
- the navigational component can deduce that there are two transactions where data from document of TypeA is exported to document of TypeB. There is one occurrence each where data from document of TypeB is exported to document of TypeC and from document of TypeC to document of TypeD. If a document of TypeA is created, the learning engine can deduce with some probability that document of TypeB will be created next.
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
SG0103000-6 | 2001-05-18 | ||
SG200130006 | 2001-05-18 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2002095626A1 true WO2002095626A1 (en) | 2002-11-28 |
Family
ID=20430887
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/SG2002/000092 WO2002095626A1 (en) | 2001-05-18 | 2002-05-15 | Integrated data sharing system |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2002095626A1 (en) |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5339434A (en) * | 1992-12-07 | 1994-08-16 | Trw Inc. | Heterogeneous data translation system |
US5557780A (en) * | 1992-04-30 | 1996-09-17 | Micron Technology, Inc. | Electronic data interchange system for managing non-standard data |
US5701423A (en) * | 1992-04-10 | 1997-12-23 | Puma Technology, Inc. | Method for mapping, translating, and dynamically reconciling data between disparate computer platforms |
US5727202A (en) * | 1995-10-18 | 1998-03-10 | Palm Computing, Inc. | Method and apparatus for synchronizing information on two different computer systems |
JPH11203329A (en) * | 1997-10-21 | 1999-07-30 | Xerox Corp | Knowledge integration system and method for providing mutual operability and synchronism of application |
US6125352A (en) * | 1996-06-28 | 2000-09-26 | Microsoft Corporation | System and method for conducting commerce over a distributed network |
WO2001018663A1 (en) * | 1999-09-09 | 2001-03-15 | Yodlee, Inc. | Automatic web form interaction proxy |
WO2002007016A1 (en) * | 2000-07-13 | 2002-01-24 | Peter Aroney | Information obtaining system |
-
2002
- 2002-05-15 WO PCT/SG2002/000092 patent/WO2002095626A1/en not_active Application Discontinuation
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5701423A (en) * | 1992-04-10 | 1997-12-23 | Puma Technology, Inc. | Method for mapping, translating, and dynamically reconciling data between disparate computer platforms |
US5557780A (en) * | 1992-04-30 | 1996-09-17 | Micron Technology, Inc. | Electronic data interchange system for managing non-standard data |
US5339434A (en) * | 1992-12-07 | 1994-08-16 | Trw Inc. | Heterogeneous data translation system |
US5727202A (en) * | 1995-10-18 | 1998-03-10 | Palm Computing, Inc. | Method and apparatus for synchronizing information on two different computer systems |
US6125352A (en) * | 1996-06-28 | 2000-09-26 | Microsoft Corporation | System and method for conducting commerce over a distributed network |
JPH11203329A (en) * | 1997-10-21 | 1999-07-30 | Xerox Corp | Knowledge integration system and method for providing mutual operability and synchronism of application |
WO2001018663A1 (en) * | 1999-09-09 | 2001-03-15 | Yodlee, Inc. | Automatic web form interaction proxy |
WO2002007016A1 (en) * | 2000-07-13 | 2002-01-24 | Peter Aroney | Information obtaining system |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11113294B1 (en) | Recommending query templates during query formation | |
US11269871B1 (en) | Displaying multiple editable queries in a graphical user interface | |
US11263268B1 (en) | Recommending query parameters based on the results of automatically generated queries | |
US20230031327A1 (en) | Recommending Query Parameters Based on Tenant Information | |
US7483879B2 (en) | System and method for accessing non-compatible content repositories | |
US7233940B2 (en) | System for processing at least partially structured data | |
RU2358318C2 (en) | Method, device and user interface for monitoring electronic mail messages and warning messages | |
JP5710851B2 (en) | System and method for impact analysis | |
US6510457B1 (en) | Data analysis method and apparatus for data mining | |
JP3851493B2 (en) | Database search method, database search system, and computer-readable recording medium recording database search program | |
US7472140B2 (en) | Label-aware index for efficient queries in a versioning system | |
US20050065911A1 (en) | Automatic database statistics creation | |
US8438141B2 (en) | System and method for providing secure access to data with user defined table functions | |
US20010003455A1 (en) | Method, system and graphic user interface for entering and editing filter conditions for filtering a database | |
WO1998030962A2 (en) | Method for content-based dynamic formatting for interoperation of computing and edi systems | |
JP2014222538A (en) | System and method for scoping searches using index keys | |
KR20060046366A (en) | Method, system, and apparatus for discovering and connecting to data sources | |
US8849848B2 (en) | Associating security trimmers with documents in an enterprise search system | |
US20060174131A1 (en) | Method and system for providing access to computer resources that utilize distinct protocols for receiving security information and providing access based on received security information | |
US20080178107A1 (en) | System and method for dynamically presenting a directory tree | |
US11636128B1 (en) | Displaying query results from a previous query when accessing a panel | |
JP2006085717A (en) | Durable storage of .net data type and instance | |
US11644955B1 (en) | Assigning a global parameter to queries in a graphical user interface | |
US11573955B1 (en) | Data-determinant query terms | |
WO2008061254A1 (en) | Storing, maintaining and locating information |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG US UZ VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase |
Ref country code: JP |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: JP |