JP6229997B2 - Data management system and program - Google Patents

Description

  The present invention relates to a data management system and a program.

  Patent Document 1 discloses a basic database that can be commonly referred to by different data center clients, and one or a plurality of custom databases for each data center client that can be referred to only by each data center client. A center system, wherein a data item of a custom database or a data item of the database command is linked to a data item of a basic database via a custom application program that can be defined for each data center client. A data center system is disclosed.

  Patent Document 2 is a method for controlling access to a database in a database device that executes a program for accessing the database. When the data access authority setting process for setting the access authority and the program tries to access the data in the database, it is determined whether the access is possible based on the importance of the data and the data access authority, A database access control process for controlling access to the data by the program, and a database access control method.

JP 2005-182297 A JP 2002-182983 A

  An object of the present invention is to provide a data management system and a program capable of easily managing which information stored in different storage destinations is used for which application software.

  According to the first aspect of the present invention, for each attribute item, a usage target storage unit that stores usage target information indicating a usage target of the attribute item, identification information and one or more attribute items associated with the identification information When the attribute value is output by the application software, the attribute item including the application software as the usage target indicated by the usage target information when the attribute value is output by the application software And an integrated output means for obtaining attribute values relating to the searched attribute items from a plurality of storage means and integrating and outputting based on the identification information.

  The present invention according to claim 2 is the data management system according to claim 1, further comprising a usage target changing unit that changes usage target information stored in the usage target storage unit.

  According to a third aspect of the present invention, the usage target changing unit uses usage target information indicating that the usage target information stored in the usage target storage unit is used by specific application software in a plurality of application software. The data management system according to claim 2, wherein the data management system is changed to use target information indicating that the information is to be used.

  The invention according to claim 4 further includes a storage destination storage unit that stores storage destination information indicating a storage destination of the attribute value of the attribute item for each attribute item, and the integrated output unit includes the storage destination storage unit The data management system according to any one of claims 1 to 3, wherein the attribute value is acquired from an acquisition destination specified by storage destination information stored by the means.

  The present invention according to claim 5 relates to attribute item association means for associating a plurality of different attribute items, and any attribute value of the attribute item associated by the association means with another attribute value associated with the association means. 5. The data management system according to claim 1, further comprising attribute value reflecting means to be reflected on the data.

  The present invention according to claim 6 further includes usage authority setting means for setting usage rights of attribute values between attribute items associated by the attribute item associating means, wherein the attribute value reflecting means includes the usage authority setting. 6. The data management system according to claim 5, wherein the attribute value is reflected when the reflection is permitted based on the use authority set by the means.

  According to the seventh aspect of the present invention, for each attribute item, a usage target storage unit that stores usage target information indicating a usage target of the attribute item, identification information and one or more attribute items associated with the identification information When the attribute value is output by application software to a computer of a data management system having a plurality of data storage means for storing data including the attribute value in attribute item units, the usage target indicated by the usage target information This is a program for executing a step of searching for an attribute item including the application software, acquiring attribute values related to the searched attribute item from a plurality of storage means, and integrating and outputting based on the identification information.

  According to the first aspect of the present invention, it is possible to easily manage which information stored in different storage destinations is to be used for which application software compared to the case where the present configuration is not provided.

  According to the second aspect of the present invention, when data is shared among a plurality of application software, the shared data target can be easily changed as compared with the case where the present configuration is not provided.

  According to the third aspect of the present invention, the data used for the specific application software can be easily changed as compared with the case where the present configuration is not provided so that the data is also used by other application software. .

  According to the fourth aspect of the present invention, the storage destination of the information to be acquired can be easily specified as compared with the case where the present configuration is not provided.

  According to the fifth aspect of the present invention, the attribute value of another related attribute item is referred to as the attribute value of the attribute item, or the edited content of the attribute value of the attribute item is referred to as the other attribute item. It can also be applied to the attribute values.

  According to the sixth aspect of the present invention, data integrity or confidentiality can be managed.

  According to the present invention of claim 7, it is possible to easily manage which information stored in different storage destinations is to be used for which application software compared to the case where the present configuration is not provided.

It is a mimetic diagram showing data management system 2 concerning an embodiment of the present invention. It is a schematic diagram which shows an example of the hardware constitutions of the shared server 8, the application alpha server 4, the application beta server 6, and the terminal device 10 which concern on embodiment of this invention. It is a schematic diagram which shows the output example by the application alpha server 4, (a) shows the output example of the personal information of the employee whose user ID is "tanaka", (b) has the user ID "suzuki". An output example of employee personal information is shown. It is a schematic diagram which shows the output example by the application beta server 6, (a) shows the output example of the information about the employee whose user ID is "tanaka", (b) has the user ID "suzuki". An example of output for employees is shown. It is a schematic diagram which shows an example of the data managed by each database, (a) shows an example of the data managed by shared DB18, (b) shows an example of the data managed by application (alpha) DB14, (c ) Shows an example of data managed by the application βDB 16. It is a schematic diagram which shows a mode that the data of each database are integrated via internal ID. It is a schematic diagram explaining registration of a new user record. It is a schematic diagram explaining the case where application software is newly introduced. It is a table | surface which shows an example of the attribute item management information which the data management system 2 which concerns on this embodiment memorize | stores. It is a schematic diagram which shows an example of the data integrated based on utilization object information, (a) shows an example of the data displayed and output by application (alpha), (b) is an example of the data displayed and output by application (beta). Is shown. It is a table | surface which shows an example of the attribute item management information in which utilization object information was changed. It is a schematic diagram shown about the data displayed and output, (a) shows the data displayed and output by application (alpha), (b) has shown the data displayed and output by application (beta). It is a schematic diagram which shows an example of the data output by the application beta server 6 after change of utilization object information, (a) shows the output example about the employee whose user ID is "tanaka", (b) , An output example for an employee whose user ID is “suzuki” is shown. 6 is a flowchart illustrating an example of an operation when data is integrated and output by an application α or an application β in the data management system 2. 6 is a flowchart illustrating an example of an operation when changing the use target of an attribute item in the data management system 2; It is a schematic diagram which shows an example of the data managed by each database in the data management system 2 which concerns on a modification, (a) shows an example of the data managed by shared DB18, (b) is managed by application (alpha) DB14. (C) shows an example of data managed by the application βDB 16. It is a table | surface which shows an example of the attribute item management information which the data management system 2 which concerns on a modification memorize | stores. It is a flowchart which shows an example of the operation | movement which associates several different attribute items in the data management system 2 which concerns on a modification. In the data management system 2 which concerns on a modification, it is a flowchart which shows an example of the operation | movement which reflects the attribute value of the related attribute item on the other related attribute value, (a) is the operation | movement at the time of outputting an attribute value (B) shows an example of the operation when editing the attribute value. FIG. 20 is a flowchart in which the operation example shown in FIG. 19 is modified to provide permission / refusal of reflection by the access right as described above.

Embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a schematic diagram showing a data management system 2 according to an embodiment of the present invention. The data management system 2 includes servers 4 and 6 that perform processing based on application software, a server 8 that manages data shared among a plurality of applications, and a terminal device 10, and is connected to a network 12. . The server 4 includes a database 14, the server 6 includes a database 16, and the server 8 includes a database 18, each managing data.

  In the present embodiment, a configuration including the server 4 and the server 6 is described as an example of a server that performs processing based on application software. However, the number of servers that perform processing based on application software may be one. Three or more may be sufficient. In addition, a server that performs processing based on application software and a server that manages shared data may be configured as a single casing. In this case, however, the database is constructed for each server.

  Each of the databases 14 to 18 is a database configured to store data in units of attribute items so that operations such as addition and deletion of attribute items to the data can be performed without changing the schema of the database. It is configured.

  In the present embodiment, the databases 14 to 18 are configured as column-oriented NOSQL databases so as to store data in attribute item units. Regarding the column-oriented NOSQL database, see, for example, Nobuya Motohashi, Tatsuya Kawano, Toshiaki Tsurumi, “Database Technology Utilizing Big Knowledge of NOSQL Big Data”, Rick Telecom, April 2012, pp. 11-27. 61-64 is cited as a reference. In the column-oriented NOSQL database, there is information called a column family, which defines how one or more attribute items are collected.

  The server 8 is a server that provides data stored in the database 18 in response to a request from application software. Hereinafter, the database 18 is referred to as a shared DB 18, and the server 8 is referred to as a shared server 8. In the present embodiment, the shared server 8 provides data stored in the shared DB 18 to the server 4 and the server 6.

  The server 4 is a server that performs processing based on the application software α using data stored in the database 14. Hereinafter, the application software α is referred to as application α, the database 14 is referred to as application αDB 14, and the server 4 is referred to as application α server 4. Here, when performing the process based on the application α, the application α server 4 performs the process using the data stored in the application αDB 14 in addition to the data stored in the shared DB 18 in the shared server 8.

  The server 6 is a server that performs processing based on application software β different from the application α using data stored in the database 16. Hereinafter, application software β is referred to as application β, database 16 is referred to as application βDB 16, and server 6 is referred to as application β server 6. Here, when performing the process based on the application β, the application β server 6 performs the process using the data stored in the application βDB 16 in addition to the data stored in the shared DB 18 in the shared server 8.

  Note that the application α and the application β are application software that provides services based on the application αDB 14 and the application βDB16, respectively.

  The terminal device 10 is a client terminal that requests the application α server 4 or the application β server 6 for processing. Note that the terminal device 10 may also request processing from the shared server 8.

  FIG. 2 is a schematic diagram illustrating an example of a hardware configuration of the application α server 4, the application β server 6, the shared server 8, and the terminal device 10.

.
As shown in FIG. 2, each device has a communication interface for transmitting and receiving data to and from other devices via the network 20, such as a CPU 20, a memory 22, a hard disk drive (HDD), and the like. (IF) 26 and input / output unit 28, and these components are connected to each other via a control bus 30.

  In the application α server 4, the application β server 6, and the shared server 8, the databases of the application α DB 14, the application β DB 16, and the shared DB 18 are constructed on the storage unit 24 that configures each server.

  The CPU 20 executes processing based on a program stored in the memory 22 or the storage unit 24 and controls the operation of each device.

  In the present embodiment, the CPU 20 has been described as reading and executing a program stored in the memory 22 or the storage unit 24. However, the program is stored in a storage medium such as a CD-ROM and provided to the CPU 20. It is also possible to do.

  Next, data output by the processes performed by the application α server 4 and the application β server 6 will be described based on specific examples with reference to FIGS. 3 and 4. In this example, the application α provides a service for managing employee personal information, and the application β provides a service for managing information related to the use of the scanner device by the employee. 4 and the application β server 6 are not limited to these services.

  FIG. 3 is a schematic diagram showing an output example by the application α server 4, FIG. 3A shows an output example of personal information of an employee whose user ID is “tanaka”, and FIG. An output example of personal information of an employee whose user ID is “suzuki” is shown. Here, for each employee, the user ID, which is information for identifying the employee, the department to which the employee belongs, the nationality of the employee, the address of the employee, and the age of the employee are output.

  FIG. 4 is a schematic diagram illustrating an output example by the application β server 6, FIG. 4A illustrates an output example of information about an employee whose user ID is “tanaka”, and FIG. An output example for an employee whose user ID is “suzuki” is shown. Here, for each employee, the user ID, which is information identifying the employee, the department to which the employee belongs, the billing method when the employee uses the scanner device, and the storage location of the scanned image data read by the employee with the scanner The folder is output.

  Here, the output by the application α server 4 is an output in which the data managed by the shared DB 18 in the shared server 8 and the data managed by the application α DB 14 are integrated. Similarly, the output from the application β server 6 is an output in which the data managed by the shared DB 18 in the shared server 8 and the data managed by the application βDB 16 are integrated. The data managed in each database will be described below based on the example shown in FIGS.

  FIG. 5 is a schematic diagram showing an example of data managed in each database. FIG. 5A shows an example of data managed by the shared DB 18, and FIG. 5B is managed by the application αDB 14. An example of data is shown, and FIG. 5C shows an example of data managed by the application βDB 16.

  Each database stores an attribute value of one or more attribute items and identification information (key) that identifies a set of attribute values of the one or more attribute items in association with each other. In the example shown in FIG. 5, “internal ID” is identification information. In the shared DB 18, the attribute items “user ID” and “affiliation” are stored in association with the identification information. In the application αDB 14, the attribute items “nationality”, “address”, and “age” are stored in association with the identification information. In the application βDB 16, the attribute items “charging method” and “folder” are stored in association with the identification information.

  The shared DB 18 exists at a position represented by the position information aaa as a position on the network, the application αDB 14 exists at a position represented by the position information bbb as a position on the network, and the application βDB16 serves as a position on the network. It exists at the position represented by the position information ccc.

  Thus, in the data management system 2, the data managed in the database of each server is stored in association with the internal ID that is identification information, and the application α (application β) is the application αDB14 (application βDB16). When the data managed in (1) and the data managed in the shared DB 18 are integrated and output, the data having the same internal ID are integrated and output (see FIG. 6).

  Next, generation of new data will be described. When registering a new user record, for example, the user ID uses, for example, unique information (e.g., an email address) specified during the user registration procedure, and the internal ID uses, for example, a hash value of the user ID. It is done. As a specific example, the hash value of “tanaka@xxxxxxxxx.co.jp” (here, 1234) is the internal ID of the record relating to this user. Even if the user ID is changed by changing the e-mail address or the like after the internal ID is determined, the internal ID is not changed.

  Registration of a new user record may be performed by the shared server 8, the application α server 4, or the application β server 6. As shown in FIG. 7, when a new user record is registered in the application α server 4 or the application β server 6, data is also generated in the shared DB 18 in association with the internal ID. FIG. 7 illustrates a case where a user record whose user ID is “suzuki” is registered in the application α. Among the attribute values registered through the application α, the attribute items “user ID”, “affiliation” "Is stored as data managed by the shared DB 18, and the attribute items“ nationality ”,“ address ”, and“ age ”are stored as data managed by the application αDB 14.

  Next, a case where application software is newly introduced will be described. Here, the case where the shared server 8 and the application α server 4 are existing servers and the application β server 6 is newly introduced will be described as an example. Here, it is assumed that data is not yet registered in the application βDB 16 at the time of introduction. When the application β server 6 is newly introduced, the data of the attribute item managed by the shared DB 18 can be output because the data of the shared DB 18 is used in the output of the application β, but there is no data in the application βDB 16. There is no display target for the attribute items managed by the application βDB 16. Here, as shown in FIG. 8, when data about the attribute item managed by the application βDB 16 is added via the application β (in the example shown in FIG. 8, the attribute item is assigned to the user whose user ID is “tanaka”). The attribute value of “billing method” is added, and the attribute value of the attribute item “folder” is added to the user whose user ID is “suzuki”), and is added to the application βDB 16 in association with the internal ID. Stored data is stored.

  Next, details of the integrated output of data will be described. As described above, the application α (application β) integrates and outputs the data managed by the application αDB 14 (application βDB16) and the data managed by the shared DB 18. Here, the data integration is performed using the usage target information (column family).

  FIG. 9 is a table showing an example of attribute item management information stored in the data management system 2 according to the present embodiment. As shown in FIG. 9, for each attribute item managed by each database of the data management system 2, the data management system 2 stores the usage target information indicating the usage target of the attribute item and the storage destination of the attribute value of the attribute item. And remember. The attribute item management information may be stored in any database, or may be stored in a storage form different from the database. Further, regardless of the physical storage position, the storage position may be either the storage unit 24 of the terminal device 10 or the storage unit 24 of each server.

  The usage target information is information that defines a usage target indicating how the attribute item is used. In the example shown in this embodiment, “shared”, “application α”, and “application β” are used. One of three types is given. Specifically, here, “shared” is assigned as usage target information for the attribute item managed by the shared DB 18, and “application α” is assigned as usage target information for the attribute item managed by the application αDB 14. In addition, “application β” is assigned as usage target information for the attribute items managed by the application β DB 16. As will be described later, the usage target information given to the attribute item can be changed.

  In the data management system 2, the application α (application β) is the data having the same internal ID as the attribute value of the attribute item whose usage target information is “shared” or “application α” (“application β”). Acquired from each database of the management system 2, integrated and output. Specifically, the application α (application β) refers to the attribute item management information, and searches for an attribute item whose usage target information is “shared” or “application α” (“application β”). For the attribute item, the storage location is confirmed by referring to the attribute item management information, and the attribute value is acquired from the confirmed storage location.

  FIG. 10 is a schematic diagram illustrating an example of data integrated based on the usage target information, FIG. 10A illustrates an example of data displayed and output by the application α, and FIG. An example of data displayed and output by the application β is shown.

  In the output example described above, the case where the data managed by the application αDB 14 (application βDB16) is exclusively used for output in the application α (application β) has been described. Next, regarding the data managed by the application αDB 14 (application βDB16), a description will be given of changing the data configuration so as to be provided to other application software like the data managed by the shared DB 18.

  The data management system 2 includes usage target changing means for changing the stored usage target information, and is configured to arbitrarily change the usage target information. For example, the data management system 2 changes the usage target information in accordance with an instruction by a user operation such as a system administrator.

  Here, the attribute item “age” managed by the application αDB 14 will be described assuming that it can be used by application software other than the application α.

  In this case, with respect to the attribute item “age”, the usage target information is changed from “application α” to “shared” (see FIG. 11), so that the attribute item “age” is not limited to the application α but in the application β. Is also output (see FIG. 12). As a result, as shown in FIG. 13, in the output by the application β, the attribute value of the attribute item “age” is output. In FIG. 13, (a) shows an output example of information about an employee whose user ID is “tanaka”, and (b) shows an output example of an employee whose user ID is “suzuki”. Yes.

  Thus, the usage target changing unit changes, for example, usage target information indicating that it is used in specific application software into usage target information indicating that it is used in a plurality of application software. The usage target changing means may change the usage target information indicating that it is used by a plurality of application software into usage target information indicating that it is used by specific application software.

Next, the operation of the data management system 2 will be described.
FIG. 14 is a flowchart illustrating an example of an operation when data is integrated and output by the application α or the application β in the data management system 2.

  In step 100 (S100), the application α (application β) refers to the attribute item management information and searches for an attribute item whose usage target information is “shared”.

  In step 102 (S102), the application α (application β) refers to the attribute item management information, and the application α (application β) refers to the attribute item management information and sets the attribute item whose usage target information is “application α” (“application β”). Search for.

  In step 104 (S104), the attribute value of the attribute item searched in step 100 and step 102 is acquired. Specifically, the storage location of the attribute value is confirmed with reference to the attribute item management information, and the attribute value is acquired from the confirmed storage location. The attribute value may be acquired for all internal IDs, or may be limited to attribute values corresponding to internal IDs in a range specified by an arbitrary method.

  In step 106 (S106), the application α (application β) integrates and outputs the data for each internal ID.

  FIG. 15 is a flowchart illustrating an example of an operation when the usage target of the attribute item is changed in the data management system 2.

  In step 200 (S200), the data management system 2 accepts an instruction to specify an attribute item whose usage target is to be changed. For example, the user inputs an instruction by performing an operation for designating an attribute item whose usage target is changed.

  In step 202 (S202), the data management system 2 accepts an instruction to change usage target information. For example, the user inputs an instruction by performing an operation of inputting the changed usage target information.

  In step 204 (S204), the data management system 2 rewrites the usage target information in the stored attribute item management information in accordance with the instructions in steps 200 and 202.

  After the usage target information is changed in this way, the series of processing shown in FIG. 14 is performed based on the changed usage target information, so that an output reflecting the change is made.

Hereinafter, modifications of the embodiment will be described.
The modification includes the attribute item association unit that associates a plurality of different attribute items, and the attribute value reflection unit that reflects any attribute value of the associated attribute item to the other associated attribute value. Different from the embodiment. In the modification, the data management system 2 associates a plurality of different attribute items in accordance with an instruction by an operation of a user such as a system administrator.

  There may be cases where different attribute items are to be handled together. For example, if the attribute values for the different attribute items managed in different databases are the same, even if the attribute items are formally different, they actually mean the same attribute item and can be handled as a whole. preferable. In addition, even if the attribute values are not the same, if one attribute value is the same as a part of the other attribute value (for example, attribute items “address” and “location” indicating the place where the user's life is based) When one attribute value is “Yokohama City, Kanagawa Prefecture” and the other attribute value is “Kanagawa Prefecture”), it is possible to handle different attribute items in an integrated manner. preferable.

  Here, integrally handling means that the attribute value of any attribute item among the integrally treated attribute items is reflected in the attribute values of other attribute items handled integrally. When an attribute value is output, the attribute value of another attribute item that is handled integrally with the attribute item is referenced and output, or when the attribute value is changed, other attributes that are handled integrally with the attribute item The attribute value of an item can be changed in the same way.

Hereinafter, the features of the modification will be described with reference to FIG. 16 and FIG.
FIG. 16 is a schematic diagram illustrating an example of data managed in each database in the data management system 2 according to the modification. FIG. 16A illustrates an example of data managed by the shared DB 18, and FIG. FIG. 16B shows an example of data managed by the application αDB 14, and FIG. 16C shows an example of data managed by the application βDB16. The example shown in FIG. 16 is different from the example shown in FIG. 5 in that an attribute item “location” is added as data managed by the application βDB 16.

  Note that the attribute item “address” managed by the application αDB 14 and the attribute item “location” managed by the application βDB 16 are both attribute items representing a place where the user's life is based.

  Here, it is assumed that the attribute item “address” managed by the application αDB 14 is associated with the attribute item “location” managed by the application βDB16. The data management system 2 associates the attribute item “address” and the attribute item “location” according to an instruction of a user such as a system administrator, for example.

  The data management system 2 may be configured to display a list of attribute items and their attribute values managed by each database in order to assist the user in finding an attribute item group that should be handled in an integrated manner. In this case, for example, the user looks at the displayed list and finds an attribute item group to be handled integrally from the name of the attribute item and its attribute value.

  The data item management system 2 may automatically discover the attribute item group that should be handled integrally. For example, the name of the attribute item managed by each database and the attribute value thereof may be referred to extract a matching or similar attribute item group as an attribute item group to be handled integrally.

  For example, the data management system 2 realizes the association of the attribute items by storing information indicating that they are associated. In this modification, the association between attribute items is realized by storing the attribute item management information.

  FIG. 17 is a table showing an example of attribute item management information stored in the data management system 2 according to the modification. In the example shown in FIG. 17, information indicating that “location” exists as a corresponding attribute for the attribute item “address” is stored, and “address” exists as a corresponding attribute for the attribute item “location”. Information to do so is stored.

  In the example shown in FIG. 17, two attribute items are associated with each other as being associated with each other, but three or more attribute items may be associated with each other as being associated with each other.

  The data management system 2 refers to the attribute item management information including the information about the association in this way, and the attribute value of any attribute item among the integrally handled attribute items is changed to the other attribute that is integrally handled. Reflect in the attribute value of the item.

  Hereinafter, the operation of the data management system 2 according to the modification will be described with reference to FIGS. 18 and 19.

  FIG. 18 is a flowchart illustrating an example of an operation of associating a plurality of different attribute items in the data management system 2 according to the modification.

  In step 300 (S300), the data management system 2 accepts designation of an attribute item group to be handled integrally. For example, the data management system 2 accepts an instruction to designate an attribute item group to be handled integrally by performing an operation for designating the attribute item group to be handled integrally by the user.

  In step 302 (S302), the fact that the attribute items specified in step 300 are attribute items corresponding to each other is stored as attribute item management information.

  FIG. 19 is a flowchart illustrating an example of an operation of reflecting the attribute value of the associated attribute item in another associated attribute value in the data management system 2 according to the modification. FIG. 19A illustrates the attribute value. FIG. 19B shows an example of the operation when editing the attribute value.

First, the operation when outputting attribute values will be described with reference to FIG.
In step 400 (S400), it is checked whether or not the attribute value of the attribute item to be output is stored on the database. If the attribute value is stored, it is stored in step 402 (S402). Output attribute values. On the other hand, if no attribute value is stored, the process proceeds to step 404 (S404).

  In step 404 (S404), it is confirmed whether there is an attribute item associated with the attribute item to be output. Specifically, it is checked whether there is an attribute item associated with the attribute item to be output with reference to the attribute item management information. When there is an associated attribute item, the process proceeds to step 406, and when there is no associated attribute item, the process proceeds to step 408.

  In step 406 (S406), the attribute value of the attribute item associated with the attribute item to be output is output as the attribute value of the attribute item to be output. On the other hand, in step 408 (S408), there is no attribute value to be output, so no output is made. Note that, in step 406, even if the attribute item associated with the attribute item to be output has no attribute value, output is not performed as in step 408.

Next, the operation when editing the attribute value will be described with reference to FIG.
In step 500 (S500), an attribute value editing instruction is accepted.

  In step 502 (S502), the attribute value is changed according to the editing content instructed in step 500.

  In step 504 (S504), it is confirmed whether or not there is an attribute item associated with the attribute item whose attribute value has been edited. If there is an associated attribute item, the process proceeds to step 506, and if there is no associated attribute item, the process ends.

  In step 506 (S506), the attribute value of the associated attribute item is also changed according to the editing content instructed in step 500.

  As described above, the configuration in which the attribute value of the associated attribute item is unconditionally reflected in the attribute value of the other associated attribute item has been described. However, the use authority (access right) of the attribute value between the associated attribute items has been described. It may be configured to reflect the attribute value when reflection between the attribute items is permitted based on the set access right.

  For example, for each attribute item, one of n levels (n is an integer of 2 or more) of access rights is assigned, and when the attribute value is reflected between the attribute items, the access rights of both attribute items are determined in advance. You may comprise so that reflection may be permitted when conditions are satisfy | filled. Note that the information indicating the access right given to each attribute item is managed as attribute item management information, for example.

  Regarding denial of reflection due to access rights, the confidentiality of data may be ensured using the Bell-LaPadula model, or the integrity of data may be ensured using the Biba Integrity model.

  For example, when comparing the access rights of the target attribute item with the access rights of the target attribute item, the access right of the target attribute item is higher than the access right of the target attribute item. In some cases, it is possible to ensure the confidentiality of the data by prohibiting rewriting the attribute value of the reflection-destination attribute item with the attribute value of the reflection-destination attribute item.

  Also, for example, when comparing the access rights of the reflection source attribute item with the access rights of the target attribute item, the access right of the reflection source attribute item is lower than the access right of the target attribute item. In the case of a right, it is possible to ensure data integrity by prohibiting rewriting the attribute value of the reflection-destination attribute item with the attribute value of the reflection-destination attribute item.

  FIG. 20 is a flowchart in which the operation example shown in FIG. 19 is modified to provide permission / refusal of reflection by the access right as described above.

  First, the operation when outputting attribute values will be described with reference to FIG. As shown in FIG. 20A, it is different from the flowchart shown in FIG. 19A in that step 405 (S405) is added. If it is determined in step 404 that there is an associated attribute item, the process proceeds to step 405.

  In step 405, the access right of the reflection-source attribute item is compared with the access right of the reflection-destination attribute item, and whether the access right of both attribute items satisfies a predetermined condition for referring to the attribute value or not. If the condition is satisfied, the process proceeds to step 406. If the condition is not satisfied, the process proceeds to step 408.

  Next, the operation when editing the attribute value will be described based on FIG. As shown in FIG. 20B, it is different from the flowchart shown in FIG. 19B in that step 505 (S505) is added. If it is determined in step 504 that there is an associated attribute item, the process proceeds to step 505.

  In step 505, the access right of the reflection-source attribute item is compared with the access right of the reflection-destination attribute item, and whether the access right of both attribute items satisfies a predetermined condition for reflecting the change of the attribute value. If the condition is satisfied, the process proceeds to step 506. If the condition is not satisfied, the process ends.

  As described above, the embodiment and the modification of the present invention have been described. However, the application α (application β) does not necessarily have to be output by integrating the data of a plurality of databases. Only the data managed by the shared DB 18 may be output.

  Further, in the embodiment of the present invention and the modification thereof, an example in which any of the three types of “shared”, “application α”, and “application β” is given as an example of the usage target information has been described. The usage target information is not limited to this. For example, it is not limited to one specific application software such as “application α” and “application β”, but a plurality of specific application software such as “application α and application β” and “application β and application γ”. It may be usage target information limited to. Specifically, for example, the usage target information for the attribute item “user ID” may be “application α and application β”, and the usage target information “application β and application γ” for the attribute item “affiliation” may be used. In this case, the attribute item “user ID” indicates that the application α is also used by the application β, and the attribute item “affiliation” indicates that the application β is also used by the application β.

2 Data management system 4 Application α server 6 Application β server 8 Shared server 10 Terminal device 14 Application αDB
16 App βDB
18 shared DB

Claims (7)

For each attribute item, usage target storage means for storing usage target information indicating the usage target of the attribute item;
A plurality of data storage means for storing data including identification information and attribute values of one or more attribute items associated with the identification information for each of the usage target information ;
When the output of the attribute values by the application software, retrieve search the attribute items included the application software as the usage target the utilization object information indicating an attribute value relating to the retrieved attribute item from said plurality of data storage means And an integrated output means for integrating and outputting based on the use target information and the identification information;
A data management system. The data management system according to claim 1, further comprising usage target changing means for changing usage target information stored in the usage target storage means. The usage target changing means converts the usage target information indicating that the usage target information stored in the usage target storage means is used by specific application software into usage target information indicating that the usage target information is used by a plurality of application software. The data management system according to claim 2 to be changed. Storage destination storage means for storing storage destination information indicating the storage destination of the attribute value of the attribute item for each attribute item;
The data management system according to any one of claims 1 to 3, wherein the integrated output unit acquires an attribute value from an acquisition destination specified by storage destination information stored in the storage destination storage unit. Attribute item association means for associating a plurality of different attribute items;
5. The data management according to claim 1, further comprising: an attribute value reflection unit that reflects any attribute value of the attribute item associated by the association unit to another attribute value associated by the association unit. system. Use authority setting means for setting the authority to use attribute values between attribute items associated by the attribute item association means;
The data management system according to claim 5, wherein the attribute value reflecting means reflects the attribute value when reflection is permitted based on the use authority set by the use authority setting means. For each attribute item, a usage target storage means which stores usage target information indicating a utilization object of the attribute items, the data including the attribute values of one or more attribute items corresponding to the identification information and identification information the In a computer of a data management system having a plurality of data storage means for storing attribute information for each usage target information ,
When the output of the attribute values by the application software, retrieve search the attribute items included the application software as the usage target the utilization object information indicating an attribute value relating to the retrieved attribute item from said plurality of data storage means And executing the step of integrating and outputting based on the use target information and the identification information.

Images