JP2022130362A - Information processing device, data management system, destination information display device, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide management means for important destination information and frequently used destination information for multiple users and individual users to reduce the time and effort required to edit information regarding destination information registered in a destination database.

SOLUTION: An information processing device includes a destination database 112 and display means that displays a list of destination information registered in the destination database 112. The list displayed on the display means includes all information lists that include all pieces of destination information registered in the destination database 112, a shared list of at least a part of the destination information registered in the destination database 112 and shared by multiple users, and an individual list used by authenticated users. When the destination database 112 is edited, the editing result is reflected in the destination information corresponding to the destination information edited in the destination database 112, among the pieces of destination information registered in the shared list and the individual list.

SELECTED DRAWING: Figure 2

COPYRIGHT: (C)2022,JPO&INPIT

Description

The present invention relates to an information processing device, a data management system, a destination information display device, and a program.

An information processing device communicates with other information processing devices connected via a network. Destination information for specifying a communication destination is used in communication between devices. When managing a large amount of destination information, a destination database such as a so-called address book is used. Japanese Patent Laid-Open No. 2002-200000 discloses a method for storing a list of destination information registered by a plurality of users and an address book that includes reference information for referring to the destination information in the list and that corresponds to each of the plurality of users. An arrangement is disclosed that improves the efficiency of storage areas for storing information.

Japanese Unexamined Patent Application Publication No. 2014-116800

A list of destination information shared by multiple users may be limited to users with editing authority. In addition, in the database of the addressee information as the original, there are cases where the addressee data is registered regardless of the frequency and importance of use. It is requested to prepare a list of collected destination data. When a database of destination information is shared by a plurality of users, each user may be requested to create an individual list.

With respect to destination information registered in a destination database, the present invention manages important destination information and frequently used destination information common to a plurality of users and important destination information and frequently used destination information for each user. The purpose is to provide management means to

The present invention according to claim 1,
first destination information display means for displaying destination information registered in a destination database;
second destination information display means for displaying a list in which at least part of the destination information registered in the destination database is registered and which is shared by a plurality of users;
a third destination information display means for displaying a list in which at least part of the destination information registered in the destination database is registered and which is used by an authenticated user;
When the destination database is edited, the second destination information display means reflects the editing result in the destination information corresponding to the destination information edited in the destination database among the destination information registered in the shared list. and said third destination information display means reflects the result of editing on destination information corresponding to destination information edited in said destination database among destination information registered in said individual list. It is a device.
The present invention according to claim 2,
When displaying the individual list, the third destination information display means deletes the destination information deleted from the destination database among the destination information registered in the individual list from the destination database. 2. The information processing apparatus according to claim 1, wherein a display is provided to notify that the operation has been performed.
The present invention according to claim 3,
Further comprising individual list creation means for creating the individual list,
2. The third destination information display means displays the already created list as an initial display when a new individual list is created by the individual list creation means. It is an information processing apparatus described.
The present invention according to claim 4,
3. The third destination information display means displays the already created shared list as an initial display when a new individual list is created by the individual list creation means. 3. The information processing apparatus according to .
The present invention according to claim 5,
further comprising individual list editing means for accepting designation of one or a plurality of destination information among destination information registered in the destination database or destination information registered in the shared list, and adding the designated destination information to the individual list. 2. The information processing apparatus according to claim 1, comprising:
The present invention according to claim 6,
a destination database in which destination information is registered;
First destination list management for managing a first destination list in which reference information referring to destination information registered in the destination database is registered, and destination information can be read by terminal devices of a plurality of users via the reference information. Department and
A second destination for each authenticated user, in which reference information referring to the destination information registered in the destination database is registered, and the destination information can be read by the terminal device of the authenticated user via the reference information a second destination list management unit that manages the list;
A data management system comprising:
The present invention according to claim 7,
the destination database is permitted to be edited by a user having editing authority for the destination database;
the first destination list permits registration and deletion of the reference information by a user who has operation authority for the first destination list;
7. The data management according to claim 6, wherein registration and deletion of said reference information by said authenticated user corresponding to said individual second destination list is permitted for each said second destination list. system.
The present invention according to claim 8,
Registration of reference information in the first destination list is performed by designating destination information to be registered, creating reference information corresponding to the destination information in the destination database, and registering the reference information in the first destination list,
Registration of reference information in the second destination list includes specifying destination information to be registered, duplicating reference information corresponding to the destination information in the first destination list, and registering the reference information in the second destination list; Alternatively, the data management system according to claim 6, wherein reference information corresponding to the destination information in the destination database is created and registered in the second destination list.
The present invention according to claim 9,
display means for displaying destination information based on a shared list shared by multiple users and a separate list used by authenticated users;
switching means for switching between display based on the shared list and display based on the individual list;
changing means for changing the order of destination information in the individual list,
The display means is a destination information display device characterized by displaying destination information based on the shared list as an initial display when a new individual list is created.
The present invention according to claim 10,
the computer,
first destination information display means for displaying destination information registered in a destination database on a display device;
second destination information display means for displaying, on a display device, a shared list in which at least part of the destination information registered in the destination database is registered and shared by a plurality of users;
At least a part of the destination information registered in the destination database is registered and functions as third destination information display means for displaying an individual list used by an authenticated user on a display device;
When the destination database is edited, the second destination information display means reflects the editing result in the destination information corresponding to the destination information edited in the destination database among the destination information registered in the shared list. , said third destination information display means reflects an editing result in destination information corresponding to destination information edited in said destination database among destination information registered in said individual list, be.

According to the invention of claim 1, in comparison with a configuration in which a plurality of users share a destination database and individually edit each list of destination information, the destination information registered in the destination database is common to a plurality of users. It is possible to manage important destination information and frequently used destination information and important destination information and frequently used destination information for each user, and reduce the labor required for editing registration information of each list. can.
According to the invention of claim 2, the user can recognize that the editing result of the destination database is reflected in the individual list, compared with the configuration in which the destination information deleted in the destination database is not notified. .
According to the third aspect of the present invention, when creating an individual list, the labor required for registering the individual list can be reduced compared to a configuration in which all the destination information is acquired one by one from the destination database and registered. can be done.
According to the fourth aspect of the invention, an individual list can be created based on a list highly related to the individual list, compared to the case of using a list other than the shared list as a base.
According to the invention of claim 5, in comparison with the configuration in which only the destination information specified from the shared list can be registered in the individual list, the destination information which is not included in the shared list and which each user desires to use individually. can be registered in individual lists.
According to the invention of claim 6, in comparison with a configuration in which a plurality of users simply share a destination database, the destination information registered in the destination database is important destination information common to a plurality of users and frequently used destination information. It is possible to manage destination information, destination information that is important to individual users, and destination information that is frequently used.
According to the invention of claim 7, it is possible to give each user editing authority suited to the nature of the list, compared to a configuration in which individual authority is not set according to the type of list.
According to the eighth aspect of the invention, when registering reference information for a list, an individual list is created based on a shared list, compared to a configuration in which only creation based on destination information registered in a destination database is performed. In some cases, the processing can be simplified by duplicating the reference information of the shared list and registering it in the individual list.
According to the ninth aspect of the invention, in comparison with a configuration in which a plurality of users share a destination database, regarding destination information registered in the destination database, important destination information common to a plurality of users and destinations with high frequency of use can be obtained. A list of information and a list of destination information important to each user and a list of destination information with high frequency of use can be displayed and used, and the labor required for registering individual lists can be reduced.
According to the tenth aspect of the present invention, in a computer in which the program of the present invention is installed, a plurality of users simply share the destination database and individually edit each list of destination information. Regarding the destination information obtained, a list of important destination information and frequently used destination information common to a plurality of users and a list of important destination information and frequently used destination information for each user are displayed and used. At the same time, it is possible to reduce the labor required for editing the registration information of each list.

It is a figure showing the whole data management system composition by this embodiment. It is a figure which shows the functional structure of a management server. It is a figure which shows the structural example of authority authentication DB. It is a figure which shows the structural example of destination DB. It is a figure which shows the structural example of user DB. 6 is a diagram illustrating a configuration example of a destination type management table; FIG. It is a figure which shows the functional structure of a terminal device. It is a figure which shows the hardware structural example of the computer used as a management server and a terminal device. FIG. 10 is a flowchart for explaining operations of a management server and a terminal device when displaying a list of destination information; FIG. 10(A) is a diagram showing a display example of an individual list, FIG. 10(B) is a diagram showing a display example of a shared list, and FIG. FIG. 10 is a diagram showing a display example of a full information list; It is a flowchart which shows the edit operation|movement of an individual list|wrist, and is a figure which shows operation|movement until a terminal device acquires destination information from a management server. FIG. 10 is a flowchart showing editing operation of an individual list, and is a diagram showing operation after displaying the list of destination information acquired by the terminal device. It is a figure which shows the functional structure of the information processing apparatus with which this embodiment was applied.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. This embodiment uses a list for referring to destination information registered in the destination database as means for using the destination database. Lists include a shared list shared by a plurality of users and individual lists prepared by individual users. When displaying the destination information on the user interface (UI), any one of an individual list, a shared list, and a full list displaying all the destination information registered in the destination database is selected and displayed. be. Examples of a system to which this embodiment is applied include a server-client system comprising a management server that manages a destination database and a client device that provides a UI, and an information processing device that includes both a destination database and a UI by itself. etc. can be configured. The embodiment will be described below by taking as an example a case where the present invention is applied to a server/client system.

<System configuration>
FIG. 1 is a diagram showing the overall configuration of a data management system according to this embodiment. The data management system 100 includes a management server 10 and terminal devices 20 . The management server 10 is a server that manages destination data. The terminal device 20 is a device for using destination data managed by the management server 10 .

Although only one terminal device 20 is shown in FIG. 1, a plurality of terminal devices 20 are actually connected to the management server 10 and use destination data. Operations that can be executed from the terminal device 20 to the management server 10 are controlled according to the authority given to the user using the terminal device 20 . For example, only viewing of destination data managed by the management server 10 is permitted from the terminal device 20 of a user who has only viewing authority. On the other hand, from the terminal device 20 of the user who has the editing authority, it is possible to edit the destination data managed by the management server 10 and register new destination data.

The management server 10 and terminal device 20 are connected via a network 101 . The network 101 is not particularly limited as long as it is a communication network used for data communication between the management server 10 and the terminal device 20, and may be, for example, a LAN (Local Area Network), a WAN (Wide Area Network), the Internet, or the like. The communication line used for data communication may be wired or wireless, and both may be used.

<Functional configuration of management server>
FIG. 2 is a diagram showing the functional configuration of the management server 10. As shown in FIG. The management server 10 includes a database management section 11 , a shared list editing section 12 , an individual list editing section 13 , and a transmission/reception section 14 . The management server 10 also includes an authority authentication database (DB) 111 , a destination database (DB) 112 , a user database (DB) 113 and a destination type management table 114 .

The database management unit 11 is management means for managing each database (authorization authentication DB 111, destination DB 112, user DB 113, and destination type management table 114). Further, the database management unit 11 edits registration information registered in each database. Specifically, the database management unit 11 performs processing such as addition and deletion of registration items and modification of the contents of registration items for each database. Editing of registration information in each database is performed by receiving an edit command from a user who has editing authority for each database.

The database management unit 11 also manages registration information of the shared list and the individual list used to refer to all the destination information registered in the destination database. Here, the shared list is an example of a first destination list, and the individual list is an example of a second destination list. That is, the database management section 11 is an example of a first destination list management section and a second destination list management section. When the display of the shared list is requested, the database management unit 11 refers to the destination DB 112 to generate the shared list. Further, when the display of the individual list is requested, the database management unit 11 refers to the destination DB 112 and the user DB 113 to generate the individual list.

The shared list editing unit 12 is processing means for editing the shared list. The shared list editing unit 12 registers and edits shared lists. Specifically, the shared list editing unit 12 performs processing such as new registration of a shared list, addition and deletion of registered items, and change of contents of registered items. Although details will be described later, in this embodiment, the registration information of the shared list is held in the destination DB 112 . Editing of the shared list is performed by receiving an edit command from a user who has editing authority for the shared list.

The individual list editing unit 13 is processing means for editing an individual list. The individual list editing unit 13 registers and edits individual lists. Specifically, the individual list editing unit 13 executes processing such as new registration of an individual list, addition and deletion of registration items, and change of contents of registration items. Although details will be described later, in this embodiment, the registration information of the individual list is held in the destination DB 112 and the user DB 113 . Editing of the individual list is performed by receiving an edit command from a user who has been personally authenticated. In addition, regarding editing of individual lists, editing authority may be set for users so that only users having editing authority can register and edit their own individual lists.

The transmission/reception unit 14 is communication means for exchanging data with the terminal device 20 . Specifically, the transmission/reception unit 14 receives, from the terminal device 20, a request for a destination information list (shared list, individual list, etc.), an instruction to edit each database or list, user authentication information, and the like. Then, the transmitting/receiving unit 14 transmits to the terminal device 20 the list generated in response to the request for the list, the information about each database and the list, and the like.

The authority authentication DB 111 is a database that manages user authority. FIG. 3 is a diagram showing a configuration example of the authority authentication DB 111. As shown in FIG. In the authority authentication DB 111 shown in FIG. 3, authority settings related to destination information are registered in association with user IDs (UserIDs in the drawing) and user names. In the illustrated example, three types of authority settings are registered: "registration", "reference", and "individual list creation". The item “registration” is the authority to register destination information in the destination DB 112 . The item “reference” is the authority to refer to destination information in the destination DB 112 . The item "create individual list" is the authority to create an individual list. For example, a user "Yamada" with a user ID "0001" is authorized to register and refer to destination information in the destination DB 112 and create an individual list. A user “Tanaka” with a user ID “0002” is authorized to refer to destination information in the destination DB 112 and create an individual list. User "Suzuki" with user ID "0003" is authorized to register and refer to destination information in destination DB 112, but is not authorized to create an individual list.

The destination DB 112 is a database that manages destination information. FIG. 4 is a diagram showing a configuration example of the destination DB 112. As shown in FIG. In the destination DB 112 shown in FIG. 4, for each destination ID (“ContactID” in the figure), each information of destination name, destination type, destination ID (“DestinationID” in the figure), destination, and shared list attribute corresponds. attached and registered. The item "destination type" is information indicating the type of communication specified based on the application software that uses the destination information. Therefore, a plurality of destination types may be registered for one destination ID. For example, in the example shown in FIG. 4, for destination ID "0001" (destination name "User01"), e-mail ("Email" in the figure), facsimile transmission ("Fax" in the figure), FTP (File Transfer Protocol) Three types of file transfer ("FTP" in the figure) are registered. Each information of destination ID, destination, and shared list attribute is registered for each destination type.

The item "destination ID" is an ID uniquely assigned to each destination. The item “destination” is information specifying a destination specified for each destination type. Destinations can take different forms for different destination types. Referring to FIG. 4, destination IDs "0001" to "0003" correspond to destination types of destination ID "0001" (destination name "User01"), and the destination type of destination ID "0001" is "Email" and the destination is the e-mail address "User01@xxx.xxx". Similarly, the destination type of the destination ID "0002" is "Fax", and the destination is the fax number (telephone number) "111-111-111". The destination type of the destination ID "0003" is "FTP", and the destination is the FTP server address "ftp://xxx.xxx.xxx.xxx". Destination IDs "0004" and "0005" correspond to each destination type of destination ID "0002" (destination name "User02"), and the destination type of destination ID "0004" is "Email", The destination is the e-mail address "User02@xxx.xxx". The destination type of the destination ID "0005" is "SMB", and the destination is the SMB server address "\\User01\Share". Here, the destination type "SMB" indicates communication by the SMB (Server Message Block) protocol. Also, the destination ID "0006" corresponds to the destination type "Fax" of the destination ID "0003" (destination name "User03"), and the destination is the fax number (telephone number) "333-333-333". is.

The item “shared list attribute” is information indicating whether or not the destination information is registered in the shared list. In the example shown in FIG. 4, each piece of destination information corresponding to destination IDs "0001", "0003", and "0006" has a shared list attribute (marked with a circle "o" in the figure). Destination information having these shared list attributes is destination information registered in the shared list.

The user DB 113 is a database that manages individual lists of users. FIG. 5 is a diagram showing a configuration example of the user DB 113. As shown in FIG. In the user DB 113 shown in FIG. 5, user IDs, application software (“application” in the drawing), and destination IDs are associated and registered. Here, a user registered in the user DB 113 (a user specified by a user ID) is a user who has registered an individual list.

The item "application software" is information indicating application software that can be used by the user. Application software registered in the user DB 113 is application software for which an individual list is set. Each user may use multiple software as application software that can utilize the destination information. Therefore, a plurality of application software may be registered for one user ID. For example, in the example shown in FIG. 5, application software "Email" and application software "ScanTo" are registered for user ID "0001". This allows a separate list to be set for each application software. In the above example, separate lists are set for the application software "Email" and the application software "ScanTo".

The item “destination” in the user DB 113 is the destination registered in the individual list. As described above, the "destination" of the individual list is set for each application software. In the example shown in FIG. 5, destination ID "0001" and destination ID "0004" are registered for application software "Email" with user ID "0001". This means that the destination IDs "0001" and "0004" of the destination DB 112 shown in FIG. 4 are registered as the destinations of the individual list for the application software "Email" of the user ID "0001". .

The destination type management table 114 is a table for managing destination types that application software can take. FIG. 6 is a diagram showing a configuration example of the destination type management table 114. As shown in FIG. In the destination type management table 114 shown in FIG. 6, application software (“application”) and destination types that can be obtained in communication by the application software are associated and registered. In the example shown in FIG. 6, application software "Fax" is software for facsimile communication. Application software "Email" is software for sending and receiving electronic mails. The application software "ScanTo" is software for transmitting an image captured by scanning with a scanner. The application software "ScanToServer" is software for transmitting an image captured by scanning to a server.

Referring to FIG. 6, the application software "Fax" can perform facsimile transmission (Fax) and SIP fax transmission ("SipFax" in the figure). SIP facsimile is facsimile communication means for establishing a session with a counterpart using SIP (Session Initiation Protocol) on an IP network and performing peer-to-peer communication. The application software "Email" can send by electronic mail (Email). The application software "ScanTo" can perform transmission by e-mail (Email), file transfer by FTP (FTP), and communication by SMB (SMB). The application software "ScanToServer" can perform file transfer by FTP (FTP) and communication by SMB (SMB).

<Functional configuration of terminal device>
FIG. 7 is a diagram showing the functional configuration of the terminal device 20. As shown in FIG. The terminal device 20 includes a display section 21 , an operation reception section 22 , a control section 23 and a transmission/reception section 24 . As the terminal device 20, for example, a personal computer, a tablet-type information terminal, or other portable information terminal may be used.

The display unit 21 is display means for displaying a list of destination information. A list of destinations includes a private list and a shared list. Also, a list of all destination information registered in the destination DB 112 (hereinafter referred to as “all information list”) is included. That is, the display unit 21 is an example of first destination information display means, an example of second destination information display means, and an example of third destination information display means.

The operation accepting unit 22 is processing means for accepting various operations related to the destination information list displayed on the display unit 21 . Specifically, the operation accepting unit 22 accepts an operation for selecting the destination information list displayed on the display unit 21 . That is, the operation receiving unit 22 is an example of selection operation receiving means. In addition, the operation accepting unit 22 accepts an operation for changing the arrangement order of the destination information in the individual list displayed on the display unit 21 . Further, the operation receiving unit 22 receives an operation of selecting destination information and creating an individual list or a shared list according to the authority given to the user of the terminal device 20 . Further, the operation receiving unit 22 performs an editing operation for adding or deleting destination information to/from the individual list or the shared list displayed on the display unit 21 according to the authority given to the user of the terminal device 20. accept. Further, the operation accepting unit 22 accepts an editing operation for editing destination information registered in the destination DB 112 according to authority given to the user of the terminal device 20 . Various operations related to the list of destination information are performed using, for example, a pointing device such as a mouse or an input device such as a keyboard.

The control unit 23 is control means for controlling display of the destination information list on the display unit 21 and data communication with the management server 10 . For example, the control unit 23 reflects the operation received by the operation receiving unit 22 on the display of the display unit 21, and makes a request to the management server 10 based on the received operation. Therefore, the display unit 21, the operation receiving unit 22, and the control unit 23 are an example of individual list changing means, an example of individual list creating means, and an example of individual list editing means.

The transmission/reception unit 24 is communication means for exchanging data between the management server 10 and the terminal device 20 . Specifically, under the control of the control unit 23, the transmission/reception unit 24 transmits to the management server 10 a request for a destination information list, an instruction to edit each database or list, user authentication information, and the like. The transmitting/receiving unit 24 receives a list generated in response to a list request from the management server 10, information about each database and the list, and the like.

<Computer hardware configuration>
FIG. 8 is a diagram showing a hardware configuration example of a computer used as the management server 10 and the terminal device 20. As shown in FIG. A computer 200 shown in FIG. 8 includes a CPU (Central Processing Unit) 201 as computing means, a main memory device (main memory) 202 and an external storage device 203 as storage means. The CPU 201 loads a program stored in the external storage device 203 into the main storage device 202 and executes it. A RAM (Random Access Memory), for example, is used as the main memory device 202 . As the external storage device 203, for example, a magnetic disk device, an SSD (Solid State Drive), or the like is used. The computer 200 also includes a display mechanism 204 for outputting a display on a display device (display) 207, and an input device 205 through which an operator of the computer 200 performs an input operation. A keyboard, a mouse, or the like is used as the input device 205, for example. Computer 200 also includes a network interface 206 for connecting to a network. The configuration of the computer 200 shown in FIG. 8 is merely an example, and the computer used in this embodiment is not limited to the configuration example of FIG. For example, a configuration including a non-volatile memory such as a flash memory or a ROM (Read Only Memory) as a storage device may be used.

When the management server 10 shown in FIG. 2 is implemented by the computer shown in FIG. 8, each function of the database management unit 11, the shared list editing unit 12, and the individual list editing unit 13 is executed by the CPU 201 executing a program, for example. It is realized by The transmitting/receiving unit 14 is realized by a network interface 206, for example. The authority authentication DB 111, the destination DB 112, the user DB 113, and the destination type management table 114 are realized by the main storage device 202 and the external storage device 203, for example.

When the terminal device 20 shown in FIG. 7 is realized by the computer shown in FIG. 8, the display unit 21 is realized by the display device 207, for example. The operation receiving unit 22 is realized by the input device 205 and the CPU 201, for example. The main functions of the control unit 23 are realized, for example, by the CPU 201 executing a program. Moreover, the display control function by the control unit 23 is realized by the display mechanism 204, for example. The transmitting/receiving unit 24 is implemented by, for example, a network interface 206 .

<Display operation of destination information>
FIG. 9 is a flow chart for explaining the operation of the management server 10 and the terminal device 20 when displaying the destination information list. As an initial operation, in the terminal device 20 , when the application software requests the display of the destination information, the terminal device 20 transmits a request for the destination information list to the management server 10 . Upon receiving a request from the terminal device 20, the management server 10 determines whether or not to give priority to lists (individual lists and shared lists) that refer to the destination DB 112 (S901). Here, the determination as to whether or not to give priority to the list that refers to the destination DB 112 is based on, for example, an instruction received from the terminal device 20 together with the list request, the type of application software that requested the list in the terminal device 20, the terminal It may be performed based on the attribute of the user of the device 20, the operation mode of the management server 10, or the like. If the list that refers to the destination DB 112 is not prioritized (No in S901), the database management unit 11 of the management server 10 acquires all destination information registered in the destination DB 112, generates a list of all information, and It is returned to the device 20 (S908). The terminal device 20 displays the all information list received from the management server 10 on the display unit 21 (S909).

If priority is given to the list that refers to the destination DB 112 (Yes in S901), then the management server 10 determines whether or not the user of the terminal device 20 has been authenticated (S902). If the user of the terminal device 20 has not been authenticated (No in S902), the database management unit 11 of the management server 10 determines whether there is a shared list for the application software requesting the destination information (S906). Here, whether or not there is a shared list is determined by referring to the "shared list attribute" of the destination DB 112 based on the type of application software that requests destination information. For example, assume that the application software requesting the destination information is "ScanTo". Referring to the destination type management table 114 shown in FIG. 6, there are three destination types selectable by the application software "ScanTo": "Email", "FTP", and "SMB". Referring to the destination DB 112 of FIG. 4, the destination type corresponding to the destination ID "0001" having the shared list attribute is "Email", the destination type corresponding to the destination ID "0003" is "FTP", and the destination ID " 0006" is "Fax". Therefore, if the application software requesting the destination information is "ScanTo", the destination IDs "0001" and "0003" will appear in the shared list for this application software. Since the application software "ScanTo" cannot set the destination type "Fax" as the destination, the destination ID "0006" is not included in the shared list. Note that the shared list for each application software is created at a predetermined timing by the operation of a user who has the authority to edit the shared list.

If there is a shared list for the application software requesting the destination information (Yes in S906), the database management unit 11 of the management server 10 refers to the destination DB 112 and is registered in the shared list (that is, the shared list attribute is assigned), generates a list of the acquired destination information, and returns it to the terminal device 20 (S907). The terminal device 20 displays the list received from the management server 10 on the display unit 21 (S909). On the other hand, if there is no shared list for the application software that requests destination information (No in S906), the database management unit 11 of the management server 10 generates a list of all information and returns it to the terminal device 20 (S908). The terminal device 20 displays the all information list received from the management server 10 on the display unit 21 (S909).

If the user of the terminal device 20 has been authenticated (Yes in S902), the database management unit 11 of the management server 10 determines whether an individual list for application software requesting destination information is registered for the authenticated user. (S903). Here, the user DB 113 is referred to to determine whether or not the individual list is registered. For example, consider a case where the authenticated user has the user name "Yamada" (see the authority authentication DB 111 in FIG. 3) and the application software requesting the destination information is the application software for sending and receiving e-mails. Referring to the user DB 113 of FIG. 5, the application software "Email" is registered in relation to the user ID "0001" of the user "Yamada", and the destination ID "0001", "0004" is registered. Therefore, if the authenticated user is "Yamada" and the application software requesting the destination information is e-mail software whose destination ID is e-mail software, an individual list is registered, and this individual list includes: Destination IDs "0001" and "0004" will appear. Note that the individual list may be created by the authenticated user himself/herself if necessary. However, as described with reference to FIG. 3, when the authority to create an individual list is set in the authority authentication DB 111, only users who have the authority to create an individual list can create their own individual list. .

If an individual list for the application software requesting the destination information is registered for the authenticated user (Yes in S903), then the database management unit 11 refers to the user DB 113 and refers to the destination information in the destination DB 112. A destination ID is acquired as information (S904). Then, the database management unit 11 refers to the destination DB 112 using the acquired destination ID as a key, acquires the destination information corresponding to the destination ID used as the key, generates a list of the acquired destination information, and 20 (S905). The terminal device 20 displays the list received from the management server 10 on the display unit 21 (S909).

On the other hand, if the authenticated user does not have an individual list registered for the application software requesting the destination information (No in S903), the database management unit 11 determines whether or not there is a shared list for this application software. (S906). Then, if there is a shared list, the database management unit 11 acquires destination information registered in the shared list, generates a list of the acquired destination information, and returns it to the terminal device 20 (S907). On the other hand, if there is no shared list, the database management unit 11 generates a list of all information in the destination DB 112 and returns it to the terminal device 20 (S908). The terminal device 20 displays the list received from the management server 10 on the display unit 21 (S909).

As described above, a destination information list (individual list, shared list, or all information list) is obtained from the management server 10 in response to a request from the terminal device 20 and displayed on the display section 21 of the terminal device 20 . The list to be displayed is displayed from the list with the highest display policy among the created lists. According to the above operation example, if the individual list corresponding to the request exists, the individual list is obtained, and if the individual list does not exist and the shared list exists, the shared list is obtained, and neither the individual list nor the shared list exists. A full information list is obtained when Then, the obtained list is displayed on the terminal device 20 . This is based on the display policy that, if an individual list exists, the individual list is a list that meets the individual user's intention. If some display policy with a higher priority for the shared list is applied, the shared list may be preferentially acquired and displayed over the individual list. In the above example, each list is acquired and displayed according to the priority based on the display policy. The corresponding list may be generated by the management server 10 and returned to the terminal device 20 . In response to a request from the terminal device 20, the management server 10 may provide all existing lists, and the terminal device 20 may preferentially display individual lists, shared lists, and all information lists in this order. .

<Example of address information display>
10A and 10B are diagrams showing display examples of destination information on the terminal device 20. FIG. 10A is a diagram showing a display example of an individual list, and FIG. 10B is a diagram showing a display example of a shared list. 10(C) is a diagram showing a display example of the all information list. As shown in FIGS. 10A to 10C, the destination information display screen 210 displayed on the display unit 21 includes an operation field 211 and a destination information field 212. FIG. Here, it is assumed that destination information is displayed in response to a request from e-mail software.

The operation column 211 is a display column for indicating the type of the displayed list and for accepting an operation for selecting the list to be displayed. In the illustrated example, the operation field 211 includes a block for displaying an individual list (displayed as "User01's Favorites" in the figure), a block for displaying a shared list (displayed as "Shared Favorites" in the figure), and a block for displaying a shared list. A block (displayed as "address book" in the drawing) showing the display of the information list is displayed. When an operation to select one block is performed in the operation field 211 , a list corresponding to the selected block is displayed in the destination information field 212 . Also, a block (selected block) corresponding to the displayed list is displayed in a display manner different from that of other blocks. Specifically, in the operation column 211 of FIG. 10A, the blocks indicating the display of the individual list are shaded, and in the operation column 211 of FIG. 10B, the blocks indicating the display of the shared list are shaded. In the operation column 211 of FIG. 10C, the block showing the display of the all information list is shown by hatching. In the illustrated example, a search button (displayed as "Search" in the figure) for shifting to a search screen for searching for specific destination information, and an end button (in the figure, a cross mark "X") for closing the destination information display screen 210 ) is displayed in the operation column 211 .

The destination information column 212 is a display column for displaying any of the individual list, shared list, and all information list. In the illustrated example, the list is displayed in response to a request from e-mail software, so in the destination information column 212, as destination information, the destination name and e-mail address of the destination, or a group of mailing lists. Names ("EmailGroup_SalesDepartment" and "EmailGroup_R&D Department") are displayed. Comparing FIGS. 10A to 10C, the destination information displayed in the individual list and the destination information displayed in the shared list are each part of the destination information displayed in the all information list. It's becoming This is because both the individual list and the shared list are created from the destination information registered in the destination DB 112 . Also, in the illustrated example, the destination information displayed in the individual list is part of the destination information displayed in the shared list. However, destination information that is not registered in the shared list may be acquired from the destination DB 112 and registered in the individual list. As an initial display when the destination information display screen 210 is displayed, if there is a corresponding individual list in the destination information column 212 as described with reference to FIG. displayed. Then, if the corresponding individual list does not exist, the shared list is displayed, and if the shared list does not exist, the all information list is displayed. After the display screen 210 is displayed, when a list other than the displayed list is selected by operating the operation column 211, the display of the destination information column 212 is switched to the selected list according to the operation.

<Editing operation of individual list>
11 and 12 are flow charts showing the editing operation of the individual list. Editing of the individual list is performed by specifying the application software that uses the individual list to be edited by operating from the terminal device 20 . When a request for editing an individual list is transmitted from the terminal device 20 to the management server 10, the management server 10 determines whether or not the user of the terminal device 20 has been authenticated (S1101). An unauthenticated user (No in S1101) is not permitted to edit the individual list, so the process ends.

If the user of the terminal device 20 has been authenticated (Yes in S1101), the database management unit 11 of the management server 10 checks whether an individual list for the specified application software is registered for the authenticated user. It judges (S1102). Determining whether or not there is registration in the individual list is the same as the operation described with reference to FIG. 9 (see S903). If the individual list is registered (Yes in S1102), then the database management unit 11 refers to the user DB 113 and acquires the destination ID as reference information for the destination information in the destination DB 112 (S1103). Then, the database management unit 11 refers to the destination DB 112 using the acquired destination ID as a key, and acquires the destination information corresponding to the destination ID used as the key (S1104).

Here, it is assumed that there is destination information that is registered in the individual list but cannot be obtained from the destination DB 112 (Yes in S1105). That is, this is the case where the destination information corresponding to the destination ID acquired from the user DB 112 does not exist in the destination DB 112 . In this case, the database management unit 11 notifies the terminal device 20 that there is a destination deleted from the destination DB 112 (S1106).

If there is no destination information that cannot be acquired from the destination DB 112 (No in S1105), the destination information acquired in S1104 is sent from the management server 10 to the terminal device 20. FIG. Then, in the terminal device 20, the list of destination information acquired from the management server 10 is displayed on the screen of the individual list for editing operation (S1108). If there is destination information that cannot be acquired from the destination DB 112 (Yes in S1105), the destination information acquired in S1104 is sent from the management server 10 to the terminal device 20. FIG. Then, in the terminal device 20, together with the information notified in S1106, a list of destination information acquired from the management server 10 is displayed on the individual list screen for editing operation (S1108). In addition, in S1106, along with information indicating that there is a destination deleted from the destination DB 112, information specifying the deleted destination may be notified and displayed on the terminal device 20. FIG. The individual list screen for editing operation is a screen that accepts an editing operation for the individual list. For example, the display screen of the individual list shown in FIG. 10A is configured as a screen to which operators (buttons, objects, etc.) for accepting editing operations and confirming operations for confirming edited contents are added.

On the other hand, when the individual list for the specified application software is not registered for the authenticated user (No in S1102), the database management unit 11 acquires the destination information of the shared list regarding this application software from the destination DB 112. (S1107). The acquired destination information of the shared list is sent from the management server 10 to the terminal device 20 . Then, in the terminal device 20, a list of destination information of the shared list acquired from the management server 10 is displayed on the screen of the individual list for editing operation (S1108). That is, if an individual list for the identified application software is not registered, the destination information of the shared list is initially acquired and displayed as an individual list.

After the individual list is displayed on the display unit 21, the control unit 23 of the terminal device 20 waits for the operation reception unit 22 to receive the user's operation. User operations include an editing operation (S1109) and a confirmation operation (S1115). Editing operations include an operation of adding destination information, an operation of changing the arrangement order of destination information, and an operation of deleting destination information with respect to the list of destination information on the individual list screen for editing operation displayed in S1108. included. The confirmation operation is an operation for confirming the contents of the individual list in the destination information list displayed on the screen of the individual list for editing operation. When the confirmation operation is performed, the editing operation of the individual list ends.

If the editing operation is accepted (Yes at S1109), and the content of the editing operation requests addition of a destination to the individual list (Yes at S1110), the terminal device 20 sends a request for a shared list to the management server 10. done. The management server 10 acquires the destination information of the shared list from the destination DB 112 in response to the request and returns it to the terminal device 20 . The terminal device 20 displays a list of destination information of the shared list acquired from the management server 10 separately from the screen of the individual list for editing operation (S1111). When the user performs a selection operation of one or more items of destination information on the displayed shared list, the operation receiving unit 22 receives the selection operation, and the control unit 23 selects one or more items selected by the operation. is detected (S1112). Then, the control unit 23 adds the detected destination information to the individual list, and updates the individual list screen for editing operation (S1114). Note that addition of destination information to the individual list may be performed from the all information list (the destination information itself registered in the destination DB 112) instead of the destination information of the shared list.

If the content of the editing operation does not request addition of a destination to the individual list (No in S1110), the control unit 23 executes editing processing according to the accepted operation (S1113). Specifically, the arrangement order of the destination information in the individual list is changed, or the destination information in the individual list is deleted. When the destination information of the individual list is deleted in the terminal device 20, the terminal device 20 notifies the management server 10 of it. Upon receiving this notification, the database management unit 11 of the management server 10 deletes the reference information (destination ID) of the corresponding destination information from the user DB 113 . That is, the destination information of the individual list is obtained by referring to the destination DB 112, and the reference information to the destination DB 112 is registered in the individual list. Even if the destination information is deleted, the reference information in the individual list is deleted, and the destination information itself registered in the destination DB 112 is not deleted. After the above editing process, the control unit 23 adds the detected destination information to the individual list and updates the individual list screen for editing operation (S1114).

When the confirmation operation is performed as the operation by the user (No in S1109, Yes in S1115), the control unit 23 ends the editing operation of the individual list. The confirming operation is performed, for example, by operating an operator for confirming operation added to the screen of the individual list for editing. When the confirmation operation is performed, the information of the editing result is transmitted from the terminal device 20 to the management server 10 and reflected in the user DB 113 by the database management section 11 .

In the above operation example, in the editing operation when the individual list is not registered (when registering a new individual list), the destination information of the shared list is initially displayed on the individual list screen for editing. (See FIG. 11, S1107). However, the destination information initially displayed when the individual list is not registered may be a list of destination information that has already been created, and is not limited to the destination information of the shared list. For example, the destination information in the all information list of the destination DB 112 may be displayed as an initial display. Also, if there is an individual list created in association with other application software, the destination information of the other individual list may be displayed as an initial display. In this way, when registering a new individual list, by initially displaying other existing lists and editing the displayed list to create a new individual list, all destination information can be obtained. is obtained one by one from the destination DB 112 and registered, the labor required for registering the individual list is reduced.

When the destination information (reference information) is registered based on the shared list on the screen of the individual list for editing in the terminal device 20, for example, the user designates the destination information (reference information) to be registered in the shared list. , the control unit 23 duplicates the designated destination information (reference information) and registers it in the individual list. Further, when the destination information (reference information) is registered based on the all information list of the destination DB 112, for example, the user designates the destination information to be registered in the all information list, and the control unit 23 registers the designated destination information. This is done by creating the reference information of and registering it in the individual list.

The editing of the individual list has been described above. In the above operational example, it was assumed that an authenticated user could create and edit an individual list. On the other hand, as described with reference to FIG. 3, the authority to create an individual list may be managed by the authority authentication DB 111. FIG. In this case, only users granted creation authority can create and edit their own individual lists. In the example shown in FIG. 3, user ID "0001", user name "Yamada" and user ID "0002", user name "Tanaka" can create and edit their own individual lists. The name "Suzuki" cannot create or edit his own individual list.

Also, although the editing of the individual list has been described here, the editing of the shared list may also be performed by the same processing procedure. However, editing of the shared list can only be performed by users who have been given permission to edit the shared list. The shared list destination information is reference information for obtaining destination information registered in the destination DB 112, and is recorded as a shared list attribute of the destination DB 112 as described with reference to FIG. Therefore, the user who has the editing authority for the destination DB 112 may also have the editing authority for the shared list, or the editing authority for the shared list may be set separately from the editing authority for the destination DB 112 .

When registering a new shared list, a new shared list can be created by displaying another list as an initial display and editing the displayed list, as in the case of newly registering an individual list. In this case, a list of all information in the destination DB 112 is used as the list displayed as the initial display. Also, if there is a shared list created in association with other application software, the destination information of the other shared list may be displayed as an initial display. Also, when the destination information is deleted in editing the shared list, the shared list attribute in the corresponding destination information in the destination DB 112 is deleted.

When the destination information (reference information) is registered in the shared list based on the all information list of the destination DB 112, for example, the user designates the destination information to be registered in the all information list, and the control unit 23 registers the designated destination. This is done by creating reference information for information and registering it in an individual list.

Also, the destination DB 112 itself can be edited by a user who has been granted the authority to edit the destination DB 112 . In the example of the authority authentication DB 111 shown in FIG. 3, user ID "0001", user name "Yamada" and user ID "0003", user name "Suzuki" have the authority to edit the destination DB 112 (register destination information). As described above, the destination information of the individual list and the shared list is obtained by referring to the destination information registered in the destination DB 112 using the reference information registered in each list when these lists are displayed. is obtained. Therefore, when the destination information in the destination DB 112 is edited, the edited result is reflected in the individual list and the shared list.

<Modification>
In the configuration example shown in FIG. 1, the present embodiment has been described as a server/client system composed of the management server 10 and the terminal device 20, but the present embodiment is not limited to the configuration shown in FIG. Various configurations are possible. Next, a configuration in which the present embodiment is applied to an information processing apparatus that includes both a destination database and a UI alone will be described.

FIG. 13 is a diagram showing the functional configuration of an information processing apparatus to which this embodiment is applied. The information processing device 30 includes a database management unit 11 , a shared list editing unit 12 and an individual list editing unit 13 . The information processing device 30 also includes a display control unit 31 , a display unit 32 , and an operation reception unit 33 . The information processing apparatus 30 also includes an authority authentication database (DB) 111 , a destination database (DB) 112 , a user database (DB) 113 and a destination type management table 114 . In the information processing apparatus 30 shown in FIG. 13, the database management unit 11, the shared list editing unit 12, the individual list editing unit 13, the transmission/reception unit 14, the authority authentication DB 111, the destination DB 112, the user DB 113, and the destination type management table 114 are configured as shown in FIG. Since these functional blocks are the same as the functional blocks of the management server 10 shown in FIG.

The display control unit 31 is control means for generating a list (individual list, shared list, all information list) based on the destination information registered in the destination DB 112 and causing the display unit 32 to display the list. Further, the display control unit 31 controls the display of the display unit 32 or requests the database management unit 11 to operate each of the databases 111 to 113 according to the operation received by the operation reception unit 33 .

The display unit 32 is display means for displaying lists of destination information (individual list, shared list, all information list). The operation receiving unit 33 is processing means for receiving various operations related to the destination information list displayed on the display unit 32 . The details of the display of the list by the display unit 32 and the display control unit 31 are the same as the display by the display unit 21 and the control unit 23 of the terminal device 20 shown in FIG. Further, the details of the operation related to the list accepted by the operation accepting unit 33 are the same as the operations accepted by the operation accepting unit 22 of the terminal device 20 shown in FIG. The display control unit 31, the display unit 32, and the operation reception unit 33 provide a UI for the user of the information processing device 30 to browse the list and perform operations on the list.

Although the information processing device 30 shown in FIG. 13 is a single device, the UI function of the display control unit 31, the display unit 32, and the operation reception unit 33 is configured as an external device, and is connected to the main body by wireless connection or cable connection. can be used as For example, a portable information terminal such as a tablet terminal device or a smart phone may be used as the external device that performs the UI function. As a wireless connection for connecting the external device and the main body, connection means such as short-range wireless communication such as Bluetooth (registered trademark) and NFC, or Wi-Fi may be used. As a cable connection for connecting the external device and the main body, connection means by USB (Universal Serial Bus) or IEEE1394 may be used. In addition, the present invention includes various modifications and alternative configurations that do not depart from the scope of the technical idea of the present invention.

DESCRIPTION OF SYMBOLS 10... Management server, 11... Database management part, 12... Shared list editing part, 13... Individual list editing part, 14... Transmission/reception part, 20... Terminal device, 21... Display part, 22... Operation reception part, 23... Control part , 24... Transmission/reception unit, 31... Display control unit, 32... Display unit, 33... Operation reception unit, 100... Data management system, 101... Network, 111... Authority authentication database (DB), 112... Destination database (DB), 113... User database (DB), 114... Destination type management table

Claims (10)

first destination information display means for displaying destination information registered in a destination database;
second destination information display means for displaying a list in which at least part of the destination information registered in the destination database is registered and which is shared by a plurality of users;
a third destination information display means for displaying a list in which at least part of the destination information registered in the destination database is registered and which is used by an authenticated user;
When the destination database is edited, the second destination information display means reflects the editing result in the destination information corresponding to the destination information edited in the destination database among the destination information registered in the shared list. and said third destination information display means reflects the result of editing on destination information corresponding to destination information edited in said destination database among destination information registered in said individual list. Device. When displaying the individual list, the third destination information display means deletes the destination information deleted from the destination database among the destination information registered in the individual list from the destination database. 2. The information processing apparatus according to claim 1, wherein a display is provided to notify that the information processing has been performed. Further comprising individual list creation means for creating the individual list,
2. The third destination information display means displays the already created list as an initial display when a new individual list is created by the individual list creation means. The information processing device described. 3. The third destination information display means displays the already created shared list as an initial display when a new individual list is created by the individual list creation means. The information processing device according to . further comprising individual list editing means for accepting designation of one or a plurality of destination information among destination information registered in the destination database or destination information registered in the shared list, and adding the designated destination information to the individual list. 2. The information processing apparatus according to claim 1, comprising: a destination database in which destination information is registered;
First destination list management for managing a first destination list in which reference information referring to destination information registered in the destination database is registered, and destination information can be read by terminal devices of a plurality of users via the reference information. Department and
A second destination for each authenticated user, in which reference information referring to the destination information registered in the destination database is registered, and the destination information can be read by the terminal device of the authenticated user via the reference information a second destination list management unit that manages the list;
A data management system comprising: the destination database is permitted to be edited by a user having editing authority for the destination database;
the first destination list permits registration and deletion of the reference information by a user who has operation authority for the first destination list;
7. The data management according to claim 6, wherein registration and deletion of said reference information by said authenticated user corresponding to said individual second destination list is permitted for each said second destination list. system. Registration of reference information in the first destination list is performed by designating destination information to be registered, creating reference information corresponding to the destination information in the destination database, and registering the reference information in the first destination list,
Registration of reference information in the second destination list includes specifying destination information to be registered, duplicating reference information corresponding to the destination information in the first destination list, and registering the reference information in the second destination list; 7. The data management system according to claim 6, wherein reference information corresponding to said destination information in said destination database is created and registered in said second destination list. display means for displaying destination information based on a shared list shared by multiple users and a separate list used by authenticated users;
switching means for switching between display based on the shared list and display based on the individual list;
changing means for changing the order of destination information in the individual list,
The destination information display device, wherein the display means displays destination information based on the shared list as an initial display when a new individual list is created. the computer,
first destination information display means for displaying destination information registered in a destination database on a display device;
second destination information display means for displaying, on a display device, a shared list in which at least part of the destination information registered in the destination database is registered and shared by a plurality of users;
At least a part of the destination information registered in the destination database is registered and functions as third destination information display means for displaying an individual list used by an authenticated user on a display device;
When the destination database is edited, the second destination information display means reflects the editing result in the destination information corresponding to the destination information edited in the destination database among the destination information registered in the shared list. , wherein the third destination information display means reflects the result of editing on destination information corresponding to the destination information edited in the destination database among the destination information registered in the individual list.

Images