JP2004013430A - Data processing method and software program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a method for differently setting a reference condition with every member in the method for referring to profile data on a member belonging to a group. <P>SOLUTION: The constitution is formed for displaying only a providable attribute item by determining the attribute item of the profile data providable for a user according to the reference condition set in a table by acquiring the reference condition setting table registered with every group constitutive member when receiving a profile data reference request from the user. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a data processing method and a software program therefor, and more particularly to a data processing method for referencing or searching for profile data relating to individuals, corporations and services registered in advance in a database or registered in a predetermined management system, and for the same. Related to software programs.
[0002]
[Prior art]
In the method of referring to or searching for profile data as described above, a system that does not necessarily permit a user who has requested a reference or search to view all data and does not allow a specific registered item to be viewed by the user. Exists. Specifically, there are the following two methods to realize such a system. That is, in the first method, a plurality of specific users are grouped together, an access right called “role” is given to the group, and a role is individually assigned to each reference / search target profile. . As a result, users belonging to the same group can access predetermined profile data under the same conditions, and thus can refer to the same information.
[0003]
Another method is to create a “view” in an RDBMS (relational database management system), assign the above-mentioned role to the created view, and use the view to set the view according to the role. Only the data records required by the user are combined, and the combined data records are displayed on the view.
[0004]
In any of these methods, in any case, users are grouped in advance, and the same data schema can be referred to by giving a single type of authority common to all members of the group.
[0005]
[Problems to be solved by the invention]
Here, a case is considered in which the profile data records of all the groups to which a specific user belongs are combined using the view in the RDBMS, and displayed as a list. In this case, the values of the same type of attribute are displayed side by side in the list of the referenced user profile data. However, in such a case, it is conceivable that some users corresponding to the profile data do not necessarily want to provide their profile data to all the group members under the same conditions.
[0006]
For example, in a company, etc., their profile data is released unconditionally to their direct supervisors, but to members of the same group who have the same role, they are released to some extent under certain conditions. In some cases, it is possible to release the information under more restricted conditions.
[0007]
In such a case, for example, in the case of the above-mentioned RDBMS, it is considered that this can be realized by the system administrator providing a plurality of types of the views having roles according to the plurality of disclosure conditions. However, if various views are created for a large number of users, the number of views becomes enormous and maintenance work becomes difficult. In addition, when a user's profile is updated due to promotion of the user or the like, many views related to the profile need to be changed, and when many views are created for many users, the work of updating the view is extremely difficult. Becomes difficult.
[0008]
SUMMARY OF THE INVENTION In view of the above circumstances, the present invention is a data processing method for referencing and searching profile data, in which members of a group can individually set the disclosure conditions of their own profile data, and changing the disclosure conditions. The purpose is to provide a method that can be flexibly used even at times.
[0009]
[Means for Solving the Problems]
In order to achieve the above object, the present invention provides, for each member belonging to a group, reference condition setting information that specifies, for each member, an attribute item that can be provided to a member of the group among profile data of each member. Further, the reference condition setting information has a configuration for individually specifying, for each member of the group, attribute items that can be provided to the member. Further, as another configuration of the present invention, the reference condition setting information includes rank information which numerically defines an authority relationship between members set for each member, and a member to be accessed to be compared with the rank information. Has a configuration for designating the attribute items of the profile data that can be provided according to the comparison result with respect to the rank information held by.
[0010]
By providing the reference condition setting information individually for each group member in this manner, each member can freely set the reference condition, and when the reference condition is changed, the member corresponding to the changed item is simply set. What is necessary is just to change the setting of the reference condition, and it is possible to cope without performing the knitting work of the group each time.
[0011]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, examples of the present invention will be described.
[0012]
Consider a system that allows collective browsing of profile data on individuals, corporations and services, even if users in the same group do not necessarily want to provide their own profile data under the same conditions Consider the configuration. In this case, for example, in the case of the above RDBMS, it is considered that the configuration can be realized by providing a plurality of types of the views having roles (viewing / referencing authority) according to a plurality of disclosure conditions as described above. However, in this case, providing a plurality of types of views may complicate the system. In addition, a list obtained by searching according to the conditions of each view must collectively display only attributes that can be made public. Therefore, from the user's point of view, if there is an attribute that was originally forgotten to enter the attribute value and is not displayed, or the user intentionally refused to enter the attribute value and hidden it without entering the attribute value It cannot be distinguished.
[0013]
In the embodiment of the present invention, a reference condition setting table in which individual reference conditions are described is prepared so that information of members belonging to the same group can be explicitly referred to based on the intentions of the members. There are two types of this table, the first of which is a table in which attribute items which are linked to the user profile to be accessed by a pointer and can be referred to for each user ID of members in the group (FIGS. 2 and 3) reference). The second is to provide a value called a user rank which numerically determines the authority relationship between users accessing the reference condition setting table, and attribute items that can be referred to by users in the group based on the numerical value of the user rank. (See FIGS. 2 and 4).
[0014]
In order to specifically explain the contents of the table, FIG. 3A shows, for example, “Taro Tanaka” (pointer; condition_id: “0010”) which is the first member of the members in the group shown in FIG. ") Is a reference condition setting table, and the registration condition accept_user num = 1 is set, and" name "is given to a member of the user ID" 01 "(user_id = 1), that is," Taro Tanaka "who is self. (Name) and “phone” (telephone number) are designated to be provided. Similarly, as the registration condition accept_user num = 2, members of the user ID “03” (user_id = 03), that is, “Jiro Nakamura” It is specified that only “name” (name) can be provided, and As ccept_user num = 3, for the members of the user ID "12" (user_id = 12) "name" it is specified that can provide the (name) and the "phone" (phone number).
[0015]
Next, in the example of FIG. 3B, “name” and “telephone” of the profile data of “Taro Tanaka” which is the first member (pointer “0010”) among the members in the same group as above. It is specified that the "number" can be provided to all members (user_id = ALL) in the group.
[0016]
Further, in the example of FIG. 3 (c), the profile data of "Taro Tanaka" which is the first member of the members in the same group cannot be provided to any members in the group. Is stipulated.
[0017]
On the other hand, in the reference condition setting table shown in FIG. 4, a user rank (user_rank) is registered for each group member, and profile data that can be provided to each member is determined based on a result of comparison of the rank. That is, in the case of the example of FIG. 4, the user rank of the member "Taro Tanaka" of the pointer "0010" is "7", and as a condition of reference_accept_user condition = 1, the member (user_rank> = 7), profile data "name" (name) and "phone number" (phone) can be provided. On the other hand, a member of lower rank (user_rank <) is set as accept_user condition = 2 in the reference condition. For 7), only profile data "name" (name) can be provided.
[0018]
FIG. 5 shows a schematic configuration of the embodiment of the present invention. The search execution unit 11 executes a search operation on the profile database 15 to search and acquire a list of user profile data of a group to which the user belongs based on the input user ID. The table acquisition unit 12 refers to the pointer (condition_id in FIG. 2) to the reference condition setting table indicated in one (one record) of each user profile data of the list acquired in this way, and (FIG. 3A, FIG. 3B or FIG. 3C, or FIG. 4, hereinafter, referred to as a “reference condition table”).
[0019]
Next, the condition selection processing unit 13 checks whether or not the input user ID matches the condition described in the reference condition setting table thus obtained. Then, the result data generation unit 14 performs a process on each attribute of each user profile according to the condition that is matched as a result of the above check, and combines the results to output a list.
[0020]
Hereinafter, the embodiment of the present invention will be described in more detail.
[0021]
First, a functional block diagram according to the first embodiment of the present invention is shown in FIG. 6, and an operation flowchart thereof is shown in FIG. First, the user inputs his / her user ID and password to this system (step S1), and the authentication function unit 21 verifies whether or not the user is a user of the data reference system (step S2). As a result, when the user is authenticated as a user of the system (Yes in S2), the search execution unit 11 searches and acquires a list of the user profile data of the group to which the user belongs based on the input user ID. A search operation is performed on the profile database 15 (step S3).
[0022]
The table acquisition unit 12 refers to the pointer to the reference condition setting table indicated in one (one record) of each user profile data of the list acquired in this way, and acquires information of the corresponding table ( Step S4). The condition selection processing unit 13 checks whether or not the input user ID matches the condition (accept_usernum) described in the reference condition setting table thus obtained (step S5).
[0023]
For example, consider the case where the user is “Jiro Nakamura” with user ID “03”. In this case, the search operation is performed for all members of the group shown in FIG. 2, and the record of “Taro Tanaka” with the user ID “01” is referred to as the first record at that time. Assume that a reference condition setting table as shown in FIG. 3A has been set for "Taro Tanaka". In this case, the table shown in FIG. 3A is referred to by the pointer "0010" of the record. In this table, the data of “accept_user num = 2” is defined as “user_id = 03, attributes = (name)”. This means that only “name” (name) is disclosed to the user ID “03”, that is, “Jiro Nakamura”. Therefore, in this case, “Taro Tanaka” in the profile data of “Taro Tanaka” Only data could be provided to Jiro Nakamura.
[0024]
Next, the result data generating unit 14 leaves blank the attribute that cannot be disclosed (attribute restricted) to the user who has accessed according to the condition that matches the result of the check (step S6). Is repeated (loop of steps S4 to S7), and the results obtained in this way are combined and output as a list (step S8). If the matching condition is not included in the corresponding reference condition setting table as a result of the above check (No in step S5), it is determined that the accessing user is not a member of the group, and the process ends.
[0025]
That is, in the case of the above example, the reference condition setting table set for each member is sequentially referred to according to the pointer as described above for the members in the group, and as a result, the user ID “03” is given to Jiro Nakamura. On the other hand, profile data permitted to be disclosed is sequentially determined, and as a result, a list as shown in FIG. 1A is created and output to “Jiro Nakamura”. Therefore, in this case, in the list output to Jiro Nakamura, for example, only the “name” data is specified as the profile data of “Taro Tanaka”, and the other data “phone” (telephone number), “ Each column of “department” (department) is output as “blank”.
[0026]
Next, a second embodiment of the present invention will be described. In this embodiment, similarly to the first embodiment, the functional blocks shown in FIG. 6 are used, and the operation flowchart is shown in FIG. First, the user inputs his / her user ID and password to this system (step S11). When the user is verified as a user of the system by the authentication function (Yes in step S12), the search execution unit 11 inputs the user ID and password. A search operation for acquiring a list of user profile data of the group to which the user belongs is executed on the profile database 15 based on the user ID thus set (step S13). The table acquisition unit 12 acquires the corresponding table information according to the pointer to the reference condition setting table indicated in one (one record) of each user profile data of the acquired list (step S14).
[0027]
The condition selection processing unit 13 checks whether or not the input user ID matches the condition (accept_usernum) described in the acquired reference condition setting table (step S15). As a result, the data generation unit 14 inputs a character string of “Private” as an attribute that cannot be provided to the accessing user (attribute restricted) according to the matched condition (step S16). Is repeated (loop of steps S14 to S17), and the results obtained in this manner are combined and output as a list. As in the above embodiment, if there is no condition item that matches the user ID as a result of the check, it is determined that the user does not belong to the group, and the process ends.
[0028]
The configuration of the second embodiment is the same as that of the first embodiment. However, in the first embodiment, the profile data that cannot be provided is output as “blank”, whereas in the second embodiment, the profile data is referred to as “non-public”. The difference is that a character string is output. By explicitly indicating "non-public" instead of "blank", it is possible to clearly understand that the data of the item is not originally registered but is registered but concealed.
[0029]
Next, a third embodiment of the present invention will be described. In this embodiment, similarly to the first embodiment, the functional blocks shown in FIG. 6 are used, and the operation flowchart is shown in FIG. First, the user inputs his / her user ID and password to this system (step S21), and if the user is verified as a user of this system by the authentication function (Yes in step S22), the search execution unit 11 Then, a search operation for acquiring a list of the user profile data of the group to which the user belongs is executed on the profile database 15 based on the input user ID (step S23).
[0030]
Next, the table acquisition unit 12 acquires the corresponding table according to the pointer to the reference condition setting table indicated in one (one record) of each user profile data of the list acquired as described above (step S24). ). The condition selection processing unit 13 acquires the profile data of the accessing user using the input user ID as a key, and acquires and holds the value of the user rank set for the user. Then, it is checked whether or not this value matches the condition (accept_usercondition) described in the reference condition setting table linked to the profile data of the users of all the group members (step S25). Then, in the result data generation unit, according to the matched condition, an attribute that cannot be provided to the accessing user (an attribute to restrict reference) is left blank so as not to be displayed (step S26), and this operation is repeated (step S26). S24 to S27), the results thus obtained are combined and output as a list (step S28). Also, as in the above embodiment, if there is no condition corresponding to the user ID as a result of the check, it is determined that the accessing user is not a member of the group, and the process ends.
[0031]
Specifically, for example, it is assumed that the accessing user is “Jiro Nakamura” and the user rank of the user is “4”. In that case, the records are referred to for each group member according to the list acquired in step S23 (loop of steps S24 to S27). As an example, referring to the first record “Taro Tanaka”, it is assumed that the reference condition setting table indicated by the pointer “0010” is that of FIG. In this case, since the rank of the accessing user is “4” as described above, in the table shown in the figure, it matches “accept_user condition = 2 (user_rank <7, attribute = (name))”. As a result, Tanaka It is determined that only “name” of Taro's profile data can be provided, and therefore “blank” is output for profile data items that cannot be provided to the access user with respect to the member.
[0032]
Hereinafter, a fourth embodiment of the present invention will be described. In this embodiment, similarly to the first embodiment, the functional blocks shown in FIG. 6 are used, and an operation flowchart thereof is shown in FIG. First, the user inputs his / her user ID and password to this system (step S31). When the user is verified as a user of this system by the authentication function (Yes in step S32), the search execution unit 11 Then, a search operation for acquiring a list of user profile data of the group to which the user belongs is executed on the profile database based on the input user ID (step S33).
[0033]
Next, the table obtaining unit 12 obtains the corresponding table according to the pointer to the reference condition setting table indicated in one (one record) of the user profile data of each member of the list thus obtained (step). S34). The condition selection processing unit 13 refers to profile data of the user who has accessed from the input user ID, and acquires and holds the value of the user rank set for the user. Then, it is checked whether or not this value matches the condition (accept_usercondition) described in the reference condition setting table linked to each user profile.
[0034]
Then, the result data generating unit 14 inputs a character string “undisclosed” for an attribute that cannot be provided to the accessing user (attribute to be restricted) according to the condition matched in step 35 (step S36). This operation is further repeated (steps S34 to S37), and the results thus obtained are combined and output as a list (step S38). Also, as in the above embodiment, if there is no condition corresponding to the user ID as a result of the check, it is determined that the accessing user is not a member of the group, and the process ends.
[0035]
The configuration of the fourth embodiment is the same as that of the third embodiment. However, in the third embodiment, the profile data that cannot be provided is output as “blank”, whereas in the fourth embodiment, it is referred to as “non-public”. The difference is that a character string is output.
[0036]
As described above, according to the present invention, when a list of user profile data of members in a group is generated, information for designating the disclosure or non-disclosure of attributes based on the intention of each member is added in advance, and this information is added. , Each attribute information constituting the resulting list can be explicitly displayed. According to this method, even when the reference condition changes, it is not necessary to reconfigure the group each time, and only to correct the reference condition setting table set for each member. Thus, a profile data list meeting the conditions can be dynamically generated.
[0037]
Note that the present invention having the configuration described with reference to FIGS. 5 and 6 can be provided in the form of a software program including instructions for causing a computer to execute the operations described with reference to the flowcharts of FIGS. Needless to say, there is.
[0038]
【The invention's effect】
As described above, according to the present invention, the reference condition for the group member of the profile data of the member is set for each member of the group, and the setting method is to specify the available range for each member or A rank is set for each member, and a provisionable range is designated according to a comparison result with a predetermined reference rank. In the former method, reference conditions can be set for each member freely. Alternatively, in the latter method, the reference condition for all the members can be set only by determining the reference rank, so that the setting is easy.
[Brief description of the drawings]
FIG. 1 is a diagram showing a display example of a profile data list that can be created by the data processing method of the present invention.
FIG. 2 is a diagram showing an example of the contents of a user profile database applicable to each embodiment of the present invention.
FIG. 3 is a diagram showing each example of a reference condition setting table in the first embodiment and the second embodiment of the present invention.
FIG. 4 is a diagram showing an example of a reference condition setting table in a third embodiment and a fourth embodiment of the present invention.
FIG. 5 is a block diagram showing a basic configuration of each embodiment of the present invention.
FIG. 6 is a functional block diagram of each embodiment of the present invention.
FIG. 7 is a flowchart showing an operation procedure of the first embodiment of the present invention.
FIG. 8 is a flowchart showing an operation procedure of the second embodiment of the present invention.
FIG. 9 is a flowchart showing an operation procedure of the third embodiment of the present invention.
FIG. 10 is a flowchart showing an operation procedure of the fourth embodiment of the present invention.

Claims (7)

A data processing method for providing a user with profile data registered for each member belonging to a predetermined group,
Upon receiving a reference request from the user, refer to the reference condition setting information in which the reference conditions for the members belonging to the predetermined group are set with respect to the profile data registered for each member,
As a result, each step comprises determining the attribute items of the profile data that can be provided to the user so that the user can refer to the profile data from the profile data registered for each member,
The data processing method according to claim 1, wherein the reference condition setting information individually specifies, for each member belonging to the predetermined group, an attribute item of profile data that can be provided to the member. 2. The configuration according to claim 1, wherein the reference condition setting information includes a configuration in which attribute items of profile data that can be provided to a user who has made a reference request are collectively designated for all members belonging to the predetermined group. Data processing method. 3. The data processing method according to claim 1, wherein the reference condition setting information is configured using user identification information assigned to each member belonging to the predetermined group as a key. A data processing method for combining profile data registered for each member belonging to a predetermined group and providing the combined data to a user,
Upon receiving a reference request from the user, refer to the reference condition setting information in which the reference conditions for the members belonging to the predetermined group are set with respect to the profile data registered for each member,
As a result, each step comprises determining the attribute items of the profile data that can be provided to the user so that the user can refer to the profile data from the profile data registered for each member,
The reference condition setting information specifies an attribute item of profile data that can be provided according to a result of comparing rank information that numerically defines the authority relationship between members set for each member belonging to the predetermined group. A data processing method having a configuration to perform. The method further includes displaying to the user an attribute item of profile data that can be provided to the user who has made the reference request determined in the determining step,
The data processing method according to claim 1, wherein nothing is displayed for attribute items other than the attribute items that can be provided. The method further includes displaying to the user an attribute item of profile data that can be provided to the user who has made the reference request determined in the determining step,
The data processing method according to any one of claims 1 to 4, wherein an attribute item other than the attribute item that can be provided is displayed to indicate that it cannot be provided. A software program comprising instructions for causing a computer to execute the data processing method according to claim 1.

Images