WO2006046395A1 - Message information management system - Google Patents

Abstract

[PROBLEMS] Centralized management of shared information shared within a group and message information communicated among the members are performed. [MEANS FOR SOLVING PROBLEMS] A server (1) stores shared data (1c) such that shared information is divided into arbitrary blocks of divided shared information and identification information for identifying each block of the divided shared information is added to each block of the divided shared information, and the blocks of the divided shared information and the identification information are registered and massage data (1e) such that identification information on one or more items of shared data (1c) associated with each set of message information and identification information on the addresses of the message information and the senders are added to the message data (1e), and the message data (1e) and the identification information are registered. From a member terminal (2), the shared data (1c) and/or the message data (1e) with addition of identification information on the member is retrieved, read, or referenced.

Description

 Specification

 Contact information management system

 Technical field

 The present invention relates to a contact information management system that centrally manages shared information shared within a group and contact information exchanged between members within the group.

 Background art

 Conventionally, sharing of computerized information within a group has been performed by a file sharing system or a database system.

[0003] For example, in the ordering data management system and management method described in Patent Document 1, it is accompanied by ordering!電子 Electronic data such as standards (specifications) and design drawings to be created are stored in a database on the server, and are shared and managed so that authorized terminals within the group can freely search and view the data. Yes. Furthermore, in the system and method described in Patent Document 1, in addition to information related to a specification, the change history of the specification can be recorded as a comment and displayed.

 [0004] However, such an ordering data management system and management method have the following technical problems.

[0005] Patent Document 1: Japanese Patent Application Laid-Open No. 2001-297204

 Disclosure of the invention

 Problems to be solved by the invention

 [0006] In the ordering / ordering data management system and management method described in Patent Document 1, the contents of the commissioned work, the specifications of the deliverables by the commissioned work, and the history that the specification change was "performed" It is managed as shared information.

 [0007] However, contact information that is exchanged between each person in the group, such as the reason for the specification change and confirmation and inquiries about the specification, is not managed, and management of the contact information is not possible. In addition to managing shared information, it was necessary to perform these individually using paper media such as e-mail systems, electronic bulletin board systems, and fax and contact forms.

[0008] Therefore, for example, specification information managed as shared information within a group If it becomes necessary to confirm the reason or circumstances of the change, a large number of e-mails exchanged between the persons in charge in the past, files stored personally by the person in charge, etc. It was very inefficient because it could only be done by manual search using information such as date, sender and subject.

 [0009] In particular, with regard to consignment work, detailed specification changes occur on a daily basis due to changes in requirements from the consignor side and restrictions on implementation of work from the consignor side. In some cases, it is possible that a specification that was determined at some point was subsequently changed, and then the previous specification was still stronger. In such a case, if past records cannot be found, it can be a serious trouble between the contractor and the trustee regarding the location of the responsibility, similar to a so-called “don't say saying”.

 [0010] The present invention has been made in view of such conventional problems, and its purpose is to exchange information between shared information shared within the group and specific members within the group. It is to provide a contact information management system that associates contact information, manages them centrally, and efficiently searches and browses shared information and contact information.

 Means for solving the problem

 [0011] In order to achieve the above object, a contact information management system according to the present invention makes a request for a terminal used by a member of a group that shares information and data registration of the terminal power 'search / viewing reference, etc. A contact information management system that centrally manages shared information shared among the members and communication information exchanged between the specific members, which are connected to each other via a network. In the server, for each divided shared information obtained by dividing the shared information into arbitrary units, shared data registered with identification information for identifying the divided shared information, and each contact information The contact information registered with the identification information of one or more of the shared data associated with the contact information and the identification information of the destination and the sender of the contact information is stored. From the above-mentioned member's terminal, the shared data and z or identification information of the member is attached, and the contact data is searched and browsed.

[0012] According to the contact information management system configured as described above, the server associates the shared data shared within the group with the contact data exchanged between specific members. Therefore, each member can search and browse the shared data and the contact data related to the shared data and exchanged by him / her as appropriate. Centralized management of shared information and contact information becomes possible.

 [0013] Further, if the contact data is associated with a plurality of pieces of shared data, the contact data power to be searched and viewed can be associated with a plurality of pieces of shared data even if it is not sure which shared data is associated with. Therefore, contact data can be searched from the viewpoint of individual members and from multiple types of viewpoints, and search efficiency is improved.

 [0014] In addition, for each of the shared data, the terminal is registered with identification information of one or a plurality of shared data corresponding to a higher level concept of the shared data as a higher level item. From the shared data identification information corresponding to the superordinate concept or the subordinate concept, the shared data configured in a hierarchical tree structure is searched and browsed, and any shared data is designated. When the contact data search 'view reference request is made, all contact data associated with all shared data corresponding to the subordinate concept of the specified shared data is searched and viewed. May

[0015] According to this configuration, since the contact data associated with the lower shared data can be searched and browsed transparently from the upper side of the hierarchical shared data, individual shared data can be searched. Even without specifying, the desired contact data can be found quickly. In addition, if the highest shared data is specified, all contact data can be browsed and browsed, and the lower the number, the smaller the number of contact data displayed, and the desired contact while narrowing down. You can search for data.

 [0016] Also, if the record record content of the shared data is changed between! / And the deviation, the record record content before the change is stored as history data in the server, and the history data force is changed before the shared data is changed. It may be the contact destination of contact data associated with.

[0017] According to this configuration, the shared data before the change remains as historical data while maintaining the relationship with the linked data associated with the shared data. It is possible to grasp the contact information exchanged at a glance. [0018] In addition, the shared data includes one shared item record in which property information such as the name, update date, registrant, and upper item of the divided shared information is recorded, and detailed contents of the divided shared information And is composed of one or more shared attribute records recorded with identification information attached to each item, and the server and the Z or the terminal arbitrarily. Addition and modification of the shared attribute record may be performed.

 [0019] According to this configuration, any number of shared attribute records can be assigned to one shared item record, and members and server administrators can freely define item names and values. Freedom · A highly versatile contact information management system is established.

 [0020] Further, the server registers the contact data with identification information for identifying the contact information, and registers the contact information that is a response to the contact information of the registered contact data as the contact data. In addition, the identification information of the contact data of the response source is added as reference information and registered, so that a series of contact information related to the response can be searched and browsed from the terminal. Yo ...

 [0021] According to this configuration, the identification information of the contact data of the response source is recorded in the contact data, so that a series of exchanges in a response relationship can be obtained, and the shared data is thereby updated. You will be able to easily know the reason and how it was updated.

 The invention's effect

 [0022] According to the contact information management system of the present invention, shared data shared within a group and contact data exchanged between specific members are recorded in association with each other on the server. The members can search and browse the shared data and the contact data associated with the shared data and exchanged with each other as needed. It becomes. BEST MODE FOR CARRYING OUT THE INVENTION

Hereinafter, the best mode for carrying out the present invention will be described with reference to the drawings.

 FIG. 1 is a diagram showing the overall configuration of the contact information management system of the present invention. In the figure, a server 1 is connected to a plurality of terminals 2 via a network 3 such as the Internet.

[0024] Each of the server 1 and the terminal 2 executes and uses a predetermined program, and the network It has the configuration (CPU, ROM, RAM, hard disk, communication means, input / output means, etc.) necessary for connecting to the network 3 and transmitting / receiving data, and is a normal computer server Any computer can be used. The hard disk included in the server 1 may include a management program such as database management software in the server 1, which is desired to have a large capacity due to the nature of the server.

 In FIG. 1, the server 1 has a contact information management program la in addition to the general components as the server computer described above, and data lb to 1 e used in these programs. Is also included in Server 1.

 Furthermore, the server 1 accepts a data search / registration / view request from the terminal 2 and transmits the processing result of the request to the terminal 2.

 [0027] The network 3 may be the Internet, a LAN (local area network), or may have a dedicated line or other connection form (whether wired or wireless). Authentication data exchanged between the server 1 and the terminal 2 via the network 3 is preferably encrypted in consideration of security problems. In that case, the server 1 and the terminal 2 Each communication means and program includes an encryption means.

 [0028] In particular, when the network 3 is the Internet, data encryption is strongly recommended because the risk of information leakage is high compared to other networks. For the encryption key, known methods and means such as SSL (Secure Socket Layer) and VPN (Virtual Private Network) can be used.

 [0029] The contact information management program la is a component that plays a central role in the contact information management system of the present invention. The contact information management program la processes data registration requests from the terminal 2 and data retrieval 'viewing (display) requests. Data that is shared among authorized members (basically all members) and communication data that is exchanged between individual members and can be searched and viewed only by that member This is a centralized management program.

[0030] It should be noted that the contact information management program la may be configured to operate on the terminal 2 that is not only on the server 1, and may be configured to operate on both the server 1 and the terminal 2. It's good. Moreover, middleware may be one that runs on the OS of server 1 and terminal 2, or one installed on server 1 runs on the web browser of terminal 2. It may be.

 [0031] Also, for example, when the contact information management program la includes a program for generating Web page display data, the terminal 2 displays a Web page, and thus a known Web browser included in its own terminal. The power to use the program As a supplement to this Web browser program, it is conceivable that some functions of the contact information management program la, for example, a form printing program is incorporated in the terminal 2 in advance.

FIG. 2 is a diagram showing a detailed configuration of the contact information management program la. The contact information management program la includes a login processing unit 21, a main processing unit 22, a shared data registration processing unit 23, a shared data search processing unit 24, a shared data display processing unit 25, a contact data registration processing unit 26, and a contact data search. A processing unit 27, a contact data display processing unit 28, and a tree display processing unit 29 are provided.

 Hereinafter, each processing unit of the contact information management program la will be described together with a detailed description of each data lb˜: Le stored in the server 1.

 [0034] When the member starts using the contact information management system, the login processing unit 21 displays a login screen on the terminal 2 of the member, accepts input of a login ID and password, It is a means for performing authentication processing based on a comparison with stored user data lb. This prevents unauthorized members who have not been given a login ID and password from using the contact information management system, and prevents leakage of data stored in server 1. The login ID and password are assigned to each member in advance. FIG. 5 is an example of the mouth guin screen 5 displayed by the login processing unit 21.

 [0035] It should be noted that all screen examples shown below are assumed to be the ASP type in which the contact information management program la is installed in the server 1, and the processing contents are displayed in the Web browser of the terminal 2. The ability to use the function of the Web browser or operating system for the screen refresh button, the screen close button, the data upload and download functions is not necessarily displayed by the Web browser. , Web browser and operating system functions do not need to be used.

[0036] User data lb may identify members who use the contact information management system. This data contains at least the identification information that can be generated. It is generated for each member and stored in server 1.

 [0037] The user data lb is composed of the user record 110 shown in FIG. 3, and the user record 110 of the present embodiment is a user ID 110a that is unique for each server and a login for identifying a member. It consists of the login IDl 10b, password 110c, member authority 110d, and member name 110e used for authentication.

 [0038] It is desirable that the password 110c be encrypted and stored in the server 1 in consideration of security. Furthermore, it is desirable that a means for displaying a password change screen (not shown) to change the password by the member himself / herself is provided in the contact information management program la! /.

 [0039] In addition, for the authority 110d, a processing range in which the operation of the contact information management system is permitted for each member is code (for example, browsing reference only: 1, contact data registration is possible: 2, shared data registration is possible: 3, system administrator: 9, etc.) are recorded.

[0040] In addition, the same value may be recorded in the user ID 10a and the login ID 10b. In that case, one of the items may be deleted!

[0041] Further, the user record 110 may be configured to record setting values such as screen layout, character color, and font displayed on the terminal 2 after the member logs in to the contact information management system. Good.

 [0042] When the login processing unit 21 completes member authentication, the main processing unit 22 performs various processes on the terminal 2 (in this embodiment, display of contact data list, display of shared data content, contact data search, sharing). This is a means for displaying a main screen for selecting (data search) and calling the shared data search processing unit 24, the contact data search processing unit 27, and the single display processing unit 29 in accordance with instructions for selecting various processes from the terminal 2. FIG. 6 is an example of the main screen 6 displayed by the main processing unit 22.

 [0043] The shared data registration processing unit 23 displays a shared data registration update screen on the terminal 2, and performs processing for registering or updating the shared data lc. FIG. 7 shows an example of the shared data registration update screen 7.

[0044] Here, the shared data lc is the end of the member permitted to operate according to the value of the authority 110d. End 2 is shared information that can be registered, updated, searched, and browsed in the contact information management system, and is composed of a shared item record 120 and a shared attribute record 130 shown in FIG. One set of shared data lc includes one shared item record 120 and 0 to a plurality of shared attribute records 130. Note that the value of authority 110d can be set in units of this shared data lc.

 [0045] One set of shared data lc is created in units divided for each unit that is easy to manage shared information. The division unit may be freely determined by the member who registers shared data lc. Operation method of registering divided into large units at first, and registering shared data lc corresponding to a more detailed concept at the lower level when it becomes necessary to further divide it later. May be adopted.

 [0046] For example, when a contact information management system is operated in a product development project, the shared information is divided into design drawing units, product function units, development flow units, etc., and "design drawings" "product functions" If the shared data lc named “Development Flow” is registered, management in the contact information management system becomes easy. Also, for example, if it is a website construction project, it will be easier to manage if it is divided into screen units constituting the website and the shared data lc having the name of each screen is registered.

 In the following description, shared information refers to individual shared information (divided shared information) divided for each arbitrary unit.

 [0048] The shared item record 120 is a record that records property information such as the superordinate concept, name, update date, registrant, etc. of the shared information. One record is created for one set of shared data lc. .

 [0049] In this embodiment, the shared item record 120 is configured with the item powers of the shared data ID 120a, the upper list 120b, the name 120c, the update date 120d, and the registrant 120e as shown in FIG.

[0050] Shared data, that is, an ID code that can identify the shared item record 120 is recorded in the shared data ID 120a.

[0051] In the upper list 120b, the value of the shared data ID 120a of the shared item record 120 corresponding to the superordinate concept of the shared item record 120 is recorded. That is, shared item record 120 Has a hierarchical structure (tree structure), and the relationship between the shared item records 120 can be known by sequentially reading the values of the upper list 120b.

[0052] For example, a shared item record 120 whose name 120c is "design drawing" has already been registered, and "drawing of board 1" and "drawing of board 2" are named 120c below "design drawing". When the shared item record 120 is hung up, the value of the shared data ID 120a of the “design drawing” is recorded in the upper list 120b of the shared item record 120 of “board 1 drawing” and “drawing of board 2”. It is recorded.

 In the present invention, it is not always necessary that one value is recorded in the upper list 120b, and values of a plurality of shared data IDs 120a may be recorded. That is, one shared item record 120 may be subordinate to a plurality of superordinate concept shared item records 120 such as “product function” and “development flow”, for example.

 [0054] In the name 120c, a name that briefly represents the shared information is recorded as text data.

 [0055] In the update date and time 120d, the date and time when any value in the shared item record 120 and the shared attribute record 130 belonging to the shared item record 120 is registered / updated is recorded.

 [0056] The registrant 120e records the value of the user IDl 10a of the member who registered 'updated any value in the shared item record 120 and the shared attribute record 130 belonging to the shared item record 120. Is done. In this embodiment, since the shared data registration processing unit 23 is not activated unless the login processing unit 21 permits the login of the terminal 2, the registrant 120e is inevitably given to the logged-in member. User ID 110a value is recorded

[0057] The shared attribute record 130 is a record for recording the substantial content of the shared information, and an arbitrary number (even 0) is created for one shared item record 120.

 In the present embodiment, as shown in FIG. 3, the shared attribute record 130 is also configured with each item force of shared data ID 130a, attribute ID 130b, type 130c, name 130d, and value 130e.

In the shared data ID 130a, the value of the shared data ID 120a of the shared item record 120 to which the shared attribute record 130 belongs is recorded. A hierarchical structure is formed in which the shared attribute records 130 are hung.

 [0060] In the attribute ID 130b, an ID code capable of identifying the shared attribute record 130 in 0 to a plurality of shared attribute records 130 having the same value of the shared data ID 130a is recorded. Note that the attribute ID assignment system may be freely determined within the group.

 [0061] In the name 130d, the substantial content of the shared information represented by the shared attribute record 130 is further itemized and recorded for each name power item.

 [0062] In the type 130c, the data type and data type code (for example, numeric value: 1, character string: 2, date: 3, attached file: 4 etc.) recorded for each item are recorded in the item 130c. Is done.

 [0063] In the value 130e, the substantial content of the shared information is recorded for each item based on the data type indicated by the previous type 130c. For example, if the data type is a numeric value, a specific numeric value is recorded as it is. If it is a character string, text data is recorded. If it is a date, for example, 20050101 (January 1, 2005) If the file is an attached file, the attached file name and the directory name indicating the storage location are recorded.

[0064] As described above, the substantial content of the shared information is expressed by the recorded content of the shared attribute record 130. However, any number of shared attribute records can be included in one shared item record 120. 130, and members and server administrators can freely define names and data types, so it can be said that this is a highly flexible and versatile contact information management system.

 [0065] For example, if the daily work report is to be shared information within the group, the name 130d of the shared attribute record 130 is defined as "work contents", "work place", "date and time", etc. What is necessary is just to record the value according to the data type. If the trouble management ledger is to be shared information within the group, the name 130d may be defined as “occurrence status”, “response method”, “solution status”, etc.

[0066] In this way, according to the type and content of the shared information, the name 130d and the data type 130c registered are designated as a specific shared information template, and newly added under the shared information. When creating shared information, the template name 130d should be displayed as an input item when the shared data registration update screen 7 shown in FIG. 7 is displayed. May be. As a result, it is only necessary to update the recorded content of the value 130e every time the daily work report is updated, and the registration of the shared information by the member is updated.

 [0067] Furthermore, when any value in the shared data lc is updated, the shared data registration processing unit 23 copies the recorded content of the shared data lc before the update to the history data Id as history information. The feature is that the shared data lc before update is also stored.

 The history data Id is composed of the history item record 140 and the history attribute record 150 shown in FIG. One set of history data Id is composed of one history item record 140 and the same number of history attribute records 150 as the number of shared attribute records 130 of one set of shared data lc.

 [0069] The history item record 140 includes items of a history data ID 140a, a shared data ID 140b, an upper list 14 Oc, a name 140d, an update date 140e, and a registrant 140f.

 In the history data ID 140a, history information, that is, an ID code that can identify the history item record 140 is recorded.

 [0071] When any value in shared data lc is updated, each value of shared data ID 140a to registrant 140f has each value of shared data ID 120a to registrant 120e before update. Will be recorded.

 The history attribute record 150 includes items of history data ID 150a, attribute ID 150b, type 150c, name 150d, and value 150e.

 In the history data ID 150a, the value of the history data ID 140a of the history item record 140 to which the history attribute record 150 belongs is recorded. That is, when any value in the shared data lc is updated, all values of the shared attribute record 130 are also included in the history data Id.

 Accordingly, each value of attribute data ID 130b to value 130e before update is recorded in each item of attribute ID 150b to value 150e.

[0075] In this way, for each update of the shared data lc, the shared data registration processing unit 23 maintains the relationship between the content of the shared data lc before the update and the contact data le associated with the shared data lc. As it is copied to the history data Id, the shared data ID 140b value in the history data Id is entered in order, or the contact data le associated with the history data Id is viewed. By referring, it becomes possible to know the change history of the shared data lc.

[0076] The shared data search processing unit 24 displays a shared data search screen on the terminal 2, and searches for the desired shared data lc and Z or history data Id using the search condition specified by the member terminal 2 as a key. In addition, the shared data ID 120a value of the shared data lc or the history data ID 140a value of the historical data Id as a search result is delivered to the shared data display processing unit 25.

 [0077] The shared data display processing unit 25 displays the shared data display screen on the terminal 2, and the value of the shared data ID1 20a or the history data ID 140a delivered from the shared data search processing unit 24 or the tree display processing unit 29 described later. Based on the value of! /, It is a means to display the record contents of shared data lc or history data Id.

 FIG. 8 is an example of a shared data search screen 8 having a shared data search area 8a, a shared data list display area 8b, and a shared data content display area 8c. As shown in FIG. 8, after receiving an input of an arbitrary search condition on the shared data search screen 8 and executing the search, the shared data display processing unit 25 is searched within the same screen. The record contents of shared data lc or history data Id can be displayed.

 [0079] Specifically, the values recorded in the upper level list 120b, name 120c, update date 120d, registrant 120e, name 130d, value 130e, etc. are displayed in the record records of the searched shared data lc. The

 [0080] The value recorded in the value 130e is displayed after being appropriately edited in accordance with the value recorded in the mold 130c. For example, if the value recorded in the type 130c is “date” and the value 20050101 recorded in the value 130e, “January 1, 2005” is displayed on the display screen.

 [0081] When the value recorded in the type 130c is "attached file" and the value 130e records the name of the attached file and the directory in which the attached file is stored, the display screen The attached file name is displayed above, and when the display location is clicked, the attached file may be downloaded from the storage directory or displayed on another screen.

[0082] Each value recorded in the shared item record 120 may also be displayed after being edited as appropriate. For example, values recorded in the upper list 120b may be displayed at a glance even if they are displayed as they are. Since it cannot be grasped, the value of the name 120c of the shared item record 120 in which the value of the upper list 120b is recorded in the shared data ID 120a may be displayed.

Next, the contact data registration processing unit 26 displays a contact data registration screen on the terminal 2 and performs processing for registering or updating the contact data le. FIG. 9 shows an example of the contact data registration screen 9. Note that the contact data registration screen 9 in FIG. 9 has almost the same specifications as the mail creation screen used when creating a new reply mail in a general electronic mail system.

 [0084] Here, the contact data le is exchanged by two or more specific members in the group using the terminal 2, and only the members can search and browse the contact information management system. 3 is composed of a contact item record 160, a destination management record 170, and a contact association record 180 shown in FIG. One set of contact data le is associated with one to a plurality of shared data lc, one contact item record 160, one to a plurality of destination management records 170, and one to a plurality of contact association records. It is composed of 180.

 [0085] Note that new registration of contact data le in the contact data registration processing unit 26 can be performed by all members in the group.

[0086] The contact item record 160 includes items of a contact data ID 160a, a response source 160b, a subject 160c, a body text 160d, an attached file 160e, a sender 160f, and a transmission date 160g.

 [0087] In the contact data ID 160a, contact information, that is, an ID code that can identify the contact item record 160 is recorded.

 [0088] In the response source 160b, the value of the contact data ID 160a of another contact data le that becomes the response source of the contact data le is recorded. For example, when a certain contact data le is a response to an inquiry, the value of the contact data ID 160a of the original inquiry contact data le is recorded in the response source 160b.

As described above, by recording the value of the contact data ID 160a of the response source in the contact item record 160, the contact data le having the value of the response source 160b as the value of the contact data ID 160a is searched later. By answering a series of responses in a response relationship, it becomes possible to easily know the reason why the shared data lc was updated and the background of the update. Response source 160b If it is possible to specify more than one, it is possible to reply to multiple contact data le with one contact data le.

[0090] In the subject 160c, text information representing the subject of the contact information is recorded.

[0091] In the body 160d, text information representing the body of the contact information is recorded.

In the attached file 160e, when it is desired to attach a file to the body of the contact information, the file name of the file and the storage location of the file are recorded. If there are multiple files, they are recorded together.

 In this embodiment, the file is uploaded to the server 1 by using the function of the operation system of the contact information management program la or the server 1 and the terminal 2, and the attached file storage folder in the server 1 If a file storage folder that can be shared with other terminals 2 is created in the terminal 2 that is stored in the terminal 2 (not shown), the file may be stored in the file storage folder. In addition, each time a file is downloaded from terminal 2 to another terminal 2! /, Even! /.

 [0094] In the sender 160f, the value of the user ID 110a of the member who registered the contact data le is recorded.

 [0095] The date and time when the contact data le is registered is recorded in the transmission date and time 160g.

 [0096] Address management records 170 are created for the total number of members specified as the address (TO) and broadcast address (CC) of one contact information, and the contact data ID 170a, address 170b, segment Each item power of 170c and state 170d is also configured.

[0097] The contact data ID 170a has a contact item record 16 to which this destination management record 170 belongs.

A value of 0 contact data ID 160a is recorded, and 1 contact item record 160 forms a hierarchical structure in which one to a plurality of destination management records 170 hang.

[0098] Address 170b includes the user ID of the member specified as the address of the contact information or the broadcast address.

The value of 110a is recorded one record at a time.

[0099] In the section 170c, whether the member power destination or the broadcast destination recorded in the destination 170b is recorded by a code (for example, destination: 1, broadcast destination: 2, etc.).

[0100] In this embodiment, it is not possible to designate a member who is not registered as user data lb in the database as a destination, but of course, contact the destination 170b. It is also possible to specify an email address outside the information management system. Also, change the record structure of the user data lb so that members with external email addresses are included in the members of the group.

 [0101] In addition, in this embodiment, the user ID 110a value is recorded for each record of the destination management record 170. In a record that collects multiple values of the user ID 110a. By creating a group by assigning a name and specifying the group as the destination 170b, all members belonging to the group may be able to view and refer to the contact data le.

 [0102] In addition, when creating a group, one user record is assigned to each group, and an item of higher ID is added to each user record 110, and the group belonging to the higher ID is added. By setting the value of loop user ID 110a, the user records are hierarchically configured, and the value of group user ID 110a is specified as the contact data le destination 170b, thereby creating a chain of higher IDs. All subordinate members can view and refer to the contact data le addressed to the group.

 [0103] With this configuration, it is not necessary to record the values of multiple user IDs 110a each time in the destination 170b, and even if the number of members increases later, the upper ID of the user record is set. As a member of the group, the contact data le can be browsed and viewed retroactively, and there is no need to add and modify the destination management record 170 for each contact data le later. .

 [0104] The contact data le is either the value recorded in the destination 170b or the value recorded in the previous caller 160f. Only if it matches, it will be displayed on the screen of the member's terminal 2.

 [0105] In the state 170d, whether or not the text of the member contact information recorded in the destination 170b is read is recorded by a code (for example, division information such as unread: 1, read: 2, etc.).

As described above, by setting the status 170d as one item of the destination management record 170, for example, when displaying the record record contents of the contact data le on the terminal 2, the unread contact data le is already read. By distinguishing from the contact data le and displaying it in red, etc. It is possible to prompt the user to read the link information as soon as possible, and the contact information can be transmitted early.

 [0107] It should be noted that the value of the status 170d is updated when the terminal 2 of the member displays the record record content of the contact data le created with the member as the destination on the contact data display screen (not shown). It may be changed to read by accepting the click input of the “read” button, or automatically changed to read by displaying the record contents for a certain period of time. A little.

 [0108] The contact association record 180 is created only for the total number of shared data lc to which the contact data le is associated, and includes the field data of the contact data ID 180a, the shared data ID 180b, and the history data ID 180c.

 [0109] Contact data ID 180a is the value of the contact data ID 160a of the contact item record 160 to which this contact association record 180 belongs. One contact item record 160 contains one to more than one contact association record. A hierarchical structure in which 180 is hanging is formed.

 [0110] In shared data ID 180b, the value of shared data ID 120a of shared data lc associated with the contact data le to which this contact association record 180 belongs is recorded.

 In the history data ID 180c, when there is history data Id associated with the contact data le to which the contact association record 180 belongs, the value of the history data ID 140a of the history data Id is recorded. It should be noted that the history data ID 180c is a force that remains empty (0) when the contact data le is registered. Then, the shared data lc set in the shared data ID 180b is changed, and the shared data lc is changed to the history data Id. At this point, the value data of the history data 1d of the history data 1d is recorded in the history data ID 180c.

 [0112] Thus, the shared data ID 180b and the historical data ID 180c of the contact data le have the same value as the shared data ID 120a of any existing shared data lc and the historical data ID 140a of the historical data Id. Since the values are recorded, based on these values, the contact data le related to the desired shared data lc can be searched, browsed, or the communication data le This makes it possible to know the history data Id associated with the URL, and enables centralized management of shared information and contact information.

[0113] Shi force, 1 contact data le, 1 shared data lc 'history data Id as well as multiple Shared data of lc 'can be associated with historical data Id. Figure 4 shows a conceptual diagram of this association. As shown in FIG. 4, for example, “contact data 001” is associated with one shared data “shared data 100”, but “contact data 002” has “shared data 301” and “ It is associated with “History data 201-01”. As described above, it is expected that the search efficiency of the contact data le is improved by associating the contact data le 1S with the plurality of shared data lc and the history data Id.

 [0114] Moreover, in reality, there is a possibility that the method of association may differ depending on the members who have difficulty in associating 1 contact data le with 1 shared data lc on a one-to-one basis. In this sense, there is an advantage that the member can easily associate the contact data le with the shared data lc.

 [0115] The registration of the contact data le in the contact data registration processing unit 26 is performed by searching the shared data search processing unit 24 for the shared data ID 120a of the shared data lc to which the contact data le is to be associated. If the record contents of the data lc are displayed after being displayed on the terminals 2 and 3, the same value as the shared data ID 120a of the shared data lc is automatically copied to the shared data ID 180b of the contact data le. The data le becomes associated with the shared data lc.

 [0116] In addition to this, although not shown, the main processing unit 22 may be able to directly call the contact data registration processing unit 26. On face 9, it should be possible to search for shared data lc to be associated

[0117] The contact data search processing unit 27 displays the contact data search screen on the terminal 2, searches for the desired contact data le using the search conditions specified by the member terminal 2 as a key, and displays the search result. This is means for delivering the value of the contact data ID 160a of the contact data le to the contact data display processing unit 28.

[0118] Basically, since the contact data le is contact information exchanged between specific members, the range of the contact data le searched by the contact data search processing unit 27 is the sender 16 Of or Value of destination 170b Limited to contact data le that is the same as the value of user ID1 10a of the member who logged in at login processing unit 21. [0119] The contact data display processing unit 28 displays a contact data display screen on the terminal 2, and based on the value of the contact data ID1 60a delivered from the contact data search processing unit 27 or the tree display processing unit 29 described later, It is a means for displaying the record contents of the record of the contact data le. The range of contact data le that can be displayed by the contact data display processing unit 28 is the same as the search range of the contact data search processing unit 27.

 FIG. 10 is an example of the contact data search screen 10 having a contact data search area 10a, a contact data list display area 10b, and a contact data display area 10c. As shown in FIG. 10, after receiving any search condition input on the contact data search screen 10 and executing the search, the contact data display processing unit 28 displays the searched contact data le in the same screen. Can be displayed.

 [0121] Specifically, among the record records of the retrieved contact data le, subject 160c, body 160d, attached file 160e, sender 160f, date and time of transmission 160g, destination 170b, status 170d, shared data ID 180b, etc. Value power As appropriate, edited and displayed so that members can understand.

 [0122] For example, the value of the caller 160f is converted into the name 110e in the user record 110 and displayed, and the value of the status 170d is "read" or "unread" depending on whether it is 0 or 1. Displayed after conversion.

 [0123] Furthermore, the contact data display processing unit 28 displays a list of record records of a predetermined number or all of the contact data le in the response relation based on the value of the response source 160b of the contact data le. . As a result, the member can know the contact information exchanged in the past by using the contact data le in the response relationship.

 [0124] As shown in FIG. 10, only some items of the contact data le (in FIG. 10, the status, subject, text, sender, transmission date and time) may be displayed in a list. Note that the size of the display screen, change of display items, rearrangement of the display order of display items, and the like can be changed according to the preference of the member using the terminal 2. For example, the display order of display items can be arranged in ascending or descending order chronologically using the value of the transmission date 160g in the contact item record 160 as a key, and the values of other items are displayed as a key. It is also possible to do.

[0125] In addition, for example, unread contact data le is displayed as a list in tabular form on the main screen 6 in FIG. May be. As a result, when the logged-in member starts processing, the unread contact data le that is not missed can be confirmed on the main screen 6 that is always displayed after the login screen 6.

 [0126] In that case, the main processing unit 22 calls the contact data search processing unit 27, and the value of the destination 170b matches the value of the user ID 11 Oa of the logged-in member, and the value S "of the state 170d The record that is “unread” is extracted, and the record contents of the contact item record 160 whose contact data ID 17b matches the value of the contact data ID D 160a, one record per line (not shown) Display).

 [0127] Further, the shared data display processing unit 25 is displayed on the display screen of the terminal 2, and displays an instruction to display the record record contents of the contact data le associated with the shared data lc. If there is an operation, the contact data search processing unit 27 is called, and the contact data search processing unit 27 contacts the shared data ID 130a value of the shared data lc as the value recorded in the shared data ID 180b. It is possible to retrieve the data le.

 Note that a search means corresponding to the contact data search processing unit 27 of the present embodiment may already be included in the contact data display processing unit 28. This eliminates the need for the contact data display processing unit 28 to operate through two means of the shared data display processing unit 25 and the contact data search processing unit 27.

 [0129] When called from the main processing unit 22, the tree display processing unit 29 displays a tree display screen on the terminal 2, and displays the value of the upper list 120b of the shared data lc and the value of the shared data ID 140b of the history data Id. In other words, it is a means of displaying the interconnection relationship between the shared data lc and the history data Id in a tree shape.

 FIG. 4 is a diagram showing a concept of tree display of shared data lc and history data Id displayed by the tree display processing unit 29. As shown in FIG. 4, the history data Id is displayed to be lower than the shared data lc. As a result, the change history of the shared data lc can be grasped at a glance.

FIG. 11 is an example of a contact data list display screen 11 having a tree display area l la, a contact data list display area l lb, and a contact data display area 11c. As shown in FIG. 11, in the tree display area 11a, the tree display processing unit 29 has shared data stored in the server 1. The value of ID 120a is searched for the shared data lc as recorded in the upper list 120b, and the history data Id whose value of the shared data ID 120a is recorded in the shared data ID 140b of the history data Id is searched. Then, the mutual relationship between the shared data lc or between the shared data lc and the history data Id is given and a tree display is performed based on the mutual relationship.

 It should be noted that whether or not the history data Id is included in the interconnection relationship in the tree display area, such as when the tree display area with a large number of history data Id is likely to become complicated, depends on whether the terminal 2 or the server 1 It can be set arbitrarily based on the force instruction.

 FIG. 12 is a force tree display area 12a, which is an example of the shared data content display screen 12 having the tree display area 12a and the shared data content display area 12b. The tree display area 12a is the same as the tree display area 11a of FIG. The shared data content display area 12b is the same as the shared data content display area 8c in FIG.

 [0134] The contact information management system according to the present embodiment is configured so that the contact data registration processing unit 26 registers the contact data 1e and the user ID 110a recorded in the sender 160f or the destination 170b of the contact data le. By logging in to the contact information management system, it is possible to search for, view and refer to the registered contact data le at the terminal 2 that has logged in. For example, contact information management Program la can be linked to an existing e-mail transmission / reception program (not shown).

 [0135] In that case, the e-mail transmission / reception program is called when the contact data registration processing unit 26 registers the contact data le in the server 1, and based on the value of the user ID 110a recorded in the destination 170b. Search the member's email address and send contact data le to the email address. If the user record 110 includes an item for recording the member's email address, the member's email address can be extracted immediately.

 [0136] When sending contact data le using an e-mail sending / receiving program, SMTP

Operate the (Simple Mail Transfer Protocol) server, and from the contact information management program la, set the destination email address, subject (title), and body text as arguments according to the record content of the registered contact data le, and send Contact the original email address It may be possible to send an e-mail by setting a fixed e-mail address that means the information management system or server 1 or an e-mail address that is the reply destination of the e-mail, and transferring this information to the SMTP server. .

[0137] Furthermore, when the shared data registration processing unit 23 registers and updates the shared data lc, the e-mail transmission / reception program sends all the members registered as the user data lb. Alternatively, notification that shared data lc has been registered or updated may be sent.

 [0138] As a result, the member who received the notification can log in to the contact information management system immediately and check the change history of the shared data and the details of the contact data related to the shared data. Be able to quickly know that changes have occurred

[0139] In addition, when an e-mail transmitted by this e-mail transmission / reception program is received by a mail receiving function of a personal computer or a mobile phone other than the terminal 2, a reply to the e-mail can be made without speaking to this system. You may be able to register contact data le by sending an email.

[0140] For this purpose, the communication data registration processing unit 26 is configured to receive the contents of the mail received by the electronic mail transmission / reception program. In this case, the contact data registration processing unit 26 creates the contact data ID 160a based on the received mail title, destination, sender, text, and attached file information and writes it to the database.

 [0141] For example, by embedding the contact data ID 160a in the format of "MSGID: 12 34" at the end of the title of an email sent as an email, the email of general email software or mobile phone When a reply email is created from the compose screen, the contact data ID160a of the reply source is automatically embedded at the end of the title of the email. 26 Force You can determine the response source 16 Ob when writing the reply contents as the contact item record 160 to the database.

[0142] In this case, the contact data ID 160a is embedded at the end of the email title! /, Na! /, If the contact data registration processing unit 26 receives the message, it may be configured to register it as new contact data instead of replying! /.

[0143] Further, for example, the contact data registration processing unit 26 is configured to change the state 170d of the destination management record 170 from unread to read by sending a blank mail without a body as a reply mail. Also good.

[0144] The state 170d of the destination management record 170 is automatically updated by the contact information management program la even when the member displays the contact data le addressed to the member on the contact data display screen.

 [0145] According to the contact information management system described above, the server 1 includes the shared data lc shared within the group, the history data Id before the update of the shared data lc, and the terminal 2 of a specific member. Since the contact data le exchanged in step 1 is recorded in association with each other, the member searches the shared data lc, the change history of the shared data lc, and the associated contact data le as appropriate. · Browsing and browsing can be performed, and unified management of shared information and contact information becomes possible.

 [0146] Since the contact data le is recorded in the server 1 in association with the shared data lc and the history data Id organized in a hierarchical structure, the contact data le associated with the shared data lc By speaking, it is possible to easily know the reason and background of the shared information update that was exchanged when the shared data lc was updated in the past, and it is possible to prevent misunderstandings regarding the shared information. It is possible to improve the quality and efficiency of work execution.

 [0147] Further, according to the contact information management system of the present invention, for example, a series of contact data le created as a response (reply) is displayed in association with each other, and each member has been transmitted to himself / herself. The contact data le can be referred to in association with the shared data lc and the history data Id, and only the unread contact data le can be displayed as a list. For this reason, not only the management of shared data lc but also the management of change history of shared data lc and the management of contact data le, which has been entrusted to individual management, are accurately and collectively performed. It can be done well.

[0148] The user data lb, shared data lc, history data ld, and contact data le described above are It is desirable to store it in the database in consideration of the efficiency of program creation and execution performance. At that time, depending on the database management software used, there is also a function that can save the file directly in the item part of the record. In such a case, it is not necessary to create a separate folder for storing the attached file. It is also possible to set an item for storing the attached file in the record of the shared data lc and an item for storing the attached file in the record of the contact data le.

 [0149] In addition, as a recording method of an item in which a plurality of values are listed and recorded in each item of the record, there are a method of concatenating with a delimiter such as a tab symbol, and a method of saving as data of a list structure Of course, other known recording methods may be used.

 [0150] When an e-mail transmission / reception program is used, the e-mail transmission / reception program attached to the operating system of the server 1 or the e-mail transmission / reception program that is generally distributed is incorporated into the server 1. May be. The e-mail transmission / reception program may be incorporated in the terminal 2.

 [0151] In addition, the shared data search processing unit 24 and the contact data search processing unit 27 are basically the same in the search method and program configuration except that the types of data to be searched are different. One search processing unit may be integrally configured. Similarly, the shared data registration processing unit 23 and the contact data registration processing unit 26 are the same in the point of registering data, so even if they are integrally configured as one registration processing unit. Good. Similarly, the shared data display processing unit 25 and the contact data display processing unit 28 may be integrally configured as one display processing unit! /.

 [0152] In addition, the shared data lc and the history data Id are not necessarily recorded separately in the server 1 as shown in FIG. The historical data Id may be integrated and managed with the shared data lc by adding. In this case, for example, if the history data ID value in the shared data lc is 0, the shared data lc is the latest information, and if the history data ID value is other than 0, the shared data lc is already present. The contact information management program la may be configured to determine that the history data Id is updated and the latest version exists.

[0153] In addition, when the contact information management system of the present invention is incorporated in a routine business system or the like In many cases, it is not necessary to cause individual members to newly register the shared attribute record 130. For example, the shared attribute record 130 is not used and the attribute value (type , Name, value, etc.) are now defined!

 Example 1

 [0154] In the following, a detailed embodiment when the contact information management system of the present invention is applied to the management of product sales operations within a specific group, examples of display screens of terminal 2 in Figs. 5 to 12, This will be described based on the configuration diagram of FIGS. 1 and 2 and the data structure diagram of FIG. In the following, it is assumed that the display screens of FIGS. 5 to 12 are displayed by the web browser on the terminal 2 of the member who uses the contact information management system in this embodiment.

 [0155] In addition, the records constituting the user data lb, shared data lc, history data ld, and contact data le shown in FIG. The record contents of the shared data lc and history data Id can be searched and viewed on the terminal 2 of a member who has been previously authorized within the group, and the record record contents of the contact data le It shall be possible to search and browse on the terminal 2 of the member who exchanged contact information based on the contents. In addition, it is possible to register the shared data lc and contact data le according to the authority lOd of the user record 110.

 [0156] First, the login processing unit 21 of the contact information management program la displays the login screen 5 shown in FIG. 5 on the member terminal 2, and accepts the input of the member's login ID and password. Therefore, the member inputs the login ID and password in the login ID entry field 51 and password entry field 52 of the login screen 5 and touches the login button 53 with the mouse, and the login processing unit 21 enters the login ID. Using the value entered in column 51 as a key, the record whose login ID 110b matches the key is read from user data lb that has already been registered, and the value entered in password entry column 52 is read. Check whether it matches the password 110c of the embedded record.

[0157] Here, if the user data lb that matches the key does not exist or the password does not match, the login processing unit 21 displays an error message in the message display field 54 of FIG. Prompts you to enter your login ID and password again. If the login ID and password match, the login processing unit 21 calls the main processing unit 22.

[0158] When the user data lb that matches the key exists, the main processing unit 22 allows the member to log in to the contact information management system, and displays the main screen 6 as shown in FIG. The main screen 6 is divided into a toolbar 6a at the top of the screen and a content display area 6b. The member name display field 61 in the toolbar 6a displays the name 110e of the user data lb read by the login processing unit 21.

[0159] In the following, the member whose name is displayed in the member name display field 61 of the main screen 6 is the logged-in member, and the terminal 2 on which the main screen 6 is displayed is the member Terminal 2 is logged in.

[0160] When the logout button 62 in the toolbar 6a is clicked, the main screen 6 is closed and the previous login screen 5 is restored.

[0161] Furthermore, the screen selection field 63 in the toolbar 6a is a field for selecting a screen displayed in the content display area 6b in the main screen 6 by a drop-down method.

In this embodiment, there are four types of options displayed in the screen selection field 63: contact data list display, shared data content display, contact data search, and shared data search.

[0163] When the member clicks one of the options with a mouse or the like, the main processing unit 22 calls another processing means corresponding to the option, and displays a screen for performing the process in the content display area 6b. Display within.

[0164] When the main processing unit 22 accepts the selection of the contact data list display, it calls the tree display processing unit 29 and the shared data search processing unit 24, and the tree display area 1 la shown in FIG. The contact data list display area 11, consisting of the contact data list display area l ib and the contact data display area 11 c, is displayed in the content display area 6 b of the main screen 6.

[0165] The tree display processing unit 29 selects any of the shared data lc stored in the server 1.

Extract one set and search for other shared data lc recorded in the shared data ID 120a in the value list 120b. That is, the former shared data lc is under the latter shared data lc.

[0166] In this way, the tree display processing unit 29 performs an upper list 120b of the shared data lc sequentially searched. The shared data lc that matches the value of shared data ID120a is searched for using the value of the shared data ID120a, and the parent-child relationship between the shared data lc and the value of the name 120c of the shared data lc is determined for all the stored shared data lc. It is displayed in the tree display area 11a by the node displaying the symbol and the branch representing the relationship between the nodes.

 [0167] In the figure, the sales node 110a, product X110b, product Y110c, function 110f, customer l lOg, which are the displayed nodes, all have the value of the name 120c. In addition, product X110b, product Y110c, and customer lOg are connected to branch Y11a through sales branch 110a, and function 110f is connected to product Yl10c through branch 11lb. Has been. In other words, the subordinate concepts of sales operations are product X, product Y, and customer, and that the subordinate concept of product X is a function, the display content in the tree display area 11a can be divided.

 [0168] Furthermore, in the present embodiment, the tree display processing unit 29 searches for the shared data lc in which the value of the shared data ID 140b of the history data Id is recorded in the shared data ID 120a, and the tree display area 11a The nodes 110d and 110e (in this example, displayed as product Y (history)) with the value 140d of the history data Id are displayed, and the value of the name 120c of the searched shared data lc is displayed. A tree display is made such that the branch 11 lc is connected to a lower level of the node 110c (in the present embodiment, indicated as product Y).

 That is, in the tree display area 11a, not only the parent-child relationship between the currently registered shared data lc is displayed, but also the history data Id representing the shared data lc before being updated is displayed as a node. Since it is displayed below the node representing the current shared data lc, it is possible to easily grasp the update history of the shared data lc by moving the node of the history data Id from the node of the shared data lc.

 [0170] It should be noted that it is possible to arbitrarily decide whether or not to display the node representing the history data Id in the tree display area 11a. For example, a switch button for displaying or not displaying may be provided in the toolbar 6a. . In addition, when displaying the node of the history data Id, in order to clearly indicate that it is a history, it is displayed in a color different from the color of the node of the shared data lc, or following the value of the name 14 Od in the node. The value of update date 140a and the value of registrant 140f may be displayed.

[0171] When terminal 2 clicks a specific node (product XI 10b in this example) in tree display area 11a, tree display processing unit 29 changes the display color of the clicked node, and No Clarify that the mode is selected. The tree display processing unit 29 then compares the value of the shared data ID 120a of the selected node and the shared data lc represented by the node below the node and the user ID 110a of the logged-in member's user data lb. The value is passed to the contact data search processing unit 27.

[0172] The tree display processing unit 29, when clicked by the node power terminal 2 representing the history data Id, uses the value of the history data ID 140a of the history data Id and the logged-in member. The data of the user ID 110a of the user data lb is transferred to the contact data search processing unit 27.

 [0173] The contact data search processing unit 27 records the transferred shared data ID 120a value in the shared data ID 180b, and the contact data 1 e (if the passed data data is the value of the history data ID 140a, Search the contact data le) whose value is recorded in the history data ID 180c.

 [0174] Furthermore, the contact data search processing unit 27 is contact data associated with the shared data lc subordinate to the shared data lc to which the searched contact data le (or history data Id) is associated. Also search le and history data Id.

 [0175] The contact data display processing unit 28 displays a list of record records of the searched contact data le (or history data Id) in the contact data list display area l ib. In this embodiment, each line in the contact data list display area l ib includes a predetermined capacity value (for example, the first 5 characters) of the subject 160 c in the contact item record 160, the body text Of the 160d values, a value for a predetermined capacity (for example, the first 10 characters), the value of the caller 160f, the value of the transmission date and time 160g, and the value of the state 170d in the destination management record 170 Recognized text data (for example, the value of the caller 160f is the value of the name 110e, the value of the status 1 70d is “read” or “unread”) and the like are displayed.

 [0176] Conventionally, when personally managing received e-mails, for example, it is common to create e-mail storage folders in a tree format and move e-mails sequentially to the corresponding folders. is there.

[0177] In that case, if you subdivide the folder too much, even the person who created the folder will have no power to know which folder the e-mail was stored in after the time has passed. Na Each time I had to click on an individual folder to find the email.

 [0178] In this example, when the upper node in the tree display area 11a of the contact data list display screen 11 is clicked, the shared data lc corresponding to the clicked node and the lower level of the shared data lc are displayed. The contact data le associated with the shared data lc is displayed in the contact data list display area l ib. In other words, the contact data le associated with the lower node can be browsed and referenced transparently from the upper node of the hierarchical shared data lc, so that the desired data can be obtained without clicking each node. The contact data le can be found quickly.

 [0179] In this way, if you click on the node of the top shared data lc, you can browse and see all the contact data le, and the number of contact data le displayed is lower as you go down. Thus, the desired contact data le can be searched while narrowing down. Such a search method is generally called drill-down.

 [0180] Contact data list display area l When any of the lines representing the record record contents of the contact data le displayed in ib is clicked from the terminal 2, the contact data display processing unit 28 is clicked. The line is displayed in a color different from that of the other lines, and the record data details of the contact data le corresponding to the clicked line are displayed in the contact data display area 11c.

 [0181] In this example, the value of the subject 160c of the contact item record 160, the value of the caller 160f (in this example, described as "FROM: BBBBBB"), the value of the transmission date 160g, the value of the body 160d, The value of the attached file 160e and the value of the destination 170b of the destination management record 170 (in this embodiment, “TT: written as YAMADAJ”) are displayed.

 [0182] Furthermore, in the contact data display area lc, the value of the shared data lc associated with the displayed contact data le and the name 120c of the shared data lc above the shared data lc is " Item "is displayed.

In this example, the value of the shared data ID 180b of the displayed contact data le is recorded in the shared data lc recorded in the shared data ID 120a and the upper list 120b of the shared data lc. The value of the name 120c of the shared data lc (if there is a higher rank, the higher rank shared data lc) is displayed in the tree display area 11a, for example, “Z sales business Z product X” They are displayed concatenated with a delimiter such as a slash (z) in the order of the highest power in the tree.

 [0184] When an attached file name in the contact data display area 11c (in this example, "filename.txt") is clicked, it is downloaded from the attached file power server 1 or the attached file storage destination, and the terminal It's going to be opened in 2, but ...

 [0185] In addition, the values such as the address 170b, the caller 160f, and the transmission date 160g displayed in the contact data display area 11c are recognizable by members as in the contact data list display area l ib. Appropriately converted and displayed as text data.

 [0186] The contact data display processing unit 28 displays the record record contents of the contact data le in the contact data display area 11c, and then changes the status 170d of the destination management record 170 from "unread" to "already". It may be changed to “Read”. In addition, for example, a “read as read” button is displayed in the contact data display area 11c, and clicking this button actively changes the status 170d to “read” so that members can actively Let's change the state.

 [0187] When the terminal 2 clicks the new creation button 112 or the reply button 11 3 in the contact data display area 11c, the contact data display processing unit 28 calls the contact data registration processing unit 26, and the contact data registration processing unit 26 Displays a contact data registration screen 9 as shown in FIG. 9 on a separate screen from the main screen 6.

 [0188] The contact data registration screen 9 in FIG. 9 has a button 91 for closing the entire screen, a subject input field 92, a related item input field 93, a destination (TO) input field 94, and a broadcast destination (CC) input. It consists of a field 95, a text input field 96, an attached file input field 97, and a send button 98.

 [0189] When the reply button 113 is clicked in the contact data display area 11c of Fig. 11, the contact data registration processing unit 26 sets the contact data le displayed in the contact data display area 11c. Of the record contents, the value of subject 160c with “RE:” indicating the meaning of the reply is automatically entered in subject entry field 92 of contact data registration screen 9 and the value of sender 160 f Is automatically entered in the destination entry field 94, and the name 120c of the shared item record 120 in which the value of the shared data ID 180a is recorded in the shared data ID 120a is automatically entered in the related item entry field 93.

[0190] In the attached file input field 97, for example, "attached file" (not shown) is displayed. By clicking the button with the mouse, you can select an arbitrary file saved in the storage medium such as the hard disk of terminal 2 or server 1, the selected file name is automatically entered, and the file is stored in the attachment storage folder. You can upload it.

 [0191] When terminal 2 inputs text data in each input field or designates an attached file, and clicks send button 98, contact data registration processing unit 26, based on the input data, A set of contact data le is generated and stored in server 1.

 Specifically, the value entered in the subject entry field 92 is recorded in the subject 160 c of the contact item record 160. Further, based on the value entered in the related item input field 93, the value of the shared data ID 120a of the shared data lc to which the contact data le registered here is associated is changed to the shared data ID 180b of the contact related record 180. To be recorded.

 [0193] In addition, the data entered in the destination input field 94 and the broadcast destination input field 95 are recorded in the destination 170c of the destination management record 170 in a data format that can distinguish between the destination and the broadcast destination. The destination or the broadcast destination is distinguished by the classification 170c of the destination management record 170.

 [0194] The value entered in the text entry field 96 is recorded in the text 160d of the contact item record 160. The value entered in the attached file input field 97 is recorded in the attached file 16 Oe of the contact item record 160.

 [0195] When the contact data le is associated with a plurality of shared data lc, as many contact association records 180 as the number of associated data are registered. Of course, the same value is recorded in the contact data ID 180a of all records related to contact 180.

 [0196] In addition, in the response source 160b of the contact item record 160, when the new creation button 112 of the contact data list display screen 11 is clicked and the contact data registration screen 9 is displayed, it becomes empty and the reply button 113 When is clicked and the contact data registration screen 9 is displayed, the value of the contact data ID 160a of the contact data le displayed in the contact data display area 11c is recorded.

[0197] The value of the user ID 110a of the logged-in member is recorded in the sender 160f, and the value indicating the date and time when the send button 98 is clicked is recorded in the transmission date and time 160g. In the state 170d of the destination management record 170, a code meaning unread is recorded. [0198] The history data ID 180c of the record with contact relation 180 has an empty value (0) recorded at the time of registration of the contact data le. The shared data ID 120b has the value of the shared data ID 180b. Is transferred to the history data Id, the value of the history data ID 140a of the history data Id is recorded.

 [0199] The contact data ID 160a, contact data ID 170a, and contact data ID 18 Oa of the three types of records recorded in each item in this way (multiple records may be created for each type) have the same number. Is assigned and recorded by automatic numbering, and registration of the contact data le is completed.

 [0200] Returning to the description of the contact data display area 11c in Fig. 11, when the related item change button 114 in the same area is clicked from the terminal 2, the contact data display processing section 28 is changed to the shared data registration processing section. 23, the shared data registration processing unit 23 displays a related item change screen (not shown) for changing the currently specified related item (the shared data lc with which the contact data le is associated). The contact data le associated with the contact data 1 is changed to the value of the shared data ID 180b of 80, and the value of the history data ID 180c is set to 0.

 [0201] In this way, the shared data lc to which the contact data le is associated can be changed and added later. Feel free to create. Also, if the subject matter of the contact information has changed while exchanging contact information, the associated shared data lc can be added or changed from that point.

 [0202] Returning to the description of the main screen 6 in FIG. 6, when the main processing unit 22 accepts the selection of the shared data content display, the tree display processing unit 29 and the shared data search processing unit 24 are connected. By calling, the shared data content display screen 12 including the tree display area 12a and the shared data display area 12b shown in FIG. 12 is displayed in the content display area 6b of the main screen 6.

 [0203] The contents and display method displayed in the tree display area 12a in Fig. 12 are the same as the contents and display method displayed in the tree display area 11a in Fig. 11, and thus description thereof is omitted.

[0204] On the shared data content display screen 12 in FIG. 12, when the terminal 2 clicks a specific node (product XI 20b in this example) in the tree display area 12a, the tree display processing unit 29 Change the display color of the clicked node to clarify that the node is in the selected state. Then, the tree display processing unit 29 passes the value of the shared data ID 120a of the shared data lc represented by the selected node to the shared data display processing unit 25.

 It should be noted that the tree display processing unit 29, when clicked by the node power terminal 2 representing the history data Id, selects the value of the history data ID 140a of the history data Id as the shared data display processing unit 25. To hand over.

 The shared data display processing unit 25 displays the record recording content of the shared data lc (or history data Id of history data ID 140a) of the delivered shared data ID 120a in the shared data display area 12b.

 In this embodiment, the shared data display area 12b includes the values of the shared data ID 120a, the name 120c, the upper list 120b, the update date 120d, and the registrant 120e among the record contents of the shared data lc (this embodiment Then, “ID: 2”, “Name: Product X”, “Top: Z Sales Operations”, “Renewal Date: 2005Z06Z01 16: 25”, “Register: Taro Yamada”) Text that can be recognized by members It is converted into data and displayed as appropriate. In addition, the value of the upper list 120b may be displayed not only by the latest higher rank but also by the delimiter such as a slash (Z) up to the highest value.

 [0208] Furthermore, in the shared data display area 12b, text data that can be recognized by members according to the value of the name 130d of the shared attribute record 130 and the value type of the value 130e of the data type 130c, Appropriately converted and displayed.

 [0209] In the shared data display area 12b of FIG. 12, "description", "sales start", "department in charge", and "attached file" display the values of the names 130d of multiple shared attribute records 130. Yes, “Store information about product X under this”, “2005Z08Z01”, “Global Sales Department”, and rfilename.txt are the contents of the record of value 130e corresponding to each name.

 [0210] For example, in this embodiment, the type 130c of the "attached file" is an attached file, so that when the terminal 2 clicks "filename.txt", the file with the name can be downloaded. Become.

[0211] It should be noted that the record record contents display method of the history data Id is also the above-mentioned shared data lc record. It is the same as the display method of the code record contents, and the search 'displayed record type is only the difference between the shared item record 120 · shared attribute record 130 or the history item record 140 · historical attribute record 150.

 [0212] In the shared data display area 12b in FIG. 12, when the terminal 2 clicks the new creation button 122 or the correction button 123 in the same area, the shared data display processing section 25 displays the shared data registration processing section 23. The calling and shared data registration processing unit 23 displays a shared data registration update screen 7 as shown in FIG.

 [0213] The shared data registration update screen 7 in FIG. 7 includes a button 71 for closing the entire screen, a new attribute addition button 72, a save button 73, a name input field 74, a higher level input field 75, and an attribute name input field. 76 and a value input field 77.

 [0214] When the correction button 123 is clicked in the shared data display area 12b of the shared data content display screen 12 in FIG. 12, the shared data registration processing unit 25 displays it in the shared data display area 12b. Of the recorded records of shared data lc, the value of name 120c is entered in name entry field 74, the value of upper list 120b is entered in upper entry field 75, and the value of name 130d is entered in attribute name entry field 76. The value of the value 130e is automatically entered in the column 77 (the name 130d and the value 130e are displayed in correspondence with those in the same shared attribute record 130).

 [0215] Regardless of the ability to newly register or update the shared data lc, the terminal 2 can appropriately input / modify text data in each input field or click the new attribute addition button 72 to enter the attribute name input field. 76 and the value entry field 77 are additionally displayed, data for the name 130d and value 130e are entered, and when the save button 73 is clicked, the shared data registration processing unit 25 performs the following operation based on the entered data. Register or update a set of shared data lc.

Specifically, the value input in the name input field 74 is recorded in the name 120c of the shared item record 120. Further, the value input in the upper input column 75 is recorded in the upper list 120b. In addition, the value displayed in the attribute name input field 76 and the value input in the corresponding value input field 77 constitute a set of shared attribute records 130, which are recorded in the name 130d and value 130e, respectively. The Although not shown in the figure on the shared data registration update screen 7, a column for inputting the value of the type 130c may be provided, and the type 130c is determined based on the value input in the value input column 77. It will be automatically recognized and granted.

 [0217] When the add new attribute button 72 is clicked, the number of shared attribute records 130 increases accordingly. In this way, any number of shared attribute records 130 can be combined with one shared item record 120, and depending on the type of shared data lc managed by the contact information management system, the shared information records Items to record the contents can be set freely.

 [0218] If there are a plurality of shared attribute records 130, they are registered in one shared item record 120 so that they can be distinguished by the attribute ID 140a.

 [0219] In addition, a value indicating the date and time when the save button 73 was clicked is recorded in the update date and time 120d of the shared item record 120c, and the registrant 120e is logged in on the terminal 2 that clicked the save button 73. The value of member user ID 110a is recorded.

 [0220] In this way, the same number is assigned to the shared data ID 120a and shared data ID 130a of the two types of records recorded in each item by automatic numbering, recorded, and registration of the shared data lc 'update Is completed. In the case of updating, the number already assigned may continue to be used as the value of the shared data ID 120a, 130a.

 [0221] Furthermore, in the shared data display area 12b in FIG. 12, the correction button 123 is clicked, and the input content in any of the input fields is changed on the shared data registration update screen 7 in FIG. When 73 is clicked, the shared data registration processing unit 23 performs a process of copying the recorded contents of all the records constituting the shared data lc before the change to each record of the history data Id.

 [0222] Specifically, the shared data ID 120a to the registrant 120e of the shared item record 120 before the change are each transferred to the shared data ID 140b to the registrant 140f of the history item record 140, and all before the change The attribute ID 130b to value 130e of the shared attribute record 130 are transferred to the attribute ID 150b to value 150b of the history attribute record 150, respectively. Then, the same number assigned by the automatic numbering is recorded in the history data IDs 140a and 150a and registered as the history data Id.

[0223] In addition, among records with contact relation 180, for records where shared data ID 180b matches the updated shared data ID 120a and history data ID 180c is 0, history Overwrite the value of data ID 180c with the value of history data ID 140a.

[0224] As described above, the record content of the shared data lc can be changed at any time. In addition, since the tree structure can be changed by adding the shared attribute record 130 or changing the value of the upper list 120b, it is possible to encourage the member to voluntarily register the shared data lc.

[0225] Returning to the description of the main screen 6 in FIG. 6, when the main processing unit 22 accepts the selection of the contact data search, the contact data search processing unit 27 is called and the contact data search shown in FIG. 10 is performed. A contact data search screen 10 including a condition input area 10a, a contact data list display area 10b, and a contact data display area 1 Oc is displayed in the content display area 6b of the main screen 6.

 [0226] Contact data search condition input area 10a includes search execution button 101, related item input field 102, destination (TO) input field 103, caller (FROM) input field 104, subject input field 105, , A text input field 106 and an attached file name input field 107.

 [0227] The related item input field 102 corresponds to the shared data ID 180b of the contact association record 180, and the destination input field 103 corresponds to the destination 170b of the destination management record 170. The column 104 corresponds to the caller 160f of the contact item record 160, the subject input column 105 corresponds to the subject 160c of the contact item record 160, and the body input column 106 corresponds to the body 160d of the contact item record 160. The attached file name input field 107 corresponds to the attached file 160e of the contact item record 160.

 [0228] In the related item input field 102, the value of the shared data ID 180b or the name 120c of the shared item record 120 may be directly input. , Display a reference button (not shown), and click the browse button to display the shared data lc tree display as shown in the tree display areas 11a and 12a of FIG. 11 and FIG. 12 on a separate screen. The node of the target shared data lc may be selected from among them. It is also possible to input or select multiple shared data ID 180b values and specify them by connecting them with AND and OR.

[0229] When a value as a search condition is input from any of the terminals 2 to any of the input fields 102 to 107 and the search execution button 101 is clicked, the contact data search processing unit 27 displays the input value power. The contact data le recorded in each item of the record corresponding to each input field is detected. The search result is transferred to the contact data display processing unit 28.

 [0230] The search method may specify any of complete match, forward match, backward match, and partial match between the value entered in the input field and the record record content. Input fields whose values are empty are not used as search conditions. In addition, when values are entered in multiple input fields, either AND search or OR search may be selected.

 [0231] Also, in this embodiment, when a value is entered in the related item input field 102, first, the contact association record 180 whose value is recorded in the shared data ID 180b is searched, and the corresponding By searching for the shared item record 120 whose value is recorded in the upper list 120b, the shared data 1c having the value input in the related item input field 102 in the shared data ID 120a and the lower level shared data lc It is possible to search for contact data le associated with.

 [0232] In this manner, if the higher-level shared data lc is specified and entered in the related item input field 102, the contact data le associated with the shared data lc that is lower than the specified shared data lc If the shared data lc associated with the contact data le you want to find is not accurately divided, by specifying the upper shared data lc as the associated destination, Desired contact data le can be found.

 [0233] In addition, since there may be a plurality of association destinations, there is a high possibility that the desired contact data le can be found in a short time even if there is no power to reliably associate with which shared data lc. This makes it possible to search for contact data le from the perspective of individual members. Furthermore, by specifying search conditions that combine multiple shared data lc with AND and OR conditions, flexible search such as contact data le related to shared data lc for both “Product X” and “Customer A” is possible. Is possible.

[0234] The contact data display processing unit 28 displays a part of the record contents of the retrieved contact data le in the contact data list display area 10b. The display method and display format in the contact data list display area 10b, and the method and display format for displaying the details of the contact data le of the line clicked in the contact data list display area 10b in the contact data display area 10c. The method of registering contact data le with the new creation button 108 and reply button 109 in the contact data list display area 10b, and the shared data associated with the related item change button 100 For example, how to display the contact data list display area l lb, the contact data display area 11c in the contact data list display screen 11 of Fig. 11, and the display format, etc. Since this is the same, the description thereof is omitted.

 [0235] In addition, in the contact data list display areas 10b and l ib in Fig. 10 and Fig. 11, the response relationship of the contact data le is collected and the ones in the response relationship are displayed in order from the first contact data le. It may come to be. In this case, the contact data search processing unit 27 searches the contact item record 160 in which the value of the response source 160b of the contact item record 160 is recorded in the contact data ID 160a, and the contact item record 160 searched there. Continue searching until the value of the response source 160b becomes empty, and display the record records of the contact data le in the order of search or reverse.

 [0236] Returning to the description of the main screen 6 in FIG. 6, when the main processing unit 22 accepts the selection of the shared data search in FIG. 6, the shared data search processing unit 24 is called and shown in FIG. The shared data search screen 8 including the shared data search condition input area 8a, the shared data list display area 8b, and the shared data display area 8c is displayed in the content display area 6b of the main screen 6.

 [0237] The shared data search condition input area 8a includes a search execution button 81, an upper input field 82, a name input field 83, an attribute name input field 84, and a value input field 85. The upper input field 82 corresponds to the upper list 120b of the shared item record 120, and the name input field 83 corresponds to the name 120c of the shared item record 120, and the value input with the attribute name input field 84. Column 85 corresponds to the name 130d and the value 130e of the shared attribute record 130, respectively. The specifications of the attribute name input field 84 and the value input field 85 are the same as those of the attribute name input field 76 and the value input field 77 in the shared data registration 'update screen 7 in FIG.

 [0238] When a value as a search condition is input from any terminal 2 to any of the input fields 81 to 85 and the search execution button 81 is clicked, the shared data search processing unit 27 Search for shared data lc or history data Id recorded in each item of the record corresponding to each input field, and search results (shared data ID120a or history data Id searched history data Id history data ID140a) is delivered to the shared data display processing unit 25.

[0239] The shared data display processing unit 25 records the shared data lc or history data Id that has been delivered. The recorded contents are displayed in a list in the shared data list display area 8b. In the present embodiment, each line in the shared data list display area 8b has a predetermined capacity value (for example, the first five characters) of the value of the name 120c in the shared item record 120, Value of registrant 120e, value of update date and time 120d Appropriately converted into text data that can be recognized by members (for example, the value of registrant 120e is the value of name 110e) and the like.

 [0240] When the search result is history data Id, values such as the name 140d, update date 140e, and registrant 140f of the history item record 140 are displayed as in the shared data lc.

 [0241] When either of the lines representing shared data lc or history data Id displayed in shared data list display area 8b is clicked from terminal 2, shared data display processing unit 25 is clicked. The line is displayed in a color different from that of the other lines, and the shared data search processing unit 24 passes all the record contents of the clicked shared data lc or history data Id to the shared data display processing unit 25.

 [0242] The shared data display processing unit 25 displays the record recording contents of the shared data lc or the history data Id in the shared data display area 8c based on the delivered record recording contents. The contents displayed in the shared data display area 8c, the screen specifications, and the processing contents after the new creation button 86 and the correction button 87 are clicked are basically shared in the shared data display screen 12 of FIG. The description is omitted because it is the same as that displayed in the data display area 12b.

 [0243] As with the search methods described so far, the search method is designated as any of complete match, forward match, backward match, and partial match between the value entered in the input field and the record record content. It doesn't matter. An input field whose value is empty is not used as a search condition. In addition, when values are entered in multiple input fields, either AND search or OR search may be selected.

[0244] In the upper entry field 82, the value of the shared data ID 120a or the name 120c of the shared item record 120 may be directly input. Display a button (not shown), and click the browse button to display the shared data lc tree display as shown in the tree display area 12a of the shared data content display screen 12 in FIG. 12 in a separate screen Then, you can select the node above the target shared data lc. It may come to be.

 [0245] The attribute name input field 84 may be an input field for a drop-down selection method. For example, when the value is input to the upper input field 82, the shared data search processing unit 24 Searches the shared data ID 120a that matches the input value and the lower shared data ID 120a by inputting the value of the upper list 120b, and the value of the searched shared data ID 120a is the shared data ID. The shared attribute record 130 recorded in the ID 130a can be searched, and the value of the name 130d of the shared attribute record 130 can be automatically displayed in the attribute name input field 84.

 [0246] Then, after selecting an option from a plurality of candidate names displayed in the attribute name input field 84, a value corresponding to the option is input from the terminal 2 to the value input field 85. This makes it possible to perform any number of attribute searches.

 [0247] The search range of shared data lc and history data Id is not only shared data lc and history data Id whose values entered in input fields 82 to 85 match, but also the shared data 1 c and history that match. It may include up to shared data lc and history data Id under data Id. Then, if the record of the higher-level shared data lc and historical data Id is used as the search key, the lower-level shared data lc and historical data Id are searched extensively, and the search results are displayed in the shared data list display area. Since it is displayed in 8b, search efficiency is improved.

 [0248] When the shared data lc is searched, the history data Id before the change of the shared data lc is also searched and displayed in the shared data list display area 8b, for example, in chronological order. May be. As a result, the change history of the shared data lc can be grasped at a glance.

 Example 2

[0249] In the following, in the group that also has the contractor and the contractor's power, manage the specifications and Z or the work content of the deliverable when the contractor entrusts the work to the contractor as shared information, in addition to the specifications and An embodiment of a contact information management system for managing contact information exchanged within the group regarding Z or work contents will be described. The configuration of the contact information management system and the record items of shared data lc, history data ld, and contact data le stored in Sano 1 are the same as those shown in FIGS. 1, 2, and 3. . [0250] In this embodiment, the terminal 2 shown in Fig. 1 is installed as the terminal on the consignor side and the trustee side, and the server 1 is installed at the base on the consignor side or the trustee side or at the third installation site. , Use the Internet as network 3. In this case, as a security measure, communication using encryption using a digital certificate is performed.

 [0251] Next, a login ID is determined for each person in charge on the consignor side and the trustee side, and a user record 110 is created for each person in charge.

 [0252] First, the items related to the specifications and work contents of the work to be commissioned are divided into three stages, “major item”, “medium item”, and “minor item”, and these items are arranged hierarchically (in a tree structure). Like), register as shared data lc. That is, the value of the shared data ID 120a of the shared data lc whose name is “middle item” is recorded in the upper list 120b of the shared data lc whose name is “small item”, and the shared data of “middle item” is recorded. In the upper list 120b of lc, the value of the shared data ID 120a of the shared data lc whose name is “major item” is recorded.

 Furthermore, the shared information named “issue management” is registered as shared data lc, and the shared data lc named “unresolved item” and “resolved item” are registered below it. Note that registration is performed by filling in the input fields of the shared data registration update screen 7 shown in FIG.

 [0254] By registering the shared data lc in this way, the consignor and the consignee are registered as the shared data lc in the event that any problem to be solved regarding the specification occurs. Under “Unresolved Items” under “Issue Management”, “issues” that have occurred are additionally registered as shared data lc, and “small item” shared data 1 c related to the specification in which the issue occurred, and the registered “ The shared data 1 e is created by specifying the shared data ID1 20a value of the shared data ID1 20a in the shared data ID1 20b of the contact-related record 180.

 [0255] As described above, when the contact data le is associated with a plurality of shared data lc, and the member designated as the destination 170b of the contact data 1 e receives the contact data 1 e, the content of the issue And the location where the issue occurred (specification where the issue occurred) can be grasped immediately.

[0256] In addition, when a problem that has occurred is resolved, the shared data of the "unresolved item" If the rule of moving from the lower level to the shared data lc of the “resolved item” is applied, the unresolved issue can be viewed by browsing the shared data lc under the shared data lc of the “unresolved item”. Can be displayed as a list on the shared data list display screen 8b of FIG. 8 and the management accuracy is improved.

 [0257] In this way, communication related to consignment work is performed on the contact information management system, and the rules for registering and updating shared information within the group regarding specification changes and problem management as shared data lc are established and used. If the specifications and work contents related to the commissioned work are changed, the shared data lc before the change is duplicated and stored as a history, and the shared data lc before the change is displayed on the contact data list display screen 11 tree in FIG. Since the tree is displayed in the display area 11a so as to be hung below the changed shared data lc, the change history of the shared data lc can be obtained from the tree display area 11a.

 [0258] Further, since the contact data le is associated with the shared data lc and can be associated with multiple shared data 1c, for example, when the desired contact data le is searched, for example, a specification that causes a problem. Or search content with different viewpoints, such as the content of an issue, is possible, thus improving search efficiency.

 [0259] The contact data le related to each shared data lc is listed in the contact data list display area l ib in Fig. 11. The shared data associated with the contact data le in the tree display area 11a is also displayed. If the shared data lc above lc is specified by clicking on the terminal 2 from the terminal 2, the contact data 1 e associated with the shared data 1 c below that shared data 1 is also displayed in the communication data list display area l ib etc. Therefore, when searching for contact data le, it is not necessary to specify individual shared data lc each time, and search efficiency is improved.

 Example 3

[0260] Next, when multiple authors and editors jointly author a single book, within the group consisting of the author and editor, An embodiment of a contact information management system that centrally manages contact information exchanged regarding books between specific persons in the group will be described. The configuration of the contact information management system and the record items of the shared data lc, history data ld, and contact data le stored in the server 1 are the same as those shown in FIG. 1, FIG. 2, and FIG. [0261] In this example, the terminal 2 shown in Fig. 1 is installed at each work place of a plurality of authors and editors, and the server 1 is installed at the base of a powerful author or editor or a third installation. Install in a location and use the Internet as network 3. In this case, as a security measure, communication using a cryptographic key using a digital certificate is performed.

 Next, a login ID is determined for each of a plurality of authors and editors, and a user record 110 for each member is generated.

 [0263] In this example, the chapter plan (for example, "Chapter 1" and "Chapter 2") planned for the book, which is shared information, is registered hierarchically as shared data lc. . However, since the chapter is usually changed greatly as the work progresses, it may be set roughly in the initial stage of system operation. In the contact information management system, even if the content of the shared data lc is changed in the middle, the content before the change remains as the historical data Id, so the history of the change can be grasped at any time, freely and actively Registration of shared data lc is promoted.

 [0264] In this way, by registering free and positive shared data lc, shared information is gradually organized, reviewed, and completed.

 [0265] Also, shared data lc related to "procedures associated with publication" and "work items" and shared data lc related to "issue management" are created, and "unresolved items" and "solutions" are subordinate to "issue management". Create shared data lc for "Payment item". The application of “issue management” is the same as in the first embodiment.

 [0266] In this way, all communications related to the work of the work are made on this system, and the contents of the created work are subordinate to the shared data lc of the "chapter", and "section", " It is assumed that it is subdivided as `` measures '' and registered as shared data lc, and `` headline '' and `` summary '' are used as the name 130d of the shared attribute record 130 as the detailed contents of each shared data lc regarding the copyrighted content. sign up. Then, register “text” as the name 130d of the shared attribute record 130 in the shared data lc of “bar” at the lowest layer, and record the content of the text in the value 130e of the corresponding shared attribute record 130. To do.

[0267] Also, for charts and illustrations, the type 130c of the shared attribute record 130 is registered as an attached file, and the name 130d is registered as "diagram", "illustration", etc., and the storage location of the table or picture image file is stored in the value 130e. Record the file name. [0268] By starting operation with the above rules, all changes to the composition and content related to the work of work are stored as history, and the contact data le exchanged for each content, the exchanged members browse the list This makes it possible to refer to the power of who and how to express an opinion on which part of the work, and how that work changed the opinion, and wasteful discussions and dignity. The tour can be eliminated and work efficiency can be expected to improve.

 [0269] In addition, overlooking the overall structure of the copyrighted work, each author and editor expresses opinions on each part of the copyrighted work, thereby correcting inconsistencies and oversights in the copyrighted work. As a result, quality improvement can be expected, and more creative opinions can be exchanged. As a result, the value of the copyrighted work is increased.

 [0270] In addition, the shared data lc is composed of a shared item record 120 and a shared attribute record 130, and members can arbitrarily define the type 130c and name 130d in the shared attribute record 130. The degree of freedom of the contact information management system is increased and it can be used for various purposes.

 [0271] The contact information management system of the present invention can be used for, for example, daily work report management and quality trouble management in addition to the management of consignment work described in the previous embodiment and the management of crops.

. In this case, the name 130d in the shared attribute record 130 is changed to “work content”, “work location”, “date / time” (when managing daily work reports), “occurrence status”, “response method”, “resolution status” (quality trouble management). Whenever a daily work report is created or a problem occurs, the attribute name input field 76 and the value input field on the shared data registration update screen 7 in FIG. You can enter each in 77. As a result, the shared data lc is registered smoothly and information can be shared.

[0272] If the attribute name input field 76 is a drop-down attribute name selection field, registration of shared data lc will be easier, and members will be encouraged to update data registration.

[0273] Moreover, since the contact data le is related to the shared data lc, the power of what the contact data le is related to. Also, the contact data le is read about the change of the shared data lc. You can also follow. [0274] In particular, when the contact data le is associated with a plurality of shared data lc, the search efficiency of the desired contact data 1e is significantly improved. For example, if a piece of contact information is related to a lot of shared information such as “customer”, “sales agent”, “own product”, “incident card”, “academic theory”, etc. What kind of contact information has been exchanged with customers? "What kind of exchanges have been made with this product?" It is possible to search the contact information exchanged by the user with multiple different cutting powers.

 [0275] It is also possible to create a shared item record 120 in which the value of the name 130d is set to the name 120c. Then, the shared data lc is classified by work contents, work place, date and time. And contact data le can be distributed, which can be useful for statistics.

[0276] Although the embodiment of the contact information management system has been described above, the contact information management system of the present invention is not limited to the contact information management system having all of the configuration requirements described in the above embodiments. Various changes and modifications are possible. Further, it goes without saying that such changes and modifications belong to the scope of the claims of the present invention.

 [0277] The means and database in the present invention are only logically distinguished in function, and may be physically or virtually the same area. It goes without saying that a data file may be used instead of a database, and the description of a database includes a data file.

 [0278] In carrying out the present invention, a storage medium recording software programs for realizing the functions of the present embodiment is supplied to the system, and the computer of the system reads and executes the program stored in the storage medium. This is also realized.

 [0279] In this case, the read program itself realizes the functions of the above-described embodiments, and the storage medium storing the program constitutes the present invention.

[0280] The program of the present invention is supplied mainly by a method of downloading to a computer via a network such as the Internet. In addition, it can be supplied to portable recording medium power computers such as magnetic disks, optical disks, magneto-optical disks, magnetic tapes, and non-volatile memory cards. [0281] Further, by executing the program read by the computer, not only the functions of the above-described embodiments are realized, but also the operating system running on the computer based on the instructions of the program is actually The present invention also includes a case where part or all of the processing is performed and the functions of the above-described embodiments are realized by the processing. Industrial applicability

[0282] The contact information management system of the present invention can be used for information sharing within a company, sales information for sales departments, development information for development departments, and sharing of ordering information in transactions between yarns and fabrics. Requests between organizations and within the same organization, such as development contracts, manufacturing contracts, construction work contracts, software development contracts, etc. It can be used for centralized management of shared information and contact information for information sharing related to work and collaborative work.

 Brief Description of Drawings

[0283] [FIG. 1] A diagram showing an overall configuration of a contact information management system.

 FIG. 2 is a diagram showing an internal configuration of a contact information management program.

 FIG. 3 is a diagram showing a recording structure of records constituting each data of FIG.

 [Figure 4] This is a conceptual diagram showing the tree display of shared data and history data, and the association with contact data.

 FIG. 5 is a diagram showing an example of a login screen.

 FIG. 6 is a diagram showing an example of a main screen.

 FIG. 7 is a diagram showing an example of a shared data registration update screen.

 FIG. 8 is a diagram showing an example of a shared data search screen.

 FIG. 9 is a diagram showing an example of a contact data registration screen.

 FIG. 10 is a diagram showing an example of a contact data search screen.

 FIG. 11 is a diagram showing an example of a contact data list display screen.

 FIG. 12 is a diagram showing an example of a shared data content display screen.

 Explanation of symbols

[0284] 1: Server

la: Contact information management program 21: Login processor

22: Main processing section

 23: Shared data registration processing section

24: Shared data search processing section

25: Shared data display processing section

26: Contact Data Registration Processing Department

27: Contact data search processing section

28: Contact data display processing section

29: Tree display processing part lb: User data lc: Shared data

 Id: History data

le: Contact data

 2: Device

 3: Net

Claims

The scope of the claims  [1] A terminal used by a member of a group that shares information and a server that accepts and processes a request for data registration / search / viewing reference from the terminal are connected to each other via a network. A contact information management system for centrally managing shared information shared among members and contact information exchanged between specific members,  The server includes  Shared data registered with identification information for identifying the divided shared information for each divided shared information obtained by dividing the shared information into arbitrary units;  For each contact information, one or a plurality of pieces of shared data identification information to which the contact information is associated, and contact data registered with the contact information destination and sender identification information are stored. And  From the member ’s terminal,  Search and browse reference of the contact data with the shared data and Z or the member's identification information is added.  A contact information management system characterized by that.  [2] The server includes  For each shared data, the identification information of one or a plurality of shared data corresponding to the superordinate concept of the shared data is added and registered as a superordinate item,  Positive U myself  Using the shared data identification information corresponding to the superordinate concept or subordinate concept, search and browse reference of the shared data organized in a hierarchical tree structure is performed.  When any shared data is specified and the search for the contact data is requested for browsing reference, all shared data associated with all shared data corresponding to the subordinate concept of the specified shared data are requested. Search for contact data  The contact information management system according to claim 1, wherein: [3] When any of the record records of the shared data is changed, the record record before the change is stored as history data in the server, The history data is related to the contact data associated with the shared data before the change. Be the destination  The contact information management system according to claim 1 or claim 2, characterized in that: [4] The shared data is:  1 shared item record in which property information such as the name, update date, registrant, and upper item of the divided shared information is recorded;  The detailed content of the divided shared information is further divided into items, and each of the items is composed of one or more shared attribute records recorded with a name and its content force identification information, and the server and Z or the The shared attribute record is arbitrarily added or changed by the terminal.  The contact information management system according to any one of claims 1 to 3, wherein [5] The server  When the contact data is registered with identification information for identifying the contact information and the contact information that is a response to the contact information of the registered contact data is registered as the contact data, a response source is further added. By registering the identification information of the contact data as reference information,  Positive U myself  A series of contact information in response relation is searched and browsed.  The contact information management system according to any one of claims 1 to 4, wherein