Business card management system and business card management program

Abstract

To achieve a business card management system that can increase the possibility that a date when business cards are actually exchanged or a date close to the exchange date are registered as a business card exchange date.SOLUTION: In a business card management system, a processing server executes meeting participant count estimation processing S13 of estimating a meeting participant count that is the number of participants in a meeting other than a user, executes business card exchange date registration processing S15 when a first input count Na that is the number of business cards input by a first user on an input date is equal to or less than a determination threshold Nmax defined based on the meeting participant count, and executes business card exchange date suspension processing S16 when the first input count Na is greater than the determination threshold Nmax.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present invention relates to a business card management system and a business card management program for managing information related to business cards. [Background technology]

[0002] There is known a business card management system for managing information about business cards. The business card management system of JP 2021-026630 A (Patent Document 1) includes a scanner (7a, 7b) for scanning business cards and a business card processing unit (107) for extracting business card information from the scanned business card image and registering it in a business card database. The business card processing unit (107) compares the extracted business card information with the business card information in the business card database, and if there is business card information with the same organization name, name, and email address (S102, S103), and if there is a difference between the business card information, it updates the business card information in the business card database with the extracted business card information and registers it (S104). This update is basically performed if the scan date and time is more recent. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-026630 Summary of the Invention [Problem to be solved by the invention]

[0004] In a business card management system that scans business cards, the actual date on which a user exchanged business cards may differ from the date on which the cards were scanned. Patent Document 1, however, discloses a method of requiring the user to reconfirm the date on which the cards were actually exchanged and the date on which the cards were scanned each time an update is made. However, this method places a significant burden on the user, as it can easily result in incorrect updates to business card information based on dates that differ from the actual dates on which the cards were exchanged.

[0005] Therefore, it is desirable to realize a business card management system and a business card management program that can increase the likelihood that the day on which business cards were actually exchanged or a day close to that day will be registered as the business card exchange date. [Means for solving the problem]

[0006] The business card management system according to the present disclosure includes a business card database in which business card information for each of a plurality of business cards is stored, a schedule database in which meeting information for each of a plurality of users is stored, a processing server connected to the business card database and the schedule database, and an input terminal communicably connected to the processing server and configured to accept input of the business card information for one or more of the business cards by one or more of the users, wherein the meeting information includes identification information that can identify one or more of the users who will participate in each meeting, and the processing server is configured to cooperate with the input terminal to execute a business card registration process that registers the business card information input by each of the plurality of users in the business card database, wherein one of the one or more users who input the business card information via the input terminal is defined as a first user, the date on which the first user inputs the business card information is defined as an input date, and the business card information input by the first user on the input date is defined as a first user. the processing server defines one or more of the business cards entered as first business cards, defines the number of the first business cards as a first input number, and acquires from the schedule database the meeting information of the meeting attended by the first user on the input date; identifies second users who are other users who attended the same meeting as the first user based on the acquired meeting information; performs a meeting number estimation process to estimate a meeting number, which is the number of participants in the meeting other than the first user, based on a second input number, which is the number of business cards entered by the second user on the input date; if the first input number is equal to or less than a determination threshold determined based on the meeting number, performs a business card exchange date registration process to register the input date in the business card database as the business card exchange date of the first business card; and if the first input number is greater than the determination threshold, performs a business card exchange date reservation process to register the business card exchange date of the first business card in the business card database as unknown, or to leave the business card exchange date of the first business card as unregistered.

[0007] A business card management program according to the present disclosure is a business card management system including a business card database in which business card information for each of a plurality of business cards is stored, a schedule database in which meeting information for each of a plurality of users is stored, a processing server connected to the business card database and the schedule database, and an input terminal communicably connected to the processing server and configured to accept input of the business card information for one or more of the business cards by one or more of the users. The business card management program causes a computer to realize the business card management function of the processing server, wherein the meeting information includes identifying information that can identify one or more of the users participating in each meeting, one of the one or more users who input the business card information via the input terminal is designated as a first user, the date on which the business card information was input by the first user is designated as an input date, the one or more business cards input by the first user on the input date are designated as first business cards, and the number of the first business cards is designated as a first input number, and the processing server receives the input information from the input terminal. The terminal cooperates with the terminal to execute a business card registration process that registers the business card information entered by each of the multiple users in the business card database, acquires from the schedule database the meeting information of the meeting attended by the first user on the input date, identifies a second user who is another user who attended the same meeting as the first user based on the acquired meeting information, and executes a meeting number estimation process that estimates a meeting number, which is the number of participants in the meeting other than the first user, based on a second input number that is the number of business cards entered by the second user on the input date, and if the first input number is equal to or less than a judgment threshold determined based on the meeting number, executes a business card exchange date registration process that registers the input date in the business card database as the business card exchange date of the first business card, and if the first input number is greater than the judgment threshold, registers the business card exchange date of the first business card in the business card database as unknown, or executes a business card exchange date suspension process that leaves the business card exchange date of the first business card unregistered.

[0008] According to this configuration, when business card information for a number of business cards that is too large compared to the number of people at the meeting estimated based on the meeting information is input, the input date of such business card information may not be the actual date of the business card exchange, and the business card exchange date can be set as unknown or unregistered. Therefore, when business card information for business cards exchanged in the past is input, and the number of business cards is too large compared to the number of people at the meeting, the possibility of registering such input date as the business card exchange date as erroneous information can be reduced. This increases the possibility that the actual date of the business card exchange or a date close to that date will be registered as the business card exchange date. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a business card management system according to a first embodiment; [Figure 2] A diagram showing multiple business card information registered in the business card database in Figure 1. [Figure 3] A diagram showing a search screen for business card information registered in the business card database in Figure 1. [Figure 4] A diagram showing details of the business card information registered in the business card database in Figure 1. [Figure 5] A diagram showing an example of meeting information registered in the schedule database of Figure 1. [Figure 6] FIG. 2 is a flowchart showing the processing executed by the processing server of FIG. 1. [Figure 7] FIG. 7 is a diagram showing details of the meeting number estimation process in FIG. 6; [Figure 8] FIG. 2 is a diagram showing another example of meeting information registered in the schedule database of FIG. 1. [Figure 9] FIG. 10 is a diagram showing details of a meeting number estimation process according to the second embodiment; DETAILED DESCRIPTION OF THE INVENTION

[0010] [First embodiment] A business card management system and a business card management program according to a first embodiment will be described below with reference to the drawings.

[0011] FIG. 1 shows an example of the system configuration of a business card management system 10. The business card management system 10 includes a processing server 15. The processing server 15 manages the business card information 31d of each of a plurality of business cards 11. The processing server 15 may be a single server, or may include a plurality of servers, and the functions of the processing server 15 may be realized by these multiple servers. In this embodiment, the processing server 15 is a cloud server, but it may also be an on-premise server.

[0012] The business card management program is a program that enables the processing server 15 in the business card management system 10 to realize the business card management function. The business card management function is realized by the cooperation of hardware with a computing device at its core and software (the business card management program). The computing device is, for example, a motherboard built into the main body of a personal computer, and includes at least one microprocessor as its core, as well as a DSP (Digital Signal Processor) and other peripheral elements. The computing device is connected to a storage device such as an HDD (Hard Disc Drive) or SSD (Solid State Drive).

[0013] The business card management system 10 includes an input terminal 20. The input terminal 20 accepts input of business card information 31d of one or more business cards 11 by one or more users 12. In this embodiment, the processing server 15 includes a plurality of input terminals 20. Examples of the input terminal 20 include an imaging device such as a camera or scanner, a touch panel, a keyboard, a mouse, a microphone, a personal digital assistant (PDA) that can be carried by the user 12, a desktop personal computer, a laptop personal computer, etc. In this embodiment, the input terminal 20 is a terminal capable of optical character recognition of characters written on the business card 11 or characters in a captured image of the business card 11.

[0014] In this embodiment, the business card management system 10 is equipped with an input terminal 20 that can capture multiple business cards 11 consecutively or all at once to generate multiple captured images. Examples of such an input terminal 20 include a scanner with an automatic document feeder, an information terminal with a photography function and a photo division function, etc.

[0015] In this embodiment, the input terminal 20 includes an output device 21. Examples of the output device 21 include a touch panel, a liquid crystal display, a projector, and a speaker.

[0016] In this embodiment, the input terminal 20 includes a communication device 22. Examples of the communication device 22 include a wireless LAN (Local Area Network) adapter, a wired LAN adapter, an LTE (Long Term Evolution) adapter, and a 4G (4th Generation Mobile Communication System) adapter.

[0017] In this embodiment, the business card management system 10 includes a plurality of input terminals 20, which are portable information terminals. Each input terminal 20, which is a portable information terminal, includes an imaging device 23 that can capture an image of at least one business card 11.

[0018] The processing server 15 and the plurality of input terminals 20 are connected to each other so as to be able to communicate with each other via a network 25. The network 25 may be both a wired and a wireless network. In this embodiment, a relay device (not shown) and the processing server 15 are connected via a wired network, and the input terminals 20 and the relay device are connected via a wireless network. However, the processing server 15 and the input terminals 20 may be connected via a wired network, or the processing server 15 and the input terminals 20 may be directly connected via a wireless network.

[0019] The business card management system 10 includes a business card database 31. The business card database 31 stores business card information 31d for each of a plurality of business cards 11. The processing server 15 is connected to the business card database 31. In this embodiment, one piece of business card information 31d is registered in the business card database 31 for one business card 11.

[0020] 2 is a diagram showing an example of a screen displaying multiple pieces of business card information 31d registered in the business card database 31. Examples of the business card information 31d include a name 17a, an affiliation 17b such as a company name or department name, a job title, an address, contact information such as an email address 17c or a telephone number, an exchange user who is a user 12 with whom the business card 11 was exchanged, and a captured image of the business card 11. The business card information 31d is associated with a business card ID. In this embodiment, the business card ID is a number unique to each of the multiple business cards 11.

[0021] The screen shown in FIG. 2 displays the results of a search narrowed down by main item A1 for all business card information 31d registered in the business card database 31. Main item A1 is an item for identifying whether or not the person listed on multiple business cards 11 is the same person. Examples of main item A1 include name 17a, affiliation 17b, email address 17c, and an identification number for identifying the same person. On the screen shown in FIG. 2, multiple pieces of business card information 31d with the same main item A1 are arranged in descending order of input date D1. In the illustrated example, main item A1 is name 17a and affiliation 17b. In this embodiment, affiliation 17b is a company name, but it may also be a company name and department name, or the name of a local government, region, etc.

[0022] Returning to FIG. 1, the business card management system 10 includes a user database 32. The user database 32 stores attribute information 32d for each of a plurality of users 12. The processing server 15 is connected to the user database 32. Examples of the attribute information 32d include user address information indicating the address of the user 12, and user area information indicating the area covered by the user 12.

[0023] The business card management system 10 includes a map database 33. The map database 33 stores map information 33d. The processing server 15 is connected to the map database 33. Examples of the map information 33d include coordinates such as latitude, longitude, and altitude, topographical features such as rivers, mountains, and coastlines, and areas such as national borders and administrative districts. In this embodiment, the map information 33d is information used to estimate the area of ​​responsibility of each user 12.

[0024] The business card management system 10 includes a schedule database 34. The schedule database 34 stores meeting information 34d for each of a plurality of users 12. The processing server 15 is connected to the schedule database 34. Here, a meeting is a general term for a situation in which a business card 11 is used, in other words, a situation in which people meet, and includes various situations such as business trips.

[0025] Examples of the meeting information 34d include the name of the meeting, the planned participants, the planned number of participants, the planned date and time, the meeting method such as a visit or a web meeting, business partner information such as the business partner's name and business partner's company information, the location, the actual participants, the actual number of participants, and the actual date and time of the meeting. In this embodiment, the meeting information 34d includes specific information that can identify one or more users 12 who will be attending each meeting. The meeting information 34d includes specific information that can identify all users 12 who will be attending each meeting or all users 12 who have attended each meeting. Examples of the specific information include user names, account names, email addresses, etc.

[0026] Each of the multiple users 12 inputs the business card information 31d of the business card 11 into the input terminal 20 on the day they exchanged the business card 11. The input of the business card information 31d by the users 12 into the input terminal 20 is performed according to a rule that the business card information 31d of the business card 11 is input within a set period that is set starting from the day the business cards 11 were exchanged. This set period is set to, for example, one day or two days. In this embodiment, this set period is one day, and each of the multiple users 12 is prohibited from inputting the business card information 31d of the business card 11 into the input terminal 20 on a day after the day the business cards 11 were exchanged.

[0027] The processing server 15 is configured to cooperate with multiple input terminals 20 to register business card information 31d in the business card database 31. As shown in FIG. 2, in this embodiment, when registering the business card information 31d, the input date and time of the business card information 31d by each input terminal 20 of multiple users 12 are registered in the business card database 31 as part of the business card information 31d. The input date and time of this business card information 31d may be only the input date D1, or may be the input date D1 and the input time. The input date and time of the business card information 31d may be acquired by the input terminal 20 and sent to the processing server 15, and the date and time of reception by the processing server 15 may be used as the input date and time of the business card information 31d. The screen shown in FIG. 2 is a screen displayed on the output device 21. In this embodiment, the screen shown in FIG. 2 is a screen for managing the business card database 31.

[0028] Fig. 3 shows an example of a search screen for multiple pieces of business card information 31d registered in the business card database 31. The screen shown in Fig. 3 is a search screen displayed on the output device 21. A search button that allows for a refined search is displayed in a first area E1 of the search screen. The first area E1 of the search screen is configured to allow for a refined search using the above-mentioned main item A1, attribute information 32d, map information 33d, etc.

[0029] The search results are displayed in the second area E2 of the search screen. The second area E2 of the search screen is configured to be able to hide business card information 31d for which the business card exchange date Da is unknown, unregistered, etc. In this embodiment, the second area E2 of the search screen is configured to be able to display only the business card information 31d with the most recent business card exchange date Da among multiple pieces of business card information 31d with the same main item A1. This prevents multiple pieces of business card information 31d of the same person from being displayed on the screen and interfering with the search. Furthermore, displaying business card information 31d with the most recent business card exchange date Da can be prioritized over displaying business card information 31d with the most recent input date D1.

[0030] 4 is a diagram showing an example of a screen displaying one piece of business card information 31d registered in the business card database 31. The business card information 31d is input by capturing an image of the business card 11 using the input terminal 20. The input terminal 20 or the processing server 15 performs optical character recognition on the captured image 11p of the business card 11 to acquire character information 11s of the business card 11 as business card information 31d to be registered in the business card database 31. In this embodiment, in the business card registration process S11 described below, the captured image 11p of the business card 11 is registered in the business card database 31 as part of the business card information 31d. The screen shown in FIG. 4 is a screen displayed on the output device 21.

[0031] FIG. 5 is a diagram showing an example of a screen displaying meeting information 34d registered in the schedule database 34. One of the one or more users 12 who input business card information 31d via the input terminal 20 is referred to as the first user 12a. The date on which the first user 12a inputs the business card information 31d is referred to as the input date D1. Another user 12 who participated in the same meeting as the first user 12a on the input date D1 is referred to as the second user 12b. If the second user 12b participated in another meeting on the input date D1, the other user 12 who participated in the other meeting is referred to as the third user 12c. The third user 12c is a user 12 different from the first user 12a. The third user 12c is also a user 12 different from the other user 12 (i.e., the second user 12b) who participated in the same meeting as the first user 12a on the input date D1.

[0032] One or more business cards 11 input by the first user 12a on input date D1 are referred to as the first business cards 11a. The number of first business cards 11a is referred to as the first input number Na. One or more business cards 11 input by the second user 12b on input date D1 are referred to as the second business cards 11b. The number of second business cards 11b is referred to as the second input number Nb. One or more business cards 11 input by the third user 12c on input date D1 are referred to as the third business cards 11c. The number of third business cards 11c is referred to as the third input number Nc.

[0033] The screen shown in Fig. 5 is a screen displayed on the output device 21. Fig. 5 shows meeting information 34d when the second user 12b attended another meeting on input date D1. In addition to the screen showing the meeting information 34d on input date D1, Fig. 5 also shows, for reference, two first business cards 11a, five second business cards 11b, and three third business cards 11c that the first user 12a, the second user 12b, and the third user 12c actually received, respectively.

[0034] 6 is a diagram showing an example of processing that the business card management program causes the processing server 15 to execute. The processing server 15 is configured to execute business card registration processing S11 in which business card information 31d input by each of a plurality of users 12 is registered in the business card database 31 in cooperation with the input terminal 20. In this embodiment, the processing server 15 executes the business card registration processing S11 every time business card information 31d input by a user 12 is received from the input terminal 20.

[0035] The processing server 15 executes a minimum number determination process S12 to determine whether the first input number Na is equal to or less than the first minimum number Nmin. If the first input number Na is greater than the first minimum number Nmin, the processing server 15 executes a meeting number estimation process S13. If the first input number Na is equal to or less than the first minimum number Nmin, the processing server 15 executes a business card exchange date registration process S15 (described later) without executing the meeting number estimation process S13. In this embodiment, the first minimum number Nmin is 1, but it may be 2, 3, or more. This can omit the meeting number estimation process S13 when the first user 12a has exchanged only a small number of business cards 11 and it is unlikely that business cards 11 exchanged in the past will be confused, thereby reducing the burden on the processing server 15. Furthermore, the frequency of the business card exchange date reservation process S16 can be prevented from becoming too high.

[0036] The processing server 15 executes a meeting number estimation process S13 to estimate a meeting number H1, which is the number of meeting participants other than the user 12. The processing server 15 executes a business card exchange date registration process S15 to register the input date D1 as the business card exchange date Da of the first business card 11a in the business card database 31. In this embodiment, the meeting participants other than the user 12 are participants from an organization (e.g., a company, a business group, a local government, a region, etc.) different from that of the first user 12a. Furthermore, the second user 12b and the third user 12c belong to the same organization (e.g., a company, a business group, a local government, a region, etc.) as the first user 12a.

[0037] The processing server 15 executes a business card exchange date reservation process S16 in which the business card exchange date Da of the first business card 11a is registered as unknown in the business card database 31, or the business card exchange date Da of the first business card 11a is not registered. The processing server 15 executes a warning process S17 in which the first user 12a is warned.

[0038] In this embodiment, the meeting number estimation process S13 for estimating the number of people H1 attending a meeting on input date D1 is executed, for example, during the night on input date D1, after work hours, or on the day following input date D1. The processing server 15 executes the meeting number estimation process S13 from the business card information 31d entered by the user 12 whose input time on input date D1 is the latest, or from the business card information 31d entered by the user 12 whose priority is the lowest. The priority of a user 12 is determined based on, for example, the frequency of past input of business card information 31d, the frequency of past business card exchange date reservation process S16, the job responsibilities, the job title, etc.

[0039] In addition, the processing server 15 may be configured to execute the meeting number estimation processing S13, business card exchange date registration processing S15, business card exchange date reservation processing S16, warning processing S17, etc., each time it executes the business card registration processing S11.

[0040] 7 is a diagram showing details of the subroutine that is the meeting number estimation process S13. In the meeting number estimation process S13, the processing server 15 acquires meeting information 34d of the meeting that the first user 12a attended on the input date D1 from the schedule database 34 (S21).

[0041] The acquisition of meeting information 34d by the processing server 15 from the schedule database 34 may be acquisition of meeting information 34d of meetings attended by the first user 12a on an input date D1 prior to the input time, or acquisition of meeting information 34d of all meetings attended by the first user 12a on the input date D1. The meeting information 34d of meetings attended by the first user 12a on the input date D1 may be meeting information 34d of meetings that the first user 12a actually attended on the input date D1, or may be meeting information 34d of meetings that the first user 12a is scheduled to attend on the input date D1.

[0042] In this embodiment, if the processing server 15 cannot obtain meeting information 34d of a meeting that the first user 12a attended on the input date D1 from the schedule database 34, it executes the business card exchange date reservation process S16 described below, but it may also be configured to execute the business card exchange date registration process S15.

[0043] The processing server 15 determines whether the meeting information 34d acquired from the schedule database 34 includes number-of-persons information Ht that can identify the number of people H1 at the meeting (S22). If the meeting information 34d includes number-of-persons information Ht that can identify the number of people H1 at the meeting, the processing server 15 executes a meeting number-of-persons estimation process S13 using the number-of-persons information Ht (S31). Examples of the number-of-persons information Ht include names of planned participants, the planned number of participants, names of actual participants, the actual number of participants, etc.

[0044] If the meeting information 34d does not include number of people information Ht, the processing server 15 estimates the number of people at the meeting H1 based on the first input number Na, the second input number Nb, the third input number Nc, etc. in the meeting number estimation process S13 as follows.

[0045] In the meeting number-of-persons estimation process S13, the processing server 15 identifies the second user 12b, who is another user 12 who attended the same meeting as the first user 12a, based on the acquired meeting information 34d. In the example shown in FIG. 7, the processing server 15 identifies the second user 12b and determines whether the second input number Nb of the second user 12b is greater than the second minimum number N2 (S23). In this embodiment, the second minimum number N2 is 1, but it may be 2, or a number greater than or equal to 3. In this manner, if the second input number Nb is a small value, such as 0 or 1, it is possible to avoid executing processes such as S24 or S34 described below based on such a second input number Nb, thereby reducing the burden on the processing server 15. Furthermore, it is possible to prevent the meeting number H1 from being estimated based on a small second input number Nb, which would result in the business card exchange date reservation process S16 being executed too frequently.

[0046] In this embodiment, when the processing server 15 cannot identify a second user 12b who participated in the same meeting as the first user 12a in the meeting information 34d, or when it determines that there are no other users 12 who participated in the same meeting as the first user 12a, the processing server 15 estimates the number of people at the meeting H1 based on the first input number Na.

[0047] 7, the processing server 15 estimates the number of people attending the meeting H1 based on the first input number Na when the second input number Nb is equal to or less than the second minimum number N2 (S32). In the example shown in FIG. 7, the processing server 15 estimates the number of people attending the meeting H1 to be the same as the first input number Na (S32).

[0048] In the meeting number-of-persons estimation process S13, the processing server 15 estimates the meeting number H1, which is the number of meeting participants other than the user 12, based on the second input number Nb, which is the number of business cards 11 input by the second user 12b on the input date D1. In the example shown in Fig. 7, when the second input number Nb is greater than the second minimum number N2, the processing server 15 estimates the meeting number H1 based on the second input number Nb (S33, S34).

[0049] In the meeting number-of-persons estimation process S13, if the second user 12b attended another meeting on the input date D1, the processing server 15 identifies the third user 12c, who is another user 12 who attended the same meeting as the second user 12b, based on the acquired meeting information 34d. In the example shown in Figure 7, the processing server 15 identifies the third user 12c and determines whether the third input number Nc is greater than the third minimum number N3 (S24). In this embodiment, the third minimum number N3 is 0, but it may also be 1 or a number greater than or equal to 2.

[0050] In this embodiment, when the processing server 15 cannot identify a third user 12c who attended the same meeting as the second user 12b in the meeting information 34d, or when it determines that there are no other users 12 who attended the same meeting as the second user 12b, it estimates the number of people at the meeting H1 based on the second input number Nb.

[0051] In the meeting number estimation process S13, the processing server 15 derives the meeting number H1 from the second input number Nb. In this embodiment, in the meeting number estimation process S13, the processing server 15 estimates the meeting number H1 to be the same as the second input number Nb. In the example shown in FIG. 7, the processing server 15 derives the meeting number H1 from the second input number Nb when the third input number Nc is equal to or less than the third minimum number N3 (S33). In the example shown in FIG. 7, the processing server 15 estimates the meeting number H1 to be the same as the second input number Nb when the third input number Nc is equal to or less than the third minimum number N3 (S33). In this way, it is easy to derive the meeting number H1 from the second input number Nb.

[0052] In the meeting number-of-persons estimation process S13, if the second user 12b attended another meeting on the input date D1, the processing server 15 estimates the meeting number H1 based on the second input number Nb and the third input number Nc, which is the number of business cards 11 entered on the input date D1 by the third user 12c, who is another user 12 who attended the other meeting. In the example shown in Fig. 7, if the third input number Nc is greater than the third minimum number N3, the processing server 15 estimates the meeting number H1 based on the second input number Nb and the third input number Nc (S34).

[0053] 7, the processing server 15 estimates the number of people attending the meeting H1 to be equal to the value obtained by subtracting the third input number Nc from the second input number Nb (S34). Although not shown, if the value obtained by subtracting the third input number Nc from the second input number Nb is less than the minimum number of people Hmin, the processing server 15 estimates the number of people attending the meeting H1 to be equal to the minimum number of people Hmin. In this embodiment, the minimum number of people Hmin is 1, but it may also be 2, 3 or more, or the same value as the first minimum number Nmin.

[0054] In this embodiment, in the meeting number-person estimation process S13, if there are multiple third users 12c participating in the same meeting as the second user 12b, the meeting number H1 is estimated based on the second input number Nb and the third input number Nc of any one of the multiple third users 12c. However, the meeting number H1 may also be estimated based on the second input number Nb and the average value Ncv of the multiple third input numbers Nc, or the meeting number H1 may be estimated based on the second input number Nb and the maximum value Ncx of the multiple third input numbers Nc. Furthermore, the meeting number H1 may also be estimated based on the second input number Nb and any one third input number Nc among the multiple third input numbers Nc that is greater than the third minimum number N3. Furthermore, in calculating the average value Ncv, third input numbers Nc that are equal to or less than the third minimum number N3 may be excluded.

[0055] 6, the processing server 15 executes a maximum number determination process S14 to determine whether the first input number Na is equal to or less than a determination threshold value Nmax. In this embodiment, the processing server 15 determines whether the first input number Na is equal to or less than a determination threshold value Nmax determined based on the number of people attending the meeting H1. The determination threshold value Nmax may be a decimal number or an irrational number.

[0056] Although not shown, in this embodiment, when there are multiple second users 12b, the processing server 15 estimates the number of meeting people Hu for each second user 12b (number of meeting people per second user), and determines the judgment threshold Nmax using the average value or maximum value of the number of meeting people Hu as the number of meeting people H1. Note that when there are multiple second users 12b, the number of meeting people H1 may be estimated based on any one of the multiple second input numbers Nb that is larger than the second minimum number N2.

[0057] Although not shown in the figure, in this embodiment, when the first user 12a attends multiple meetings on the input date D1, the processing server 15 estimates the number of people attending each meeting (number of people attending each meeting) Hd, and determines the judgment threshold Nmax by adding up all of these number of people attending Hd as the number of people attending H1.

[0058] In this embodiment, the determination threshold Nmax is set to a value obtained by multiplying the number of people meeting H1 by a predetermined coefficient K1. In this embodiment, Nmax = K1 × H1. Examples of the coefficient K1 include 1, 2, 3, a number between 1 and 2, and a number between 1 and 3.

[0059] If the first input number Na is less than or equal to the judgment threshold Nmax determined based on the number of people meeting H1, the processing server 15 executes a business card exchange date registration process S15 to register the input date D1 in the business card database 31 as the business card exchange date Da of the first business card 11a.

[0060] If the first input number Na is greater than the judgment threshold Nmax, the processing server 15 executes a business card exchange date reservation process S16 in which the business card exchange date Da of the first business card 11a is registered in the business card database 31 as unknown, or the business card exchange date Da of the first business card 11a is not registered.

[0061] When the processing server 15 executes the business card exchange date reservation processing S16, it executes an alert processing S17 for issuing an alert to the first user 12a. Examples of alerts issued to the first user 12a include outputting alert information from the output device 21 of the input terminal 20, which is the mobile information terminal of the first user 12a, sending an alert message to the contact information of the first user 12a, sending an alert message to the contact information of the first user 12a's boss, etc.

[0062] According to the business card management system 10 and business card management program described above, when business card information 31d of a large number of business cards 11 compared to the number of people attending a meeting is entered, for example, when a user 12 inputs all business cards 11 exchanged in the past, or when business cards 11 exchanged in the past are input mixed in with business cards 11 exchanged by a first user 12a at a meeting on input date D1, it is possible to reduce the possibility that such an incorrect input date D1 will be registered as the business card exchange date Da in the business card database 31. It is also possible to reduce the possibility that a large amount of business card information 31d with an incorrect business card exchange date Da will be registered in the business card database 31, and it is also possible to reduce the effort required to correct business card information 31d registered in the business card database 31, for example.

[0063] Second Embodiment The following describes a business card management system 10 and a business card management program according to a second embodiment with reference to the drawings. This embodiment differs from the first embodiment in that in the meeting number estimation process S13, if the second user 12b attended another meeting on the input date D1, the third user 12c is not identified. The following description will focus on the differences from the first embodiment. Note that points not specifically described are the same as those in the first embodiment.

[0064] Fig. 8 is a diagram showing an example of a screen displaying meeting information 34d registered in the schedule database 34. In addition to the screen showing the meeting information 34d on input date D1, Fig. 8 also shows, for reference, three first business cards 11a actually received by the first user 12a and four and three second business cards 11b actually received by multiple second users 12b. The screen shown in Fig. 8 is a screen displayed on the output device 21. Fig. 8 shows meeting information 34d when there are multiple second users 12b.

[0065] 9 is a diagram showing details of the subroutine that is the meeting number estimation process S13. In this embodiment, in the meeting number estimation process S13, the processing server 15 identifies second users 12b based on the acquired meeting information 34d and determines whether there are one or more second users 12b (S41).

[0066] If the number of second users 12b who attended the same meeting as the first user 12a is less than one, the processing server 15 estimates the number of people attending the meeting H1 based on the first input number Na (S32).If the number of second users 12b who attended the same meeting as the first user 12a is one or more, the processing server 15 estimates the number of people attending the meeting H1 based on the second input number Nb (S33, S45).

[0067] In the meeting number-of-persons estimation process S13, the processing server 15 determines whether there are two or more second users 12b based on the acquired meeting information 34d (S42).

[0068] If there is one second user 12b who participated in the same meeting as the first user 12a, the processing server 15 determines whether the second input number Nb of the second user 12b is greater than the second minimum number N2 (S43).

[0069] In this embodiment, when the second user 12b is one person and the second input number Nb is equal to or less than the second minimum number N2, the processing server 15 estimates the number of people attending the meeting H1 based on the first input number Na (S32).When the second user 12b is one person and the second input number Nb is greater than the second minimum number N2, the processing server 15 estimates the number of people attending the meeting H1 based on the second input number Nb (S33).

[0070] In this embodiment, in the meeting number-of-persons estimation process S13, if there are multiple second users 12b and their respective second input numbers Nb do not match, the processing server 15 estimates the meeting number H1 based on the average value Nbv of the second input numbers Nb or the maximum value Nbx of the second input numbers Nb. In this embodiment, the processing server 15 estimates the meeting number H1 to be the same as the average value Nbv or the maximum value Nbx.

[0071] In the illustrated example, in the meeting number-person estimation process S13, if there are multiple second users 12b and their second input numbers Nb do not match, the processing server 15 calculates an average value Nbv for second input numbers Nb greater than the second minimum number N2 (S44). In other words, the processing server 15 excludes second input numbers Nb equal to or less than the second minimum number N2 from the calculation of the average value Nbv. In this way, the influence of second users 12b with small second input numbers Nb can be excluded from the average value Nbv.

[0072] In this embodiment, the processing server 15 estimates the number of people attending the meeting H1 to be equal to the average value Nbv or the maximum value Nbx of the second input number Nb, which is greater than the second minimum number N2 (S45). Note that if the average value Nbv or the maximum value Nbx is less than the minimum number of people Hmin, the processing server 15 estimates the number of people attending the meeting H1 to be equal to the minimum number of people Hmin.

[0073] In addition, even when there are multiple second users 12b and their respective second input numbers Nb are the same, the processing server 15 may be configured to estimate the number of people meeting H1 based on the average value Nbv of the second input numbers Nb or the maximum value Nbx of the second input numbers Nb.

[0074] Other Embodiments Next, other embodiments of the business card management system and the business card management program will be described.

[0075] (1) In the above embodiment, an example has been described in which the processing server 15, in cooperation with a plurality of input terminals 20, executes the business card registration process S11 to register the business card information 31d input by each of a plurality of users 12 in the business card database 31. However, the present invention is not limited to such an example. For example, the processing server 15 may be configured to cooperate with a single input terminal 20 to register the business card information 31d input by a plurality of users 12 in the business card database 31. Furthermore, for example, input by a plurality of users 12 may be performed by a single agent. Furthermore, for example, the processing server 15 may be configured to cooperate with a single input terminal 20 to register the business card information 31d input by a single user 12 in the business card database 31.

[0076] (2) In the above embodiment, an example has been described in which the input terminal 20 includes the output device 21. However, the present invention is not limited to such an example, and for example, the output device 21 may be provided in the business card management system 10 separately from the input terminal 20.

[0077] (3) In the above embodiment, the processing server 15 estimates that the first input number Na, the second input number Nb, or the value obtained by subtracting the third input number Nc from the second input number Nb is equal to the number of people at the meeting H1. However, without being limited to such an example, the processing server 15 may estimate that the number of people at the meeting H1 is equal to the value obtained by adding or multiplying the first input number Na, the second input number Nb, or the value obtained by subtracting the third input number Nc from the second input number Nb by a predetermined value (e.g., 1, 1.5, 2, etc.).

[0078] (4) In the above embodiment, an example has been described in which the number of attendees H1 is estimated based on the second input number Nb and the third input number Nc when the second user 12b attends another meeting on the input date D1. However, without being limited to such an example, for example, when the second user 12b attends another meeting on the input date D1, the number of attendees H1 may be estimated to be equal to the first input number Na, the second input number Nb, the average value of the second input number Nb, or the like. Also, for example, in the meeting number-of-attendees estimation process S13, when the third user 12c attends yet another meeting on the input date D1, in addition to the second input number Nb and the third input number Nc, a fourth input number, which is the number of business cards 11 entered on the input date D1 by a fourth user 12, who is another user 12 who attended the yet another meeting, may be used to estimate the number of attendees H1.

[0079] (5) In the above embodiment, the processing server 15 executes the meeting number estimation process S13 using the number-of-persons information Ht when the meeting information 34d includes number-of-persons information Ht that can identify the number of people attending the meeting H1. However, the present invention is not limited to such an example. For example, the processing server 15 may execute the meeting number estimation process S13 based on the second input number Nb, regardless of whether the meeting information 34d includes number-of-persons information Ht that can identify the number of people attending the meeting H1.

[0080] (6) In the above embodiment, an example has been described in which the determination threshold Nmax is set to a value obtained by multiplying the number of people at a meeting H1 by a predetermined coefficient K1. However, without being limited to such an example, for example, the determination threshold Nmax may be set to a value obtained by adding a predetermined value (e.g., 1 or 2) to the number of people at a meeting H1. Also, for example, the determination threshold Nmax may be a value obtained by adding the average number of business cards 11 registered per day by the first user 12a in the past to the number of people at a meeting H1. Also, for example, the determination threshold Nmax may be the number of people at a meeting H1.

[0081] (7) In the above embodiment, the processing server 15 executes the alert process S17 to alert the first user 12a when the business card exchange date reservation process S16 is executed. However, without being limited to such an example, for example, the processing server 15 may execute the alert process S17 to alert the first user 12a when the processing server 15 is unable to acquire the meeting information 34d of the meeting that the first user 12a attended on the input date D1 from the schedule database 34. Also, for example, the processing server 15 may not execute the alert process S17. Also, for example, the processing server 15 may not execute the minimum number determination process S12.

[0082] (8) In the above embodiment, the processing server 15 executes the business card registration process S11 each time business card information 31d input by the user 12 is received from the input terminal 20. However, the present invention is not limited to such an example, and may be configured such that the processing server 15 executes the business card registration process S11 collectively for multiple pieces of business card information 31d received from the input terminal 20 on the input date D1.

[0083] (9) In the above embodiment, an example has been described in which each of the multiple users 12 is prohibited from inputting the business card information 31d of the business card 11 into the input terminal 20 on a date after the date on which the business card 11 was exchanged. However, the present invention is not limited to such an example, and for example, each of the multiple users 12 may be configured to be able to register the input date D1 from the input terminal 20. Furthermore, for example, a user 12 who has received a warning from the warning process S17 may be configured to be able to change the input date D1 from the input terminal 20.

[0084] (10) The configurations disclosed in the above-described embodiments may be combined with configurations disclosed in other embodiments as long as no contradictions arise. Regarding other configurations, the embodiments disclosed in this specification are merely examples in all respects. Therefore, various modifications may be made as appropriate within the scope of the present disclosure.

[0085] Summary of the above embodiment The business card management system and business card management program according to the present disclosure will be described below.

[0086] In one aspect, the business card management system includes a business card database in which business card information for each of a plurality of business cards is stored, a schedule database in which meeting information for each of a plurality of users is stored, a processing server connected to the business card database and the schedule database, and an input terminal communicably connected to the processing server and configured to accept input of the business card information for one or more of the business cards by one or more of the users, wherein the meeting information includes identification information that can identify one or more of the users who will participate in each meeting, and the processing server is configured to cooperate with the input terminal to execute a business card registration process that registers the business card information input by each of the plurality of users in the business card database, wherein one of the one or more users who input the business card information using the input terminal is defined as a first user, the date on which the first user inputs the business card information is defined as an input date, and the business card information input by the first user on the input date is defined as a first user. the processing server defines one or more of the business cards entered as first business cards, defines the number of the first business cards as a first input number, and acquires from the schedule database the meeting information of the meeting attended by the first user on the input date; identifies second users who are other users who attended the same meeting as the first user based on the acquired meeting information; performs a meeting number estimation process to estimate a meeting number, which is the number of participants in the meeting other than the first user, based on a second input number, which is the number of business cards entered by the second user on the input date; if the first input number is equal to or less than a determination threshold determined based on the meeting number, performs a business card exchange date registration process to register the input date in the business card database as the business card exchange date of the first business card; and if the first input number is greater than the determination threshold, performs a business card exchange date reservation process to register the business card exchange date of the first business card in the business card database as unknown, or to leave the business card exchange date of the first business card as unregistered.

[0087] According to this configuration, when business card information for a number of business cards that is too large compared to the number of people at the meeting estimated based on the meeting information is input, the input date of such business card information may not be the actual date of the business card exchange, and the business card exchange date can be set as unknown or unregistered. Therefore, when business card information for business cards exchanged in the past is input, and the number of business cards is too large compared to the number of people at the meeting, the possibility of registering such input date as the business card exchange date as erroneous information can be reduced. This increases the possibility that the actual date of the business card exchange or a date close to that date will be registered as the business card exchange date.

[0088] In one aspect, the processing server estimates the number of people attending the meeting to be the same as the second input number in the meeting number estimation process.

[0089] According to this configuration, the number of people meeting is estimated to be the same as the second input number, which increases the likelihood that the day on which the first user actually exchanged business cards or a day close to that day will be registered as the business card exchange date.

[0090] In one embodiment, in the meeting number estimation process, if there are multiple second users and the number of second input sheets for each user does not match, the processing server estimates the number of people meeting based on the average value of the number of second input sheets or the maximum value of the number of second input sheets.

[0091] According to this configuration, the number of people meeting is estimated based on the average value of the number of second input sheets or the maximum value of the number of second input sheets, so even if there are multiple second users, the likelihood that the day on which the first user actually exchanged business cards or a day close to that day will be registered as the business card exchange date can be increased.

[0092] In one embodiment, in the meeting number estimation process, if the second user attended another meeting on the input date, the processing server estimates the number of people attending the meeting based on the second input number and the third input number, which is the number of business cards entered on the input date by a third user, another user who attended the other meeting.

[0093] According to this configuration, the number of people attending the meeting is estimated based on the second input number and the third input number, so even if the second user attends multiple meetings on the input date, the likelihood that the day on which the first user actually exchanged business cards or a day close to that day will be registered as the business card exchange date is increased.

[0094] In one aspect, when the meeting information includes number-of-persons information that can identify the number of people attending the meeting, the processing server executes the meeting number-of-persons estimation process using the number-of-persons information.

[0095] According to this configuration, if the meeting information includes number of people information that can identify the number of people attending the meeting, the number of people attending the meeting estimation process is performed using that number of people information, thereby further increasing the possibility that the day on which business cards were actually exchanged or a day close to that day will be registered as the business card exchange date.

[0096] In one embodiment, the determination threshold is set to a value obtained by multiplying the number of people meeting by a predetermined coefficient.

[0097] According to this configuration, when a number of business cards that is significantly different from the number of people the first user met on the input date is input, the business card exchange date of the first business card input on that input date is registered in the business card database as unknown, or the business card exchange date of the first business card is not registered. Therefore, for example, when business cards that have been exchanged in the past are input all at once, the possibility of registering incorrect information in the business card database as the business card exchange date can be reduced.

[0098] In one aspect, the processing server executes an alert process for issuing an alert to the first user when the business card exchange date reservation process is executed.

[0099] According to this configuration, it is possible to increase the likelihood that the first user who has been alerted will enter the actual business card exchange date, thereby increasing the likelihood that the actual business card exchange date or a date close to that date will be registered as the business card exchange date.

[0100] In one aspect, a business card management program is provided for a business card management system including a business card database storing business card information for each of a plurality of business cards, a schedule database storing meeting information for each of a plurality of users, a processing server connected to the business card database and the schedule database, and an input terminal communicably connected to the processing server and configured to accept input of the business card information for one or more of the business cards by one or more of the users. The business card management program causes a computer to realize the business card management function of the processing server, wherein the meeting information includes identifying information that can identify one or more of the users participating in each meeting, one of the one or more users who input the business card information via the input terminal is designated as a first user, the date on which the business card information was input by the first user is designated as an input date, the one or more business cards input by the first user on the input date are designated as first business cards, and the number of the first business cards is designated as a first input number, and the processing server receives the input information. The terminal cooperates with the terminal to execute a business card registration process that registers the business card information entered by each of the multiple users in the business card database, acquires from the schedule database the meeting information of the meeting attended by the first user on the input date, identifies a second user who is another user who attended the same meeting as the first user based on the acquired meeting information, and executes a meeting number estimation process that estimates a meeting number, which is the number of participants in the meeting other than the first user, based on a second input number that is the number of business cards entered by the second user on the input date, and if the first input number is equal to or less than a judgment threshold determined based on the meeting number, executes a business card exchange date registration process that registers the input date in the business card database as the business card exchange date of the first business card, and if the first input number is greater than the judgment threshold, registers the business card exchange date of the first business card in the business card database as unknown, or executes a business card exchange date suspension process that leaves the business card exchange date of the first business card unregistered.

[0101] According to this configuration, when business card information for a number of business cards that is too large compared to the number of people at the meeting estimated based on the meeting information is input, the input date of such business card information may not be the actual date of the business card exchange, and the business card exchange date can be set as unknown or unregistered. Therefore, when business card information for business cards exchanged in the past is input, and the number of business cards is too large compared to the number of people at the meeting, the possibility of registering such input date as the business card exchange date as erroneous information can be reduced. This increases the possibility that the actual date of the business card exchange or a date close to that date will be registered as the business card exchange date.

[0102] The business card management system and business card management program according to the present disclosure may achieve at least one of the above-described effects. The technical features of the business card management system according to the present disclosure may also be applied to a business card management method. [Explanation of symbols]

[0103] 10: Business card management system 11: Business card 11a: First business card 12: User 12a: First user 12b: Second user 12c: Third user 15: Processing server 20: Input terminal 31: Business card database 31d: Business card information 34: Schedule database 34d: Meeting Information D1: Input date Da: Business card exchange date Na: First input number Nb: Number of second inputs Nc: Third input number Nmax: Judgment threshold S11: Business card registration process S13: Meeting number estimation process S15: Business card exchange date registration process S16: Business card exchange date pending processing S17: Attention processing

Claims

1. a business card database in which business card information for each of a plurality of business cards is stored; a schedule database storing meeting information for each of a plurality of users; a processing server connected to the business card database and the schedule database; an input terminal connected to the processing server so as to be able to communicate with the processing server and configured to accept input of the business card information of one or more of the business cards by one or more of the users; A business card management system comprising: The meeting information includes identification information that can identify one or more of the users participating in each meeting; the processing server is configured to execute a business card registration process in cooperation with the input terminal to register the business card information input by each of the plurality of users in the business card database; One of the one or more users who input the business card information using the input terminal is defined as a first user, the day on which the business card information is input by the first user is defined as an input date, the one or more business cards input by the first user on the input date are defined as first business cards, and the number of the first business cards is defined as a first input number, The processing server acquires from the schedule database the meeting information of the meeting attended by the first user on the input date, identifies a second user who is another user who attended the same meeting as the first user based on the acquired meeting information, and executes a meeting number estimation process to estimate a meeting number, which is the number of participants in the meeting other than the first user, based on a second input number, which is the number of business cards input by the second user on the input date; If the first input number is equal to or less than a threshold value determined based on the number of people meeting, a business card exchange date registration process is executed to register the input date in the business card database as the business card exchange date of the first business card; A business card management system that, if the first input number is greater than the judgment threshold, registers the business card exchange date of the first business card as unknown in the business card database, or performs a business card exchange date reservation process that leaves the business card exchange date of the first business card unregistered.

2. The business card management system according to claim 1 , wherein the processing server estimates the number of people meeting to be the same as the second input number in the meeting number estimation process.

3. The business card management system of claim 1, wherein, in the meeting number estimation process, when there are multiple second users and the respective second input numbers do not match, the processing server estimates the number of people meeting based on the average value of the second input numbers or the maximum value of the second input numbers.

4. The business card management system of claim 1, wherein, in the meeting number estimation process, if the second user attended another meeting on the input date, the processing server estimates the number of people attending the meeting based on the second input number and the third input number, which is the number of business cards entered on the input date by a third user, another user who attended the other meeting.

5. The business card management system according to claim 1 , wherein, when the meeting information includes number-of-persons information that can identify the number of people attending the meeting, the processing server executes the meeting number estimation process using the number-of-persons information.

6. The business card management system according to claim 1 , wherein the determination threshold is set to a value obtained by multiplying the number of people to be in a meeting by a predetermined coefficient.

7. The business card management system according to claim 1 , wherein the processing server executes an alert process for issuing an alert to the first user when the business card exchange date reservation process is executed.

8. In a business card management system comprising a business card database in which business card information for each of a plurality of business cards is stored, a schedule database in which meeting information for each of a plurality of users is stored, a processing server connected to the business card database and the schedule database, and an input terminal connected to the processing server so as to be able to communicate with the processing server and which accepts input of the business card information for one or more of the business cards by one or more of the users, a business card management program that causes a computer to realize the business card management function of the processing server, The meeting information includes identification information that can identify one or more of the users participating in each meeting; One of the one or more users who input the business card information using the input terminal is defined as a first user, the day on which the business card information is input by the first user is defined as an input date, the one or more business cards input by the first user on the input date are defined as first business cards, and the number of the first business cards is defined as a first input number, The processing server, executes a business card registration process in cooperation with the input terminal to register the business card information input by each of the plurality of users in the business card database; acquires from the schedule database the meeting information of the meeting attended by the first user on the input date, identifies a second user who is another user who attended the same meeting as the first user based on the acquired meeting information, and executes a meeting number estimation process to estimate a meeting number, which is the number of participants in the meeting other than the first user, based on a second input number, which is the number of business cards input by the second user on the input date; If the first input number is equal to or less than a threshold value determined based on the number of people meeting, a business card exchange date registration process is executed to register the input date in the business card database as the business card exchange date of the first business card; A business card management program that, if the first input number is greater than the judgment threshold, registers the business card exchange date of the first business card as unknown in the business card database, or executes a business card exchange date reservation process that sets the business card exchange date of the first business card as unregistered.

Images