Matching system, recruiter device, and method

Abstract

Provided is a matching system (1) which matches a recruiter and an applicant who applies for a position, if the owner of an asset, who serves as the recruiter, is recruiting an asset transferee or an asset user. The matching system comprises: a recruiter device (200) operated by a recruiter; a first applicant device (300A) operated by a first applicant; and a computing device (100) which communicates with the recruiter device and the first applicant device and which is capable of accessing a database. The recruiter device (200) transmits, to the computing device (100), asset information indicating an asset target and disclosure information indicating a disclosure range for the asset information. The computing device (100) registers the asset information together with the disclosure information in a database (120). The computing device (100) determines, on the basis of the disclosure information, asset information which is allowed to be disclosed to the first applicant, from among pieces of asset information registered in the database (120), and provides, to the first applicant device (300A), the asset information that is allowed to be disclosed to the first applicant.

Description

Matching system, recruiter device, and method

[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 a recruitment when an asset holder becomes a recruiter and recruits a recipient or user of the asset.

[0002] Conventionally, systems that mediate the sale and purchase of goods between individuals have 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 an intermediary, in which the intermediary manages personal information of the seller and the buyer, and mediates the sale and purchase of goods between individuals without the personal information being disclosed to the seller or the buyer.

[0003] The system described in Patent Document 1 can smoothly match people who want to sell unwanted items with people who want to purchase desired items.

[0004] Japanese Patent Application Laid-Open No. 2002-74055

[0005] The need to dispose of or utilize surplus assets such as unnecessary goods exists not only among individuals but also among groups such as companies. Groups such as companies can act as recruiters seeking recipients of assets or uses for assets, and can solicit applicants to apply for the recruitment.

[0006] However, the recruiter must avoid not only the transfer of surplus assets to a competitor, but also the disclosure of the details of the surplus assets that the recruiter wishes to transfer to a competitor. This is because there is a risk that the details of the surplus assets that the recruiter wishes to transfer may reveal confidential information or business trends to the competitor. Therefore, when matching recruiters and applicants who belong to groups such as companies, it is necessary to take into consideration the conflicts of interest between the recruiter and the applicant.

[0007] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to make it possible to select appropriate applicants taking into consideration the conflicts of interest between the applicant and the solicitor seeking a recipient or user of assets.

[0008] A matching system according to a first aspect of the present disclosure is a matching system that matches an asset holder acting as a recruiter and seeking a recipient or use for the asset with an applicant who applies for the recruitment, and 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 transmits asset information indicating the target of the asset and disclosure information indicating the scope of disclosure of the asset information to the computing device, the computing device registers the asset information together with the disclosure information in the database, and the computing device determines, based on the disclosure information, which asset information registered in the database is permitted to be disclosed to the first applicant, and provides the asset information permitted to be disclosed to the first applicant to the first applicant device.

[0009] A recruiter device according to a second aspect of the present disclosure is a recruiter device operated by an asset holder when the asset holder becomes the recruiter and recruits recipients for asset transfer or utilization, the recruiter device communicates with a computing device that matches the recruiter with applicants applying for the recruitment, and is equipped with an interface that accepts operations to input asset information indicating the target of the asset and disclosure information indicating the scope of disclosure of the asset information, and a processor that transmits the asset information and disclosure information accepted by the interface to the computing device, and the disclosure information includes information that instructs 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.

[0010] A method according to a third aspect of the present disclosure is a method for matching an asset holder who acts as a recruiter and is seeking a recipient or use for the asset with an applicant who applies for the recruitment, and includes the steps of communicating with a recruiter device operated by the recruiter and a first applicant device operated by a first applicant, receiving asset information indicating the target of the asset and disclosure information indicating the scope of disclosure of the asset information from the recruiter device operated by the recruiter, registering the asset information together with the disclosure information in a database, and determining, based on the disclosure information, asset information that is permitted to be disclosed to the first applicant from the asset information registered in the database, and providing the asset information that is permitted to be disclosed to the first applicant to the first applicant device.

[0011] According to the present disclosure, it is possible to select an appropriate applicant taking into consideration the interests of a group of recruiters seeking recipients or users of assets and a group of applicants.

[0012] 1 is a block diagram showing an overview of a matching system. FIG. 1 is a block diagram showing the configurations of a sharing server, a recruiter device, and an applicant device. FIG. 2 is a block diagram showing the configurations of a sharing server, a recruiter device, and an applicant device. FIG. 3 is a block diagram showing an example of a company database. FIG. 4 is a block diagram showing an example of a member database. FIG. 5 is a block diagram showing an example of a community database. FIG. 6 is a block diagram showing an example of a job posting database. FIG. 7 is a block diagram showing an example of an evaluation input database. FIG. 8 is a block diagram showing an example of an evaluation summary database. FIG. 9 is a block diagram explaining the functions of the sharing server, the recruiter device, and the applicant device. FIG. 10 is a block diagram explaining the functions of the sharing server, the recruiter device, and the applicant device. FIG. 11 is a block diagram explaining the functions of the sharing server, the recruiter device, and the applicant device. FIG. 12 is a block diagram explaining the functions of the applicant device. FIG. 13 is a block diagram explaining the procedure for registering a job posting in the job posting database. FIG. 14 is a block diagram explaining the procedure for searching for a job posting from the database. FIG. 15 is a block diagram explaining the procedure for registering an evaluation of an applicant in the database. FIG. 16 is a block diagram explaining the procedure for registering an evaluation of a recruiter in the database. FIG. 17 is a block diagram explaining the procedure for displaying evaluations of an applicant and search results for members on a display. FIG. 18 is a block diagram explaining the procedure for displaying evaluations of a recruiter and search results for members on a display. FIG. 19 is a block diagram explaining the viewable range of the evaluation summary database. FIG. 19 is a block diagram showing an example in which the disclosure range is set according to the disclosure level. FIG. 1 is a diagram showing details of asset contents included in a job listing database. FIG. 2 is a diagram showing an example of a profile database. FIG. 3 is a diagram showing an example of an in-house terminology database. FIG. 4 is a flowchart showing processing procedures related to the indexing function of the matching system. FIG. 5 is a flowchart showing processing procedures of an in-house terminology registration unit. FIG. 6 is a flowchart showing processing procedures of a job listing registration unit. FIG. 7 is a flowchart showing processing procedures for displaying the meaning of an in-house term on a screen in accordance with an applicant's operation. FIG. 8 is a diagram showing an example of a job listing database related to variant 1. FIG. 9 is a diagram for explaining the procedure for registering a job listing in the job listing database related to variant 1. FIG. 10 is a flowchart showing processing procedures of a first determination process related to variant 1. FIG. 11 is a flowchart showing processing procedures of a second determination process related to variant 1.Fig. 10 is a flowchart showing the processing procedure of a third determination process according to Modification 1. Fig. 11 is a diagram showing the configuration of a matching system according to Modification 2. Fig. 12 is a diagram showing an example (Modification 3) in which Kerberos authentication is applied to the matching system.

[0013] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are designated by the same reference numerals, and description thereof will not be repeated.

[0014] [Background for Proposing Matching System 1] FIG. 1 is a block diagram showing an overview of a matching system 1 according to this embodiment.

[0015] Hereinafter, in the matching system 1, surplus assets that are being solicited for transfer to or use by a counterparty may be referred to as a "solicited project," a person who provides a solicited project or a person who may provide a solicited project may be referred to as a "recruiter," and a person who applies for a solicitation by a recruiter or a person who may apply may be referred to as an applicant. A person who receives approval for their application from the recruiter is permitted to transfer or use surplus assets related to the solicited project depending on the content of the solicitation. In this way, a person who receives approval for their application from the recruiter may be referred to as the "acquirer" of the solicited project.

[0016] If a transaction related to a solicitation is concluded, the applicant will be the "transferee," and the offeror who transfers surplus assets to the "transferee" will be the "transferor." However, in the following, the "transferee" may be referred to as the "applicant," and the "transferor" may be referred to as the "offeror."

[0017] First, the background behind the proposal of the matching system 1 in this embodiment will be described. Systems that mediate the buying and selling of goods for individuals are widely known. By using such systems, individuals can dispose of unwanted goods in exchange for payment.

[0018] Companies also have the need to dispose of surplus assets, such as items that are no longer needed. Companies can make a profit from surplus assets by selling or leasing them, rather than depreciating or disposing of them. However, when companies are looking for buyers for surplus assets, they need to be aware of the following points, which are not an issue when buying and selling items between individuals.

[0019] [Possibility of leakage of confidential information] For example, when a company intends to lend or sell surplus assets such as dormant patents, plans, or ideas, it must not only avoid competitors becoming the trading partners of the surplus assets, but also avoid competitors becoming aware of the contents of the surplus assets it is planning to lend or sell. This is because there is a risk that competitors may learn confidential information or business trends through the contents of the surplus assets it is planning to lend or sell. Similarly, when a company intends to lend or sell surplus assets such as facilities and equipment, it must ensure that information about the surplus assets is not made known to competitors. This is because there is a risk that competitors may be able to infer future business trends from the fact that facilities, etc. are planned to be sold.

[0020] Companies should also pay close attention to the background of their business partners to avoid damaging their own creditworthiness.

[0021] Therefore, when matching recruiters and applicants, each of whom belongs to a company, it becomes necessary to take into consideration the interests of the recruiter's group and the recruiting company and the applicant company.

[0022] However, traditional intermediary systems for personal sales do not take into consideration the interests of the companies recruiting and applying for jobs. Therefore, when a human resources intermediary system is used in transactions between companies, it carries both corporate and personal risks. For example, confidential information may be leaked to a rival company through assets listed by an employee of one company. Furthermore, traditional intermediary systems for personal sales do not allow administrators to verify that employees are not selling the company's assets to competitors.

[0023] [Possibility of not obtaining accurate information about offerors and applicants] Excess assets are registered in the matching system by offerors as offers for trading. Those who wish to acquire the surplus assets apply for the offers. Applicants will likely select an offer that satisfies them, taking into consideration the content and amount of the surplus assets, etc.

[0024] However, some offerors may frequently change the value of their surplus assets or may register surplus assets of poor quality. Applicants will want to avoid such offerors and apply for offers. Conversely, there are also offerors that offer high-quality surplus assets at reasonable prices. Applicants will want to apply for offers from such offerors, if possible.

[0025] In addition, some applicants may have problems paying for surplus assets or may make unreasonable price demands. The offeror will want to avoid such applicants and do business with applicants who act honestly.

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

[0027] However, a person in charge (recruiter or applicant) of one company may, out of consideration for the person in charge (recruiter or applicant) of another company being evaluated, enter a higher rating into the system than they should. Also, a person in charge of one company may avoid giving a low rating to a person in another company out of concern that this could worsen the relationship between the companies. Furthermore, a person in a position to rate may not see any benefit in rating someone and enter a rating into the system that is far from their true rating. Considering these possibilities, the reliability of the ratings provided by the system may be reduced. In this case, even if ratings for recruiters and applicants are shared through the system, users will not be able to use the ratings as reference data when doing business with the recruiters or applicants.

[0028] [Internal jargon may hinder communication] In some companies, internal jargon specific to that company is widely used. Although internal jargon is understood by people in the company where it is widely used, there is a risk that it may not be understood by people who do not belong to the company where it is widely used. Alternatively, internal jargon may be understood as a term with a specific meaning among people in the company where it is widely used, but may be understood as a term with a different meaning from that specific meaning by people who do not belong to the company where it is widely used.

[0029] There is a possibility that internal company terminology may be used in the text describing the surplus assets. If the company to which the recruiter belongs is different from the company to which the applicant belongs, the applicant may not correctly understand the meaning of the internal company terminology used by the recruiter to describe the surplus assets. The applicant may apply for the job without correctly understanding the meaning of the internal company terminology used by the recruiter to describe the surplus assets. As a result, there is a risk of trouble arising between the recruiter and the applicant.

[0030] In-house jargon may be used during meetings between recruiters and applicants. If the recruiter belongs to a different company than the applicant, the applicant may not correctly understand the meaning of the in-house jargon used by the recruiter. Similarly, the recruiter may not correctly understand the meaning of the in-house jargon used by the applicant.

[0031] If the company term used by either the recruiter or the applicant is unfamiliar, the other person can understand the meaning of the term by asking the speaker. However, if the understanding of the meaning of a certain company term differs between the recruiter and the applicant, the meeting will proceed without correcting the misunderstanding between the two parties. As a result, there is a risk of trouble arising between the recruiter and the applicant.

[0032] Terms similar to in-house jargon can be used with unique meanings not only in companies but also in non-profit organizations. Whether for-profit or non-profit, an organization may be divided into multiple units, such as departments and sections, and each unit may have its own unique terminology. Such terms may also be prevalent in communities formed by multiple organizations, such as companies. Therefore, when recruiters and applicants belong to different organizations, units, and communities, differences in understanding of terminology can lead to the problems described above.

[0033] In this embodiment, the term "in-house terminology" refers not only to "internal terminology" used in profit-making organizations such as companies and their units, but also to "terms similar to internal terminology" used in non-profit organizations, communities, and their units. In the following, this embodiment will be explained using "internal terminology" for a company as an example of "in-house terminology."

[0034] In this embodiment, a matching system 1, which will be described in detail below, is proposed in order to solve at least one of the above-mentioned various problems that conventional intermediary systems have.

[0035] [Overall Configuration] The general configuration of the matching system 1 will be described with reference to Fig. 1. The matching system 1 includes a sharing server 100, recruiter devices 200A, 200B, 200C, etc., and applicant devices 300A, 300B, 300C, etc.

[0036] The sharing server 100 provides a matching service to a large number of companies, which matches the transfer or use of surplus assets between companies. Figure 1 shows company A, company B, company C, etc. as examples of companies that use the matching service. Company A, company B, company C, etc. are registered as corporate members of the matching system 1. Employees of company A, company B, company C, etc. who use the matching system 1 are also individually registered as members of the matching system 1.

[0037] Companies A, B, C, etc. have various surplus assets. The surplus assets that are the target of the matching system 1 include hardware such as facilities and equipment, and software such as dormant patents, plans, and ideas.

[0038] Company A, Company B, Company C, etc. can offer various surplus assets to the matching system 1. Company A, Company B, Company C, etc. may also offer assets that are not necessarily "surplus" to the matching system 1. Hereinafter, items to be offered for sale to the matching system 1 may be referred to as "assets" in a broad sense, including "surplus assets."

[0039] In the matching system 1, an applicant from company A can also apply as a transferee of an asset that is being offered for sale by company A. For example, in the matching system 1, a person belonging to a different department Y of company A can apply as a transferee of an asset that is being offered for sale by department X of company A.

[0040] The matching system 1 handles not only recruitment requests for transfer to applicants, but also recruitment requests for allowing applicants to use assets while the applicant maintains ownership of the assets. For example, vacation facilities and conference rooms fall under such recruitment requests. A company that owns a training program may offer the right to use the training program as a recruitment request on the matching system 1. In this case, a recruitment request for allowing applicants to use the training program is registered in the matching system 1.

[0041] When a transaction related to this type of offering is concluded, the applicant will be considered the "user," and the offeror who transfers assets to the "user" will be considered the "licensor." However, in the following, the "user" may be referred to as the "applicant," and the "licensor" may be referred to as the "offeror."

[0042] The sharing server 100 has a database 120 necessary for the matching service. The database 120 includes various databases in which information necessary for providing the matching service is registered. For example, the database 120 registers information about members and recruitment opportunities. The sharing server 100 is managed and operated by a company separate from the companies that use the matching service. Any of the companies that use the matching service may manage and operate the sharing server 100.

[0043] The recruiter device 200A is operated by an administrator of company A. The recruiter device 200B is operated by an administrator of company B. The recruiter device 200C is operated by an administrator of company C. Hereinafter, the recruiter devices 200A, 200B, 200C, etc. may be collectively referred to as "recruiter devices 200."

[0044] Applicant device 300A is operated by an applicant from company A. Applicant device 300B is operated by an applicant from company B. Applicant device 300C is operated by an applicant from company C. Hereinafter, applicant devices 300A, 300B, 300C, etc. may be collectively referred to as "applicant devices 300." Although FIG. 1 shows two applicants for each company, the number of applicants is not limited to this. There may be more applicants for each company, or a company may have only one applicant. Sharing server 100 may also accept applicants who do not belong to a company.

[0045] The managers of companies A, B, C, etc. act as recruiters. Therefore, hereinafter, the managers of each company may be referred to as "recruiters." Recruiters can also act as applicants for jobs being recruited by other recruiters. In this case, the recruiter device 200 functions as the applicant device 300. In the present disclosure, when a company manager acts as a recruiter, the device that the manager uses to use the matching service is referred to as the recruiter device 200.

[0046] Company A may have one or more administrators. If company A has administrators, each administrator may own a recruiter device 200, or one recruiter device 200 may be shared by multiple administrators. The same applies to companies B, C, etc.

[0047] The sharing server 100 and the recruiter device 200 are configured to be able to communicate with each other via the Internet 50, which is an example of a communication network. The sharing server 100 and the applicant device 300 are configured to be able to communicate with each other via the Internet 50.

[0048] The sharing server 100 requires sign-in with input of a member ID and password when accepting access from the recruiter device 200. Similarly, the sharing server 100 requires sign-in with input of a member ID and password when accepting access from the applicant device 300. The sharing server 100 identifies each recruiter and applicant by the member ID notified at the time of sign-in.

[0049] The recruiter device 200 accepts various operations by the recruiter. For example, the recruiter device 200 accepts an operation to input a recruitment request and an operation to search for members of the matching service.

[0050] The recruiter device 200 communicates with the sharing server 100 in response to each operation on the recruiter device 200. The sharing server 100 registers a recruitment request in the database 120 in response to an operation to input a recruitment request, and provides member information to the recruiter device 200 in response to an operation to search for a member.

[0051] The applicant device 300 accepts various operations by the applicant. For example, the applicant device 300 accepts an operation to search for a job posting and an operation to apply for a job posting.

[0052] The applicant device 300 communicates with the sharing server 100 in response to each operation on the applicant device 300. The sharing server 100 provides the applicant device 300 with an appropriate job posting in response to an operation to search for a job posting, and provides the applicant device 300 with a notification of acceptance or rejection in response to an operation to apply for the job posting.

[0053] 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 a job posting by using the matching system 1. A recruiter belonging to company A can select an applicant belonging to company B as the winner of a job posting by using the matching system 1.

[0054] Members who use the matching system 1 access the sharing server 100 as recruiters or applicants. Hereinafter, members of the matching system 1 may be referred to as "users." Also, below, the recruiter device 200 and applicant device 300 operated by members may be collectively referred to as "user device 500."

[0055] 1 illustrates an example of a screen 550 displayed on the user device 500. Various information is displayed on the screen 550. For example, the screen 550 displays a detailed description of an asset. A user (applicant) looks at the screen 550 to check the details of the asset that is being offered for sale.

[0056] The asset descriptions and the like displayed on screen 550 may contain in-house terminology. If the company to which the user viewing screen 550 belongs is different from the company to which the user providing the information belongs, the user viewing screen 550 may not be able to correctly understand the in-house terminology.

[0057] Therefore, the matching system 1 registers each company's internal terms and their meanings in the database 120. The matching system 1 generates an index of internal terms from sentences such as descriptions of assets, and links the index to the internal terms registered in the database 120. In this way, the matching system 1 has an indexing function.

[0058] When an in-house term is included in a sentence displayed on the screen 550, the user device 500 displays the in-house term in a different display mode from other terms. This allows the user to understand that the term is an in-house term. Furthermore, the user device 500 displays the intended meaning of the in-house term on the screen 550 in response to a user operation (for example, a click on the in-house term).

[0059] For example, screen 550 shown in FIG. 1 displays "DX" as an example of an internal company term. "DX" is underlined to indicate that it is an internal company term. The user clicks on "DX." A window explaining the meaning of the term "DX" is then displayed on screen 550. DX is an abbreviation for "Digital Transformation" and generally refers to transformation using digital technology. However, some companies may use "DX" as an internal company term to mean the creation of some kind of new value, regardless of whether digital technology is used. In such cases, the meaning corresponding to the internal company term is explained in the window on screen 550. This allows the user to correctly understand the meaning of "DX" that the other party intends.

[0060] FIG. 2 is a block diagram showing the configurations of the sharing server 100, the recruiter device 200, and the applicant device 300.

[0061] [Configuration of Sharing Server 100 ] The sharing server 100 includes a processor 101 , a memory 102 , a storage 103 , and a communication interface 104 .

[0062] The memory 102 may include a random access memory (RAM), a read only memory (ROM), a flash memory, or any other suitable memory system. The memory 102 stores programs required for the arithmetic processing of the processor 101, temporary data calculated in the arithmetic processing, and the like.

[0063] The storage 103 is configured with a hard disk drive, a solid state drive, etc. A database 120 is stored in the storage 103. The database 120 includes multiple types of databases. The multiple types of databases include a company database (company DB) 121, a member database (member DB) 122, a community database (community DB) 123, a wanted job database (wanted job DB) 124, an evaluation input database (evaluation input) 126, and an evaluation summary database (evaluation summary DB) 127. The wanted job database (wanted job DB) 124 registers information on (surplus) assets as wanted jobs.

[0064] Some of these multiple types of databases may be stored in storage provided separately from the sharing server 100. For example, the sharing server 100 may be connected to a cloud service separate from the sharing server 100, and some of the multiple types of databases shown in Fig. 2 may be stored on that cloud. In this case, the sharing server 100 can access the necessary databases by communicating with that cloud via the Internet 50.

[0065] Processor 101 connects to Internet 50 via communication interface 104 in accordance with a program stored in memory 102. Processor 101 connects to Internet 50 and communicates with recruiter device 200 and applicant device 300. Processor 101 accesses database 120 and executes processes such as extracting necessary data, registering new data in database 120, and updating data registered in database 120.

[0066] [Configuration of Recruiter Device 200] 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 includes a mouse, a keyboard, and the like.

[0067] The memory 202 may include a random access memory (RAM), a read only memory (ROM), a flash memory, or any other suitable memory system. The memory 202 stores programs required for the arithmetic processing of the processor 201, temporary data calculated in the arithmetic processing, and the like.

[0068] The processor 201 connects to the Internet 50 via the communication interface 203 in accordance with a program stored in the memory 202. The processor 201 connects to the Internet 50 and communicates with the sharing server 100. The processor 201 communicates with the sharing server 100 and executes processes such as sending a solicitation request, displaying information about applicant members on the display 205, allowing the recruiter to accept or reject the applicant as the winner of the solicitation request, and sending the contents of the evaluation of the applicant (transferee) entered by the recruiter (transferor) to the sharing server 100.

[0069] Information input by operating the operation unit 206 is notified to the processor 201 via the input / output interface 204 .

[0070] [Configuration of Applicant Device 300] Applicant device 300 comprises a processor 301, memory 302, a communication interface 303, an input / output interface 304, a display 305, and an operation unit 306. Operation unit 306 is made up of a mouse, a keyboard, and the like.

[0071] The memory 302 may include a random access memory (RAM), a read only memory (ROM), a flash memory, or any other suitable memory system. The memory 302 stores programs required for the arithmetic processing of the processor 301, temporary data calculated in the arithmetic processing, and the like.

[0072] The processor 301 connects to the Internet 50 via the communication interface 303 in accordance with a program stored in the memory 302. The processor 301 connects to the Internet 50 and communicates with the sharing server 100. The processor 301 communicates with the sharing server 100 and executes processes such as applying for a job, displaying a notification of acceptance or rejection of the job on the display 305, and transmitting the contents of an evaluation of the recruiter (transferor) entered by the applicant (transferee) to the sharing server 100.

[0073] Information input by operating the operation unit 306 is notified to the processor 301 via the input / output interface 304 .

[0074] [Overview of Database 120] Below, an overview of the database 120 will be described. The company database 121 stores information about companies that are members of the matching system 1. The member database 122 stores information about members who use the matching system 1. Many of the members are employees of companies that are members of the matching system 1.

[0075] Members registered in the member database 122 can act as recruiters or applicants by using the matching system 1. Members may include employees of companies registered in the company database 121 as well as individuals who are not affiliated with any company.

[0076] The community database 123 stores information for identifying companies that belong to a community. A community is formed by agreement between companies. Therefore, multiple communities can be formed depending on how the companies agree. The number of companies that belong to one community can also be set in various ways. Companies that have a community relationship form a relationship of trust within the scope determined by how they agree to form the community. The community database 123 registers information for each community that identifies companies that belong to the community.

[0077] The open job database 124 registers open jobs. An open job is an asset that is being sought for transfer to or use by a counterparty. As members of the matching system 1, employees of each company can apply for open jobs posted by other departments of their own company or by other companies.

[0078] The evaluation input database 126 stores evaluation information for applicants and evaluation information for recruiters. By using the matching system 1, recruiters can evaluate, as an evaluator, the behavior of applicants during a transaction. By using the matching system 1, applicants can evaluate, as an evaluator, the behavior of recruiters during a transaction. Evaluations made by individual evaluators are registered in the evaluation input database 126.

[0079] Evaluation summaries are registered in the evaluation summary database 127. Evaluation summaries are registered for each member in the evaluation summary database 127. The evaluation summaries include a recruiter evaluation summary and an applicant evaluation summary. The recruiter evaluation summary indicates the level of evaluation of the member when he or she behaved as a recruiter. The applicant evaluation summary indicates the level of evaluation of the member when he or she behaved as an applicant. The recruiter evaluation summary is created based on the applicant's evaluation of the recruiter. The applicant evaluation summary is created based on the recruiter's evaluation of the applicant.

[0080] Members can view the evaluation summaries. Recruiters can view each member's applicant evaluation summaries and select a member they deem appropriate as a transferee. Applicants can view each member's recruiter evaluation summaries and apply for projects offered by recruiters they deem appropriate.

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

[0082] [Member Database 122] Figure 4 is a diagram showing an example of the member database 122. Various information about members is registered in the member database 122. The various information about members includes a "member ID" for identifying the member, a "company ID" of the company to which the member belongs, a "member name," the member's "authority," and the "department" to which the member belongs.

[0083] The types of member authority include administrator and applicant. A member with administrator authority is given the authority to use the matching system 1 as both a recruiter and an applicant. A member with only applicant authority is given the authority to use the matching system 1 as an applicant, but not as a recruiter. A department head within a company is given administrator authority to manage applications from subordinates within the department. A manager with administrator authority is given the authority to approve applications from subordinate applicants. Therefore, a manager functions as an approver.

[0084] [Community Database 123] Fig. 5 is a diagram showing an example of the community database 123. Information on communities formed between companies is registered in the community database 123. The community information includes a "community ID" and a "community name" for identifying the community, and a "company ID list" of companies that belong to the community. Each company can form various communities by agreeing with other companies. A company that belongs to a community can change the companies that belong to the community by agreeing with the other companies.

[0085] [Recruitment Request Database 124] Fig. 6 is a diagram showing an example of the recruitment request database 124. Information on recruitment requests is registered in the recruitment request database 124. The recruitment request information includes a "recruitment request ID (asset ID)" for identifying the recruitment request, a "company ID" of the company to which the recruiter who registered the recruitment request belongs, a "non-disclosure company ID list," a "recruiter's member ID," a "disclosure level," an "asset title," an "asset content," an "asset classification," an "asset transfer amount," a "number of requests," and a "transfer / use."

[0086] For example, the "Non-Disclosure Company ID List" registers the IDs of companies that prohibit disclosure of job postings. The "Disclosure Level" can be set to one of three levels: "Company," "Within the Community," or "All." If the disclosure level is set to "All," applicants outside the community will also be disclosed.

[0087] The IDs of the companies that can view the recruitment requests are shown on the right side of the recruitment request database 124 in Figure 6. For example, for the recruitment request corresponding to request ID = 001, the disclosure level is set to "our company." In this case, only members belonging to the company that registered the recruitment request (company ID = 00A) can view the recruitment request corresponding to request ID = 001. In this case, it is assumed that surplus assets from one department within the company identified by company ID = 00A will be transferred to or used by another department.

[0088] Hereinafter, using the case ID, the recruiting cases corresponding to each case ID may be referred to as case 001, case 002, case 003, etc. Similarly, using the community ID, the communities corresponding to each community ID may be referred to as community 01, community 02, community 03, etc., and using the member ID, the members corresponding to each member ID may be referred to as member P1, member P2, member P3, etc. Also, hereinafter, using part of the company ID, the companies corresponding to each company ID may be referred to as company A, company B, company C, etc.

[0089] The disclosure level for case 002 is set to "within the community." The recruiter for case 002 is a member (member ID = P2) who belongs to company A. According to the community database 123 shown in Figure 5, the companies that have a community relationship with company A, which registered case 002, are company B and company C. Therefore, as shown in Figure 6, only members who belong to company A, company B, or company C can view case 002.

[0090] Case 003 has the same registered companies and disclosure level as case 002. However, case 003 has "00B" registered in the "Non-Disclosure Company ID List." Therefore, as shown in Figure 6, only members belonging to either company A or company C can view case 003, and members belonging to company B are not authorized to view case 003.

[0091] If the disclosure level of a job posting is set to "all," all members can view the job posting. This is the case for job posting 005 shown in Figure 6. If one or more company IDs are registered in the non-disclosure company ID list for job posting 005, members belonging to the companies with those company IDs will not be authorized to view job posting 005.

[0092] In the "Asset Title" field, a title that provides an overview of the asset related to the solicited project is registered. For example, "Desk" is registered as the asset title corresponding to Project 001. As can be seen from the asset titles shown in Figure 6, various assets can be registered as solicited projects, such as desks, patents, project plans, conference rooms, and employee welfare facilities.

[0093] "Asset details" is where explanatory items that allow a detailed understanding of the asset content related to the solicitation are registered. "Asset classification" is where classifications such as equipment, patents, ideas, space and facilities are registered. "Asset transfer amount" is where the amount related to the transfer or use of the asset is registered.

[0094] The number of assets to be transferred or used is registered in the "number of offers." For example, the number of desks corresponding to asset ID=1 is 100.

[0095] In "Transfer / Use," information is registered to identify whether the property being offered is for transfer or use. For example, Case 001 is for transfer, and the winner of Case 001 will receive 100 desks from the offeror on the condition that they pay the asset transfer amount.

[0096] The conference room in Item 004 is a solicited item for use, and the right to use the conference room will be granted by the solicitor to the winner of Item 004, subject to payment of the asset transfer amount. For example, if the conference room being solicited is located in Tokyo and the applicant's company is located in Osaka, by winning Item 004, the applicant will be able to use the conference room when on a business trip to Tokyo.

[0097] It is possible to adopt various variations in the setting of the disclosure level. For example, by selecting a specific item, the user may be able to control to whom the asset information is disclosed. More specifically, a screen for registering a job posting may be provided with check boxes for selecting companies to which the asset information is to be disclosed. Furthermore, the user may be able to control related information and functions by selecting one of predefined options. For example, a screen for registering a job posting may display a list from which the user can select the scope of asset information disclosure from "within the company," "within the community," and "all users."

[0098] The user device 500 may provide the user with a setting screen for setting various disclosure levels. For example, the setting screen may display check boxes for the user to select the targets for which the project will be disclosed by industry, such as "pharmaceuticals," "chemicals," "electrical equipment," "railways and buses," and "food." Furthermore, by displaying the names of companies corresponding to each industry on the setting screen, the user may be able to select the targets for which the project will be disclosed by "industry" and "company."

[0099] For example, suppose that the companies corresponding to "pharmaceuticals" are Company A, Company B, Company C, and Company D, the companies corresponding to "chemicals" are Company E, Company F, Company G, and Company H, and the companies corresponding to "electrical equipment" are Company I, Company J, Company K, and Company L.

[0100] In this case, the setting screen indicates that the industry of "pharmaceuticals" includes "Company A" to "Company D," and displays check boxes corresponding to "pharmaceuticals," "Company A," "Company B," "Company C," and "Company D." Furthermore, the setting screen indicates that the industry of "chemicals" includes "Company E" to "Company H," and displays check boxes corresponding to "chemicals," "Company E," "Company F," "Company G," and "Company H." Furthermore, the setting screen indicates that the industry of "electrical equipment" includes "Company I" to "Company L," and displays check boxes corresponding to "electrical equipment," "Company I," "Company J," "Company K," and "Company L."

[0101] For example, suppose a user checks the checkboxes corresponding to "pharmaceuticals" and "chemicals" but does not check the checkbox corresponding to "electrical equipment." In this case, the "electrical equipment" industry is excluded from the targets for which projects will be disclosed. Furthermore, suppose that the checkboxes corresponding to Companies A through C belonging to "pharmaceuticals" and Companies E through H belonging to "chemicals" are checked, but the checkbox corresponding to Company D belonging to "pharmaceuticals" is not checked. In this case, Companies A through C belonging to "pharmaceuticals" and Companies E through H belonging to "chemicals" are treated as targets for which projects will be disclosed, but Company D belonging to "pharmaceuticals" is excluded from the targets for which projects will be disclosed.

[0102] [Evaluation Input Database 126] Fig. 7 is a diagram showing an example of the evaluation input database 126. Evaluation information for the person being evaluated is registered in the evaluation input database 126. The evaluation information includes the subject of evaluation, the member ID of the person being evaluated, the member ID of the evaluator, and the evaluation result.

[0103] The evaluation input database 126 includes a recruiter evaluation section 126A and an applicant evaluation section 126B. The recruiter evaluation section 126A stores evaluation information for the recruiter (transferor). The applicant evaluation section 126B stores evaluation information for the applicant (transferee).

[0104] In the recruiter evaluation unit 126A, the target of evaluation (evaluated person) corresponds to the recruiter (transferor), and the evaluator corresponds to the applicant who applied for the recruitment project of the evaluated person and won the recruitment project. In the recruiter evaluation unit 126A, evaluations of the evaluated person are registered for each evaluator. Figure 7 shows an example in which members P1 and P2, who correspond to the evaluated person, have been evaluated by evaluator members. In particular, Figure 7 shows an example in which member P1 has been evaluated by each of evaluator members P5, P7, P11, and P12. The evaluation result (evaluation value) is expressed as a numerical value with 10 as the maximum value and 0 as the minimum value.

[0105] In the applicant evaluation section 126B, the evaluation target (evaluee) corresponds to the applicant (transferee) for the recruitment project, and the evaluator corresponds to the recruiter (transferor) of that project. Evaluations of the evaluatee are registered for each evaluator in the applicant evaluation section 126B. Figure 7 shows an example in which member P7, who is the evaluatee, is evaluated by members P1, P2, and P3, who are evaluators. Note that, although examples of evaluation results in the applicant evaluation section 126B are omitted in Figure 7, various evaluation results are registered there, just like in the recruiter evaluation section 126A.

[0106] When an applicant (transferee) completes a transaction with a recruiter (transferor), he / she uses the applicant device 300 to evaluate the recruiter (the evaluatee) as an evaluator. The evaluator's evaluation results are registered in the evaluation input database 126. When an applicant acquires another job from a recruiter who has previously acquired a job, the applicant evaluates the recruiter again. In this case, the average value of the previous evaluation result and the subsequent evaluation result is registered in the evaluation input database 126.

[0107] When the recruiter (transferor) completes a transaction with the applicant (transferee), he / she uses the recruiter device 200 to evaluate the applicant (appraisee) as an evaluator. The evaluator's evaluation results are registered in the evaluation input database 126. When a recruiter transfers another asset to an applicant with whom he / she has previously traded assets, the recruiter evaluates the applicant again. In this case, the average value of the previous evaluation result and the subsequent evaluation result is registered in the evaluation input database 126.

[0108] Therefore, the evaluation results registered in the evaluation input database 126 reflect the average value of each evaluator's evaluation of the evaluatee. Note that instead of the average value, a weighted average value calculated according to the number of evaluations or a deviation value, etc., may be used. Evaluation results by case ID may also be registered in the evaluation input database 126.

[0109] [Evaluation Summary Database 127] Fig. 8 is a diagram showing an example of the evaluation summary database 127. Department-specific evaluation information for the person being evaluated is registered in the evaluation summary database 127. The evaluation information by organization includes the evaluation target, the member ID of the person being evaluated, the ID of the company to which the person being evaluated belongs, the ID of the company to which the evaluator belongs, the department to which the evaluator belongs, and an evaluation summary.

[0110] 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 (transferor) corresponds to the evaluation target (evaluated person). In the applicant evaluation summary section 127B, the applicant (transferee) corresponds to the evaluation target (evaluated person). In the evaluation summary database 127, evaluation summaries for the evaluation targets are registered by department.

[0111] The evaluation summary is calculated based on the results of the evaluation input database 126. The department category includes each department, such as the "System Department" or the "Planning Department," that belongs to the company, as well as "Overall," which refers to the entire company. The evaluation summary is calculated for each such "department."

[0112] Figure 8 shows an example in which member P1 corresponds to the person being evaluated in the recruiter evaluation summary section 127A. The company ID of the person being evaluated is "00A." Therefore, member P1 belongs to company A. In Figure 8, data group 1271 represents company B's evaluation of member P1, who acts as a recruiter, and data group 1272 represents company C's evaluation of member P1, who acts as a recruiter.

[0113] Referring to data group 1271, it can be seen that the evaluation of company B is categorized 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 evaluation summary registers the average value of the evaluation corresponding to each categorized category.

[0114] For example, the evaluation summary corresponding to Company B as a whole is registered with the average value of the evaluation results of the members of Company B who evaluated member P1, who acts as a recruiter. In Figure 8, this value is set to "4.75". The evaluation summary corresponding to the System Department is registered with the average value of the evaluation results of the members of Company B who belong to the System Department and who evaluated member P1, who acts as a recruiter. In Figure 8, this value is set to "4.0". The evaluation summary corresponding to the Planning Department is registered with the average value of the evaluation results of the members of Company B who belong to the Planning Department and who evaluated member P1, who acts as a recruiter. In Figure 8, this value is set to "5.0".

[0115] As with data group 1271, the evaluation of company C in data group 1272 is classified into an evaluation of the entire company and an evaluation of each department within company C. Data groups 1271 and 1272 are data that evaluate recruiters. Therefore, the evaluation summaries registered in data groups 1271 and 1272 are recruiter evaluation summaries.

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

[0117] The applicant evaluation summary section 127B has a similar structure to the recruiter evaluation summary section 127A, except that the evaluation target is the "applicant" rather than the "recruiter." Therefore, the explanation of the applicant evaluation summary section 127B will be replaced by the explanation of the recruiter evaluation summary section 127A that has already been given.

[0118] The sharing server 100 identifies the evaluation results of each member using the evaluation input database 126, and identifies the affiliation of each member using the member database 122. The sharing server 100 updates the data in the evaluation summary database 127 based on these identification results.

[0119] 8 shows only members P1 and P7 as evaluatees, other members P2 to P6, member P8, member P9, etc. are also registered as evaluatees in the evaluation summary database 127. The evaluation summary database 127 may include data in which the same member is evaluated as both a recruiter and an applicant. For example, the evaluation summary database 127 shown in FIG. 8 may register an applicant evaluation summary for member P1 in addition to a recruiter evaluation summary for member P1.

[0120] [Functions of the Sharing Server, Recruiter Device, and Applicant Device] FIGS. 9 to 11 are diagrams for explaining the functions of the sharing server, recruiter device, and applicant device.

[0121] 9, the sharing server 100 functionally includes a community registration unit 140, a company registration unit 141, a member registration unit 142, a member search unit 143, and a case registration unit 144. These various functions are realized by a processor 101, a memory 102, a storage 103, and a communication interface 104 provided in the sharing server 100.

[0122] The community registration unit 140 has a function of registering a community in the community database 123. A system administrator who manages the matching system 1 inputs information about the community into the sharing server 100 using an operation unit such as a keyboard (not shown).

[0123] The information about the community includes the community name and information about the companies that belong to the community. The community registration unit 140 registers the community in the community database 123 according to the input by the system administrator (step S1). The community registration unit 140 further has a function of updating the information about the community registered in the community database 123.

[0124] The company registration unit 141 has a function of registering new companies that will join the matching system 1. A system administrator inputs information about the company into the sharing server 100 using an operation unit such as a keyboard.

[0125] The information about the company includes information such as the company name and address. The company registration unit 141 registers the company in the company database 121 according to the input by the system administrator (step S2). The company registration unit 141 further has a function of updating information about companies that have already been registered.

[0126] The member registration unit 142 has a function of registering (signing up) new members to join the matching system 1. The member registration unit 142 issues a member ID and a password in response to a request from a person belonging to a company that is a member of the matching system 1. A person who wishes to become a member executes the sign-up process using a personal computer or the like (step S3).

[0127] Specifically, a person wishing to become a member enters information such as their name, the company they belong to, and their department into a personal computer or the like, and transmits the entered information to the sharing server 100. The member registration unit 142 registers the entered information in the member database 122. New members can sign in to the sharing 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.

[0128] FIG. 9 shows two applicant devices 300. One is a device intended to be operated by a manager of the applying company. The other is a device intended to be operated by someone other than the manager at the applying company. The manager of the applying company is a managerial position such as a department head, and is the superior of the applicants who are his or her subordinates. The manager of the applying company plays the role of an approver who approves applications for job openings by his or her subordinates.

[0129] The member search unit 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 unit 143 provides information on members registered in the member database 122 to the recruiter device 200 and the applicant device 300.

[0130] When the recruiter's device 200 receives a search operation for the recruiter, it executes a member search process (step S4A). This allows the recruiter to, for example, view applicant information. The recruiter can select from multiple applicants an applicant to whom assets related to the job offer will be transferred, taking into account the applicant information. Similarly, when the applicant device 300 receives a search operation for a manager who is the superior of a certain applicant, it executes a member search process (step S4A).

[0131] Furthermore, when the applicant device 300 receives an applicant search operation, it executes a member search process (step S4B). This allows the applicant to, for example, view information about the recruiter. The applicant can select a case that includes the assets they wish to acquire from among multiple recruiting cases, taking into account the recruiter information.

[0132] The member search process (step S4A) executed by the recruiter device 200 and the process of the member search unit 143 will be described in detail later with reference to Fig. 17. The member search process (step S4B) executed by the applicant device 300 and the process of the member search unit 143 will be described in detail later with reference to Fig. 18.

[0133] The request registration unit 144 has a function of registering a recruitment request in the recruitment request database 124. When the recruiter device 200 receives an operation to input a recruitment request, it executes a process to register the recruitment request (step S5). In the process of registering the recruitment request, the recruiter device 200 transmits information about the recruitment request to the sharing server 100. The request registration unit 144 registers the received information about the recruitment request in the recruitment request database 124.

[0134] The recruiting request registration process (step S5) executed by the recruiter device 200 and the process of the request registration unit 144 will be described in detail later with reference to FIG.

[0135] 10 , the sharing 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 realized by a processor 101, a memory 102, a storage 103, and a communication interface 104 that the sharing server 100 includes.

[0136] The job extraction unit 145 has a function of extracting job listings that can be viewed by applicants. The application unit 146 has a function of submitting an application by an applicant to a manager (the applicant's superior). The approval unit 147 has a function of sending the contents of the application for the job listing to the recruiter on the condition that approval of the application has been received from the 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 device 300 of the applicant and the manager of the application result (acceptance, rejection) corresponding to the information.

[0137] The application unit 146, approval unit 147, and notification unit 148 realize, by means of a workflow system, notifications to the administrator requesting approval, notifications of applicants to the recruiter, and notifications of application results to applicants.

[0138] When the applicant device 300 receives an operation from the applicant requesting a search for a job, the applicant device 300 executes a search process for the job (step S6). In the search process for the job, the applicant device 300 transmits a search request to the job extraction unit 145 of the sharing server 100.

[0139] When the request extraction unit 145 receives a search request, it extracts requests that the applicant is permitted to view from among the requests registered in the request database 124, and transmits the extracted requests to the applicant device 300. The request extraction unit 145 determines whether the applicant is permitted to view the requests based on the disclosure range set for the requests. The disclosure range is determined by the disclosure information.

[0140] Based on the determination result, the case extraction unit 145 extracts cases that are permitted to be disclosed to the applicant who received the search request from among the cases registered in the case database 124. The case extraction unit 145 transmits the cases that are permitted to be viewed by the applicant to the applicant device 300.

[0141] The applicant device 300 receives the recruitment requests from the request extraction unit 145. The applicant device 300 displays the received recruitment requests on the display 305 (step S7). This allows the applicant to view the recruitment requests as search results.

[0142] The job search process (step S6), the job display process (step S7), and the process of the job extractor 145 will be described in detail later with reference to FIG.

[0143] The applicant operates the applicant device 300 to select an application target from the recruitment jobs displayed on the display 305. The applicant device 300 executes application processing in response to the applicant's operation (step S8). In the application processing, the applicant device 300 transmits application information indicating the job to be applied for to the application unit 146 of the sharing server 100.

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

[0145] The application unit 146 transmits the subordinate's application information to the applicant device 300 corresponding to the identified superior's member ID. The application information transmitted to the applicant device 300 includes the "asset title," "asset details," "asset classification," "asset transfer amount," "number of applications," and "transfer / use" registered in the solicited job database 124. The manager checks the details of the solicited job for which the subordinate has applied on his or her own applicant device 300.

[0146] The manager performs an operation to approve the application on 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 transmits approval information to the approval unit 147 of the sharing server 100. As a result, approval information, which is an example of an approval notice, is transmitted from the applicant device 300 of the manager (approver) to the approval unit 147.

[0147] The approval unit 147 accepts an applicant's application on the condition that approval information has been received from the applicant device 300. In this way, an applicant's application is accepted on the condition that it is approved by the manager to whom the applicant belongs. Therefore, the manager can check in advance the content of the recruitment job for which his or her subordinate is applying.

[0148] 10 shows the flow when the manager approves an application. If an operation to reject the application is accepted in step S9, rejection information is transmitted from the applicant device 300 of the manager to the approval unit 147. If the rejection information is received, the approval unit 147 may notify the applicant device 300 of the applicant that the application has been rejected.

[0149] The approval unit 147, which has accepted the applicant's application, transmits application information to the recruiter device 200. The application information includes information about the applicant and the details of the job offer to which the applicant is applying. The recruiter device 200 displays the details of the application information on the display 205 (step S10). The recruiter checks the applicant and the job offer based on the display 205 and decides whether to accept or reject the applicant's application.

[0150] The recruiter inputs the result of the decision of acceptance or rejection to the recruiter device 200. The recruiter device 200 accepts the input result (step S11). The recruiter device 200 transmits the accepted result of acceptance or rejection to the notification unit 148 of the sharing server 100.

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

[0152] The applicant device 300 of the applicant and the applicant device 300 of the administrator display the application results on the display 305 (steps S12 and S13). The applicant and the administrator confirm the application results by looking at the display 305. If the application is accepted, a procedure is carried out to transfer the target assets between the recruiter and the applicant.

[0153] 11 , the sharing server 100 functionally includes a rating receiving unit 151 and a rating output unit 152. These functions are realized by a processor 101, a memory 102, a storage 103, and a communication interface 104 provided in the sharing server 100.

[0154] The evaluation receiving unit 151 has a function of receiving an evaluation of an applicant input by the recruiter in the recruiter device 200. The evaluation output unit 152 has a function of outputting information indicating an evaluation of an applicant to the recruiter device 200. When a transaction related to a recruitment matter with an applicant is completed, the recruiter inputs an evaluation of the applicant in the recruiter device 200. There are various points that the recruiter uses to evaluate an applicant.

[0155] For example, if the recruiter can communicate smoothly with the applicant and complete the transaction in a short time, the recruiter will likely give the applicant a high rating. Conversely, if the applicant frequently requests changes to the amount of assets to be transferred or if the applicant's response to transaction communications is poor, the recruiter will likely give the applicant a low rating.

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

[0157] The recruiter device 200 transmits the received evaluations to the evaluation receiving unit 151 of the sharing server 100. The evaluation receiving unit 151 updates the evaluation input database 126 and the evaluation summary database 127 based on the received evaluations. As a result, the information in the applicant evaluation unit 126B is updated in the evaluation input database 126, and the information in the applicant evaluation summary unit 127B is updated in the evaluation summary database 127.

[0158] The process of step S16A executed by the recruiter device 200 and the process of the evaluation receiving unit 151 will be described in detail later with reference to FIG.

[0159] When the recruiter accepts an operation to view the evaluation of the applicant, the recruiter device 200 executes a view request process (step S17A). In the view request process, the recruiter device 200 transmits a view request to the evaluation output unit 152 of the sharing server 100. In response to the view request, the evaluation output unit 152 transmits 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).

[0160] The processes of steps S17A and S18A executed by the recruiter device 200 and the process of the evaluation output unit 152 will be described in detail later with reference to FIG.

[0161] Figure 12 is a diagram further explaining the functions of the applicant device 300. Here, the input and output of evaluations of the recruiter will be explained using Figure 12. The evaluation receiving unit 151 further has a function to receive an evaluation of the recruiter input by the applicant on the applicant device 300. The evaluation output unit 152 further has a function to output information indicating the evaluation of the recruiter to the applicant device 300. When an applicant completes a transaction with the recruiter regarding a recruitment matter, the applicant inputs an evaluation of the recruiter to the applicant device 300. There are various points that an applicant can consider when evaluating a recruiter.

[0162] For example, if the applicant can communicate smoothly with the offeror and complete the transaction in a short time, the applicant will likely rate the offeror highly. Conversely, if the offeror frequently requests changes to the transaction amount or if the assets involved in the transaction are in poor condition, the applicant will likely rate the offeror poorly.

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

[0164] The applicant device 300 transmits the received evaluation to the evaluation receiving unit 151 of the sharing server 100. The evaluation receiving unit 151 updates the evaluation input database 126 and the evaluation summary database 127 based on the received evaluation. As a result, the information in the recruiter evaluation unit 126A is updated in the evaluation input database 126, and the information in the recruiter evaluation summary unit 127A is updated in the evaluation summary database 127.

[0165] The processing of step S16B executed by applicant device 300 and the processing of evaluation receiving section 151 will be described in detail later with reference to FIG.

[0166] When the applicant device 300 receives an operation to view the applicant's evaluation of the recruiter, it executes a view request process (step S17B). In the view request process, the recruiter device 200 transmits a view request to the evaluation output unit 152 of the sharing server 100. In response to the view request, the evaluation output unit 152 transmits 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).

[0167] The processing of steps S17B and S18B executed by applicant device 300 and the processing of evaluation output section 152 will be described in detail later with reference to FIG.

[0168] [Details of Processing by the Request Registration Unit 144 and the Recruiter Device 200] Fig. 13 is a diagram for explaining the procedure for registering a request in the request database 124. Step S5 in Fig. 9 and the function of the request registration unit 144 will be described in more detail with reference to Fig. 13.

[0169] A recruiter who registers a recruitment request first signs in to the sharing server 100 using the recruiter device 200. This establishes a logical communication path identified by the recruiter's member ID between the recruiter device 200 and the sharing server 100. Next, the recruiter inputs asset information and disclosure information for the recruitment request into the recruiter device 200 using the operation unit 206, such as a mouse and keyboard.

[0170] The asset information includes "asset title," "asset details," "asset classification," "asset transfer amount," "number offered," and "transfer / use." The disclosure information includes the disclosure level. The disclosure information may include the IDs of "non-disclosure" companies, depending on the offeror's choice.

[0171] 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 that accepts an operation to input the contents of the recruitment request and an operation to input the disclosure information.

[0172] The recruiter device 200 receives input of the asset information and disclosure information of the recruitment request and executes a process of registering the recruitment request (step S5). In the process of registering the recruitment request, the recruiter device 200 transmits the asset information and disclosure information of the recruitment request to the sharing server 100.

[0173] The request registration unit 144 of the sharing server 100 acquires information about the recruiter (step S1441). Specifically, the request registration unit 144 identifies the company to which the recruiter belongs.

[0174] The sharing server 100 stores the member ID used when a member signs in to the sharing server 100 using the recruiter device 200 or the applicant device 300. When the sharing server 100 receives any information from the recruiter device 200 or the applicant device 300 in communication established using this member ID, it identifies the member who sent the information by the member ID used to sign in.

[0175] Therefore, when the case registration unit 144 receives asset information and disclosure information for a solicitation case from the recruiter device 200, it uses the member ID used to sign in to identify the recruiter operating the recruiter device 200. The case registration unit 144 uses the identified member ID, the member database 122, and the company database 121 to identify the member who is the recruiter and the company to which the recruiter belongs.

[0176] Next, the matter registration unit 144 executes a process of registering the solicited matter in the solicited matter database 124 (step S1442). Specifically, after generating a matter ID, the matter registration unit 144 registers company information (company ID), disclosure information (disclosure level and ID of company not to be disclosed), asset information (asset title, asset content, asset classification, asset transfer amount, number of assets offered, and transfer / use information) and the like in the solicited matter database 124 in association with the generated matter ID.

[0177] According to this embodiment, the recruiter can freely control the disclosure scope of the recruitment request at the level of "within the company," "within the community," or "without restriction." As a result, the recruiter can prevent the recruitment request from being disclosed to specific companies, such as competitors, without the recruiter's intention.

[0178] According to this embodiment, companies that are not to be disclosed can be set separately from the disclosure level. Therefore, the recruiter can set the disclosure range by excluding some of the companies that have a community relationship with the recruiter's company. As a result, it is possible to prevent information about recruitment opportunities from being leaked to specific companies within the community.

[0179] Instead of or in addition to the non-disclosure company ID list, a non-disclosure member ID list for registering member IDs for which disclosure of recruitment requests is prohibited may be provided in the recruitment request database 124. The recruiter device 200 may accept an operation to designate a member for whom disclosure of recruitment requests is prohibited, and transmit the member's ID to the sharing server 100. The sharing server 100 may not provide recruitment requests corresponding to a member whose member ID is listed on the non-disclosure member ID list. In this way, the recruiter device 200 may accept either a company or a member as a target for whom disclosure of recruitment requests is prohibited.

[0180] Fig. 14 is a diagram for explaining the procedure for searching for recruitment requests from the database 120. The processes of steps S6 and S7 in Fig. 10 and the function of the request extraction unit 145 will be explained in more detail with reference to Fig. 14.

[0181] When the applicant device 300 receives an operation from the applicant requesting a search for a job, the applicant device 300 executes a search process for the job (step S6). In the search process for the job, the applicant device 300 transmits a search request to the job extraction unit 145 of the sharing server 100.

[0182] When the request extraction unit 145 receives a search request, it extracts requests that the applicant is permitted to view from among the requests registered in the request database 124. To this end, the request extraction unit 145 executes the processes of steps S1451 and S1452.

[0183] Steps S1451 and S1452 are processes for extracting jobs that are permitted for viewing by the applicant based on the disclosure scope set for the job. In step S1451, the applicant's company and the company's community are determined. In step S1452, job openings that can be disclosed are extracted.

[0184] [Process for Extracting Cases Based on Disclosure Scope] Step S1451 includes step S1451A and step S1451B.

[0185] In step S1451A, the company to which the applicant belongs is identified based on the member ID used at the time of signing in, company database 121, and member database 122.

[0186] In step S1451B, the community of the company to which the applicant belongs is identified based on the ID of the company to which the applicant belongs and the community database 123.

[0187] Step S1452 includes steps S1452 A and S1452 B. In step S1452 A, jobs that can be disclosed to the applicant are extracted from the job database 124 based on the community to which the applicant's company belongs and the disclosure level.

[0188] In step S1452B, among the jobs extracted in step S1452A, jobs for which the applicant's company is included in the non-disclosure company list are excluded, thereby extracting matching jobs that can be disclosed to the applicant.

[0189] [Process for Providing Extracted Projects] Next, the project extraction unit 145 transmits information about the matching projects to the applicant device 300 (step S1455). The applicant device 300 receives the matching projects. The applicant device 300 displays a list of the received matching projects as recruiting projects on the display 305 (step S7). The applicant is provided with recruiting projects that fall within the disclosure scope intended by the recruiter. As a result, when the applicant searches for recruiting projects, only recruiting projects that will not cause disadvantage to the recruiter are provided to the applicant. As a result, for example, it is possible to prevent information about the assets of the company to which the recruiter belongs from being leaked to competitors.

[0190] [Process for Registering Evaluation Results (Evaluation of Applicant)] Fig. 15 is a diagram for explaining the procedure for registering an evaluation of an applicant in database 120. Using Fig. 15, step S16A in Fig. 11 and the function of evaluation receiving unit 151 will be described in more detail.

[0191] When the recruiter has completed the 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 transmits the accepted evaluation to the evaluation receiving unit 151 of the sharing server 100. The information transmitted from the recruiter device 200 to the sharing server 100 includes the member ID and evaluation value (0 to 10) of the applicant to be evaluated.

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

[0193] If evaluation results for the evaluatee (applicant) have already been registered in the evaluation input database 126, the evaluation receiving unit 151 calculates the average value of the evaluation results for the evaluatee, including the value of the evaluation received this time. The evaluation receiving unit 151 updates the evaluation results registered in the evaluation input database 126 with the calculated average value. As a result, the average values ​​of the evaluations (evaluation results) for the evaluatee (applicant) are registered for each evaluator (recruiter) in the evaluation input database 126. This updates the information in the applicant evaluation unit 126B in the evaluation input database 126.

[0194] Next, the evaluation receiving unit 151 executes evaluation summary processing (step S1514A). In the evaluation summary processing, the evaluation receiving unit 151 calculates the average value of the evaluation results for the evaluatee (applicant) by company and department, and registers the calculation results in the evaluation summary database 127. As a result, the information in the applicant evaluation summary section 127B in the evaluation summary database 127 is updated.

[0195] For example, the evaluation receiving unit 151 identifies the evaluator (recruiter) using the member ID used by the recruiter device 200 to sign in to execute step S16A. Based on the evaluation information received in step S1513A, the company database 121, and the member database 122, the evaluation receiving unit 151 identifies the ID of the company to which the evaluator belongs, the department to which the evaluator belongs, the member ID of the person being evaluated, and the ID of the company to which the person being evaluated belongs. The "member ID" is an example of "identification information that enables the sharing server 100 including the evaluation receiving unit 151 to identify the affiliation (company and department) of a person accessing the sharing server 100."

[0196] The evaluation receiving unit 151 accesses the evaluation summary database 127 and detects a data row containing the specified IDs (the member ID of the person being evaluated, the ID of the company to which the person being evaluated belongs, and the ID of the company to which the evaluator belongs). The evaluation receiving unit 151 updates the value of the applicant evaluation summary corresponding to the detected data row.

[0197] [Process for Registering Evaluation Results (Evaluation of Recruiter)] Fig. 16 is a diagram for explaining the procedure for registering evaluations of recruiters in the database. Using Fig. 16, step S16B in Fig. 12 and the function of the evaluation receiving unit 151 will be described in more detail.

[0198] After completing the transaction with the recruiter, the applicant operates the applicant device 300 to input an evaluation of the recruiter into the applicant device 300. The applicant device 300 accepts the input evaluation (step S16B). The applicant device 300 transmits the accepted evaluation to the evaluation receiving unit 151 of the sharing server 100. The information transmitted from the applicant device 300 to the sharing server 100 includes the member ID of the recruiter who is being evaluated and the evaluation value (0 to 10).

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

[0200] If evaluation results for the ratee (recruiter) have already been registered in the evaluation input database 126, the evaluation receiving unit 151 calculates the average value of the evaluation results for the ratee, including the value of the evaluation received this time. The evaluation receiving unit 151 updates the evaluation results registered in the evaluation input database 126 with the calculated average value. As a result, the average values ​​(evaluation results) of the evaluations for the ratee (recruiter) are registered for each evaluator (applicant) in the evaluation input database 126. This updates the information in the recruiter evaluation unit 126A in the evaluation input database 126.

[0201] Next, the evaluation receiving unit 151 executes evaluation summary processing (step S1514B). In the evaluation summary processing, the evaluation receiving unit 151 calculates the average value of the evaluation results for the evaluatee (recruiter) by company and department, and registers the calculation results in the evaluation summary database 127. As a result, the information in the recruiter evaluation summary unit 127A is updated in the evaluation summary database 127.

[0202] For example, the evaluation receiving unit 151 identifies the evaluator (applicant) using the member ID used by the applicant device 300 to sign in to execute step S16B. Based on the evaluation information received in step S1513B, the company database 121, and the member database 122, the evaluation receiving unit 151 identifies the ID of the company to which the evaluator belongs, the department to which the evaluator belongs, the member ID of the person being evaluated, and the ID of the company to which the person being evaluated belongs. The "member ID" is an example of "identification information that enables the sharing server 100 including the evaluation receiving unit 151 to identify the affiliation (company and department) of a person accessing the sharing server 100."

[0203] The evaluation receiving unit 151 accesses the evaluation summary database 127 and detects a data row containing the specified IDs (the member ID of the person being evaluated, the ID of the company to which the person being evaluated belongs, and the ID of the company to which the evaluator belongs). The evaluation receiving unit 151 updates the value of the recruiter evaluation summary corresponding to the detected data row.

[0204] 8 includes the member ID of the person being evaluated (P1), the ID of the company to which the person being evaluated belongs (00A), and the ID of the company to which the evaluator belongs (00B). When a member belonging to the systems department of company B evaluates member P1, the evaluation is accepted in step S1513B.

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

[0206] More specifically, the evaluation receiving unit 151 sets the average value of the evaluations of the entire company B, including the evaluations received in step S1513B, as the recruiter evaluation summary corresponding to "Overall" in the data group 1271. Similarly, the evaluation receiving unit 151 sets the average value of the evaluations of the system part, including the evaluations received in step S1513B, as the recruiter evaluation summary corresponding to "System part" in the data group 1271.

[0207] Fig. 17 is a diagram for explaining the procedure for displaying the evaluation of an applicant and the search results of members on the display 205. Using Fig. 17, step S4A (processing of the recruiter device 200) and the function of the member search unit 143 in Fig. 10, as well as steps S17A and S18A and the function of the evaluation output unit 152 in Fig. 11 will be explained in more detail.

[0208] [Processing for Outputting Applicant Evaluation Summary] First, the processing of steps S17A, S18A, S1521A, and S1522A shown in FIG. 17 will be described.

[0209] When the recruiter accepts an operation to view the evaluation of an applicant, the recruiter device 200 executes a view request process (step S17A). In the view request process, the recruiter device 200 transmits a view request to the evaluation output unit 152 of the sharing server 100. In response to the view request, the evaluation output unit 152 selects from the evaluation summary database 127 an applicant evaluation summary for which the recruiter (view requester) has permission to view (step S1521A).

[0210] The recruiter who made the viewing request is authorized to view the applicant evaluation summary for the entire company to which the recruiter belongs and the applicant evaluation summary for the department to which the recruiter belongs. The recruiter who made the viewing request is not authorized to view any evaluation summaries other than these. The evaluation output unit 152 determines the viewing authority based on the member ID of the recruiter who sent the viewing request, the company database 121, and the member database 122. The "member ID" is an example of "identification information that allows the sharing server 100 including the evaluation receiving unit 151 to identify the affiliation (company and department) and viewing authority of a person who has accessed the sharing server 100."

[0211] The evaluation output unit 152 selects an applicant evaluation summary corresponding to the viewing authority from the evaluation summary database 127. The evaluation output unit 152 transmits data including the selected applicant evaluation summary to the recruiter device 200 (step S1522A). In addition to the applicant evaluation summary, the transmitted data includes the applicant's (evaluated) membership ID, information about the company to which the applicant belongs, information about the department to which the applicant belongs, etc. The transmitted data may include applicant evaluation summaries corresponding to each of multiple applicants (evaluated), depending on the viewing request.

[0212] Upon receiving the applicant evaluation summary, the recruiter device 200 displays the applicant evaluation summary on the display 205 together with information about the company to which the applicant belongs and information about the department to which the applicant belongs (step S18A). When applicant evaluation summaries corresponding to multiple applicants (evaluated persons) are received, the recruiter device 200 displays the applicant evaluation summaries in a list of multiple applicants (evaluated persons).

[0213] In this way, when the sharing server 100 receives a viewing request in communication established by a member ID that can identify the company and department to which the recruiter belongs, it sends an applicant evaluation summary, which is an example of evaluation information, to the recruiter device 200 of the recruiter that sent the viewing request.

[0214] [Process for Searching for Members (Applicants)] Next, with reference to FIG. 17, the processes in steps S4A, S19A, and S1431A to S1433A will be described.

[0215] When the recruiter device 200 receives a search operation from the recruiter, it executes a member search process to search for information about the applicant (step S4A). In the member search process, the recruiter device 200 transmits a search request to the member search unit 143 of the sharing server 100. The search request includes a reference value for excluding members with low applicant evaluations from the search. This reference value is determined, for example, based on the value of the applicant evaluation summary.

[0216] The member search unit 143, which has received the search request, identifies the company to which the recruiter who sent the search request belongs (step S1431A). Here, the company identified in step S1431A is referred to as "company Xa."

[0217] The member search unit 143 identifies the recruiter operating the recruiter device 200 by using the member ID used when the recruiter device 200 signed in to the sharing server 100. The member search unit 143 identifies the company Xa to which the recruiter belongs by using the company database 121 and the member database 122.

[0218] Next, the member search unit 143 extracts from the evaluation summary database 127 members whose applicant evaluation summary values ​​for the identified company Xa as a whole exceed a reference value (step S1432A). In other words, the member search unit 143 extracts search results by excluding members who have low evaluations for the company Xa as a whole.

[0219] It should be noted here that the member search unit 143 determines whether the evaluation is low based on the applicant evaluation summary. That is, member α, who has the authority of both an applicant and a recruiter, may act as an applicant or as a recruiter. Therefore, as evaluation summaries for such member α, an applicant 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 an applicant. In this case, member α may be excluded from the extraction targets in step S1432A.

[0220] The sharing server 100 may be provided with a function for receiving setting information of the reference value from the recruiter device 200 of each company. This allows each company to exclude members with low evaluations based on their own reference value from the search results.

[0221] Next, the member search unit 143 outputs the extracted member information as a search result to the recruiter device 200 that made the search request (step S1433A). The recruiter device 200 displays the received search results in a list on the display 205 (step S19A).

[0222] As a result, the recruiter can view the search results excluding members with low overall ratings of the company to which the recruiter belongs on the display 205. Therefore, when selecting a transferee from among applicants, the recruiter can save the trouble of visually excluding members with low overall ratings of the company.

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

[0224] Fig. 18 is a diagram for explaining the procedure for displaying evaluations of recruiters and search results of members on the display 305. Using Fig. 18, step S4B (processing of applicant device 300) and the function of member search unit 143 in Fig. 10, as well as steps S17B and S18B in Fig. 12 and the function of evaluation output unit 152 will be explained in more detail.

[0225] [Processing for Outputting Recruiter Evaluation Summary] First, the processes of steps S17B, S18B, S1521B, and S1522B shown in FIG. 18 will be described.

[0226] When the applicant device 300 receives an operation to view the applicant's evaluation of the recruiter, the applicant device 300 executes a view request process (step S17B). In the view request process, the applicant device 300 transmits a view request to the evaluation output unit 152 of the sharing server 100. In response to the view request, the evaluation output unit 152 selects from the evaluation summary database 127 a recruiter evaluation summary for which the applicant (view requester) has permission to view (step S1521B).

[0227] An applicant who has made a viewing request is authorized 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 viewing request is not authorized to view any evaluation summaries other than these. The evaluation output unit 152 determines the viewing authority based on the member ID of the applicant who sends the viewing request, the company database 121, and the member database 122. The "member ID" is an example of "identification information that allows the sharing server 100 including the evaluation receiving unit 151 to identify the affiliation (company and department) and viewing authority of a person who has accessed the sharing server 100."

[0228] The evaluation output unit 152 selects a recruiter evaluation summary corresponding to the viewing authority from the evaluation summary database 127. The evaluation output unit 152 transmits data including the selected recruiter evaluation summary to the applicant device 300 (step S1522B). The transmitted data includes the recruiter evaluation summary as well as the member ID of the recruiter (person being evaluated), information about the company to which the recruiter belongs, information about the department to which the recruiter belongs, etc. The transmitted data may include recruiter evaluation summaries corresponding to each of multiple recruiters (persons being evaluated) depending on the viewing request.

[0229] Upon receiving the recruiter evaluation summary, the applicant device 300 displays the recruiter evaluation summary together with information about the company to which the recruiter belongs and information about the department to which the recruiter belongs on the display 305 (step S18B). When receiving recruiter evaluation summaries corresponding to multiple recruiters (evaluated persons), the applicant device 300 displays the recruiter evaluation summaries in a list of multiple recruiters (evaluated persons).

[0230] In this way, when the sharing server 100 receives a viewing request in communication established using a member ID that can identify the company and department to which the applicant belongs, it sends a recruiter evaluation summary, which is an example of evaluation information, to the applicant device 300 of the applicant who sent the viewing request.

[0231] [Processing for Searching for Members (Recruiters)] Next, with reference to FIG. 18, the processing in steps S4B, S19B, and S1431B to S1433B will be described.

[0232] When the applicant device 300 receives a search operation from the applicant, it executes a member search process to search for information about the recruiter (step S4B). In the member search process, the applicant device 300 transmits a search request to the member search unit 143 of the sharing server 100. The search request includes a reference value for excluding members with low ratings as recruiters. This reference value is determined, for example, based on the value of the recruiter evaluation summary.

[0233] Upon receiving the search request, the member search unit 143 identifies the company to which the applicant who sent the search request belongs (step S1431B). Here, the company identified in step S1431B is referred to as "company Xb."

[0234] The member search unit 143 identifies the applicant operating the applicant device 300 by using the member ID used when the applicant device 300 signed in to the sharing server 100. The member search unit 143 uses the company database 121 and the member database 122 to identify the company Xb to which the applicant belongs.

[0235] Next, the member search unit 143 extracts members whose recruiter evaluation summary values ​​for the entire identified company Xb exceed a reference value from the evaluation summary database 127 (step S1432B). In other words, the member search unit 143 extracts search results by excluding members whose evaluations of the entire company Xb are low.

[0236] The sharing server 100 may be provided with a function for receiving setting information of the reference value from the recruiter device 200 of each company. This allows each company to exclude members with low evaluations based on their own reference value from the search results.

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

[0238] As a result, the applicant can view the search results excluding members whose companies have low overall ratings on the display 305. Therefore, when selecting a suitable recruiter from among the recruiters, the applicant can save the trouble of visually excluding members whose companies have low overall ratings.

[0239] In this embodiment, even if a member (recruiter) of a department of the company to which the applicant belongs has a low evaluation, the member (recruiter) is not excluded from the search results if the evaluation of the company as a whole is not low. However, the member search unit 143 may further exclude such a member (recruiter) from the search results.

[0240] [Viewable Range of Evaluation Summary Database 127] Fig. 19 is a diagram for explaining the viewable range of the evaluation summary database 127. Here, the viewable range will be explained using the recruiter evaluation summary section 127A of the evaluation summary database 127, which is also shown in Fig. 8, as an example.

[0241] The recruiter evaluation summary section 127A shown in Figure 19 includes evaluation summaries from companies B and C for member P1, who acts as a "recruiter." Member P1 belongs to company A. Company B's evaluation summary is categorized into "overall," "system department," and "planning department." Company C's evaluation summary is categorized into "overall," "planning department," etc. Members belonging to companies B and C view the evaluation summaries for member P1 as "applicants."

[0242] The viewing authority for the evaluation summary calculated from the overall evaluation of company B is granted to all members belonging to company B, as shown in the "viewable range" column in FIG.

[0243] The right to view the evaluation summary calculated from the evaluation of the Systems Department of Company B is granted to members of the Systems Department of Company B, but not to members other than the Systems Department of Company B. The right to view the evaluation summary calculated from the evaluation of the Planning Department of Company B is granted to members of the Planning Department of Company B, but not to members other than the Planning Department of Company B.

[0244] The right to view the evaluation summary calculated from the overall evaluation of Company C is granted to all members belonging to Company C. The right to view the evaluation summary calculated from the evaluation of the Planning Department of Company C is granted to members of the Planning Department of Company C, but not to members other than those of the Planning Department of Company C.

[0245] The above has described the viewable range using the recruiter evaluation summary section 127A as an example. In the matching system 1, the viewable range for the applicant evaluation summary section 127B (see FIG. 8) is also determined based on the same design concept as for the recruiter evaluation summary section 127A.

[0246] If the viewers are members of Company X's first division and Company X's second division, the viewers' authority to the overall evaluation summary of Company X, the evaluation summary of Company X's first division, and the evaluation summary of Company X's second division will be as shown in Table 401 in Figure 19. Here, when the applicant corresponds to the "viewer," the object to be viewed is the evaluation summary of the "recruiter." Conversely, when the recruiter corresponds to the "viewer," the object to be viewed is the evaluation summary of the "applicant."

[0247] A member belonging to the first division of company X can view the evaluation summary for company X as a whole and the evaluation summary for company X's first division, but cannot view the evaluation summary for company X's second division. A member belonging to the second division of company X can view the evaluation summary for company X as a whole and the evaluation summary for company X's second division, but cannot view the evaluation summary for company X's second division. A member belonging to company Y other than company X cannot view the evaluation summary for company X as a whole, the evaluation summary for company X's first division, and the evaluation summary for company X's second division.

[0248] The evaluation summary of company X as a whole, the evaluation summary of company X's first division, and the evaluation summary of company X's second division will not be disclosed to members of companies other than company X. Therefore, when evaluating a recruiter belonging to company X, a member belonging to company Y and acting as an applicant can objectively evaluate the recruiter belonging to company X without considering the relationship between the companies, etc. Similarly, when evaluating an applicant belonging to company X, a member belonging to company Y and acting as a recruiter can objectively evaluate the applicant belonging to company X without considering the relationship between the companies, etc.

[0249] Furthermore, evaluations made by members of Company X (evaluations of recruiters and applicants) are shared within Company X as recruiter evaluation summaries and applicant evaluation summaries. This allows evaluators to be aware that the accumulation of each evaluation produces useful information. This motivates evaluators to make accurate evaluations.

[0250] As a result, the accuracy of the recruiter evaluation summary and the applicant evaluation summary is improved. This allows the recruiter evaluation summary to be usefully used as reference data when selecting a job offer. Similarly, the applicant evaluation summary can be usefully used as reference data when selecting a recipient.

[0251] Furthermore, according to this embodiment, when the recruiter device 200 executes the member search process (step S4A), the search results excluding low-rated members are provided to the recruiter (step S1432A). Similarly, when the applicant device 300 executes the member search process (step S4B), the search results excluding low-rated members are provided to the recruiter (step S1432B). In other words, the matching system 1 has a filtering function that provides search results excluding low-rated members.

[0252] Therefore, when deciding on a transferee for a job posting, the recruiter can prevent, on a company-by-company basis, the mistaken adoption of a member with a low evaluation. Similarly, when deciding on a target to apply for from among a large number of jobs, the applicant can prevent, on a company-by-company basis, the mistaken selection of a job posting from a member with a low evaluation. The sharing server 100 may also perform filtering using the evaluation summary for each department.

[0253] A command signal instructing which of filtering using the evaluation summary for the entire company or filtering using the evaluation summary for each department to use may be transmitted from the recruiter device 200 to the sharing server 100. In this case, the sharing server 100 is provided with a function to change the evaluation summary used for filtering in response to the command signal.

[0254] [Example in which the disclosure range is set according to the disclosure level] Figure 20 is a diagram showing an example in which the disclosure range is set according to the disclosure level. Here, as shown in Figure 20, consider a case in which companies A to E form a community relationship, and company F does not form a community relationship with any company. In this case, the disclosure range of the job for which information is being recruited will be as shown in Table 402, depending on the company to which the recruiter belongs and the disclosure level set by the recruiter.

[0255] The disclosure levels "Level 1" to "Level 3" shown in FIG. 20 correspond to the three levels of "Company," "Within Community," and "All" already explained. Therefore, at Level 1, the recruiter's job posting is disclosed only to applicants who belong to the same company as the recruiter's company. At Level 2, the recruiter's job posting is disclosed to applicants who belong to companies that have a community relationship with the recruiter's company, in addition to the scope of Level 1. At Level 3, the recruiter's job posting is disclosed to applicants who belong to all companies, including the recruiter's company. However, if the recruiter specifies a company ID that is not to be disclosed, the company corresponding to that company ID is excluded from the companies to be disclosed, regardless of the disclosure level set. Among the disclosure levels in this embodiment, "Level 1" corresponds to "permitting disclosure of asset information (job posting information) to the first applicant and prohibiting disclosure of asset information to applicants who do not belong to the first group." "Level 2" corresponds to "allowing disclosure of asset information to applicants who belong to either the first group or a community group that has formed a community relationship with the first group, and prohibiting disclosure of asset information to applicants who do not belong to either the first group or a community group." "Level 3" corresponds to "allowing disclosure of asset information to applicants regardless of the group to which the applicant belongs."

[0256] Here, the above-mentioned levels 1 to 3 have been described as an example of multiple types of disclosure levels. However, the multiple types of disclosure levels are not limited to these. For example, a community may be divided into multiple small communities, and whether or not to disclose job openings may be set for each small community. More specifically, community 02 shown in FIG. 5 is divided into a first small community and a second small community. Company C belongs to the first small community, and companies D and E belong to the second small community. In this case, the recruiter of company D may be able to select whether the disclosure scope of his or her job openings should be within the scope of the first small community or the scope of the second small community.

[0257] The sharing server 100 may accept an operation to set a different disclosure range for each solicited case. For example, among the many solicited cases, cases 001 to 003 will be used as examples to explain a specific example of setting a different disclosure range for each solicited case.

[0258] For example, the disclosure range of job 001 may be limited to only companies A and C that belong to the community identified by community ID=03. Alternatively, the disclosure range of job 002 may be limited to only companies C, D, and E that belong to the community identified by community ID=02. Alternatively, the disclosure range of job 003 may be limited to companies C, D, and E that belong to the community identified by community ID=02 and companies A and C that belong to the community identified by community ID=03.

[0259] Company A may form a community separate from the community identified by community ID=01 or 02. For example, as shown by the dashed line in FIG. 20 , company A may form a community identified by community ID=Z with company Z. For example, if a recruiter belongs to company A, the recruiter's job postings may be disclosed to applicants belonging to company A and applicants belonging to company Z. This level of disclosure may be adopted as a variation of "Level 3" as shown in FIG. 20 .

[0260] In this case, "Level 3" corresponds to "allowing disclosure of asset information to applicants who belong to a specific community group (a community identified by community ID = Z) that is different from the first group (Company A) and the second-level community groups (Companies A to C) that have formed community relationships with the first group, and prohibiting disclosure of asset information to applicants who do not belong to either the first group or the specific community group."

[0261] Here, levels 1 to 3 have been described as an example of multiple levels, but even more levels may be set as multiple types of disclosure levels. As an example of an interface for the recruiter to set the disclosure range, a screen may be displayed on the user device 500 that displays check boxes for setting a desired level from multiple types of levels.

[0262] [Details of Asset Content] Fig. 21 is a diagram showing details of asset content included in the solicited job database 124. As shown in Fig. 21, asset content (job outline) is registered in the solicited job database 124 by job ID.

[0263] The asset contents include the items of project name (asset title), project details (detailed information), project registrant, and project registering company. The project name describes the title of the asset related to the project. The project details include a sentence (detailed information) that explains in detail the contents of the project. This sentence may also include the conditions required of applicants who will receive the asset transfer. The project registrant refers to the person who registered the project, i.e., the recruiter. The project registering company refers to the company to which the project registrant belongs.

[0264] The asset details are made public to users (applicants) who are permitted to disclose the job corresponding to the asset details. The sentences included in the job details may contain company terms. The company terms in such sentences are registered in the job database 124 as "index information" so that they can be linked to company terms in the company terminology database 137 (described later).

[0265] As already explained with reference to FIG. 1 , the user device 500 displays the in-house term in a different display mode from other terms. This allows the user to understand that the term is an in-house term. Furthermore, the user device 500 displays the intended meaning of the in-house term on the screen 550 in response to a user operation (for example, a click on the in-house term).

[0266] Applicants review the asset details of each project and select from among the many projects they wish to apply for. Applicants may meet with the project offeror as necessary before finally applying for the project. In addition, after the offeror selects a specific person from among the applicants as a provisional assignee, they may meet with the provisional assignee before completing the transaction.

[0267] The user device 500 may provide the recruiter and the applicant with a web conference environment for conducting these interviews. When a sentence including an in-house term is displayed on the display during the web conference, the user device 500 may display the in-house term in the manner shown in FIG. 1 .

[0268] [Other Databases] In the following, in addition to the various databases 121 to 124, 126, and 127 shown in FIG. 2, other databases employed in this embodiment will be described.

[0269] FIG. 22 is a diagram showing an example of the profile database 129. As shown in FIG. 22, the profile database 129 registers the profile information of members (users) by member ID. Some of the profile information may overlap with information registered in the member database 122. The profile information includes the member's name, age, and gender. Furthermore, the profile information includes affiliation information that can identify the member's affiliation (company and department). The affiliation information is an example of group information for identifying either the company or a department within the company.

[0270] Furthermore, the profile information includes the member's competency information, which is categorized by skills, experience, and qualifications.

[0271] Fig. 23 is a diagram showing an example of the in-house terminology database 137. As shown in Fig. 23, in-house terminology information is registered for each company ID in the in-house terminology database 137. The sharing server 100 refers to the in-house terminology database 137 to identify in-house terms for each company.

[0272] The internal term information includes affiliation information that can identify the member's affiliation (company and department). The affiliation information is an example of group information that identifies either the company or a department within the company. The affiliation information can also be said to be information that indicates the company and department in which the internal term to be registered is prevalent.

[0273] The in-house term information further includes the "name," "reading," and "meaning" of the term to be registered. For example, in the case of the in-house term "DX," "DX" is registered as the "name," "D-X" is registered as the "reading," and "D-X" is registered as the "meaning."

[0274] Another example of an in-house term is "application development." "Application development" is generally understood to mean developing applications for use on electronic devices such as smartphones. However, in a certain department of a company that handles electronic components, "application development" may mean "developing new uses for components." In such a case, the term "application development" and its meaning (developing new uses for components) are registered in the in-house term database 137.

[0275] [Explanation of Processing Procedures Related to Index Function] Next, various processing procedures related to the index function will be described with reference to Fig. 24 to Fig. 27. Fig. 24 is a flowchart showing the processing procedures related to the index function of the matching system 1.

[0276] In the flowchart shown in Figure 24, first, the sharing server 100 registers in-house terms in the in-house terminology database 137 (step Sw1). In step Sw1, the sharing server 100 functions as an in-house terminology registration unit. Next, the sharing server 100 registers a recruitment request in the recruitment request database 124 (step Sw2). In step Sw2, the sharing server 100 functions as a request registration unit. When registering a recruitment request in the recruitment request database 124, the request registration unit indexes in-house terms included in the recruitment request information.

[0277] Next, the sharing server 100 displays the indexed case information on the screen 550 (see FIG. 1 ) of the user device 500 (step Sw3). For example, if an in-house term is used in a sentence explaining the details of the case, the sentence is displayed on the screen 550 with the in-house term underlined. Instead of or in addition to underlining the in-house term, the in-house term may be displayed on the screen 550 in a color different from other words. In step Sw3, the sharing server 100 functions as a display unit.

[0278] FIG. 25 is a flowchart showing the processing steps of the in-house terminology registration unit (Sw1). First, a company employee compiles in-house terminology by using their company's system or the like (step Sw11). In other words, the employee creates something like an in-house glossary. Next, the employee downloads a registration template from the sharing server 100 (step Sw12). Next, the employee enters the necessary information into the template (step Sw13). The necessary information includes the in-house terminology, its meaning, and its meaning.

[0279] Next, the company representative accesses the sharing server 100 and obtains the representative's own profile information from the profile database 129 (step Sw14). The profile information includes the company ID of the company to which the representative belongs. The representative uploads the profile information and a template to the matching system 1 (step Sw15). The sharing server 100 obtains the profile information and the template. The sharing server 100 generates in-house terminology information based on the obtained profile information and template, and registers the generated in-house terminology information in the in-house terminology database 137 (step Sw16). As a result, in-house terms and their meanings are registered in the in-house terminology database 137. In-house terms and their meanings are also registered by company in the in-house terminology database 137.

[0280] The processing of steps Sw11 to Sw16 is executed for each company. As a result, in-house terminology information is registered for each company in the in-house terminology database 137. Note that the sharing server 100 may also register in-house terms collectively in the in-house terminology database 137 from an external file such as a CSV (Comma Separated Value) file.

[0281] 26 is a flowchart showing the processing steps of the job registration unit (Sw2). First, a recruiter who wishes to register a job in the system accesses the profile database 129 to obtain his / her company information (step Sw21). Next, the recruiter inputs the job information into the user device 500 (step Sw22). The job information includes various information such as the job content registered in the job database 124. The recruiter may input details of the job content using in-house terminology commonly used in the company to which the recruiter belongs.

[0282] Next, the sharing server 100 automatically searches for in-house terms included in the input job information (step Sw23). At this time, the sharing server 100 indexes the in-house terms found by the search and links them to in-house terminology information registered in the in-house terminology database 137. Next, the sharing server 100 registers the job information input by the recruiter in the recruiting job database 124 (step Sw24). As a result, the job information is registered in the recruiting job database 124 with the in-house terms and their meanings associated with each other.

[0283] 27 is a flowchart showing the processing procedure for displaying the meaning of company terminology on the screen in response to an applicant's operation. Here, we will explain the processing for providing a matching job that matches the applicant, taking into consideration the disclosure range for the job, and for informing the applicant of the meaning of company terminology as needed.

[0284] First, the sharing server 100 receives a search request for a job posting from an applicant (step Sw101). Next, the sharing server 100 determines the applicant's affiliation (step Sw102). The details of this process have already been described as step S1451.

[0285] Next, the sharing server 100 extracts matching cases (discloseable cases) (step Sw105). Details of this process have been described as step S1452. Next, the sharing server 100 transmits the matching cases (step Sw106). Details of this process have been described as step S1455. In this way, the sharing server 100 transmits the matching cases to the applicant device 300, thereby displaying the matching cases on the applicant device 300.

[0286] Next, the sharing server 100 detects a click operation on an in-house term corresponding to the registered index (step Sw107). Next, the sharing server 100 references the in-house term database 137 and transmits the meaning of the in-house term to the applicant device 300 (step Sw108). Next, the applicant device 300 displays the meaning of the in-house term on the display 305 (step Sw109). As a result, for example, the screen 550 shown in FIG. 1 is displayed on the display 305. In this way, the sharing server 100 transmits the meaning of the in-house term to the applicant device 300, thereby displaying the meaning of the in-house term on the applicant device 300.

[0287] As described above, this embodiment provides a matching system 1 that functions as a crowdsourcing platform. To use crowdsourcing to find suitable recipients for surplus assets, it is desirable to broaden the scope of crowdsourcing beyond a specific company or a small number of companies. In this case, it becomes necessary to consider the conflict of interest between the recruiter seeking a recipient for an asset-related project and the applicant who applies for the project. In this embodiment, the sharing server 100 communicates with the applicant device 300, operated by the applicant, via the communication interface 104. The sharing server 100 registers asset information indicating the target of the asset and disclosure information indicating the disclosure scope of the asset information in the database (step S1442). Based on the disclosure information, the sharing server 100 determines, from the asset information registered in the database 120, which asset information is permitted to be disclosed to the applicant (step S1452). The asset information includes detailed information about the asset (project details (transaction terms)). The sharing server 100 displays on the applicant device 300 the asset information that is permitted to be disclosed to the applicant and the meanings of terms (in-house terms including company terms) contained in the detailed information (steps Sw3, Sw106, Sw109).

[0288] Therefore, according to this embodiment, it is possible to select an appropriate applicant taking into consideration the interests of the applicant and the recruiter. Furthermore, according to this embodiment, it is possible to prevent applicants from misunderstanding the content of the asset information due to terms that are unfamiliar to them or that are used in a different way than usual.

[0289] Furthermore, according to this embodiment, users can reduce the effort required to provide supplementary explanations of in-house terminology when exchanging information about a project with users outside the company. Furthermore, the sharing server 100 can automatically index in-house terminology contained in project information. Therefore, users do not need to manually index in-house terminology. Furthermore, the sharing server 100 has a function for registering in-house terminology in the in-house terminology database 137. Therefore, users do not need to manually register in-house terminology in the in-house terminology database 137. Furthermore, users can recognize that in-house terminology is not understood by other companies, and can therefore understand cultural differences with other companies.

[0290] In this embodiment, "company terms" for a company are cited as an example of "in-house terms" that are prevalent in the group to which the user belongs. However, instead of or in addition to "company terms," ​​the embodiments described so far may also be applied to terms similar to company terms used in non-profit organizations, communities, and units (departments, sections, etc.) within those organizations.

[0291] In the present embodiment described above, a "company group" and a "departmental group within the same company" are examples of a "group." Applicants who do not belong to a company, such as freelancers, may also form a "group." A "company group" may also be formed by multiple companies.

[0292] The communication (S9 in FIG. 11) for transmitting approval information from the applicant device 300 of the manager who functions as the approver to the approval unit 147 is performed on a logical communication path identified by the member ID of the approver. "The approval unit 147 receiving the approval information on such a communication path" is an example of "receiving an approval notification in communication involving the identification information of the approver of the first applicant."

[0293] 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 functioning 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 functioning as an evaluator device."

[0294] 8 merely shows an example of data registered in the evaluation summary database 127. In this embodiment, it is also assumed that a member belonging to company A, in the position of an applicant, evaluates members belonging to companies A, B, C, ... and acting as recruiters. In this embodiment, it is also assumed that a member belonging to company B, in the position of an applicant, evaluates members belonging to companies A, B, C, ... and acting as recruiters. In this embodiment, it is also assumed that a member belonging to company A, in the position of a recruiter, evaluates members belonging to companies A, B, C, ... and acting as applicants. In this embodiment, it is also assumed that a member belonging to company B, in the position of a recruiter, evaluates members belonging to companies A, B, C, ... and acting as applicants.

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

[0296] In this 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 (recruiting-side second evaluator device) operated by one or more evaluators belonging to a second group different from the first group." In this 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."

[0297] 19 illustrates a systems department and a planning department as departments of company B. In this embodiment, "one of the systems department and 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.

[0298] As described above, the sharing server 100 determines which asset information of the recruitment request registered in the database 120 is permitted to be disclosed to the applicant based on various information that can identify the relationship between the applicant and the recruiter (member ID, company ID, community ID, affiliated company ID list, non-disclosure company ID list, disclosure level, non-disclosure target), and provides the applicant with the asset information that is permitted to be disclosed to the applicant. According to this embodiment, it is possible to select an appropriate applicant taking into consideration the conflict of interest between the company of the recruiter seeking a transfer or use of assets and the company of the applicant. This prevents confidential information of the recruiter's company from being leaked to competing companies through the content of the assets related to the recruitment request.

[0299] In this embodiment, a "company" and a "department within the same company" are examples of a "group of recruiters" and a "group of applicants," which are examples of a "group." Applicants who do not belong to a company may form a "group." A "corporate group" may be formed by multiple companies.

[0300] In this embodiment, the “companies that form a community relationship” is an example of a “community group.” In this embodiment, the information on “non-disclosure targets” included in the disclosure information is an example of “information that can identify targets to whom disclosure of asset information is prohibited.”

[0301] Of the disclosure levels in this embodiment, "Level 1" corresponds to "permitting disclosure of asset information to the first applicant and prohibiting disclosure of asset information to applicants who do not belong to the first group." "Level 2" corresponds to "permitting disclosure of asset information to applicants who belong to either the first group or a community group that has formed a community relationship with the first group and prohibiting disclosure of asset information to applicants who do not belong to either the first group or a community group." "Level 3" corresponds to "permitting disclosure of asset information to applicants regardless of the group to which the applicant belongs."

[0302] The recruiter device 200 and the applicant device 300 may not only be equipped with all of the processor, memory, communication interface, and input / output interface shown in FIG. 2, but may also be a thin client system using VDI (Virtual Desktop Infrastructure). A thin client system using VDI is a system in which a desktop environment on a server is transferred to a terminal in a remote location for use. The recruiter device 200, applicant device 300, and sharing server 100 do not necessarily have to be independent devices. When using a thin client system such as the one described above, the functions of the recruiter device 200, applicant device 300, and sharing server 100 can be provided on the same aggregation server.

[0303] The database 120 is not limited to a relational database, and an object-type or NoSQL-type database may also be used.

[0304] The sharing server 100 is an example of a computing device. The computing device may be configured by a server (such as an on-premise server or a cloud server) or a serverless system. Here, an on-premise server is a server installed and managed in facilities managed within a company. A cloud server is a server (a rented server) provided by another business via a network. A serverless system is a system in which computing and memory functions can be used only when necessary, without being aware of the existence of a server. Computing devices include servers and serverless systems. Servers include on-premise servers and cloud servers.

[0305] <Modification 1> Next, Modification 1 will be described with reference to Figures 28 to 32. Here, a share function that allows assets related to a job to be shared by a plurality of applicants will be described.

[0306] Fig. 28 is a diagram showing an example of the solicited request database 124A according to Modification 1. The solicited request database 124A shown in Fig. 28 has the additional function of being able to register "solicitation type" and "share establishment conditions" in comparison with the solicited request database 124 shown in Fig. 6.

[0307] As "recruitment type", information indicating whether the recruitment type of the recruitment item is "share", "single", or "unlimited" is registered.

[0308] A recruitment project for which the recruitment type is set to "share" requires applications from multiple applicants who satisfy the "share establishment conditions." For a recruitment project set to "share," the "share establishment conditions" are registered. The recruiter can set various "share establishment conditions." Figure 28 shows an example of setting share establishment conditions. The share establishment conditions set by the recruiter are registered in the recruitment project database 124A.

[0309] For example, if the share establishment condition for the training of Project 003 is set to five companies, and five companies apply for Project 003, the recruiter will grant each company the right to use the training corresponding to Project 003. For example, employees of the five companies that have been granted the right to use the training will be allowed to go to a predetermined training venue and take the training corresponding to Project 003. In this way, the share establishment condition is configured by the condition regarding the number of applicants for the shared asset.

[0310] A recruitment project with the recruitment type set to "single" is a project that does not allow "sharing" by multiple applicants. Project 001, Project 002, and Project 004 are examples of such projects. Anyone who wants to acquire a recruitment project that is set to "single" must apply for that project alone. For recruitment projects with the recruitment type set to "single," the "share establishment conditions" are not registered (BLANK).

[0311] A recruitment project with the recruitment type set to "no restrictions" is one that allows applications from both a single applicant and multiple applicants. Project 005 is such a project. Applicants for a recruitment project with "no restrictions" decide the number of applications they will make within the number of available positions. Applications will close when the total number of applications from each applicant reaches the number of available positions. For recruitment projects with the recruitment type set to "no restrictions", no "share establishment conditions" are registered (BLANK).

[0312] 29 is a diagram for explaining the procedure for registering a solicitation request in the solicitation request database, in relation to Modification 1. In comparison with FIG. 13, in FIG. 29, the solicitation type and share establishment conditions are added to the asset information input to the solicitor device 200.

[0313] In the first modification, when a recruiter registering a solicitation request inputs asset information and disclosure information of the solicitation request into the recruiter device 200, the recruiter can include the solicitation type and share establishment conditions of the solicitation request in the asset information. As already explained, the solicitation type is either share, sole, or unlimited. When the recruiter sets the solicitation type to share, he or she inputs the share establishment conditions.

[0314] The request registration unit 144 of the sharing server 100 registers the solicited request, including the solicitation form and share establishment conditions selected by the recruiter, in the solicited request database 124A (step S1442). The other contents shown in Figure 29 are the same as those already explained in Figure 13, so the explanation will not be repeated here.

[0315] The "recruitment type" information is an example of "recruitment type information that can identify that the asset is a shared asset in which multiple applicants are selected as the asset transfer recipient or user." The sharing server 100 registers the "recruitment type" information in the solicitation request database 124A in association with other asset information. The sharing server 100 further registers the "share establishment conditions" in the solicitation request database 124A in association with the "recruitment type" information.

[0316] [Processing Procedure for Recruitment Type Corresponding to "Share" (First Determination Process)] Fig. 30 is a flowchart showing the processing procedure of the first determination process related to Modification Example 1. Using the flowchart shown in Fig. 30, the processing procedure for a recruitment request corresponding to the recruitment type "share" will be described. 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 the recruitment request.

[0317] First, the sharing server 100 receives an application for a solicitation request (step Sa1). Next, the sharing server 100 determines whether the solicitation type of the solicitation request for which the application was made is "share" (step Sa2). If the solicitation type of the solicitation request for which the application was made is not "share," the sharing server 100 ends the processing based on this flowchart.

[0318] If the solicitation type of the requested request is "share," the sharing server 100 updates the parameters for determining the share establishment conditions (step Sa3). The parameters for determining the share establishment conditions differ for each request.

[0319] For example, if the share establishment condition is set to "five companies," the determination parameter is the number of applicant companies. The sharing server 100 identifies the applicant company each time an application is received. For example, the sharing server 100 adds 1 to the determination parameter each time an application is received from a different company, such as company A, B, C, etc.

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

[0321] If the determination parameters satisfy the share establishment conditions, the sharing server 100 notifies all applicants for the recruitment request and the recruiter that the share establishment conditions have been established (step Sa5). In other words, if the share establishment conditions have been established, the sharing server 100 confirms the applicants for the share-type recruitment request. Next, the sharing server 100 accepts an input of acceptance / rejection from the recruiter (step Sa6) and ends the processing based on this flowchart. Thereafter, the processing by the notification unit 148 described using FIG. 10 is executed.

[0322] [Processing Procedure for Recruitment Type Corresponding to "Single" (Second Determination Process)] Fig. 31 is a flowchart showing the processing procedure for the second determination process related to Modification Example 1. Using the flowchart shown in Fig. 31, the processing procedure for a recruitment request corresponding to the recruitment type "Single" will be described. 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 the recruitment request.

[0323] First, the sharing server 100 receives an application for a recruitment request (step Sa21). Next, the sharing server 100 determines whether the recruitment type of the application request is "single" (step Sa22). If the recruitment type of the application request is not "single," the sharing server 100 ends the processing based on this flowchart.

[0324] If the recruitment type of the requested job is "single," the sharing server 100 determines whether the number of assets desired by the recruiter matches the number of assets being recruited (step Sa23). If the number of assets desired by the recruiter does not match the number of assets being recruited, the number of assets desired by the applicant is less than the number of assets being recruited by the recruiter. In this case, the sharing server 100 ends the processing based on this flowchart. As a result, the applicant's application is not accepted.

[0325] If the number of assets desired by the recruiter matches the number of assets being offered, the sharing server 100 notifies the recruiter that an application has been made (step Sa24). Next, the sharing server 100 accepts an input of acceptance / rejection from the recruiter (step Sa25) and ends the processing based on this flowchart. Thereafter, the processing by the notification unit 148 described using FIG. 10 is executed.

[0326] [Processing Procedure for Recruitment Type Corresponding to "No Restrictions" (Third Determination Process)] Fig. 32 is a flowchart showing the processing procedure of the third determination process related to Modification Example 1. Using the flowchart shown in Fig. 32, the processing procedure for a recruitment request corresponding to the recruitment type "No Restrictions" will be described. 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 the recruitment request.

[0327] First, the sharing server 100 receives an application for a recruitment request (step Sa31). Next, the sharing server 100 determines whether the recruitment type of the application request is "unlimited" (step Sa32). If the recruitment type of the application request is not "unlimited," the sharing server 100 ends the processing based on this flowchart.

[0328] If the solicitation type of the requested item is "unlimited," the sharing server 100 determines whether applications have already been accepted from other applicants for this item (step Sa33). If applications have not yet been accepted from other applicants, this is the first application for this item. In this case, the sharing server 100 determines whether the number of assets desired by the applicant matches the number of items being solicited (step Sa34).

[0329] If the number of assets desired by the applicant matches the number of assets being offered, there is no need to wait for applications from other applicants. In this case, the sharing server 100 notifies the recruiter that an application has been received from the applicant (step Sa35). Next, the sharing server 100 accepts an input of acceptance / rejection from the recruiter (step Sa36) and ends the processing based on this flowchart. From this point on, the processing by the notification unit 148 described using FIG. 10 is executed.

[0330] If the number of assets desired by the applicant does not match the number of assets being offered, the sharing server 100 confirms that the number of assets desired by the applicant is less than the number of assets being offered (step Sa37). If the number of assets desired by the applicant is greater than the number of assets being offered, the sharing server 100 ends the processing based on this flowchart without accepting the application.

[0331] If the number of assets desired by the applicant is less than the number of assets being offered, the sharing server 100 associates the applicant with the number of assets desired by the applicant and stores the number of assets together with the corresponding recruitment case (step Sa38). Next, the sharing server 100 calculates "number of assets being offered - number of assets desired" to obtain the remaining number of assets being offered (step Sa39).

[0332] The sharing server 100 stores the remaining number of applications in association with the application. The sharing server 100 then waits for new applications. If a new application is made for the same application, the sharing server 100 determines YES in step Sa33. The sharing server 100 compares the remaining number of applications stored in association with the same application with the number of assets desired by the applicant in the new application. If the desired number is greater than the remaining number of applications, the sharing server 100 does not accept the application and ends the processing based on this flowchart.

[0333] If the desired number is not greater than the remaining number of applicants, the sharing server 100 stores the new applicant and the desired number in association with each other (step Sa41). Next, the sharing server 100 updates the remaining number of applicants by subtracting the new desired number from the remaining number of applicants (step Sa42). The sharing server 100 determines whether the updated remaining number of applicants has become 0 (step Sa43).

[0334] If the number of remaining assets after the update does not become 0, it means that the total number of assets desired by multiple applicants does not reach the number of assets being offered. In this case, it is necessary to wait for a new applicant who desires the number of assets that is insufficient to meet the number of assets being offered. Therefore, in this case, the sharing server 100 temporarily ends the processing based on this flowchart and waits for applications for the same recruitment item.

[0335] If the updated number of remaining applications becomes 0, the previous application and the new application result in "number of applications = total number of requests." In this case, the sharing server 100 notifies the recruiter of the application and accepts input of acceptance / rejection from the recruiter (steps Sa35 and Sa36). From this point on, the notification unit 148 executes the process described with reference to FIG. 10.

[0336] As described above, according to the first variation regarding the share function, assets related to the job offer can be shared by multiple applicants. By adding the share function to the embodiment described above, multiple applicants can acquire assets related to the job offer.

[0337] Moreover, in this embodiment, when an applicant searches for a job offer, the applicant is provided with a job offer that will not cause any disadvantage to the applicant (see FIG. 14). Therefore, according to the matching system 1 to which the first modification is applied, it is possible to prevent any disadvantage to the applicant, regardless of whether the assets related to the job offer are shared by multiple applicants or acquired by a single applicant.

[0338] When the recruitment project is an educational curriculum such as training that can be shared among multiple companies, it is undesirable for competitors to be included among the multiple applicants. This is because the content of the educational curriculum could leak information about the educational field in which the recruiting company is focusing to competitors. According to the matching system 1 to which the first modification is applied, even when such an educational curriculum is the recruitment project, it is possible to prevent the recruiter from being disadvantaged.

[0339] In addition, in Modification 1, the amount of burden per applicant may be reduced as the number of applicants sharing the recruitment job increases. For example, if the recruitment job is for training, the amount of burden per applicant may be determined by dividing the preset amount of the recruitment job by the number of applicants, and the amount of burden per applicant may be reduced as the number of applicants increases.

[0340] <Modification 2> Fig. 33 is a diagram showing the configuration of a matching system 1A according to Modification 2. As shown in Fig. 33, the functions of the sharing server 100 may be distributed among systems within each company. That is, instead of the centralized management type matching system 1, a decentralized management type matching system 1A may be adopted as the matching system 1.

[0341] The system configuration shown in Fig. 33 is common to companies A, B, C, D, etc. Each company is provided with a user device 500, a database 520, and a storage 503 for storing the database. 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.

[0342] The user device 500 is configured, for example, by a server. The user device 500 is an example of a computing device that includes the recruiter device 200 and the applicant device 300. Like the recruiter device 200 and the applicant device 300, the user device 500 includes a processor, a memory that stores programs and the like necessary for the processor's arithmetic processing, a communication interface, and the like.

[0343] Database 520 has the functions of database 120 shown in Fig. 2 and includes a job posting database 524 that replaces job posting database 124, as well as various other databases. Job postings proposed by employees of company A as recruiters are registered in company A's job posting database 524. Job postings proposed by employees of company B as recruiters are registered in company B's job posting database 524. Similarly, job postings proposed by employees of each company as recruiters are registered in other companies' job posting databases 524.

[0344] A disclosure permission list 521 is registered in the database 520. The disclosure permission list 521 includes a list of groups (companies, communities, etc.) that are permitted to disclose the job openings. The disclosure permission list 521 includes information corresponding to the "non-disclosure company ID list" and "disclosure level" among the information registered in the job openings database 124 shown in FIG. 6. The user device 500 registers the job openings (asset information) and the disclosure permission list 521 (disclosure information) that indicates the disclosure range of the job openings in the database 520.

[0345] The user device 500 of company A determines which companies or communities to disclose the recruitment opportunity to and which companies or communities not to disclose the recruitment opportunity to, based on the disclosure permission list 521. The user device 500 of company A transmits the recruitment opportunity to each company or community based on the determination. For example, if the user device 500 of company A determines to disclose a recruitment opportunity to company C but not to companies B and D, it transmits the recruitment opportunity to company C but does not transmit the recruitment opportunity to companies B and D.

[0346] Like the user device 500 of company A, the user device 500 of each of companies B, C, D, and so on operates based on the disclosure permission list 521. In this way, the user device 500 determines, from among the recruitment requests registered in the database 520, which recruitment requests are permitted to be disclosed to the applicant based on the disclosure permission list 521, and provides the applicant device 300 with the recruitment requests that are permitted to be disclosed to the applicant.

[0347] According to the second modification, there is no need to provide a server for centrally managing the system within the matching system.

[0348] <Variation 3> Variation 3 will be described with reference to Fig. 34. Fig. 34 is a diagram showing an example (variation 3) in which Kerberos authentication is applied to the matching system 1A. As shown in Fig. 34, Kerberos authentication may be applied to authentication between companies in the matching system 1A. Kerberos authentication is one of the network authentication methods applied between a server and a client.

[0349] Here, Modification 3 will be described using companies A and C as examples of multiple companies. As shown in FIG. 34 , authentication system 510A is installed in company A, and authentication system 510C is installed in company C. Authentication system 110 is a KDC (Key Distribution Center). Authentication system 110 is operated, for example, by an authentication authority. Authentication system 110 is configured by a server installed in the authentication authority. Authentication systems 510A and 510C are configured, for example, by user device 500 (see FIG. 33 ).

[0350] The authentication system 110 has a function of issuing a Ticket Granting Ticket (TGT). The authentication system 110 includes an Authentication Server (AS) and a Ticket Granting Server (TGS). The AS issues a Ticket Granting Ticket (TGT). The TGT is a ticket required to obtain a service ticket. The TGS issues a service ticket. By obtaining the service ticket, company A becomes able to send data to company C.

[0351] Here, an example will be described in which company A performs Kerberos authentication and then transmits a recruitment request to company C. Therefore, in this case, company A is the recruiter, and company C is the applicant. First, authentication system 510A requests authentication procedure from authentication system 110 (step Sk101). For example, authentication system 510A transmits information required for authentication, such as an ID and password for login, to the AS of authentication system 110. Authentication system 510A may use a public authentication key method for the authentication procedure.

[0352] The AS of the authentication system 110 performs authentication based on the information received from the authentication system 510A, and then transmits the TGT to the authentication system 510A (step Sk102). The authentication system 510A performs permission authentication for the case and obtains permission to issue a service ticket (step Sk103).

[0353] 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. The TGS checks the TGT and then transmits the service ticket for company C to the authentication system 510A (step Sk105).

[0354] Next, authentication system 510A transmits the service ticket to authentication system 510C of company C to obtain transmission permission from company C (step Sk106). Authentication system 510C obtains the service ticket. Authentication system 510C transmits data transmission permission to authentication system 510A (step Sk107).

[0355] Thereafter, the authentication system 510A transmits to the authentication system 510C, from among the job listings registered in the job listing database 524, those for which disclosure to company C is permitted by the disclosure permission list 521. This allows company A to allow applicants from company C to view its job listings. Note that instead of each company storing its own disclosure permission list 521, the authentication system 110 may store the disclosure permission list 521 for all companies. In this case, the authentication system 110 has a function of determining the viewing authority for job listings.

[0356] When Kerberos authentication is applied to the matching system 1, company A can use the acquired TGT to simplify the authentication procedure when sending a job to a company other than company C. For example, when company A wants to send a job to company D, the authentication system 510A of company A presents the acquired TGT and requests a service ticket for company D from TGS. If there is no problem with the TGT, TGS issues a service ticket for company D to authentication system 510A.

[0357] By using the Kerberos authentication described above, a single sign-on technique can be implemented in the matching system 1. As a result, for example, when company A sends data such as job postings to other companies, authentication does not need to be performed for each company. Note that companies A and C are shown here as an example of multiple companies. However, the Kerberos authentication described above may also be applied as an authentication method between three or more multiple companies.

[0358] The present embodiment described above has the following configuration: (a) In the matching system, a recruiter device operated by a recruiter transmits asset information (project information) for which a transferee is being sought and disclosure information indicating the scope of disclosure of the asset information to a computing device, the computing device registers the asset information together with the disclosure information in a database, the computing device determines, based on the disclosure information, asset information that is permitted to be disclosed to the first applicant from the asset information registered in the database, and provides the asset information that is permitted to be disclosed to the first applicant to the first applicant device.

[0359] (b) The matching system further includes a second applicant device operated by a second applicant different from the first applicant, and the computing device determines, based on the disclosure information, asset information that is permitted to be disclosed to the second applicant from among the asset information registered in the database, and provides the asset information that is permitted to be disclosed to the second applicant to the second applicant device.

[0360] (c) In the matching system, the matching system further includes a third applicant device operated by a third applicant different from the first applicant and the second applicant, and multiple disclosure levels are set for the disclosure information, and the computing device determines whether to allow disclosure for each of the first applicant to the third applicant depending on the disclosure level.

[0361] (d) In the matching system, a first applicant belongs to a first group and a second applicant belongs to a second group different from the first group, and the multiple disclosure levels include a first level and a second level, the first level corresponding to allowing disclosure of asset information to the first applicant and prohibiting disclosure of asset information to applicants who do not belong to the first group, and the second level corresponding to allowing disclosure of asset information to applicants who belong to either the first group or a community group that has formed a community relationship with the first group and prohibiting disclosure of asset information to applicants who do not belong to either the first group or the community group.

[0362] (e) In the matching system, the first applicant belongs to a first group and the second applicant belongs to a second group different from the first group, and the multiple disclosure levels include a first level, a second level, and a third level, the first level corresponding to allowing disclosure of asset information to the first applicant and prohibiting disclosure of asset information to applicants who do not belong to the first group, the second level corresponding to allowing disclosure of asset information to applicants who belong to either the first group or a community group that has formed a community relationship with the first group, and the third level corresponding to allowing disclosure of asset information to applicants who belong to a specific community group that is different from the first group and the second-level community group that has formed a community relationship with the first group, and prohibiting disclosure of asset information to applicants who do not belong to either the first group or the specific community group.

[0363] (f) In the matching system, the plurality of disclosure levels includes a disclosure level corresponding to allowing disclosure of asset information to applicants regardless of the group to which the applicants belong.

[0364] (g) In the matching system, attribute data that can identify community groups is registered in the database, and the computing device identifies applicants who are permitted to disclose asset information based on the disclosure information and the attribute data.

[0365] (h) In the matching system, the recruiter device accepts an operation to input a target group for which disclosure of asset information is prohibited, and transmits information that can identify the accepted target group to a computing device, and the computing device prohibits disclosure of asset information to applicants belonging to the target group even if the disclosure level is a level that allows disclosure of asset information to the target group.

[0366] (i) In the matching system, a first applicant belongs to a first company, and a second applicant belongs to a second company different from the first company.

[0367] (j) An evaluator device operated by one or more evaluators belonging to a first group includes an interface that accepts operations to input evaluations of applicants, a reception unit that accepts viewing requests, a display, and a processor that transmits the evaluations accepted by the interface and the viewing requests accepted by the reception unit to a computing device that can access the database, and when a viewing request is received, the processor displays the evaluations by one or more evaluators belonging to the first group on the display.

[0368] (k) A method for evaluating an applicant includes the steps of communicating with a first evaluator device operated by one or more evaluators belonging to a first group, receiving an evaluation of the 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 viewing request is received in a first communication established by identification information that can identify the applicant as belonging to the first group, transmitting the first evaluation information to the sender that sent the viewing request in the first communication.

[0369] (l) An evaluator device operated by one or more evaluators belonging to a first group includes an interface that accepts operations to input evaluations of recruiters, a reception unit that accepts viewing requests, a display, and a processor that transmits the evaluations accepted by the interface and the viewing requests accepted by the reception unit to a computing device that can access the database, and when a viewing request is received, the processor displays the evaluations by one or more evaluators belonging to the first group on the display.

[0370] (m) A method for evaluating a recruiter includes the steps of 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 viewing request is received in a first communication established by identification information that can identify the person as belonging to the first group, transmitting the first evaluation information to the sender that sent the viewing request in the first communication.

[0371] (n) A computing device included in a matching system that matches recruits with applicants, the computing device having a communication interface that communicates with a first applicant device operated by a first applicant, and a processor that accesses a database, wherein the processor registers asset information indicating the object of the asset and disclosure information indicating the scope of disclosure of the asset information in the database, and the processor determines, from the asset information registered in the database, asset information that is permitted to be disclosed to the first applicant based on the disclosure information, the asset information including detailed information regarding the content of the asset, and the processor displays, on the first applicant device, the asset information that is permitted to be disclosed to the first applicant and the meanings of terms included in the detailed information.

[0372] (o) A method for matching a recruiter with an applicant includes the steps of communicating with a first applicant device operated by a first applicant, registering asset information indicating the object of the asset and disclosure information indicating the scope of disclosure of the asset information in a database, and determining, from the asset information registered in the database, asset information that is permitted to be disclosed to the first applicant based on the disclosure information, wherein the asset information includes detailed information regarding the content of the asset, and the method further includes the step of displaying, on the first applicant device, the asset information that is permitted to be disclosed to the first applicant and the meanings of terms included in the detailed information.

[0373] [Aspects] Aspects of the present disclosure are listed below.

[0374] (Section 1) The matching system described in Section 1 is a matching system that matches an asset holder who acts as a recruiter and is seeking a recipient or use for the asset with an applicant who applies for the recruitment, and is equipped with 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 transmits asset information indicating the target of the asset and disclosure information indicating the scope of disclosure of the asset information to the computing device, the computing device registers the asset information together with the disclosure information in the database, and the computing device determines, based on the disclosure information, asset information that is permitted to be disclosed to the first applicant from the asset information registered in the database, and provides the asset information that is permitted to be disclosed to the first applicant to the first applicant device.

[0375] (Section 2) The matching system described in Section 2 is the matching system described in Section 1, further comprising a second applicant device operated by a second applicant different from the first applicant, and the computing device determines, based on the disclosure information, asset information registered in the database that is permitted to be disclosed to the second applicant, and provides the asset information that is permitted to be disclosed to the second applicant to the second applicant device.

[0376] (Section 3) The matching system described in Section 3 is the matching system described in Section 2, further comprising a third applicant device operated by a third applicant different from the first applicant and the second applicant, wherein multiple disclosure levels are set for the disclosure information, and the computing device determines whether or not to allow disclosure for each of the first to third applicants depending on the disclosure level.

[0377] (Section 4) The matching system described in Section 4 is the matching system described in Section 3, wherein the first applicant belongs to a first group and the second applicant belongs to a second group different from the first group, and the multiple disclosure levels include a first level and a second level, the first level corresponding to allowing disclosure of asset information to the first applicant and prohibiting disclosure of asset information to applicants who do not belong to the first group, and the second level corresponding to allowing disclosure of asset information to applicants who belong to either the first group or a community group that has formed a community relationship with the first group and prohibiting disclosure of asset information to applicants who do not belong to either the first group or the community group.

[0378] (Section 5) The matching system described in Section 5 is the matching system described in Section 3, wherein the first applicant belongs to a first group and the second applicant belongs to a second group different from the first group, and the multiple disclosure levels include a first level, a second level, and a third level, and the first level corresponds to allowing disclosure of asset information to the first applicant and prohibiting disclosure of asset information to applicants who do not belong to the first group, the second level allows disclosure of asset information to applicants who belong to either the first group or a community group that has formed a community relationship with the first group, and the third level corresponds to allowing disclosure of asset information to applicants who belong to a community different from the first group and a second-level community group that has formed a community relationship with the first group, and prohibiting disclosure of asset information to applicants who do not belong to either the first group or a community group.

[0379] (Section 6) The matching system described in Section 6 is the matching system described in Section 4, wherein the multiple disclosure levels include a disclosure level corresponding to allowing disclosure of asset information to applicants regardless of the group to which the applicant belongs.

[0380] (Section 7) The matching system described in Section 7 is the matching system described in Section 5 or 6, in which attribute data that can identify community groups is registered in the database, and the computing device identifies applicants who are permitted to disclose their asset information based on the disclosure information and the attribute data.

[0381] (Section 8) The matching system described in Section 8 is a matching system described in any one of Sections 3 to 7, in which the recruiter device accepts an operation to input a target group for which disclosure of asset information is prohibited, and transmits information that can identify the accepted target group to the computing device, and the computing device prohibits disclosure of asset information to applicants belonging to the target group even if the disclosure level is a level that allows disclosure of asset information to the target group.

[0382] (Section 9) The matching system described in Section 9 is a matching system described in any one of Sections 2 to 8, in which the first applicant belongs to a first company and the second applicant belongs to a second company different from the first company.

[0383] (Clause 10) The matching system described in clause 10 is a matching system described in any one of clauses 1 to 9, in which the recruiter device transmits to the computing device solicitation type information that can identify the asset as a shared asset in which one or more applicants are selected as the recipient or user of the asset, and the computing device registers the solicitation type information in the database in association with the asset information.

[0384] (Section 11) The matching system described in Section 11 is the matching system described in Section 10, in which the computing device registers the share establishment conditions in the database in association with the recruitment form information, the share establishment conditions being conditions regarding the number of applicants for the shared asset, and when the share establishment conditions are met, the computing device confirms the applicants for the shared asset.

[0385] (Clause 12) The matching system described in clause 12 is the matching system described in clause 1, wherein the recruiter device includes a first recruiter device operated by one or more recruiters belonging to a first group, the first recruiter device accepts input of an evaluation for a first applicant and transmits the accepted evaluation to a computing device, the computing device registers first evaluation information based on the evaluation received from the first recruiter device in a database for each applicant, and when the computing device receives a viewing request in a first communication established by identification information that can identify the applicant as belonging to the first group, it transmits the first evaluation information to the sender that sent the viewing request in the first communication.

[0386] (Clause 13) The matching system described in clause 13 is the matching system described in clause 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 input of an evaluation of the first applicant and transmits the accepted evaluation to a computing device, the computing device registers second evaluation information based on the evaluation received from the second recruiter device in a database for each applicant, and when the computing device receives a viewing request in a second communication established by identification information that can identify the applicant as belonging to the second group, it transmits the second evaluation information to the sender that sent the viewing request in the second communication.

[0387] (Item 14) The matching system described in item 14 is the matching system described in item 13, in which a first group is made up of one company and a second group is made up of a second company different from the first company.

[0388] (Clause 15) The matching system described in clause 15 is the matching system described in clause 13, wherein the first group is composed of a first division of a first company, and the second group is composed of a second division of the first company.

[0389] (Clause 16) The matching system described in clause 16 is a matching system described in any one of clauses 12 to 15, wherein when the computing device receives evaluations of a specified applicant from multiple recruiters belonging to a first group, the computing device calculates an average value of the evaluations of the specified applicant by the multiple recruiters, and transmits the average value as first evaluation information of the specified applicant to the sender that sent the viewing request in the first communication.

[0390] (Clause 17) The matching system described in clause 17 is the matching system described in clause 16, wherein the first group includes one or more recruiters belonging to the first divided group and one or more recruiters belonging to a second divided group different from the first divided group, and the computing device calculates a first average value which is an average value of evaluations for a specified applicant based on evaluations for a specified contractor received from a plurality of recruiters belonging to the first divided group, and the computing device calculates a second average value which is an average value of evaluations for a specified applicant based on evaluations for a specified contractor received from a plurality of recruiters belonging to the second divided group, and the computing device calculates a second average value which is an average value of evaluations for a specified applicant based on evaluations for a specified contractor received from a plurality of recruiters belonging to the first group. Based on the evaluation of a specified contractor received from the recruiter, the computing device calculates a third average value, which is the average value of the evaluations of a specified applicant, and when the computing device receives a viewing request in a third communication established by identification information that can identify the person as belonging to the first divided group, it transmits the first average value and the third average value to the sender that sent the viewing request in the third communication as first evaluation information of the specified applicant, and when the computing device receives a viewing request in a fourth communication established by identification information that can identify the person as belonging to the second divided group, it transmits the second average value and the third average value to the sender that sent the viewing request in the fourth communication as first evaluation information of the specified applicant.

[0391] (Clause 18) The matching system described in clause 18 is a matching system described in any one of clauses 12 to 17, in which a list of applicants is registered in a database, and when the first recruiter device receives an operation to search the list, it sends a search request to a computing device, and when the computing device receives the search request, it sends search results to the sender that sent the viewing request in the first communication, excluding from the list applicants whose evaluation level identified by the first evaluation information does not meet the standard.

[0392] (Clause 19) The matching system described in clause 19 is the matching system described in clause 1, wherein the first applicant belongs to a first group, the first applicant device accepts input of an evaluation of the recruiter and transmits the accepted evaluation to a computing device, the computing device registers first evaluation information based on the evaluation received from the first applicant device in a database for each recruiter, and when the computing device receives a viewing request in a first communication established by identification information that can identify the applicant as belonging to the first group, it transmits the first evaluation information to the sender that sent the viewing request in the first communication.

[0393] (Clause 20) The matching system described in clause 20 is the matching system described in clause 19, further comprising a second applicant device operated by one or more second applicants belonging to a second group different from the first group, wherein the second applicant device accepts input of an evaluation of the recruiter and transmits the received evaluation to a computing device, the computing device registers second evaluation information based on the evaluation received from the second applicant device in a database for each recruiter, and when the computing device receives a viewing request in a second communication established by identification information that can identify the person as belonging to the second group, it transmits the second evaluation information to the sender that sent the viewing request in the second communication.

[0394] (Clause 21) The matching system described in clause 21 is the matching system described in clause 20, in which a first group is formed by a first company and a second group is formed by a second company different from the first company.

[0395] (Clause 22) The matching system described in Clause 22 is the matching system described in Clause 20, wherein the first group is composed of a first division of a first company, and the second group is composed of a second division of the first company.

[0396] (Clause 23) The matching system described in clause 23 is a matching system described in any one of clauses 19 to 22, in which, when the computing device receives evaluations of a specified recruiter from multiple first applicants belonging to a first group, the computing device calculates an average value of the evaluations of the specified recruiter by the multiple first applicants, and transmits the average value as first evaluation information of the specified recruiter to the sender that sent the viewing request in the first communication.

[0397] (Item 24) The matching system described in item 24 is the matching system described in any one of items 19 to 21, wherein 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, and the computing device calculates a first average value which is an average value of the evaluations for the predetermined recruiter based on the evaluations for the predetermined recruiter received from the plurality of first applicants belonging to the first divided group, and the computing device calculates a second average value which is an average value of the evaluations for the predetermined recruiter based on the evaluations for the predetermined recruiter received from the plurality of first applicants belonging to the second divided group, and The computing device calculates a third average value, which is the average value of the evaluations for the specified recruiter, based on the evaluations for the specified recruiter received from multiple first applicants belonging to the same group, and when the computing device receives a viewing request in a third communication established by identification information that can identify the person as belonging to the first divided group, it transmits the first average value and the third average value to the sender that sent the viewing request in the third communication as first evaluation information for the specified recruiter, and when the computing device receives a viewing request in a fourth communication established by identification information that can identify the person as belonging to the second divided group, it transmits the second average value and the third average value to the sender that sent the viewing request in the fourth communication as first evaluation information for the specified recruiter.

[0398] (Clause 25) The matching system described in clause 25 is a matching system described in any one of clauses 19 to 24, in which a list of recruits is registered in a database, and when the first applicant device receives an operation to search the list, it sends a search request to a computing device, and when the computing device receives the search request, it sends a search result to the sender that sent the viewing request in the first communication, excluding from the list recruits whose rating specified by the first rating information does not meet the standard.

[0399] (Clause 26) The matching system described in clause 26 is the matching system described in clause 1, wherein the asset information includes detailed information regarding the content of the asset, and the computing device displays to the first applicant device the asset information that is permitted to be disclosed to the first applicant and the meanings of terms included in the detailed information.

[0400] (Item 27) The matching system described in Item 27 is the matching system described in Item 26, in which the terms included in the detailed information are in-house terms that are common in the group to which the recruiter belongs.

[0401] (Item 28) The matching system described in item 28 is the matching system described in item 27, wherein the computing device registers the in-house terms and the meanings of the in-house terms in a database.

[0402] (Item 29) The matching system described in item 29 is the matching system described in item 28, in which the computing device registers in-house terms in a database by group to which the recruiter belongs.

[0403] (Clause 30) The matching system described in clause 30 is the matching system described in clause 28 or 29, in which the computing device transmits information capable of identifying the meaning of the in-house term registered in the database to the first applicant device when the first applicant's operation on the in-house term is detected on the first applicant device.

[0404] (Clause 31) The matching system described in clause 31 is a matching system described in any one of clauses 27 to 30, in which the computing device searches for in-house terms contained in the detailed information, and registers the asset information in the database while associating the detected in-house terms with the meanings of the in-house terms.

[0405] (Clause 32) The recruiter device described in clause 32 is a recruiter device operated by an asset holder when he or she becomes the recruiter and recruits recipients or users of the assets, and the recruiter device communicates with a computing device that matches the recruiter with applicants who apply for the recruitment, and is equipped with an interface that accepts operations to input asset information indicating the target of the asset and disclosure information indicating the scope of disclosure of the asset information, and a processor that transmits the asset information and disclosure information accepted by the interface to the computing device, and the disclosure information includes information that instructs the computing device to allow 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.

[0406] (Clause 33) The method described in clause 33 is a method for matching a recruiter with an applicant who applies for a recruitment when an asset holder acts as a recruiter and is recruiting for a transfer or use of the asset, and includes the steps of communicating with a recruiter device operated by the recruiter and a first applicant device operated by the first applicant, receiving asset information indicating the target of the asset and disclosure information indicating the scope of disclosure of the asset information from the recruiter device operated by the recruiter, registering the asset information together with the disclosure information in a database, and determining, based on the disclosure information, asset information that is permitted to be disclosed to the first applicant from the asset information registered in the database, and providing the asset information that is permitted to be disclosed to the first applicant to the first applicant device.

[0407] The embodiments disclosed herein should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims, not by the description of the above embodiments, and is intended to include all modifications within the meaning and scope of the claims.

[0408] 1 Matching system, 50 Internet, 100 Sharing server, 101 Processor, 102 Memory, 103 Storage, 104 Communication interface, 120 Database (DB), 121 Company database (Company DB), 122 Member database (Member DB), 123 Community database (Community DB), 124, 124A Recruitment job database (Recruitment job DB), 126 Evaluation input database (Evaluation input DB), 126A Recruiter evaluation section, 126B Applicant evaluation section, 127 Evaluation summary database (Evaluation summary DB), 127A Recruiter evaluation summary section, 127B Applicant evaluation summary section, 129 Profile database (Profile DB), 137 In-house terminology database (In-house terminology DB), 140 Community registration section, 141 Company registration section, 142 Member registration section, 143 Member search section, 144 Job registration section, 145 Case extraction unit, 146 Application unit, 147 Approval unit, 148 Notification unit, 149 Performance reception unit, 150 Performance output unit, 151 Evaluation reception unit, 152 Evaluation output unit, 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 an asset holder who becomes a solicitor and solicits recipients or users of the asset with applicants who apply for the solicitation, comprising: a recruiter device operated by a recruiter; a first applicant device operated by a first applicant; a computing device in communication with the recruiter device and the first applicant device and capable of accessing a database; The first applicant belongs to a first group, and the recruiter belongs to a recruiter group different from the first group; The recruiter device transmits asset information indicating a target of the asset and disclosure information indicating a disclosure range of the asset information to the computing device; The computing device registers the asset information together with the disclosure information in the database; A matching system in which the computing device determines, based on the disclosure information, asset information that is permitted to be disclosed to the first group from the asset information registered in the database, and provides the asset information that is permitted to be disclosed to the first group to the first applicant device.

2. A second applicant device operated by a second applicant different from the first applicant, The second applicant belongs to a second group different from the first group; The matching system of claim 1, wherein the computing device determines, based on the disclosure information, asset information that is permitted to be disclosed to the second group from among the asset information registered in the database, and provides the asset information that is permitted to be disclosed to the second group to the second applicant device.

3. The matching system further includes a third applicant device operated by a third applicant different from the first applicant and the second applicant; The third applicant belongs to a third group different from the first group and the second group; A plurality of disclosure levels are set for the disclosure information, The matching system according to claim 2 , wherein the computing device determines whether or not to permit disclosure for each of the first applicant to the third applicant depending on the disclosure level.

4. The plurality of disclosure levels includes a first level and a second level, the first level corresponds to permitting disclosure of the asset information to the first applicant and prohibiting disclosure of the asset information to applicants not belonging to the first group; The matching system of claim 3, wherein the second level corresponds to allowing disclosure of the asset information to applicants who belong to either the first group or a community group that has formed a community relationship with the first group, and prohibiting disclosure of the asset information to applicants who do not belong to either the first group or the community group.

5. The plurality of disclosure levels includes a first level, a second level, and a third level; the first level corresponds to permitting disclosure of the asset information to the first applicant and prohibiting disclosure of the asset information to applicants not belonging to the first group; the second level permits disclosure of the asset information to applicants who belong to either the first group or a community group that has formed a community relationship with the first group; The matching system of claim 3, wherein the third level corresponds to allowing disclosure of the asset information to applicants who belong to a community other than the first group and the second level community group with which a community relationship has been formed with the first group, and prohibiting disclosure of the asset information to applicants who do not belong to either the first group or the community group.

6. The matching system according to claim 4 , wherein the plurality of disclosure levels includes a disclosure level corresponding to allowing disclosure of the asset information to an applicant regardless of a group to which the applicant belongs.

7. The database has registered therein attribute data capable of identifying the community group, 7. The matching system according to claim 5, wherein the computing device identifies applicants who are permitted to disclose the asset information based on the disclosure information and the attribute data.

8. The recruiter device receives an operation for inputting a target group to which the disclosure of the asset information is prohibited, and transmits information capable of identifying the received target group to the computing device; The matching system of any one of claims 3 to 7, wherein the computing device prohibits disclosure of the asset information to applicants belonging to the target group even if the disclosure level is a level that allows disclosure of the asset information 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 company, and the second applicant belongs to a second company different from the first company.

10. The recruiter device transmits to the computing device recruitment type information capable of identifying that the asset is a share type asset in which one or more applicants are selected as a transferee or user of the asset; 10. The matching system according to claim 1, wherein the computing device registers the recruitment form information in the database in association with the asset information.

11. The computing device registers the share establishment conditions in the database in association with the recruitment form information; The share establishment condition is a condition regarding the number of applicants for the share-type asset, The matching system according to claim 10 , wherein the computing device finalizes the applicant for the shared asset when the share establishment condition is established.

12. The recruiter devices include a first recruiter device operated by one or more recruiters belonging to a first group; the first recruiter device accepts an input of an evaluation for the first applicant and transmits the received 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 for each applicant; The matching system of claim 1, wherein when the computing device receives a viewing request in a first communication established by identification information that can identify the person as belonging to the first group, the computing device transmits the first evaluation information to the sender that sent the viewing request in the first communication.

13. 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 an input of an evaluation of the first applicant and transmits the received 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; The matching system of claim 12, wherein when the computing device receives a viewing request in a second communication established by identification information that can identify the person as belonging to the second group, the computing device transmits the second evaluation information to the sender that sent the viewing request in the second communication.

14. The matching system according to claim 13 , wherein the first group is constituted by a first company, and the second group is constituted by a second company different from the first company.

15. The matching system according to claim 13 , wherein the first group is made up of a first division of a first company, and the second group is made up of a second division of the first company.

16. When the computing device receives evaluations of a particular applicant from a plurality of recruiters belonging to the first group, the computing device calculates an average value of the evaluations of the particular applicant by the plurality of recruiters; A matching system as described in any one of claims 12 to 15, wherein the computing device transmits the average value as the first evaluation information of the specified applicant to the sender that sent the viewing request in the first communication.

17. The first group includes one or more recruits belonging to a first division group and one or more recruits belonging to a second division group different from the first division group; The computing device calculates a first average value, which is an average value of the evaluations for the specified applicant, based on the evaluations for the specified contractor received from the multiple recruiters belonging to the first division group; The computing device calculates a second average value, which is an average value of the evaluations for the specified applicant, based on the evaluations for the specified contractor received from the multiple recruiters belonging to the second divided group; The computing device calculates a third average value, which is an average value of the evaluations for the specific applicant, based on the evaluations for the specific contractor received from the multiple recruiters belonging to the first group; when the computing device receives a viewing request in a third communication established by identification information that can identify the person as belonging to the first divided group, the computing device transmits the first average value and the third average value to a source that transmitted the viewing request in the third communication as the first evaluation information of the specified applicant; The matching system of claim 16, wherein when the computing device receives a viewing request in a fourth communication established by identification information that can identify the person as belonging to the second divided group, the computing device transmits the second average value and the third average value to the sender that sent the viewing request in the fourth communication as the first evaluation information of the specified applicant.

18. The database contains a list of applicants, When the first recruiter device receives an operation to search the list, the first recruiter device transmits a search request to the computing device; A matching system as described in any one of claims 12 to 17, wherein when the computing device receives the search request, it transmits a search result to the sender of the viewing request in the first communication, the search result excluding from the list applicants whose evaluation level identified by the first evaluation information does not meet the standard.

19. The first applicant belongs to a first group; The first applicant device accepts an input of an evaluation of the recruiter and transmits the accepted evaluation to the computing device; The computing device registers first evaluation information based on the evaluation received from the first applicant device in the database for each applicant; The matching system of claim 1, wherein when the computing device receives a viewing request in a first communication established by identification information that can identify the person as belonging to the first group, the computing device transmits the first evaluation information to the sender that sent the viewing request in the first communication.

20. 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 transmits the received evaluation to the computing device; The computing device registers second evaluation information based on the evaluation received from the second applicant device in the database for each applicant; The matching system of claim 19, wherein when the computing device receives a viewing request in a second communication established by identification information that can identify the person as belonging to the second group, the computing device transmits the second evaluation information to the sender that sent the viewing request in the second communication.

21. The matching system according to claim 20 , wherein the first group is constituted by a first company, and the second group is constituted by a second company different from the first company.

22. 21. The matching system of claim 20, wherein the first group is made up of a first division of a first company, and the second group is made up of a second division of the first company.

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

24. The first group includes one or more first applicants belonging to a first division group and one or more first applicants belonging to a second division group different from the first division group, The computing device calculates a first average value, which is an average value of the evaluations for the specific recruiter, based on the evaluations for the specific recruiter received from the first applicants belonging to the first divided group; The computing device calculates a second average value, which is an average value of the evaluations for the specific recruiter, based on the evaluations for the specific recruiter received from the multiple first applicants belonging to the second divided group; The computing device calculates a third average value, which is an average value of the evaluations for the specific recruiter, based on the evaluations for the specific recruiter received from the first applicants belonging to the first group; When the computing device receives a browsing request in a third communication established by identification information that can identify the person as belonging to the first divided group, the computing device transmits the first average value and the third average value to a source that transmitted the browsing request in the third communication as the first evaluation information of the specified recruiter; A matching system as described in any one of claims 19 to 21, wherein when the computing device receives a viewing request in a fourth communication established by identification information that can identify the person as belonging to the second divided group, the computing device transmits the second average value and the third average value as the first evaluation information of the specified recruiter to a sender that sent the viewing request in the fourth communication.

25. The database contains a list of recruiters, When the first applicant device receives an operation to search the list, the first applicant device transmits a search request to the computing device; A matching system as described in any one of claims 19 to 24, wherein when the computing device receives the search request, it transmits a search result to the sender of the viewing request in the first communication, the search result excluding from the list recruiters whose rating specified by the first rating information does not meet the standard.

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

27. The matching system of claim 26, wherein the terms included in the detailed information are in-house terms that are prevalent in a group to which the recruiter belongs.

28. 28. The matching system of claim 27, wherein the computing device registers the in-house terms and meanings of the in-house terms in the database.

29. The matching system of claim 28 , wherein the computing device registers the in-house terms in the database according to a group to which the recruiter belongs.

30. The matching system of claim 28 or claim 29, wherein the computing device transmits information capable of identifying the meaning of the in-house term registered in the database to the first applicant device when the first applicant's operation on the in-house term is detected on the first applicant device.

31. A matching system as described in any one of claims 27 to 30, wherein the computing device searches for the in-house terms contained in the detailed information, and registers the asset information in the database while matching the detected in-house terms with the meanings of the in-house terms.

32. A solicitor device operated by a solicitor when a holder of an asset becomes a solicitor and solicits recipients or users of the asset, comprising: the recruiter device is in communication with a computing device that matches recruits with applicants who apply for the recruitment; an interface for receiving an operation for inputting asset information indicating a target of the asset and disclosure information indicating a disclosure range of the asset information; a processor for transmitting the asset information and the disclosure information received by the interface to the computing device; The disclosure information includes information instructing the computing device to allow disclosure of the asset information to a group to which a first applicant belongs and to prohibit disclosure of the asset information to a group to which a second applicant belongs that is different from the group to which the first applicant belongs, on a recruiter device.

33. A method for matching an asset holder who becomes a solicitor and solicits recipients or users of the asset with applicants who apply for the solicitation, the method comprising: communicating with a recruiter device operated by the recruiter and a first applicant device operated by the first applicant; receiving asset information indicating a target of the asset and disclosure information indicating a disclosure range of the asset information from a recruiter device operated by a recruiter; registering the asset information together with the disclosure information in a database; determining, based on the disclosure information, from the asset information registered in the database, which asset information is permitted to be disclosed to the group to which the first applicant belongs, and providing, to the first applicant device, the asset information which is permitted to be disclosed to the group to which the first applicant belongs.