CN109564541B - Data exchange system, data exchange method, and data exchange program - Google Patents

Data exchange system, data exchange method, and data exchange program Download PDF

Info

Publication number
CN109564541B
CN109564541B CN201780047417.5A CN201780047417A CN109564541B CN 109564541 B CN109564541 B CN 109564541B CN 201780047417 A CN201780047417 A CN 201780047417A CN 109564541 B CN109564541 B CN 109564541B
Authority
CN
China
Prior art keywords
database
data
external
code
conversion
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.)
Active
Application number
CN201780047417.5A
Other languages
Chinese (zh)
Other versions
CN109564541A (en
Inventor
西村真
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Toshin System Ltd
Original Assignee
Toshin System Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Toshin System Ltd filed Critical Toshin System Ltd
Publication of CN109564541A publication Critical patent/CN109564541A/en
Application granted granted Critical
Publication of CN109564541B publication Critical patent/CN109564541B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The present invention provides a data exchange system, a data exchange method, and a data exchange program, which can realize a transparent data exchange even between databases managing data having different granularities by using a database having a hierarchical structure for intermediation. The data exchange system (1) comprises: the system comprises a base database (120), a conversion database (105), a base code conversion part (110), a code existence judging part (115), and a data conversion part (125), wherein the code existence judging part (115) judges whether standard data is stored in the conversion database (105) in association with other database identifiers, the data conversion part (125) converts the standard data into external identification codes when the base code corresponding to the standard data is stored in the conversion database in association with other database identifiers, and converts the standard data into external identification codes which are stored in the conversion database (105) in association with the base code of a hierarchical structure stored in the base database (120) and the other database identifiers when the base code is not stored.

Description

Data exchange system, data exchange method, and data exchange program
Technical Field
The present invention relates to a data exchange system, a data exchange method, and a data exchange program. The present invention relates to a data exchange system, a data exchange method, and a data exchange program for exchanging data between arbitrary systems using a database having a hierarchical structure.
Background
When a database process is to be performed on a collection of a plurality of elements and the database process is to be managed, an identifier for identifying the elements is generally given. For example, a commodity code is assigned to a commodity handled by a certain company. Based on the "commodity code", a commercial transaction is conducted. Here, if the other party of the transaction imparts another "commodity code" to the same component, no data exchange can be performed. In order to solve such problems, standard codes, unicode, or the like have been developed.
However, there are cases where these standard codes or unicode codes cannot be solved. This refers to a case where a plurality of elements are classified according to a complex hierarchical structure, and the classification element (hereinafter referred to as "note") of each hierarchy itself has a meaning of a valid identifier. For example, a plurality of types of "turnips" (for example, "gate-on turnips") are registered by "standard commodity codes for vegetables and fruits" developed by food circulation structure improvement promoting institutions, but "turnips" which should be "classification concepts" of these are registered as items. The reason for this is that: "radish" is also commonly used as a stand-alone element concept. In the "vegetable and fruit commodity codes", no hierarchical relationship is defined between these codes. Thus, even when the "standard commodity code for vegetables and fruits" is to be used, data cannot be exchanged between an operator who handles a certain "radish" as "radish" and an operator who handles a "gate keeper radish". That is, in a case where a plurality of databases for processing elements to be represented by a hierarchical structure are managed so as to be located at different levels (hereinafter, this is referred to as "different granularity" of data), the corresponding databases cannot realize appropriate data exchange by the concept of standard codes or unified codes in the past.
That is, in the case where elements to be located at different levels in a hierarchical structure are to be managed by corresponding databases among a plurality of databases processing elements that should be represented by the hierarchical structure (hereinafter, this is referred to as "different granularity" of data), appropriate data exchange cannot be realized by the concept of past standard codes or unified codes.
In the past, there has been known an electronic commerce transaction mediating method as mediating commercial transactions between a plurality of suppliers of products or services and buyers via a digital data communication network: (a) Standardized processing is performed on attribute information concerning the same product or service supplied by a plurality of suppliers, and these attribute information are compared, and viewing data that can be viewed and non-viewing data including transaction conditions set for each combination of the suppliers and the buyers are stored in advance as a database of the intermediary; (b) The intermediary party converts the transaction content of the product or service of the supplier which is presented to the purchaser into a classification code system of the purchaser through codes, and presents the classification code system to the purchaser; (c) The purchaser selecting a product or service desired to be purchased, and conducting a transaction request for the selected product or service with respect to the intermediary; (d) The mediator reads transaction conditions different for each of the purchasers of the product or service selected by the purchaser from the non-viewing data, and gives a price to the purchaser; (e) Determining the supplier by the purchaser based on the quote prompted by step (d); (f) The mediating party converts the transaction condition determined in the step (e) into a corresponding classification code system of the purchaser and the donor by the code, and performs an e-commerce transaction mediating method of ordering the purchase acceptance order in place of the purchaser and the donor (for example, refer to patent document 1). According to the e-commerce transaction mediating method described in patent document 1, transactions of specific transaction conditions of each transaction party can be performed without any obstacle caused by a difference in classification code system between a purchaser and a supplier.
Prior art literature
Patent literature
Patent document 1: JP 2002-230342A
Disclosure of Invention
Problems to be solved by the invention
The e-commerce transaction mediating method described in patent document 1 uses a standard code system and an absorption code system that are 1-to-1-corresponding to each other by using a code system on the service provider side and a code system on the purchaser side. However, in this method, data cannot be exchanged between databases that manage data having different granularities as described above.
Accordingly, an object of the present invention is to provide a data exchange system, a data exchange method, and a data exchange program capable of realizing a transparent data exchange by using a database having a hierarchical structure as an intermediary.
Means for solving the problems
In order to achieve the above object, the present invention provides a data exchange system for implementing a transmission data exchange between external databases by using databases having a hierarchical structure as intermediaries, comprising: a base database storing hierarchical structure information represented by a hierarchical structure of a base code of the identification data; a conversion database for storing an external identification code for identifying external data stored in the external database in association with a database identifier for identifying the external database and a base code stored in the base database; a base code conversion section that converts an external identification code that identifies an external data from an external database into standard data associated with a base code stored in the conversion database in association with a database identifier of the external database; a code presence judging section that judges whether or not the base code corresponding to the standard data is stored in the conversion database in association with another database identifier that identifies another external database; and a data conversion unit which converts the standard data into an external identification code stored in the conversion database in association with the base code corresponding to the standard data and the other database identifier when the base code corresponding to the standard data is stored in the conversion database in association with the other database identifier, and converts the standard data into an external identification code stored in the conversion database in association with the base code corresponding to the standard data and the other database identifier when the base code corresponding to the standard data is not stored in the conversion database in association with the other database identifier, wherein the external identification code is traced back to an upper classification position from a classification position of the base code corresponding to the standard data in a hierarchical structure stored in the base database, and is lowered to a lower classification position or stored in association with the base code and the other database identifier of the classification position in the same column as the classification position.
In the data exchange system, the hierarchical structure information may be information represented by a hierarchical structure of a base code configured to include at least any one of a base code that identifies data of a higher concept of predetermined data, a base data that identifies data of a lower concept of predetermined data, and a base code that identifies predetermined data.
The data exchange system may further include an information adding unit that adds additional information related to one external data to the external identification code converted by the data conversion unit.
The data exchange system may further include a code attaching unit that attaches an external identification code of one external data received from one external database to the external identification code converted by the data conversion unit.
In the above data exchange system, the basic code conversion unit may receive one external data from one external database together with another database identifier and another external identification code for identifying another external data of another database, and may add a set of the other database identifier and the other external identification code to the standard data, or may not form the standard data, and the code presence determination unit may determine whether or not the other external identification code is stored in the conversion database in association with the other database identifier, and the data conversion unit may treat the other external identification code as the converted external identification code.
In the data exchange system, the conversion database may store a group of other external identification codes corresponding to one external identification code and storing other database identifiers and other external data in the other database, the basic code conversion unit may refer to the conversion database, and the group may be added to the standard data or the standard data may not be formed, and the code presence determination unit may determine whether or not the other external identification codes are stored in the conversion database in association with the other database identifiers, and the data conversion unit may treat the other external identification codes as converted external identification codes.
In the above data exchange system, the conversion database may store a set of one database identifier and one external identification code corresponding to another external identification code for identifying another external data of another database, and the data conversion unit may search the conversion database based on the database identifier and the external identification code stored in the standard data before the code presence determination unit determines that the external identification code is present, and treat the external identification code as the converted external identification code when the database identifier stored in the standard data, the database identifier corresponding to the external identification code, and the external identification code are stored in the conversion database.
In the above data exchange system, when the base code corresponding to one external data is directly received from one external database, the base code conversion unit does not refer to the conversion database, and the code presence determination unit determines that the received base code is directly used.
In order to achieve the above object, the present invention provides a data exchange system for implementing data exchange between external databases by using databases having a hierarchical structure as intermediaries, the data exchange system comprising: an input data processing unit that processes external data stored in an external database; an output data processing unit that processes data supplied to other external databases according to processing in the input data processing unit, the input data processing unit including: a base database storing hierarchical structure information represented by a hierarchical structure of a base code of the identification data; a conversion database for storing an external identification code for identifying external data in association with a database identifier for identifying the external database and a base code stored in the base database; and a basic code conversion unit for converting an external identification code for identifying one external data from one external database into standard data, the standard data being associated with a basic code stored in the conversion database in association with a database identifier of one external database, the output data processing unit including a data conversion unit for converting the standard data into an external identification code when the basic code corresponding to the standard data is stored in the conversion database in association with another database identifier for identifying another external database, the external identification code being stored in the conversion database in association with the basic code corresponding to the standard data and another database identifier, and converting the standard data into an external identification code when the basic code corresponding to the standard data is not stored in the conversion database in association with another database identifier, the external identification code being lowered from a classification position of the basic code corresponding to the standard data to a classification position of the upper bit in the hierarchy structure stored in the basic database, or lowered to a classification position of the basic code corresponding to the classification position of the database and the conversion position in association with the other database.
In order to achieve the above object, the present invention provides a data exchange method of a data exchange system for implementing transmission data exchange between external databases by using databases having a hierarchical structure as intermediaries, the data exchange system comprising: a base database storing hierarchical structure information represented by a hierarchical structure of a base code of the identification data; a conversion database for storing an external identification code for identifying external data stored in an external database in association with a database identifier for identifying the external database and a base code stored in a base database, the data exchange method of the data exchange system comprising: a basic code conversion step of converting an external identification code that identifies an external data from an external database into standard data associated with a basic code stored in the conversion database in association with a database identifier of the external database; a code presence judging step of judging whether or not the base code corresponding to the standard data is stored in the conversion database in association with another database identifier that identifies another external database; and a data conversion step of converting the standard data into an external identification code stored in the conversion database in association with the base code corresponding to the standard data and the other database identifier when the base code corresponding to the standard data is stored in the conversion database in association with the other database identifier, and converting the standard data into an external identification code stored in the conversion database in association with the base code corresponding to the standard data and the other database identifier when the base code corresponding to the standard data is not stored in the conversion database in association with the other database identifier, wherein the external identification code is traced back from the classification position of the base code corresponding to the standard data to the upper classification position in the hierarchical structure stored in the base database, and is lowered to the lower classification position, or the base code of the classification position in the same column as the classification position and the other database identifier are stored in association with the conversion database.
In order to achieve the above object, the present invention provides a data exchange program for a data exchange system for implementing transmission data exchange between external databases by using databases having a hierarchical structure as intermediaries, the data exchange system comprising: a base database storing hierarchical structure information represented by a hierarchical structure of a base code of the identification data; a conversion database for storing an external identification code for identifying external data stored in an external database in association with a database identifier for identifying the external database and a base code stored in a base database, in a computer, implementing: a base code conversion function in which an external identification code that identifies an external data from an external database is converted into standard data associated with a base code stored in the conversion database in association with a database identifier of the external database; a code presence judging function of judging whether or not the base code corresponding to the standard data is stored in the conversion database in association with another database identifier that identifies another external database; a data conversion function of converting the standard data into an external identification code stored in the conversion database in association with the base code corresponding to the standard data and the other database identifier, when the base code corresponding to the standard data is stored in the conversion database in association with the other database identifier; when the base code corresponding to the standard data is not stored in the conversion database in association with the other database identifier, the standard data is converted into an external identification code which is stored in the conversion database in association with the base code and other database identifier in the hierarchical structure stored in the base database, and the external identification code is traced back from the classification position of the base code corresponding to the standard data to the upper classification position, descends to the lower classification position, or is stored in association with the base code of the classification position in the same column as the classification position.
ADVANTAGEOUS EFFECTS OF INVENTION
According to the data exchange system, the data exchange method, and the data exchange program of the present invention, a data exchange system, a data exchange method, and a data exchange program that realize transmission data exchange by using a database having a hierarchical structure as an intermediary can be provided.
Drawings
Fig. 1 is a schematic diagram of a data exchange system according to the present embodiment;
fig. 2 is a functional block diagram of the data exchange system according to the present embodiment;
fig. 3 is a data structure diagram of the conversion database of the present embodiment;
fig. 4 is a data structure diagram of the base database of the present embodiment;
fig. 5 is a functional block diagram showing another embodiment of the data exchange system according to the present embodiment;
fig. 6 is a diagram showing an example of the conversion database according to the present embodiment;
fig. 7 is a diagram showing an example of the base database according to the present embodiment;
fig. 8 is a flowchart of the processing of the data exchange system of the present embodiment;
FIG. 9 is a diagram of a base database of another embodiment;
FIG. 10 is a diagram of data of a conversion database of yet another embodiment;
fig. 11 is a conceptual diagram of a flow of data exchange in a data exchange system according to another embodiment;
Fig. 12 is a hardware configuration diagram of the data exchange system according to the present embodiment.
Detailed Description
Embodiment(s)
Fig. 1 schematically shows a data exchange system according to an embodiment of the present invention.
[ outline of data exchange System 1 ]
In the case of completely standardizing products one by one like industrial products, it is easy to associate a single identifier with a single variety. On the other hand, in the case of sorting elements having various kinds of attributes, such as classification of animals and plants, classification of a hierarchy having a tree structure is required. In contrast to such elements, if identifiers are assigned by a common one-dimensional structure, problems arise. For example, even when a certain database uses the item of "dog" as an element, there are cases where "dog" is classified into "bomex" and "autumn dog" in other databases, and the elements are "bomex" and "cola". There are substantial difficulties associated with the exchange of data between these databases.
Regarding the exchange of data between these different databases, what has been done in the past has been a solution by determining a unified "standard code" or "unified code" and advancing the way it is used. However, when standard codes and unified codes are used, various problems are involved. First, when each operator uses a database by using a separate code system, a great difficulty is associated with the change of the code system. Even if the standard code and the unified code are used in the original place, the present invention is not suitable for the use of the company. For example, there are operators who have to require classification up to "bomek" and "autumn dog", and on the other hand, there are operators who are sufficient according to classification of "dog". In addition, there will be operators who must require both. Typically, the "granularity" of the information that must be required is different, respectively, along with the operator.
In addition, even if the code system is not changed to the standard code or the unified code, the user still searches for the use of the standard code or the unified code when exchanging data with the outside. However, in this case as well, the problem of the case unsuitable for the operation of each operator is not changed, and the intrinsic difficulty in the case of managing the data having the ambiguous attribute of the tree structure cannot be solved.
That is, in the case of managing elements that must require such a hierarchy of attributes, in the case of standard code and unified code methods, the problem of "granularity" of information that must be required by each operator being different cannot be solved. This causes an essential problem in the context of data exchange. For example, even in a JAN code that specifically identifies a product, a code cannot be assigned to a product that cannot identify the "color" of the product, and therefore, the product cannot be ordered by specifying the color. In addition, in some products, in order to encode the product so as to include the color, there is a problem that the order of the product is not possible, for example, because the color is all the same.
The data exchange system 1 according to the present embodiment is a system developed by the present inventors to solve the problem, and is a system in which, when a database having a hierarchical structure that forms the basis of data exchange is used, the data exchange is freely performed while absorbing the problem of granularity without changing the individual code system used by each operator. That is, the data exchange system 1 is a data exchange system in which transmission data exchange is realized even when a plurality of databases that process elements that are originally represented by a hierarchical structure are managed so that the corresponding databases are located at different levels of the hierarchical structure.
Specifically, the data exchange system 1 of the present invention is a data exchange system in which data exchange is performed between respective databases of a plurality of databases (for example, the external database 20, the external database 22, and the external database 24) storing data of mutually different code systems. In particular, even when a plurality of databases are processed for elements that are originally represented by a hierarchical structure, and the corresponding databases manage elements that are to be located at different levels of the hierarchical structure, the data exchange is realized. In the present embodiment, among a plurality of databases that process elements that are originally represented by a hierarchical structure, there is a case where states of elements that should be located at different levels of the hierarchical structure are referred to as "different granularities". That is, the data exchange system 1 is a system in which appropriate data exchange is performed between one database storing one data (or data group) of one code system and other databases storing other data (or other data group) of other code systems different from the one code system even in the case where the granularity of the data is different.
The data exchange system 1 performs data exchange in which the attributes constituting the reference are various, and the definition of the attributes includes ambiguous data. For example, the data exchange system 1 is a data exchange system for classifying animal plants, for crops (for example, varieties of crops), for fresh foods (including vegetables and fruits, aquatic products, and the like), for clothing, for foods (including processed foods), and the like.
For example, a case will be described in which one external database (hereinafter, simply referred to as external database 20) supplies predetermined external data (i.e., data stored in external database 20) to other external databases (hereinafter, simply referred to as external database 22). Here, as an example, an example will be described in which the external database 20 supplies information for ordering a predetermined commodity to the external database 22.
In addition, the external databases and the data exchange system 1 are communicably linked to each other via a communication network 5 such as the internet. The external databases include servers of retailers, wholesalers, intermediaries, and public institutions such as enterprises, stores, restaurants, etc. that afford sales of predetermined products and commodities, and services, education institutions such as universities, and administrative institutions, for example. In addition, the server may also have a part of the function and structure of the data exchange system 1.
First, the external database 20 is used to store external data in association with an external identification code that identifies the external data. Specifically, the external database 20 is used to store external data in association with an external identification code that identifies the content and/or attributes of the external data. For example, the external database 20 stores, as external data, a plurality of types of radishes classified by "radishes", which are the lower concepts of "radishes", in association with an external identification code that specifically identifies the external data. As an example, the external database 20 stores external data "guard turnip" and external identification code "a 11 'associating the external data' radish with soil 'with the external identification code' a 12 ' in association, they are stored.
On the other hand, the external database 22 stores external data in the same manner as the external database 20 according to a code hierarchy different from that of the external database 20. As an example, the external database 22 stores, as external data, a plurality of root crops classified by "root crops" as the lower concept of "root crops" in association with an external identification code that specifically identifies the external data. As an example, the external database 22 will have external data "radish "with external identification code" a 1 ' associating the external data "root plant" with the external identification code "a 2 ' associated, they are stored.
In addition, the data exchange system 1 includes a base database 120 storing hierarchical structure information represented by a hierarchical structure of base codes identifying data and/or attributes of data. For example, "vegetables and fruits" are the generic concepts of "vegetables" and "fruits" and the like. In addition, the lower concept of "vegetables" includes "root crops" and "leaf vegetables". In addition, the lower concept of "root crops" includes "radishes" and "root plants". In addition, the lower concept of "radish" includes "radish with soil" and "radish with gate" and the like. The base database 120 stores information indicating attributes of such commodities or products as hierarchical structure information forming a hierarchical structure that is stored in multiple levels and includes a hierarchy of attributes of the lower-level concepts among the attributes of the upper-level concepts.
As one example, the base database 120 stores a base code "a" of the identification data "root crop", a base code "B" of the identification data "leaf vegetables", and the like in association with the base code of the identification data "vegetables". Next, the base database 120 stores the base code "a" of the identification data "radish" in association with the base code "A 1 "and a base code" a "identifying the data" root plant " 2 "etc. In addition, the base database 120 and the base code "a 1 Basic code "a" of "associated with" guard radish "identification data 11 Basic code "a" of "radish with soil" with identification data 12 "etc. are stored in the lower hierarchical level.
That is, the base database 120 stores, as the base code having the base code that identifies the data "vegetable", the base code having the hierarchical structure constituted by the base code corresponding to the upper concept to the base code corresponding to the lower concept; basic codes for identifying a plurality of data (e.g., root crops, leaf vegetables, etc.) contained in the lower concept of the data "vegetable"; basic codes for identifying a plurality of data (for example, respective products of radish with soil, gate-on radish, etc.) included in the lower concept of "root crop" and corresponding data among the plurality of data included in the lower concept of "leaf vegetable"; and a base code identifying corresponding data of the plurality of data contained in the lower concept of the respective product (e.g., the ground radish, the gate-on radish, etc.). Then, when the predetermined base code is included, the data exchange system 1 searches for the base code of the upper concept or the base code of the lower concept of the predetermined base code by tracking the hierarchical structure represented by the hierarchical structure information. In particular, in the data exchange system 1, the base code corresponding to the upper concept of the base code can be obtained by tracing back from the classification position of the base code of the lower concept to the upper one.
In addition, the data exchange system 1 includes a conversion database 105, and the conversion database 105 stores in advance the external identification codes of the respective external databases in association with the database identifier of the respective external databases that specifically identifies the plurality of external databases and the base code stored in the base database 120. As an example, the database 105 is transformed to associate the external identification code "a" of the identification data "gate keeper" with the database identifier of the external database 20 11 ' and base code "a" stored in base database 120 11 "stores it in the manner of" a "table. Likewise, the database 105 is transformed to correlate the external identification code "a" of the identification data "radish with soil" with the database identifier of the external database 20 12 ' and base code "a" stored in base database 120 12 "stores it in the manner of" a "table. In addition, the database 105 is converted to correlate the external identification code "a" of the identification data "radish with soil" with the database identifier of the external database 22 1 ' and base code "a" stored in base database 120 1 "store it in the manner of a" table ".
Here, an example in which the external database 20 is ordered with "radish with soil" will be described. For example, external data as other external databases The library 22 does not store data related to "radish with soil". First, the external database 20 stores the external identification code of "radish with soil" (for example, the external identification code "a" of 12 ' ") to the data exchange system 1. In addition, the external database 20 may also supply the external identification code and/or the external data to the data exchange system 1 together with information specifying the external database 22 (i.e., a database identifier of the external database 22).
The data exchange system 1 retrieves the conversion database 105 using the external identification code received from the external database 20. That is, the data exchange system 1 retrieves and recognizes the database identifier and the external identification code (for example, "a" of the external database 20 12 '') is stored in association with the base code in the conversion database 105, and the external identification code is converted into standard data (for example, standard data "a" using the base code extracted by the retrieval 12 "). Specifically, the data exchange system 1 uses data represented by the base code as standard data. The standard data is data associated with the external identification code, such as a base code, an external database identifier, and/or external data. The standard data is freely referred to for accessing the database of the data exchange system 1.
Next, the data exchange system 1 determines whether or not to store the base code corresponding to the standard data in the information stored in the conversion database 105 in association with the database identifier of any other external database. For example, the data exchange system 1 determines whether or not the conversion database 105 stores the base code corresponding to the standard data in association with the database identifier of the external database 22.
In this case, the base code corresponding to the standard data is stored in the conversion database 105 without being associated with the database identifier of the external database 22. Then, the data exchange system 1 retrieves the base database 120, converts the standard data into an external identification code stored in the conversion database 105 in association with the database identifier of the external database 22 and any base code in the hierarchical structure including the base code corresponding to the standard data.
For example, in the above example, the base database 120 is included as the base code "a" in the hierarchical structure 12 Basic code "a" of "upper concept 1 ". In addition, the conversion database 105 is used for the database identifier and the base code "a" with the external database 22 1 "associatively storing external identification code" a 1 '". The data exchange system 1 then exchanges the standard data "a" with the slave data 12 "consistent base code" a 12 In the classification position of "tracking hierarchy (for example, tracing the upper level of hierarchy), the basic code" a "is extracted 1 ". The data exchange system 1 then exchanges the standard data "a 12 "convert to and extracted base code" a 1 "external identification code" a stored in conversion database 105 in association with the database identifier of external database 22 1 ’”。
That is, the data exchange system 1 searches the hierarchical structure of the base database 120 (i.e., searches in the upper direction of the classification position) by tracing back the direction of the upper concept when the base code corresponding to the standard data is not stored in the conversion database 105 in association with the database identifier of the external database 22. Next, the data exchange system 1 converts the basic code obtained by the search into an external identification code stored in the conversion database 105 in association with the basic code obtained by the search of the database identifier of the external database 22. Then, the external identification code obtained by the conversion and/or external data associated with the external identification code are supplied to the external database 22.
In addition, when it is determined that the basic data corresponding to the standard data is stored in the conversion database 105, the data exchange system 1 supplies the external identification code stored in the conversion database 105 in association with the database identifier of the external database 22 and the basic code corresponding to the standard data (i.e., the basic code stored in the conversion database 105) and/or the external data associated with the external identification code to the external database 22.
Thus, according to the data exchange system 1 of the present embodiment, when a plurality of external databases store data in mutually different code systems, even when no database is constructed in which the code system of one external database corresponds to the code system 1 to 1 of another external database, predetermined data can be smoothly supplied from one external database to another external database. In addition, according to the data exchange system 1, even when the granularity of data received by the plurality of external databases is different from each other, appropriate data exchange can be performed from one external database to another external database. That is, according to the data exchange system 1, data exchange from one external database to a plurality of external databases can be flexibly performed.
The data exchange system 1 may further include an attribute storage unit that stores information related to data corresponding to the base code (for example, information related to an attribute of a predetermined commodity) in association with the base code as text data, numeric data, graphic data, and/or symbol data.
The communication network 5 is a communication network such as a mobile phone network and/or the internet. The communication network 5 may also include a communication network of a wired LAN, a wireless LAN, and the like. In addition, each of the plurality of external databases may be provided not only in a prescribed database apparatus but also in an information processing terminal such as a personal computer, a notebook computer, a tablet PC, or the like. In addition, the data exchange system 1 may obtain various data from outside via a recording medium such as a magnetic recording medium, an optical recording medium, and/or a semiconductor recording medium when the communication network 5 is not present.
The data processed by the data exchange system 1 is data which can be associated with a predetermined code, and is data used in a database including various data. In particular, data is data related to items that are not limited to items that are completely standardized by individual products (i.e., items whose attributes have ambiguity), and is data that can be classified according to a hierarchical structure (i.e., tree structure). In addition, the data may be data related to products and/or commodities circulating in a predetermined market, or data used between organizations (non-profit, profit-related) exchanging predetermined information. The data is, for example, data related to classification of animal plants, data related to crops, data related to fresh foods, data related to clothing, or data related to foods and the like. As an example, the data is data on fresh foods and the like which vary with date, such as manufacturers, varieties/production places, cultivation methods, seasons, sizes, and/or grades. In addition, the fresh food includes vegetables and fruits, aquatic products, etc.
[ details of the construction of the data exchange System 1 ]
Fig. 2 shows an example of the functional configuration of the data exchange system according to the present embodiment. In addition, the data exchange system 1 of the present embodiment may be communicably linked with a plurality of external databases, but for simplicity of explanation, in the following, an example will be described in which the data exchange system 1 and 1 external databases are communicably linked via the communication network 5 as a principle.
The data exchange system 1 includes: a data input unit 100, the data input unit 100 receiving input of data from the outside; a conversion database 105 for storing an external identification code in association with a database identifier and a base code identifying the external database; a base code conversion section 110, the base code conversion section 110 converting an external identification code received from an external database into standard data; a code presence judging section 115, the code presence judging section 115 judging whether or not the base code corresponding to the standard data is stored in the conversion database 105 in association with another database identifier; a base database 120, the base database 120 storing hierarchical structure information represented by a hierarchical structure of base codes; a data conversion section 125, the data conversion section 125 converting the standard data into an external identification code; an accompanying unit 130, wherein the accompanying unit 130 attaches the external identification code with prescribed data; a correspondence updating unit 150, the correspondence updating unit 150 updating the data stored in the conversion database 105; an information updating unit 155, wherein the information updating unit 155 updates information stored in the base database 120. Each component element included in the data exchange system 1 may also have some or all of the functions of other component elements.
(data input section 100)
The data input section 100 receives input of other database identifiers identifying other databases as one external data and/or as a supplier of one external data from one external database. In addition, the data input unit 100 receives information or instructions to update the content of the data stored in the conversion database 105 or information or instructions to update the content of the information stored in the base database 120. Further, the data input part 100 receives additional information related to one external data and/or input of one external identification code identifying one external data. In addition, the external data may also store a plurality of pieces of information.
When receiving an input of one external data, the data input unit 100 may directly receive an input of a base code corresponding to the one external data. In this case, the base code conversion unit 110 directly supplies the base code to the code presence determination unit 115 without referring to the conversion database 105. In this case, the base code conversion unit 110 may determine the presence or absence of the base code and suitability thereof, and perform predetermined error processing. In this case, the external database for supplying predetermined data to the data exchange system 1 is not required to store the external identification code of the external database in the conversion database 105. In this case, an external system having an external database has a predetermined data conversion function.
The data input section 100 supplies one external data received from one external database, other database identifier, and/or one external identification code to the base code conversion section 110. In addition, in the one external data, a database identifier of the one external database is included or associated with the one external data. In addition, an external data may also include a plurality of different information. The data input unit 100 supplies information or instructions for updating the content of the data stored in the conversion database 105 to the correspondence relation updating unit 150. The data input unit 100 supplies information or instructions for updating the content of the information stored in the base database 120 to the information updating unit 155. In addition, the data input section 100 supplies additional information and/or an external identification code to the accompanying unit 130.
(conversion database 105)
Fig. 3 shows an example of a data structure of a conversion database according to an embodiment of the present invention.
The conversion database 105 is used to store an external identification code that identifies external data of an external database storing external data of a predetermined code hierarchy in association with a database identifier that identifies the external database and any base code stored in the base database 120. As shown in fig. 3, the conversion database 105 is used to store an external identification code that identifies an attribute, and/or a concept, etc. of external data stored in an external database in association with a data identifier that specifically identifies the external database, and a base code corresponding to the external identification code. Here, the base code stored in the conversion database 105 is the same as the base code stored in the base database 120. In this case, the conversion database 105 fixedly associates the external identification code with the database identifier and the prescribed base code.
For example, the conversion database 105 stores, as a base code associated with an external identification code, a higher-level concept or a lower-level concept of external data corresponding to the external identification code, or a base code associated with data corresponding to the same concept. Preferably, the conversion database 105 stores, as a base code associated with external data corresponding to the external identification code, at least a base code of the same or the same kind as the external data or a base code of data corresponding to a higher-order concept of the external data. The conversion database 105 supplies the stored data to the corresponding portions of the base code conversion section 110, the code presence determination section 115, and/or the data conversion section 125 in correspondence with the start-up of the base code conversion section 110, the code presence determination section 115, and/or the data conversion section 125.
In addition, the conversion database 105 may store the external identification code and the base code in a relation of n to m (where n and m represent integers of 1 or more, respectively). For example, the conversion database 105 may store a plurality of base codes in such a manner that they are associated with one external identification code (in the following, the case of "multiple registration" with an external identification code). As an example, consider a case where an external database stores information of "green turnip" and information of "gate-on turnip" as external data, and information of "turnip" is not stored. In addition, when one external database receives information of radishes other than the information of "green turnips" and the information of "gate-on radishes", for example, information of "turnips with soil", it is required to convert the information into information of "green turnips". In this case, the conversion database 105 may associate not only the basic code corresponding to "green-headed radish" but also the basic code corresponding to "earthed radish" with the external identification code corresponding to the information corresponding to "green-headed radish". In addition, by associating a base code (for example, a base code corresponding to "radish") of one upper level of the hierarchical structure stored in the base database 120 with a base code corresponding to "green-headed radish", a base code corresponding to "green-headed radish" can be employed for all of other kinds of "radishes".
Here, when a plurality of basic codes are associated with 1 external identification code, the correspondence between the external identification code stored in the conversion database 105 and one basic code may be associated with information indicating "master registration" in preference to other correspondence. Since the basic code conversion section 110 preferentially performs conversion processing using the external identification code and the basic code associated with the information indicating "main registration", a stable conversion processing result can be obtained.
The conversion database 105 may also store a plurality of external identification codes in association with 1 base code (hereinafter, a case of "multiple registration" of base codes). For example, an external database stores information of "green turnip" and information of "gate keeper turnip" as external data, and on the other hand, all of these information are associated with a base code corresponding to "turnip". Here, in this case, original information (for example, information of the "green head" portion of the "green head radish") is lost. Further, since such a function can be realized by the search of the follow-up hierarchy, the data exchange system 1 can prohibit the multiple registration of the base code of the conversion database 105.
Here, in the case where the conversion database 105 registers the base code a plurality of times, information indicating "main registration" in preference to other correspondence may be associated with the correspondence between the base code stored in the conversion database 105 and one external identification code. Since the base code conversion section 110 preferentially performs conversion processing using the base code associated with the information indicating "main registration" and the external identification code, a stable conversion processing result can be obtained.
The conversion database 105 may be controlled by artificial intelligence, and the external identification code may be stored so as to be dynamically associated with the database identifier and any base code stored in the database 120. In this case, the conversion database 105 may have a function of dynamically associating an external identification code with a database identifier and/or a base code. The transformation database 105 may update the association at any time through learning of artificial intelligence. The artificial intelligence may also learn from information provided from an external server or the like via the communication network 5. The transformation database 105 may store learning results of artificial intelligence, which may be updated at any time.
(basic code conversion section 110)
The basic code conversion section 110 converts the external identification code into standard data based on the external data, the external identification code, and/or the database identifier received from the data input section 100. That is, the base code conversion section 110 converts one external identification code into standard data associated with the base code based on the base code and one external identification code stored in the conversion database 105 in association with one external identification code that identifies one external data from one external database. Specifically, the base code conversion section 110 receives one external data and an external identification code identifying one external data from one external database. In addition, the base code conversion section 110 may also receive external data together with an external identification code together with other database identifiers that identify other external databases that are suppliers of one external data. Further, the base code conversion section 110 converts one external identification code into standard data, which is standard data associated with one external identification code and one external data stored in the conversion database 105 in association with a database identifier of one external database, with reference to the conversion database 105. For example, the base code conversion unit 110 extracts the base code stored in the conversion database 105, and converts the extracted base code and data obtained by associating one external data with one external identification code as standard data, thereby converting the external identification code into standard data. The base code conversion section 110 supplies the standard data to the code presence determination section 115.
The basic code conversion unit 110 may not convert the external identification code into the standard data when receiving one external data together with another external identification code for identifying another external data of another database from one external database. When the external identification code is not converted into standard data, the base code conversion unit 110 supplies information indicating that the external identification code is not converted and the external identification code to the code presence determination unit 115. In addition, when the external identification code is not converted into the standard data, the base code conversion unit 110 does not refer to the external identification code received from one external database in a database different from the other databases.
(code presence judging section 115)
The code presence determination unit 115 refers to the conversion database 105, and determines whether or not the base data corresponding to the standard data received from the base code conversion unit 110 is stored in the column of the base code of the conversion database 105 in association with another database identifier. The conversion database 105 supplies information indicating the determination result to the data conversion unit 125. When receiving information indicating that the external identification code has not been converted into the standard data from the base code conversion unit 110, the code presence determination unit 115 does not perform a determination process of whether or not the base code corresponding to the standard data is stored in the conversion database 105 in association with another database identifier. The code presence judging section 115 supplies information indicating that the judgment process is not performed and the external identification code received from the base code converting section 110 to the data converting section 125.
(base database 120)
Fig. 4 shows an example of a data structure of a base database according to an embodiment of the present invention.
The base database 120 stores hierarchical structure information represented by a hierarchical structure of base codes of identification data. Specifically, the base database 120 stores hierarchical structure information represented by a hierarchical structure of base codes including at least any one of base codes of data identifying the content of predetermined data, attributes of upper concepts, etc., base codes of data identifying attributes of lower concepts of predetermined data, etc., and base codes identifying predetermined data itself. The hierarchical structure is a structure in which a plurality of predetermined data are sequentially superimposed on data of a higher-level concept from data of a lower-level concept to form a whole (hereinafter, the depth of the hierarchical structure is a hierarchy of n levels (where n > 1)).
For example, examples of the case where the 1 st data, the 2 nd data, the 3 rd data, the 4 th data, and the 5 th data are different from each other, and the data of the lower concept is expressed in the order of the 1 st data, the 2 nd data, the 3 rd data, the 4 th data, and the 5 th data (as an example, the 1 st data is "vegetables", the 2 nd data is "root crops", the 3 rd data is "radishes", the 4 th data is "radishes with soil", and the 5 th data is "radishes with soil" which is a limited place of production) are given.
In this case, as shown in FIG. 4, in the hierarchical structure, the base code "A" for identifying the 1 st data is provided on the upper side of the hierarchical structureBit, and identifies base code "a" of data 2 1 "set in the lower position of the base code" a ". Similarly, the base code "a" of the 3 rd data is identified 11 "set in base code" a 1 "lower level, basic code" a "identifying the 4 th data 111 "set in base code" a 11 "lower level, basic code" a "identifying the 5 th data 1111 "set in base code" a 111 "lower level". The base database 120 stores the respective codes of the plurality of base codes by: the base code of the data corresponding to the upper concept is packed by a plurality of layers. For example, where there are n tiers, the underlying database 120 has a hierarchical structure of tiers. The base database 120 supplies predetermined data to the data conversion unit 125 in response to the activation of the data conversion unit 120.
The base database 120 may further store character strings such as "standard names" corresponding to the base codes, and other incidental information together with the base codes. The base database 120 may store character string information represented by character string formats of any of full-angle, half-angle, or full-half-angle mixture, or character string information in the form of all of them (i.e., character string information called "full format" in this embodiment), as information of "standard name". When the correspondence relation updating unit 150 and/or the information updating unit 155 performs a predetermined process, the base database 120 may output the "standard name" to the user in a perceptible manner via the data output unit 140 in response to the activation of the correspondence relation updating unit 150 and/or the information updating unit 155. The data output unit 140 may attach information related to a standard name as incidental information to the output data.
(data conversion section 125)
When the code presence judging section 115 judges that the base code corresponding to the standard data converted by the base code converting section 110 is stored in the conversion database 105 in association with another database identifier, the data converting section 125 converts the standard data into an external identification code stored in the conversion database 105 in association with the base code corresponding to the standard data and the other database identifier.
In addition, when the code presence judging section 115 judges that the same basic code as the basic code corresponding to the basic code converted by the basic code converting section 110 is not stored in the conversion database 105 in association with another database identifier, the data converting section 125 converts the basic code into an external identification code stored in the conversion database 105 in association with another database identifier and the basic code of any one within the hierarchical structure indicated by the hierarchical structure information including the basic code corresponding to the standard data. That is, the data conversion unit 125 searches for a basic code constituting a substitute for the basic code corresponding to the standard data converted by the basic code conversion unit 110 from the hierarchical structure for the purpose of converting the standard data into the external identification code, and performs the conversion processing using the basic code extracted by the search. For example, the data conversion unit 125 converts the basic code corresponding to the standard data into the external identification code stored in the conversion database 105 in association with the basic code classified into the upper, lower, or horizontal (same column) classification position from the position in the hierarchical structure stored in the basic database 120 (i.e., the classification position of the basic code corresponding to the standard data) and the other database identifier.
Specifically, when the code presence determination unit 115 determines that the base code corresponding to the standard data is not stored in the conversion database 105 in association with another database identifier, the data conversion unit 125 searches for the appropriate base code by: a search (upward search) to trace back from the classification position of the base code corresponding to the standard data (i.e., the base code corresponding to the standard data), a search (downward search) to move down to the lower level, and/or a search (horizontal search) within the same hierarchy are performed. The data conversion unit 125 searches for the base code using at least 1 search method selected from the group consisting of upward search, downward search, and horizontal search, or a combination of at least 2 search methods. When a plurality of search methods are combined, the data conversion unit 125 searches for the base code according to a predetermined rule.
The data conversion unit 125 may perform upward search, downward search, and/or horizontal search (hereinafter, referred to as "compound search" in some cases) by a predetermined combination. For example, the data conversion unit 125 may perform upward search, downward search, and horizontal search in this order. As an example, the data conversion unit 125 performs upward search first, and then performs downward search when a suitable base code cannot be extracted by the upward search. Then, the data conversion unit 125 performs horizontal search in the case where the appropriate base code cannot be extracted even by downward search.
In the composite search, the data conversion unit 125 may not perform some of the upward search, the downward search, and the horizontal search. For example, the data conversion unit 125 first performs upward search until n levels (where n represents an integer of 1 or more, and the value of n is predetermined). Then, the data conversion unit 125 may perform processing of performing the downward search and not performing the horizontal search. The combination of the upward search, the downward search, and/or the horizontal search performed by the data conversion section 125 may also be determined in response to a request from the data supply side database and/or the data reception side database. In the case of a request for determining a combination of searches from both the data supply side database and the data reception side database, it is preferable to determine with priority who is to be given priority.
The data conversion unit 125 may perform a search (hereinafter referred to as "mixed search") in which upward search, downward search, and/or horizontal search are combined in 1 search. As an example, the data conversion unit 125 searches the hierarchical structure at 1 hierarchical level and then searches the hierarchical structure at 1 hierarchical level. For example, when the base code in the hierarchy stored in the relative base database 120 is not present in the same group of base codes corresponding to the same hierarchy as the base code of the designated hierarchy in the case where the base code is received from one external database via the data exchange system 1 only from the external database arranged in the designated hierarchy, the predetermined base code is retrieved from the plurality of base codes of the "adjacent" group. That is, in this case, the data conversion unit 125 performs processing of "searching up at level 2" and "searching down at level 2".
The data conversion unit 125 performs a search process by a predetermined combination in the hybrid search. For example, the data conversion unit 125 performs the downward search immediately after the upward search, and can perform the hybrid search if the appropriate basic code cannot be extracted during any search. In the hybrid search, the data conversion unit 125 may trace back 1 hierarchy and then perform the downward search, and then trace back 2 hierarchy and then perform the downward search in order. The implementation of the search may be predetermined. In addition, a combination of upward search, downward search, and/or horizontal search constituting the mixed search performed by the data conversion section 125 may also be determined in response to a request from the data supply side database and/or the data reception side database. In the case of a request having a determination of a combination of the searches from both the data supply side database and the data reception side database, it is preferable to determine which one is to be preferred in advance.
Here, the upward search is explained. The data conversion unit 125 may search for a base code corresponding to the classification position of the external data in the hierarchical structure of the other database in the upward search. Specifically, the data conversion unit 125 searches for the base code of the upper n hierarchy level (where n is equal to or greater than 1) from the classification position of the base code corresponding to the standard data. For example, the data conversion unit 125 searches for a base code corresponding to information obtained when rounding the granularity of information corresponding to the base code (for example, when information called "beagle dog" is associated with a predetermined base code, the granularity may be rounded by converting the information into information called "dog" which is higher-order information, and the data conversion unit 125 searches for a base code corresponding to information called "dog" which rounds the granularity by the initial base code). In addition, when specific information is not required on the external database side of the received data, conversion of the base code corresponding to the information of the upper concept is effective when the capability of specific information processing is not performed, or the like. The data conversion unit 125 converts the standard data into an external identification code stored in the conversion database 105 in association with the base code extracted by the search and other database identifiers.
The following description will explain the downward search. The data conversion section 125 retrieves, in the downward retrieval, the base code corresponding to the classification position of the external data in the other hierarchical structure employed by the other database. Specifically, when retrieving the base code, the data conversion unit 125 retrieves the hierarchical structure from the upper level to the lower level. That is, the data conversion unit 125 can extract the base code of the classification position which is lowered from the classification position to the lower position. For example, the data conversion unit 125 retrieves a base code corresponding to information obtained when the granularity of information corresponding to the base code is reduced (thinned) (for example, when information called "dog" is associated with a predetermined base code, the granularity may be reduced by converting the information into information of "bomek" which is lower information, and the data conversion unit 125 retrieves, from the base code at the beginning, a base code corresponding to the information of "bomek" whose granularity is reduced). When the external database side that receives data does not have an external identification code for receiving information with a large granularity, conversion of the base code corresponding to the information of the lower level concept is effective. In other words, in the downward search, the data conversion section 125 appends specific information that the original information does not have to the original information.
For example, when "order data" of a predetermined transaction is supplied from one external database to another external database via the data exchange system 1, external data called "dog" is supplied from one external database to the data exchange system 1, and "any kind if dog is the case" is also possible). In this case, the data exchange system 1 performs an operation of retrieving and extracting the base code corresponding to the information of "bomek" corresponding to the concept level lower than the concept level of the information of "dog".
Here, when the hierarchical structure of the conversion database 105 is searched downward, a plurality of codes corresponding to the lower concept level are provided. In this case, the data conversion unit 125 performs processing by selecting which of the plurality of base codes is selected according to a predetermined rule. For example, the data conversion unit 125 may perform the search at a search level predetermined for each level of the hierarchical structure stored in the base database 120. The data conversion unit 125 may search for the base codes in the base database 120 in the order corresponding to the base codes. The data conversion unit 125 searches for a base code of 1 hierarchical lower hierarchy, and may search for a hierarchy further lowered by 1 hierarchical level if the base code does not include a base code corresponding to an external identification code to be converted. Then, even when the search is lowered by 1 hierarchical level and the appropriate base code is not provided, the data conversion unit 125 may sequentially repeat the search lowered to the lower side.
In addition, horizontal search will be described. The data conversion unit 125 may search for a basic code corresponding to the classification position of the external data in another hierarchical structure employed in another database in the horizontal search. Specifically, when retrieving the base code, the data conversion unit 125 may retrieve the base code classified by the same column as the conceptual level of the classification position of the base code corresponding to the standard data. For example, the data conversion unit 125 searches for another base code of the same concept level without changing the granularity of information corresponding to the base code or the concept level of the classification in the hierarchical structure (for example, when information called "autumn dogs" is associated with a predetermined base code, the information can be converted into information of "bomeidogs" which is the same concept level as the information, and the information can be converted into another base code without changing the granularity). In the case where one external database (data supply side) and another external database (data receiving side) exchange data via the data exchange system 1, the horizontal search is effective when the external database on the receiving side does not have information corresponding to the upper concept of predetermined external data and any one of the information corresponding to the lower concept stores only another external data having the same level of the external data and the concept.
In the horizontal search, the data conversion unit 125 searches for a plurality of base codes belonging to the lower level of the base code corresponding to the same upper concept within the same group of the same hierarchy level within the hierarchy structure stored in the base database 120. The data conversion unit 125 extracts one basic code from the plurality of basic codes based on a predetermined reference within the same group at the same level, and uses the extracted basic code for conversion processing. The predetermined criterion is a criterion or the like for determining a search rank in advance for each level of the hierarchical structure of the base database 120, for example, a criterion for searching for the base code in the hierarchical structure in accordance with the search rank. The search rank may also be determined in response to a request from the data-supplying-side database and/or the data-receiving-side database. In the case where there is a request for determining the search rank from both the data supply side database and the data reception side database, it is preferable to determine which one is prioritized in advance.
In addition, the data conversion unit 125 may convert the standard data into an external identification code stored in the conversion database 105 in association with the base code extracted from the base database 120, and may lose information of a part of the external data corresponding to the original external identification code (that is, the external identification code of the external data received by the data input unit 100 from one external database). That is, the data conversion unit 125 converts the external identification code of the external data received by the data input unit 100 into the external identification code of the external data corresponding to the higher-level concept, thereby causing information loss. For example, the data input unit 100 receives an external identification code of "radish with earth" from an external database, and the data conversion unit 125 is configured to convert the external identification code into an external identification code of "radish" and involves at least information loss of "radish with earth".
Then, when the standard data is converted into the external identification code and information loss occurs, the data conversion unit 125 may include loss information indicating information loss and/or loss level information indicating a level of information loss (i.e., a level of loss) in the converted external identification code. For example, whenever the hierarchy of the underlying database 120 is traced, the granularity of information associated with the underlying code is coarse, resulting in a loss of information. Then, the data conversion unit 125 generates "trace back number of levels" indicating the degree of loss as "loss level". The data conversion unit 125 may include the formed information in the converted external identification code. Thus, the other external database that received the external identification code can grasp the occurrence of loss and the level of loss. For example, when searching the hierarchical structure of the base database 120, the data conversion unit 125 generates the number of levels to be traced (i.e., the "number of trace levels") as loss information in the search of the hierarchical structure. As an example, the case where the number of trace back levels is "0" indicates "no information is lost", the case where the number of trace back levels is "1" indicates "trace back of 1 level is generated", and the case where the number of trace back levels is "m" indicates "trace back of m levels is generated" (where m > 1).
Similarly, the data conversion unit 125 may generate information indicating the number of hierarchical levels falling from the upper level to the lower level in the hierarchical structure search. For example, by lowering the hierarchy of the underlying database 120, the information that is appended to the original information is more specific. Then, the data conversion unit 125 can return "trace back number of levels" by a negative value using the same item as "loss level" at the time of upward search. That is, for example, when the search is performed at 1 hierarchical level down, the data conversion unit 125 returns to "-1". In addition, when the base code corresponding to the external identification code to be converted does not exist even if the data conversion unit 125 is lowered to the lowest level of the hierarchical structure, predetermined error information may be formed. The data conversion unit 125 may include error information in the converted external identification code.
In addition, when performing the horizontal search, the data conversion unit 125 may generate information indicating that the horizontal search is performed. For example, the data conversion unit 125 may form a horizontal search occurrence flag indicating that search processing in the horizontal direction (i.e., search processing within one hierarchical level belonging to the same conceptual level of the hierarchical structure) is to be performed. The data conversion unit 125 may be provided with a predetermined flag indicating a search including generation substitution of the upward search and the downward search (i.e., a "substitution search"), and if the flag is provided, information identifying the generation of the horizontal search may be formed if the value of the "trace back number of levels" is zero. The data conversion unit 125 may form predetermined error information when an appropriate base code cannot be retrieved during horizontal retrieval.
In addition, when the hybrid search is performed, the data conversion unit 125 generates information indicating that the hybrid search is performed. For example, the data conversion unit 125 may combine the number of upward trace-back levels (hereinafter, denoted as "U". U denotes an integer of 0 or more) in the upward search performed in the mixed search with the number of downward falling levels (hereinafter, denoted as "D". D denotes an integer of 0 or more) in the downward search to generate mixed search information denoted as "U, D". For example, when the search is performed at 1 level, the mixed search information is "1,0", and when the search is performed at 1 level, the mixed search information is "0,1". In addition, when horizontal search is performed in the same group, the mixed search information is "1,1". In addition, when there are a plurality of groups in the same conceptual hierarchy of the hierarchical structure, the mixed search information is "2,2" when the horizontal search is performed for a group "adjacent" to one group, and the mixed search information is "2,1" when the "parent" of the hierarchical structure (that is, the base code located at the upper classification position of one base code) is searched for the "sibling" (that is, a plurality of base codes classified according to the same conceptual hierarchy (the same hierarchy) as the upper classification position).
When receiving the information indicating that the judgment process is not performed and the external identification code, the data conversion unit 125 treats the external identification code as a converted external identification code. The data conversion unit 125 supplies the converted external identification code to the attachment unit 130 and/or the data output unit 140. That is, the data conversion unit 125 treats the received external identification code as an external identification code that is output to the outside (in this embodiment, this process is referred to as "direct conversion").
The data conversion unit 125 performs trace back from the lower level to the upper level in the hierarchical structure of the base database 120, and when a base code matching the standard data is retrieved, even when the uppermost level in the hierarchical structure is retrieved, the same base code as the base code corresponding to the standard data converted by the base code conversion unit 110 is not found, and error information indicating that the base code is not found is supplied to the data output unit 140. The error information is, for example, a null value or a "0" value, or flag information indicating an error.
(with unit 130)
The accompanying unit 130 includes an information accompanying part 132 and a code accompanying part 134, the information accompanying part 132 accompanying the external identification code with additional information, the code accompanying part 134 accompanying the external identification code received from the outside. In addition, the attaching unit 130 may store information, which is additional information attached to the external identification code by the information attaching portion 132 and/or information related to the external identification code attached to the external identification code by the code attaching portion 134, in the conversion database 105 in association with the external identification code. In this case, when the basic code is supplied to other constituent elements, the conversion database 105 may be supplied in accordance with the additional information or the like.
(information-carrying section 132)
The information adding unit 132 adds additional information related to one external data to the external identification code converted by the data conversion unit 125. The additional information is, for example, text data, numerical data, symbol data, and/or graphic data representing the content of the external data, or the like. As an example, when the external data is "gate keeper", the information adding unit 132 adds additional information indicating text data of "gate keeper" to the external identification code converted by the data conversion unit 125. The information adding unit 132 supplies the external identification code added with the additional information to the data output unit 140. Thus, even when the external identification code (hereinafter referred to as the original external identification code) supplied from one external database to another external database is converted into the external identification code of the external data of the upper concept of the external data represented by the original external identification code, the other external database which receives the external identification code with the additional information can grasp the content of the external data corresponding to the original external identification code.
Here, in response to the start-up from the base code conversion section 110, the information adding section 132 may add additional information (for example, information related to a character string such as a name) added to the external data received by the data input section 100 and/or additional information stored in the conversion database 105 or information related to the external identification code to the standard data when the base code conversion section 110 converts the external identification code to the standard data. When the additional information includes information related to a character string such as a name, the character string represented by the information is a character string in a format of any one of a full-angle, a half-angle, and a full-half-angle mixture. In addition, the information related to the character string attached to the standard data may be information converted into all formats of full angle, half angle, or full half angle mixture (hereinafter referred to as "full format") by the processing described below. For example, the base code conversion section 110 and/or the data conversion section 125 may perform conversion processing of information concerning the full format of information of a character string. As an example, the basic code conversion section 110 may perform the conversion processing at the timing when the data input section 100 receives the input of external data. The basic code conversion unit 110 may perform the conversion process at the time when predetermined information is stored in the conversion database 105. In addition, when the data conversion unit 125 performs processing for converting standard data into an external identification code, it is also possible to perform conversion processing of information in a complete format.
In addition, when receiving input of external data of text data, the data input unit 100 may further receive the following 3 kinds of information. That is, the format of the character string of the text data includes a full-angle character string, a half-angle character string, and a character string in which the full-angle character string and the half-angle character string are mixed. The data input unit 100 receives input of "full-angle character string information" which is a signal when a character string of text data is a full-angle character string, and "half-angle character string information" which is information when a character string is a half-angle character string, and "full-half-angle mixed character string information" which is information when a character string of a full-angle is mixed. The data input unit 100 supplies full-angle character string information, half-angle character string information, and/or full-half-angle mixed character string information to the information attaching unit 132.
When the external identification code is attached with additional information, the information attaching unit 132 converts the text data into a predetermined format based on the full-angle character string information, the half-angle character string information, or the full-half-angle mixed character string information received from the data input unit 100 when the additional information is text data. Specifically, when information of at least one of the full-angle character string information, the half-angle character string information, and the full-half-angle mixed character string information is not received from the data input unit 100, the information adding unit 132 automatically generates information other than the received information, which is added to the external identification code as added information. The information adding unit 132 may analyze text data when the data input unit 100 receives input of the text data, and the information adding unit 132 may associate full-angle character string information, half-angle character string information, or full-half-angle mixed character string information with the text data.
For example, when full-angle character string information is not received from the data input unit 100, the information adding unit 132 converts half-angle characters in a character string represented by the full-angle character string information into full-angle characters to form full-angle character string information when full-angle character string information is received. The information adding unit 132 includes the full-angle mixed string information, the half-angle mixed string information, and the full-half-angle mixed string information, which are obtained by the generation, in the additional information. When the data input unit 100 does not receive the full-angle character string information or the full-half-angle mixed character string information, the information adding unit 132 converts half-angle characters of the character string indicated by the half-angle character string information into full-angle characters to form full-angle character string information. Next, the information adding unit 132 includes the full-angle character string information and the half-angle character string information obtained by the generation in the additional information.
When full-character string information is not received from the data input unit 100, the information adding unit 132 includes the full-character string information in the additional information as it is when the full-character string information is received. On the other hand, when the data input unit 100 does not receive the full-angle mixed string information and also does not receive the full-angle string information, the information adding unit 132 converts the half-angle character of the string represented by the half-angle string information into the full-angle, generates the full-angle string information, or maintains the half-angle character of the string represented by the half-angle string information as it is. The information adding unit 132 includes the full-angle character string information obtained by the generation as it is in the additional information, and includes the half-angle character string information as it is in the additional information.
When half-angle character string information is not received from the data input unit 100, the information adding unit 132 includes conversion character string information for performing kanji-kana conversion on character strings indicated by the full-angle character string information in the additional information when the full-half-angle character string information is received. On the other hand, when half-angle character string information is not received from the data input unit 100, and when full-half-angle mixed character string information is not received, the information adding unit 132 includes half-angle character string information for kana conversion of a character string represented by full-angle character string information in the additional information.
Thus, in the data exchange system 1, even when the formats of the character strings handled by one external database and the formats of the character strings handled by the other external databases are different from each other, one external database can convert the external data supplied to the other external databases into the predetermined character string format, so that stable data exchange can be realized between the external databases.
Also, the information incidental portion 132 may also be used alone as a text data conversion system. The text data conversion system includes: a text data obtaining section that obtains text data from outside; a text data judging section that judges the kind of the text data obtained by the text data obtaining section; and a text data conversion unit that converts the text data into a predetermined format based on the determination result of the text data determination unit. The type of text data is a type indicating that the text data is a full-character string, a type indicating that the text data is a half-character string, or a type indicating that the full-character string may be mixed. The text data conversion system may further include a text data output unit that outputs text data converted in a predetermined format and/or a flag unit that adds a flag indicating whether or not the outputted text data is automatically generated by the text data conversion system to the outputted text data.
The text data judging unit analyzes that the obtained text data is a full-angle character string, judges full-angle character string information as a type of text data when the character string of the text data is a half-angle character string, judges half-angle character string information as a type of text data when the character string of the text data is a half-angle character string, and judges full-angle character string information as a type of text data when the character string of the text data is a character string in which the full-angle character string and the half-angle character string are mixed. The text data conversion unit performs conversion processing such as conversion of half characters into full characters, kanji conversion, and the like of the obtained text data based on the text data obtained by the text data obtaining unit, the text data not obtained, and the judgment result of the text data judgment unit, as in the above description of the information adding unit 132.
The flag section attaches a flag to the converted text data, the flag indicating whether the text data conversion section automatically generates the text data. For example, when the text data converting section converts a half angle of the text data into a full angle and/or when the full angle is converted into a half angle, the marking section does not have an automatically generated mark attached thereto or does not have an automatically generated mark attached thereto. On the other hand, when the text data conversion unit performs kana conversion processing, the marking unit adds a mark indicating automatically generated text data to the converted text data.
Thus, even if the types of text data input are not unified, the text data conversion system can unify the types of text data output. In addition, in the text data conversion system, since the predetermined flag can be attached to the outputted text data, it is easy to determine whether or not the outputted text data is automatically generated by the text data conversion system.
(code attachment portion 134)
The code attaching unit 134 attaches, to the external identification code converted by the data converting unit 125, one external identification code of one external data received from one external database. That is, the code attaching unit 134 attaches, to the external identification code converted by the data converting unit 125, one external identification code of one external data received by the data exchange system 1 from one external database. The code adding unit 134 supplies the external identification code converted by the data converting unit 125, together with the external identification code, to the data output unit 140. Thus, in the data exchange system 1, when a predetermined external identification code is supplied from one external database to another external database, the external identification code supplied from one external identification code to the other external database can be restored based on the external identification code of the other external database.
(data output section 140)
The data output unit 140 outputs the external identification code, the external data, and/or additional information related to the external identification code or the external data converted by the data conversion unit 125, and/or information related to the external identification code, to other external databases (that is, one external database is an external database corresponding to a database identifier specified as an external database of the supplier with respect to the data exchange system 1). The data output unit 140 may store the external identification code converted by the data conversion unit 125 in a predetermined storage medium.
In addition, in the data exchange system 1, there may be a part of each constituent element described by the above in the outside of the system. For example, in the data exchange system 1, the conversion database 105, the base database 120, the data conversion unit 125, and the like are provided in an external server.
(correspondence relation updating section 150)
The correspondence relation updating section 150 updates the data stored in the conversion database 105. When receiving information or an instruction to update the data stored in the conversion database 105, the correspondence relation updating unit 150 updates the stored data in accordance with the information or the instruction.
In addition, when the conversion database 105 stores a plurality of basic codes in association with 1 external identification code, the correspondence relation updating unit 150 may instruct the user that information indicating "master registration" should be associated with the correspondence relation between the 1 external identification code and one basic code, or may force the operation. Similarly, when the conversion database 105 stores a plurality of base codes in association with 1 external identification code, the correspondence relation updating unit 150 may instruct the user that information indicating "master registration" should be associated with the correspondence relation between the 1 external identification code and one base code, or may force the operation.
(information updating section 155)
The information updating unit 155 updates information stored in the base database 120. When receiving information or an instruction to update the content of the information stored in the base database 120, the information update unit 155 updates the stored information in accordance with the information or the instruction.
(code Change management section)
The correspondence relation updating unit 150 and/or the information updating unit 155 may include a code change management unit in order to prevent the data exchange system 1 from outputting unexpected data conversion processing results when changing the information associated with the base code. The code change management unit prevents the unexpected result from being output when the update of the data stored in the conversion database 105 is not performed in the correspondence relation update unit 150 in response to the change of the content of the external database on the data supply side.
For example, the code change management unit functions under the following preconditions. First, the external data input by the data input unit 100 has not only an external identification code or the like but also name string information indicating the name of the content of the external data. The conversion database 105 further stores name string information of external data identified by the external identification code in association with the database identifier and the external identification code and the base code.
In addition, when the external identification code is converted into standard data by the base code conversion unit 110, the code change management unit checks name string information attached to the external identification code or the like with the name string information stored in the conversion database 105. When the collation results are not identical, the code change management unit may supply information indicating an error to one external database side which supplies external data to the data exchange system 1. The code change management unit supplies information indicating an error to the data output unit 140. The information indicating the error may include a flag indicating that the error has occurred, and/or name string information attached to the external data input by the data input unit 100 is received, and the name string information stored in the database 105 is converted.
Here, when the code change management unit compares the name string information attached to the external data received and input by the data input unit 100 with the name string information stored in the conversion database 105, the code change management unit can simply and completely match the comparison. Further, a comparison of "fuzzy search" may be performed in which the difference in full angle and half angle of the name string represented by the name string information, the difference in large character and small character, and the difference in katakana and hiragana are absorbed. In addition, the code change management unit may detect the matching portion and the difference portion and attach the matching portion and the difference portion to information indicating an error when the name string information attached to the external data and the name string information registered in the conversion database 105 are compared. The code change management unit may perform the comparison by using the "fuzzy search" when detecting the matching portion and the difference portion. In addition, the code change management unit may automatically store the name string information attached to the external data in the conversion database 105 in association with the external identification code or the like when the name string information is not stored in the conversion database 105 in advance. The code change management unit may automatically store the name string information attached to the external data in the conversion database 105 when there is a difference between the name string information attached to the external data and the name string information stored in the conversion database 105. In this case, the code change management unit may supply predetermined error information and warning to one external database side and/or the data output unit 140 side, which provide external data to the data exchange system 1.
(error message)
All or a part of the constituent elements included in the data exchange system 1 may have an error processing function of supplying a predetermined error to an external database and/or other external databases when the error is detected. In addition, when a predetermined error is detected in each of all or a part of the constituent elements included in the data exchange system 1, the processing of each constituent element may be stopped at the detection timing. In this case, the data exchange system 1 may associate, with all or a part of the various data received as input, a flag indicating that any process is performed or is not performed inside the data exchange system 1, with respect to the various data received as input from one external database. Even when a predetermined error occurs, the data exchange system 1 can continue the data processing of the data exchange system 1 and supply the converted data to another external database. Alternatively, the data exchange system 1 may stop all the processes in the data exchange system 1 when m predetermined errors (where m is an integer of 1 or more) occur.
Fig. 5 shows an example of an outline of a functional configuration of another form of the data exchange system according to the embodiment of the present invention. In addition, the data exchange system 1a shown in fig. 5 has a functional configuration different from that of the data exchange system 1. That is, the data exchange system 1a has a structure and functions of a basic system with all or a part of the data exchange system 1, in addition to aspects of the input data processing unit 10 and the output data processing unit 15. Accordingly, unless otherwise specified, a specific explanation is omitted.
The data exchange system 1a includes an input data processing unit 10 and an output data processing unit 15, the input data processing unit 10 processing external data stored in an external database, the output data processing unit 15 processing data supplied to other external databases in accordance with the processing of the data of the input data processing unit 10. The input data processing unit 10 includes a conversion database 105, a base code conversion section 110, and a base database 125. In addition, the output data processing unit 15 includes a data converting section 25. The input data processing unit 10 and the output data processing unit 15 may further include a part or all of the data input section 100, the code presence judging section 115, the information attaching section 132, the code attaching section 134, the data output section 140, the correspondence updating section 150, and/or the information updating section 155.
The input data processing unit 10 converts the external identification code into standard data based on the obtained external data, external identification code, and/or database identifier when the external data is obtained from the external database. Specifically, the base code conversion section 110 refers to the conversion database 105, and obtains the base code stored in the conversion database 105 in association with the external identification code of the obtained external data. Next, the base code conversion section 110 converts the external identification code into standard data associated with the obtained base code. For example, the base code conversion unit 110 converts the external identification code into standard data by using, as standard data, base code obtained from the conversion database 105 and external data obtained from the external database, as well as data associated with the external identification code of the external database. The input data processing unit 10 supplies standard data to the output data processing unit 15.
The output data processing unit 15 refers to the conversion database 105, and determines whether or not the base code corresponding to the received standard data is stored in the conversion database 105 in association with the database identifier of the other database. Next, when it is determined that the base code identical to the base code corresponding to the received standard data is stored in the conversion database 105 in association with another database identifier, the data conversion unit 125 converts the standard data into an external identification code stored in the conversion database 105 in association with the standard data and the other database identifier.
On the other hand, when it is determined that the same basic code as the basic code corresponding to the converted standard data is not stored in the conversion database 105 in association with another database identifier, the data conversion unit 125 converts the basic code corresponding to the standard data into a code stored in the conversion database 105 in association with the basic code and another database identifier, which classifies the hierarchical structure stored in the basic database 120 into a classification position from the standard data and traces back to the upper classification position.
The data conversion unit 125 may perform a conversion method (hereinafter referred to as "direct conversion processing") without using a conversion process or the like using the base database 120. For example, the data conversion unit 125 may perform at least any one of the following 1 st to 3 rd direct conversion processes.
Specifically, the 1 st direct conversion process is performed by, for example, the following method. First, the data input unit 100 receives the database identifier and the external identification code on the output side. The data input unit 100 may receive the database identifier and the set of external identification codes in n sets (n represents an integer of 1 or more). Next, the base code conversion unit 110 adds the set of n database identifiers and external identification codes received by the data input unit 100 to the standard data, or supplies the set of n database identifiers and external identification codes to the data conversion unit 125 without generating the standard data. Then, the data conversion section 125 supplies the external identification code added to the standard data or the external identification code received by the data input section 100 as information indicating the conversion result (i.e., the information indicating the conversion result is handled as the external identification code obtained by conversion, hereinafter the same) to the data output section 140 without via the search of the base database 120 of the code presence determination section 115.
The 2 nd direct conversion process is performed by, for example, the following method. First, n sets (n represents an integer of 1 or more) of the conversion database 105 may be stored with sets of the database identifier on the output side and the external identification code corresponding to the external identification code on the input side. Next, the basic code conversion unit 110 refers to the conversion database 105, and adds n sets of database identifiers and external identification codes to the standard data, or supplies the standard data to the data conversion unit 125 without generating the standard data. The data conversion unit 125 supplies the external identification code attached to the standard data or the external identification code received by the data input unit 100 to the data output unit 140 as information indicating the conversion result, without searching the base database 120 of the code presence determination unit 115.
The 3 rd direct conversion process is performed by, for example, the following method. First, n sets (n represents an integer of 1 or more) of the conversion database 105 may be stored with sets of the database identifier on the input side and the external identification code corresponding to the external identification code on the output side. Next, the data conversion unit 125 searches the conversion database 105 based on the database identifier stored in the standard data and the external identification data before the search process of the conversion database 105 by the code presence determination unit 115 is performed. Next, when the database identifier and the external identification code corresponding to the database identifier and the external identification data stored as standard data are stored in the conversion database 105, the data conversion unit 125 supplies the external identification code to the data output unit 140 as information indicating the conversion result.
Here, the 1 st to 3 rd direct conversion processes may be performed in preference to other direct conversion processes by associating the priority order with the corresponding process among the direct conversion processes, for example.
(outline of flow of processing of data exchange System 1)
Fig. 6 shows an example of data of a conversion database according to an embodiment of the present invention, and fig. 7 shows an example of data of a base database according to an embodiment of the present invention. Fig. 8 shows an example of a flow of processing in the information input system according to the embodiment of the present invention.
Here, a case where predetermined data is supplied from the 1 st external database to the 2 nd external database will be described as an example. In addition, the database identifier of the 1 st external database is "001", and the 1 st external database combines the data "guard turnip" with the external identification code "a 11 'storing the data' radish with soil 'in association with the external identification code' a 12 ' are stored in association. On the other hand, the database identifier of the 2 nd external database is "002", and the data "radish" and the external identification code "a" are used 1 ' storing the data "root plant" in association with the external identification code "a 2 ' are stored in association.
Next, as shown in FIG. 6, the conversion database 105 stores the database identifier "001" and the external identification code "a 11 ' base code "a stored in association in base database 120 11 "store and database identifier" 001 "and external identification code" a 12 ' base code "a stored in association in base database 120 12 ". Similarly, the conversion database 105 stores the database identifier "002" and the external identification code "a 1 ' associated withBase code "a" stored in base database 120 1 "storing and database identifier" 002 "and external identification code" a 2 ' base code "a stored in association in base database 120 2 ”。
As shown in fig. 7, the base database 120 stores hierarchical structure information of a hierarchical structure formed by: base code "a" associated as a lower concept of base code "a" (e.g., base code corresponding to data "root crop") 1 "(e.g., base code corresponding to data" radish "), base code" a 2 ", base code" a 3 "etc., and is associated as a base code" a 1 "underlying concept base code" a 11 "(e.g., base code corresponding to data" guard radish "), base code" a 12 "etc. In the description herein, the conversion database 105 and the base database 120 store a plurality of database identifiers, external identification codes, and/or base codes, even if not described above, but for simplicity of description, a part of the database identifiers, external identification codes, and/or base codes are extracted and described.
First, the data input section 100 receives input of external data from the 1 st external database (step 10. The step is denoted as "S" in the following). For example, the data input unit 100 will indicate that the external identification code "a" is associated 11 The input of the external data of the "gate keeper radish" is received together with the database identifier "002" of the 2 nd external data. The data input section 100 supplies the received data and the like to the basic code conversion section 110.
The basic code conversion unit 110 converts the external identification code into standard data based on the data received from the data input unit 100, or the like (S15). For example, the base code conversion section 110 obtains the base code "a" described below 11 "the following basic code" a " 11 "is to externally identify code" a 11 ' and database of external identification code and 1 st external database received from data input unit 100The identifier "001" is stored in association with the code in the conversion database 105. Next, the base code conversion section 110 converts the obtained base code "a" into a code "a 11 "and external identification code" a 11 ' external identification code "a" in external data associated with 11 ' the associated data is treated as standard data (in this embodiment, for simplicity of explanation, standard data is expressed as the same basic code as the standard data). The base code conversion section 110 supplies the obtained standard data to the code presence determination section 115.
The code presence judging section 115 judges whether or not the base code corresponding to the standard data received from the base code converting section 110 is stored in the conversion database 105 in association with the database identifier "002" of the 2 nd external database (S20). The code presence judging section 115 supplies information indicating the judgment result to the data converting section 125.
When the code presence judging section 115 judges that the base code corresponding to the standard data is stored in the conversion database 105 (yes in S20), the data converting section 125 converts the standard data into the external identification code stored in the conversion database 105 in association with the standard data and the database identifier of the 2 nd external database (S25). The data conversion section 125 supplies the external identification code obtained by the conversion to the data output section 140.
On the other hand, when the code presence judging section 115 judges that the basic code corresponding to the standard data is not stored in the conversion database 105 (S20: no), the data converting section 125 refers to the basic database 120 and converts the standard data into the external identification code stored in the conversion database 105 in association with the database identifier of the 2 nd external database in association with any basic code included in the hierarchical structure including the basic code corresponding to the standard data (S30). For example, the data conversion section 125 refers to the sum-sum standard data "a 11 "corresponding base code" a 11 "same basic code" a 11 "hierarchy information of the underlying database 120. The base database 120 includes a base code "a 11 ”，And converts the database 105 with the base code "a 11 Basic code "a" of "upper concept 1 "storing the external identification code" a in association with the database identifier "002" of the 2 nd external database 1 ’”。
Then, the data conversion section 125 first uses the basic code "a" of the hierarchical structure 11 "the upper concept is searched by tracing the center, and the basic code" a "is extracted 1 ". Next, the data conversion unit 125 refers to the conversion database 105 and refers to the external identification code "a 1 ' the external identification code "a 1 ' and database identifier "002" and extracted base code "a 1 "associated". Then, the data conversion unit 125 converts the standard data "a 11 "convert to external identification code" a 1 '". In this case, the data conversion unit 125 may add loss information indicating "1" which is "trace back number" to the converted external identification code.
The data output unit 140 outputs the external identification code and/or the external data received from the data conversion unit 125 to a predetermined external database (S35). For example, the data output section 140 will be connected to the external identification code "a 1 'and/or standard data' a 11 "a part or all of the associated external data is output to the 2 nd external database.
Fig. 9 shows an example of a basic database according to another embodiment of the present invention, and fig. 10 shows an example of data of a conversion database according to yet another embodiment of the present invention. Fig. 11 is a schematic diagram showing a flow of data exchange in the data exchange system according to another embodiment of the present invention. Here, an example of providing data from company a to company B will be described.
As shown in fig. 9, the base database 120 sets the base code "a" identifying the 1 st data at an upper level of the hierarchical structure (i.e., tree structure), and identifies the base code "a" of the 2 nd data 1 "and basic code" a for identifying 3 rd data 2 "set in the lower position of the base code" a ". Similarly, the base code "a" of the 4 th data will be identified 11 "sumBasic code "a" for identifying 5 th data 12 "set in base code" a 1 "lower level, will identify the base code" a "of the 6 th data 111 "basic code" a "identifying 7 th data 112 "and basic code for identifying 8 th data" a 113 "set in base code" a 11 "lower level". In addition, in the same column as the base code "a", other base codes "B" and the like are set. Likewise, the basic code "a" can be also used 1 ", base code" a 11 "or base code" a 111 In the corresponding code of "other base codes are set in addition to the ones shown in the figure.
Here, as an example, the 1 st data is data representing "vegetables", the 2 nd data is data representing "root crops", the 4 th data is data representing "radishes", the 5 th data is data representing "root plants", the 6 th data is data representing "radishes with soil", the 7 th data is data representing "turnips", and the 8 th data is data representing "holly nursing home radishes".
As shown in fig. 10, the conversion database 105 stores the external identification code, the base code, and/or the name of the article in association with the database identifier "a" identifying company a. In addition, the conversion database 105 stores the external identification code, the base code, and/or the name of the article in association with the database identifier "B" identifying company B.
For example, the conversion database 105 causes the external identification code "0001" and the base code "a 11 The "and the name of the item" radish "are associated with the database identifier" a "and stored. Similarly, the conversion database 105 makes the external identification code "0002" and the base code "a 111 The "and article name" radish with soil "is associated with database identifier" A ", and the external identification code" 0003 "and the base code" a "are made to be identical 12 The "and the name of the article" root plant "are associated with the database identifier" A ", and the external identification code" 0003 "and the base code" a "are made to be associated with each other 113 "name of article" root plant "and numberThe database identifier "a" is associated and stored.
Here, although a base code "a" is associated 113 "and the name" root plant "of the item, however, it indicates that company a employs associations other than the underlying database 120. The translation database 105 then prohibits the plurality of associations or associates the priority order with the respective ones of the plurality of associations where there are a plurality of associations in the association of the external identification code and the base code. Next, the data conversion unit 125 performs conversion processing using the base code associated with the highest priority order. For example, in the example of fig. 10, a flag (hereinafter, referred to as "priority flag" (not shown in the figure)) indicating that the highest priority level corresponds to the base code "a" corresponding to the external identification code "0003" may be associated 12 "associated". On the other hand, the priority flag is not made to correspond to the base code "a" corresponding to the external identification code "0003 113 "associated".
In addition, the conversion database 105 makes the external identification code "1001" and the base code "a 111 The "radish with article name" is associated with database identifier "B", so that the external identification code "1002" and the basic code "a" are made 112 * The "and article name" gate keeper radish "is associated with the database identifier" B ", so that the external identification code" 1003 "and the basic code" a "are made 11 Associating "with item name" radish "with database identifier" B "to make external identification code" 1004 "and base code" a 12 The "root plant associated with the item name" is associated with the database identifier "B", so that the external identification code "1005" and the base code "a" are made 113 The "and item name" holly-hospital radish "is associated with a database identifier" B ".
Here, the base code may be attached with predetermined attached information. For example, in the base code "a 112 * In "a flag indicating that predetermined incidental information is appended. The data conversion unit 125 converts the standard data into an external identification code based on the incidental information. For example, the incidental information is a base indicating a rule associated with a rule database identifier The base code uses a predetermined another code as information of the external identification code irrespective of the hierarchical structure of the base database 120.
As an example, base code "a" is associated with database identifier "B 112 "stored in the conversion database 105," in the base code, incidental information indicating that, when the base code is adopted by company a, the external base code "0003" of company a is adopted. In this case, when data (here, data corresponding to the external base code "1002") is supplied to company a, first, the base code conversion unit 110 searches the conversion database 105 using the external identification code "1002" supplied from the external database of company B, and obtains the base code "a" stored in association with the database identifier "B" and the external identification code "1002" 112 ". Next, the base code conversion unit 110 converts the base code "a" into a code "a 112 Data associated with the external identification code 1002 as standard data a 112 "treat, convert external identification code" 1002 "into standard data" a 112 ". The incidental information is respectively incidental to the base code and the standard data stored in the conversion database 105.
Next, the data conversion unit 125 receives the standard data from the base code conversion unit 110, and confirms whether or not the base code corresponding to the standard data exists in the hierarchical structure of the base database 120. Here, the standard data is attached with incidental information. As described above, this incidental information is information indicating that the external base code "0003" of company a is used when company a uses this base code. I.e., information representing a transformation of another hierarchy different from the hierarchy employed by the underlying database 120. Then, the data conversion unit 125 makes a predetermined code (here, the code "0003") an external identification code by the incidental information, not in accordance with the hierarchical structure of the base database 120.
Then, as shown in fig. 11, the external identification code of company B is converted to the external identification code of company a via standard data by the functions of the code presence judging section 115 and the data converting section 125And (3) a part identification code. For example, the external identification code "1001" of company B is compared with the base code "a" in the conversion database 105 111 "associated", the base code is converted into a code called "a" in the base code converting section 110 111 "standard data. Then, the data conversion unit 125 converts the standard data "a 111 "convert to the following code, which refers to the sum in the conversion database 105 and the standard data" a 111 "corresponding base code consistent base code" a 111 "external identification code" 0002 "associated with database identifier" a ". The data exchange system 1 performs the same processing for the base code with no accompanying information.
On the other hand, the conversion database stores the base code "a" accompanied by the incidental information in association with the external identification code "1002" of the B company 112 ". Next, the conversion database 105 stores the base code "a" without being associated with the database identifier of company a 112 ". In this case, the data exchange system 1 traces back the code "a" of the base database 120 when there is no incidental information 112 "upper level, will transform the base code" a 11 "selected as the base code for the conversion. In addition, the data exchange system 1, when there is no incidental information, stores the standard data "a 111 "to a code which is referred to as a base code" a "and forms an external identification code 11 "external identification code" 0001 "stored in the conversion database 105 in association with the database identifier" a ". However, here, the base code is accompanied by the incidental information, so that the data exchange system 1 makes the code represented by the incidental information the converted external identification code. That is, here, the code "0003" is the converted external identification code. Thus, the data exchange system 1 can convert the external identification code "1002" of company B into the external identification code "0003" of company a.
When the base code conversion unit 110 converts the external identification codes in the database 105, in which the plurality of base codes are associated with the same external identification code, the processing is performed based on the priority flag. For example, when the external identification code "0003" is obtained from company a, the base code conversion unit 110 uses the base code (in the example of fig. 10, the base code "a" associated with the priority flag 12 ") to convert the external identification code into standard data. Next, the data conversion section 125 performs conversion processing using standard data converted by the base code conversion section 110 according to the priority flag.
Fig. 12 shows an example of a hardware configuration of a data exchange system according to an embodiment of the present invention.
The data exchange system 1 according to the embodiment of the present invention is configured as follows: a CPU 1500; a graphics controller 1520; a memory 1530 such as Random Access Memory (RAM), read Only Memory (ROM), and/or flash memory (flash ROM); a storage 1540 for storing data; a read/write device 1545 for reading data from the recording medium and/or writing data to the recording medium; input means 1560 for inputting data; a communication interface 1550 for transmitting and receiving data to and from an external communication device; a chipset 1510, wherein the chipset 1510 connects the CPU 1500, the graphics controller 1520, the memory 1530, the storage device 1540, the read/write device 1545, the input device 1560, and the communication interface 1550 in a manner so as to communicate with each other. The constituent elements of the CPU 1500 and the like are 1 or more CPUs and the like, and may be configured to include a plurality of CPUs and the like.
The chipset 1510 performs transfer of data between the respective constituent elements by interconnecting the memory 1530, the CPU 1500 that performs predetermined processing, and the graphics controller 1520 that controls display of an external display device by accessing the memory 1530. The CPU 1500 operates according to a program stored in the memory 1530, and controls the constituent elements. The graphic controller 1520 displays an image on a predetermined display device based on the image data temporarily stored in the buffer provided in the memory 1530.
The chipset 1510 connects the storage device 1540, the read/write device 1545, and the communication interface 1550. The storage 1540 stores programs and data employed by the CPU 1500 of the data exchange system. Storage 1540 is, for example, flash memory. The read/write device 1545 reads a program and/or data from the storage device 1540 storing the program and/or data, and stores the read program and/or data in the storage device 1540. The read/write device 1545 obtains a predetermined program from a server on the internet, for example, via the communication interface 1550, and stores the obtained program in the storage device 1540.
The communication interface 1550 transmits and receives data to and from an external device via a communication network. When the communication network is not connected, the communication interface 1550 may transmit and receive data to and from an external device without going through the communication network. Further, an input device 1560 such as a tablet computer or a microphone is connected to the chipset 1510 via a predetermined interface.
The data exchange program stored in the storage device 1540 is supplied to the storage device 1540 via a communication network such as a network, or a recording medium such as a magnetic recording medium or an optical recording medium. Next, the data exchange program stored in the storage device 1540 is executed by the CPU 1500. In addition, the data exchange program may be installed in a computer by using a recording medium. The recording medium storing the program may be a non-transitory recording medium such as a CD-ROM or DVD.
The information input program executed by the data exchange system 1 is started in the CPU 1500, and the data exchange system 1 functions as the input data processing unit 10, the output data processing unit 15, the data input unit 100, the conversion database 105, the basic code conversion unit 110, the code presence determination unit 115, the basic database 120, the data conversion unit 125, the attachment unit 130, the information attachment unit 132, the code attachment unit 134, the data output unit 140, the correspondence relation update unit 150, and the information update unit 155 described by fig. 1 to 11.
(effects of the embodiment)
With the data exchange system 1 of the present embodiment, since the correspondence relationship of the data of the respective base databases 120 with respect to the plurality of external databases is defined in the conversion database 105, data exchange can be freely realized between the external databases different from each other. In particular, the data exchange system 1 of the present embodiment includes the base database 120 which forms the basis of the conversion process and has a tree structure defining a hierarchical structure of a plurality of levels, with respect to a standard code or a unified code having a one-dimensional structure in the past. By employing the base database 120, the data exchange system 1 can realize data exchange between arbitrary databases. Thus, the data exchange system 1 can realize data exchange between arbitrary databases by defining the correspondence relation of the data stored in the conversion database 105.
That is, in the data exchange system 1 of the present embodiment, the respective databases of the plurality of external databases can exchange data in a format that enables grasping the content of the data with respect to the external databases of different code systems while maintaining the state of the unique code system. That is, according to the data exchange system 1, data exchange between the data exchange system and any database can be freely performed. Further, since the data exchange system 1 includes the base database 120 including the ambiguous data as the hierarchical structure information having the hierarchical structure, the data exchange system can be used effectively and flexibly by exchanging the data between the areas of the mutually different societies even when the information employed in the areas of the mutually different societies (for example, the plurality of servers using the mutually different code systems) increases and changes with the development of the information communication technology and the complicated progress of the society.
Thus, according to the data exchange system 1, even in the case where the same base code as the base code corresponding to the standard data converted by the base code conversion section 110 is not stored in the conversion database 105 in association with other database identifiers, the standard data can be converted into an appropriate external identification code by detecting the hierarchical structure of the base database 120 in consideration of the so-called difference in granularity. Thus, the data exchange system 1 can use the code systems alone for each of the various external databases using the system, and can realize flexible data exchange.
The embodiments of the present invention have been described above, but the embodiments described above do not limit the invention described in the claims. Note that all combinations of the features described in the embodiments are not necessarily essential to the means for solving the problems of the invention. The technical elements of the above-described embodiments may be used alone or may be applied as a plurality of components such as a program component and hardware.
Description of the reference numerals:
reference numerals 1, 1a denote data exchange systems;
reference numeral 5 denotes a communication network;
reference numeral 10 denotes an input data processing unit;
reference numeral 15 denotes an output data processing unit;
reference numerals 20, 22, 24 denote external databases;
reference numeral 100 denotes a data input section;
reference numeral 105 denotes a conversion database;
reference numeral 110 denotes a basic code conversion section;
reference numeral 115 denotes a code presence judging section;
reference numeral 120 denotes a base database;
reference numeral 125 denotes a data conversion section;
reference numeral 130 denotes an incidental unit;
reference numeral 132 denotes an information attaching portion;
reference numeral 134 denotes a code attaching portion;
reference numeral 140 denotes a data output section;
reference numeral 150 denotes a correspondence updating section;
Reference numeral 155 denotes an information updating section;
reference numeral 1500 denotes a CPU;
reference numeral 1510 denotes a chipset;
reference numeral 1520 denotes a graphics controller;
reference numeral 1530 denotes a memory;
reference numeral 1540 denotes a storage device;
reference numeral 1545 denotes a read/write device;
reference numeral 1550 denotes a communication interface;
reference numeral 1560 denotes an input device.

Claims (11)

1. A data exchange system for implementing data exchange between external databases by using databases having hierarchical structures as intermediaries;
the data exchange system includes:
a base database storing hierarchical structure information represented by a hierarchical structure of a base code of the identification data;
a conversion database storing an external identification code for identifying external data stored in an external database in such a manner as to be associated with a database identifier for identifying the external database and the base code stored in the base database;
a basic code conversion unit that converts an external identification code for identifying one external data from one external database into standard data, the standard data being associated with the basic code, the basic code being stored in the conversion database in association with a database identifier of the one external database;
A code presence judging section for judging whether or not the base code corresponding to the standard data is stored in the conversion database in association with a database identifier identifying another external database;
a data conversion unit that converts the standard data into the external identification code stored in the conversion database in association with the base code corresponding to the standard data and the database identifier identifying the other external database, when the base code corresponding to the standard data is stored in the conversion database in association with the database identifier identifying the other external database;
when the base code corresponding to the standard data is not stored in the conversion database in association with the database identifier for identifying another external database, the standard data is converted into an external identification code which is stored in the conversion database in association with the base code and the database identifier for identifying another external database from the classification position of the base code corresponding to the standard data to the upper classification position, the lower classification position, or the classification position in the same column as the classification position in the hierarchical structure stored in the base database.
2. The data exchange system according to claim 1, wherein the hierarchical information is information represented by the hierarchical structure of the base code, and the base code is configured to include at least one of a base code that identifies data of a higher concept of predetermined data, a base code that identifies data of a lower concept of the predetermined data, and a base code that identifies the predetermined data.
3. The data exchange system according to claim 1 or 2, further comprising an information attaching portion that attaches additional information related to the one external data to the external identification code converted by the data converting portion.
4. The data exchange system according to claim 1 or 2, further comprising a code attaching portion that attaches the one external identification code of the one external data received from the one external database to the external identification code converted by the data converting portion.
5. The data exchange system according to claim 1 or 2, wherein the basic code conversion unit receives the one external data together with a database identifier for identifying another external database and an external identification code for identifying external data of the other external database from the one external database, and adds a set of the database identifier for identifying the other external database and the external identification code for identifying external data of the other external database to the standard data, or does not form the standard data;
The code presence judging unit does not judge whether or not the code presence judging unit is stored in the conversion database in association with the database identifier for identifying another external database;
the data conversion unit treats the external identification code of the external data of the other external database as a converted external identification code.
6. A data exchange system according to claim 1 or 2, wherein said conversion database stores a set of said database identifier identifying the other external database and an external identification code identifying external data of said other external database corresponding to said one external identification code;
the basic code conversion unit refers to the conversion database, and adds the group to the standard data, or does not form the standard data;
the code presence judging unit does not judge whether or not the conversion database is stored in association with the database identifier for identifying another external database;
the data conversion unit treats the external identification code of the external data of the other external database as a converted external identification code.
7. A data exchange system according to claim 1 or 2, wherein said conversion database stores a database identifier of one of said external databases and a set of said one external identification code corresponding to an external identification code identifying external data of said other external database;
the data conversion unit searches the conversion database based on the database identifier and the external identification code stored in the standard data, and treats the external identification code as a converted external identification code when the database identifier stored in the standard data, the database identifier corresponding to the external identification code, and the external identification code are stored in the conversion database before the code presence determination unit determines that the external identification code is present.
8. The data exchange system according to claim 1 or 2, wherein, in the case where the base code corresponding to the one external data is directly received from the one external database,
the basic code conversion unit does not refer to the conversion database;
the code presence judging unit directly uses the received base code to judge.
9. A data exchange system for implementing data exchange between external databases by using databases having hierarchical structures as intermediaries;
the data exchange system includes: an input data processing unit that processes external data stored in an external database; an output data processing unit that processes data supplied to other external databases according to the processing in the input data processing unit;
the input data processing unit includes:
a base database storing hierarchical structure information represented by a hierarchical structure of a base code of the identification data;
a conversion database for storing an external identification code for identifying external data in association with a database identifier for identifying the external database and the base code stored in the base database;
a basic code conversion unit that converts an external identification code for identifying one external data from one external database into standard data, the standard data being associated with the basic code, the basic code being stored in the conversion database in association with a database identifier of the one external database;
The output data processing unit includes a data conversion section that:
when the base code corresponding to the standard data is stored in the conversion database in association with a database identifier for identifying the other external database, converting the standard data into the external identification code stored in the conversion database in association with the base code corresponding to the standard data and the database identifier for identifying the other external database;
when the base code corresponding to the standard data is not stored in the conversion database in association with the database identifier for identifying the other external database, the standard data is converted into an external identification code which is stored in the conversion database in association with the base code and the database identifier for identifying the other external database, from the classification position of the base code corresponding to the standard data to the upper classification position, down to the lower classification position, or in association with the classification position in the same column as the classification position, in the hierarchical structure stored in the base database.
10. A data exchange method of a data exchange system, the data exchange system uses a database with a hierarchical structure as an intermediary to realize the data exchange of transmission among external databases;
the data exchange system includes:
a base database storing hierarchical structure information represented by a hierarchical structure of a base code of the identification data; a conversion database for storing an external identification code for identifying external data stored in an external database in association with a database identifier for identifying the external database and the base code stored in the base database;
the data exchange method of the data exchange system comprises the following steps:
a basic code conversion step of converting an external identification code for identifying an external data from an external database into standard data, the standard data being associated with the basic code, the basic code being stored in the conversion database in association with a database identifier of the external database;
a code presence judging step of judging whether or not the base code corresponding to the standard data is stored in the conversion database in association with a database identifier that identifies another external database;
A data conversion step of, when the base code corresponding to the standard data is stored in the conversion database in association with the database identifier for identifying another external database, converting the standard data into the external identification code stored in the conversion database in such a manner that the base code corresponding to the standard data and the database identifier for identifying another external database are associated with each other;
when the base code corresponding to the standard data is not stored in the conversion database in association with the database identifier for identifying another external database, the standard data is converted into an external identification code which is stored in the conversion database in association with the base code and the database identifier for identifying another external database from the classification position of the base code corresponding to the standard data to the upper classification position, the lower classification position, or the classification position in the same column as the classification position in the hierarchical structure stored in the base database.
11. A data exchange program for a data exchange system for implementing transmission data exchange between external databases by using databases having hierarchical structures as intermediaries;
the data exchange system includes:
a base database storing hierarchical structure information represented by a hierarchical structure of a base code of the identification data; a conversion database for storing an external identification code for identifying external data stored in an external database in such a manner as to be associated with a database identifier for identifying the external database and the base code stored in the base database;
in a computer, the following steps are realized:
a basic code conversion function of converting an external identification code for identifying an external data from an external database into standard data, the standard data being associated with the basic code, the basic code being stored in the conversion database in association with a database identifier of the external database;
a code presence judging function of judging whether or not the base code corresponding to the standard data corresponds to a database identifier for identifying another external database, and storing the base code in the conversion database;
A data conversion function of converting the standard data into the external identification code stored in the conversion database in association with the base code corresponding to the standard data and the database identifier identifying the other external database, when the base code corresponding to the standard data is stored in the conversion database in association with the database identifier identifying the other external database;
when the base code corresponding to the standard data is not stored in the conversion database in association with the database identifier for identifying another external database, the standard data is converted into an external identification code which is stored in the conversion database in association with the base code and the database identifier for identifying another external database, from the classification position of the base code corresponding to the standard data to the upper classification position, down to the lower classification position, or in association with the base code of the classification position in the same column as the classification position, in the hierarchical structure stored in the base database.
CN201780047417.5A 2016-05-31 2017-05-24 Data exchange system, data exchange method, and data exchange program Active CN109564541B (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
JP2016108194 2016-05-31
JP2016-108194 2016-05-31
PCT/JP2017/019325 WO2017208922A1 (en) 2016-05-31 2017-05-24 Data exchange system, data exchange method, and data exchange program

Publications (2)

Publication Number Publication Date
CN109564541A CN109564541A (en) 2019-04-02
CN109564541B true CN109564541B (en) 2023-09-01

Family

ID=60478587

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201780047417.5A Active CN109564541B (en) 2016-05-31 2017-05-24 Data exchange system, data exchange method, and data exchange program

Country Status (3)

Country Link
JP (1) JP6842071B2 (en)
CN (1) CN109564541B (en)
WO (1) WO2017208922A1 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3633514B1 (en) * 2017-05-24 2022-02-16 Toshin System, Ltd. Data exchange system, data exchange method, and data exchange program
WO2019176824A1 (en) * 2018-03-14 2019-09-19 日本電気株式会社 Data creator, data classifier, data acquisition system, data creation method, data classification method, and recording medium
CN113656400B (en) * 2021-07-08 2024-02-27 上海二三四五网络科技有限公司 Characteristic data encoding method and device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH05165689A (en) * 1991-12-18 1993-07-02 Oki Electric Ind Co Ltd Information processing system
GB0016546D0 (en) * 1999-07-07 2000-08-23 Matsushita Electric Ind Co Ltd Data management method and system and apparatus used therein
EP1093061A1 (en) * 1999-10-14 2001-04-18 SAP Aktiengesellschaft Integrated database federation system
JP2008243193A (en) * 2007-02-26 2008-10-09 System Produce:Kk Data management system

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7693917B2 (en) * 2001-11-30 2010-04-06 Intelligent Medical Objects, Inc. Method for adaptive data management
JP2003216654A (en) * 2002-01-21 2003-07-31 Beacon Information Technology:Kk Data management system and computer program
JP4181080B2 (en) * 2004-03-31 2008-11-12 株式会社東芝 Hierarchical database management system, hierarchical database management method, and hierarchical database management program

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH05165689A (en) * 1991-12-18 1993-07-02 Oki Electric Ind Co Ltd Information processing system
GB0016546D0 (en) * 1999-07-07 2000-08-23 Matsushita Electric Ind Co Ltd Data management method and system and apparatus used therein
EP1093061A1 (en) * 1999-10-14 2001-04-18 SAP Aktiengesellschaft Integrated database federation system
JP2008243193A (en) * 2007-02-26 2008-10-09 System Produce:Kk Data management system

Also Published As

Publication number Publication date
JPWO2017208922A1 (en) 2019-03-28
CN109564541A (en) 2019-04-02
WO2017208922A1 (en) 2017-12-07
JP6842071B2 (en) 2021-03-17

Similar Documents

Publication Publication Date Title
Wang et al. A graph-based context-aware requirement elicitation approach in smart product-service systems
US8190556B2 (en) Intellegent data search engine
US8249954B2 (en) Third-party certification using enhanced claim validation
US9606970B2 (en) Web browser device for structured data extraction and sharing via a social network
KR102354395B1 (en) Computerized systems and methods for product integration and deduplication using artificial intelligence
US8700494B2 (en) Identifying product variants
KR101806169B1 (en) Method, apparatus, system and computer program for offering a shopping information
US11194832B2 (en) Normalization of unstructured catalog data
US20080072140A1 (en) Techniques for inducing high quality structural templates for electronic documents
CN110352427B (en) System and method for collecting data associated with fraudulent content in a networked environment
US20090125529A1 (en) Extracting information based on document structure and characteristics of attributes
US20090248707A1 (en) Site-specific information-type detection methods and systems
US9501474B2 (en) Enhanced use of tags when storing relationship information of enterprise objects
US20230214895A1 (en) Methods and systems for product discovery in user generated content
CN109564541B (en) Data exchange system, data exchange method, and data exchange program
JP5711440B1 (en) Information processing apparatus, information processing method, and information processing program
CN109716377A (en) The improvement that login page generates
US10636076B2 (en) Search result enhancement component for interest queues
US20190213543A1 (en) History management system and history management method
CN110998542B (en) Data exchange system, data exchange method, and data exchange program
US20200226378A1 (en) Methods and systems for tagged image generation
CN109948015B (en) Meta search list result extraction method and system
US20200226167A1 (en) Methods and systems for dynamic content provisioning
Usman et al. Predictive Analysis on Large Data for Actionable Knowledge: Emerging Research and Opportunities: Emerging Research and Opportunities
KR102639788B1 (en) Apparatus for managing health functional food based on artificial intelligence and method thereof

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant