JP2005196357A - Hierarchial database management system, method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To easily post instances from one classification to another different classification. <P>SOLUTION: This hierarchial database management system includes a server data management part 3 that, based on a common code for uniquely identifying all attributes included in the first classification, i.e., the side from which instances are posted, and the second classification, i.e., the side to which the instances are posted, determines whether or not first attributes belonging to the first classification and second attributes belonging to the second classification have any common attributes; and a client data management part 12 that, based on this determination, displays the names of third attributes determined to be common to the first and second attributes as well as the common code. The server data management part 3 further includes a means for updating a dictionary DB 1 and an instance DB 2 by posting the instances that belong to the third attributes from the first classification to the second classification. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a hierarchical database management system, a hierarchical database management method, and a hierarchical database management program for transferring data between classifications (classes) of a hierarchy of a hierarchical database.

  In general-purpose OSs such as Microsoft's operating system (OS) Windows (registered trademark), UNIX (registered trademark), and LINUX (registered trademark), a tree-like directory structure and file structure are visually displayed to the user. A tree display is employed as a graphic user interface (GUI) for guiding and moving (navigating) a user to a specific directory or file.

  However, between each node of this tree display, there is no relationship of inheritance of attributes or inclusion or subset relationship between the information (file etc.) contained in the upper node and the information contained in the lower node. Absent. The nodes on the tree starting from the root node merely represent that folders for storing information such as files, that is, containers of information are simply interconnected in a tree shape. This type of structure is called a hierarchical directory structure in the description of the present invention, and is a different concept from a hierarchical database. A system for managing a hierarchical database is referred to herein as a hierarchical database management system (HDBMS).

  On the other hand, in a database having a hierarchical structure in which the lower level inherits the attributes of the upper classification, such as an object-oriented database (OODB) or object-relational database (ORDB), the structure in which the attributes increase in the lower classification according to inheritance. Have. Inheriting this higher level attribute to the lower level is usually called “inheritance”. Such techniques are described in many other documents such as “Object-Oriented Concepts, Databases, and Applications, Edited by Won Kim, 1989, ACM Pres” (Non-patent Document 1). Also, in the literature for object-oriented databases, classification in a hierarchy is often referred to as “class”. On the other hand, in an object-relational database (ORDB), this is equivalent to a table that allows inheritance, and the attributes from the upper table to the lower table, that is, the columns constituting the upper table, between tables having a hierarchical relationship. Header information is inherited to the lower table. In the present specification, both are referred to as a “hierarchical database”. Data having the same attribute type belonging to the classification of each hierarchy is called “instance”, and the set is called “population” of data.

  In a database having a hierarchical structure in which the lower level inherits the attributes of the higher class, represented by the object-oriented database, the attribute has a structure in which the attributes increase in the lower level according to inheritance. Therefore, when data is transferred or moved between two classifications belonging to the object-oriented database, it is complicated to check the transfer destination and the transfer source by the name of each attribute. In addition, ISO13584 (Parts Library) Standard-Volume 24 (Non-patent Document 2) is capable of expressing values in multiple languages such as Japanese, French, and English for character-type attributes with language-dependent values. As for, differences in attributes are also determined by codes that have essentially no linguistic meaning, and name characters that depend on the language such as a normal relational database (RDB) or ORDB. It is impossible to determine the identity of an object by a column.

In addition, when collating only by name, the data type is different even if the name is the same, and in practice it may not be possible to assign a value. For this reason, the mapping tool is actually used to display the header information of the target table and the source table, that is, the attribute name and attribute data type, and the individual attributes on the source side to be posted. On the other hand, the user selects and sets attributes on the target side individually to create mapping and transfer data.
Object-Oriented Concepts, Databases, and Applications, Edited by Won Kim, 1989, ACM Press

  As described above, in the conventional technique, it is not easy to transfer an instance between two categories having different attributes.

  The present invention has been made to solve the above-described problems, and the object of the present invention is to provide a hierarchical database management system and a hierarchical database management method that facilitate the transfer of instances from one to the other between two different classifications. And providing a hierarchical database management program.

  According to an aspect of the present invention, there is provided a hierarchical database management system that manages a hierarchical database having a hierarchical structure in which a lower order inherits an attribute of an upper classification, and includes all of the first classification and the second classification. Means for determining whether or not the first attribute belonging to the first category and the second attribute belonging to the second category have a common attribute based on a common code for uniquely identifying the attribute; Means for displaying the name of the third attribute determined to be common to the first attribute and the second attribute and the common code, and the instance belonging to the third attribute from the first classification to the second attribute There is provided a hierarchical database management system characterized by comprising:

  Further, according to another aspect of the present invention, there is provided a hierarchical database management method for managing a hierarchical database having a hierarchical structure in which a lower order inherits an attribute of a higher level classification, and includes a first classification and a second classification. Determining whether the first attribute belonging to the first classification and the second attribute belonging to the second classification have a common attribute based on a common code that uniquely identifies all the included attributes; The name of the third attribute determined to be common to the first attribute and the second attribute by the determination and the common code are displayed, and the instance belonging to the third attribute is displayed from the first classification to the second attribute. A hierarchical database management method is provided, which is characterized by posting to the classification of

  According to another aspect of the present invention, there is provided a hierarchical database management program for causing a computer to execute management of a hierarchical database having a hierarchical structure that inherits the attributes of the upper classification. Based on a common code that uniquely identifies all attributes included in the first category and the second category, the first attribute belonging to the first category and the second attribute belonging to the second category are common Means for determining whether to have an attribute to be used, means for displaying the name of the third attribute determined to be common to the first attribute and the second attribute and the common code by the determination, and the third There is provided a hierarchical database management program characterized by causing an instance belonging to the attribute to function as means for transferring from the first classification to the second classification.

  According to the present invention, it is easy to transfer an instance from one to the other between two different classifications.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a functional block diagram of a hierarchical database management system 100 according to an embodiment of the present invention. The hierarchical database includes a dictionary database (DB) 1 and an instance database (DB) 2. The hierarchical database management system 100 is roughly composed of a server side device, a client side device, and a network 11. The network 11 is a digital network based on the TCP / IP protocol, for example. For example, different IP addresses are assigned to the server side device and the client side device.

  The server side device includes a dictionary DB1, an instance DB2, a server side data management unit 3, a management information storage device 3a, an instance reading unit 4, an instance writing unit 5, an instance file 6, and a dictionary parser 7. A dictionary file 9 and a dictionary writing unit 10 are shown.

  The client side device includes a client side data management unit 12, an instance page 13, an instance reading unit 14, an instance writing unit 15, an instance file 16, a class tree 17, a dictionary parser 18, and a dictionary writing unit. 19, dictionary file 20, dictionary search input unit 21, class information 22, instance search input unit 23, instance information 24, pointing device 25, keyboard 26, display device 27, transcription unit 8, This is indicated by the external processing unit 28.

  Under the control of the server-side data management unit (Data Manager) 3, the dictionary file 9 is read via the server-side dictionary parser 7 and stored in the dictionary DB 1 described above. The contents of the dictionary DB 1 are written out as a dictionary file 9 through the dictionary writing unit 10 under the control of the server-side data management unit 3. Also, the instance file 6 is read via the instance reading unit 4 and stored in the instance DB 2. The instance data stored in the instance DB 2 is written out as an instance file 6 through the instance writing unit 5 under the control of the server-side data management unit 3.

  Similar processing can be performed from the client. The client-side dictionary file 20 is read via the client-side dictionary parser 18 under the control of the client-side data management unit 12, and further sent to the server-side data management unit 12 via the network 11, and the dictionary DB1 described above. Stored in On the contrary, the dictionary data stored in the server-side dictionary DB 1 is read out by the control of the server-side data management unit 3 and sent to the client-side data management unit 12 via the network 11, so that the client side The dictionary file 20 is written through the dictionary writing unit 19.

  Similarly, the client-side instance file 16 is read via the client-side instance reading unit 14 under the control of the client-side data management unit 12 and further sent to the server-side data management unit 12 via the network 11. Stored in the instance DB2. Conversely, the dictionary data stored in the instance DB 2 on the server side is read out under the control of the data management unit 3 on the server side and sent to the data management unit 12 on the client side via the network. The instance file 16 is written via the instance writing unit 15.

  The dictionary information read from the server side is held in the client-side memory as the class tree 17 by the client-side data management unit 12 and is output to the display device 27 as the class information 22. Similarly, the instance information read from the server side is held as the instance page 13 on the client side memory, and is output to the display device 27 as the instance information 24.

  When an inquiry about a dictionary content other than the currently held dictionary or instance and an instance is input through the dictionary search input unit 21 and the instance search input unit 23 using the keyboard 26 and a pointing device 25 such as a mouse, respectively. This is transmitted to the server-side data management unit 3 through the network 11 under the control of the client-side data management unit 12, and necessary dictionary data or instance data is read from the dictionary DB1 or instance DB2, and the client-side data The class tree 17 on the client-side memory is updated via the management unit 12 or the instance page 13 on the client-side is updated, and the results are obtained as class information 22 and instance information 24, respectively. Is output to Isupurei device 27.

  As described above, the client-side data management unit 12, the display device 27, the pointing device 25, and the components interposed therebetween realize the GUI function in the client-side device.

  FIG. 2 is a diagram showing another example of the hierarchical database management system 100 of FIG. 1, and is shown as a hierarchical database management system 200 below.

  Although FIG. 1 shows the configuration of an embodiment of a hierarchical database management system that is divided into a server unit and a client unit via a network 11, in the stand-alone type configuration of FIG. The data management unit 3 and the client-side data management unit 12 are the same, and are simply indicated as the data management unit 201. Also, the dictionary and instance reading and writing sections have the same contents. Components common to those in FIG. 1 are denoted by the same reference numerals, and detailed description thereof is omitted.

  In addition, even when physically implemented by one machine, the case of using the TCP / IP protocol is included in the configuration of FIG. Further, in the following description, the description will be based on the hierarchical database management system 100, but the content described below for the hierarchical database management system 200 is only a difference between whether or not it is via the network 11. However, the present invention can be appropriately modified and applied by those skilled in the art.

  In the hierarchical database management systems 100 and 200, two code systems of an internal code and an external code are used to identify a class, an attribute, an instance, and the like of the hierarchical database.

  The internal code is a code used in the dictionary DB1 and the instance DB2.

  The external code is a common code that uniquely identifies all classifications, that is, classes of the posting source and the posting destination. In order to use this external code together with the internal code, it is used in any processing device, for example, the server-side data management unit 3 or the client-side data management unit 12 in the example of FIG. 1, and the data management unit 201 in the example of FIG. A one-to-one correspondence table between the outer code and the inner court is arranged. In the display of the code touched by the user, the external code is displayed, and this embodiment includes an implementation using the internal code for identifying the internal code of the system.

As described above, reasons for converting the external code into the internal code include the following (1) to (3), for example.
(1) To avoid this inconvenience when the code length allowed as an external code is too long and it is inconvenient for efficient recording and storing in a memory or register in the system.
(2) To create an index (index) often used in database implementation, it is faster to convert the code into an integer (but not necessarily in decimal) or reverse the order of the digits forming the code. .
(3) It is desirable to encrypt the code used internally for system security.

  If the correspondence between these internal codes and external codes is held in a table or list, different codes can be used for the internal representation and external representation of the codes.

  Also, the correspondence does not necessarily have to be held in a table. By storing the code system corresponding to the internal code and the external code in the dictionary DB 1 and the instance DB 2 in advance, the processing system using the internal code is used for the process that does not need to be displayed to the user. For processing that needs to be displayed, a processing system using an external code may be used.

  Code formats include those that simply consist of property codes, those that simultaneously indicate the code of the class to which the property belongs, and those that simultaneously indicate the information provider code as defined in the PLIB standard (ISO13584 Parts Library). As a description based on the external code, for example, ISO13584-26 and the original ISO-6523-1 (ISO6523 Information Technology-Structure for the identification of organizations and organizations parts --- Part1 Identification Of Organization Identification Scheme, 1998) If you follow the notation, the dot notation, ie the dot between codes'. By concatenating 3 codes using ', it is possible to completely specify the attribute.

supplier_code.class_code.property_code
An IP address or the like may be used as supplier_code (here, “supplier” refers to an information provider), but if it completely complies with the PLIB standard (Non-Patent Document 2), the information provider code, the class code, The property codes are called supplier BSU, class BSU, and property BSU, respectively. BSU is an abbreviation for Basic Semantic Unit, and it is stipulated that a code having no meaning as a language is used. For example, it means that you must not use a class classification code or attribute code that can be estimated from the code, such as Motor_001 for a class classification code that represents a motor and Rotation_001 for an attribute that represents the rotation speed. .

  It is recommended to use something like TOPAS_P001 instead. This is because if the meaning is presumed from the language, it seems convenient at first glance, but it depends on the background of the user's background, culture, customs, and the context of the industry. This is because they are different. For example, what is called a motor includes a car engine, a rocket engine, an AC motor, and a DC motor, and the number of revolutions can be defined as per second, per minute, and per hour. Therefore, it is forbidden to use linguistically meaningful character strings and words that tend to give preconceptions to the code itself that is the sole and absolute basis of identity. Of course, the code itself does not have a linguistic meaning, but there is something called Preferred_Name (recommended name) separately from the code, which plays a common name or mnemonic role. Of course, even those having the same recommended name are recognized as different attributes if the attribute code (property BSU) is different. Classes are distinguished by what attribute pairs they have. That is, when the two classes C1 and C2 are described using different Class_BSUs, at least one attribute is different between the two classes. On the other hand, definitions for classification and attributes must be clearly described in natural language. If you follow the PLIB Standards Volume 42 (Non-Patent Document 2), for example, a dictionary provided in English, French, Japanese, and four German languages must be defined as equivalent equivalent translations of each other. Therefore, the user understands the definition object from the description itself given to the definition. Needless to say, even in that case, in practice, for example, it is natural to provide only English and Japanese, and for French and German, it is natural to prepare a device such as displaying English text in different fonts and colors.

  In this embodiment, in order to use the features of the PLIB standard represented by the above, the standard code system incorporating some or all of the characteristics is referred to as the above common code system, that is, “Property BSU defined in ISO13584 as its representative. Included in the code system indicated by "Globally unique code". IEC61360-2 (second volume) takes the form of an independent standard issued by IEC, but the main body of the standard is the same as ISO13584, and IEC61360-4 (fourth volume) This is a high-level dictionary for the classification of electronic and electrical products used. IEC61360-1 (first volume) describes the principles regarding classification or description of classes and attributes. Therefore, corporate classifications and industry classifications that use some or all of the standard classification systems that use or apply them are also unique within standardization organizations and corporate classification systems by simplifying or using the above-mentioned ISO13584. Included in those using the "standard code attached to attributes".

  However, of course, these standards themselves do not disclose new concepts and devices described in this embodiment. That is, there is no disclosure of a mechanism for automatically collating attributes in data transfer between classes, a mechanism for notifying registration of new data based on conditions registered via the Internet between different sites, and a mechanism for transferring data.

  Note that, according to the hierarchical database management system 100 of FIG. 1, the internal code may be used in, for example, the server side device, and the client side device may use the external code. In this case, transmission / reception may be performed between the networks 11 using an internal code or using an external code.

  FIG. 3 is a diagram illustrating an example of a display screen using a GUI according to the present embodiment. Based on the common attribute code extracted by the server-side data management unit 3 or the client-side data management unit 12 based on the common code, the classification class “sedan type car” that was browsed when the user activated the transcription function , And a common attribute of the classification class “car estimate class” that is the transfer destination in the class tree 17 displayed in the class tree display areas 30 and 32a is shown in the list 31 in FIG. The classification classes “sedan type automobile” and “automobile estimation class” belong to the same classification system dictionary “automobile dictionary”. In the following, the classification class or instance of the transfer source is called a source, and the classification class or instance of the transfer destination is called a target.

  While looking at the list 31, the user transcribes what is not transcribed from the sedan class instance to the “car estimate class” by the selecting means (hereinafter simply referred to as “selecting means”) using the pointing device 25 or the keyboard 26. The prohibition (protection) display 32b can be described in the list 31 in association with the attribute. In FIG. 3, the protection of the attribute value of the automobile estimation class that is the target of transcription is specified by setting the entry prohibition mark of the road traffic sign by the GUI operation.

  When posting from the classification class “sedan type automobile” to another classification class “automobile estimation class”, it is possible to specify an attribute to be protected among the attribute values in the “automobile estimation class”. Of course, contrary to the example in FIG. 3, the user may designate the attribute to be actually transferred by the selection means.

  Moreover, the classification system which can be simultaneously published, that is, the dictionary is not limited to one. In FIG. 3, “organization dictionary”, “electric appliance dictionary”, “asset dictionary” and the like are indicated by reference numeral 29 in the display frame of the same classification tree in addition to “car dictionary”. In addition to the classification class specified for the transfer source, a classification system dictionary different from the transfer source classification system dictionary can be specified for the transfer destination. In this case, transcription can be performed between different classification system dictionaries.

  FIG. 4 is a diagram showing a GUI screen display example for explaining processing when the data type is common even when the source side and target side attribute codes are different, or when the code added to the data type is common It is. In such a case, the user designates the attribute name or code of the source side to be substituted with respect to the target side attribute name or code via the GUI, for example, on the screen using the selection means. This is an example. In FIG. 4, the attribute code having the same data type (character string type in FIG. 4) in the “sedan class” attribute is shown on the right side of the attribute 34 “handled vehicle type” indicated by the attribute code “TOPAS_P0171”. Is shown in the list 33 of FIG. In the list 33, the user selects one attribute using the selection means, thereby specifying the mapping between the actual attributes. In the example of FIG. 4, the attribute data type indicating the attribute “car type / model”, which is different from the attribute 34 “handled vehicle type” indicated by “TOPAS_P0171”, is the same as the data type of the attribute 34. can do. The attribute name and code between the mapped source and target are posted by the server-side data management unit 3. Note that the mapping relationship is displayed by associating the source and the target with reference numeral 36 in FIG. Reference numeral 35 denotes a target classification class display area.

  FIG. 5 shows that when the data type can be substituted from the source side to the target side, the name or code of the source side attribute to be substituted by the user via the GUI with respect to the name or code of the attribute 41 on the target side. It is a figure which shows the example of a screen of the process in the case of designating from on a screen. The screen includes an attribute display area 40 on the target side and an attribute display area 42 on the source side. Reference numeral 39 denotes a copy permission flag indicating that the attribute of the target can be transferred.

  As shown in FIG. 5, for an attribute “handled vehicle model” indicated by a code 41 “TOPAS_PT0171” having a data type “STRING” type, an integer ( A source candidate 44 including “store number” having a data type “INTEGER” is shown. This is because substitution is possible by treating an integer as a character string. In fact, most data types (REAL, DATE, etc.) can be converted to variable-length character string types. In this way, even if the data types on the source side and the target side are different, if the assignment from the data type on the source side to the data type on the target side is possible, the transcription can be performed.

  FIG. 6 is a flowchart illustrating an example of a basic procedure of a transcription process for transcribing attribute data based on a matching attribute code. Regarding the processing on the source side, the server-side data management unit 3 collects the attributes of the source selected by the user using the selection means via the network 11 (S4), and obtains the attributes of the source (S5).

  On the other hand, regarding the processing on the target side, first, the user selects a target from the class tree 17 displayed on the class tree display area 30 shown in FIG. And the server side data management part 3 which received the selected target via the network 11 collects the attribute of the target based on the target (S2), and obtains the attribute of the target (S3).

  The server-side data management unit 3 determines whether or not both attributes have a common attribute code based on the collected source attribute and target attribute. Are collected as a common set (S6, S7). Information such as the attribute name, data type, and unit corresponding to the attribute code included in the obtained common set is transmitted to the client-side data management unit 12 via the network 11 and displayed on the display device 27. After the display of the common set, for example, when the user is prompted to input the approval of the posting and the user selects the approval using the selection means, the posting request is sent from the client side data management unit 12 via the network 11 to the server side. The attribute code, attribute name, data type, unit, etc. that are transmitted to the data management unit 3 and defined in the common set by the server side data management unit 3 are transferred to the dictionary DB 1 and the instance DB 2.

  Of course, after the information is displayed to the user, when the user does not input consent, the user may cancel the mapping.

  FIG. 7 is a flowchart illustrating an example of a basic processing procedure for selecting a transcription candidate using a GUI. 7, source attribute collection (S14, S15), target selection and target attribute collection (S11-S13), common set collection (S16, S17), common set information display (S18), value The execution of copying (S20) is common to (S1 to S9) in FIG. In FIG. 7, in the information display of the common set, in (S18), the attribute name and data related to the common set are displayed as candidates for the actual mapping by the user. Based on the display of the mapping candidates, the user selects an attribute actually desired for mapping by the selection means, for example, as indicated by reference numeral 46 in the display screen shown in FIG. 9 (S19). The selected attribute is transmitted from the client side data management unit 12 to the server side data management unit 3 via the network 11. The server-side data management unit 3 performs transcription only for the selected attribute.

  FIG. 8 is a diagram showing a flowchart of a basic processing procedure of attribute data transfer based on attribute code matching. The processing (S21 to S26) from the collection of the target attribute to the collection of the source attribute is common to the processing (S11 to S15) shown in FIG.

  That is, for each attribute of the target (class or table) in (S30), the user can select from the candidates presented by the hierarchical database management system 100 that can be mapped to the attribute on the source side (class or table). Select the one that actually performs the mapping. The mapping is defined by this selection, and the instance is transferred from the source side to the target in (S31).

  More specifically, in the example of FIG. 8, among the collected source and target attributes, the source attributes that can be substituted are collected for each individual attribute of the target (S27). When the attributes of all the targets are not collected (S28), the process is repeated (S27) for the uncollected targets. When the attributes of all targets are collected (S28), the hierarchical database management system, data type, unit, etc. of the attributes common to the target and the source are displayed on the display device 27. Then, similarly to (S19) in FIG. 7, the user designates what is actually transcribed by using the selection means on the GUI (S30). The selected transfer target is transmitted from the client side data management unit 12 to the server side data management unit 3 via the network 11. The server-side data management unit 3 performs transcription for the obtained transcription target (S31).

  FIG. 9 is a diagram showing a GUI screen display example of a posting line selection function for displaying instances to be actually transferred in a table format and selecting an instance to be transferred from among them. FIG. 8 shows an example of activation using a mouse. In FIG. 9, the instance of the three lines indicated by reference numeral 46 is marked, and the system changes the character color and typeface, changes the frame color, or exaggerates the check box and the user selects the mouse. There are various methods such as entering a check mark. Of course, this marking may be performed on the rows in the class or table before being narrowed down by searching with the search function of the database management system (DBMS), or the class or table after narrowing down the target by searching. You may go to the middle row. The server-side data management unit 3 performs transcription for the selected instance of the row.

  FIG. 10 is a diagram showing a flowchart of a basic processing procedure of the transfer function between classes.

  The processing up to the collection of target and source attributes (S41 to S46), the collection and display of common attributes based on the collected attributes, and the designation by the user to be transferred (S47 to S50) are the processing shown in FIG. S21 to S30).

  In the example of FIG. 10, after narrowing down the instances to be transferred in (S50), in (S51), the server-side data management unit 3 selects the selected row, that is, a unit called a parcel in which the instances are grouped together. Collectively, this is pooled on the management information storage device 3a such as a disk or server memory. In (S53), on the client side having the editing processing authority, for example, the parcel is selected by the user by dragging and dropping the parcel symbol or the like to the target class or the like using the mouse, and the target is designated. Then, the parcel creation notification is read from, for example, the management information storage device 3a (for example, FIFO buffer) by the notification queue (S59), so that the server-side data management unit 3 transmits the parcel information to the client side. For example, a parcel list is displayed on the display device 27 (S53). Here, the server-side data management unit 3 can restrict the editing process authority by not transmitting the parcel list to the client-side data management unit 12 in the case of access from a client device that does not have the editing process authority.

  In the parcel list, information on a plurality of attributes and instances included in the parcel is displayed in a list format. The user selects, from the displayed parcel list, the attribute or instance desired to be transferred by the selecting means (S54).

  Then, parcel information related to the attribute or instance desired to be transcribed is displayed on the display device 27 (S55). Then, the user determines the parcel to be actually transcribed based on the display screen by the selection means (S56). Information relating to the determined posting, that is, source and target information, is transmitted from the client-side data management unit 12 to the server-side data management unit 3 via the network 11. The server-side data management unit 3 actually performs the transcription based on the obtained information relating to the transcription (S57).

  Of course, in the implementation form, the parcel and the notification can be combined and included in the parcel pooled in (S58).

  In addition, the server-side data management unit 3 performs the transfer date and time, the user name, or the name or ID of the group to which the user belongs, or the information attached to the transferred parcel described in the notification or the parcel itself, At this time, secondary information such as names and symbols assigned to the transcription units is associated with the parcel and stored in the management information storage device 3a. And the accompanying information of these parcels is displayed together with the parcels. This is aimed at facilitating the determination as to whether or not the user's corresponding writing is allowed at the target. For example, the date and time of posting is stored in association with the information attached to the parcel, and when selecting the parcel, the selection unit specifies the time range to be edited on the display device 27, Parcel processing within a specified time range can be executed.

  FIG. 11 is a diagram illustrating an example of a display screen of a transfer line selection function using a GUI. In FIG. 11, as a result of selecting and extracting an instance to be transferred and related class and attribute information on the source side without specifying a target and collecting them into a parcel, this extraction operation ends and a symbol 47 symbolizing this unit A parcel icon or symbol as shown in FIG. By using the pointing device 25 such as a mouse to drag and drop the icon 47 to a desired class, mapping associated with actual transcription is activated. In FIG. 11, since it is difficult to guide the relatively large icon 47 to the small class icon 48a, the post box 48b for acceptance is opened and displayed when the class icon 48a is clicked. ing. By moving the icon 47 to the post box 48b using the pointing device 25, the target class can be specified.

  Of course, the parcel icon 47 may be directly brought into the target class icon 48a.

  FIG. 12 is a diagram illustrating an example of a screen for explaining a transfer line selection function using a copy instance value direct designation GUI. A value is obtained by marking the target from the target attribute list 52 of FIG. 12 by using the pointing device 25 such as a mouse by changing the background color of one or a plurality of attributes and selecting the button 51 with the selection means. Tells the system to do a direct assignment of. This instruction is transmitted from the client-side data management unit 12 to the server-side data management unit 3, and transcription based on the instruction is performed. That is, it becomes possible for the user to directly describe and instruct values to be written for the selected attribute or attributes.

  FIG. 12 also shows an embodiment of a mapping saving function. In the figure, reference numeral 49 denotes a mapping read button for instructing reuse of mapping, and reference numeral 50 denotes a mapping saving button for instructing saving of mapping. When the user selects the mapping save button 50 using the selection means, various information specified by the mapping, such as the class code, the attribute, and the mapping relationship for each of the source and target, is saved in the management information storage device 3a, for example. This stored information can be easily recalled by selecting the read mapping button 49. By calling, a screen as shown in FIG. 12 is displayed.

  Further, in the hierarchical database management system 100 described in the present embodiment, since the attribute is inherited from the upper class to the lower class, the saved mapping file is stored in each of the target and source subclasses in the saved mapping file. It can be used. When the posting function is started in a certain class C1, the class C1 is used as a source, and the class C2 is actually selected as a target for posting, all mapping files targeting the upper class C3 of the class C2 created for the class C1 are used. It becomes possible. This is because, for example, each time the server-side data management unit 3 receives the designation and posting of the source and target from the client side, the class code included in the source and target to be designated or posted, or the upper level of this class code The class code of the class is compared with the class code included in the stored mapping information, and if there is a match, the mapping information may be displayed.

  Accordingly, when the mapping read button 49 is pressed for reading, the list is displayed, and the user selects from the list.

FIG. 13 is a conceptual diagram for explaining an embodiment of a transcription function including external processing.
The transcription unit 8 in FIG. 1 is based on the processing specified by the external function between the source and the target based on the information on the source and target acquired from the client-side data management unit 12 and the external function acquired from the external processing unit 28. Make a posting.

  The external process has an output data type of the external process and a data type for each of the input parameters. A data type code having the same code system as the common code (this is called Datatype_BSU in the PLIB) is assigned to the data type of the dictionary attribute.

  For example, for one attribute of the class 63 on the target side, for example, the attribute 54 having a common code “P_BSU3” in FIG. 13, the data type code T1 of the attribute 54 and the output data are regarded as attributes. If the code T1 of the data type indicated by reference numeral 56 matches, the output of the external processing 55 can be substituted for the class 53 and the attribute on the target side. Therefore, this time, the input parameter list 58 of the external process 55 can be regarded as an attribute and mapped from the attribute 61 of the source class 60.

  In order to actually realize this, a list of assignability between data types as shown in FIG. 14 and a list of output data types and input parameters of external processing functions as shown in FIG. 15 are hierarchical. It is sufficient that one of the database management systems 100, for example, the transcription unit 8 is prepared. That is, the data type T1 (here, the character string type) can be substituted with the data type T1, the data type T2 (REAL type real number type), and the data type T3 (INTEGER integer type). As a result, it can be understood which data type can be assigned to which data type, and which external processing can be used to obtain the required data type. Of course, it goes without saying that some of the input parameters of the external processing may be directly designated by the user as already described with reference to FIG.

  As described above, according to the hierarchical database management system of the present embodiment, it is possible to select a transfer destination category or table on the tree of the hierarchy displayed on the screen, and attributes belonging to the target-side category and the source-side category. The attribute belonging to is compared with the difference based on the code. When using a name instead of a code, the data type is also common, or assignment from an integer type (INTEGER) to a real type (REAL), or conversion from a numeric type to a string type, Use only data types that can be assigned or converted from source to target. Then, a common set of attributes that match or can be converted and substituted is displayed on the screen, and the data values on the source side are actually transferred to the table on the target side for only the attributes that are common between the target and the source. According to the present embodiment, it is also easy to grasp the possibility of assignment between data types by using a code attached to the data type and a table of assignability.

  In addition, the correspondence between the attributes of the transfer source and the transfer destination can be saved in a secondary storage device such as a hard disk and recalled later, so that it can be reused without setting conditions every time.

  In addition, the mapping technique at the time of posting is essentially different from a simple mapping mechanism of XML tags performed using XSLT. This is because, first of all, in XML, there is no mechanism (inheritance) to inherit attributes at the top and bottom of the hierarchy, attributes do not have a strict data type, and data is basically a character string. Mapping is possible, and it does not have a unique code structure in the world that does not have a linguistic specific meaning like BSU defined in the ISO13584 (PLIB) standard described in the present invention in the description of classes and attributes. Can be mentioned. Therefore, as shown in, for example, Microsoft's BizTalk Mapper (XML and SOAP programming for BizTalk servers, Brian E. Travis, 2000, Microsoft Press), the mapping between tags using only XML or XSLT The identity and the possibility of substitution cannot be determined, and this is a technique different from the present embodiment.

  However, the structure of the dictionary defined in PLIB is expressed in XML DTD or XML Schema, and the application or logic program provided separately, such as the EXPRESS language, is provided with the sameness or substitutability between the attributes described in the above embodiment. This embodiment can be realized by making a determination using the processing program used or the actual processing system of XML Schema, and preparing an application that displays or recommends mapping candidates to the user based on this determination.

  Further, in the invention of this embodiment, the mapping file is inherited between the parent and child classes for the saved mapping file, and the codes of the source side class and the target side class being mapped are saved. By combining this information and the parent-child relationship between classes obtained from the dictionary, it is possible to reuse the saved mapping file definition. That is, when mapping is newly performed between classes, for example, when the target is TGT1 and the source class is SRC1, TGT1 <TGT0 and SRC1 <for each of the target TGT0 and the source SRC0 described in the existing mapping file If SRC0 (A <B indicates that A is equal to B or a subclass thereof), the saved mapping file definition can be reused. In this case, it is only necessary for the user to add only the attributes on the target side that are not in the mapping file.

  The present invention is not limited to the above embodiment.

  In the above embodiment, ISO-6523-1 is used as an example of the external code, but the present invention is not limited to this. Other standards include ISO13584 Parts Library Standard Part42, ISO13584 Parts Library Standard Part24, ISO6523 Information Technology-Structure for the identification of organizations, and organizations parts --- Part2 Registration of Identification Schemes, 1998 in the same way as above. It can be used as long as it is an external code other than the code system defined in the hierarchical database and can uniquely identify the attribute in each category.

  Note that the present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. In addition, various inventions can be formed by appropriately combining a plurality of components disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, constituent elements over different embodiments may be appropriately combined.

  As described above, the present invention is effective in the technical field of a hierarchical database management system, a hierarchical database management method, and a hierarchical database management program for transferring data between classifications (classes) of a hierarchy of a hierarchical database. It is.

The functional block diagram of the hierarchical database management system 100 which concerns on one Embodiment of this invention which concerns on one Embodiment of this invention. The functional block diagram which shows another example of the hierarchical database management system which concerns on the embodiment. The figure which shows the example of a display screen by GUI which concerns on the embodiment. The figure which shows the example of a screen display by GUI for demonstrating the process when a data type is common even when the attribute code which concerns on the embodiment differs, and the code added to the data type is common. The figure which shows the example of a screen of a process when the data type which concerns on the embodiment is substitutable from the source side to the target side. The figure which shows the flowchart of the basic procedure of the transcription | transfer process which transcribe | transfers attribute data based on the matching attribute code based on the embodiment. The figure which shows the flowchart of an example of the fundamental process sequence of the transcription | transfer candidate selection using GUI which concerns on the embodiment. The figure which shows the flowchart of the basic process sequence of transcription | transfer of the attribute data based on matching of the attribute code which concerns on the embodiment. The figure which shows the example of a screen display of GUI of the selection function of the transfer line which displays the instance actually transferred based on the embodiment in a table | surface form, and selects the instance which should be transferred from it. The figure which shows the flowchart of the basic process sequence of the transfer function between the classes concerning the embodiment. The figure which shows the example of a display screen of the selection function of the transcription line using GUI which concerns on the embodiment. The figure which shows the example of a screen for demonstrating the selection function of the transcription line using the direct designation | designated GUI of the copy instance value which concerns on the embodiment. The conceptual diagram for demonstrating embodiment of the transcription | transfer function containing the external process which concerns on the embodiment. The figure which shows the list | wrist of the substitutability between the data types which concern on the embodiment. FIG. 6 is a view showing a list of output data types and input parameters of an external processing function according to the embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Dictionary DB, 2 ... Instance DB, 3 ... Server side data management part, 4 ... Instance reading part, 5 ... Instance writing part, 6 ... Instance file, 7 ... Dictionary parser, 8 ... Transfer part, 9 ... Dictionary file DESCRIPTION OF SYMBOLS 10 ... Dictionary writing part, 11 ... Network, 12 ... Client side data management part, 13 ... Instance page, 14 ... Instance reading part, 15 ... Instance writing part, 16 ... Instance file, 17 ... Class tree, 18 ... Dictionary parser, 19 ... Dictionary writing unit, 20 ... Dictionary file, 21 ... Dictionary search input unit, 22 ... Class information, 23 ... Instance search input unit, 24 ... Instance information, 25 ... Pointing device, 26 ... Keyboard, 27 ... Display device, 28 ... external processing unit

Claims (18)

A hierarchical database management system for managing a hierarchical database having a hierarchical structure in which a lower level inherits an attribute of a higher level classification,
An attribute in which the first attribute belonging to the first classification and the second attribute belonging to the second classification are common based on a common code that uniquely identifies all attributes included in the first classification and the second classification Means for determining whether or not
Means for displaying the name of the third attribute determined to be common to the first attribute and the second attribute by the determination and the common code;
A hierarchical database management system comprising: means for transferring an instance belonging to the third attribute from the first classification to the second classification. The means for displaying displays the name of the third attribute and the common code as transfer candidates,
And a means for selecting one of the transfer candidates.
The said means to transcribe | transfer the instance which belongs to the said 3rd attribute and belongs to the attribute selected by the said selection means from the said 1st classification to the said 2nd classification. The Claim 1 characterized by the above-mentioned. The hierarchical database management system described. The means for determining is when the codes for identifying the attributes of the first classification and the second classification are different, and when the first attribute has a data type that can be transferred to the second attribute, the data type is Determining that the data type is common to the first attribute and the second attribute;
The hierarchical database according to claim 1 or 2, wherein the transfer means transfers an instance of the first attribute having the data type from the first classification to the second classification. Management system.   The hierarchical database management system according to any one of claims 1 to 3, wherein the common code is a code uniquely set in a classification system other than the hierarchical database. When the hierarchical database has first and second classification systems, the display means displays a classification tree including the first and second classification systems, and the first classification system includes a first classification system. When a classification and a second classification are included, an instance belonging to the second classification is displayed as a transfer destination instance,
The selecting means selects the posting destination instance,
The hierarchical database management system according to any one of claims 2 to 4, wherein the means for transferring posts the instance of the transfer destination within the first classification system. When the hierarchical database has first and second classification systems, the display means displays a classification tree including first and second classification systems, and the first classification system includes the first classification system. 1 is included, and when the second classification is included in the second classification system, an instance belonging to the second classification is displayed as a transfer destination instance.
The selecting means selects the posting destination instance,
The hierarchical database management according to any one of claims 2 to 4, wherein the transfer means transfers the transfer destination instance from the first classification system to the second classification system. system. The means for displaying displays a plurality of instances of the first classification to be posted in a tabular format,
The selecting means selects and selects at least one of a plurality of instances displayed in the tabular format,
The hierarchical database management system according to any one of claims 2 to 6, wherein the transfer means transfers at least one instance selected in a limited manner. And further comprising means for pooling in association with one pool unit identification information for at least one instance selected by the means for selecting,
The display means displays the at least one instance pooled by the pooling means and the pool unit identification information in response to an access from a user having an editing process authority,
The selection means selects whether or not to perform the transfer of the at least one instance;
3. The transfer means transfers the at least one instance from the first classification to the second classification only when the selection means selects that execution of the transfer is permitted. 8. The hierarchical database management system according to any one of items 1 to 7. The pooling means pools the pooling time in association with the pool unit identification information,
The means for displaying displays a time designation screen together with the pool unit identification information,
The means for selecting collectively selects the at least one instance associated with the pooling time corresponding to a specified time range,
The hierarchical database management system according to claim 8, wherein the means for transferring transfers the at least one instance selected in a batch. The pooling means pools the date and time or user identification information selected by the selecting means in association with the pool unit identification information,
The hierarchical database management system according to claim 8 or 9, wherein the display means displays the date and time or user identification information selected by the selecting means together with the pool unit identification information. The means for displaying displays a plurality of classifications,
The means for selecting selects the first category as a transcription source from the plurality of categories,
And further comprising a transcription source association means for associating the first classification, the first attribute belonging to the first classification, and the transcription source identification information for identifying the first instance,
The means for displaying displays the transcription source identification information,
In the case where the means for transferring is designated by the selecting means to move from the transcription source identification information to the second category of the transcription destination or the second attribute belonging to the second category or the second instance. The hierarchical database management system according to any one of claims 2 to 10, wherein instances belonging to the third classification are transferred from the first classification to the second classification. The means for displaying displays a constant identifying the first attribute;
The means for transferring, when the constant is selected by the means for selecting, transfers the instance having the first attribute identified by the constant to the second classification. The hierarchical database management system according to any one of 1 to 11. Further, means for storing the first and second classifications that are actually transferred and the mapping relationship of the transfer between the first and second attributes in association with the mapping identification information that identifies the mapping relationship. With
The means for displaying displays the mapping relationship identified by the mapping identification information when the first or second attribute is selected by the means for selecting,
13. The means for transferring, when the mapping relation is selected by the means for selecting, posts between the first and second attributes specified in the mapping relation. The hierarchical database management system according to any one of the above. The display means displays the mapping relationship identified by the mapping identification information when a third category having a fourth attribute that inherits the second attribute is selected as a transfer destination or a transfer source. The hierarchical database management system according to claim 13, which is displayed. The storing means stores identification information of a user who specified the mapping relationship in association with the mapping identification information,
The display means displays the mapping relationship identified by the mapping identification information when the first or second attribute is selected by the user identified by the user identification information by the selecting means. The hierarchical database management system according to claim 13 or 14, wherein, when selected by another user, the mapping relation is not displayed. The means for displaying displays a list of external processes defined by input parameters associated with a first common code and output parameters associated with a second common code,
When one of the external processes is selected by the selecting means, the instance having the first common code defined by the input parameter is changed to the instance having the second common code defined by the output parameter. Means for performing the external processing of:
The hierarchy according to any one of claims 1 to 15, wherein the means for transferring performs transfer from the first classification to the second classification based on the externally processed result. Type database management system. A hierarchical database management method for managing a hierarchical database having a hierarchical structure in which a lower level inherits an attribute of a higher level classification,
An attribute in which the first attribute belonging to the first classification and the second attribute belonging to the second classification are common based on a common code that uniquely identifies all attributes included in the first classification and the second classification Whether or not
Displaying the name of the third attribute determined to be common to the first attribute and the second attribute by the determination and the common code;
A hierarchical database management method, wherein an instance belonging to the third attribute is transferred from the first classification to the second classification. A hierarchical database management program for causing a computer to execute management of a hierarchical database having a hierarchical structure in which a lower level inherits an attribute of a higher level classification, the program including:
An attribute in which the first attribute belonging to the first classification and the second attribute belonging to the second classification are common based on a common code that uniquely identifies all attributes included in the first classification and the second classification Means for determining whether or not
Means for displaying the name of the third attribute determined to be common to the first attribute and the second attribute by the determination and the common code;
A hierarchical database management program that causes an instance belonging to the third attribute to be transferred as means for transferring from the first classification to the second classification.

Images