Government affair version address book processing method and device

Abstract

The invention relates to a government affair version address book processing method and device. The method comprises the following steps of: manually inputting or importing information of personnel in an address book into a user center system in batches according to a job sequence; the user center system transmits address book personnel information to the address book management background through an interface; the address book management background receives the address book personnel information and places the address book personnel information into a database personnel table orgemployee; the address book management background sequentially displays different departments according to the job sequence through the id of the affiliated mechanism and the arrangement sequence, performs one-person multi-post display through the main post and the auxiliary post, and views the authority through the role label; and the front end of the address book is connected with a government affair app or an applet in an H5 page for display. According to the method, the government affair version address book personnel are strictly displayed according to the job ranking sequence; one-person multi-post display is realized, and display is performed in a plurality of departments according to a post ranking sequence; according to the method, permissions are configured according to role labels, and personnel are associated with roles, so that flexible setting of personnel viewing permissions is realized.

Description

Technical Field

[0001] The present invention relates to the technical field of address book management methods, and in particular to a government version address book processing method and device. Background Art

[0002] The current corporate address book has the following characteristics:

[0003] 1. The personnel display in the corporate address book (such as DingTalk, Enterprise WeChat, etc.) is sorted according to the first letter of the name, usually case-sensitive (or uniformly converted to lowercase / uppercase for comparison), and arranged in alphabetical order.

[0004] 2. When dealing with main positions and secondary positions, the corporate address book only displays the main position.

[0005] 3. The permission to view the corporate address book is generally limited to viewing the address book of the department or subordinate departments, or only viewing designated departments or personnel.

[0006] However, the above-mentioned corporate address book is not suitable for use as a government address book for the following reasons:

[0007] 1. The display of personnel in the government version of the address book must be strictly in order of job ranking. Sorting by the first letter of the name does not meet government requirements.

[0008] 2. In the government version of the address book, one person may hold multiple positions, and each department is required to display them in order of position. For example, the deputy secretary of the county party committee and the county governor are displayed first in the government department, but second in the county party committee department.

[0009] 3. The permission to view the government version of the address book needs to be divided according to position and administrative level. It is necessary to view not only the personnel with low administrative levels, but also the personnel with high administrative levels. For example, a deputy county-level official can view both the township-level official and the county-level official. Summary of the invention

[0010] In order to overcome the defect that the existing enterprise address book is not suitable for use as a government version address book, the present invention proposes a new government version address book processing method and device.

[0011] The present invention improves the existing address book structure based on the characteristics of government services, and mainly includes the following designs:

[0012] (1) Based on the organization ID (org_id) and sort order (sort_no) stored in the database personnel table org_employee, the problem of displaying government employees in order of their positions is solved.

[0013] (2) Based on the department name (org_name) and the organization ID (org_id) stored in the database personnel table org_employee, the main position information of the personnel is displayed; based on the deputy department position information json (deputy_dept_position_json) field stored in the database personnel table org_employee, the deputy position department name (org_name), the organization ID (org_id) and the sorting order (sort_no) are obtained to display the deputy position information of the personnel.

[0014] (3) Based on the employee ID (emp_id) stored in the database employee table org_employee, the corresponding role ID (role_id) is queried through the associated table (cap_party_auth), thereby obtaining the corresponding viewing permission.

[0015] Specifically, the present invention provides a method for processing a government version address book, and the method comprises the following steps:

[0016] S1. Manually enter or batch import the address book personnel information into the user center system in order of job titles;

[0017] S2. The user center system transmits the address book personnel information to the address book management backend through the interface;

[0018] S3. The address book management backend receives the address book personnel information and stores it in the database personnel table org_employee;

[0019] S4-1. The address book management backend displays different departments in order of their positions based on the organization ID (department number) and the sorting order;

[0020] S4-2. The address book management backend displays multiple posts for one person through the main and deputy posts;

[0021] S4-3. Check the permissions through the role tag in the address book management backend;

[0022] S5. The address book front end is displayed using an H5 page connected to a government app or mini program.

[0023] Furthermore, the address book personnel information described in step S1 of the government version address book processing method of the present invention includes but is not limited to: user name, mobile phone number, gender, position, affiliated organization, and ranking.

[0024] Furthermore, the interface described in step S2 of the government version address book processing method of the present invention sends data in sequence through the organization id (org_id) in the array object (belongOrg) and the user's sorting (sortNum) within the current organization.

[0025] Furthermore, the interface described in step S2 of the government version of the address book processing method of the present invention sends the main position and deputy position data through the position type (jobType) in the array object (belongOrg).

[0026] Furthermore, step S3 of the government version of the address book processing method of the present invention also includes: after the address book personnel information is stored in the database, the personnel ID (emp_id) is automatically generated as a unique identifier; the personnel name (emp_name) is stored in the user name of the step S2 interface field; the mobile phone number (mobile_no) is stored in the mobile phone number of the step S2 interface field; the gender (gender) is stored in the gender of the step S2 interface field; the position (position) is stored in the position of the step S2 interface field; the department name (org_name) is stored in the organization of the step S2 interface field; the sorting order (sort_no) is stored in the sorting order of the step S2 interface field.

[0027] Furthermore, the government version address book processing method of the present invention includes step S4-1:

[0028] S4-11: Use the personnel ID (emp_id) stored in the database personnel table org_employee to check the organization ID (org_id) and sort order (sort_no) of the corresponding main post information, and store it in the database personnel organization association table (t_emp_org_deputy);

[0029] S4-12: Use the personnel ID (emp_id) stored in the database personnel table org_employee to view the deputy department position information json (deputy_dept_position_json) field, and store the deputy position's organization ID (org_id) and sort order (sort_no) into the database personnel organization association table (t_emp_org_deputy);

[0030] S4-13: Based on the personnel ID (emp_id) stored in the database personnel table org_employee, the personnel are displayed in different departments in order of their positions according to the organization ID (org_id) and sort order (sort_no) stored in the database personnel organization association table (t_emp_org_deputy).

[0031] Furthermore, the government version address book processing method of the present invention includes step S4-2:

[0032] S4-21: Use the department name (org_name) and the organization ID (org_id) stored in the database personnel table org_employee to display the main position information of the personnel;

[0033] S4-22: Use the deputy department position information json (deputy_dept_position_json) field stored in the database personnel table org_employee to obtain the deputy position department name (org_name), the affiliated organization id (org_id) and the sorting order (sort_no) to display the deputy position information of the personnel.

[0034] Furthermore, step S4-3 of the government version address book processing method of the present invention includes:

[0035] S4-31: Create a role table (cap_role) containing role tags, where the role tags include but are not limited to: county-level chief, county-level deputy, township-level chief, township-level deputy, section-level, and section-level, and assign a unique role ID (role_id) to each role tag;

[0036] S4-32: Configure viewing permissions based on the created role tags. The viewing permissions for county-level chief positions, county-level deputy positions, and township-level chief positions are county-level chief positions, county-level deputy positions, township-level chief positions, township-level deputy positions, section-level, and section-level personnel; the viewing permissions for township-level deputy positions are county-level deputy positions, township-level chief positions, township-level deputy positions, section-level, and section-level personnel; the viewing permissions for section-level and section-level personnel are township-level chief positions, township-level deputy positions, section-level, and section-level personnel;

[0037] S4-33: Add related personnel in batches according to the created role tags;

[0038] S4-34: Based on the personnel ID (emp_id) stored in the database personnel table org_employee, the corresponding role ID (role_id) is queried through the associated table (cap_party_auth), so as to view the corresponding permissions.

[0039] On the other hand, the present invention also provides a government version address book processing device, which implements the steps of the above-mentioned government version address book processing method when running.

[0040] In addition, the present invention also provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the steps of the above-mentioned government version address book processing method are implemented.

[0041] In summary, the government version address book processing method of the present invention has the following advantages:

[0042] (1) The method of the present invention realizes that the personnel in the government version of the address book are displayed strictly in the order of job ranking.

[0043] (2) The method of the present invention realizes the display of multiple positions for one person, and displays them in multiple departments in order of job ranking.

[0044] (3) The method of the present invention configures permissions according to role tags, associates personnel with roles, and realizes flexible setting of personnel viewing permissions. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the technical solution of the present invention, the following briefly introduces the drawings required for use in the description of the present invention. Obviously, the following drawings are only some embodiments recorded in the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without paying creative work.

[0046] Figure 1 A flowchart of the implementation process of a government version address book processing method provided in one embodiment of the present invention. DETAILED DESCRIPTION

[0047] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with specific embodiments. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments, and the present invention can also be implemented or applied through other different specific implementation methods. The details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention.

[0048] At the same time, it should be understood that the protection scope of the present invention is not limited to the specific embodiments described below; it should also be understood that the terms used in the embodiments of the present invention are for describing specific embodiments rather than for limiting the protection scope of the present invention.

[0049] Embodiment: A method for processing government version address book

[0050] like Figure 1 As shown, the method comprises the following steps:

[0051] Step S1: manually input or batch import the address book personnel information into the user center system;

[0052] The required fields for address book personnel information include: user name, mobile phone number, gender, position, organization, and ranking;

[0053] During the information import process, manual entry or batch import is required according to the order of positions.

[0054] Step S2: The user center system transmits the address book personnel information to the address book management backend through the interface;

[0055] The interface sends data in order through the organization ID (org_id) in the array object (belongOrg) and the user's sorting within the current organization (sortNum);

[0056] The interface sends the main position and deputy position data through the position type (jobType) in the array object (belongOrg).

[0057] Step S3: The address book management backend receives the address book personnel information and stores it in the database personnel table org_employee;

[0058] After the information is stored in the database, the personnel ID (emp_id) is automatically generated as a unique identifier; the personnel name (emp_name) is stored in the user name of the step S2 interface field; the mobile phone number (mobile_no) is stored in the mobile phone number of the step S2 interface field; the gender (gender) is stored in the gender of the step S2 interface field; the position (position) is stored in the position of the step S2 interface field; the department name (org_name) is stored in the organization of the step S2 interface field; the sorting order (sort_no) is stored in the sorting order of the step S2 interface field.

[0059] Step S4-1: The address book management backend displays different departments in order of position according to the organization ID (department number) and the sorting order. The specific steps are as follows:

[0060] S4-11: Use the personnel ID (emp_id) stored in the database personnel table org_employee to check the organization ID (org_id) and sort order (sort_no) of the corresponding main post information, and store it in the database personnel organization association table (t_emp_org_deputy);

[0061] S4-12: Use the personnel ID (emp_id) stored in the database personnel table org_employee to view the deputy department position information json (deputy_dept_position_json) field, and store the deputy position's organization ID (org_id) and sort order (sort_no) into the database personnel organization association table (t_emp_org_deputy);

[0062] S4-13: Based on the personnel ID (emp_id) stored in the database personnel table org_employee, the personnel are displayed in different departments in order of their positions according to the organization ID (org_id) and sort order (sort_no) stored in the database personnel organization association table (t_emp_org_deputy).

[0063] Step S4-2: The address book management backend displays multiple posts for one person through the main and deputy posts. The specific steps are as follows:

[0064] S4-21: Use the department name (org_name) and the organization ID (org_id) stored in the database personnel table org_employee to display the main position information of the personnel;

[0065] S4-22: Use the deputy department position information json (deputy_dept_position_json) field stored in the database personnel table org_employee to obtain the deputy position department name (org_name), the affiliated organization id (org_id) and the sorting order (sort_no) to display the deputy position information of the personnel.

[0066] Step S4-3: Check the permissions through the role tag in the address book management backend. The specific steps are as follows:

[0067] S4-31: Create a role table (cap_role) containing role tags, including: county-level chief, county-level deputy, township-level chief, township-level deputy, section-level, and section-level, and assign a unique role ID (role_id) to each role tag;

[0068] S4-32: Configure viewing permissions based on the created role tags. The viewing permissions for county-level chief positions, county-level deputy positions, and township-level chief positions are county-level chief positions, county-level deputy positions, township-level chief positions, township-level deputy positions, section-level, and section-level personnel; the viewing permissions for township-level deputy positions are county-level deputy positions, township-level chief positions, township-level deputy positions, section-level, and section-level personnel; the viewing permissions for section-level and section-level personnel are township-level chief positions, township-level deputy positions, section-level, and section-level personnel;

[0069] S4-33: Add related personnel in batches according to the created role tags;

[0070] S4-34: Based on the personnel ID (emp_id) stored in the database personnel table org_employee, the corresponding role ID (role_id) is queried through the associated table (cap_party_auth), so as to view the corresponding permissions.

[0071] Step S5: The address book front end is displayed by connecting the government app or mini program with an H5 page.

[0072] The above description is only a preferred embodiment of the present invention and does not limit the present invention in any form. Any technician familiar with the profession can make some changes or modifications to the technical contents disclosed above without departing from the scope of the technical solution of the present invention to obtain equivalent embodiments of equivalent changes. However, any simple modification, equivalent changes and modifications made to the above embodiments based on the technical essence of the present invention without departing from the content of the technical solution of the present invention should be included in the scope of protection of the claims of the present invention.

Claims

1. A government version address book processing method, characterized in that: The method comprises the following steps: S1. Manually enter or batch import the address book personnel information into the user center system in order of job titles; S2. The user center system transmits the address book personnel information to the address book management backend through the interface; S3. The address book management backend receives the address book personnel information and stores it in the database personnel table org_employee; S4-1. The address book management backend displays different departments in order of their positions based on the organization ID and sorting order; S4-2. The address book management backend displays multiple posts for one person through the main and deputy posts; S4-3. Check the permissions through the role tag in the address book management backend; S5. The address book front end is displayed using an H5 page connected to a government app or mini program.

2. The government version address book processing method according to claim 1 is characterized in that: The contact person information described in step S1 includes: user name, mobile phone number, gender, position, organization, and ranking.

3. The government version address book processing method according to claim 1 is characterized in that: The interface described in step S2 sends data in sequence according to the ID of the institution to which the user belongs and the order of the user within the current institution in the array object.

4. The government version address book processing method according to claim 1 is characterized in that: The interface described in step S2 sends the main position and deputy position data through the position type in the array object.

5. The government version address book processing method according to claim 1 is characterized in that: Step S3 also includes: after the address book personnel information is stored in the database, the personnel ID is automatically generated as a unique identifier; the personnel name is stored in the step S2 interface field user name; the mobile phone number is stored in the step S2 interface field mobile phone number; the gender is stored in the step S2 interface field gender; the position is stored in the step S2 interface field position; the department name is stored in the step S2 interface field affiliated organization; the arrangement order is stored in the step S2 interface field sort.

6. The government version address book processing method according to claim 1 is characterized in that: Step S4-1 includes: S4-11: Use the personnel ID stored in the database personnel table org_employee to check the organization ID and arrangement order of the corresponding main position information, and store it in the database personnel organization association table; S4-12: Use the personnel ID stored in the database personnel table org_employee to view the deputy department position information json field, and store the deputy position's organization ID and arrangement order into the database personnel organization association table; S4-13: Based on the personnel ID stored in the database personnel table org_employee, the personnel are displayed in different departments in order of their positions according to the organization ID and the sorting order stored in the database personnel organization association table.

7. The government version address book processing method according to claim 1 is characterized in that: Step S4-2 includes: S4-21: Use the department name and organization ID stored in the database personnel table org_employee to display the personnel's main position information; S4-22: Use the deputy department position information json field stored in the database personnel table org_employee to obtain the deputy position department name, the organization ID and the arrangement order to display the deputy position information of the personnel.

8. The government version address book processing method according to claim 1 is characterized in that: Step S4-3 includes: S4-31: Create a role table containing role tags, and assign a unique role ID to each role tag; S4-32: Configure viewing permissions based on the created role tags; S4-33: Add related personnel in batches according to the created role tags; S4-34: Based on the personnel ID stored in the database personnel table org_employee, the corresponding role ID is queried through the association table to view the corresponding permissions.

9. A government version address book processing device, characterized in that: When the device is running, the steps of the government version address book processing method described in any one of claims 1 to 8 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the steps of the government version address book processing method described in any one of claims 1 to 8 are implemented.

Images