Matching system, recruiter device and method

Abstract

A matching system (1) for matching a recruiter with a recruiter for recruiting a recruitment in a case where a holder of an asset becomes the recruiter and a transfer destination or utilization destination of the asset is recruited, the matching system (1) being provided with: a recruiter device (200) operated by the recruiter; a first recruiter device (300A) operated by the first recruiter; and a computing device (100) that communicates with the recruiter device and the first recruiter device and is capable of accessing the database, in which the recruiter device (200) transmits to the computing device (100) asset information indicating the subject of the asset and public information indicating the public range of the asset information, the computing device (100) registers the asset information together with the public information in the database (120), and the computing device (100) communicates with the recruiter device (200) and the first recruiter device (200). The computing device (100) determines, from among the asset information registered in the database (120), the asset information permitted to be published to the first recruiter on the basis of the publication information, and provides the asset information permitted to be published to the first recruiter device (300A) with the asset information permitted to be published to the first recruiter.

Description

Technical Field

[0001] The present disclosure relates to a matching system, a recruiter device, and a method for matching a recruiter with an applicant who applies for recruitment when the holder of an asset becomes a recruiter and recruits a transfer destination or a utilization destination of the asset. Background Art

[0002] Conventionally, a system for brokering the sale and purchase of items for individuals has been known. For example, Patent Document 1 discloses a system that includes a personal terminal of a seller, a personal terminal of a buyer, and a network server of a broker. The broker manages the personal information of the seller and the buyer and brokers personal transactions without notifying the seller and the buyer of the personal information.

[0003] According to the system described in Patent Document 1, it is possible to smoothly match a person who wants to sell and dispose of unnecessary items with a person who wants to buy desired items.

[0004] Prior Art Documents

[0005] Patent Documents

[0006] Patent Document 1: Japanese Patent Application Laid-Open No. 2002-74055 Summary of the Invention

[0007] Problems to be Solved by the Invention

[0008] Regarding the demand for disposing of or making flexible use of surplus assets such as unwanted items, such a demand exists not only among individuals but also among groups such as enterprises. Groups such as enterprises can act as recruiters for transfer destinations or utilization destinations of assets and recruit applicants who apply for the recruitment.

[0009] However, it goes without saying that a recruiter needs to prevent a competing company from becoming a transfer destination of surplus assets, and also needs to prevent the content of the surplus assets to be transferred from being known to a competing company. This is because a competing company may learn secret information and business trends from the content of the surplus assets to be transferred. Therefore, when matching recruiters and applicants belonging to groups such as enterprises, it is necessary to consider the interests of the recruiter and the applicant.

[0010] The present disclosure has been made to solve the above-described problems, and an object thereof is to be able to select an appropriate applicant while considering the interests of a recruiter for a transfer destination or a utilization destination of a recruited asset and the applicant.

[0011] Means for Solving the Problems

[0012] The matching system according to the first aspect of the present disclosure is used to match a recruiter with an applicant who applies for the recruitment when the holder of an asset becomes a recruiter and recruits a transfer destination or utilization destination of the asset. The matching system includes: a recruiter device operated by the recruiter; a first applicant device operated by a first applicant; and a computing device that communicates with the recruiter device and the first applicant device and can access a database. The recruiter device sends asset information representing the object of the asset and disclosure information representing the disclosure scope of the asset information to the computing device. The computing device registers the asset information and the disclosure information in the database together, and the computing device determines, based on the disclosure information, the asset information registered in the database that is allowed to be disclosed to the first applicant, and provides the asset information allowed to be disclosed to the first applicant to the first applicant device.

[0013] The recruiter device according to the second aspect of the present disclosure is a recruiter device operated by a recruiter when the holder of an asset becomes a recruiter and recruits a transfer destination or utilization destination of the asset. The recruiter device communicates with a computing device, and the computing device is used to match the recruiter with an applicant who applies for the recruitment. The recruiter device includes: an interface for accepting an operation of inputting asset information representing the object of the asset and disclosure information representing the disclosure scope of the asset information; and a processor that sends the asset information and the disclosure information accepted by the interface to the computing device. The disclosure information includes information for instructing the computing device to allow the asset information to be disclosed to the first applicant and prohibit the asset information from being disclosed to a second applicant different from the first applicant.

[0014] The method according to the third aspect of the present disclosure is used to match a recruiter with an applicant who applies for the recruitment when the holder of an asset becomes a recruiter and recruits a transfer destination or utilization destination of the asset. The method includes the following steps: communicating with a recruiter device operated by the recruiter and a first applicant device operated by the first applicant; receiving from the recruiter device operated by the recruiter asset information representing the object of the asset and disclosure information representing the disclosure scope of the asset information; registering the asset information and the disclosure information in the database together; and determining, based on the disclosure information, the asset information registered in the database that is allowed to be disclosed to the first applicant, and providing the asset information allowed to be disclosed to the first applicant to the first applicant device.

[0015] Effects of the Invention

[0016] According to the present disclosure, it is possible to select an appropriate applicant by considering the interests between the group of recruiters who recruit the transfer destination or utilization destination of the asset and the group of applicants. Brief Description of the Drawings

[0017] Figure 1 It is a block diagram showing an overview of the matching system.

[0018] Figure 2 It is a block diagram showing the structures of the shared server, the recruiter device, and the applicant device.

[0019] Figure 3 It is a diagram showing an example of the enterprise database.

[0020] Figure 4 It is a diagram showing an example of the member database.

[0021] Figure 5 It is a diagram showing an example of the community database.

[0022] Figure 6 It is a diagram showing an example of the recruitment case database.

[0023] Figure 7 It is a diagram showing an example of the evaluation input database.

[0024] Figure 8 It is a diagram showing an example of the evaluation summary database.

[0025] Figure 9 It is a diagram for explaining the functions of the shared server, the recruiter device, and the applicant device.

[0026] Figure 10 It is a diagram for explaining the functions of the shared server, the recruiter device, and the applicant device.

[0027] Figure 11 It is a diagram for explaining the functions of the shared server, the recruiter device, and the applicant device.

[0028] Figure 12 It is a diagram for further explaining the functions of the applicant device.

[0029] Figure 13 It is a diagram for explaining the process of registering a recruitment case in the recruitment case database.

[0030] Figure 14 It is a diagram for explaining the process of retrieving a recruitment case from the database.

[0031] Figure 15 It is a diagram for explaining the process of registering an evaluation of an applicant in the database.

[0032] Figure 16 It is a diagram for explaining the process of registering an evaluation of a recruiter in the database.

[0033] Figure 17This is a diagram for explaining the process of displaying the evaluation of applicants and the search results of members on a monitor.

[0034] Figure 18 This is a diagram for explaining the process of displaying the evaluation of recruiters and the search results of members on a monitor.

[0035] Figure 19 This is a diagram for explaining the browsable range of the evaluation summary database.

[0036] Figure 20 This is a diagram showing an example of setting the disclosure range according to the disclosure level.

[0037] Figure 21 This is a diagram showing the details of the asset content included in the recruitment case database.

[0038] Figure 22 This is a diagram showing an example of the profile database.

[0039] Figure 23 This is a diagram showing an example of the in-company terminology database.

[0040] Figure 24 This is a flowchart showing the processing procedure related to the indexing function of the matching system.

[0041] Figure 25 This is a flowchart showing the processing procedure of the in-company terminology registration department.

[0042] Figure 26 This is a flowchart showing the processing procedure of the case registration department.

[0043] Figure 27 This is a flowchart showing the processing procedure for displaying the meaning of in-company terminology on the screen according to the operations of applicants.

[0044] Figure 28 This is a diagram showing an example of the recruitment case database related to Modification Example 1.

[0045] Figure 29 This is a diagram related to Modification Example 1 for explaining the process of registering recruitment cases into the recruitment case database.

[0046] Figure 30 This is a flowchart showing the processing procedure of the first determination process related to Modification Example 1.

[0047] Figure 31 This is a flowchart showing the processing procedure of the second determination process related to Modification Example 1.

[0048] Figure 32 This is a flowchart showing the processing procedure of the third determination process related to Modification Example 1.

[0049] Figure 33 It is a diagram showing the structure of the matching system related to Modification 2.

[0050] Figure 34 It is a diagram showing an example (Modification 3) of applying Kerberos authentication to the matching system. Detailed Description of the Invention

[0051] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In addition, the same or corresponding parts in the drawings are denoted by the same reference numerals, and their description will not be repeated.

[0052] [Background of Proposing Matching System 1]

[0053] Figure 1 It is a block diagram showing an overview of the matching system 1 according to the present embodiment.

[0054] Hereinafter, in the matching system 1, the remaining assets that are being recruited and transferred to the counterparty or used by the counterparty are sometimes referred to as "recruitment cases", the people who provide the recruitment cases and those who may provide the recruitment cases are sometimes referred to as "recruiters", and the people who apply for the recruiters' recruitment and those who may apply for the recruiters' recruitment are sometimes referred to as applicants. The people who are permitted to transfer or use the remaining assets related to the recruitment case according to the recruitment content after obtaining the consent of the recruiter. In this way, the people who are permitted to apply for the recruitment case after obtaining the consent of the recruiter are sometimes referred to as the "recipients" of the recruitment case.

[0055] In the case where a transaction related to a recruitment case is established, the applicant is equivalent to the "assignee", and the recruiter who transfers the remaining assets to the "assignee" is equivalent to the "assignor". However, hereinafter, they are sometimes referred to as "applicants" including the "assignee", and sometimes referred to as "recruiters" including the "assignor".

[0056] First, the background of proposing the matching system 1 in the present embodiment will be described. A system for mediating the sale and purchase of items for individuals is well known. Everyone can use this system to dispose of unwanted items in exchange for consideration.

[0057] Companies also have a need to dispose of remaining assets such as items that have become unnecessary. Companies can profit from the remaining assets by selling or lending them instead of amortizing or scrapping them. However, when companies are looking for transaction parties for the remaining assets, they need to pay attention to the following aspects that do not pose a problem in the scenario of item trading between individuals.

[0058] [Possibility of Secret Information Leakage]

[0059] For example, when a company wants to lend or sell surplus assets such as dormant patents, plans, and ideas, it is necessary to avoid having competitor companies as the counterparties of the surplus assets. Needless to say, it is also necessary to prevent the content of the surplus assets to be lent or sold from being known to competitor companies. This is because competitor companies may learn about confidential information and business trends through the content of the surplus assets to be lent or sold. When a company wants to lend or sell surplus assets such as facilities and spare parts, it should also avoid the information of the surplus assets from being known to competitor companies. This is because competitor companies may infer future business trends from the fact that facilities, etc. are scheduled to be sold.

[0060] In addition, companies should also pay full attention to the background of the counterparty to avoid a decline in their own creditworthiness.

[0061] Therefore, when matching recruiters and applicants belonging to respective companies, it is necessary to consider the group of recruiters and the interests between the recruiting company and the applying company.

[0062] However, in the previous personal trading intermediation system, the interests between the recruiting company and the applying company were not considered. Therefore, when the personal trading intermediation system is adopted in the scenario of inter-company transactions, there are enterprise risks and personal risks. For example, confidential information may be leaked to competing companies through the assets exhibited by an employee of a certain company. In addition, in the previous personal trading intermediation system, managers could not confirm that employees did not sell the assets of their own company to competing companies.

[0063] [Possibility of not obtaining accurate information related to recruiters and applicants]

[0064] Surplus assets are registered by recruiters in the matching system as recruitment cases for trading targets. Those who hope to receive the transfer of surplus assets apply as applicants for the recruitment cases. Applicants will refer to the content of the surplus assets, the amount of the surplus assets, etc. to select satisfactory cases.

[0065] However, among recruiters, there may be those who frequently change the amount of surplus assets and those who register inferior surplus assets. As an applicant, one would want to avoid applying for recruitment cases from such recruiters. On the contrary, there are also recruiters who offer high-quality surplus assets at a reasonable price. As an applicant, one would want to apply for the cases recruited by such recruiters as much as possible.

[0066] In addition, among applicants, there may be those who have problems with paying the price of surplus assets and those who make unreasonable price reduction requests. As a recruiter, one would want to avoid such people and conduct transactions with honest applicants.

[0067] Therefore, it is desirable to widely share the evaluations of recruiters and applicants in the crowdsourcing system.

[0068] However, the person in charge of a certain enterprise (recruiter or applicant) may be overly considerate of the person in charge of another enterprise (recruiter or applicant) being evaluated and input a higher evaluation into the system than the original evaluation. In addition, the person in charge of a certain enterprise may avoid giving a lower evaluation to the person in charge of another enterprise for fear of the possibility of deterioration of the relationship between enterprises. Also, the person in the position of making an evaluation may not feel the benefits of making an evaluation, and thus input an evaluation that is far from the original evaluation into the system. When considering these possibilities, the reliability of the evaluations provided by the system may decrease. In this case, even if the evaluations of recruiters and applicants are shared in the system, users cannot flexibly use this evaluation as reference data when trading with recruiters or applicants.

[0069] [Possibility of company-internal terms hindering communication]

[0070] In an enterprise, sometimes company-internal terms unique to that enterprise become widespread. Regarding company-internal terms, although people in the enterprise where the term is widespread can understand it, people who do not belong to the enterprise where the term is widespread may not be able to understand it. Or, a company-internal term may be understood to have a specific meaning among people in the enterprise where the term is widespread, but for people who do not belong to the enterprise where the term is widespread, it may be understood to have a meaning different from that specific meaning.

[0071] In an article explaining the residual assets, company-internal terms may be used. When the enterprise to which the recruiter belongs is different from the enterprise to which the applicant belongs, the applicant may not be able to correctly understand the meaning of the company-internal terms used by the recruiter in the explanation of the residual assets. The applicant may apply for the recruitment case without correctly understanding the meaning of the company-internal terms used by the recruiter in the explanation of the residual assets. As a result, disputes may arise between the recruiter and the applicant.

[0072] In the negotiation occasion between the recruiter and the applicant, it is possible to use company-internal terms. When the enterprise to which the recruiter belongs is different from the enterprise to which the applicant belongs, the applicant may not be able to correctly understand the meaning of the company-internal terms mentioned by the recruiter. Similarly, the recruiter may not be able to correctly understand the meaning of the company-internal terms mentioned by the applicant.

[0073] If the in-company term mentioned by one of the recruiter and the applicant is an unfamiliar in-company term, the other party can understand the meaning of the in-company term by asking the speaker about the meaning of the term. However, when there is a difference in the understanding of the meaning of an in-company term between the recruiter and the applicant, the negotiation will proceed with the cognitive bias generated between the two parties remaining uncorrected. As a result, disputes may arise between the recruiter and the applicant.

[0074] Regarding terms similar to in-company terms, there is room for terms that are used with unique meanings not only in enterprises but also in non-profit organizations. Whether it is a for-profit organization or a non-profit organization, an organization is divided into multiple units such as departments and sections, and it is possible that terms used with unique meanings are popularized in each unit. Or, such terms may be popularized in a community formed by aggregating multiple enterprises and other groups. Therefore, when the recruiter and the applicant belong to different groups, units, and communities, differences in the perception of terms may lead to the above-mentioned disputes.

[0075] In the present embodiment, "internal terms" include not only "in-company terms" used in profit-making organizations such as enterprises and units within such profit-making organizations, but also "terms similar to in-company terms" used in non-profit organizations, communities, and units within them. Hereinafter, as an example of "internal terms", "in-company terms" targeting enterprises will be cited to explain the present embodiment.

[0076] In the present embodiment, a matching system 1 described in detail below is proposed for the purpose of solving at least one of the above various problems existing in the conventional intermediary system.

[0077] [Overall Structure]

[0078] Refer to Figure 1 to explain the schematic structure of the matching system 1. The matching system 1 includes a shared server 100, recruiter devices 200A, 200B, 200C ···, and applicant devices 300A, 300B, 300C ···.

[0079] The shared server 100 provides a matching service that matches the transfer or utilization of surplus assets between enterprises to a large number of enterprises. In Figure 1 , as examples of enterprises using the matching service, enterprises A, B, C ··· are shown. Enterprises A, B, C ··· are registered as enterprise members of the matching system 1. Those among the employees of enterprises A, B, C ··· who use the matching system 1 are also individually registered as members of the matching system 1.

[0080] Companies A, B, C... have various surplus assets. The surplus assets that are the processing targets of the matching system 1 are hardware assets such as facilities and spare parts, as well as software assets such as dormant patents, plans, and ideas.

[0081] Companies A, B, C... can exhibit various surplus assets in the matching system 1. Companies A, B, C... can also exhibit assets that are not necessarily "surplus" in the matching system 1. Hereinafter, the exhibition targets exhibited to the matching system 1 will sometimes be referred to as "assets" in a broad sense including "surplus assets".

[0082] In the matching system 1, the applicants of Company A can also apply as assignees for the assets exhibited by Company A. For example, in the matching system 1, for the assets exhibited by Department X of Company A, people belonging to a different Department Y of Company A are also allowed to apply as its assignees.

[0083] The matching system 1 not only processes recruitment cases targeted at transfer to applicants, but also processes recruitment cases targeted at allowing applicants to use the assets while maintaining the ownership of the assets on the recruiter side. For example, vacation facilities and meeting rooms are equivalent to such recruitment cases. A company with a training plan can also exhibit the right to use the training plan as a recruitment case in the matching system 1. In this case, a recruitment case allowing applicants to use the training plan is registered in the matching system 1.

[0084] In the case where a transaction related to such a recruitment case is established, the applicant is equivalent to the "user", and the recruiter who transfers the assets to the "user" is equivalent to the "licensor of use", but hereinafter, sometimes including the "user" is referred to as the "applicant", and sometimes including the "licensor of use" is referred to as the "recruiter".

[0085] A database 120 required for the matching service is built in the shared server 100. The database 120 includes various databases registering information required for providing the matching service. For example, information on members and recruitment cases is registered in the database 120. The shared server 100 is managed and operated by a company different from the company using the matching service. The shared server 100 can also be managed and operated by any company using the matching service.

[0086] The recruiter device 200A is operated by the manager of Company A. The recruiter device 200B is operated by the manager of Company B. The recruiter device 200C is operated by the manager of Company C. Hereinafter, the recruiter devices 200A, 200B, 200C... will sometimes be collectively referred to as the "recruiter device 200".

[0087] The applicant device 300A is operated by the applicants of Company A. The applicant device 300B is operated by the applicants of Company B. The applicant device 300C is operated by the applicants of Company C. Sometimes, the applicant devices 300A, 300B, 300C... are collectively referred to as the "applicant device 300" below. In Figure 1 In the figure, two applicants are drawn for each company, but the number of applicants is not limited to this. There may be more applicants in each company, or there may be only one applicant in a certain company. The shared server 100 may also accept people who do not belong to a company as applicants.

[0088] The managers of Company A, Company B, Company C... act as recruiters. Therefore, sometimes the managers of each company are referred to as "recruiters" below. A recruiter can also be regarded as an applicant for the cases recruited by other recruiters. In this case, the recruiter device 200 functions as an applicant device 300. In the present disclosure, when the manager of a company is regarded as a recruiter, the device used by the manager in the use of the matching service is called the recruiter device 200.

[0089] The manager of Company A can be either one person or multiple people. When configuring a manager for Company A, each manager can hold a recruiter device 200, or multiple people can share one recruiter device 200. The same applies to Company B, Company C...

[0090] The shared server 100 and the recruiter device 200 are configured to be able to communicate via the Internet 50, which is an example of a communication line network. The shared server 100 and the applicant device 300 are configured to be able to communicate via the Internet 50.

[0091] When the shared server 100 accepts an access from the recruiter device 200, it requires a login accompanied by the input of a member ID and a password. Similarly, when the shared server 100 accepts an access from the applicant device 300, it requires a login accompanied by the input of a member ID and a password. The shared server 100 determines each recruiter and applicant based on the member ID notified at the time of login.

[0092] The recruiter device 200 accepts various operations of the recruiter. For example, the recruiter device 200 accepts operations for inputting recruitment cases and operations for retrieving members of the matching service, etc.

[0093] The recruiter device 200 communicates with the shared server 100 according to each operation on the recruiter device 200. The shared server 100 registers the recruitment case in the database 120 according to the operation for inputting the recruitment case, and provides the information of the member to the recruiter device 200 according to the operation for retrieving the member.

[0094] The applicant device 300 accepts various operations of the applicant. For example, the applicant device 300 accepts operations for retrieving recruitment cases and operations for applying for recruitment cases, etc.

[0095] The applicant device 300 communicates with the shared server 100 according to each operation on the applicant device 300. The shared server 100 provides an appropriate recruitment case to the applicant device 300 according to the operation for retrieving the recruitment case, and provides a notice of consent or rejection to the applicant device 300 according to the operation for applying for the recruitment case.

[0096] A recruiter belonging to a certain department of Company A can select an applicant belonging to another department of Company A as the winner of the recruitment case by using the matching system 1. A recruiter belonging to Company A can select an applicant belonging to Company B as the winner of the recruitment case by using the matching system 1.

[0097] Members using the matching system 1 access the shared server 100 as recruiters or applicants. Sometimes the members of the matching system 1 are hereinafter referred to as "users". In addition, sometimes the recruiter device 200 and the applicant device 300 operated by the members are hereinafter collectively referred to as "user devices 500".

[0098] In Figure 1 A screen 550 displayed on the user device 500 is illustrated. Various information is displayed on the screen 550. For example, a detailed description related to the asset is displayed on the screen 550. The user (applicant) views the screen 550 and checks the details of the asset presented as the recruitment case.

[0099] Company-internal terms may be included in the description of the asset displayed on the screen 550. In the case where the company to which the user viewing the screen 550 belongs is different from the company to which the user providing this information belongs, the user viewing the screen 550 may not be able to correctly understand the company-internal terms.

[0100] Therefore, the matching system 1 registers the company-internal terms of each company and their meanings in the database 120. The matching system 1 generates an index related to the company-internal terms according to the text such as the description of the asset, and links the index to the company-internal terms registered in the database 120. In this way, the matching system 1 has an indexing function.

[0101] In the case where the text displayed on the screen 550 contains company-internal terms, the user device 500 displays the company-internal terms in a display manner different from other terms. Thus, the user understands that these are company-internal terms. And the user device 500 displays the meaning meant by the company-internal terms on the screen 550 according to the user's operation (for example, a click operation on the company-internal term part).

[0102] For example, in Figure 1 on the screen 550 shown, "DX" is displayed as an example of an in-company term. "DX" is underlined to indicate that it is an in-company term. The user clicks on "DX". Then, a window explaining the meaning of the term "DX" is displayed on the screen 550. DX is an abbreviation for Digital Transformation, which generally means a transformation using digital technologies. However, depending on the enterprise, "DX" may be used as an in-company term meaning to create some new value regardless of whether digital technologies are used. In this case, the corresponding meaning of this in-company term is explained in the window on the screen 550. Thus, the user can correctly understand the meaning of "DX" intended by the other party.

[0103] Figure 2 is a block diagram showing the structures of the shared server 100, the recruiter device 200, and the applicant device 300.

[0104] [Structure of the Shared Server 100]

[0105] The shared server 100 includes a processor 101, a memory 102, a storage device 103, and a communication interface 104.

[0106] The memory 102 includes a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory, or any other suitable memory system. The memory 102 stores programs required for the arithmetic processing of the processor 101, as well as temporary data calculated during the arithmetic processing, etc.

[0107] The storage device 103 is composed of a hard disk drive, a solid state drive, etc. A database 120 is stored in the storage device 103. The database 120 includes multiple types of databases. The multiple types of databases include an enterprise database (Enterprise DB) 121, a member database (Member DB) 122, a community database (Community DB) 123, a recruitment case database (Recruitment Case DB) 124, an evaluation input database (Evaluation Input) 126, and an evaluation summary database (Evaluation Summary DB) 127. Information on the (remaining) assets of the recruitment case is registered in the recruitment case database (Recruitment Case DB) 124.

[0108] Part of these multiple types of databases may also be stored in a storage device separately provided from the shared server 100. For example, a cloud service independent of the shared server 100 may be connected to Figure 2A part of multiple types of databases shown is stored in the cloud. In this case, the sharing server 100 can access the required databases by communicating with the cloud via the Internet 50.

[0109] The processor 101 is connected to the Internet 50 via the communication interface 104 according to the program stored in the memory 102. The processor 101 is connected to the Internet 50 to communicate with the recruiter device 200 and the applicant device 300. The processor 101 accesses the database 120 and executes processes such as extracting required data, registering new data in the database 120, and updating the data registered in the database 120.

[0110] [Structure of the Recruiter Device 200]

[0111] The recruiter device 200 includes a processor 201, a memory 202, a communication interface 203, an input / output interface 204, a display 205, and an operation unit 206. The operation unit 206 is composed of a mouse, a keyboard, etc.

[0112] The memory 202 includes a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory, or any other appropriate memory system. The memory 202 stores programs required for the arithmetic processing of the processor 201, and temporary data calculated during the arithmetic processing, etc.

[0113] The processor 201 is connected to the Internet 50 via the communication interface 203 according to the program stored in the memory 202. The processor 201 is connected to the Internet 50 to communicate with the sharing server 100. The processor 201 communicates with the sharing server 100 to execute processes such as sending recruitment cases, displaying information of members as applicants on the display 205, processes for the recruiter to agree or reject an applicant as the winner of a recruitment case, and processes for sending the content of the evaluation of the applicant (assignee) input by the recruiter (assignor) to the sharing server 100.

[0114] The information input through the operation of the operation unit 206 is notified to the processor 201 via the input / output interface 204.

[0115] [Structure of the Applicant Device 300]

[0116] The applicant device 300 includes a processor 301, a memory 302, a communication interface 303, an input / output interface 304, a display 305, and an operation unit 306. The operation unit 306 is composed of a mouse, a keyboard, etc.

[0117] The memory 302 includes a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory, or any other suitable memory system. The memory 302 stores programs required for the arithmetic processing of the processor 301, as well as temporary data calculated during the arithmetic processing, etc.

[0118] The processor 301 connects to the Internet 50 via the communication interface 303 according to the program stored in the memory 302. The processor 301 connects to the Internet 50 to communicate with the sharing server 100. The processor 301 communicates with the sharing server 100 to execute the processing of recruitment cases, the processing of displaying the consent or rejection notice for the applied cases on the display 305, and the processing of sending the content of the evaluation input by the applicant (assignee) to the recruiter (assignor) to the sharing server 100, etc.

[0119] The information input through the operation of the operation unit 306 is notified to the processor 301 via the input / output interface 304.

[0120] [Overview of Database 120]

[0121] The overview of the database 120 is described below. Information of enterprises affiliated with the matching system 1 is registered in the enterprise database 121. Information of members using the matching system 1 is registered in the member database 122. Many members are employees of enterprises affiliated with the matching system 1.

[0122] The members registered in the member database 122 can act as recruiters or applicants by using the matching system 1. Members can also include individuals not belonging to an enterprise in addition to employees belonging to the enterprises registered in the enterprise database 121.

[0123] Information for determining enterprises belonging to a community is stored in the community database 123. A community is formed through an agreement between enterprises. Therefore, multiple communities can be formed according to the way of reaching an agreement between enterprises. The number of enterprises belonging to one community can also be set arbitrarily. A trust relationship is formed between enterprises with a community relationship within the scope determined by the way of reaching an agreement when forming the community. In the community database 123, information for determining enterprises belonging to each community is registered for each community.

[0124] Recruitment cases are registered in the recruitment case database 124. A recruitment case is an asset that is being recruited for transfer to or use by a counterparty. Employees of each enterprise can apply for recruitment cases exhibited from other departments of their own enterprise or recruitment cases exhibited from other enterprises as members of the matching system 1.

[0125] In the evaluation input database 126, information on the evaluation of applicants and information on the evaluation of recruiters are registered. By using the matching system 1, recruiters can evaluate the attitudes of applicants during the transaction period, etc., as evaluators. By using the matching system 1, applicants can evaluate the attitudes of recruiters during the transaction period, etc., as evaluators. The evaluations conducted by each evaluator are registered in the evaluation input database 126.

[0126] Evaluation summaries are registered in the evaluation summary database 127. In the evaluation summary database 127, evaluation summaries are registered for each member. The evaluation summary includes a recruiter evaluation summary and an applicant evaluation summary. The recruiter evaluation summary shows the evaluation level when a member is regarded as a recruiter. The applicant evaluation summary shows the evaluation level when a member is regarded as an applicant. The recruiter evaluation summary is created based on the evaluation of the recruiter by the applicant. The applicant evaluation summary is created based on the evaluation of the applicant by the recruiter.

[0127] Members can view the evaluation summaries. Recruiters can view the applicant evaluation summaries of each member and select appropriate members as assignees. Applicants can view the recruiter evaluation summaries of each member and apply for cases proposed by appropriate recruiters.

[0128] [Enterprise Database 121]

[0129] Figure 3 It is a diagram showing an example of the enterprise database 121. In the enterprise database 121, "enterprise ID" for identifying the enterprise, "enterprise name", and the "address" of the enterprise are registered for each enterprise.

[0130] [Member Database 122]

[0131] Figure 4 It is a diagram showing an example of the member database 122. Various information of members is registered in the member database 122. The various information of members includes "member ID" for identifying the member, "enterprise ID" of the enterprise to which the member belongs, "member name", "permissions" of the member, and the "department" to which the member belongs.

[0132] The types of member permissions include managers and applicants. Members with manager permissions are given the permission to use the matching system 1 as recruiters and applicants. Members with only applicant permissions are given the permission to use the matching system 1 as applicants, but not the permission to use the matching system 1 as recruiters. The head of a department within an enterprise is given manager permissions to manage the applications of subordinates within the department. Managers with manager permissions are given the permission to approve the applications of subordinate applicants. Thus, managers function as approvers.

[0133] [Community Database 123]

[0134] Figure 5 It is a diagram showing an example of the community database 123. Information on communities formed among enterprises is registered in the community database 123. The information on the community includes a "community ID" for identifying the community, a "community name", and an "enterprise ID list" of the enterprises belonging to the community. Each enterprise can form various communities by reaching an agreement with other enterprises. The enterprises belonging to the community can change the enterprises targeted for belonging to the community by reaching an agreement with other enterprises.

[0135] [Recruitment Case Database 124]

[0136] Figure 6 It is a diagram showing an example of the recruitment case database 124. Information on recruitment cases is registered in the recruitment case database 124. The information on the recruitment case includes a "case ID (asset ID)" for identifying the recruitment case, an "enterprise ID" of the enterprise to which the recruiter of the recruitment case belongs, a "non-disclosure enterprise ID list", a "member ID of the recruiter", a "publication level", an "asset title", an "asset content", an "asset classification", an "asset transfer amount", a "recruitment quantity", and a "transfer / use".

[0137] For example, the IDs of the enterprises that prohibit the disclosure of the recruitment case are registered in the "non-disclosure enterprise ID list". In the "publication level", any one of the three levels of "company", "within the community", and "all" is set. When the publication level is set to "all", the recruitment target also includes applicants outside the community.

[0138] In Figure 6 the right side of the recruitment case database 124, the IDs of the enterprises that can view the recruitment cases are shown. For example, for the recruitment case corresponding to the case ID = 001, the publication level is set to "company". In this case, only the members belonging to the enterprise (enterprise ID = 00A) that registered the recruitment case can view the recruitment case corresponding to the case ID = 001. In this case, it is assumed that the surplus assets of a certain department within the enterprise identified by the enterprise ID = 00A are transferred to or used by other departments.

[0139] Hereinafter, the recruitment cases corresponding to each case ID are sometimes referred to as Case 001, Case 002, Case 003, etc. using the case ID. Similarly, the communities corresponding to each community ID are sometimes referred to as Community 01, Community 02, Community 03, etc. using the community ID, and the members corresponding to each member ID are sometimes referred to as Member P1, Member P2, Member P3, etc. using the member ID. In addition, hereinafter, the companies corresponding to each company ID are sometimes referred to as Company A, Company B, Company C, etc. using a part of the company ID.

[0140] For Case 002, the disclosure level is set to "within the community". The recruiter for Case 002 is a member (member ID = P2) belonging to Company A. According to Figure 5 the community database 123 shown, the companies that have a community relationship with Company A where Case 002 is registered are Company B and Company C. Therefore, as Figure 6 shown, only the members belonging to any of Company A, Company B, and Company C can view Case 002.

[0141] The registering company and the disclosure level of the recruitment case of Case 003 are the same as those of Case 002. However, for Case 003, "00B" is registered in the "non-disclosure company ID list". Therefore, as Figure 6 shown, only the members belonging to any of Company A and Company C can view Case 003, and the members belonging to Company B are not granted the permission to view Case 003.

[0142] In the case of a recruitment case where the disclosure level is set to "all", all members can view the recruitment case in question. Figure 6 Case 005 shown is equivalent to this recruitment case. Assuming that one or more company IDs are registered in the non-disclosure company ID list of Case 005, the members of the companies belonging to these company IDs are not given the permission to view Case 005.

[0143] In the "asset title", a title is registered that can understand the outline of the assets related to the recruitment case. For example, as the asset title corresponding to Case 001, a desk drawer is registered. From Figure 6 the asset title shown, the assets that can be registered as recruitment cases are various cases such as desk drawers, patents, project plans, meeting rooms, and welfare facilities.

[0144] In the "asset content", explanatory items are registered that can understand the content of the assets related to the recruitment case in detail. In the "asset classification", classifications such as spare parts, patents, ideas, spaces, and facilities are registered. In the "asset transfer amount", the amount related to the transfer or use of the assets is registered.

[0145] In "recruitment quantity", the quantity of assets related to transfer or utilization is registered. For example, the quantity of desks with drawers corresponding to asset ID = 1 is 100.

[0146] In "transfer / utilization", information is registered for determining whether the recruitment item as the object is a recruitment case for the purpose of transfer or a recruitment case for the purpose of utilization. For example, case 001 is a recruitment case for the purpose of transfer, and 100 desks with drawers are transferred from the recruiter to the recipient of case 001 on the condition of paying the asset transfer amount.

[0147] The meeting room in case 004 is a recruitment case for the purpose of utilization, and the right to use the meeting room is granted from the recruiter to the recipient of case 004 on the condition of paying the asset transfer amount. For example, when the meeting room as the recruitment object is located in Tokyo and the location of the applicant enterprise is in Osaka, the applicant can use the meeting room when traveling to Tokyo on business by obtaining case 004.

[0148] In addition, regarding the setting of the disclosure level, various variations are considered. For example, it can also be set so that the user can control the disclosure destination of asset information by selecting specific items. More specifically, check boxes for selecting the enterprises to which asset information is to be disclosed can also be set on the screen for registering recruitment cases. Additionally, it can also be set so that by the user selecting one from pre-defined options, the user can control the associated information and functions. For example, a list for the user to select the disclosure scope of asset information from "within the company", "within the community", and "all users" can also be displayed on the screen for registering recruitment cases.

[0149] The user device 500 can also provide the user with a setting screen for setting the disclosure level to various levels. For example, on the setting screen, check boxes for the user to select the objects of disclosed cases by industry types such as "pharmaceuticals", "chemistry", "electrical equipment", "railways and buses", "food", etc. can also be displayed. And it can also be set so that by displaying the enterprise names corresponding to each industry type on the setting screen, the user can select the objects of disclosed cases by "industry type" and by "enterprise".

[0150] For example, as the enterprises corresponding to "pharmaceuticals", there are Company A, Company B, Company C, and Company D; as the enterprises corresponding to "chemistry", there are Company E, Company F, Company G, and Company H; as the enterprises corresponding to "electrical equipment", there are Company I, Company J, Company K, and Company L.

[0151] In this case, on the setting screen, it is shown that in the industry type of "pharmaceuticals", it includes "Company A" to "Company D", and check boxes corresponding to "pharmaceuticals", "Company A", "Company B", "Company C", and "Company D" are displayed. Also, on the setting screen, it is shown that in the industry type of "chemistry", it includes "Company E" to "Company H", and check boxes corresponding to "chemistry", "Company E", "Company F", "Company G", and "Company H" are displayed. Further, on the setting screen, it is shown that in the industry type of "electrical equipment", it includes "Company I" to "Company L", and check boxes corresponding to "electrical equipment", "Company I", "Company J", "Company K", and "Company L" are displayed.

[0152] For example, assume that the user checks the check boxes corresponding to "pharmaceuticals" and "chemistry" respectively, and does not check the check box corresponding to "electrical equipment". In this case, the industry type of "electrical equipment" is excluded from the objects of the disclosed cases. Also, assume that the check boxes corresponding to Company A to Company C belonging to "pharmaceuticals" and the check boxes corresponding to Company E to Company H belonging to "chemistry" are checked, but the check box corresponding to Company D belonging to "pharmaceuticals" is not checked. In this case, Company A to Company C belonging to "pharmaceuticals" and Company E to Company H belonging to "chemistry" are regarded as the objects of the disclosed cases for processing, but Company D belonging to "pharmaceuticals" is excluded from the objects of the disclosed cases.

[0153] [Evaluation Input Database 126]

[0154] Figure 7 It is a figure showing an example of the evaluation input database 126. Information on the evaluation of the evaluated person is registered in the evaluation input database 126. The evaluation information includes the evaluation object, the member ID of the evaluated person, the member ID of the evaluator, and the evaluation result.

[0155] The evaluation input database 126 includes a recruiter evaluation unit 126A and an applicant evaluation unit 126B. Information on the evaluation of the recruiter (assignor) is registered in the recruiter evaluation unit 126A. Information on the evaluation of the applicant (assignee) is registered in the applicant evaluation unit 126B.

[0156] In the recruiter evaluation unit 126A, the recruiter (assignor) is equivalent to the evaluation object (evaluated person), and the applicant who applied for the recruitment case of the evaluation object and obtained the applicant of the recruitment case is equivalent to the evaluator. In the recruiter evaluation unit 126A, the evaluation of the evaluated person is registered by the evaluator. In Figure 7 an example is shown where the member P1 and P2 equivalent to the evaluated person received evaluations from the evaluator members. In particular, in Figure 7An example is shown in which member P1 has received evaluations from each of members P5, P7, P11, and P12. The evaluation results (evaluation values) are represented by numerical values with 10 as the maximum value and 0 as the minimum value.

[0157] In the applicant evaluation unit 126B, the applicant (assignee) of the recruitment case is equivalent to the evaluation object (evaluated person), and the recruiter (assignor) of the case is equivalent to the evaluator. In the applicant evaluation unit 126B, the evaluations of the evaluated person are registered by evaluator. In Figure 7 An example is shown in which member P7, who is equivalent to the evaluated person, has received evaluations from each of members P1, P2, and P3, who are equivalent to the evaluators. In addition, in Figure 7 Examples of the evaluation results in the applicant evaluation unit 126B are omitted, but various evaluation results are registered here in the same way as in the recruiter evaluation unit 126A.

[0158] When the applicant (assignee) completes the transaction with the recruiter (assignor), the applicant uses the applicant device 300 as an evaluator to evaluate the recruiter as the evaluated person. The evaluation results of the evaluator are registered in the evaluation input database 126. When a certain applicant obtains another recruitment case from a recruiter who has previously obtained a recruitment case, the applicant evaluates the recruiter again. In this case, the average value of the previous evaluation results and the subsequent evaluation results is registered in the evaluation input database 126.

[0159] When the recruiter (assignor) completes the transaction with the applicant (assignee), the recruiter uses the recruiter device 200 as an evaluator to evaluate the applicant as the evaluated person. The evaluation results of the evaluator are registered in the evaluation input database 126. When a certain recruiter transfers other assets to an applicant who has previously conducted an asset-related transaction again, the recruiter evaluates the applicant again. In this case, the average value of the previous evaluation results and the subsequent evaluation results is registered in the evaluation input database 126.

[0160] Therefore, the average value of the evaluations of the evaluated person by each evaluator is reflected in the evaluation results registered in the evaluation input database 126. In addition, instead of the average value, weighted average values, deviation values, etc. calculated based on the number of evaluations can also be used. In the evaluation input database 126, the evaluation results of each case ID can also be registered.

[0161] [Evaluation Summary Database 127]

[0162] Figure 8It is a diagram showing an example of the evaluation summary database 127. Information on evaluations by department for the evaluated person is registered in the evaluation summary database 127. The information on evaluations by organization includes the evaluation object, the member ID of the evaluated person, the ID of the company to which the evaluated person belongs, the ID of the company to which the evaluator belongs, the department to which the evaluator belongs, and the evaluation summary.

[0163] The evaluation summary database 127 includes a recruiter evaluation summary section 127A and an applicant evaluation summary section 127B. In the recruiter evaluation summary section 127A, the recruiter (assignor) corresponds to the evaluation object (evaluated person). In the applicant evaluation summary section 127B, the applicant (assignee) corresponds to the evaluation object (evaluated person). In the evaluation summary database 127, evaluation summaries for the evaluation object are registered by department.

[0164] The evaluation summary is calculated based on the statistical results of the evaluation input database 126. The categories of departments include each department such as the "Systems Department" and "Planning Department" belonging to the company, and "All" representing the entire company. The evaluation summary is calculated by such "departments".

[0165] In Figure 8 as an example of the recruiter evaluation summary section 127A, an example where member P1 corresponds to the evaluated person is shown. The company ID of the evaluated person is "00A". Therefore, member P1 belongs to company A. In Figure 8 data set 1271 represents the evaluation of member P1 regarded as a recruiter by company B, and data set 1272 represents the evaluation of member P1 regarded as a recruiter by company C.

[0166] Referring to data set 1271, the evaluation of company B is classified into an evaluation of the entire company, an evaluation of the Systems Department within company B, and an evaluation of the Planning Department within company B. The average value of the evaluations corresponding to each classified category is registered in the evaluation summary.

[0167] For example, as the evaluation summary corresponding to the entire company B, the average value of the evaluation results of the members of company B who evaluated member P1 regarded as a recruiter is registered. In Figure 8 this value is set to "4.75". As the evaluation summary corresponding to the Systems Department, the average value of the evaluation results of the members belonging to the Systems Department among the members of company B who evaluated member P1 regarded as a recruiter is registered. In Figure 8 this value is set to "4.0". As the evaluation summary corresponding to the Planning Department, the average value of the evaluation results of the members belonging to the Planning Department among the members of company B who evaluated member P1 regarded as a recruiter is registered. In Figure 8 this value is set to "5.0".

[0168] For the data group 1272, similar to the data group 1271, the evaluation of Company C is classified into the evaluation of the entire company and the evaluation by each department within Company C. The data groups 1271 and 1272 are data with the recruiter as the evaluation object. Therefore, the evaluation summaries registered in the data groups 1271 and 1272 are recruiter evaluation summaries.

[0169] The recruiter evaluation summary section 127A has been described in detail above. Next, the applicant evaluation summary section 127B will be described. In Figure 8 , as the applicant evaluation summary section 127B, an example where member P7 is the evaluated person is shown. The company ID of the evaluated person is "00C". Therefore, member P7 belongs to Company C. In the applicant evaluation summary section 127B, the evaluations of member P7 regarded as an applicant are registered by department.

[0170] The applicant evaluation summary section 127B has the same structure as the recruiter evaluation summary section 127A except that the evaluation object is an "applicant" instead of a "recruiter". Therefore, the description of the recruiter evaluation summary section 127A that has already been made is used here to replace the description of the applicant evaluation summary section 127B.

[0171] The shared server 100 uses the evaluation input database 126 to determine the evaluation results of each member, and uses the member database 122 to determine the affiliation of each member. The shared server 100 updates the data in the evaluation summary database 127 based on these determination results.

[0172] In addition, in Figure 8 , only members P1 and P7 are shown as the evaluated persons, but other members P2 - P6, member P8, and member P9... are also registered in the evaluation summary database 127 as evaluated persons in the same way. The evaluation summary database 127 can also include data where the same member is set as the evaluation object as a recruiter and an applicant. For example, in the evaluation summary database 127 shown in Figure 8 , in addition to registering the recruiter evaluation summary related to member P1, the applicant evaluation summary related to member P1 can also be registered.

[0173] [Functions of the Shared Server, Recruiter Device, and Applicant Device]

[0174] Figures 9 - 11 is a diagram for explaining the functions of the shared server, recruiter device, and applicant device.

[0175] As shown in Figure 9As shown in the figure, the shared server 100 functionally includes a community registration department 140, an enterprise registration department 141, a member registration department 142, a member search department 143, and a case registration department 144. These various functions are implemented by the processor 101, the memory 102, the storage device 103, and the communication interface 104 provided in the shared server 100.

[0176] The community registration department 140 has the function of registering a community in the community database 123. The system administrator of the management matching system 1 uses an operation unit such as a keyboard (not shown) to input information related to the community into the shared server 100.

[0177] Among the information related to the community, it includes the community name and information about the enterprises belonging to the community. The community registration department 140 registers the community in the community database 123 according to the input of the system administrator (step S1). The community registration department 140 also has the function of updating the information of the community registered in the community database 123.

[0178] The enterprise registration department 141 has the function of registering new enterprises joining the matching system 1. The system administrator uses an operation unit such as a keyboard to input information related to the enterprise into the shared server 100.

[0179] Among the information related to the enterprise, it includes information such as the enterprise name and address. The enterprise registration department 141 registers the enterprise in the enterprise database 121 according to the input of the system administrator (step S2). The enterprise registration department 141 also has the function of updating the information of the registered enterprise.

[0180] The member registration department 142 has the function of registering (enrolling) new members joining the matching system 1. The member registration department 142 issues a member ID and password according to the request from a person belonging to an enterprise that has joined the matching system 1. A person who wishes to become a member uses a personal computer or the like to perform the registration process (step S3).

[0181] Specifically, a person who wishes to become a member inputs information such as name, affiliated enterprise, and affiliated department into a personal computer or the like, and sends the input information to the shared server 100. The member registration department 142 registers the input information in the member database 122. The new member can log in to the shared server 100 using the personal computer used for member registration. In this case, the personal computer functions as the recruiter device 200 or the applicant device 300.

[0182] In Figure 9Two applicant devices 300 are shown. One applicant device is a device assumed to be operated by a manager of a recruiting company. The other applicant device is a device assumed to be operated by a person other than the manager in the recruiting company. The manager of the recruiting company holds a management position such as a department head and is equivalent to the supervisor of the applicants who are his subordinates. The manager of the recruiting company acts as an approver who approves the recruitment cases of his subordinates.

[0183] The member search section 143 has a function of searching for members of the matching system 1. In response to requests from the recruiter device 200 and the applicant device 300, the member search section 143 provides information on the members registered in the member database 122 to the recruiter device 200 and the applicant device 300.

[0184] When the recruiter device 200 receives a search operation by the recruiter, it performs a member search process (step S4A). As a result, the recruiter can, for example, view the information of the applicants. The recruiter can consider the information of the applicants and select a person from among multiple applicants to whom the assets related to the recruitment case are to be transferred. Similarly, when the applicant device 300 receives a search operation by a manager who is the supervisor of a certain applicant, it performs a member search process (step S4A).

[0185] In addition, when the applicant device 300 receives a search operation by the applicant, it performs a member search process (step S4B). As a result, the applicant can, for example, view the information of the recruiters. The applicant can consider the information of the recruiters and select a case containing the assets that he or she wants to receive from among multiple recruitment cases.

[0186] The member search process (step S4A) performed by the recruiter device 200 and the process of the member search section 143 will be described in detail later using Figure 17 The member search process (step S4B) performed by the applicant device 300 and the process of the member search section 143 will be described in detail later using Figure 18 for this purpose.

[0187] The case registration section 144 has a function of registering recruitment cases in the recruitment case database 124. When the recruiter device 200 receives an operation of inputting a recruitment case, it performs a process of registering the recruitment case (step S5). In the process of registering the recruitment case, the recruiter device 200 sends information on the recruitment case to the shared server 100. The case registration section 144 registers the received information on the recruitment case in the recruitment case database 124.

[0188] The recruitment case registration process (step S5) performed by the recruiter device 200 and the process of the case registration section 144 will be described in detail later using Figure 13 for this purpose.

[0189] As shown Figure 10 in FIG., the shared server 100 functionally includes a case extraction unit 145, an application unit 146, an approval unit 147, and a notification unit 148. These various functions are implemented by a processor 101, a memory 102, a storage device 103, and a communication interface 104 provided in the shared server 100.

[0190] The case extraction unit 145 has a function of extracting recruitment cases that applicants can view. The application unit 146 has a function of applying for an applicant's application to a manager (the applicant's supervisor). The approval unit 147 has a function of sending the content of the application for a recruitment case to the recruiter on the condition that approval of the application is received from a manager (approver). The notification unit 148 has a function of receiving information indicating whether the applicant's application is approved or rejected from the recruiter device 200, and notifying the applicant and the manager of the corresponding recruitment result (approval, rejection) to their respective applicant devices 300.

[0191] The application unit 146, the approval unit 147, and the notification unit 148 implement the notification of requesting approval from the manager, the notification of the applicant to the recruiter, and the notification of the recruitment result to the applicant through a workflow system.

[0192] When the applicant device 300 receives an operation of requesting to retrieve recruitment cases by the applicant, it executes a retrieval process of recruitment cases (step S6). In the retrieval process of recruitment cases, the applicant device 300 sends a retrieval request to the case extraction unit 145 of the shared server 100.

[0193] When the case extraction unit 145 receives the retrieval request, it extracts cases that allow the applicant to view from the recruitment cases registered in the recruitment case database 124, and sends the extracted cases to the applicant device 300. The case extraction unit 145 determines whether a case is one that allows the applicant to view based on the public scope set for the recruitment case. The public scope is determined by public information.

[0194] Based on the determination result, the case extraction unit 145 extracts cases from the recruitment cases registered in the recruitment case database 124 that are allowed to be made public to the applicant who has received the retrieval request. The case extraction unit 145 sends the cases that allow the applicant to view to the applicant device 300.

[0195] The applicant device 300 receives the recruitment cases from the case extraction unit 145. The applicant device 300 displays the received recruitment cases on the display 305 (step S7). Thus, the applicant can view the recruitment cases as the retrieval result.

[0196] In addition, regarding the recruitment case retrieval process (step S6), the process of displaying recruitment cases (step S7), and the process of the case extraction unit 145, they will be described in detail later using Figure 14 as follows.

[0197] The applicant performs an operation of selecting an application target from the recruitment cases displayed on the display 305 in the applicant device 300. The applicant device 300 executes an application process (step S8) according to the applicant's operation. In the application process, the applicant device 300 sends the application information indicating the case as the application target to the application unit 146 of the shared server 100.

[0198] The application unit 146 sends the application information received from the applicant device 30 to the applicant device 300 of the manager (the applicant's supervisor). The application unit 146 determines the member ID of the supervisor, who is the manager of the applicant, based on, for example, the relationship between the member ID of the applicant registered in the member database 122 and the member ID of the supervisor.

[0199] The application unit 146 sends the application information of the subordinate to the applicant device 300 corresponding to the determined supervisor's member ID. The application information sent to the applicant device 300 includes the "asset title", "asset content", "asset classification", "asset transfer amount", "recruitment quantity", and "transfer / use" registered in the recruitment case database 124. The manager confirms the content of the recruitment case applied by the subordinate in his / her own applicant device 300.

[0200] The manager performs an operation for approving the application in the applicant device 300. The applicant device 300 accepts the approval operation and executes the application approval process (step S9). In the application approval process, the applicant device 300 sends approval information to the approval unit 147 of the shared server 100. Thus, the approval information, which is an example of an approval notice, is sent from the applicant device 300 of the manager (approver) to the approval unit 147.

[0201] The approval unit 147 accepts the applicant's application on the condition that the approval information is received from the applicant device 300. In this way, the applicant's application is accepted on the condition of the approval of the manager to whom the applicant belongs. Therefore, the manager can confirm in advance the content of the recruitment case that the subordinate wants to apply for.

[0202] In addition, the process when the manager approves the application is shown in Figure 10 . Assuming that an operation to reject the application is accepted in step S9, rejection information is sent from the applicant device 300 of the manager to the approval unit 147. The approval unit 147 may also notify the applicant device 300 of the applicant that the application has been rejected when the rejection information is received.

[0203] The approval unit 147 that has accepted the application of the applicant sends the application information to the recruiter device 200. The application information includes the information of the applicant and the content of the recruitment case for which the applicant is applying. The recruiter device 200 displays the content of the application information on the display 205 (step S10). The recruiter confirms the applicant and the recruitment case based on the display on the display 205, and decides whether to approve or reject the applicant's application.

[0204] The recruiter inputs the result of the judgment of approval or rejection to the recruiter device 200. The recruiter device 200 accepts the input result (step S11). The recruiter device 200 sends the accepted result of approval or rejection to the notification unit 148 of the shared server 100.

[0205] When the notification unit 148 receives the result of approval or rejection from the recruiter device 200, it sends the application result (the result of approval or rejection) to the applicant device 300 of the applicant and the applicant device 300 of the manager.

[0206] The applicant device 300 of the applicant and the applicant device 300 of the manager display the application result on the display 305 (step S12, step S13). The applicant and the manager confirm the application result by viewing the display on the display 305. In the case of approving the application, procedures for transferring the target assets are handled between the recruiter and the applicant.

[0207] As Figure 11 shown, the shared server 100 functionally includes an evaluation acceptance unit 151 and an evaluation output unit 152. These functions are implemented by the processor 101, the memory 102, the storage device 103, and the communication interface 104 provided in the shared server 100.

[0208] The evaluation acceptance unit 151 has the function of accepting the evaluation of the applicant input by the recruiter in the recruiter device 200. The evaluation output unit 152 has the function of outputting information indicating the evaluation of the applicant to the recruiter device 200. When the recruiter completes the transaction regarding the recruitment case with the applicant, the recruiter inputs the evaluation of the applicant to the recruiter device 200. The key points for the recruiter to evaluate the applicant are diverse.

[0209] For example, when the recruiter can communicate smoothly with the applicant and complete the transaction in a short time, the recruiter will give a high evaluation to the applicant. On the contrary, when the applicant frequently requests to change the amount of asset transfer, or when the applicant has a poor response to transaction contacts, the recruiter will give a lower evaluation to the applicant.

[0210] The recruiter device 200 accepts the input of the evaluation of the applicant (step S16A). Therefore, when accepting the input evaluation, the recruiter device 200 functions as an evaluator device operated by the evaluator (recruiter).

[0211] The recruiter device 200 sends the accepted evaluation to the evaluation acceptance department 151 of the shared server 100. The evaluation acceptance department 151 updates the evaluation input database 126 and the evaluation summary database 127 based on the received evaluation. Thereby, the information of the applicant evaluation department 126B is updated in the evaluation input database 126, and the information of the applicant evaluation summary department 127B is updated in the evaluation summary database 127.

[0212] Regarding the processing of step S16A performed by the recruiter device 200 and the processing of the evaluation acceptance department 151, it will be described in detail later Figure 15 using

[0213] When the recruiter device 200 accepts an operation for the recruiter to view the evaluation of the applicant, it executes a browse request process (step S17A). In the browse request process, the recruiter device 200 sends a browse request to the evaluation output department 152 of the shared server 100. In response to the browse request, the evaluation output department 152 sends the evaluation of the applicant (applicant evaluation summary) registered in the evaluation summary database 127 to the recruiter device 200. The recruiter device 200 displays the received evaluation of the applicant on the display 205 (step S18A).

[0214] Regarding the processing of step S17A and step S18A performed by the recruiter device 200 and the processing of the evaluation output department 152, it will be described in detail later Figure 17 using

[0215] Figure 12 It is a diagram for further explaining the functions of the applicant device 300. Here, Figure 12 is used to explain the input and output of the evaluation of the recruiter. The evaluation acceptance department 151 also has the function of accepting the evaluation of the recruiter input by the applicant to the applicant device 300. The evaluation output department 152 also has the function of outputting information indicating the evaluation of the recruiter to the applicant device 300. When the applicant completes the transaction regarding the recruitment case with the recruiter, the applicant inputs the evaluation of the recruiter to the applicant device 300. The key points for the applicant to evaluate the recruiter are diverse.

[0216] For example, when the applicant can communicate smoothly with the recruiter and complete the transaction in a short time, the applicant will give a high evaluation to the recruiter. On the contrary, when the recruiter frequently requests to change the transaction amount, or when the status of the assets involved in the transaction is poor, the applicant will give a lower evaluation to the recruiter.

[0217] The applicant device 300 accepts the input of the evaluation of the recruiter (step S16B). Therefore, the applicant device 300 functions as an evaluator device operated by the evaluator (applicant) when accepting the input evaluation.

[0218] The applicant device 300 sends the accepted evaluation to the evaluation acceptance unit 151 of the shared server 100. The evaluation acceptance unit 151 updates the evaluation input database 126 and the evaluation summary database 127 based on the received evaluation. Thus, the information of the recruiter evaluation unit 126A is updated in the evaluation input database 126, and the information of the recruiter evaluation summary unit 127A is updated in the evaluation summary database 127.

[0219] Regarding the processing of step S16B performed by the applicant device 300 and the processing of the evaluation acceptance unit 151, it will be described in detail later. Figure 16 To elaborate.

[0220] When the applicant device 300 accepts an operation for the applicant to view the evaluation of the recruiter, it performs a browsing request process (step S17B). In the browsing request process, the recruiter device 200 sends a browsing request to the evaluation output unit 152 of the shared server 100. In response to the browsing request, the evaluation output unit 152 sends the evaluation of the recruiter (recruiter evaluation summary) registered in the evaluation summary database 127 to the applicant device 300. The applicant device 300 displays the received evaluation of the recruiter on the display 305 (step S18B).

[0221] Regarding the processing of step S17B, step S18B performed by the applicant device 300 and the processing of the evaluation output unit 152, it will be described in detail later. Figure 18 To elaborate.

[0222] [Details of the processing of the case registration unit 144 and the recruiter device 200]

[0223] Figure 13 It is a diagram for explaining the process of registering a recruitment case in the recruitment case database 124. Using Figure 13 To explain in more detail Figure 9 Step S5 and the functions of the case registration unit 144.

[0224] The recruiter who registers the recruitment case first logs in to the shared server 100 using the recruiter device 200. Thus, a logical communication path identified by the recruiter's member ID is established between the recruiter device 200 and the shared server 100. Then, the recruiter uses an operation unit 206 such as a mouse and a keyboard to input the asset information and public information of the recruitment case into the recruiter device 200.

[0225] The asset information includes "asset title", "asset content", "asset classification", "asset transfer amount", "recruitment quantity", and "transfer / use". The public information includes the public level. In the public information, depending on the recruiter's selection, sometimes it includes the ID of an enterprise that is a "non-disclosure object".

[0226] The information input through the operation unit 206 is notified to the processor 201 via the input / output interface 204 of the recruiter device 200. The operation unit 206 and the input / output interface 204 constitute an interface for accepting operations for inputting the content of a recruitment case and operations for inputting public information.

[0227] The recruiter device 200 accepts the input of the asset information and public information of a recruitment case and executes the process of registering the recruitment case (step S5). In the process of registering the recruitment case, the recruiter device 200 sends the asset information and public information of the recruitment case to the shared server 100.

[0228] The case registration unit 144 of the shared server 100 acquires the information of the recruiter (step S1441). Specifically, the case registration unit 144 determines the enterprise to which the recruiter belongs.

[0229] When a member logs in to the shared server 100 using the recruiter device 200 or the applicant device 300, the shared server 100 stores the member ID used for the login. When the shared server 100 receives certain information from the recruiter device 200 or the applicant device 300 in a communication established based on this member ID, the shared server 100 uses the member ID used for the login to identify the member who is the source of this information.

[0230] Therefore, when the case registration unit 144 receives the asset information and public information of a recruitment case from the recruiter device 200, it uses the member ID used for the login to determine the recruiter who is operating the recruiter device 200. The case registration unit 144 uses the determined member ID, the member database 122, and the enterprise database 121 to determine the member who is the recruiter and the enterprise to which the recruiter belongs.

[0231] Next, the case registration unit 144 executes the process of registering the recruitment case in the recruitment case database 124 (step S1442). Specifically, after generating a case ID, the case registration unit 144 registers the enterprise information (enterprise ID), public information (public level and the ID of the enterprise set as non-disclosed), and asset information (asset title, asset content, asset classification, asset transfer amount, recruitment quantity, and transfer / use information), etc. corresponding to the generated case ID in the recruitment case database 124.

[0232] According to the present embodiment, the recruiter can freely control the disclosure range of recruitment cases at levels of "within the company", "within the community", and "unrestricted". As a result, it is possible to prevent recruitment cases that the recruiter does not expect from being disclosed to specific enterprises such as competitor companies.

[0233] According to the present embodiment, it is possible to set enterprises that are not subject to disclosure separately from the disclosure level. Therefore, the recruiter can set the disclosure range in such a way as to exclude some of the multiple enterprises that have a community relationship with the enterprise to which the recruiter belongs. As a result, it is possible to prevent information on recruitment cases from leaking to specific enterprises within the community.

[0234] Instead of the non-disclosure enterprise ID list, a non-disclosure member ID list may be set in the recruitment case database 124, or in addition to the non-disclosure enterprise ID list, a non-disclosure member ID list may be set in the recruitment case database 124. The non-disclosure member ID list is used to register member IDs that prohibit the disclosure of recruitment cases. The recruiter device 200 may also accept an operation for specifying a member who prohibits the disclosure of a recruitment case and send the ID of the member to the sharing server 100. The sharing server 100 may not provide recruitment cases corresponding to the list to members corresponding to the member IDs registered in the non-disclosure member ID list. In this way, the recruiter device 200 may also accept either an enterprise or a member as an object for prohibiting the disclosure of recruitment cases.

[0235] Figure 14 It is a diagram for explaining the process of retrieving recruitment cases from the database 120. Use Figure 14 Explain in more detail Figure 10 the processing of step S6, step S7, and the function of the case extraction unit 145.

[0236] When the applicant device 300 receives an operation for the applicant to request the retrieval of recruitment cases, it executes the retrieval process of recruitment cases (step S6). In the retrieval process of recruitment cases, the applicant device 300 sends a retrieval request to the case extraction unit 145 of the sharing server 100.

[0237] When the case extraction unit 145 receives the retrieval request, it extracts cases that allow the applicant to view from the recruitment cases registered in the recruitment case database 124. Therefore, the case extraction unit 145 executes the processing of steps S1451 and S1452.

[0238] Steps S1451 and S1452 are processes for extracting cases that allow the applicant to view based on the disclosure range set for the recruitment cases. In step S1451, it is determined the enterprise to which the applicant belongs and the community of the enterprise to which the applicant belongs. In step S1452, recruitment cases that can be disclosed are extracted.

[0239] [Processing of cases extracted based on the public scope]

[0240] Step S1451 includes Step S1451A and Step S1451B.

[0241] In Step S1451A, based on the member ID used at the time of login, the enterprise database 121, and the member database 122, the enterprise to which the applicant belongs is determined.

[0242] In Step S1451B, based on the ID of the enterprise to which the applicant belongs and the community database 123, the community of the enterprise to which the applicant belongs is determined.

[0243] Step S1452 includes Step S1452A and Step S1452B.

[0244] In Step S1452A, based on the community to which the enterprise to which the applicant belongs belongs and the public level, recruitment cases that can be made public to the applicant are extracted from the recruitment case database 124.

[0245] In Step S1452B, among the recruitment cases extracted in Step S1452A, the recruitment cases in which the enterprise to which the applicant belongs exists in the non-public enterprise list are excluded. Thus, matching cases that can be made public to the applicant are extracted.

[0246] [Processing of providing the extracted cases]

[0247] Next, the case extraction unit 145 sends the information of the matching cases to the applicant device 300 (Step S1455). The applicant device 300 receives the matching cases. The applicant device 300 displays the received matching cases as recruitment cases on the display 305 at a glance (Step S7). Recruitment cases within the public scope desired by the recruiter are provided to the applicant. Thus, when the applicant retrieves recruitment cases, only recruitment cases that will not cause disadvantages to the recruiter are provided to the applicant. As a result, for example, it is possible to prevent information related to the assets of the enterprise to which the recruiter belongs from being leaked to competing companies.

[0248] [Processing of registering evaluation results (evaluation of applicants)]

[0249] Figure 15 is a diagram for explaining the process of registering the evaluation of the applicant into the database 120. Using Figure 15 Explain in more detail Figure 11 Steps S16A and the functions of the evaluation reception unit 151.

[0250] When the recruiter completes a transaction with the applicant, the recruiter operates the recruiter device 200 to input an evaluation of the applicant into the recruiter device 200. The recruiter device 200 accepts the input evaluation (step S16A). The recruiter device 200 sends the accepted evaluation to the evaluation acceptance unit 151 of the shared server 100. The information sent from the recruiter device 200 to the shared server 100 includes the member ID of the applicant as the evaluated person and the evaluation value (0 to 10).

[0251] When the evaluation acceptance unit 151 receives information on the evaluation of the evaluated person (applicant) from the recruiter device 200, it reflects the evaluation of the evaluated person in the evaluation input database 126 (step S1513A).

[0252] When the evaluation result of the evaluated person (applicant) has been registered in the evaluation input database 126, the evaluation acceptance unit 151 calculates the average value of the evaluation results of the evaluated person in a way that includes the value of the evaluation received this time. The evaluation acceptance unit 151 updates the evaluation result registered in the evaluation input database 126 with the calculated average value. As a result, in the evaluation input database 126, the average value (evaluation result) of the evaluation of the evaluated person (applicant) is registered for each evaluator (recruiter). Thus, the information of the applicant evaluation unit 126B is updated in the evaluation input database 126.

[0253] Next, the evaluation acceptance unit 151 performs an evaluation summary process (step S1514A). In the evaluation summary process, the evaluation acceptance unit 151 calculates the average value of the evaluation results of the evaluated person (applicant) by enterprise and by department, and registers the calculation result in the evaluation summary database 127. Thus, the information of the applicant evaluation summary unit 127B is updated in the evaluation summary database 127.

[0254] For example, the evaluation acceptance unit 151 uses the member ID used in the login performed by the recruiter device 200 to execute step S16A to identify the evaluator (recruiter). The evaluation acceptance unit 151 determines the ID of the enterprise to which the evaluator belongs, the department to which the evaluator belongs, the member ID of the evaluated person, and the ID of the enterprise to which the evaluated person belongs based on the evaluation information received in step S1513A, the enterprise database 121, and the member database 122. The "member ID" is an example of "identification information that the shared server 100 including the evaluation acceptance unit 151 can use to identify the affiliation (enterprise and department) of the person who accessed the shared server 100".

[0255] The evaluation acceptance unit 151 accesses the evaluation summary database 127 to detect a data row formed by arranging the determined IDs (the member ID of the evaluated person, the ID of the company to which the evaluated person belongs, and the ID of the company to which the evaluator belongs). The evaluation acceptance unit 151 updates the value of the applicant evaluation summary corresponding to the detected data row.

[0256] [Processing for registering evaluation results (evaluation of recruiters)]

[0257] Figure 16 This is a diagram for explaining the process of registering the evaluation of recruiters in the database. Use Figure 16 to explain in more detail Figure 12 Steps S16B and the functions of the evaluation acceptance unit 151.

[0258] After the applicant completes the transaction with the recruiter, the applicant device 300 is operated to input an evaluation of the recruiter to the applicant device 300. The applicant device 300 accepts the input evaluation (step S16B). The applicant device 300 sends the accepted evaluation to the evaluation acceptance unit 151 of the shared server 100. The information sent from the applicant device 300 to the shared server 100 includes the member ID of the recruiter as the evaluated person and the evaluation value (0 - 10).

[0259] When the evaluation acceptance unit 151 receives information on the evaluation of the evaluated person (recruiter) from the applicant device 300, it reflects the evaluation of the evaluated person in the evaluation input database 126 (step S1513B).

[0260] When the evaluation result for the evaluated person (recruiter) has already been registered in the evaluation input database 126, the evaluation acceptance unit 151 calculates the average value of the evaluation result for the evaluated person in a way that includes the value of the evaluation received this time. The evaluation acceptance unit 151 updates the evaluation result registered in the evaluation input database 126 with the calculated average value. As a result, in the evaluation input database 126, the average value (evaluation result) of the evaluation of the evaluated person (recruiter) is registered for each evaluator (applicant). Thus, the information of the recruiter evaluation unit 126A is updated in the evaluation input database 126.

[0261] Next, the evaluation acceptance unit 151 performs an evaluation summary process (step S1514B). In the evaluation summary process, the evaluation acceptance unit 151 calculates the average value of the evaluation results for the evaluated person (recruiter) by company and by department, and registers the calculation result in the evaluation summary database 127. Thus, the information of the recruiter evaluation summary unit 127A is updated in the evaluation summary database 127.

[0262] For example, the evaluation reception unit 151 determines the evaluator (applicant) using the member ID used in the login performed by the applicant device 300 to execute step S16B. The evaluation reception unit 151 determines the ID of the enterprise to which the evaluator belongs, the department to which the evaluator belongs, the member ID of the evaluatee, and the ID of the enterprise to which the evaluatee belongs based on the evaluation information received in step S1513B, the enterprise database 121, and the member database 122. The "member ID" is an example of "identification information that enables the shared server 100 including the evaluation reception unit 151 to identify the affiliation (enterprise and department) of the person who accessed the shared server 100".

[0263] The evaluation reception unit 151 accesses the evaluation summary database 127 and detects the data row formed by arranging the determined IDs (the member ID of the evaluatee, the ID of the enterprise to which the evaluatee belongs, and the ID of the enterprise to which the evaluator belongs). The evaluation reception unit 151 updates the value of the recruiter evaluation summary corresponding to the detected data row.

[0264] For example, in Figure 8 the data group 1271, the member ID of the evaluatee = P1, the ID of the enterprise to which the evaluatee belongs = 00A, and the ID of the enterprise to which the evaluator belongs = 00B are arranged. In the case where a member of the system department belonging to enterprise B evaluates member P1, this evaluation is received in step S1513B.

[0265] In this case, in step S1514B, the evaluation received in step S1513B is reflected in the recruiter evaluation summary corresponding to "all" of the data group 1271 and the recruiter evaluation summary corresponding to "system department".

[0266] More specifically, the evaluation reception unit 151 sets the average value of the evaluations of the entire enterprise B including the evaluation received in step S1513B as the recruiter evaluation summary corresponding to "all" of the data group 1271. Similarly, the evaluation reception unit 151 sets the average value of the evaluations of the system department including the evaluation received in step S1513B as the recruiter evaluation summary corresponding to "system department" of the data group 1271.

[0267] Figure 17 is a diagram for explaining the process of displaying the evaluation of the applicant and the search result of the member on the display 205. Using Figure 17 Explain in more detail Figure 10 step S4A (processing of the recruiter device 200) and the function of the member search unit 143, and Figure 11 step S17A, step S18A and the function of the evaluation output unit 152.

[0268] [Processing of Evaluation Summary of Applicants]

[0269] First, the Figure 17 processing of each of step S17A, step S18A, step S1521A, and step S1522A shown will be described.

[0270] When the recruiter device 200 receives an operation for the recruiter to view the evaluations of applicants, it executes a view request process (step S17A). In the view request process, the recruiter device 200 sends a view request to the evaluation output unit 152 of the shared server 100. In response to the view request, the evaluation output unit 152 selects applicant evaluation summaries for which the recruiter (view requester) has been granted view permission from the evaluation summary database 127 (step S1521A).

[0271] The recruiter who has made the view request has been granted the permission to view applicant evaluation summaries for the entire enterprise to which the recruiter belongs and applicant evaluation summaries for the department to which the recruiter belongs. The recruiter who has made the view request has not been granted the permission to view evaluation summaries other than these. The evaluation output unit 152 determines the view permission based on the member ID of the recruiter who sent the view request, the enterprise database 121, and the member database 122. "Member ID" is an example of "identification information that enables the shared server 100 including the evaluation reception unit 151 to identify the affiliation (enterprise and department) of the person who has accessed the shared server 100 and the view permission".

[0272] The evaluation output unit 152 selects applicant evaluation summaries corresponding to the view permission from the evaluation summary database 127. The evaluation output unit 152 sends data including the selected applicant evaluation summaries to the recruiter device 200 (step S1522A). In the data sent, in addition to including the applicant evaluation summaries, it also includes the member ID of the applicant (evaluated person), information on the enterprise to which the applicant belongs, information on the department to which the applicant belongs, etc. In the data sent, depending on the view request, it may include applicant evaluation summaries corresponding to multiple applicants (evaluated persons) respectively.

[0273] The recruiter device 200 that has received the applicant evaluation summary displays the applicant evaluation summary together with the information on the enterprise to which the applicant belongs and the information on the department to which the applicant belongs on the display 205 (step S18A). When receiving applicant evaluation summaries corresponding to multiple applicants (evaluated persons) respectively, the recruiter device 200 creates a list of the multiple applicants (evaluated persons) to display the applicant evaluation summaries.

[0274] In this way, when the shared server 100 receives a browsing request in a communication established based on a member ID that can identify the company and department to which the recruiter belongs, the shared server 100 sends a candidate evaluation summary, which is an example of evaluation information, to the recruiter device 200 of the recruiter who is the source that sent the browsing request.

[0275] [Processing for Retrieving Members (Candidates)]

[0276] Next, with reference to Figure 17 the respective processes of step S4A, step S19A, and steps S1431A to S1433A will be described.

[0277] When the recruiter device 200 receives a retrieval operation from the recruiter, the recruiter device 200 executes a member retrieval process (step S4A) for retrieving information related to candidates. In the member retrieval process, the recruiter device 200 sends a retrieval request to the member retrieval unit 143 of the shared server 100. The retrieval request includes a reference value for excluding members with low evaluations as candidates for retrieval. This reference value is determined based on, for example, the value of the candidate evaluation summary.

[0278] The member retrieval unit 143 that has received the retrieval request determines the company to which the recruiter who sent the retrieval request belongs (step S1431A). Here, the company determined through step S1431A is referred to as "Company Xa".

[0279] The member retrieval unit 143 uses the member ID used when the recruiter device 200 logs in to the shared server 100 to determine the recruiter who is operating the recruiter device 200. The member retrieval unit 143 uses the company database 121 and the member database 122 to determine the company Xa to which the recruiter belongs.

[0280] Next, the member retrieval unit 143 extracts members from the evaluation summary database 127 whose candidate evaluation summary values for the entire determined company Xa exceed the reference value (step S1432A). That is, the member retrieval unit 143 extracts the retrieval results after excluding members with low evaluations for the entire company Xa.

[0281] Here, it should be noted that the member retrieval unit 143 determines whether the evaluation is low based on the candidate evaluation summary. That is, for member α who has the authorities of both a candidate and a recruiter, there are cases where member α is regarded as a candidate and cases where member α is regarded as a recruiter. Therefore, as the evaluation summary of such member α, a candidate evaluation summary and a recruiter evaluation summary are registered in the evaluation summary database 127. Member α may have a high evaluation as a recruiter but a low evaluation as a candidate. In this case, in step S1432A, member α may be excluded from the extraction target.

[0282] It is also possible to set a function in the shared server 100 to receive setting information of a reference value from the recruiter devices 200 of each company. Thus, each company can exclude members with low evaluations from the search results based on its own reference value.

[0283] Next, the member search unit 143 outputs the information of the extracted members as a search result to the recruiter device 200 with a search request (step S1433A). The recruiter device 200 displays the received search result list on the display 205 (step S19A).

[0284] As a result, the recruiter can browse the search result on the display 205 after excluding members with low evaluations for the entire company to which the recruiter belongs. Therefore, when selecting an assignee from the applicants, the recruiter can save the effort of visually excluding members with low evaluations for the entire company.

[0285] In addition, in the present embodiment, even if a member (applicant) of a certain department of the company to which the recruiter belongs has a low evaluation, if the evaluation of the entire company is not low, this member (applicant) will not be excluded from the search results. However, the member search unit 143 can also further exclude such a member (applicant) from the search results.

[0286] Figure 18 It is a diagram for explaining the process of displaying the evaluation of the recruiter and the search result of the members on the display 305. Use Figure 18 to explain in more detail Figure 10 step S4B (processing of the applicant device 300) and the function of the member search unit 143, and Figure 12 step S17B, step S18B, and the function of the evaluation output unit 152 in

[0287] [Processing of outputting the evaluation summary of the recruiter]

[0288] First, explain Figure 18 each process of step S17B, step S18B, step S1521B, and step S1522B shown in

[0289] When the applicant device 300 receives an operation for an applicant to browse the evaluation of the recruiter, it executes a browse request process (step S17B). In the browse request process, the applicant device 300 sends a browse request to the evaluation output unit 152 of the shared server 100. In response to the browse request, the evaluation output unit 152 selects the recruiter evaluation summary for which the applicant (browse requester) has been granted browsing permission from the evaluation summary database 127 (step S1521B).

[0290] An applicant who has made a browsing request is granted the right to view the recruiter evaluation summary for the entire company to which the applicant belongs and the recruiter evaluation summary for the department to which the applicant belongs. An applicant who has made a browsing request is not granted the right to view evaluation summaries other than these. The evaluation output unit 152 determines the browsing right based on the member ID of the applicant who sent the browsing request, the company database 121, and the member database 122. "Member ID" is an example of "identification information that enables the shared server 100 including the evaluation reception unit 151 to identify the affiliation (company and department) and browsing rights of a person who has accessed the shared server 100".

[0291] The evaluation output unit 152 selects the recruiter evaluation summary corresponding to the browsing right from the evaluation summary database 127. The evaluation output unit 152 sends the data including the selected recruiter evaluation summary to the applicant device 300 (step S1522B). In the data sent, in addition to including the recruiter evaluation summary, it also includes the member ID of the recruiter (the person being evaluated), information on the company to which the recruiter belongs, information on the department to which the recruiter belongs, etc. In the data sent, depending on the browsing request, it may include recruiter evaluation summaries corresponding to multiple recruiters (persons being evaluated) respectively.

[0292] The applicant device 300 that has received the recruiter evaluation summary displays the recruiter evaluation summary together with the information on the company to which the recruiter belongs and the information on the department to which the recruiter belongs on the display 305 (step S18B). In the case of receiving recruiter evaluation summaries corresponding to multiple recruiters (persons being evaluated) respectively, the applicant device 300 creates a list of the multiple recruiters (persons being evaluated) to display the recruiter evaluation summaries.

[0293] In this way, when the shared server 100 receives a browsing request in a communication established based on the member ID that can identify the company and department to which the applicant belongs, the shared server 100 sends the recruiter evaluation summary, which is an example of evaluation information, to the applicant device 300 of the applicant who is the source of the browsing request.

[0294] [Processing for retrieving members (recruiters)]

[0295] Next, with reference to Figure 18 the respective processes of step S4B, step S19B, and steps S1431B to S1433B will be described.

[0296] When the applicant device 300 receives a search operation from an applicant, it performs a member search process for searching for information related to the recruiter (step S4B). In the member search process, the applicant device 300 sends a search request to the member search unit 143 of the shared server 100. The search request includes a reference value for excluding members with low evaluations as recruiters for the search. This reference value is determined, for example, based on the recruiter evaluation summary value.

[0297] The member search unit 143 that has received the search request determines the company to which the applicant who sent the search request belongs (step S1431B). Here, the company determined through step S1431B is referred to as "Company Xb".

[0298] The member search unit 143 uses the member ID used when the applicant device 300 logs in to the shared server 100 to determine the applicant who is operating the applicant device 300. The member search unit 143 uses the company database 121 and the member database 122 to determine the company Xb to which the applicant belongs.

[0299] Next, the member search unit 143 extracts from the evaluation summary database 127 members whose recruiter evaluation summary value for the entire determined company Xb exceeds the reference value (step S1432B). That is, the member search unit 143 extracts the search results after excluding members with low evaluations for the entire company Xb.

[0300] It is also possible to set in the shared server 100 a function for receiving the setting information of the reference value from the recruiter devices 200 of each company. Thus, each company can exclude members with low evaluations from the search results with its own reference value.

[0301] Next, the member search unit 143 outputs the information of the extracted members as search results to the applicant device 300 that has sent the search request (step S1433B). The applicant device 300 displays the received search results in a list on the display 305 (step S19B).

[0302] As a result, the applicant can browse on the display 305 the search results after excluding members with low evaluations for the entire company to which the applicant belongs. Therefore, when the applicant selects a recruiter that is considered appropriate from the recruiters, the applicant can save the effort of visually excluding members with low evaluations for the entire company.

[0303] In addition, in the present embodiment, even if a member (recruiter) of a certain department of the company to which the applicant belongs has a low evaluation, as long as the evaluation of the entire company is not low, this member (recruiter) will not be excluded from the search results. However, the member search unit 143 may further exclude such a member (recruiter) from the search results.

[0304] [Viewable Range of the Evaluation Summary Database 127]

[0305] Figure 19 This is a diagram for explaining the viewable range of the evaluation summary database 127. Here, taking the recruiter evaluation summary section 127A shown in Figure 8 as an example, the viewable range will be explained.

[0306] In Figure 19 the recruiter evaluation summary section 127A shown, the evaluation summaries of member P1 regarded as a "recruiter" by Company B and Company C are included. Member P1 belongs to Company A. The evaluation summary of Company B is classified into "Overall", "System Department", and "Planning Department". The evaluation summary of Company C is classified into "Overall" and "Planning Department", etc. Members belonging to Company B and Company C view the evaluation summary of member P1 as "applicants".

[0307] The viewing permission for the evaluation summary calculated based on the overall evaluation of Company B is granted to all members belonging to Company B as shown in the "Viewable Range" column in Figure 19 .

[0308] The viewing permission for the evaluation summary calculated based on the evaluation of the system department of Company B is granted to the members of the system department of Company B, but not to members other than the system department of Company B. The viewing permission for the evaluation summary calculated based on the evaluation of the planning department of Company B is granted to the members of the planning department of Company B, but not to members other than the planning department of Company B.

[0309] The viewing permission for the evaluation summary calculated based on the overall evaluation of Company C is granted to all members belonging to Company C. The viewing permission for the evaluation summary calculated based on the evaluation of the planning department of Company C is granted to the members of the planning department of Company C, but not to members other than the planning department of Company C.

[0310] The viewable range was explained above by taking the recruiter evaluation summary section 127A as an example. In the matching system 1, the applicant evaluation summary section 127B (refer to Figure 8 ) also determines the viewable range with the same design concept as the recruiter evaluation summary section 127A.

[0311] In the case where the viewers are members of the first department of Company X and members of the second department of Company X, the viewing permissions of the viewers for the evaluation summary of Company X as a whole, the evaluation summary of the first department of Company X, and the evaluation summary of the second department of Company X are as shown in Figure 19As shown in Table 401. Here, when the applicant is equivalent to the "browser", the browsing object is the evaluation summary of the "recruiter". On the contrary, when the recruiter is equivalent to the "browser", the browsing object is the evaluation summary of the "applicant".

[0312] Members belonging to the first department of Company X can view the evaluation summary of the entire Company X and the evaluation summary of the first department of Company X, but cannot view the evaluation summary of the second department of Company X. Members belonging to the second department of Company X can view the evaluation summary of the entire Company X and the evaluation summary of the second department of Company X, but cannot view the evaluation summary of the second department of Company X. Members belonging to Company Y other than Company X cannot view the evaluation summary of the entire Company X, the evaluation summary of the first department of Company X, and the evaluation summary of the second department of Company X.

[0313] The evaluation summary of the entire Company X, the evaluation summary of the first department of Company X, and the evaluation summary of the second department of Company X are not disclosed to members of companies other than Company X. Therefore, members belonging to Company Y and regarded as applicants can objectively evaluate the recruiters belonging to Company X without considering the relationship between companies, etc. in the scenario of evaluating the recruiters belonging to Company X. Similarly, members belonging to Company Y and regarded as recruiters can objectively evaluate the applicants belonging to Company X without considering the relationship between companies, etc. in the scenario of evaluating the applicants belonging to Company X.

[0314] In addition, evaluations (evaluations of recruiters and evaluations of applicants) made by members belonging to Company X are shared in Company X as recruiter evaluation summaries and applicant evaluation summaries. Therefore, it is possible to make evaluators aware that the accumulation of individual evaluations generates useful information. This gives evaluators the motivation to make accurate evaluations.

[0315] As a result, the accuracy of the recruiter evaluation summary and the applicant evaluation summary is improved. Thus, the recruiter evaluation summary can be usefully utilized as reference data when selecting recruitment cases. Similarly, the applicant evaluation summary can be usefully utilized as reference data when selecting assignees.

[0316] Moreover, according to this embodiment, in the recruiter device 200, when the member search process (step S4A) is executed, the search result after excluding members with low evaluations is provided to the recruiter (step S1432A). Similarly, in the applicant device 300, when the member search process (step S4B) is executed, the search result after excluding members with low evaluations is provided to the recruiter (step S1432B). That is, the matching system 1 has a filtering function that provides a search result after excluding members with low evaluations.

[0317] Therefore, when determining the assignee for a recruitment case, the recruiter can prevent the incorrect employment of members with low evaluations on a company-by-company basis. Similarly, when an applicant decides on an application target from a large number of recruitment cases, the applicant can prevent the incorrect selection of cases that recruit members with low evaluations on a company-by-company basis. In addition, the shared server 100 can also perform filtering using the evaluation summary on a department-by-department basis.

[0318] An instruction signal for indicating which one of the filtering using the evaluation summary of the entire company and the filtering using the evaluation summary on a department-by-department basis can also be sent from the recruiter device 200 to the shared server 100. In this case, a function for changing the evaluation summary used for filtering according to the instruction signal is set in the shared server 100.

[0319] [Example of setting the disclosure range according to the disclosure level]

[0320] Figure 20 is a diagram showing an example of setting the disclosure range according to the disclosure level. Here, as Figure 20 shown, consider the case where companies A to E form a community relationship and company F has no community relationship with any company. In this case, according to the company to which the recruiter belongs and the disclosure level set by the recruiter, the disclosure range of the recruitment case is as shown in Table 402.

[0321] Figure 20 The disclosure levels of "Level 1" to "Level 3" shown correspond to the three levels of "Company", "Within the community", and "All" that have been described. Thus, in Level 1, the recruitment cases of the recruiter are disclosed only to the applicants within the same company as the company to which the recruiter belongs. In Level 2, in addition to the range of Level 1, the recruitment cases of the recruiter are also disclosed to the applicants belonging to the companies that have a community relationship with the company to which the recruiter belongs. In Level 3, the recruitment cases of the recruiter are disclosed to the applicants belonging to all companies including the company to which the recruiter belongs. However, when the recruiter designates a company ID to be set as non-disclosed, regardless of the set disclosure level, the company corresponding to the company ID is excluded from the companies that are the disclosure targets. "Level 1" in the disclosure level of the present embodiment corresponds to the level of "allowing the disclosure of asset information (case information) to the first applicant and prohibiting the disclosure of asset information to applicants who do not belong to the first group". "Level 2" corresponds to the level of "allowing the disclosure of asset information to the applicants belonging to any group in the first group and the community group that has formed a community relationship with the first group and prohibiting the disclosure of asset information to applicants who do not belong to any of the first group and the community group". "Level 3" corresponds to the level of "allowing the disclosure of asset information to the applicant regardless of the group to which the applicant belongs".

[0322] Here, as an example of multiple disclosure levels, levels 1 to 3 as described above are illustrated. However, the multiple disclosure levels are not limited to these levels. For example, a certain community can be divided into multiple small communities, and it is possible to set whether to publicly recruit cases for each small community. More specifically, Figure 5 the community 02 shown in is divided into a first small community and a second small community. Enterprise C belongs to the first small community, and enterprises D and E belong to the second small community. In this case, it can also be set that the recruiter of enterprise D can choose whether to set the disclosure range of their recruitment case to the range of the first small community or to the range of the second small community.

[0323] The shared server 100 can also accept an operation of setting the disclosure range in a different way for each recruitment case. For example, taking cases 001 to 003 among multiple recruitment cases as examples, a specific example of setting the disclosure range in a different way for each recruitment case is described.

[0324] For example, the disclosure range of recruitment case 001 can be limited only to enterprises A and C belonging to the community identified by the community ID = 03. Or, the disclosure range of recruitment case 002 can be limited only to enterprises C, D, and E belonging to the community identified by the community ID = 02. Or, the disclosure range of case 003 can be limited to enterprises C, D, and E belonging to the community identified by the community ID = 02 and enterprises A and C belonging to the community identified by the community ID = 03.

[0325] Enterprise A can also form a community different from the community identified by the community ID = 01 or 02. For example, as shown by the dotted line in Figure 20 , enterprise A can form a community identified by the community ID = Z with enterprise Z. For example, when the recruiter belongs to enterprise A, the recruiter's recruitment case can be publicly disclosed to the applicants belonging to enterprise A and the applicants belonging to enterprise Z. Such a disclosure level can also be adopted as a variant of "level 3" as shown in Figure 20 .

[0326] In this case, "level 3" corresponds to "allowing the disclosure of asset information to the applicants belonging to the first group (enterprise A) and a specific community group (the community identified by the community ID = Z) different from the second level and having a community relationship with the first group (enterprises A to C), and prohibiting the disclosure of asset information to the applicants who do not belong to any of the first group and the specific community group".

[0327] Here, as an example of multiple levels, levels 1 to 3 are illustrated. However, as the public levels of multiple types, more levels can also be set. As an example of an interface for the recruiter to set the public scope, a screen showing check boxes for setting the desired level from multiple types of levels may also be displayed on the user device 500.

[0328] [Details of Asset Content]

[0329] Figure 21 FIG. is a diagram showing the details of the asset content included in the recruitment case database 124. As Figure 21 shown, the asset content (case key points) is registered in the recruitment case database 124 by case ID.

[0330] The asset content includes items such as the case name (asset title), case details (detailed information), case registrant, and case-registering company. The case name records the title of the asset related to the recruitment case. The case details include an article (detailed information) that details the content of the recruitment case. In this article, the conditions required for the applicant who accepts the transfer of the asset may be included. The case registrant refers to the person who registered the case, that is, the recruiter. The case-registering company refers to the company to which the case registrant belongs.

[0331] The asset content is made public to users (applicants) who are permitted to view the cases corresponding to the asset content. In the article included in the case details, in-house company terms may sometimes be used. Such in-house company terms in the article are registered in the recruitment case database 124 in a manner associated with the in-house company terms in the in-house company term database 137 described later as "index information".

[0332] As already used Figure 1 as described, the user device 500 displays the in-house company terms in a display manner different from other terms. Thereby, the user understands that these are in-house company terms. And the user device 500 displays the meaning of the in-house company terms on the screen 550 according to the user's operation (for example, a click operation on the in-house company term part).

[0333] The applicant studies the asset content of each case and decides on the case to which they want to apply from a large number of cases. Before finally applying for a case, the applicant may conduct an interview with the recruiter of the case as needed. In addition, the recruiter may conduct an interview with the temporary assignee after selecting a specific person from the applicants as the temporary assignee and before completing the transaction.

[0334] The user device 500 may also provide a Web conference environment for the recruiter and the applicant to conduct these interviews. When an article containing in-house company terms is displayed on the monitor during a Web conference, the user device 500 may alsoFigure 1 Displays the in-company terms in the manner shown.

[0335] [Other databases]

[0336] Next, in addition to Figure 2 the various databases 121 to 124, 126, 127 shown, other databases adopted in this embodiment will also be described.

[0337] Figure 22 is a diagram showing an example of the profile database 129. As Figure 22 shown, in the profile database 129, the profile information of members (users) is registered by member ID. A part of the profile information may overlap with the information registered in the member database 122. The profile information includes the name, age, and gender of the member. The profile information also includes the affiliation information that can determine the affiliation (company and department) of the member. The affiliation information is an example of group information for determining either a company or a department within a company.

[0338] Moreover, the profile information includes the possession ability information of the member. The possession ability information of the member is classified by skill, experience, and qualification.

[0339] Figure 23 is a diagram showing an example of the in-company terms database 137. As Figure 23 shown, in the in-company terms database 137, the in-company terms information is registered by company ID. The shared server 100 determines the in-company terms by company by referring to the in-company terms database 137.

[0340] The in-company terms information includes the affiliation information that can determine the affiliation (company and department) of the member. The affiliation information is an example of group information for determining either a company or a department within a company. The affiliation information can also be said to be information indicating the company and department where the in-company terms to be registered are popular.

[0341] The in-company terms information also includes the "name", "pronunciation", and "meaning" of the terms to be registered. For example, in the case of the in-company term "DX", "DX" is registered in the "name", "ディーエックス" is registered in the "pronunciation", and "Creates some new value regardless of whether digital technology is used" is registered in the "meaning".

[0342] As another example of in-company terms, for instance, "application development" can be cited. "Application development" is generally understood to mean developing application programs used in electronic devices such as smartphones. However, in a certain department of an enterprise dealing with electronic components, "application development" may mean "exploring the uses of components". In this case, the term name "application development" and its meaning (exploring the uses of components) are registered in the in-company terms database 137.

[0343] [Explanation of the processing procedures related to the indexing function]

[0344] Next, with reference to Figures 24 - 27 the various processing procedures related to the indexing function will be explained. Figure 24 is a flowchart showing the processing procedures related to the indexing function of the matching system 1.

[0345] In Figure 24 the flowchart shown, first, the shared server 100 registers in-company terms in the in-company terms database 137 (step Sw1). In step Sw1, the shared server 100 functions as an in-company terms registration section. Next, the shared server 100 registers the recruitment cases in the recruitment case database 124 (step Sw2). In step Sw2, the shared server 100 functions as a case registration section. When registering the recruitment cases in the recruitment case database 124, the case registration section attaches indexes to the in-company terms included in the recruitment case information.

[0346] Next, the shared server 100 displays the case information with indexes attached on the screen 550 of the user device 500 (refer to Figure 1 )(step Sw3). For example, when an in-company term is used in the article explaining the case details, the article with the in-company term underlined is displayed on the screen 550. Instead of underlining the in-company term, the in-company term can also be displayed on the screen 550 in a color different from other words, or in addition to underlining the in-company term, the in-company term can also be displayed on the screen 550 in a color different from other words. In step Sw3, the shared server 100 functions as a display section.

[0347] Figure 25 is a flowchart showing the processing procedures of the in-company terms registration section (Sw1). First, the person in charge of the enterprise summarizes the in-company terms using the company's system, etc. (step Sw11). That is to say, the person in charge creates something like a set of in-company terms. Next, the person in charge downloads the registration template from the shared server 100 (step Sw12). Next, the person in charge inputs the necessary items in the template (step Sw13). The necessary items include the in-company term, the meaning of the in-company term, and the meaning of the in-company term.

[0348] Next, the person in charge of the enterprise accesses the shared server 100 and obtains the profile information of the person in charge from the profile database 129 (step Sw14). The enterprise ID of the enterprise to which the person in charge belongs is included in the profile information. The person in charge uploads the template together with the profile information to the matching system 1 (step Sw15). The shared server 100 obtains the profile information and the template. The shared server 100 generates in-company term information based on the obtained profile information and template, and registers the generated in-company term information in the in-company term database 137 (step Sw16). Thus, the in-company terms and the meanings of the in-company terms are registered in the in-company term database 137. In addition, the in-company terms and the meanings of the in-company terms are registered in the in-company term database 137 by enterprise.

[0349] The processes of steps Sw11 to Sw16 are executed for each enterprise. Thus, the in-company term information is registered in the in-company term database 137 for each enterprise. In addition, the shared server 100 may also register the in-company terms in the in-company term database 137 from an external file such as a CSV (Comma Separated Value) file.

[0350] Figure 26 It is a flowchart showing the processing procedure of the case registration department (Sw2). First, a recruiter who wants to register a recruitment case in the system accesses the profile database 129 to obtain the enterprise information of the recruiter himself / herself (step Sw21). Next, the recruiter inputs the case information into the user device 500 (step Sw22). Various information such as the case content registered in the recruitment case database 124 is included in the case information. The recruiter may use in-company terms that are popular in the enterprise to which the recruiter belongs to input the details of the case content.

[0351] Next, the shared server 100 automatically retrieves the in-company terms included in the input case information (step Sw23). At this time, the shared server 100 attaches an index to the in-company terms found through the retrieval to associate them with the in-company term information registered in the in-company term database 137. Next, the shared server 100 registers the case information input by the recruiter in the recruitment case database 124 (step Sw24). Thus, the case information is registered in the recruitment case database 124 in a state where the in-company terms are associated with the meanings of the in-company terms.

[0352] Figure 27It is a flowchart showing the processing procedure for displaying the meaning of in-company terms on the screen according to the operations of the applicant. Here, the processing for providing matching cases that match the applicant and, if necessary, teaching the applicant the meaning of in-company terms in consideration of the disclosure scope of the recruitment case will be described.

[0353] First, the shared server 100 receives a retrieval request for a recruitment case sent by the applicant (step Sw101). Next, the shared server 100 determines the affiliation of the applicant (step Sw102). The details of this processing have already been described as step S1451.

[0354] Next, the shared server 100 extracts matching cases (cases that can be disclosed) (step Sw105). The details of this processing have already been described as step S1452. Next, the shared server 100 sends the matching cases (step Sw106). The details of this processing have already been described as step S1455. In this way, the shared server 100 displays the matching cases on the applicant device 300 by sending the matching cases to the applicant device 300.

[0355] Next, the shared server 100 detects a click operation on an in-company term corresponding to the registered index (step Sw107). Next, the shared server 100 refers to the in-company term database 137 and sends the meaning of the in-company term to the applicant device 300 (step Sw108). Next, the applicant device 300 displays the meaning of the in-company term on the display 305 (step Sw109). Thus, for example, the screen 550 shown is displayed on the display 305. In this way, the shared server 100 displays the meaning of the in-company term on the applicant device 300 by sending the meaning of the in-company term to the applicant device 300. Figure 1 shown screen 550. In this way, the shared server 100 displays the meaning of the in-company term on the applicant device 300 by sending the meaning of the in-company term to the applicant device 300.

[0356] As described above, according to the present embodiment, a matching system 1 that functions as a crowdsourcing platform can be provided. In order to find an appropriate transfer destination related to the surplus assets by crowdsourcing, it is desirable to further expand the scope of crowdsourcing rather than limiting the scope to within a specific company or a small number of companies. In this case, it is necessary to consider the interests of the recruiter who recruits assignees for cases related to assets and the applicants who apply for the recruitment. In the present embodiment, the shared server 100 communicates with the applicant device 300 operated by the applicant via the communication interface 104. The shared server 100 registers asset information representing an object of the asset and public information representing the public scope of the asset information in the database (step S1442). The shared server 100 determines the asset information registered in the database 120 that is allowed to be disclosed to the applicant based on the public information (step S1452). The asset information includes detailed information related to the content of the asset (case content (transaction points)). The shared server 100 displays the asset information allowed to be disclosed to the applicant and the meanings of the terms included in the detailed information (internal terms including in-company terms) on the applicant device 300 (steps Sw3, Sw106, Sw109).

[0357] Therefore, according to the present embodiment, an appropriate applicant can be selected considering the interests of the recruiter and the applicant. And, according to the present embodiment, it is possible to prevent the applicant from misunderstanding the content of the asset information due to unfamiliar terms or terms used with a meaning different from the normal case.

[0358] In addition, according to the present embodiment, when the user exchanges information related to the case with users outside the company, the effort of supplementing the in-company terms can be reduced. And the shared server 100 can automatically attach an index to the in-company terms included in the case information. Therefore, the user does not need to manually attach an index to the in-company terms. And the shared server 100 has a function of registering the in-company terms in the in-company term database 137. Therefore, the user does not need to manually register the in-company terms in the in-company term database 137. And since the user can recognize that other companies do not understand the in-company terms, the user can grasp the cultural differences with other companies.

[0359] In the present embodiment, as an example of the "internal terms" popular in the group to which the user belongs, "in-company terms" for enterprises are cited. However, instead of or in addition to "in-company terms", the embodiments described so far can be applied to terms similar to in-company terms used in non-profit organizations, communities, and units (departments, employees, etc.) within them.

[0360] In the embodiment described above, "each enterprise group" and "each department group within the same enterprise" are examples of "groups". Applicants who are not affiliated with an enterprise, such as freelancers, can also form a "group". An "enterprise group" can also be composed of multiple enterprises.

[0361] The communication ( Figure 11 S9) for sending approval information from the applicant device 300 of the manager who functions as an approver to the approval department 147 is carried out in a logical communication path identified by the member ID of the approver. "The approval department 147 receives approval information in such a communication path" is an example of "receiving an approval notice in a communication accompanied by the identification information of the approver of the first applicant".

[0362] In this embodiment, the "applicant evaluation summary" registered in the evaluation summary database 127 is an example of "evaluation information based on evaluations received from the recruiter device 200 that functions as an evaluator device". In this embodiment, the "recruiter evaluation summary" registered in the evaluation summary database 127 is an example of "evaluation information based on evaluations received from the applicant device 300 that functions as an evaluator device".

[0363] In Figure 8 only an example of the data registered in the evaluation summary database 127 is shown. In this embodiment, it is also assumed that a member belonging to enterprise A evaluates members belonging to enterprises A, B, C,... and regarded as recruiters from the perspective of an applicant. In this embodiment, it is also assumed that a member belonging to enterprise B evaluates members belonging to enterprises A, B, C,... and regarded as recruiters from the perspective of an applicant. In this embodiment, it is also assumed that a member belonging to enterprise A evaluates members belonging to enterprises A, B, C,... and regarded as applicants from the perspective of a recruiter. In this embodiment, it is also assumed that a member belonging to enterprise B evaluates members belonging to enterprises A, B, C,... and regarded as applicants from the perspective of a recruiter.

[0364] In this embodiment, the "recruiter device 200A" operated by a recruiter belonging to enterprise A functions as an evaluator device and is an example of "the first recruiter device (recruitment side first evaluator device) operated by one or more evaluators belonging to the first group". In this embodiment, the "applicant device 300A" operated by an applicant belonging to enterprise A functions as an evaluator device and is an example of "the first evaluator device (applicant side first evaluation device) operated by one or more evaluators belonging to the first group".

[0365] In the present embodiment, the "recruiter device 200B" operated by a recruiter belonging to Company B functions as an evaluator device and is an example of a "second recruiter device (recruitment-side second evaluator device)" operated by one or more evaluators belonging to a second group different from the first group. In the present embodiment, the "applicant device 300B" operated by an applicant belonging to Company B functions as an evaluator device and is an example of a "second evaluator device (applicant-side second evaluation device)" operated by one or more evaluators belonging to a second group different from the first group.

[0366] In Figure 19 Company B, the system department and the planning department are exemplified as departments. In the present embodiment, "either the system department or the planning department" is an example of a "first divided group" included in the first group, and the other is an example of a "second divided group" included in the first group.

[0367] As described above, the shared server 100 determines, based on various information (member ID, company ID, community ID, list of affiliated company IDs, list of non-public company IDs, public level, non-public target) capable of determining the relationship between the applicant and the recruiter, the asset information of the recruitment case registered in the database 120 that is allowed to be disclosed to the applicant, and provides the applicant with the asset information allowed to be disclosed to the applicant. According to the present embodiment, an appropriate applicant can be selected considering the interests of the company to which the recruiter belongs and the company to which the applicant belongs in terms of the transfer destination or utilization destination of the recruitment assets. As a result, it is possible to prevent the secret information of the company on the recruiter side from being leaked to competing companies through the content of the assets related to the recruitment case.

[0368] The "company" and the "department within the same company" in the present embodiment are examples of the "group of recruiters" and the "group of applicants", and they are examples of "groups". Applicants who do not belong to a company can also form a "group". A "company group" can also be composed of multiple companies.

[0369] In the present embodiment, the "companies forming a community relationship" is an example of a "community group". In the present embodiment, the information of the "non-public target" included in the public information is an example of the "information capable of determining the target person prohibited from disclosing the asset information".

[0370] "Level 1" in the disclosure level of this embodiment corresponds to the level of "allowing the disclosure of asset information to the first applicant and prohibiting the disclosure of asset information to applicants who do not belong to the first group". "Level 2" corresponds to the level of "allowing the disclosure of asset information to applicants belonging to any group among the first group and the community groups that have formed a community relationship with the first group, and prohibiting the disclosure of asset information to applicants who do not belong to either the first group or the community groups". "Level 3" corresponds to the level of "allowing the disclosure of asset information to applicants regardless of the group to which the applicant belongs".

[0371] The recruiter device 200 and the applicant device 300 may also be not only equipped with all of the processors, memories, communication interfaces, and input / output interfaces shown, but also a thin client system that utilizes VDI (Virtual Desktop Infrastructure). A thin client system that utilizes VDI is a system that transmits the desktop environment located on the server to a remote terminal for use. The recruiter device 200, the applicant device 300, and the shared server 100 do not have to be independent devices. In the case of using the thin client system as described above, the functions of the recruiter device 200, the applicant device 300, and the shared server 100 can be provided on the same integrated server. Figure 2 The database 120 is not limited to a relational database, and an object database, a NoSQL database, etc. can also be used.

[0372] The shared server 100 is an example of a computing device. The computing device can also be composed of a server (On-Premises Server, cloud server, etc.), a serverless system, etc. Here, the local server refers to a server that is set up and managed within the equipment managed by the company. The cloud server refers to a server provided by other operators through the network (rented server). The serverless system refers to a system that is unaware of the existence of the server and can utilize the computing and memory functions only when needed. The computing device includes a server and a serverless system. The server includes a local server and a cloud server.

[0373]

[0374] <Modification Example 1>

[0375] Figures 28 - 32 Next, refer to to explain Modification Example 1. Here, the sharing function of assets related to a recruitment case that can be shared by multiple applicants will be described.

[0376] Figure 28 Figure 28 FIG. is an example of a recruitment case database 124A related to Modification Example 1. Figure 28The recruitment case database 124A shown is obtained by adding functions for registering "recruitment method" and "shared establishment conditions" to the Figure 6 recruitment case database 124 shown.

[0377] As the "recruitment method", information indicating whether the recruitment method of the recruitment case is set to "shared", "individual", or "unrestricted" is registered.

[0378] Recruitment cases with the recruitment method set to "shared" must be applied for by multiple applicants who meet the "shared establishment conditions". For recruitment cases set to "shared", the "shared establishment conditions" are registered. The recruiter can set various "shared establishment conditions". In Figure 28 a setting example of the shared establishment conditions is shown. The shared establishment conditions set by the recruiter are registered in the recruitment case database 124A.

[0379] For example, when the shared establishment conditions for the training of case 003 are set to 5 companies, in the case where 5 companies apply for case 003, the recruiter grants the right to use the training corresponding to case 003 to each company. For example, the employees of the 5 companies granted the right to use are allowed to go to a pre-determined training venue and receive the training corresponding to case 003. In this way, the shared establishment conditions are constituted by conditions related to the number of applicants for shared assets.

[0380] Recruitment cases with the recruitment method set to "individual" are cases where multiple applicants are not permitted to "share". Case 001, case 002, and case 004 are equivalent to such cases. Those who want to obtain a recruitment case set to "individual" need to recruit the case individually. For recruitment cases with the recruitment method set to "individual", the "shared establishment conditions" are not registered (BLANK).

[0381] Recruitment cases with the recruitment method set to "unrestricted" are cases where individual applicants and multiple applicants are both permitted to apply. Case 005 is equivalent to such a case. For those who apply for a recruitment case set to "unrestricted", each person decides the number of applications within the range of the recruitment quantity. Recruitment ends when the total number of applications of each applicant reaches the recruitment quantity. For recruitment cases with the recruitment method set to "unrestricted", the "shared establishment conditions" are not registered (BLANK).

[0382] Figure 29 It is a diagram related to Modification Example 1 for explaining the process of registering a recruitment case in the recruitment case database. In Figure 29 it, compared with Figure 13 the asset information input to the recruiter device 200, the recruitment method and the shared establishment conditions are added.

[0383] In Modification 1, when registering a recruitment case, the recruiter of the recruitment case can include the recruitment method and the sharing establishment conditions of the recruitment case in the asset information when inputting the asset information and the public information of the recruitment case into the recruiter device 200. As already described, the recruitment method is any one of sharing, individual, and unrestricted. When the recruiter sets the recruitment method to sharing, the sharing establishment conditions are input.

[0384] The case registration unit 144 of the sharing server 100 registers the recruitment case in the recruitment case database 124A in a manner including the recruitment method and the sharing establishment conditions selected by the recruiter (step S1442). Figure 29 The other content shown is the same as that already described Figure 13 and thus its description will not be repeated here.

[0385] The information of "recruitment method" is an example of "recruitment method information that can determine that the asset is a shared asset where multiple applicants are selected as the transfer destination or utilization destination of the asset". The sharing server 100 registers the information of "recruitment method" in the recruitment case database 124A corresponding to other asset information. The sharing server 100 also registers the "sharing establishment conditions" in the recruitment case database 124A corresponding to the information of "recruitment method".

[0386] [Processing procedure corresponding to the recruitment method of "sharing" (first determination processing)]

[0387] Figure 30 is a flowchart showing the processing procedure of the first determination processing related to Modification 1. Use Figure 30 the shown flowchart to explain the processing procedure of the recruitment case corresponding to the recruitment method of "sharing". The processing based on this flowchart is executed by the sharing server 100. The sharing server 100 executes the processing based on this flowchart every time it receives an application for a recruitment case.

[0388] First, the sharing server 100 receives an application for a recruitment case (step Sa1). Next, the sharing server 100 determines whether the recruitment method of the recruitment case with an application is "sharing" (step Sa2). If the recruitment method of the recruitment case with an application is not "sharing", the sharing server 100 ends the processing based on this flowchart.

[0389] If the recruitment method of the recruitment case with an application is "sharing", the sharing server 100 updates the determination parameter for the sharing establishment conditions (step Sa3). The determination parameter for the sharing establishment conditions is different for each recruitment case.

[0390] For example, when the sharing establishment condition is set to "5 companies", the determination parameter is the number of companies of the applicants. Whenever there is an application, the sharing server 100 determines the company of the applicant. For example, whenever there are applications from different companies such as Company A, Company B, Company C, etc., the sharing server 100 increments the determination parameter by 1.

[0391] Next, the sharing server 100 determines whether the determination parameter satisfies the sharing establishment condition (step Sa4). For example, when the sharing establishment condition is set to "5 companies", the sharing server 100 determines that the determination parameter satisfies the sharing establishment condition when the determination parameter = 5. If the determination parameter does not satisfy the sharing establishment condition, the sharing server 100 ends the process based on this flowchart.

[0392] If the determination parameter satisfies the sharing establishment condition, the sharing server 100 notifies all the applicants and the recruiter for the recruitment case that the sharing establishment condition is established (step Sa5). That is, when the sharing establishment condition is established, the sharing server 100 determines the applicants for the sharing-type recruitment case. Next, the sharing server 100 accepts the input of consent / rejection from the recruiter (step Sa6) and ends the process based on this flowchart. Thereafter, the process using Figure 10 the notification unit 148 described is executed.

[0393] [Processing procedure corresponding to the recruitment method "individual" (second determination process)]

[0394] Figure 31 It is a flowchart showing the processing procedure of the second determination process related to Modification 1. The flowchart shown in Figure 31 is used to explain the processing procedure for the recruitment case corresponding to the recruitment method "individual". The sharing server 100 executes the process based on this flowchart. The sharing server 100 executes the process based on this flowchart whenever it receives an application for a recruitment case.

[0395] First, the sharing server 100 receives an application for a recruitment case (step Sa21). Next, the sharing server 100 determines whether the recruitment method of the recruitment case with an application is "individual" (step Sa22). If the recruitment method of the recruitment case with an application is not "individual", the sharing server 100 ends the process based on this flowchart.

[0396] When the recruitment method for a recruitment case with applications is "individual", the shared server 100 determines whether the quantity of assets the recruiter wants is the same as the recruitment quantity (step Sa23). When the quantity of assets the recruiter wants is not the same as the recruitment quantity, the quantity the applicant wants is less than the recruitment quantity of the recruiter. In this case, the shared server 100 ends the processing based on this flowchart. As a result, the applicant's application is not accepted.

[0397] When the quantity of assets the recruiter wants is the same as the recruitment quantity, the shared server 100 notifies the recruiter that there is an application (step Sa24). Then, the shared server 100 accepts the input of consent / rejection from the recruiter (step Sa25) and ends the processing based on this flowchart. Thereafter, the processing of the notification unit 148 described Figure 10 is executed.

[0398] [Processing procedure corresponding to "unrestricted" recruitment method (third determination processing)]

[0399] Figure 32 is a flowchart showing the processing procedure of the third determination processing related to Modification 1. The flowchart shown in Figure 32 is used to explain the processing procedure for a recruitment case corresponding to the "unrestricted" recruitment method. The shared server 100 executes the processing based on this flowchart. The shared server 100 executes the processing based on this flowchart every time it receives an application for a recruitment case.

[0400] First, the shared server 100 receives an application for a recruitment case (step Sa31). Then, the shared server 100 determines whether the recruitment method of the recruitment case with an application is "unrestricted" (step Sa32). When the recruitment method of the recruitment case with an application is not "unrestricted", the shared server 100 ends the processing based on this flowchart.

[0401] When the recruitment method of the recruitment case with an application is "unrestricted", the shared server 100 determines whether an application from another applicant has been accepted for this recruitment case (step Sa33). When an application from another applicant has not been accepted, it is the first application for this recruitment case. In this case, the shared server 100 determines whether the quantity of assets the applicant wants is the same as the recruitment quantity (step Sa34).

[0402] When the number of assets desired by the applicant is the same as the recruitment number, there is no need to wait for the applications of other applicants. In this case, the sharing server 100 notifies the recruiter that there is an application from the applicant (step Sa35). Then, the sharing server 100 accepts the input of consent / rejection from the recruiter (step Sa36), and ends the process based on this flowchart. Thereafter, the process using Figure 10 the notification unit 148 described

[0403] When the number of assets desired by the applicant is not the same as the recruitment number, the sharing server 100 confirms the case where the number of assets desired by the applicant is less than the recruitment number (step Sa37). When the number of assets desired by the applicant is more than the recruitment number, the sharing server 100 does not accept the application and ends the process based on this flowchart.

[0404] When the number of assets desired by the applicant is less than the recruitment number, the sharing server 100 associates the applicant with the desired quantity, and stores it together with the corresponding recruitment case (step Sa38). Then, the sharing server 100 calculates "recruitment number - desired quantity" to obtain the remaining recruitment quantity (step Sa39).

[0405] The sharing server 100 stores the remaining recruitment quantity corresponding to the recruitment case. Thereafter, the sharing server 100 waits for new applications. When a new application is generated for the same recruitment case, the sharing server 100 determines "yes" in step Sa33. The sharing server 100 compares the remaining recruitment quantity stored corresponding to the same recruitment case with the quantity of assets desired by the applicant in the new application. When the desired quantity is more than the remaining recruitment quantity, the sharing server 100 does not accept the application and ends the process based on this flowchart.

[0406] When the desired quantity is not more than the remaining recruitment quantity, the sharing server 100 stores the new applicant corresponding to the desired quantity (step Sa41). Then, the sharing server 100 updates the remaining recruitment quantity by subtracting the new desired quantity from the remaining recruitment quantity (step Sa42). The sharing server 100 determines whether the updated remaining recruitment quantity has become 0 (step Sa43).

[0407] When the updated remaining recruitment quantity does not become 0, the total of the desired quantities of multiple applicants does not reach the recruitment number. In this case, it is necessary to wait for new applicants for assets with a quantity less than the recruitment number. Therefore, in this case, the sharing server 100 temporarily ends the process based on this flowchart and waits for applications for the same recruitment case.

[0408] In the case where the remaining number of recruits after the update becomes 0, "recruitment quantity = total value of desired quantities" holds based on the previous applications and new applications. In this case, the sharing server 100 notifies the recruiter of the application and accepts the input of consent / rejection from the recruiter (step Sa35, step Sa36). Thereafter, the process of the notification unit 148 described in Figure 10 is executed.

[0409] As described above, according to Modification Example 1 related to the sharing function, assets related to a recruitment case can be shared by multiple applicants. By adding the sharing function to the embodiment described above, multiple applicants can thus obtain assets related to the recruitment case.

[0410] Moreover, in the present embodiment, when an applicant retrieves a recruitment case, a recruitment case that does not cause disadvantages to the recruiter is provided to the applicant (refer to Figure 14 ). Therefore, according to the matching system 1 to which Modification Example 1 is applied, disadvantages to the recruiter can be prevented regardless of whether the assets related to the recruitment case are shared by multiple applicants or obtained by a single applicant.

[0411] In the case where the target of the recruitment case is an educational course such as training that can be shared by multiple companies, it is not desirable to include competitor companies among multiple applicants. This is because information on the educational field to which the company as the recruiter is committed will be leaked to competitor companies through the content of the educational course. According to the matching system 1 to which Modification Example 1 is applied, even in the case where such an educational course is set as the recruitment case, disadvantages to the recruiter can be prevented.

[0412] In addition, in Modification Example 1, the burden amount per applicant can also be reduced as the number of applicants sharing the recruitment case increases. For example, in the case where the target of the recruitment case is training, the amount obtained by dividing the amount of the recruitment case set in advance by the number of applicants can also be used as the burden amount per applicant, and as the number of applicants increases, the burden amount per applicant decreases.

[0413] <Modification Example 2>

[0414] Figure 33 is a diagram showing the structure of the matching system 1A related to Modification Example 2. As Figure 33 shown, the functions of the sharing server 100 can also be distributed and configured in systems within each company. That is, as the matching system 1, a distributed management type matching system 1A can also be adopted instead of the centralized management type matching system 1.

[0415] Figure 33The system structure shown is common among enterprises A, B, C, D, ···. In each enterprise, a user device 500, a database 520, and a storage device 503 for storing the database are configured. When a member operates the user device 500 as a recruiter, the user device 500 functions as a recruiter device 200. When a member operates the user device 500 as an applicant, the user device 500 functions as an applicant device 300.

[0416] The user device 500 is constituted by a server, for example. The user device 500 is an example of a computing device including a recruiter device 200 and an applicant device 300. The user device 500, like the recruiter device 200 and the applicant device 300, includes a processor, a memory for storing programs required for the arithmetic processing of the processor, and a communication interface, etc.

[0417] The database 520 has Figure 2 the functions of the database 120 shown, including a recruitment case database 524 replacing the recruitment case database 124 and various other databases. In the recruitment case database 524 of enterprise A, recruitment cases submitted by employees of enterprise A, etc. as recruiters are registered. In the recruitment case database 524 of enterprise B, recruitment cases submitted by employees of enterprise B, etc. as recruiters are registered. Similarly, in the recruitment case databases 524 of other enterprises, recruitment cases submitted by employees of each company, etc. as recruiters are registered.

[0418] A public permission list 521 is registered in the database 520. The public permission list 521 contains a list of groups (enterprises, communities, etc.) permitted to publicly recruit cases. The public permission list 521 contains Figure 6 the information corresponding to the "non-public enterprise ID list" and the "public level" in the information registered in the recruitment case database 124 shown. The user device 500 registers recruitment cases (asset information) and the public permission list 521 (public information) indicating the public scope of the recruitment cases in the database 520.

[0419] The user device 500 of enterprise A determines the enterprises or communities to which the recruitment cases are to be made public and the enterprises or communities to which the recruitment cases are not to be made public based on the public permission list 521. Based on this determination, the user device 500 of enterprise A sends the recruitment cases to each enterprise or each community. For example, when the user device 500 of enterprise A determines to make a certain recruitment case public to enterprise C and not to enterprises B and D, it sends the recruitment case to enterprise C and does not send the recruitment case to enterprises B and D.

[0420] The user devices 500 of enterprises B, C, D, etc. also operate based on the public permission list 521 in the same way as the user device 500 of enterprise A. In this way, the user device 500 determines, based on the public permission list 521, the recruitment cases registered in the database 520 that are allowed to be disclosed to the applicants, and provides the recruitment cases allowed to be disclosed to the applicants to the applicant device 300.

[0421] According to Modification Example 2, there is no need to set up a server in the matching system for centralized system management.

[0422] <Modification Example 3>

[0423] Use Figure 34 Describe Modification Example 3. Figure 34 FIG. is a diagram showing an example (Modification Example 3) in which Kerberos authentication is applied in the matching system 1A. It can also be as Figure 34 shown, apply Kerberos authentication to the authentication between enterprises in the matching system 1A. Kerberos authentication is one of the network authentication methods applied between a server and a client.

[0424] Here, take enterprises A and C among multiple enterprises as examples to describe Modification Example 3. As Figure 34 shown, an authentication system 510A is configured in enterprise A, and an authentication system 510C is configured in enterprise C. The authentication system 110 is a KDC (Key Distribution Center: Key Distribution Center). The authentication system 110 is operated by an authentication agency, for example. The authentication system 110 is composed of a server configured in the authentication agency. The authentication systems 510A and 510C are composed of user devices 500 (refer to Figure 33 ).

[0425] The authentication system 110 has the function of issuing a TGT (Ticket Granting Ticket: Ticket Granting Ticket). The authentication system 110 includes an AS (Authentication Server: Authentication Server) and a TGS (Ticket Granting Server: Ticket Granting Server). The AS issues a TGT (Ticket Granting Ticket: Ticket Granting Ticket). The TGT is a ticket required to obtain a service ticket. The TGS issues a service ticket. Enterprise A can send data to enterprise C by obtaining a service ticket.

[0426] Here, an example of sending a recruitment case to Company C after Kerberos authentication is performed at Company A is described. Thus, here, Company A is the recruiter and Company C is the applicant. First, the authentication system 510A requests an authentication procedure from the authentication system 110 (step Sk101). For example, the authentication system 510A sends information required for authentication, such as the ID and password for login, to the AS of the authentication system 110. The authentication system 510A can also use the method of publicly authenticating keys in the authentication procedure.

[0427] After the AS of the authentication system 110 performs authentication based on the information received from the authentication system 510A, it sends the TGT to the authentication system 510A (step Sk102). The authentication system 510A performs permission authentication for the case and obtains permission for issuing a service ticket (step Sk103).

[0428] Next, the authentication system 510A requests a service ticket for Company C from the TGS of the authentication system 110 (step Sk104). At this time, the authentication system 510A presents the TGT issued by the AS to the TGS. After verifying the TGT, the TGS sends a service ticket for Company C to the authentication system 510A (step Sk105).

[0429] Next, in order to obtain permission to send from Company C, the authentication system 510A sends a service ticket to the authentication system 510C of Company C (step Sk106). The authentication system 510C obtains the service ticket. The authentication system 510C sends permission to send data to the authentication system 510A (step Sk107).

[0430] After that, the authentication system 510A sends to the authentication system 510C the recruitment cases registered in the recruitment case database 524 and publicly permitted to be disclosed to Company C by the public permission list 521. Thus, Company A can enable the applicants of Company C to view the recruitment cases of its own company. In addition, instead of storing the public permission list 521 of its own company in each company, the public permission list 521 of all companies can be stored in the authentication system 110. In this case, the authentication system 110 has a function of determining the browsing authority of recruitment cases.

[0431] When Kerberos authentication is applied in the matching system 1, Company A can simplify the authentication procedure when sending cases to other companies other than Company C by using the obtained TGT. For example, when wanting to send a case to Company D, the authentication system 510A of Company A presents the obtained TGT and then requests a service ticket for Company D from the TGS. If there is no problem with the TGT, the TGS issues a service ticket for Company D to the authentication system 510A.

[0432] By using the Kerberos authentication described above, a single sign-on method can be installed in the matching system 1. As a result, for example, when sending data such as recruitment cases from Company A to other companies, there is no need to authenticate for each company. In addition, here, as an example of multiple enterprises, Companies A and C are shown. However, as an authentication method among three or more enterprises, the Kerberos authentication described above can also be applied.

[0433] The present embodiment described above has the following structures.

[0434] (a) In the matching system, a recruiter device operated by a recruiter sends asset information (case information) for recruiting an assignee and public information indicating the public scope of the asset information to a computing device. The computing device registers the asset information together with the public information in a database, and the computing device determines, based on the public information, the asset information among the asset information registered in the database that is allowed to be publicly disclosed to a first applicant, and provides the asset information allowed to be publicly disclosed to the first applicant to a first applicant device.

[0435] (b) In the matching system, there is also a second applicant device operated by a second applicant different from the first applicant. The computing device determines, based on the public information, the asset information among the asset information registered in the database that is allowed to be publicly disclosed to the second applicant, and provides the asset information allowed to be publicly disclosed to the second applicant to the second applicant device.

[0436] (c) In the matching system, the matching system also has a third applicant device operated by a third applicant who is different from the first applicant and the second applicant, and multiple public levels are set for the public information. The computing device determines whether to allow public disclosure for the first applicant, the second applicant, and the third applicant respectively according to the public level.

[0437] (d) In the matching system, the first applicant belongs to a first group, the second applicant belongs to a second group different from the first group, and the multiple public levels include a first level and a second level. The first level corresponds to the following situation: allowing the asset information to be publicly disclosed to the first applicant and prohibiting the asset information from being publicly disclosed to applicants who do not belong to the first group. The second level corresponds to the following situation: allowing the asset information to be publicly disclosed to applicants who belong to any group among the first group and a community group that has formed a community relationship with the first group, and prohibiting the asset information from being publicly disclosed to applicants who do not belong to any of the first group and the community group.

[0438] (e) In the matching system, the first applicant belongs to the first group, the second applicant belongs to the second group different from the first group, and the multiple disclosure levels include the first level, the second level, and the third level. The first level corresponds to the following situation: allowing the disclosure of asset information to the first applicant and prohibiting the disclosure of asset information to applicants who do not belong to the first group. The second level allows the disclosure of asset information to applicants who belong to any group among the first group and the community groups that have formed a community relationship with the first group. The third level corresponds to the following situation: allowing the disclosure of asset information to applicants who belong to the first group and a specific community group that is different from the second level of community groups that have formed a community relationship with the first group, and prohibiting the disclosure of asset information to applicants who do not belong to any of the first group and the specific community group.

[0439] (f) In the matching system, the multiple disclosure levels include a disclosure level corresponding to the following situation: allowing the disclosure of asset information to the applicant regardless of the group to which the applicant belongs.

[0440] (g) In the matching system, attribute data capable of determining the community group is registered in the database, and the computing device determines the applicant to whom the disclosure of asset information is permitted based on the public information and the attribute data.

[0441] (h) In the matching system, the recruiter device accepts an operation for inputting a target group for which the disclosure of asset information is prohibited, and sends information capable of determining the accepted target group to the computing device. Even if the disclosure level is a level that allows the disclosure of asset information to the target group, the computing device prohibits the disclosure of asset information to applicants who belong to the target group.

[0442] (i) In the matching system, the first applicant belongs to the first enterprise, and the second applicant belongs to the second enterprise different from the first enterprise.

[0443] (j) In the evaluator device operated by one or more evaluators belonging to the first group, it includes: an interface for accepting an operation for inputting an evaluation of the applicant; a reception unit for accepting a browsing request; a display; and a processor that sends the evaluation accepted by the interface and the browsing request accepted by the reception unit to a computing device capable of accessing the database. In the case of a browsing request, the processor displays the evaluations of one or more evaluators belonging to the first group on the display.

[0444] (k) A method for evaluating applicants includes the following steps: communicating with a first evaluator device operated by one or more evaluators belonging to a first group; receiving an evaluation of an applicant from the first evaluator device; registering first evaluation information based on the evaluation received from the first evaluator device in a database; and when a browsing request is received in a first communication established based on identification information capable of identifying a person belonging to the first group, sending the first evaluation information to the sender that sent the browsing request in the first communication.

[0445] (l) In an evaluator device operated by one or more evaluators belonging to a first group, there are provided: an interface for accepting an operation of inputting an evaluation of a recruiter; a reception unit for accepting a browsing request; a display; and a processor for sending the evaluation accepted by the interface and the browsing request accepted by the reception unit to a computing device capable of accessing the database, wherein when there is a browsing request, the processor displays the evaluations of one or more evaluators belonging to the first group on the display.

[0446] (m) A method for evaluating a recruiter includes the following steps: communicating with a first evaluator device operated by one or more evaluators belonging to a first group; receiving an evaluation of the recruiter from the first evaluator device; registering first evaluation information based on the evaluation received from the first evaluator device in a database; and when a browsing request is received in a first communication established based on identification information capable of identifying a person belonging to the first group, sending the first evaluation information to the sender that sent the browsing request in the first communication.

[0447] (n) In a computing device included in a matching system for matching a recruiter with an applicant, there are provided: a communication interface for communicating with a first applicant device operated by a first applicant; and a processor for accessing the database, wherein the processor registers asset information of an object representing an asset and public information representing the scope of disclosure of the asset information in the database, the processor determines, based on the public information, the asset information among the asset information registered in the database that is allowed to be disclosed to the first applicant, the asset information includes detailed information related to the content of the asset, and the processor displays the asset information allowed to be disclosed to the first applicant and the meanings of the terms included in the detailed information on the first applicant device.

[0448] (o)A method for matching a recruiter with an applicant includes the following steps: communicating with a first applicant device operated by a first applicant; registering asset information of an object representing an asset and public information representing the public scope of the asset information in a database; and determining, based on the public information, the asset information among the asset information registered in the database that is allowed to be disclosed to the first applicant, where the asset information includes detailed information related to the content of the asset. The method further includes the following steps: displaying the asset information allowed to be disclosed to the first applicant and the meanings of the terms included in the detailed information on the first applicant device.

[0449] [Mode]

[0450] The following are examples of the present disclosure.

[0451] (Item 1) The matching system described in Item 1 is used to match a recruiter with an applicant who applies for the recruitment when the holder of an asset becomes a recruiter and recruits a transfer destination or utilization destination of the asset. The matching system includes: a recruiter device operated by the recruiter; a first applicant device operated by a first applicant; and a computing device that communicates with the recruiter device and the first applicant device and can access a database. The recruiter device sends asset information of an object representing an asset and public information representing the public scope of the asset information to the computing device. The computing device registers the asset information and the public information in the database together. The computing device determines, based on the public information, the asset information among the asset information registered in the database that is allowed to be disclosed to the first applicant, and provides the asset information allowed to be disclosed to the first applicant to the first applicant device.

[0452] (Item 2) The matching system described in Item 2 is such that, in the matching system described in Item 1, it further includes a second applicant device operated by a second applicant different from the first applicant. The computing device determines, based on the public information, the asset information among the asset information registered in the database that is allowed to be disclosed to the second applicant, and provides the asset information allowed to be disclosed to the second applicant to the second applicant device.

[0453] (Item 3) The matching system described in Item 3 is such that, in the matching system described in Item 2, the matching system further includes a third applicant device operated by a third applicant different from the first applicant and the second applicant. Multiple public levels are set for the public information. The computing device determines whether disclosure is allowed for the first applicant, the second applicant, and the third applicant respectively according to the public level.

[0454] (Item 4) The matching system described in Item 4 is as follows. In the matching system described in Item 3, the first applicant belongs to the first group, the second applicant belongs to the second group different from the first group, and the multiple disclosure levels include the first level and the second level. The first level corresponds to the following situation: allowing the disclosure of asset information to the first applicant and prohibiting the disclosure of asset information to applicants who do not belong to the first group. The second level corresponds to the following situation: allowing the disclosure of asset information to applicants who belong to any group among the first group and the community groups that have formed a community relationship with the first group, and prohibiting the disclosure of asset information to applicants who do not belong to any of the first group and the community groups.

[0455] (Item 5) The matching system described in Item 5 is as follows. In the matching system described in Item 3, the first applicant belongs to the first group, the second applicant belongs to the second group different from the first group, and the multiple disclosure levels include the first level, the second level, and the third level. The first level corresponds to the following situation: allowing the disclosure of asset information to the first applicant and prohibiting the disclosure of asset information to applicants who do not belong to the first group. The second level allows the disclosure of asset information to applicants who belong to any group among the first group and the community groups that have formed a community relationship with the first group. The third level corresponds to the following situation: allowing the disclosure of asset information to applicants who belong to a community different from the second-level community groups that have formed a community relationship with the first group, and prohibiting the disclosure of asset information to applicants who do not belong to any of the first group and the community groups.

[0456] (Item 6) The matching system described in Item 6 is as follows. In the matching system described in Item 4, the multiple disclosure levels include disclosure levels corresponding to the following situation: allowing the disclosure of asset information to applicants regardless of the group to which the applicants belong.

[0457] (Item 7) The matching system described in Item 7 is as follows. In the matching system described in Item 5 or 6, attribute data capable of determining community groups is registered in the database, and the computing device determines the applicants who are allowed to disclose asset information based on public information and attribute data.

[0458] (Item 8) The matching system described in Item 8 is as follows. In the matching system described in any one of Items 3 to 7, the recruiter device accepts an operation for inputting a target group for which the disclosure of asset information is prohibited, and sends information capable of determining the accepted target group to the computing device. Even if the disclosure level is a level that allows the disclosure of asset information to the target group, the computing device prohibits the disclosure of asset information to applicants who belong to the target group.

[0459] (Item 9) The matching system described in Item 9 is such that, among the matching systems described in any one of Items 2 to 8, the first applicant belongs to the first company, and the second applicant belongs to the second company different from the first company.

[0460] (Item 10) The matching system described in Item 10 is such that, among the matching systems described in any one of Items 1 to 9, the recruiter device sends recruitment method information to the computing device that can determine that the asset is a shared asset for which one or more applicants are selected as the transfer destination or utilization destination of the asset, and the computing device registers the recruitment method information corresponding to the asset information in the database.

[0461] (Item 11) The matching system described in Item 11 is such that, in the matching system described in Item 10, the computing device registers the sharing establishment condition corresponding to the recruitment method information in the database. The sharing establishment condition is a condition related to the number of applicants for the shared asset. When the sharing establishment condition is satisfied, the computing device determines the applicants for the shared asset.

[0462] (Item 12) The matching system described in Item 12 is such that, in the matching system described in Item 1, the recruiter device includes a first recruiter device operated by one or more recruiters belonging to the first group. The first recruiter device accepts the input of the evaluation of the first applicant and sends the accepted evaluation to the computing device. The computing device registers the first evaluation information based on the evaluation received from the first recruiter device for each applicant in the database. When the computing device receives a browsing request in the first communication established based on the identification information that can identify a person belonging to the first group, the computing device sends the first evaluation information to the source that sent the browsing request in the first communication.

[0463] (Item 13) The matching system described in Item 13 is such that, in the matching system described in Item 12, the recruiter device further includes a second recruiter device operated by one or more recruiters belonging to the second group different from the first group. The second recruiter device accepts the input of the evaluation of the first applicant and sends the accepted evaluation to the computing device. The computing device registers the second evaluation information based on the evaluation received from the second recruiter device for each applicant in the database. When the computing device receives a browsing request in the second communication established based on the identification information that can identify a person belonging to the second group, the computing device sends the second evaluation information to the source that sent the browsing request in the second communication.

[0464] (Item 14) The matching system described in Item 14 is such that, in the matching system described in Item 13, the first group consists of one company, and the second group consists of the second company different from the first company.

[0465] (Item 15) The matching system described in Item 15 is such that, in the matching system described in Item 13, the first group consists of the first department of the first enterprise, and the second group consists of the second department of the first enterprise.

[0466] (Item 16) The matching system described in Item 16 is such that, in the matching system described in any one of Items 12 to 15, when the computing device receives evaluations of a specified applicant from multiple recruiters belonging to the first group, the computing device calculates the average value of the evaluations of the specified applicant by the multiple recruiters, and the computing device sends the average value as the first evaluation information of the specified applicant to the source that sent the browsing request in the first communication.

[0467] (Item 17) The matching system described in Item 17 is such that, in the matching system described in Item 16, the first group includes one or more recruiters belonging to the first segmentation group and one or more recruiters belonging to a second segmentation group different from the first segmentation group. The computing device calculates a first average value based on the evaluations of a specified order-taker received from multiple recruiters belonging to the first segmentation group, where the first average value is the average value of the evaluations of the specified applicant. The computing device calculates a second average value based on the evaluations of the specified order-taker received from multiple recruiters belonging to the second segmentation group, where the second average value is the average value of the evaluations of the specified applicant. The computing device calculates a third average value based on the evaluations of the specified order-taker received from multiple recruiters belonging to the first group, where the third average value is the average value of the evaluations of the specified applicant. When the computing device receives a browsing request in a third communication established based on identification information that can identify a person belonging to the first segmentation group, the computing device sends the first average value and the third average value as the first evaluation information of the specified applicant to the source that sent the browsing request in the third communication. When the computing device receives a browsing request in a fourth communication established based on identification information that can identify a person belonging to the second segmentation group, the computing device sends the second average value and the third average value as the first evaluation information of the specified applicant to the source that sent the browsing request in the fourth communication.

[0468] (Item 18) The matching system described in Item 18 is such that, in the matching system described in any one of Items 12 to 17, a list of applicants is registered in the database.

[0469] When the first recruiter device receives an operation to retrieve the list, it sends a retrieval request to the computing device.

[0470] When the computing device receives the retrieval request, it sends the retrieval result excluding the applicants whose evaluation levels determined based on the first evaluation information do not meet the criteria from the list to the source that sent the browsing request in the first communication.

[0471] (Item 19) The matching system described in Item 19 is as follows. In the matching system described in Item 1, the first applicant belongs to the first group. The first applicant device receives the input of the evaluation of the recruiter and sends the received evaluation to the computing device. The computing device registers the first evaluation information based on the evaluation received from the first applicant device for each recruiter in the database. When the computing device receives a browsing request in the first communication established based on the identification information that can identify a person belonging to the first group, the computing device sends the first evaluation information to the source that sent the browsing request in the first communication.

[0472] (Item 20) The matching system described in Item 20 is as follows. In the matching system described in Item 19, there is also a second applicant device operated by one or more second applicants belonging to a second group different from the first group. The second applicant device receives the input of the evaluation of the recruiter and sends the received evaluation to the computing device. The computing device registers the second evaluation information based on the evaluation received from the second applicant device for each recruiter in the database. When the computing device receives a browsing request in the second communication established based on the identification information that can identify a person belonging to the second group, the computing device sends the second evaluation information to the source that sent the browsing request in the second communication.

[0473] (Item 21) The matching system described in Item 21 is as follows. In the matching system described in Item 20, the first group is composed of the first company, and the second group is composed of a second company different from the first company.

[0474] (Item 22) The matching system described in Item 22 is as follows. In the matching system described in Item 20, the first group is composed of the first department of the first company, and the second group is composed of the second department of the first company.

[0475] (Item 23) The matching system described in Item 23 is as follows. In any of the matching systems described in Items 19 to 22, when the computing device receives evaluations of a specified recruiter from multiple first applicants belonging to the first group, the computing device calculates the average value of the evaluations of the specified recruiter by the multiple first applicants, and the computing device sends the average value as the first evaluation information of the specified recruiter to the source that sent the browsing request in the first communication.

[0476] (Item 24) The matching system described in Item 24 is such that, in the matching system described in any one of Items 19 to 21, the first group includes one or more first applicants belonging to the first divided group and one or more first applicants belonging to a second divided group different from the first divided group. The computing device calculates a first average value based on the evaluations of a specified recruiter received from a plurality of first applicants belonging to the first divided group. The first average value is the average value of the evaluations of the specified recruiter. The computing device calculates a second average value based on the evaluations of the specified recruiter received from a plurality of first applicants belonging to the second divided group. The second average value is the average value of the evaluations of the specified recruiter. The computing device calculates a third average value based on the evaluations of the specified recruiter received from a plurality of first applicants belonging to the first group. The third average value is the average value of the evaluations of the specified recruiter. When the computing device receives a browsing request in a third communication established based on identification information capable of identifying a person belonging to the first divided group, the computing device sends the first average value and the third average value as first evaluation information of the specified recruiter to the source that sent the browsing request in the third communication. When the computing device receives a browsing request in a fourth communication established based on identification information capable of identifying a person belonging to the second divided group, the computing device sends the second average value and the third average value as first evaluation information of the specified recruiter to the source that sent the browsing request in the fourth communication.

[0477] (Item 25) The matching system described in Item 25 is such that, in the matching system described in any one of Items 19 to 24, a list of recruiters is registered in the database. When the first applicant device receives an operation to retrieve the list, the first applicant device sends a retrieval request to the computing device. When the computing device receives the retrieval request, the computing device sends a retrieval result excluding recruiters whose evaluation levels determined based on the first evaluation information do not meet the criteria from the list to the source that sent the browsing request in the first communication.

[0478] (Item 26) The matching system described in Item 26 is such that, in the matching system described in Item 1, the asset information includes detailed information related to the content of the asset. The computing device displays the asset information that is permitted to be disclosed to the first applicant and the meanings of the terms included in the detailed information on the first applicant device.

[0479] (Item 27) The matching system described in Item 27 is such that, in the matching system described in Item 26, the terms included in the detailed information are internal terms that are prevalent in the group to which the recruiter belongs.

[0480] (Item 28) The matching system described in Item 28 is such that, in the matching system described in Item 27, the computing device registers the internal terms and the meanings of the internal terms in the database.

[0481] (Item 29) The matching system described in Item 29 is such that, in the matching system described in Item 28, the computing device registers internal terms in the database according to the group to which the recruiter belongs.

[0482] (Item 30) The matching system described in Item 30 is such that, in the matching system described in Item 28 or 29, when an operation of the first applicant for an internal term is detected in the first applicant device, the computing device sends information capable of determining the meaning of the internal term registered in the database to the first applicant device.

[0483] (Item 31) The matching system described in Item 31 is such that, in any one of the matching systems described in Items 27 to 30, the computing device retrieves the internal terms included in the detailed information and registers the asset information in the database in a state where the detected internal terms are associated with the meanings of the internal terms.

[0484] (Item 32) The recruiter device described in Item 32 is a recruiter device operated by a recruiter when the holder of an asset becomes a recruiter and recruits a transfer destination or a usage destination of the asset. The recruiter device communicates with a computing device that is used to match the recruiter with an applicant who applies for the recruitment. The recruiter device includes: an interface that is used to accept an operation of inputting asset information representing an object of the asset and public information representing the scope of disclosure of the asset information; and a processor that sends the asset information and the public information accepted by the interface to the computing device, where the public information includes information for instructing the computing device to permit disclosure of the asset information to a first applicant and prohibit disclosure of the asset information to a second applicant different from the first applicant.

[0485] (Item 33) The method described in Item 33 is used to match a recruiter with an applicant who applies for the recruitment when the holder of an asset becomes a recruiter and recruits a transfer destination or a usage destination of the asset. The method includes the following steps: communicating with a recruiter device operated by the recruiter and a first applicant device operated by a first applicant; receiving, from the recruiter device operated by the recruiter, asset information representing an object of the asset and public information representing the scope of disclosure of the asset information; registering the asset information and the public information in a database together; and determining, based on the public information, the asset information registered in the database that is permitted to be disclosed to the first applicant, and providing the asset information permitted to be disclosed to the first applicant to the first applicant device.

[0486] It should be considered that the embodiments disclosed herein are illustrative rather than restrictive in all respects. The scope of the present invention is not represented by the description of the above embodiments, but by the claims, and is intended to include all modifications within the meaning and scope equivalent to the claims.

[0487] Description of Reference Numerals

[0488] 1: Matching system; 50: Internet; 100: Shared server; 101: Processor; 102: Memory; 103: Storage device; 104: Communication interface; 120: Database (DB); 121: Enterprise database (Enterprise DB); 122: Member database (Member DB); 123: Community database (Community DB); 124, 124A: Recruitment case database (Recruitment case DB); 126: Evaluation input database (Evaluation input DB); 126A: Recruiter evaluation department; 126B: Applicant evaluation department; 127: Evaluation summary database (Evaluation summary DB); 127A: Recruiter evaluation summary department; 127B: Applicant evaluation summary department; 129: Profile database (Profile DB); 137: In-company term database (In-company term DB); 140: Community registration department; 141: Enterprise registration department; 142: Member registration department; 143: Member search department; 144: Case registration department; 145: Case extraction department; 146: Application department; 147: Approval department; 148: Notification department; 149: Performance acceptance department; 150: Performance output department; 151: Evaluation acceptance department; 152: Evaluation output department; 200, 200A, 200B, 200C: Recruiter device; 201: Processor; 202: Memory; 203: Communication interface; 204: Input / output interface; 205: Display; 206: Operation unit; 300, 300A, 300B, 300C: Applicant device; 301: Processor; 302: Memory; 303: Communication interface; 304: Input / output interface; 305: Display; 306: Operation unit; 402: Table; 500: User device; 1271, 1272: Data group.

Claims

1. A matching system for matching a recruiter with an applicant who applies for the recruitment when the holder of an asset becomes a recruiter and recruits the transfer destination or utilization destination of the asset. The matching system includes: A recruiter device operated by the recruiter; A first applicant device operated by a first applicant; And A computing device that communicates with the recruiter device and the first applicant device and can access a database, wherein the recruiter device sends asset information representing the object of the asset and public information representing the public scope of the asset information to the computing device, the computing device registers the asset information and the public information together in the database, the computing device determines, based on the public information, the asset information among the asset information registered in the database that is allowed to be disclosed to the first applicant, and provides the asset information allowed to be disclosed to the first applicant to the first applicant device.

2. The matching system according to claim 1, wherein, it further includes a second applicant device operated by a second applicant different from the first applicant, the computing device determines, based on the public information, the asset information among the asset information registered in the database that is allowed to be disclosed to the second applicant, and provides the asset information allowed to be disclosed to the second applicant to the second applicant device.

3. The matching system according to claim 2, wherein, the matching system further includes a third applicant device operated by a third applicant different from the first applicant and the second applicant, multiple public levels are set for the public information, the computing device determines whether disclosure is allowed for the first applicant, the second applicant, and the third applicant respectively according to the public level.

4. The matching system according to claim 3, wherein, the first applicant belongs to a first group, and the second applicant belongs to a second group different from the first group, the multiple public levels include a first level and a second level, the first level corresponds to the following situation: the asset information is allowed to be disclosed to the first applicant, and it is prohibited to disclose the asset information to applicants who do not belong to the first group, the second level corresponds to the following situation: the asset information is allowed to be disclosed to applicants who belong to any group among the first group and the community groups that have formed a community relationship with the first group, and it is prohibited to disclose the asset information to applicants who do not belong to any of the first group and the community groups.

5. The matching system according to claim 3, wherein, the first applicant belongs to a first group, and the second applicant belongs to a second group different from the first group, the multiple public levels include a first level, a second level, and a third level, the first level corresponds to the following situation: the asset information is allowed to be disclosed to the first applicant, and it is prohibited to disclose the asset information to applicants who do not belong to the first group, The second level allows the asset information to be disclosed to applicants in any group belonging to the first group and community groups that have formed a community relationship with the first group. The third level corresponds to the following situation: allowing the asset information to be disclosed to applicants in a community of a community group that belongs to the first group and has formed a community relationship with the first group and is different from the second level, and prohibiting the disclosure of the asset information to applicants who do not belong to any of the first group and the community group.

6. The matching system according to claim 4, wherein, the multiple disclosure levels include a disclosure level corresponding to the following situation: allowing the asset information to be disclosed to the applicant regardless of the group to which the applicant belongs.

7. The matching system according to claim 5 or 6, wherein, attribute data capable of determining the community group is registered in the database, the computing device determines the applicants who are allowed to disclose the asset information based on the disclosure information and the attribute data.

8. The matching system according to any one of claims 3 to 7, wherein, the recruiter device accepts an operation for inputting a target group for which the disclosure of the asset information is prohibited, and sends information capable of determining the accepted target group to the computing device, even if the disclosure level is a level that allows the disclosure of the asset information to the target group, the computing device prohibits the disclosure of the asset information to applicants belonging to the target group.

9. The matching system according to any one of claims 2 to 8, wherein, the first applicant belongs to a first enterprise, and the second applicant belongs to a second enterprise different from the first enterprise.

10. The matching system according to any one of claims 1 to 9, wherein, the recruiter device sends recruitment method information capable of determining that the asset is a shared asset for which one or more applicants are selected as the transfer destination or utilization destination of the asset to the computing device, the computing device registers the recruitment method information in the database corresponding to the asset information.

11. The matching system according to claim 10, wherein, the computing device registers sharing establishment conditions in the database corresponding to the recruitment method information, the sharing establishment conditions are conditions related to the number of applicants for the shared asset, when the sharing establishment conditions are satisfied, the computing device determines the applicants for the shared asset.

12. The matching system according to claim 1, wherein, the recruiter device includes a first recruiter device operated by one or more recruiters belonging to the first group, the first recruiter device accepts the input of an evaluation of the first applicant and sends the accepted evaluation to the computing device, the computing device registers first evaluation information based on the evaluation received from the first recruiter device in the database according to the applicant. When the computing device receives a browsing request in a first communication established based on identification information capable of identifying a person belonging to the first group, the computing device sends the first evaluation information to the source that sent the browsing request in the first communication.

13. The matching system according to claim 12, wherein, the recruiter device further includes a second recruiter device operated by one or more recruiters belonging to a second group different from the first group, the second recruiter device accepts the input of the evaluation of the first applicant and sends the accepted evaluation to the computing device, the computing device registers second evaluation information based on the evaluation received from the second recruiter device in the database for each applicant, when the computing device receives a browsing request in a second communication established based on identification information capable of identifying a person belonging to the second group, the computing device sends the second evaluation information to the source that sent the browsing request in the second communication.

14. The matching system according to claim 13, wherein, the first group is composed of a first enterprise, and the second group is composed of a second enterprise different from the first enterprise.

15. The matching system according to claim 13, wherein, the first group is composed of a first department of a first enterprise, and the second group is composed of a second department of the first enterprise.

16. The matching system according to any one of claims 12 to 15, wherein, when the computing device receives evaluations of a specified applicant from multiple recruiters belonging to the first group, the computing device calculates the average value of the evaluations of the specified applicant by the multiple recruiters, the computing device sends the average value as the first evaluation information of the specified applicant to the source that sent the browsing request in the first communication.

17. The matching system according to claim 16, wherein, the first group includes one or more recruiters belonging to a first sub-group and one or more recruiters belonging to a second sub-group different from the first sub-group, the computing device calculates a first average value based on the evaluations of a specified applicant received from multiple recruiters belonging to the first sub-group, and the first average value is the average value of the evaluations of the specified applicant, the computing device calculates a second average value based on the evaluations of the specified applicant received from multiple recruiters belonging to the second sub-group, and the second average value is the average value of the evaluations of the specified applicant, the computing device calculates a third average value based on the evaluations of the specified applicant received from multiple recruiters belonging to the first group, and the third average value is the average value of the evaluations of the specified applicant, When the computing device receives a browsing request in a third communication established based on identification information capable of identifying a person belonging to the first divided group, the computing device sends the first average value and the third average value as the first evaluation information of the specified applicant to the source that sent the browsing request in the third communication. When the computing device receives a browsing request in a fourth communication established based on identification information capable of identifying a person belonging to the second divided group, the computing device sends the second average value and the third average value as the first evaluation information of the specified applicant to the source that sent the browsing request in the fourth communication.

18. The matching system according to any one of claims 12 to 17, wherein, a list of applicants is registered in the database, when the first recruiter device receives an operation to retrieve the list, the first recruiter device sends a retrieval request to the computing device, when the computing device receives the retrieval request, the computing device sends a retrieval result excluding the applicants whose evaluation heights determined according to the first evaluation information do not meet the criteria from the list to the source that sent the browsing request in the first communication.

19. The matching system according to claim 1, wherein, the first applicant belongs to the first group, the first applicant device receives an input of an evaluation of the recruiter and sends the received evaluation to the computing device, the computing device registers the first evaluation information based on the evaluation received from the first applicant device in the database by recruiter, when the computing device receives a browsing request in a first communication established based on identification information capable of identifying a person belonging to the first group, the computing device sends the first evaluation information to the source that sent the browsing request in the first communication.

20. The matching system according to claim 19, wherein, it further includes a second applicant device operated by one or more second applicants belonging to a second group different from the first group, the second applicant device receives an input of an evaluation of the recruiter and sends the received evaluation to the computing device, the computing device registers the second evaluation information based on the evaluation received from the second applicant device in the database by recruiter, when the computing device receives a browsing request in a second communication established based on identification information capable of identifying a person belonging to the second group, the computing device sends the second evaluation information to the source that sent the browsing request in the second communication.

21. The matching system according to claim 20, wherein, the first group is composed of a first enterprise, and the second group is composed of a second enterprise different from the first enterprise.

22. The matching system according to claim 20, wherein, the first group is composed of a first department of a first enterprise, and the second group is composed of a second department of the first enterprise.

23. The matching system according to any one of claims 19 to 22, wherein, When the computing device receives evaluations of a specified recruiter from a plurality of first applicants belonging to the first group, the computing device calculates an average value of the evaluations of the specified recruiter by the plurality of first applicants. The computing device sends the average value as the first evaluation information of the specified recruiter to the source that sent the browsing request in the first communication.

24. The matching system according to any one of claims 19 to 21, wherein, the first group includes one or more first applicants belonging to a first divided group and one or more first applicants belonging to a second divided group different from the first divided group, the computing device calculates a first average value based on evaluations of a specified recruiter received from a plurality of first applicants belonging to the first divided group, and the first average value is an average value of the evaluations of the specified recruiter, the computing device calculates a second average value based on evaluations of the specified recruiter received from a plurality of first applicants belonging to the second divided group, and the second average value is an average value of the evaluations of the specified recruiter, the computing device calculates a third average value based on evaluations of the specified recruiter received from a plurality of first applicants belonging to the first group, and the third average value is an average value of the evaluations of the specified recruiter, when the computing device receives a browsing request in a third communication established based on identification information capable of identifying a person belonging to the first divided group, the computing device sends the first average value and the third average value as the first evaluation information of the specified recruiter to the source that sent the browsing request in the third communication, when the computing device receives a browsing request in a fourth communication established based on identification information capable of identifying a person belonging to the second divided group, the computing device sends the second average value and the third average value as the first evaluation information of the specified recruiter to the source that sent the browsing request in the fourth communication.

25. The matching system according to any one of claims 19 to 24, wherein, a list of recruiters is registered in the database, when the first applicant device receives an operation to retrieve the list, the first applicant device sends a retrieval request to the computing device, when the computing device receives the retrieval request, the computing device sends a retrieval result to the source that sent the browsing request in the first communication, excluding recruiters whose evaluation heights determined according to the first evaluation information do not meet the criteria from the list.

26. The matching system according to claim 1, wherein, the asset information includes detailed information about the content of the asset, the computing device displays the asset information that is allowed to be disclosed to the first applicant and the meanings of the terms included in the detailed information on the first applicant device.

27. The matching system according to claim 26, wherein, the terms included in the detailed information are internal terms that are popular in the group to which the recruiter belongs.

28. The matching system according to claim 27, wherein, the computing device registers the internal term and the meaning of the internal term in the database.

29. The matching system according to claim 28, wherein, the computing device registers the internal term in the database according to the group to which the recruiter belongs.

30. The matching system according to claim 28 or 29, wherein, when an operation of the first applicant for the internal term is detected in the first applicant device, the computing device sends information capable of determining the meaning of the internal term registered in the database to the first applicant device.

31. The matching system according to any one of claims 27 to 30, wherein, the computing device retrieves the internal term included in the detailed information, and registers the asset information in the database in a state where the detected internal term is associated with the meaning of the internal term.

32. A recruiter device, which is a recruiter device operated by a recruiter when the holder of an asset becomes a recruiter and recruits a transfer destination or a utilization destination of the asset, the recruiter device communicates with a computing device for matching a recruiter with an applicant who applies for the recruitment, the recruiter device includes: an interface for accepting an operation of inputting asset information representing an object of the asset and public information representing a public range of the asset information; and a processor that sends the asset information and the public information received by the interface to the computing device, wherein, the public information includes information for instructing the computing device to permit disclosure of the asset information to a first applicant and to prohibit disclosure of the asset information to a second applicant different from the first applicant.

33. A method for matching a recruiter with an applicant who applies for the recruitment when the holder of an asset becomes a recruiter and recruits a transfer destination or a utilization destination of the asset, the method comprises the following steps: communicating with a recruiter device operated by a recruiter and a first applicant device operated by a first applicant; receiving, from the recruiter device operated by the recruiter, asset information representing an object of the asset and public information representing a public range of the asset information; registering the asset information and the public information in a database; and determining, based on the public information, the asset information in the asset information registered in the database that is permitted to be disclosed to the first applicant, and providing the asset information permitted to be disclosed to the first applicant to the first applicant device.

Images