JP2023076877A - Data management system, data management apparatus, data management method, and program - Google Patents

Abstract

To provide a data management system, a data management apparatus, a data management method, and a program that make it possible to guarantee a reliability of career information on an applicant who may be, for example, a job seeker.SOLUTION: In processing of requesting an import of career information, a data management apparatus 3 receives, from an affiliation management system 5, import response information indicating an import response as a response to an import request transmitted from an applicant terminal 4 at S48, and registers carrier data, provider information, provider (transmission) date and time information, and expiration date information included in the import response information in an applicant information management DB 3004 at S49. The data management apparatus 3 then transmits, to the applicant terminal 4, response information including register URL information for registration to be performed at the applicant terminal 4 as a response to the import request information at S50.SELECTED DRAWING: Figure 16

Description

The present invention relates to a data management system, a data management device, a data management method and a program.

BACKGROUND ART Conventionally, there exists a technique for sharing personnel information of a specific person among a plurality of companies, traders, and the like.

In such technology, users 3a, 3b, 3c... (may be limited to users who are recruiters) operate terminals 2a, 2b, 2c... , department, position, etc. are input and registered, and the terminals 2a, 2b, 2c, . ).

However, in the conventional technology, there is a problem that it is not clear whether or not the reliability of career information of applicants, for example job seekers, is guaranteed.

In order to solve the above-described problems, the invention according to claim 1 provides an affiliation management system that manages information on the affiliation of an applicant who applies for the use of his or her career information, and a system that identifies the background information and the applicant. and a data management device that manages the applicant identification information in association with the data management device, wherein the data management device requests acquisition of the history information transmitted by the applicant terminal used by the applicant. receiving means for receiving specific capturing response information as a response to the capturing request information and the history information, which are acquired by the affiliated management system based on the capturing request information for registration means for adding the specific acquisition response information to the background information obtained and registering it as applicant-specific additional information associated with the applicant identification information; and transmitting means for transmitting to a terminal.

As described above, according to the present invention, it is possible to secure the reliability of career information of applicants, for example, job seekers.

It is a figure which shows an example of the whole structure of a communication system. It is a figure which shows an example of the hardware constitutions of a data management apparatus, an organization management system, and a contractor management system. It is a figure which shows an example of the hardware constitutions of an applicant terminal. It is a figure which shows an example of the functional structure of a communication system. 4 is a conceptual diagram showing an example of an account information management table; FIG. FIG. 4 is a conceptual diagram showing an example of an affiliation information management table; 4 is a conceptual diagram showing an example of a vendor information management table; FIG. It is a conceptual diagram which shows an example of an applicant information management table. 4 is a conceptual diagram showing an example of an applicant history management table; FIG. FIG. 11 is a sequence diagram showing an example of account application processing by the affiliated organization management system; It is an example of a profile editing screen in the organization management system. FIG. 10 is a sequence diagram showing an example of account application processing by the vendor management system; It is an example of a profile edit screen in a trader management system. FIG. 11 is a sequence diagram showing an example of account application processing by an applicant terminal; It is an example of the profile edit screen in an applicant terminal. FIG. 11 is a sequence diagram showing an example of history information acquisition request processing; It is an example of an operation screen for selecting a provider of career information and performing an import request on the applicant's terminal. FIG. 11 is a sequence diagram showing an example of confirmation of completion of acquisition of history information and additional correction registration processing by an applicant terminal; FIG. 11 is a sequence diagram showing an example of history information usage start processing; It is an example of an operation screen for selecting a vendor and requesting acquisition when providing career information on the applicant terminal. It is an example of an operation screen for performing an operation to stop providing career information on the applicant's terminal.

DETAILED DESCRIPTION OF THE INVENTION Embodiments for carrying out the invention will be described below with reference to the drawings. In the description of the drawings, the same elements are denoted by the same reference numerals, and if there are overlapping parts, the description thereof will be omitted.

[Embodiment]
An embodiment will be described with reference to FIGS. 1 to 21. FIG.

[Overall Configuration of Communication System]
<<System configuration example>>
<Communication system>
FIG. 1 is a diagram showing an example of the overall configuration of a communication system. The communication system 1 shown in FIG. 1 includes an applicant terminal 4 used by the applicant, an affiliation management system 5 that manages information on the applicant's affiliation, applicant identification information that identifies career information and the applicant. A system that manages applicant's background information and provides background information to the applicant by the data management device 3 that manages in association with and the vendor management system 8 that registers and provides the applicant's background information. be.

As shown in FIG. 1 , the communication system 1 has a data management device 3 , an applicant terminal 4 , a department management system 5 and a vendor management system 8 . The data management device 3 , the applicant terminal 4 , the organization management system 5 and the vendor management system 8 are connected to each other via a communication network 100 . Here, the communication network 100 is a communication network in which an unspecified number of communications are performed, and is constructed by the Internet, an intranet, a LAN (Local Area Network), or the like. The communication network 100 includes not only wired communication but also wireless communication such as 3G (3rd Generation), 4G (4th Generation), 5G (5th Generation), WiMAX (Worldwide Interoperability for Microwave Access), LTE (Long Term Evolution), and the like. A communication network by communication may be included.

The communication system 1 further includes an affiliation management system 5 constructed by an affiliation management device 6 and an affiliation terminal 7 and a trader management system 8 constructed by a trader management device 9 and a trader terminal 10 . It should be noted that the affiliation management device 6 and affiliation terminal 7, and the vendor management device 9 and vendor terminal 10 may be connected to each other via a dedicated local network or the like. ) to each other. With such a configuration, for example, when information related to various requests (e-mail, URL information, etc.) is sent from the applicant using the applicant terminal 4 to the affiliated terminal 7, the following processing is performed. is done. Specifically, the person in charge of the belonging destination who operates the belonging destination terminal 7 operates the browser via the UI provided to the belonging destination terminal 7 . As a result, the affiliation management device 6 connected to the affiliation destination terminal 7 transmits the information (data) operated by the browser to the data management device 3 through the API. Such a configuration and processing form are the same between the vendor management device 9 and the vendor terminal 10 that construct the vendor management system 8 .

The communication system 1 further has a data management system 2 constructed by the data management device 3 and the affiliation management system 5 described above. Instead of the data management system 2, a new data management system 2' including the data management device 3, the applicant terminal 4, and the affiliation management system 5 may be constructed.

<Data management device>
The data management device 3 is realized by one or more information processing devices (computer system) on which a general server OS or the like is installed. Also, the data management device 3 is one that constructs the data management system 2 . Further, the data management device 3 manages the history information of the applicant and the applicant identification information for identifying the applicant in association with each other. The data management device 3 further stores communication applications for communicating with other devices and communication terminals in the storage means.

The data management device 3 may be constructed by a single computer such as a commonly used PC (Personal Computer) or a portable notebook PC, or may be constructed by dividing each part (function or means) such as a storage. It may be constructed by a plurality of computers arbitrarily assigned by All or part of the functions of the data management device 3 may be a server computer existing in a cloud environment, or may be a server computer existing in an on-premises environment. Further, the data management device 3 may be a communication device or a communication terminal capable of operating various software such as browser software.

The data management device 3 may notify (transmit) data (information) by push notification (transmission) to the applicant terminal 4 described later. In that case, the data management device 3 can be implemented by, for example, using FCM (Firebase Cloud Messaging), which is an example of a push notification server, to perform push notification.

<Applicant terminal>
Applicant terminal 4 is implemented by one or more information processing devices (computer system) on which a general server OS or the like is installed. As the applicant terminal 4, a communication device or a communication terminal capable of operating software such as browser software and various applications is used. Applicant terminal 4 further stores a communication application (carrier data base application) for communicating with other devices and communication terminals in the storage means. Applicant terminal 4 is a communication terminal having a communication function such as a commonly used PC (Personal Computer), portable notebook PC, mobile phone, smart phone, tablet terminal, or wearable terminal (sunglass type, wristwatch type, etc.). may be Applicant terminal 4 may be a communication terminal owned by the applicant himself or a communication terminal lent by the applicant from a third party.

<Affiliation management system>
The affiliation management system 5 is implemented by one or more information processing devices (computer systems) on which a general server OS or the like is installed. Also, the affiliation management system 5 is one part of the data management system 2 . In addition, the affiliation management system 5 manages information on the affiliation of the applicant who applies to use his/her career information. The affiliation management system 5 further stores software such as communication applications and browser software for communicating with other devices and communication terminals in the storage means. The affiliation management system 5 may be constructed by a single computer such as a commonly used PC (Personal Computer) or a portable notebook PC, or may be composed of the affiliation terminal 7 and each part (function or means) may be divided and constructed by a plurality of arbitrarily assigned computers.

<Vendor management system>
The trader management system 8 is realized by an information processing device (computer system) for communication, in which a general OS or the like is installed. Further, the vendor management system 8 receives inputs such as vendor profile information input by the vendor using the vendor terminal 10 in the communication system 1 , and transmits various types of input information to the data management device 3 . The vendor management system 8 further stores software such as communication applications and browser software for communicating with other devices and communication terminals in the storage means. The trader management system 8 may be constructed by a single computer such as a commonly used PC (Personal Computer) or a portable notebook, or may be constructed by the trader terminal 10 and each part (function or means) such as a storage and a server. and may be constructed by a plurality of computers arbitrarily assigned by dividing.

●Terms●
In this embodiment, the applicant includes, for example, a job seeker who seeks a place of employment (employment place) in order to find a job or a company.

In addition, in the present embodiment, the career information of the applicant refers to the career data of the applicant's current affiliation. Career data includes personal information such as the applicant's address, name, date of birth, etc. registered at the institution to which the applicant belongs, work performance, income qualifications, rewards and punishment data, etc. accumulated through the work performed by the applicant. Applicants are sometimes simply referred to as users.

Furthermore, in the present embodiment, the affiliation means a company, a school, an organization, etc., which is composed of a certain number or more of personnel. In the present embodiment, each process performed in a company, which is an example of an affiliated company, will be described.

[Hardware configuration]
Next, the hardware configuration of the device or terminal that configures the communication system according to the embodiment will be described with reference to FIGS. 2 and 3. FIG. Components may be added or deleted from the hardware configuration of the device or terminal shown in FIGS. 2 and 3 as necessary.

<Hardware Configuration of Data Management Device, Organization Management System and Vendor Management System>
FIG. 2 is a diagram showing an example of the hardware configuration of a data management device, an affiliate management system, and a vendor management system. As shown in FIG. 2, the data management device 3 is constructed by, for example, a computer, and includes a CPU (Central Processing Unit) 301, a ROM (Read Only Memory) 302, a RAM (Random Access Memory) 303, an EEPROM ( Electrically Erasable Programmable Read-Only Memory) 304, HD (Hard Disk) 305, HDD (Hard Disk Drive) controller 306, display 307, near field communication I/F (Interface) 308, CMOS (Complementary MOS) sensor 309, image sensor It has I/F 310 , network I/F 311 , keyboard 312 , pointing device 313 , media I/F 315 , external device connection I/F 316 , sound input/output I/F 317 , microphone 318 , speaker 319 and bus line 320 .

Among these, the CPU 301 controls the operation of the data management device 3 as a whole. The ROM 302 stores programs used to drive the CPU 301 . A RAM 303 is used as a work area for the CPU 301 . The EEPROM 304 reads or writes various data such as applications under the control of the CPU 301 . The HD 305 stores various data such as programs. The HDD controller 306 controls reading or writing of various data to the HD 305 under the control of the CPU 301 . Here, the data management device 3 may have a hardware configuration in which an SSD (Solid State Drive) is installed instead of the HD 305 and HDD controller 306 . A display 307 displays various information such as cursors, menus, windows, characters, and images. The short-range communication I/F 308 is a communication device or communication terminal equipped with a wireless communication interface such as NFC (Near Field Communication), Bluetooth (registered trademark; hereinafter omitted), Wi-Fi (registered trademark; hereinafter omitted), etc. and data A communication circuit for communication. The CMOS sensor 309 is a type of built-in image pickup means that picks up an image of a subject under the control of the CPU 301 and obtains image data or moving image data. Note that the image pickup means may be an image pickup means composed of a CCD (Charge Coupled Device) sensor or the like instead of the CMOS sensor. An imaging device I/F 310 is a circuit that controls driving of the CMOS sensor 309 .

Network I/F 311 is an interface for data communication using communication network 100 . The keyboard 312 is a type of input means having a plurality of keys for inputting characters, numerical values, various instructions, and the like. A pointing device 313 is a kind of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, and the like. A media I/F 315 controls reading or writing (storage) of data to a recording medium 314 such as a flash memory. The external device connection I/F 316 is an interface for connecting various external devices. The external device in this case is, for example, a USB (Universal Serial Bus) memory or the like. A sound input/output I/F 317 is a circuit for processing input/output of sound signals between the microphone 318 and the speaker 319 under the control of the CPU 301 . A microphone 318 is a built-in circuit that converts sound into an electric signal, acquires voice or sound wave emitted from an external speaker or the like, and acquires information using the electric signal. The speaker 319 is a built-in circuit that converts electrical signals into physical vibrations to produce sounds such as music and voice. A bus line 320 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 301 .

The affiliation management system 5 is constructed by a computer, for example, and includes a CPU 501, a ROM 502, a RAM 503, an EEPROM 504, an HD 505, a HDD (Hard Disk Drive) controller 506, a display 507, a short-range communication I/F 508, a CMOS sensor 509, and an imaging device. It has an I/F 510 , a network I/F 511 , a keyboard 512 , a pointing device 513 , a media I/F 515 , an external device connection I/F 516 , a sound input/output I/F 517 , a microphone 518 , a speaker 519 and a bus line 520 . These hardware resources of the data management device 3 are CPU 301, ROM 302, RAM 303, EEPROM 304, HD 305, HDD controller 306, display 307, short-range communication I/F 308, CMOS sensor 309, imaging element I/F 310, network I/F 311. , keyboard 312, pointing device 313, media I/F 315, external device connection I/F 316, sound input/output I/F 317, microphone 318, speaker 319, and bus line 320. do.

The trader management system 8 is constructed by a computer, for example, and includes a CPU 801, a ROM 802, a RAM 803, an EEPROM 804, an HD 805, a HDD (Hard Disk Drive) controller 806, a display 807, a short-range communication I/F 808, a CMOS sensor 809, an imaging element I /F 810 , network I/F 811 , keyboard 812 , pointing device 813 , media I/F 815 , external device connection I/F 816 , sound input/output I/F 817 , microphone 818 , speaker 819 and bus line 820 . These hardware resources of the data management device 3 are CPU 301, ROM 302, RAM 303, EEPROM 304, HD 305, HDD controller 306, display 307, short-range communication I/F 308, CMOS sensor 309, imaging element I/F 310, network I/F 311. , keyboard 312, pointing device 313, media I/F 315, external device connection I/F 316, sound input/output I/F 317, microphone 318, speaker 319, and bus line 320. do.

<Hardware configuration of the applicant's terminal>
FIG. 3 is a diagram showing an example of the hardware configuration of the applicant's terminal. As shown in FIG. 3, the applicant terminal 4 is constructed by, for example, a computer, and includes a CPU 401, a ROM 402, a RAM 403, an SSD (Solid State Drive) 404, a display 407, a near field communication I/F 408, a CMOS sensor 409 , image sensor I/F 410 , network I/F 411 , pointing device 413 , media I/F 415 , external device connection I/F 416 , sound input/output I/F 417 , microphone 418 , speaker 419 and bus line 420 . These hardware resources are the CPU 301, ROM 302, RAM 303, display 307, short-range communication I/F 308, CMOS sensor 309, imaging element I/F 310, network I/F 311, pointing device, and so on of the data management device 3 shown in FIG. 313 , media I/F 315 , external device connection I/F 316 , sound input/output I/F 317 , microphone 318 , speaker 319 and bus line 320 . Note that the SSD 404 is, for example, a memory built into a USB (Universal Serial Bus) memory, and stores and reads out various data in the applicant terminal 4 .

Furthermore, the above program may be recorded in a computer-readable recording medium as an installable or executable file, or may be downloaded and distributed via a network. Examples of recording media include CD-R (Compact Disc Recordable), DVD (Digital Versatile Disk), Blu-ray Disc (Blu-ray is a registered trademark, hereinafter omitted), SD (Secure Digital) memory card, USB memory, and the like. mentioned. Also, the recording medium can be provided domestically or internationally as a program product. For example, the data management device 3 implements the data management method according to the present invention by executing the program according to the present invention.

[Functional configuration of communication system]
Next, the functional configuration of this embodiment will be described with reference to FIGS. 4 to 9. FIG. FIG. 4 is a diagram illustrating an example of a functional configuration of a communication system;

<Functional configuration of data management device>
As shown in FIG. 4, the data management device 3 has a transmitting/receiving section 31, a specifying section 35, a generating section 37, a registering section 38, and a memory reading section 39. FIG. Each of these functional units is configured such that any one of the hardware resources shown in FIG. It is a function or means realized by operating according to instructions. The data management device 3 also has a storage unit 3000 constructed from at least one of the ROM 302, EEPROM 304 and HD 305 shown in FIG. Further, the storage unit 3000 stores a communication program (communication application) for communicating with each device and each terminal via the communication network 100, a browser application, and the like.

<<Each functional configuration of the data management device>>
Next, each functional configuration of the data management device 3 will be described in detail. The transmission/reception unit 31 of the data management device 3 shown in FIG. Send and receive various data (or information) between In addition, the transmitting/receiving unit 31 receives information from the applicant terminal 4 used by the applicant, which is acquired by the affiliation management system 5 based on acquisition request information for requesting acquisition of career information (hereinafter referred to as carrier data). , receiving specific capture response information and carrier data as a response to the capture request information.

Further, the transmitting/receiving section 31 transmits the applicant identification additional information registered in the data management device 3 to the applicant terminal 4 .

Further, the transmitting/receiving unit 31 transmits expiration date information included in the specific capture response information transmitted by the affiliation management system 5 to the vendor management system 8 that provides carrier data in response to a request from the applicant. .

In addition, the transmitting/receiving unit 31 transmits the acquisition request information related to the acquisition request request for requesting the acquisition of carrier data and the supply start request for starting the provision of carrier data. It receives from the applicant terminal 4 start information and provision stop request information relating to a provision stop request for stopping the provision of carrier data.

In addition, when there are multiple affiliation management systems 5, the transmission/reception unit 31 sends import request information including specific affiliation identification information indicating a specific affiliation selected by the applicant's operation on the applicant terminal 4. receive.

The transmitting/receiving unit 31 further indicates a specific trader selected by the applicant's operation on the applicant's terminal 4 when there are a plurality of trader management systems 8 that register carrier data and provide it in response to the request of the applicant. Receive the provision start request information including the name of the specific trader. In this embodiment, the transmitting/receiving section 31 functions as an example of at least one of transmitting means and receiving means.

The specifying unit 35 is mainly implemented by processing of the CPU 301 . The identification unit 35 identifies the corresponding service to be provided by searching a dealer information management DB 3003 (to be described later) based on the name of the dealer included in the request to start providing carrier data transmitted by the applicant terminal 4, for example. In this embodiment, the specifying unit 35 functions as an example of specifying means.

The generation unit 37 is mainly realized by processing of the CPU 301 . The generation unit 37 generates the e-mail address information of the person in charge of the company, the e-mail address information of the person in charge of the company, the e-mail address information of the person in charge of the company, and the applicant's Generate each account based on email address information. In the present embodiment, the generation unit 37 functions as an example of generation means.

The registration unit 38 is mainly implemented by processing of the CPU 301 . The registration unit 38 stores the account generated by the generation unit 37 and various information associated with the contents of the account in one of various DBs managed by the data management device 3 and a predetermined area of the storage unit 3000. ,register. In this embodiment, the registration unit 38 functions as an example of registration means.

The memory reading unit 39 is mainly realized by processing of at least one of the ROM 302, the EEPROM 304 and the HD 305 by the CPU 301, stores various data (or information) in the storage unit 3000, and retrieves various data (or information) from the storage unit 3000. information). In the present embodiment, the memory reading unit 39 functions as an example of memory reading means.

●Account information management table●
FIG. 5 is a conceptual diagram showing an example of an account information management table. In the storage unit 3000, an account information management DB 3001 configured by an account information management table as shown in FIG. 5 is constructed. In the account information management table, each item of account identification information is stored and managed in association with each item of name, email address, password, date of birth, role, affiliation identification information, applicant identification information, and vendor identification information. there is

Among these, the account identification information is identification information as an account associated with the applicant using the applicant terminal 4, the person in charge of personnel affairs etc. in the organization management system 5, and the contractor person in charge in the contractor management system 8. is. The account identification information is given and managed by, for example, "A0101", "A0212", and the like. The name, e-mail address, password, and date of birth are the names, e-mail addresses, passwords, and dates of birth of the person in charge at the affiliated company, the applicant, and the person in charge at the company, respectively. The role indicates the role of a person who uses the applicant terminal 4, affiliation management system 5, and contractor management system 8. For example, "applicant", "company representative", "contractor representative", etc. given and managed. The affiliation identification information is identification information managed in association with the affiliation management system 5, and is given and managed by, for example, "C0001" and "C0002". The applicant identification information is identification information managed in association with the applicant terminal 4, and is given and managed by, for example, "J0001" and "J0002". The vendor identification information is identification information managed in association with the vendor management system 8, and is given and managed as "S0001", "S0002", etc., for example. Each piece of information shown in FIG. 5 is not limited to this.

In the present embodiment, the account information management DB 3001 is an example of an account information management unit that manages information relating to a person in charge at a department, an applicant, a person in charge of a company, a role, etc. in association with each account identification information.

●Affiliation information management table●
FIG. 6 is a conceptual diagram showing an example of the affiliation information management table. In the storage unit 3000, an affiliation information management DB 3002 configured by an affiliation information management table as shown in FIG. 6 is constructed. In the affiliation information management table, for example, the affiliation identification information is tabbed, and name, date of birth, affiliation address, affiliation contact telephone number, affiliation contact email address, affiliation (original address), industry, etc. are displayed. Associated and stored and managed.

Of these, the name, date of birth, address of the organization, contact phone number of the organization, and email address of the organization contact are managed as information related to the person in charge of the organization. The place of affiliation (original domicile) is given, for example, the name of the company to which the person belongs, and the type of business is given information indicating the type of business of the company. Each piece of information shown in FIG. 6 is not limited to this.

In this embodiment, the affiliation information management DB 3002 is an example of an affiliation information management unit that manages various types of information related to affiliation in association with each affiliation identification information.

●Vendor information management table●
FIG. 7 is a conceptual diagram showing an example of a vendor information management table. A vendor information management DB 3003 configured by a vendor information management table as shown in FIG. 7 is constructed in the storage unit 3000 . In the trader information management table, for example, name, date of birth, trader address, trader contact phone number, trader contact email address, trader (original address), business type, etc. are stored and managed in association with trader identification information as tabs. It is

Of these, the name, date of birth, trader address, trader contact phone number, and trader contact email address are managed as information related to the person in charge of the trader. For the trader (original domicile), for example, the trader name of the trader providing the carrier data is given, and for the business type, information indicating the business type of the trader is given. Each piece of information shown in FIG. 7 is not limited to this.

In this embodiment, the vendor information management DB 3003 is an example of a vendor information management unit that manages various types of information related to a vendor in association with each vendor identification information.

●Applicant information management table●
FIG. 8 is a conceptual diagram showing an example of an applicant information management table. In the storage unit 3000, an applicant information management DB 3004 configured by an applicant information management table as shown in FIG. 8 is constructed. In the applicant information management table, for example, the applicant identification information is tabbed, name, date of birth, area of residence, contact telephone number, contact e-mail address, period of enrollment, company name (original address), industry, final annual income, Job types, employee categories, job titles, qualifications, desired industries/job types, desired welfare programs, etc. are associated and stored and managed.

Among these, name, date of birth, area of residence, contact phone number, contact email address, period of employment, company name (original address), industry, final annual income, occupation, employee category, title, qualifications held, desired industry・Job type indicates personal information related to the applicant who belongs to (was) a certain company and career data in that company. Further, the desired welfare program is, for example, newly stored and managed by the applicant using the applicant's terminal 4 and inputting it via a browser or the like. Furthermore, the identification information of the affiliation of the capturing source, the provision (transmitting) date and time information, the expiration date information indicating the expiration date of the history information, etc. are managed as specific capture response information. This specific take-in response information is stored and managed as information included in the specific take-in response information sent by the affiliation management system 5 . Each piece of information shown in FIG. 8 is not limited to this.

In this embodiment, the applicant information management DB 3004 is an example of an applicant information management unit that manages various types of information related to applicants in association with each applicant identification information.

<Functional configuration of applicant terminal>
As shown in FIG. 4 , the applicant terminal 4 has a transmission/reception section 41 , an operation reception section 42 , a display control section 44 , a processing section 45 , a registration section 48 and a memory reading section 49 . Each of these functional units, any of the hardware resources shown in FIG. It is a function or means realized by an action. In addition, the applicant terminal 4 has a storage unit 4000 constructed by at least one of the ROM 402 and SSD 404 shown in FIG. Further, the storage unit 4000 stores a communication program (communication application) for communicating with each device and each terminal via the communication network 100, a browser application, and the like.

<<Each functional configuration of the applicant's terminal>>
Next, each functional configuration of the applicant terminal 4 will be described in detail. Transmitting/receiving unit 41 of applicant terminal 4 shown in FIG. Send and receive various data (or information) between In this embodiment, the transmitting/receiving unit 41 functions as an example of at least one of transmitting means and receiving means.

The operation reception unit 42 is realized mainly by the CPU 401 processing signals generated by various operations received by the pointing device 413 . The operation reception unit 42 also receives various signals generated by various operations input by the applicant, including an account application operation, a carrier data import request operation, and a carrier data provision start operation. Note that the operation reception unit 42 may use input means such as a keyboard or a touch panel instead of the pointing device 413 . In this embodiment, the operation accepting unit 42 functions as an example of accepting means.

The display control unit 44 is mainly realized by the processing of the CPU 401 on the display 407 and controls the display of various screens and information (data) on the applicant terminal 4 . Further, the display control unit 44 causes the display 407 to display a display screen created by HTML or the like using a browser, for example. In this embodiment, the display control unit 44 functions as an example of display control means.

The processing unit 45 is mainly implemented by processing of the CPU 401 . For example, the processing unit 45 selects the carrier data provider (company to which the applicant belongs) from the carrier data provider list displayed on the carrier data infrastructure application activated by the applicant terminal 4. Perform processing for extracting affiliation identification information. In this embodiment, the processing unit 45 functions as an example of processing means.

The registration unit 48 is mainly implemented by processing of the CPU 401 . The registration unit 48 stores and registers an account based on various data included in the account application response from the data management device 3 in response to the account application request transmitted by the applicant terminal 4 . For example, the registration unit 48 stores the account in either the applicant information management DB 3004 managed by the data management device 3 or a predetermined area of the storage unit 3000 via the browser opened on the applicant terminal 4, to register. In this embodiment, the registration unit 48 functions as an example of registration means.

The memory reading unit 49 is mainly implemented by the processing of the CPU 401 on at least one of the ROM 402 and the SSD 404, stores various data (or information) in the storage unit 4000, and retrieves various data (or information) from the storage unit 4000. to read out. In the present embodiment, the memory reading unit 49 functions as an example of memory reading means.

<Functional configuration of department management system>
As shown in FIG. 4 , the affiliation management system 5 has a transmission/reception section 51 , an operation reception section 52 , an acquisition section 53 , a display control section 54 , a processing section 55 , a registration section 58 and a memory/read section 59 . Each of these functional units is implemented by any one of the hardware resources shown in FIG. It is a function or means realized by operating according to the instructions of In addition, the affiliation management system 5 has a storage unit 5000 constructed by at least one of the ROM 502, the EEPROM 504 and the HD 505 shown in FIG. Further, the storage unit 5000 stores a communication program (communication application) for communicating with each device and each terminal via the communication network 100, a browser application, and the like.

<<Each function configuration of affiliation management system>>
Next, each functional configuration of the affiliation management system 5 will be described in detail. The transmission/reception unit 51 of the affiliation management system 5 shown in FIG. Sends and receives various data (or information) to and from the device. In this embodiment, the transmitting/receiving unit 51 functions as an example of at least one of transmitting means and receiving means.

The operation reception unit 52 is realized mainly by the CPU 501 processing signals generated by various operations received by the keyboard 512 and the pointing device 513 . Note that input means such as a touch panel may be used for the operation reception unit 52 instead of the keyboard 512 and the pointing device 513 . In this embodiment, the operation accepting unit 52 functions as an example of accepting means.

Acquisition unit 53 is mainly realized by processing of CPU 501 . The acquisition unit 53 manages career information (career data) related to the applicant confirmed based on the acquisition request information in association with applicant confirmation information for confirming the applicant. Obtained from DB 5001 (an example of applicant history management means). In the present embodiment, the acquisition unit 53 functions as an example of acquisition means.

The display control unit 54 is mainly realized by the processing of the CPU 501 on the display 507, and controls the display of various screens and information (data) in the affiliation management system 5 (affiliation terminal 7). In addition, the display control unit 54 causes the display 507 to display a display screen created by HTML or the like using a browser, for example. In this embodiment, the display control unit 54 functions as an example of display control means.

The registration unit 58 is mainly implemented by processing of the CPU 501 . The registration unit 58 adds specific take-in response information to the history information (carrier data) received by the transmission/reception unit 51, and registers it as applicant-specific additional information associated with the applicant identification information. In this embodiment, the registration unit 58 functions as an example of registration means.

The memory reading unit 59 is mainly realized by processing of at least one of the ROM 502, the EEPROM 504 and the HD 505 by the CPU 501, stores various data (or information) in the storage unit 5000, and reads various data (or information) from the storage unit 5000. information). In the present embodiment, the memory reading unit 59 functions as an example of memory reading means.

●Applicant Career Management Table●
FIG. 9 is a conceptual diagram showing an example of an applicant history management table. In the storage unit 5000, an applicant history management DB 5001 configured by an applicant history management table as shown in FIG. 9 is constructed. In the applicant history management table, for example, the applicant's email address is used as a tab, and the name, date of birth, area of residence, contact telephone number, assigned department and period, qualifications, rewards and punishments, etc. are associated and stored and managed. there is

Among these, name, date of birth, area of residence, contact telephone number, assigned department and period, qualifications held, rewards and punishments, etc. Various background information (career data) in the company is shown. Each piece of information shown in FIG. 9 is not limited to this.

In this embodiment, the applicant history management DB 5001 is an example of an applicant history management unit that manages various types of history information related to an applicant in association with each applicant identification information.

<Functional configuration of vendor management system>
As shown in FIG. 4 , the vendor management system 8 has a transmission/reception section 81 , an operation reception section 82 , an acquisition section 83 , a display control section 84 , a processing section 85 , a registration section 88 and a memory/read section 89 . Each of these functional units is configured such that any one of the hardware resources shown in FIG. It is a function or means realized by operating according to instructions. In addition, the vendor management system 8 has a storage unit 8000 constructed by at least one of the ROM 802, EEPROM 804 and HD 805 shown in FIG. Furthermore, the storage unit 8000 stores a communication program (communication application) for communicating with each device and each terminal via the communication network 100, a browser application, and the like.

<<Each function configuration of vendor management system>>
Next, each functional configuration of the vendor management system 8 will be described in detail. The transmission/reception unit 81 of the vendor management system 8 shown in FIG. Send and receive various data (or information) between In this embodiment, the transmitting/receiving section 81 functions as an example of at least one of transmitting means and receiving means.

The operation reception unit 82 is mainly implemented by the CPU 801 processing signals generated by various operations received by the keyboard 812 and pointing device 813 . The operation reception unit 82 may use input means such as a touch panel instead of the keyboard 812 and the pointing device 813 . In this embodiment, the operation accepting unit 82 functions as an example of accepting means.

The acquisition unit 83 is mainly realized by the processing of the CPU 801 and acquires the carrier data related to each applicant managed by the agent management system 8 by fetching from a predetermined storage area. In the present embodiment, the obtaining unit 83 functions as an example of obtaining means.

The display control unit 84 is mainly realized by the processing of the CPU 801 on the display 807, and controls the display of various screens and information (data) in the trader management system 8 (the trader terminal 10). Further, the display control unit 84 causes the display 807 to display a display screen created by HTML or the like using a browser, for example. In the present embodiment, the display control section 84 functions as an example of display control means.

The registration unit 88 is mainly realized by the processing of the CPU 801, and registers career information (carrier data) of each applicant in a predetermined storage area of the agent management system 8, for example. In this embodiment, the registration unit 88 functions as an example of registration means.

The memory reading unit 89 is mainly implemented by the processing of at least one of the ROM 802, EEPROM 804 and HD 805 by the CPU 801, stores various data (or information) in the storage unit 8000, and reads various data (or information) from the storage unit 8000. information). In the present embodiment, the memory reading unit 89 functions as an example of memory reading means.

[Processing or operation of the embodiment]
Next, each process or operation in the data management system according to the embodiment will be described with reference to FIGS. 10 to 21. FIG. In each sequence diagram described below, communication between each device is based on the assumption that various authentication processes according to a predetermined procedure, processing for establishing a session, etc. are successful, and mutual communication is possible. . Furthermore, in each device, it is assumed that processing for activating a browser in communication via the communication network 100, processing for activating a predetermined application, and the like have already been executed. In this case, the activation of the browser and various applications may be executed by reading various applications and the like by the respective storage reading units of the respective devices and communication terminals.

<Account application and registration processing by affiliate management system>
First, account application and registration processing by the organization management system will be described. FIG. 10 is a sequence diagram showing an example of account application processing by the affiliation management system. The operation accepting unit 52 of the affiliated company management system 5 accepts the account application operation by the person in charge of the affiliated company (company) and various signals associated with the account application operation (step S11).

Next, the transmission/reception unit 51 transmits an account application request to the data management device 3 (step S12). As a result, the transmission/reception unit 31 of the data management device 3 receives the account application request transmitted by the affiliation management system 5 . At this time, the account application request includes the e-mail address information assigned to the person in charge of the place of affiliation (company). In the process of sending the account application request executed in step S12, first, a user interface of the service for providing carrier data according to the present embodiment is displayed on the browser opened in the affiliated terminal 7 that constructs the affiliated institution management system 5. Predetermined information is entered using . Then, the predetermined information is transmitted to the data management device 3 via the affiliation management device 6 .

Next, the generation unit 37 of the data management device 3 generates an account related to the person in charge at the destination (step S13). Specifically, the generation unit 37 generates the account information management DB 3001 (FIG. 5) in association with the e-mail address information (for example, "[email protected]") included in the account application request received in step S12. reference) to generate account identification information (for example, “A0101”). Note that if an account has already been generated (for example, an account application request for the second person or later), the data management device 3 generates the account information for the corresponding role by the first generation process, so the account information management DB 3001 is only referenced (associated).

Next, the transmitter/receiver 31 transmits an account application response as a response to the account application request to the affiliation management system 5 (step S14). As a result, the transmission/reception unit 51 of the affiliation management system 5 receives the account application response transmitted by the data management device 3 . At this time, the account application response includes e-mail address information, URL information of the registration screen, and the like.

Next, the display control unit 54 of the affiliation management system 5 displays a predetermined registration screen on the display 507 of the affiliation management system 5 based on the URL information of the registration screen included in the account application response received in step S14. do. Specifically, the display control unit 54 displays a predetermined registration screen on the display 507 on which the browser is activated by the person in charge of the department. Then, the operation accepting unit 52 accepts an operation on a predetermined registration screen displayed on the display 507 and various signals associated with the operation (step S15).

●Screen display example●
Here, a screen display example for profile editing displayed in the affiliation management system 5 will be described. FIG. 11 is an example of a profile edit screen in the organization management system. As shown in FIG. 11, when the career data platform application for registering and providing the applicant's background information is activated by the organization management system 5, the display 507 displays the carrier's A data infrastructure application activation screen 5101 and a profile edit screen 5111 are displayed. In this case, for example, a profile editing screen 5111 is displayed by the display control unit 54 on the browser screen activated by the person in charge of the department. A profile editing screen 5111 displays a screen for editing the profile of the person in charge of the organization, and provides a UI for inputting items corresponding to the contents of the organization information management DB 3002 shown in FIG. 6 as edit targets. be done. After entering these items, the person in charge of the affiliation can transmit the affiliation information registration request described in step S16 to the data management device 3 by operating the registration button 5151 .

Returning to FIG. 9, the transmitting/receiving unit 51 transmits an affiliation information registration request to the data management device 3 (step S16). As a result, the transmission/reception unit 31 of the data management device 3 receives the affiliation information registration request transmitted by the affiliation management system 5 . At this time, the affiliation information registration request includes various information such as the company name (name of affiliation) and company address input by the person in charge of the affiliation.

Next, the generation unit 37 generates affiliation identification information (for example, "C0001") corresponding to the account identification information generated in step S13 (step S17).

Subsequently, the registration unit 38 registers various information corresponding to the affiliation identification information generated by the generation unit 37 (step S18). Specifically, the registration unit 38 registers the company name (company name), company address, etc. received in step S16 in the company information management DB 3002 (see FIG. 6) that manages company identification information as tabs. Each item is registered in a predetermined item.

Next, the transmitting/receiving section 31 transmits a affiliation information registration response to the affiliation management system 5 (step S19). As a result, the transmitting/receiving unit 51 of the affiliation management system 5 receives the affiliation information registration response transmitted by the data management device 3 . At this time, the affiliation information registration response may include information indicating that the affiliation information has been registered (for example, specific flag information).

In the communication system according to the present embodiment, for example, when the processes of steps S12 and S14 and steps S16 and S19 described above are executed, another device or the like is placed between the data management device 3 and the affiliation management system 5. may exist. That is, each piece of information (data) transmitted and received between the data management device 3 and the affiliation management system 5 may be transmitted and received once via another device. The configuration described above can be applied even when there are other processing steps between the data management device 3 and the organization management system 5 .

<Account application and registration processing by the vendor management system>
Next, account application and registration processing by the vendor management system will be described. FIG. 12 is a sequence diagram showing an example of account application processing by the vendor management system. First, the operation accepting unit 82 of the agent management system 8 accepts an account application operation by the person in charge of the agent and various signals associated with the account application operation (step S21).

Next, the transmission/reception unit 81 transmits an account application request to the data management device 3 (step S22). As a result, the transmission/reception unit 31 of the data management device 3 receives the account application request transmitted by the affiliation management system 5 . At this time, the account application request includes the e-mail address information assigned to the person in charge of the company. The process of transmitting the account application request executed in step S22 is performed by first using the UI of the service for providing carrier data according to the present embodiment with a browser opened on the vendor terminal 10 that constructs the vendor management system 8. predetermined information is input. Predetermined information is transmitted to the data management device 3 via the vendor management device 9 .

Next, the generation unit 37 of the data management device 3 generates an account related to the person in charge of the company (step S23). Specifically, the generation unit 37 generates the account information management DB 3001 (FIG. 5) in association with the e-mail address information (for example, "[email protected]") included in the account application request received in step S22. reference) to generate account identification information (for example, “A0323”). Note that if an account has already been generated (for example, an account application request for the second person or later), the data management device 3 generates the account information for the corresponding role by the first generation process, so the account information management DB 3001 is only referenced (associated).

Next, the transmitter/receiver 31 transmits an account application response as a response to the account application request to the vendor management system 8 (step S24). As a result, the transmitter/receiver 81 of the vendor management system 8 receives the account application response transmitted by the data management device 3 . At this time, the account application response includes e-mail address information, URL information of the registration screen, and the like.

Next, the display control unit 84 of the trader management system 8 displays the registration screen on the display 807 of the trader management system 8 based on the URL information of the registration screen included in the account application response received in step S24. Specifically, the display control unit 84 displays a predetermined registration screen on the display 807 on which the browser is activated by the person in charge of the trader. Then, the operation accepting unit 82 accepts an operation on a predetermined registration screen displayed on the display 807 and various signals associated with the operation (step S25).

●Screen display example●
Here, a screen display example for profile editing displayed in the vendor management system 8 will be described. FIG. 13 is an example of a profile edit screen in the vendor management system. As shown in FIG. 13, when the carrier management system 8 activates the carrier data platform application for registering and providing the applicant's career information, the display 807 displays the carrier data by the display control unit 84. A base application activation screen 8101 and a profile edit screen 8111 are displayed. In this case, for example, the profile edit screen 8111 is displayed by the display control unit 84 on the browser screen activated by the person in charge of the trader. A profile editing screen 8111 displays a screen for editing the profile of the person in charge of the vendor, and provides a UI for inputting items to be edited corresponding to the contents of the vendor information management DB 3003 shown in FIG. . By operating the registration button 8151 after entering these items, the person in charge of the trader can transmit the trader information registration request described in step S26 to the data management device 3 .

Returning to FIG. 12, the transmitting/receiving unit 81 transmits a trader information registration request to the data management device 3 (step S26). As a result, the transmitter/receiver 31 of the data management device 3 receives the vendor information registration request transmitted by the vendor management system 8 . At this time, the trader information registration request includes various kinds of information such as trader name (company name) and trader address.

Next, the generation unit 37 generates vendor identification information (for example, "S0001") corresponding to the account identification information generated in step S23 (step S27).

Subsequently, the registration unit 38 registers various information corresponding to the vendor identification information generated by the generation unit 37 (step S28). Specifically, the registration unit 38 registers the trader name, trader address, etc. received in step S26 in predetermined items of the trader information management DB 3003 (see FIG. 7) that manages the trader identification information as a tab. .

Next, the transmitting/receiving section 31 transmits a vendor information registration response to the vendor management system 8 (step S29). As a result, the transmitter/receiver 81 of the vendor management system 8 receives the vendor information registration response transmitted by the data management device 3 . At this time, the vendor information registration response may include information indicating that the vendor information has been registered (for example, specific flag information).

In the communication system according to the present embodiment, for example, when the processes of steps S22 and S24 and steps S26 and S29 described above are executed, another device or the like is placed between the data management device 3 and the vendor management system 8. may exist. In other words, each piece of information (data) transmitted and received between the data management device 3 and the vendor management system 8 may be transmitted and received once via another device. The configuration described above can be applied even when other processing steps exist between the data management device 3 and the vendor management system 8 .

<Account application and registration processing by the applicant's terminal>
Next, account application and registration processing by the applicant terminal will be described. FIG. 14 is a sequence diagram illustrating an example of account application processing by an applicant terminal. First, the operation receiving unit 42 of the applicant terminal 4 receives an account application operation by the applicant and various signals associated with the account application operation (step S31).

Next, the transmitter/receiver 41 transmits an account application request to the data management device 3 (step S32). Thereby, the transmission/reception unit 31 of the data management device 3 receives the account application request transmitted by the applicant terminal 4 . At this time, the account application request includes the e-mail address information assigned to the applicant.

Next, the generation unit 37 of the data management device 3 generates an account for the applicant (step S33). Specifically, the generation unit 37 associates the e-mail address information (for example, "[email protected]") included in the account application request received in step S32 with the account information management DB 3001 (FIG. 5). reference) to generate account identification information (eg, “A0212”). Note that if an account has already been generated (for example, an account application request for the second person or later), the data management device 3 generates the account information for the corresponding role by the first generation process, so the account information management DB 3001 is only referenced (associated).

Next, the transmitter/receiver 31 transmits an account application response as a response to the account application request to the applicant terminal 4 (step S34). As a result, the transmitter/receiver 41 of the applicant terminal 4 receives the account application response transmitted by the data management device 3 . At this time, the account application response includes e-mail address information, URL information of the registration screen, and the like.

Next, the display control unit 44 of the applicant terminal 4 displays the registration screen on the display 407 of the applicant terminal 4 based on the URL information of the registration screen included in the account application response received in step S34. Specifically, the display control unit 44 displays a predetermined registration screen on the display 407 on which the applicant has activated the browser. Then, the operation reception unit 42 receives various signals based on the operation and the operation on the predetermined registration screen displayed on the display 407 (step S35).

●Screen display example●
Here, a screen display example for profile editing displayed on the applicant terminal 4 will be described. FIG. 15 is an example of a profile edit screen on the applicant's terminal. As shown in FIG. 15 , when the carrier data platform application for registering and providing the applicant's career information is activated by the applicant terminal 4, the carrier data is displayed on the display 407 by the display control unit 44. A base application activation screen 4101 and a profile edit screen 4111 are displayed. In this case, for example, a profile edit screen 4111 is displayed by the display control unit 44 on the browser screen activated by the applicant. A profile editing screen 4111 displays a screen for editing the profile of the applicant, and provides a UI for inputting items to be edited corresponding to the contents of the applicant information management DB 3004 shown in FIG. . After entering these items, the applicant can operate the registration button 4151 to transmit information for registering an account, which will be described below, to the data management device 3 .

Returning to FIG. 14, the registration unit 48 registers an account (step S36). Specifically, the registration unit 48 transmits each information input for each item displayed on the profile edit screen 4111 by the applicant accepted in step S35 to the data management device 3 via the transmission/reception unit 41. Then, it is registered in the corresponding item of the applicant information management DB 3004 (see FIG. 8) managed by the data management device 3 .

<Processing request for import of background information>
Next, the history information acquisition request process will be described. FIG. 16 is a sequence diagram showing an example of history information import request processing. First, when the applicant activates the browser on the applicant terminal 4 , the display control unit 44 displays on the display 407 a screen requesting acquisition of career information (carrier data). Then, the operation reception unit 42 receives a predetermined operation by the applicant and a signal associated with the operation (step S41).

Next, the processing unit 45 extracts the applicant's affiliation (for example, affiliation identification information) based on the various signals received in step S41 (step S42).

Next, the registration unit 48 registers personal identification information (step S43). Specifically, the registration unit 48 registers the applicant's employee number, e-mail address, etc. input in step S41.

●Screen display example●
Here, an example of a screen display for selecting a provider of career information and requesting acquisition of career information displayed on the applicant terminal 4 will be described. FIG. 17 is an example of an operation screen for selecting a provider of history information and performing an import request operation on the applicant's terminal. As shown in FIG. 17, when the carrier data base application (or browser) for registering and providing the applicant's career information is started by the applicant terminal 4, the display 407 displays the display control unit 44 , a carrier data base application activation screen 4201 and a carrier data provider selection screen 4211 are displayed. The carrier data provider selection screen 4211 is associated with the name of one or more affiliations, including the affiliation to which the applicant belongs (belonged), the service name, and the status indicating the status of the background information acquisition request. In addition, an import request button and an import stop button are displayed for each affiliation. At this time, career information (carrier data) related to one or more affiliations is information whose reliability is guaranteed.

In this state, for example, the user operates the import request button displayed by pointing the pointer 4251 of the mouse to one of the one or more affiliations. As a result, an account information input dialog 4212 related to the selected affiliation is popped up by the display control unit 44 in the vicinity of the import request button moused over. By providing such a UI, the applicant can enter predetermined information (for example, the applicant's employee number, e-mail address, etc. for identifying the applicant) in the account information input dialog 4212 that pops up. A registration button 4261 can be operated by inputting. Then, the applicant terminal 4 can transmit fetching request information indicating a fetching request for fetching his/her history information to the data management device 3 in a step to be described later. The display of the UI screen for selecting the organization to which the applicant belongs and inputting the applicant identification information and the method of inputting the applicant identification information are not limited to the method of popping up a predetermined dialog screen.

Returning to FIG. 16, the transmission/reception unit 41 transmits capture request information indicating a capture request to the data management device 3 (step S44). As a result, the transmission/reception unit 31 of the data management device 3 receives the acquisition request information transmitted by the applicant terminal 4 . At this time, the import request information includes the applicant identification information and affiliation identification information obtained in steps S41-S43.

Next, the transmitting/receiving section 31 of the data management device 3 transmits (transfers) the import request information received in step S44 to the affiliation management system 5 (step S45). As a result, the transmission/reception unit 51 of the destination management system 5 receives the acquisition request information transmitted by the data management device 3 . At this time, the import request information includes the applicant's employee number as the applicant's identification information, the e-mail address used by the applicant's affiliated company (hereinafter referred to as "company e-mail address"), etc. included.

Next, the processing unit 55 of the affiliation management system 5 confirms the applicant (step S46). Specifically, the processing unit 55 searches the applicant history management DB 5001 (see FIG. 9) using the applicant identification information (applicant's employee number, company email address, etc.) included in the received import request information as a search key. Search and verify applicants.

Next, the acquisition unit 53 acquires the applicant's career data (step S47). Specifically, the acquisition unit 53 searches the applicant history management DB 5001 (see FIG. 9) using the applicant's employee number, company email address, etc. as the applicant identification information received in step S45 as search keys. , read and acquire the applicant's career data, which is managed using the applicant's company email address as a tab. The applicant's employee number, company e-mail address, etc. are examples of reliable information known by the personnel department of the applicant's affiliated company (company).

Next, the transmitting/receiving unit 51 transmits capture response information indicating a capture response as a response to the capture request received in step S45 to the data management device 3 (step S48). As a result, the transmission/reception unit 31 of the data management device 3 receives the capture response information. At this time, the capture response information includes the applicant's carrier data, provider information indicating the provider, information on the date and time when the applicant's carrier data was provided (transmitted) to the data management device 3, and the validity of the provided carrier data. Contains expiry date information that indicates an expiration date. In this way, the affiliation management system 5 transmits information including provider information, date and time information, and expiration date information to the data management device 3, thereby allowing the applicant's history to be retrieved. It becomes possible to ensure the reliability of information (carrier data).

Next, the registration unit 38 of the data management device 3 registers at least one of the applicant's carrier data, provider information, provision (transmission) date and time information, and expiration date information included in the capture response information received in step S48. are registered in the applicant information management DB 3004 (see FIG. 8) (step S49). As a result, the data management device 3 stores information including provider information, date and time information, and expiration date information in the applicant information management DB 3004 (FIG. 8) in association with the applicant's career information (carrier data) received in step S48. ), it is possible to register and manage various types of information whose reliability is ensured by the affiliation management system 5 as it is.

Subsequently, the transmitting/receiving section 31 transmits capture response information as a response to the capture request information received in step S44 to the applicant terminal 4 (step S50). As a result, the transmitter/receiver 41 of the applicant terminal 4 receives the capture response information transmitted by the data management device 3 . At this time, the capture response information includes registration URL information for registration performed at applicant terminal 4 and capture completion notification information for notifying completion of capture. Note that the capture completion notification information may include information indicating that the capture request has been completed (for example, specific flag information).

Next, the history information import request process will be described. FIG. 18 is a sequence diagram showing an example of confirmation of completion of acquisition of history information and additional correction registration processing by the applicant terminal. After receiving the capture response information in step S50, the processing unit 45 confirms completion of capture (step S51), and the registration unit 48 performs additional correction registration of the carrier data (step S52). Specifically, the registration unit 48 cooperates with the display control unit 44 and the operation reception unit 42 to add the additional correction information input by the applicant to the profile edit screen 4111 displayed on the browser screen. register. The additional correction information includes, for example, qualifications not registered in the company to which the applicant belongs, career history in the company to which the applicant previously belonged, and the like. At this time, the additional correction information is added to the corresponding items in the applicant information management DB 3004 (see FIG. 8) managed by the data management device 3 via the browser, or to the newly added items. . Applicants cannot edit the information registered by the company they belong to.

<Processing to start using history information>
Next, the history information usage start process will be described. FIG. 19 is a sequence diagram illustrating an example of a history information utilization start process. First, when the applicant activates the browser on the applicant terminal 4, the display control unit 44 displays a screen for designating a provider of career information (carrier data) on the display 407 (step S61).

●Screen display example●
FIG. 20 is an example of an operation screen for selecting a trader when providing history information on the applicant's terminal and performing an import request operation. As shown in FIG. 20, when the carrier data base application (or browser) for registering and providing the applicant's career information is started by the applicant terminal 4, the display 407 displays the display control unit 44 , a carrier data base application start screen 4201 and a carrier data provision start screen 4221 are displayed. On the carrier data provision start screen 4221, a list is displayed in association with the name, service name, usage, and status indicating the status of provision of career information of one or more companies that have registered career information (carrier data) of the applicant. Furthermore, a start provision button and a detail button are displayed for each trader. In this state, for example, when the user operates a provision start button displayed corresponding to one of the one or more vendors, the vendor name associated with the provision start button is specified. The detail button is a button for browsing detailed information about each trader, for example.

Returning to FIG. 19, the operation accepting unit 42 accepts the designation of the provider of the carrier data and the selection of the service to be provided (step S62).

Next, the transmission/reception unit 41 transmits provision start request information indicating a request to start provision of carrier data to the data management device 3 (step S63). Thereby, the transmission/reception unit 31 of the data management device 3 receives the provision start request information transmitted by the applicant terminal 4 . At this time, the provision start request information includes the trader name of the trader selected by the applicant in step S62.

Next, the identification unit 35 of the data management device 3 identifies the provided service (step S64). Specifically, the specifying unit 35 searches the vendor information management DB 3003 (see FIG. 7) using the vendor name received in step S63 as a search key, and retrieves the vendor information managed with the corresponding vendor identification information as a tag. Read the management table. Subsequently, the specifying unit 35 specifies the provided services included in the read vendor information management table.

Next, the transmitting/receiving unit 31 transmits additional notification information indicating an additional notification of the service user to the vendor management system 8 that provides the service specified in step S64 (step S65). As a result, the transmitter/receiver 81 of the vendor management system 8 receives the additional notification information transmitted by the data management device 3 . At this time, the additional notification information includes URL information of the confirmation screen, affiliation identification information, provision (transmission) date and time information, and expiration date information.

Next, the processing unit 85 of the vendor management system 8 confirms the service user (step S66). At this time, the processing unit 85 is independently managed by the vendor management system 8 based on the URL information of the confirmation screen received in step S65, the affiliation identification information, the provision (transmission) date and time information, the expiration date information, etc. A corresponding service user may be identified by referring to a predetermined database, external storage, or the like.

Next, the acquiring unit 83 acquires history information (carrier data) corresponding to the service user confirmed in step S66 from a predetermined database, external storage, or the like (step S67). Note that each process of steps S66 and S67 described above is a process executed by an external system such as the trader management system 8, and therefore the processing mode is not limited.

Next, the transmitting/receiving unit 81 transmits a carrier data provision start notification to the data management device 3 (step S68). As a result, the transmission/reception unit 31 of the data management device 3 receives the carrier data provision start notification transmitted by the vendor management system 8 . At this time, the carrier data provision start notification includes provision start information (flag or the like) indicating the start of carrier data provision.

Next, the transmission/reception unit 31 of the data management device 3 transmits provision start response information indicating a carrier data provision start response to the applicant terminal 4 as a response to the carrier data provision start request information received in step S63. (step S69). As a result, the transmitter/receiver 41 of the applicant terminal 4 receives the provision start response information transmitted by the data management device 3 . At this time, the provision start response information includes provision start information indicating the start of provision of carrier data.

Next, the processing unit 45 of the applicant terminal 4 confirms the start of service provision, and as indicated by the circle A, proceeds to step S41 for displaying the import request screen and accepting the operation described in FIG. to migrate. (Step S70).

Note that when executing the capture request again in step S41 with circle A, the data management device 3, based on the expiration date information received in step S65, includes the date and time when the capture request was executed ( is within the expiration date) may be determined. By performing such time limit setting and processing, carrier data whose expiration date has passed (old carrier data) is made unusable. However, it is also possible to update the expiration date by executing the carrier data import request again. The expiration date can be individually set by the applicant himself/herself, or can be set by the person in charge of the affiliated organization management system 5 to which the applicant belongs.

●Screen display example●
FIG. 21 is an example of an operation screen for stopping the provision of history information on the applicant's terminal. As shown in FIG. 21, when the carrier data base application (or browser) for registering and providing the applicant's career information is started by the applicant terminal 4, the display 407 displays the display control unit 44 , a carrier data base application start screen 4201, a message display screen 4231, a carrier data provider display screen 4232, and a carrier data provider display screen 4233 are displayed. On the message display screen 4231, a predetermined message from the system is displayed along with the start of provision of carrier data. On the carrier data provider display screen 4232, the vendor that has started providing carrier data is additionally displayed. Carrier data provider display screen 4233 displays information about the carrier data provider displayed on carrier data provider selection screen 4211 shown in FIG.

It should be noted that, in the carrier data provider display screen 4232, when the provision stop button displayed in association with one or more carrier data provider (trader) is operated, the processing of step S63 described above is executed, and the data A process for stopping the provision of carrier data to the selected carrier data provider (dealer) is executed on the management device 3 . Here, for example, the following cases are conceivable as usage scenes for stopping the provision of carrier data.
・When the applicant's place of employment, etc. has been decided and the provision of information by the vendor is no longer necessary. By enabling such measures, it becomes possible to prevent unnecessary use and leakage of highly confidential personal information such as a person's career data (biographical information).

[Main effects of the embodiment]
As described above, according to the present embodiment, the data management device 3 receives the capture response information indicating the capture response as a response to the capture request sent by the applicant terminal 4 from the affiliation management system 5. (Step S48), and registers the applicant's career data, provider information, provision (transmission) date and time information, and expiration date information included in the capture response information in the applicant information management DB 3004 (see FIG. 8) ( step S49). Thereafter, the data management device 3 transmits capture response information including registration URL information for registration performed on the applicant terminal 4 to the applicant terminal 4 as a response to the capture request information (step S50). ). As a result, it is possible to secure the reliability of career information of applicants, for example, job seekers.

Furthermore, according to the present embodiment, by managing the expiration date information indicating the expiration date in response to the history information acquisition request from the applicant together with the history information, it is possible to prevent the use of old history information. It is possible to prevent this, and it is possible to maintain the freshness of the applicant's background information.

Furthermore, according to the present embodiment, by performing the provision stop processing for a specific company by the applicant, there is an effect that it is possible to prepare a system for providing history information according to the convenience of the applicant.

Furthermore, according to the present embodiment, the affiliation management system 5 to which the applicant belongs and the data management device 3 cooperate to register and manage career information, thereby facilitating each input operation performed by the applicant. has the effect of enabling

[Supplement to the embodiment]
Each function of the above-described embodiments can be implemented by one or more processing circuits. As used herein, the term "processing circuitry" includes devices programmed by software to perform functions, such as processors implemented by electronic circuitry. This device is, for example, a processor, an ASIC (Application Specific Integrated Circuit) designed to perform each function described above, a DSP (digital signal processor), an FPGA (field programmable gate array), an SOC (System on a chip), GPU (Graphics Processing Unit), and conventional circuit modules.

Furthermore, the freshness information (e.g., validity period, etc.) related to career information (carrier data) obtained by the above-described embodiment may be obtained and managed by the learning effect of machine learning using artificial intelligence (AI). . Here, machine learning is a technology that allows computers to acquire human-like learning abilities. It is a technology that applies this to new data and makes predictions. The learning method for machine learning may be supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, or deep learning. A combined learning method may be used, and any learning method for machine learning may be used.

So far, the data management system, data management device, data management method, and program have been described as one embodiment of the present invention. , change or deletion, etc., can be changed within the range that a person skilled in the art can conceive, and as long as the action and effect of the present invention are exhibited in any aspect, it is included in the scope of the present invention.

1 communication system 2 data management system 3 data management device 4 applicant terminal 5 affiliation management system 8 trader management system 31 transmission/reception unit (an example of receiving means, an example of transmitting means)
38 registration unit (an example of registration means)
53 Acquisition unit (an example of acquisition means)
54 Display control unit (an example of display control means)

JP 2020-047251 A

Claims (12)

A affiliation management system that manages information on the affiliation of an applicant who applies for the use of his or her career information, and a data management device that manages the career information and applicant identification information that identifies the applicant in association with each other. A data management system comprising:
The data management device
A specific acquisition as a response to the acquisition request information, which is acquired by the affiliated organization management system based on the acquisition request information for requesting the acquisition of the career information transmitted by the applicant terminal used by the applicant receiving means for receiving the input response information and the history information;
a registration means for adding the specific acquisition response information to the received history information and registering it as applicant specific additional information associated with the applicant identification information;
a transmitting means for transmitting the registered applicant-identifying additional information to the applicant terminal;
having
A data management system characterized by: The specific retrieval response information includes affiliation identification information for identifying the affiliation management system, provision date and time information representing the date and time when the affiliation management system transmitted the history information to the data management device, and at least one of expiration date information indicating the expiration date of the background information,
The registration means
At least one of the organization identification information, the provision date and time information, and the expiration date information is added to the career information and registered as the applicant specific additional information associated with the applicant identification information.
The data management system according to claim 1, characterized by: The affiliation management system includes applicant history management means for managing the history information of the applicant confirmed based on the acquisition request information in association with applicant confirmation information for confirming the applicant. having an acquisition means that acquires from
3. The data management system according to claim 1 or 2, characterized by: A data management system according to any one of claims 1 to 3,
The affiliation management system further
Display control means for displaying on a display means a registration screen input to register a person in charge of an organization using the organization management system,
A data management system characterized by: The registration means
Registering information related to the management system for the affiliated organization generated based on the input contents on the registration screen;
5. The data management system according to claim 4, characterized in that: The transmission means is
Sending the expiration date information included in the specific capture response information sent by the affiliation management system to the vendor management system that provides the history information in response to the request of the applicant;
6. The data management system according to any one of claims 2 to 5, characterized in that: The receiving means
Capture request information related to a capture request request for requesting capture of the history information transmitted by the applicant terminal, provision start request information related to a provision start request for starting the provision of the history information, and receiving any of the provision stop request information related to the provision stop request for stopping the provision of the history information;
The data management system according to claim 1, characterized by: The receiving means
receiving the acquisition request information including specific affiliation identification information indicating a specific affiliation selected by the applicant's operation on the applicant terminal when there are a plurality of said affiliation management systems;
8. The data management system according to claim 7, characterized by: The receiving means
When there are a plurality of vendor management systems that register the career information and provide it in response to the applicant's request, a specific vendor name indicating the specific vendor selected by the applicant's operation on the applicant terminal receive start-up request information, including
The data management system according to claim 1, characterized by: A data management device that associates and manages applicant identification information that identifies an applicant who applies for use of his or her career information and the career information,
A specific acquisition as a response to the acquisition request information, which is acquired by the affiliated organization management system based on the acquisition request information for requesting the acquisition of the career information transmitted by the applicant terminal used by the applicant receiving means for receiving the input response information and the history information;
a registration means for adding the specific acquisition response information to the received history information and registering it as applicant specific additional information associated with the applicant identification information;
a transmitting means for transmitting the registered applicant-identifying additional information to the applicant terminal;
having
A data management device characterized by: A data management method executed by a data management device that associates and manages applicant identification information that identifies an applicant who applies for the use of his or her career information with the career information,
A specific acquisition as a response to the acquisition request information, which is acquired by the affiliated organization management system based on the acquisition request information for requesting the acquisition of the career information transmitted by the applicant terminal used by the applicant a receiving step of receiving the embedded response information and the history information;
a registration step of adding the specific acquisition response information to the received history information and registering it as applicant specific additional information associated with the applicant identification information;
a transmission step of transmitting the registered applicant-identifying additional information to the applicant terminal;
A data management method characterized by executing a process including In a data management method executed by a data management device that associates and manages applicant identification information that identifies an applicant who applies for the use of his or her career information with the career information,
A specific acquisition as a response to the acquisition request information, which is acquired by the affiliated organization management system based on the acquisition request information for requesting the acquisition of the career information transmitted by the applicant terminal used by the applicant a receiving step of receiving the embedded response information and the history information;
a registration step of adding the specific acquisition response information to the received history information and registering it as applicant specific additional information associated with the applicant identification information;
a transmission step of transmitting the registered applicant-identifying additional information to the applicant terminal;
A program that executes a process including

Images