Member information management method and device, electronic equipment and computer readable storage medium

Abstract

The present disclosure provides a member information management method and device, electronic equipment and computer readable storage medium, and relates to the technical field of computer and Internet. The member information management method comprises: creating a member information management project in a management group in a code management warehouse of a target organization; defining and storing member information in the member information management project according to the code management warehouse; and configuring a project role for a member in the target organization in the member information according to an organizational structure of the target organization in the code management warehouse, so that the member in the target organization views and modifies the member information according to the project role. The embodiment of the present disclosure can simply and conveniently manage the member information of the member in the target organization in multiple aspects and in all directions.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of computers and Internet, and particularly relates to a member information management method and device, electronic equipment and computer readable storage medium. BACKGROUND

[0002] This section is intended to provide background information to facilitate a better understanding of embodiments of this application as set forth in the claim. The description herein does not constitute admission of prior art.

[0003] In the process of company management, unified management of employee information can improve the efficiency of company management.

[0004] At present, with the development of Internet technology, various office software and databases have made great progress and can realize efficient information management. Therefore, centralized management of employee information through various third-party office software and databases is a common method for employee information management at present.

[0005] However, the method of managing all employee information by using a third-party platform is not flexible and has a strong dependence on the platform; the development of a traditional employee system by the company itself requires the introduction of a database, which has a large operation and maintenance cost, and the development of a traditional employee system also requires the processing of information updating, updating review, updating history record and other functions, which has a large development cost. SUMMARY

[0006] The purpose of the present disclosure is to provide a member information management method and device, electronic equipment and computer readable storage medium, which can simply and conveniently manage member information based on a code repository.

[0007] Other characteristics and advantages of the present disclosure will become apparent from the following detailed description, or will be learned by practice of the present disclosure.

[0008] The present disclosure provides a member information management method, which comprises: creating a member information management project in a management group in a code management repository of a target organization; defining and storing member information in the member information management project according to the code management repository; configuring a project role for a member in the target organization in the member information according to the organizational structure of the target organization in the code management repository, so that the member in the target organization can view and modify the member information according to the project role.

[0009] In some embodiments, according to the code management warehouse, the member information is defined and stored in the member information management project, including: adding a static file in the member information management project; obtaining first candidate member information from the code management warehouse, and writing the first candidate member information into the static file to generate the member information.

[0010] In some embodiments, the code management warehouse of the target organization includes at least one management group, the at least one management group includes a first management group, the first management group includes at least one management project, and the at least one management project includes a first management project; wherein the member information management project is created in the management group in the code management warehouse of the target organization, including: creating the member information management project in the first management project; wherein the first candidate member information is obtained from the code management warehouse, and the first candidate member information is written into the static file to generate the member information, including: obtaining member information of each group member in the first management group; generating the first candidate member information according to the member information of each group member in the first management group; and writing the first candidate member information into the static file to generate the member information.

[0011] In some embodiments, the first management project includes a first project member and a second project member, and the second project member has member information management authority in the first management project; wherein the method further includes: receiving second candidate member information sent by the first project member in the first management project; determining the second project member with member information management authority in the first management project according to the project role in the member information; sending the second candidate member information to the second project member so that the second project member audits the member information according to the second candidate member information; receiving the audit result; and updating the member information according to the second candidate member information after determining that the audit is passed according to the audit result.

[0012] In some embodiments, the code management warehouse of the target organization includes at least one management group; wherein creating a member information management project in a management group in the code management warehouse of the target organization includes: creating a second management group in the code management warehouse of the target organization; creating the member information management project in the second management group; wherein obtaining first candidate member information from the code management warehouse and writing the first candidate member information into the static file to generate the member information includes: obtaining member information of group members in each management group in the code management warehouse; generating the first candidate member information according to the member information of the group members in each management group in the code management warehouse; and writing the first candidate member information into the static file to generate the member information.

[0013] In some embodiments, the member information includes static member information of members in the target organization in the target organization and platform primary keys corresponding to application information of members in the target organization in a third-party platform.

[0014] In some embodiments, the members in the target organization include third project members; wherein the method further includes: receiving a member information obtaining request sent by the third project members; if static employee information is requested in the member information obtaining request, obtaining a static employee information value from the static file and returning the static employee information value to the third project members; if dynamic employee information is requested in the member information obtaining request, obtaining the platform primary key from the static file; and obtaining the dynamic employee information from the third-party platform according to the platform primary key, so as to return the dynamic employee information to the third project members.

[0015] Embodiments of the present disclosure provide a member information management device, which includes a member information management project creation module, an initialized member information module, and a project role configuration module.

[0016] The member information management project creation module is configured to create a member information management project in a management group in a code management warehouse of a target organization; the initialized member information module is configured to define and store member information in the member information management project according to the code management warehouse; and the project role configuration module is configured to configure project roles for members in the target organization in the member information according to an organizational structure of the target organization in the code management warehouse, so that the members in the target organization view and modify the member information according to the project roles.

[0017] The electronic device includes a memory and a processor. The memory is configured to store computer program instructions. The processor is configured to invoke the computer program instructions stored in the memory, and implement the member information management method.

[0018] The computer readable storage medium stores computer program instructions. The computer program instructions are read by a processor to implement the member information management method.

[0019] The computer program product or the computer program includes computer program instructions stored in a computer readable storage medium. The computer program instructions are read by a processor to implement the member information management method.

[0020] The member information management method, the device, the electronic device and the computer readable storage medium provided by the embodiments of the present disclosure can create a member information management project in a management group in a code management warehouse of a target organization, initialize each member information and a project role by using related information in the code management warehouse of the target organization, and then realize viewing and modifying of the member information by using a project role in an organizational structure in the code management warehouse of the target organization, so that the member information is conveniently and simply managed.

[0021] It should be understood that the foregoing general description and the following detailed description are only exemplary and are not limiting on the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0022] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and serve to explain the principles of the present disclosure. It is readily apparent to one of ordinary skill in the art that the accompanying drawings are merely illustrative of some embodiments of the present disclosure and that additional embodiments of the present disclosure can be obtained from these drawings without departing from the spirit or scope of the present disclosure.

[0023] Figure 1 A scenario diagram of the member information management method or the member information management device according to the embodiments of the present disclosure is shown.

[0024] Figure 2 A flowchart of a member information management method according to an exemplary embodiment is shown.

[0025] Figure 3 A member information management method according to an exemplary embodiment is shown.

[0026] Figure 4A member information management method according to an exemplary embodiment

[0027] Figure 5 A member information management method according to an exemplary embodiment

[0028] Figure 6 A member information management method according to an exemplary embodiment

[0029] Figure 7 A member information management method according to an exemplary embodiment

[0030] Figure 8 A member information management method according to an exemplary embodiment

[0031] Figure 9 A member information management method according to an exemplary embodiment

[0032] Figure 10 A member information management method according to an exemplary embodiment

[0033] Figure 11 A member information management method according to an exemplary embodiment

[0034] Figure 12 A member information management method according to an exemplary embodiment

[0035] Figure 13 A member information management method according to an exemplary embodiment

[0036] Figure 14 A member information management method according to an exemplary embodiment

[0037] Figure 15 A structure schematic diagram of an electronic device suitable for implementing the embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0038] Example embodiments now will be described more fully hereinafter with reference to the accompanying drawings. Example embodiments, however, can be implemented in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of example embodiments to those skilled in the art. Like reference numerals refer to like elements throughout the figures, and thus description of the same will be omitted.

[0039] Those skilled in the art know that the embodiments of the present application can be a system, a device, an apparatus, a method or a computer program product. Therefore, the present application can be embodied as a whole hardware, a whole software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

[0040] The features, structures or characteristics described in the present disclosure can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the present disclosure. One skilled in the relevant art will recognize, however, that the techniques of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known structures, devices, implementations or operations are not shown or described in detail in order to avoid obscuring aspects of the present disclosure.

[0041] The accompanying drawings are merely illustrative of the present disclosure and therefore should not be considered to be limiting of its scope in any way. The same reference numbers in different drawings represent the same or similar elements.

[0042] The flow diagrams illustrated in the drawings are merely exemplary and do not necessarily include all of the steps and / or components, nor do they necessarily indicate the order in which the steps can be performed. For example, some steps can be performed in parallel, or some steps can be omitted, or some steps can be combined or partially combined, and thus the order of execution can be changed according to the actual situation.

[0043] In the description of the present application, unless otherwise stated, " / " means "or", for example, A / B can mean A or B. "And / or" in this document is only a description of the relationship between the associated objects, which means that there can be three relationships, for example, A and / or B, which means that there are three cases of A alone, A and B together, and B alone. In addition, "one or more" means one or more, and "multiple" means two or more. "First", "second", etc. do not limit the quantity and execution order, and "first", "second", etc. do not necessarily mean different; the words "include", "contain" and "have" mean open inclusion and mean that there can be additional elements / components / etc. in addition to the listed elements / components / etc.

[0044] In order to enable the above-mentioned purposes, features and advantages of the present application to be more clearly understood, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments, and it should be noted that the embodiments of the present application and the features in the embodiments can be combined with each other without conflict.

[0045] It should be noted that in the technical solutions of the present disclosure, the collection, collection, updating, analysis, processing, use, transmission, storage and the like of user personal information are in line with the relevant legal regulations, are used for legal purposes, and do not violate public order and good customs. Necessary measures are taken for user personal information to prevent illegal access to user personal information data, and to maintain user personal information security, network security and national security.

[0046] First, some terms related to the embodiments of the present application will be explained below to facilitate understanding by those skilled in the art.

[0047] DevOps: DevOps (Development and Operations) is a combination of processes, methods and systems that promote communication, collaboration and integration between development (application / software engineering), technical operations and quality assurance (QA) departments.

[0048] DevOps platform: The DevOps platform is a platform that implements common DevOps functions (Git (distributed version control system), Issue (a project management software), MergeRequest (branch merge request), and CI / CD (continuous integration, continuous delivery and continuous deployment)). Common platforms include GitLab, GitHub and Gitee.

[0049] GitLab: GitLab is an integrated DevOps platform, an open source project for repository management systems, using Git as a code management tool and building a web service on this basis.

[0050] GitHub is a hosting platform for open source and private software projects. Because it only supports Git as the only version library format for hosting, it is named GitHub.

[0051] Gitee: a code hosting platform.

[0052] YAML: YAML( YAML (similar to camel) is a highly readable format for expressing data serialization.

[0053] The foregoing introduces some concepts related to the embodiments of the present application, and the technical features related to the embodiments of the present application are introduced below.

[0054] The example embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

[0055] Figure 1 A scenario diagram of a member information management method or a member information management device that can be applied to the embodiments of the present disclosure is shown.

[0056] Reference is made to Figure 1 which shows a schematic diagram of an implementation environment provided by an example embodiment of the present application.

[0057] As Figure 1 shown, the system architecture 100 can include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used to provide a communication link medium between the terminal devices 101, 102, 103 and the server 105. The network 104 can include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

[0058] The user can use the terminal devices 101, 102, 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Among them, the terminal devices 101, 102, 103 can be various electronic devices with display screens and support web browsing, including but not limited to smartphones, tablet computers, laptop computers, desktop computers, wearable devices, virtual reality devices, smart homes, etc.

[0059] The server 105 can be a server that provides various services, such as a background management server that provides support for the user's operation on the device using the terminal devices 101, 102, 103. The background management server can analyze and process the received request data, etc., and feed back the processing result to the terminal device.

[0060] The server can be a standalone physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and basic cloud computing services such as big data and artificial intelligence platforms, etc. The present disclosure does not limit this.

[0061] The server 105 can create a member information management project in a management group in the code management repository of the target organization, for example; the server 105 can define and store member information in the member information management project according to the code management repository, for example; the server 105 can configure project roles for members in the target organization in the member information according to the organizational structure of the target organization in the code management repository, so that the members in the target organization view and modify the member information according to the project roles.

[0062] It should be understood that Figure 1 The number of terminal devices, networks and servers in the above-mentioned embodiments is only illustrative, and the server 105 can be a server of one entity, or can be composed of multiple servers, and can have any number of terminal devices, networks and servers according to actual needs.

[0063] Figure 2 is a flowchart of a member information management method according to an exemplary embodiment. The method provided by the embodiments of the present disclosure can be executed by any electronic device with computing processing capability, for example, the method can be executed by the server or the terminal device in the above-mentioned embodiments, or can be executed by the server and the terminal device together. In the following embodiments, the server is taken as an example for illustration, but the present disclosure is not limited thereto. Figure 1

[0064] Referring to Figure 2 The member information management method provided by the embodiments of the present disclosure can include the following steps.

[0065] Step S202: creating a member information management project in a management group in a code management repository of a target organization.

[0066] An organization is an organized system in which two or more individuals or groups combine to achieve a common goal and improve action. For example, it can be a company, a labor union in a company, a department in a company, a public welfare organization, etc., and the present application does not limit it.

[0067] The code management repository is also called code repository or code hosting platform, etc., and any code management repository that can be used to store and manage code can be the above-mentioned code management repository. The code management repository can be a git code management platform, such as gitlab, github or gitee, etc., and the present application does not limit it.

[0068] In some embodiments, at least one group can be constructed in the code management repository of an organization, and at least one group and / or at least one project can be constructed in a group.

[0069] ​In some embodiments, the project in the code management warehouse in the related art hosts code, and the code in the project or group can be viewed, modified, merged, updated, etc. by relevant personnel. In the present application, the project in the code management warehouse in the related art hosts member management information, and the member management information hosted in the project can be viewed, modified, merged, updated, etc. by relevant personnel through the technical solutions provided in the present application.

[0070] In step S204, member information is defined and stored in the member information management project according to the code management warehouse.

[0071] In some embodiments, a member information management project can be constructed in a certain group in the code management warehouse, and the member information management project can only manage the member information in the group where the project is located, or can manage the member information in one or more specified groups in the code management warehouse, or can manage the members in all groups in the code management warehouse, which is not limited in the present application.

[0072] For example, it is assumed that the code management warehouse can include three groups A, B and C, and the group A can further include two groups a1 and a2. A group D parallel to the groups A, B and C can be constructed in the code warehouse, and a member information management project can be constructed in the group D to manage all members in the code management warehouse or to manage the members in a specified group (such as the group A). A member information management project can also be constructed in the group A to manage all members in the code management warehouse or to manage the members in a specified group (such as the group B) or to manage the members in the group (group A) where the member information management project is located. A member information management project can also be constructed in the group a1 to manage all members in the code management warehouse or to manage the members in a specified group (such as the group B) or to manage the members in the group (group a1) where the member information management project is located, which is not limited in the present application.

[0073] In some embodiments, initial member information such as name, gender, phone number, email address, etc. is generally defined when the code management warehouse or the group is constructed.

[0074] In some embodiments, after the member information management project is constructed, some initial member information can be defined and stored in the member information management project according to the member information in the code management warehouse or the group, for example, the initial member information in the group or the code management warehouse can be inherited.

[0075] In step S206, according to the organization structure of the target organization in the code management warehouse, the project roles of the members in the target organization are configured in the member information, so that the members in the target organization can view and modify the member information according to the project roles.

[0076] In some embodiments, each group can include multiple projects, each project can include multiple members, and each member can have his own project role in the project, for example, some are managers, and some are ordinary technical members.

[0077] In some embodiments, the project roles of the member information corresponding to each member in the target organization can be configured according to the project roles of the member in different projects. It can be understood that a member can have different roles in different projects, for example, a member is a manager in the b1 project and an ordinary technical member in the b2 project.

[0078] In some embodiments, after the initial construction of the member information is completed, all members or specified members in the target organization can view or modify all member information or specified member information according to their project roles. For example, member c as a project manager can view or modify his own member information, view or modify the member information of all members in his project or group, and view or modify the member information of members in other projects or groups. The present application does not limit this, and those skilled in the art can set it according to their own needs.

[0079] The technical solution provided by the above embodiments can construct a member management management project in the code management warehouse of the target organization, rely on the code warehouse of the target organization to define, modify, update and manage the member information, without the need to develop a new employee management system and maintain and update the database, saving manpower and resources.

[0080] Figure 3 A member information management method is shown according to an exemplary embodiment.

[0081] Reference Figure 3 The above member information management method can include the following steps.

[0082] In step S302, a member information management project is created in the management group in the code management warehouse of the target organization.

[0083] In step S304, a static file is added in the member information management project.

[0084] In some embodiments, static files can be added to a newly created member information management project. In related technologies, static files in a project can store code; however, in this application, static files in a project can also store member management information.

[0085] Step S306: Obtain the first candidate member information from the code management repository and write the first candidate member information into a static file to generate member information.

[0086] The aforementioned first candidate member information may include information about members already existing in the code repository, such as the member's name, gender, phone number, email address, etc.

[0087] Step S308: Based on the organizational structure of the target organization in the code management repository, configure project roles for members in the target organization in the member information so that members in the target organization can view and modify member information according to their project roles.

[0088] In some embodiments, the project roles of each member in each group of the code management repository can also be written into a static file to configure the idiom information of each member.

[0089] In the above embodiment, the basic member information configuration of a member can be completed simply by creating a static file in a group of the code management repository, obtaining the first candidate member information from the code management repository and writing it into the static file.

[0090] Figure 4 This is a member information management method illustrated according to an exemplary embodiment.

[0091] In some embodiments, the target organization’s code management repository may include at least one management group, wherein the at least one management group may include a first management group.

[0092] refer to Figure 4 The above-mentioned member information management method may include the following steps.

[0093] Step S402: Create a member information management project in the first management group.

[0094] Step S404: Add static files to the member information management project.

[0095] Step S406: Obtain member information of each group member in the first management group.

[0096] In some embodiments, the member information management project can inherit the member information in the group where the project is located and the project role. For example, the member information management project is built in group a1, then the member information management project can inherit the member information corresponding to group a1 or can inherit the member information of group a1 and group A where group a1 is located, which is not limited in the present application, and can be set according to actual needs by those skilled in the art.

[0097] In step S408, the first candidate member information is generated according to the member information of each group member in the first management group.

[0098] In step S410, the first candidate member information is written into a static file to generate member information.

[0099] In step S412, according to the organizational structure of the target organization in the code management repository, the project role is configured for the members in the target organization in the member information, so that the members in the target organization can view and modify the member information according to the project role.

[0100] In some embodiments, a member information management project can be set under each group by the above method, and the member information management project under each group only manages (such as viewing, modifying, updating and merging, etc.) the member information under the project.

[0101] Figure 5 A member information management method is shown according to an exemplary embodiment.

[0102] Reference Figure 5 The above member information management method can include the following steps.

[0103] In some embodiments, the first management project can include a first project member and a second project member, wherein the second project member has a member information management right in the first management project.

[0104] In step S502, the second candidate member information sent by the first project member in the first management project is received.

[0105] In some embodiments, the second candidate member information sent by the first project member in the first management project (such as other member information sent by the first project member, such as chat information, modified nickname information, modified online state information and sent leave information, etc.) can be received.

[0106] In some embodiments, the first project member can be in the first management project or not in the first management project, which is not limited in the present application.

[0107] Step S504, determining, according to the project role in the member information, a second project member in the first management project who has the member information management right.

[0108] In some embodiments, as long as a member management request (such as a member information viewing request, a member information modifying request, a member information adding request, or a member information merging request, etc.) initiated in the first management project needs to be sent to the member in the first management project who has the member information management right in the code management repository.

[0109] Step S506, sending the second candidate member information to the second project member, so that the second project member audits the member information according to the second candidate member information.

[0110] Step S508, receiving the audit result.

[0111] Step S510, updating the member information according to the second candidate member information after determining that the audit is passed according to the audit result.

[0112] The technical solution provided by the above embodiments can realize, on the one hand, that a member in a target organization can perform a modifying operation (such as an updating, adding, or deleting operation) on any other member in the target organization or the member himself / herself can perform a modifying operation (such as an updating, adding, or deleting operation) on his / her own member information; on the other hand, the embodiment can utilize the code updating process of the code management repository itself to audit the member information modifying process.

[0113] Figure 6 is a member information management method according to an example embodiment.

[0114] In some embodiments, the code management repository of the target organization can include at least one management group.

[0115] Reference Figure 6 The above member information management method can include the following steps.

[0116] Step S602, creating a second management group in the code management repository of the target organization.

[0117] Step S604, creating a member information management project in the second management group.

[0118] Step S606, adding a static file in the member information management project.

[0119] Wherein, the first candidate member information is obtained from the code management repository, and the first candidate member information is written into the static file to generate the member information, including:

[0120] Step S608, obtaining the member information of the group members in each management group in the code management repository.

[0121] At step S610, first candidate member information is generated according to member information of group members in each management group in the code management repository.

[0122] At step S612, the first candidate member information is written into the static file to generate member information.

[0123] At step S614, project roles are configured for members in the target organization in the member information according to the organizational structure of the target organization in the code management repository, so that the members in the target organization view and modify the member information according to the project roles.

[0124] The above embodiment can also reconstruct a management group in the code management repository to manage the member information.

[0125] Figure 7 is a flowchart of a member information management method according to an exemplary embodiment.

[0126] In some embodiments, the member information can include both static member information of the members in the target organization in the target organization (such as name, gender, online status, project role, and other information that can be recorded in the static file through static information) and platform primary keys corresponding to application information of the members in the target organization in the third-party platform.

[0127] In some embodiments, the members in the target organization include third project members.

[0128] Referring to Figure 7 The above member information management method can include the following steps.

[0129] At step S702, a member information acquisition request sent by a third project member is received.

[0130] In some embodiments, the third project member can request to acquire member information of other members for viewing.

[0131] At step S704, if the static employee information is requested in the member information acquisition request, the static employee information value is acquired from the static file and returned to the third project member.

[0132] In some embodiments, if the member information written into the static file is requested in the member information acquisition request, the static employee information is directly acquired from the static file and returned to the third project member.

[0133] At step S706, if the dynamic employee information is requested in the member information acquisition request, the platform primary key is acquired from the static file.

[0134] Step S708, obtaining dynamic employee information from the third-party platform according to the platform primary key, so as to return to the third project member.

[0135] In some embodiments, if the dynamic information of the member in the third-party platform is requested in the member information acquisition request, the primary key of the third-party platform can be acquired to pull the relevant information from the third-party platform to return to the third project member.

[0136] The technical solutions provided by the above embodiments can not only manage the member information of the project member in the code management warehouse, but also view and manage the information of the project member in the third-party platform.

[0137] In some embodiments, company employee information can be distributed in different platforms (for example, it can be distributed in an employee system, an enterprise communication system, an enterprise learning platform, etc.), and the employee information can also have some company special information (such as responsible projects, roles, etc.) that is not in some platforms. The present application improves a simple method that can manage these information, improves the company information management efficiency, and provides a unified interface for various systems of the company.

[0138] The company employee information management method (a member information management method) improved by the present application can include the following steps:

[0139] 1. Employee information is uniformly created in a company private warehouse to maintain and configure warehouse roles of employees (department managers can give Maintainer).

[0140] 2. Static files are added in the private warehouse to store employee information, wherein the third-party platform information only stores the platform primary key. Then, employee information integration and display functions (including employee list and employee detailed information) are developed, wherein the third-party information is obtained by calling the third-party platform API according to the third-party platform primary key of the employee. After that, the employee can query all the information in this system.

[0141] 3. The update audit function directly uses the existing merge approval function of the DevOps platform, and the project roles of the department employees are pre-configured.

[0142] 4. The update information data directly uses the existing continuous integration CI function of the DevOps platform, and automatically checks the data of the initiated update request to prevent problem data from entering the employee system. If the verification is passed, the request can be merged, and after the request is merged, the CI function of the DevOps platform is used to automatically deploy online, and the online data update is automatically completed.

[0143] 5. The update history directly uses the existing commit history function of the DevOps platform, and the author, commit time, and change content are all available.

[0144] Figure 8 A member information management method is shown according to an exemplary embodiment.

[0145] The company employee information management method can specifically include Figure 8 The steps shown.

[0146] It should be understood that the following specific implementation process uses the DevOps platform GitLab as an example, and other platforms such as GitHub, Gitee are similar, only the difference in function name or usage.

[0147] Step S802, create a GitLab employee information project and configure employee permissions.

[0148] In some embodiments, a GitLab employee information project can be created in the enterprise's GitLab platform, and the employee information project can be configured with employee permissions (such as employee roles and permissions for each role).

[0149] Step S804, define and store employee information data in the project, and develop employee information integration and display functions.

[0150] Step S806, use GitLab merge approval function to complete the approval process of updating information

[0151] Step S808, use GitLab continuous integration (CI) function to verify the validity of the data, and automatically deploy the updated data online.

[0152] Step S810, use Git history and merge request functions to view employee information change history.

[0153] The creation of the GitLab employee information project and the configuration of the employee permissions can include Figure 9 The steps in the embodiment shown.

[0154] Step S902, determine whether the company has a GitLab system.

[0155] If the company does not have a GitLab system, steps S904-S905 are performed. Step S904, build a GitLab system within the company or directly use the GitLab SaaS platform. Step S906, create a company group in the GitLab system.

[0156] If the company already has a GitLab system or has created a company group in the newly created GitLab platform, step S908 is performed to create an employee information project under the company group.

[0157] Step S910, add all employees of the company (or inherit from the group) to the project member

[0158] Step S912, configure project roles, ordinary employees as Developers, and supervisors as Maintainers (useful in subsequent employee information updates).

[0159] In some embodiments, Figure 8 "Defining and storing employee information data in the project and developing employee information integration display functions" in the above Figure 10 steps in the embodiments shown.

[0160] Step S1002, open the member information project of the GitLab system.

[0161] Step S1004, add all employee information in the project, one YAML file for each employee, and the file name uses the unique identifier of the employee (such as the employee number).

[0162] Step S1006, define the employee information file format, and the third-party platform only stores foreign keys, and the company's special information stores complete information.

[0163] Step S1008, read the information file of each employee through the YAML library.

[0164] Step S1010, determine whether the information to be read is static employee information.

[0165] Step S1012, for static employee information, directly use the values in the information file.

[0166] Step S1014, for third-party platform information, the function of API connection of each platform needs to be developed first.

[0167] Step S1016, use the corresponding platform primary key in the employee information file to perform API query on all platforms to obtain the API information of all platforms.

[0168] Step S1018, develop information display functions to display the complete information of the employee.

[0169] Step S1020, in order to enhance the performance of the system, a cache function can be added to the information obtained by these APIs, and a cache refresh function is provided on the information page.

[0170] In some embodiments, Figure 8 the step "use GitLab merge approval function to complete the approval process of updating information" in the above Figure 11 steps.

[0171] Step S1102, open the member information project of the GitLab system.

[0172] Step S1104, the employee or the information maintainer changes the employee information in the project and initiates a merge request in the project.

[0173] Step S1106, the employee supervisor merges the update.

[0174] Step S1108, the employee supervisor approves the merge request of the information update.

[0175] If the approval is not passed, step S1108 is performed, the approver communicates with the requester in the GitLab system to modify and re-approve.

[0176] Step S1110, the employee supervisor merges and updates the employee information.

[0177] In some embodiments, Figure 8 The step "verify the validity of the data and automatically deploy the updated data online using the GitLab continuous integration (CI) function" in the above embodiment can include Figure 12 the steps shown in the following.

[0178] Step S1202, develop the employee information verification logic first, and add the verification Job in the GitLab CI function.

[0179] Step S1204, the employee or the information maintainer changes the employee information in the project and initiates a merge request in the project.

[0180] Step S1206, the verification Job in the GitLab CI verifies the changed data.

[0181] If the verification fails, step S1208 is performed, the initiator fixes the data problem and re-initiates the data verification.

[0182] If the verification is successful, step S1210 is performed, the supervisor approves the change and merges the update request.

[0183] Step S1212, after merging the new information, the GitLab CI automatically deploys the updated data online.

[0184] In some embodiments, Figure 8 The step "view the history of employee information changes using the Git history and merge request function" in the above embodiment can include Figure 13 the following steps in the above embodiment.

[0185] Step S1302, open the member information project of the GitLab system.

[0186] Step S1304, view the Git commit history of the project repository to obtain the record of each change of the employee information.

[0187] Step S1306, expand the specific submission information, view the corresponding merge request, and view the change background and approver in the merge request.

[0188] The above embodiment has the following key technical points: 1, the employee information is stored through the warehouse static file, and the YAML structure design; 2, the project role function of the DevOps platform is used to solve the permission problem of the employee information management; 3, the merge approval function of the DevOps platform is used to solve the approval problem of the employee information update; 4, the CI function of the DevOps platform is used to solve the data verification problem of the employee information update; 5, the Git history record and merge request function of the DevOps platform is used to solve the problem of viewing the employee information update history.

[0189] The technical scheme provided by the embodiment has the following advantages: on the one hand, the information is stored by using the Git warehouse, and the database service does not need to be introduced again; on the other hand, the project management function of the DevOps platform is used to simply and efficiently complete an employee information management project; in addition, the data is directly placed in the project warehouse, so that the project is more intuitive, clear and easy to maintain; finally, the continuous integration (CI) function of the DevOps platform is used to quickly verify the validity of the updated information and automatically deploy online, thereby improving the development efficiency of the traditional system.

[0190] Based on the same inventive concept, the member information management device is also provided in the embodiment of the disclosure, as follows. Since the principle of solving the problem of the device embodiment is similar to that of the above-mentioned method embodiment, the implementation of the device embodiment can be referred to the implementation of the above-mentioned method embodiment, and the repeated parts will not be described here.

[0191] Figure 14 is a block diagram of a member information management device according to an exemplary embodiment. Referring to Figure 14 The member information management device 1400 provided by the embodiment of the disclosure can include: a member information management project creation module 1401, an initialization member information module 1402, and a project role configuration module 1403.

[0192] The member information management project creation module 1401 can be configured to create a member information management project in a management group in a code management warehouse of a target organization; the initialization member information module 1402 can be configured to define and store member information in the member information management project according to the code management warehouse; and the project role configuration module 1403 can be configured to configure a project role for a member in the member information according to an organizational structure of the target organization in the code management warehouse, so that the member in the target organization views and modifies the member information according to the project role.

[0193] It should be noted that the member information management project creation module 1401, the initialization member information module 1402, and the project role configuration module 1403 correspond to S202-S206 in the method embodiment, and the modules and the examples and application scenarios implemented by the corresponding steps are the same, but are not limited to the content disclosed in the above method embodiment. It should be noted that the above modules as part of the device can be executed in a computer system such as a set of computer executable instructions.

[0194] In some embodiments, the initialization member information module 1402 can include a static file adding sub-module and a first candidate member information obtaining sub-module.

[0195] The static file adding sub-module can be used to add a static file in the member information management project; the first candidate member information obtaining sub-module can be used to obtain first candidate member information from the code management repository, and write the first candidate member information into the static file to generate member information.

[0196] In some embodiments, the code management repository of the target organization includes at least one management group, the at least one management group includes a first management group, the first management group includes at least one management project, and the at least one management project includes a first management project; the member information management project creation module 1401 can include a member information management project creation sub-module; and the first candidate member information obtaining sub-module can include a first management group member information obtaining unit, a first candidate member information generating unit, and a member information generating unit.

[0197] The member information management project creation sub-module can be used to create a member information management project in the first management project; the first management group member information obtaining unit can be used to obtain member information of each group member in the first management group; the first candidate member information generating unit can be used to generate first candidate member information according to the member information of each group member in the first management group; and the member information generating unit can be used to write the first candidate member information into a static file to generate member information.

[0198] In some embodiments, the first management project includes a first project member and a second project member, and the second project member has a member information management right in the first management project; the member information management device 1400 can further include a second candidate member information receiving sub-module, a second project member determining sub-module, an auditing sub-module, an auditing result obtaining sub-module, and a member information updating sub-module.

[0199] The second candidate member information receiving submodule can be configured to receive second candidate member information sent by a first project member in a first managed project; the second project member determining submodule can be configured to determine, according to a project role in the member information, a second project member who has a member information management right in the first managed project; the auditing submodule can be configured to send the second candidate member information to the second project member, so that the second project member audits the member information according to the second candidate member information; the auditing result obtaining submodule can be configured to receive an auditing result; and the member information updating submodule can be configured to update the member information according to the second candidate member information after it is determined that the auditing is passed according to the auditing result.

[0200] In some embodiments, the code management repository of the target organization includes at least one management group; the member information management project creating module 1401 can include a second management group creating submodule and a project creating submodule; and the first candidate member information obtaining submodule can include a group member information obtaining unit, a first candidate member information generating second unit, and a first candidate member information first writing unit.

[0201] The second management group creating submodule can be configured to create a second management group in the code management repository of the target organization; and the project creating submodule can be configured to create a member information management project in the second management group; the group member information obtaining unit can be configured to obtain member information of group members in each management group in the code management repository; the first candidate member information generating second unit can be configured to generate first candidate member information according to the member information of the group members in each management group in the code management repository; and the first candidate member information first writing unit can be configured to write the first candidate member information into a static file to generate the member information.

[0202] In some embodiments, the member information includes static member information of a member in the target organization in the target organization and a platform primary key corresponding to application information of the member in the target organization in a third-party platform.

[0203] In some embodiments, the member in the target organization includes a third project member; and the member information management apparatus 1400 can further include a member information obtaining request receiving module, a static information value obtaining module, a platform primary key obtaining module, and a dynamic information obtaining module.

[0204] The member information acquisition request receiving module can be configured to receive a member information acquisition request sent by a third project member; the static information value acquiring module can be configured to acquire a static employee information value from a static file and return the static employee information value to the third project member if the member information acquisition request requests static employee information; the platform primary key acquiring module can be configured to acquire a platform primary key from the static file if the member information acquisition request requests dynamic employee information; and the dynamic information acquiring module can be configured to acquire dynamic employee information from a third-party platform according to the platform primary key, so as to return the dynamic employee information to the third project member.

[0205] Since the functions of the apparatus 1400 have been described in detail in the corresponding method embodiments, the present disclosure will not be described here again.

[0206] The modules and / or sub-modules and / or units described in the embodiments of the present application can be implemented in the form of software or in the form of hardware. The described modules and / or sub-modules and / or units can also be arranged in a processor. In some cases, the names of these modules and / or sub-modules and / or units do not constitute a limitation on the modules and / or sub-modules and / or units themselves.

[0207] The flowcharts and block diagrams in the drawings illustrate the possible implementation architectures, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowcharts or block diagrams can represent a module or a part of a program segment containing one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur in different orders from those shown in the drawings. For example, two blocks that are shown in succession can actually be executed substantially in parallel, and sometimes in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams or flowcharts, and combinations of blocks in the block diagrams or flowcharts, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer program instructions.

[0208] In addition, the above-described drawings are only schematic illustrations of the processes included in the method according to the exemplary embodiments of the present disclosure, and are not for limiting purposes. It is easy to understand that the processes shown in the above-described drawings do not indicate or limit the time sequence of these processes. In addition, it is also easy to understand that these processes can be executed synchronously or asynchronously, for example, in multiple modules.

[0209] Figure 15 A structural schematic diagram of an electronic device suitable for implementing the embodiments of the present disclosure is shown. It should be noted that, Figure 15The illustrated electronic device 1500 is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments disclosed herein.

[0210] like Figure 15 As shown, the electronic device 1500 includes a central processing unit (CPU) 1501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1502 or a program loaded from a storage section 1508 into a random access memory (RAM) 1503. The RAM 1503 also stores various programs and data required for the operation of the electronic device 1500. The CPU 1501, ROM 1502, and RAM 1503 are interconnected via a bus 1504. An input / output (I / O) interface 1505 is also connected to the bus 1504.

[0211] The following components are connected to I / O interface 1505: an input section 1506 including a keyboard, mouse, etc.; an output section 1507 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1508 including a hard disk, etc.; and a communication section 1509 including a network interface card such as a LAN card, modem, etc. The communication section 1509 performs communication processing via a network such as the Internet. A drive 1510 is also connected to I / O interface 1505 as needed. Removable media 1511, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1510 as needed so that computer programs read from them can be installed into storage section 1508 as needed.

[0212] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable storage medium, the computer program containing computer program instructions for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1509, and / or installed from removable medium 1511. When the computer program is executed by central processing unit (CPU) 1501, it performs the functions defined above in the system of this application.

[0213] It should be noted that the computer-readable storage medium shown in the present disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. The computer-readable storage medium may, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device or apparatus. In the present application, the computer-readable signal medium can include a data signal carrying computer-readable computer program instructions in a baseband or as part of a carrier wave. Such a propagated data signal can take many forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer-readable signal medium can also be any computer-readable storage medium other than the computer-readable storage medium, which can send, propagate or transmit programs for use by or in conjunction with an instruction execution system, device or apparatus. The computer-readable storage medium contains computer program instructions that can be transmitted in any suitable medium, including but not limited to wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0214] As another aspect, the present application also provides a computer-readable storage medium, which can be contained in the device described in the above embodiments; or can exist independently without being assembled into the device. The above computer-readable storage medium carries one or more programs, when the one or more programs are executed by the device, the device can realize functions including: creating member information management projects in the management group of the target organization's code management repository; defining and storing member information in the member information management project according to the code management repository; configuring project roles for members in the target organization in the member information according to the organizational structure of the target organization in the code management repository, so that the members in the target organization view and modify the member information according to the project roles.

[0215] According to an aspect of the present application, a computer program product or computer program is provided, which includes computer program instructions stored in a computer readable storage medium. The computer program instructions are read from the computer readable storage medium and executed by a processor to implement the method provided in various optional implementation manners of the above-mentioned embodiments.

[0216] Through the above description of the embodiments, those skilled in the art can easily understand that the example embodiments described herein can be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solutions of the embodiments of the present disclosure can be embodied in the form of a software product. The software product can be stored in a non-volatile storage medium (which can be a CD-ROM, a U disk, a mobile hard disk, etc.), and includes a plurality of computer program instructions for causing an electronic device (which can be a server or a terminal device, etc.) to execute the method according to the embodiments of the present disclosure.

[0217] Other embodiments of the present disclosure will be readily apparent to those skilled in the art upon considering the description of the specification and practicing the present disclosure as disclosed herein. The present disclosure is intended to cover any variations, uses, or adaptations of the present disclosure following the general principles thereof and including other known or customary features and functions that are within the general purview of the present disclosure. The specification and embodiments are to be considered exemplary only, with the true scope and spirit of the present disclosure being indicated by the claims.

[0218] It should be understood that the present disclosure is not limited to the detailed structure, drawing manner or implementation method shown herein, but rather the present disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

1. A member information management method characterized by comprising: The method comprises the following steps: creating a member information management project in a management group in a code management warehouse of a target organization; defining and storing member information in the member information management project according to the code management warehouse; configuring a project role for a member in the target organization in the member information according to an organizational structure of the target organization in the code management warehouse, so that the member in the target organization views and modifies the member information according to the project role; wherein creating a member information management project in a management group in a code management warehouse of a target organization comprises: creating a second management group in the code management warehouse of the target organization; creating the member information management project in the second management group; wherein the member information management project is used for information management of members in all groups in the code management warehouse; wherein defining and storing member information in the member information management project according to the code management warehouse comprises: adding a static file in the member information management project; obtaining first candidate member information from the code management warehouse and writing the first candidate member information into the static file to generate the member information; wherein obtaining first candidate member information from the code management warehouse and writing the first candidate member information into the static file to generate the member information comprises: obtaining member information of group members in each management group in the code management warehouse; generating first candidate member information to be written into the static file according to the member information of the group members in each management group in the code management warehouse; writing the first candidate member information into the static file to define and store member information in the member information management project through the static file.

2. The method of claim 1, wherein, The code management warehouse of the target organization comprises at least one management group, and the at least one management group comprises a first management group; wherein creating a member information management project in a management group in a code management warehouse of a target organization further comprises: creating the member information management project in the first management group; wherein obtaining first candidate member information from the code management warehouse and writing the first candidate member information into the static file to generate the member information further comprises: obtaining member information of each group member in the first management group; generating the first candidate member information according to the member information of each group member in the first management group; writing the first candidate member information into the static file to generate the member information.

3. The method of claim 2, wherein, The member information management project comprises a first project member and a second project member, and the second project member has a member information management permission in the member information management project; wherein the method further comprises: receiving second candidate member information sent by the first project member in the member information management project; determining the second project member with the member information management permission in the member information management project according to the project role in the member information. sending the second candidate member information to a second project member, so that the second project member audits the member information according to the second candidate member information; receiving an audit result; updating the member information according to the second candidate member information after determining that the audit is passed according to the audit result.

4. The method of claim 1, wherein, The member information includes static member information of members in the target organization in the target organization and application information of members in the target organization in the third-party platform corresponding to the platform primary key.

5. The method of claim 4, wherein, The members in the target organization include a third project member; wherein the method further comprises: receiving a member information acquisition request sent by the third project member; if the static employee information is requested in the member information acquisition request, obtaining the static employee information value from the static file and returning it to the third project member; if the dynamic employee information is requested in the member information acquisition request, obtaining the platform primary key from the static file; obtaining the dynamic employee information from the third-party platform according to the platform primary key, so as to return it to the third project member.

6. A member information management apparatus characterized by comprising: Comprise: a member information management project creation module for creating a member information management project in a management group in a code management repository of a target organization; an initialization member information module for defining and storing member information in the member information management project according to the code management repository; a project role configuration module for configuring project roles for members in the target organization in the member information according to the organizational structure of the target organization in the code management repository, so that the members in the target organization can view and modify the member information according to the project roles; wherein creating a member information management project in a management group in a code management repository of a target organization comprises: creating a second management group in the code management repository of the target organization; creating the member information management project in the second management group; wherein the member information management project is used for information management of members in all groups in the code management repository; wherein defining and storing member information in the member information management project according to the code management repository comprises: adding a static file in the member information management project; obtaining first candidate member information from the code management repository and writing the first candidate member information into the static file to generate the member information; wherein obtaining first candidate member information from the code management repository and writing the first candidate member information into the static file to generate the member information comprises: obtaining member information of group members in each management group in the code management repository; generating first candidate member information to be written into the static file according to the member information of the group members in each management group in the code management repository; writing the first candidate member information into the static file to define and store member information in the member information management project through the static file.

7. An electronic device, comprising: Comprise: a memory; and a processor coupled to the memory, the processor being configured to perform the member information management method according to any one of claims 1-5 based on computer program instructions stored in the memory.

8. A computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the member information management method according to any one of claims 1-5.

Images