CN116362692A - Collaborative data processing method and system suitable for administrative office OA platform - Google Patents

Collaborative data processing method and system suitable for administrative office OA platform Download PDF

Info

Publication number
CN116362692A
CN116362692A CN202310393598.4A CN202310393598A CN116362692A CN 116362692 A CN116362692 A CN 116362692A CN 202310393598 A CN202310393598 A CN 202310393598A CN 116362692 A CN116362692 A CN 116362692A
Authority
CN
China
Prior art keywords
service
item
feature
node
audit
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202310393598.4A
Other languages
Chinese (zh)
Other versions
CN116362692B (en
Inventor
包迅格
蔡晴
詹佳雯
张景明
尚天婷
朱铭达
甘文杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Information and Telecommunication Branch of State Grid Zhejiang Electric Power Co Ltd
Original Assignee
Information and Telecommunication Branch of State Grid Zhejiang Electric Power Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Information and Telecommunication Branch of State Grid Zhejiang Electric Power Co Ltd filed Critical Information and Telecommunication Branch of State Grid Zhejiang Electric Power Co Ltd
Priority to CN202310393598.4A priority Critical patent/CN116362692B/en
Publication of CN116362692A publication Critical patent/CN116362692A/en
Application granted granted Critical
Publication of CN116362692B publication Critical patent/CN116362692B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F18/00—Pattern recognition
    • G06F18/20—Analysing
    • G06F18/22—Matching criteria, e.g. proximity measures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F18/00—Pattern recognition
    • G06F18/20—Analysing
    • G06F18/24—Classification techniques
    • G06F18/241—Classification techniques relating to the classification model, e.g. parametric or non-parametric approaches
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/101—Collaborative creation, e.g. joint development of products or services
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30—Computing systems specially adapted for manufacturing

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Data Mining & Analysis (AREA)
  • Theoretical Computer Science (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Artificial Intelligence (AREA)
  • Quality & Reliability (AREA)
  • Operations Research (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Tourism & Hospitality (AREA)
  • Bioinformatics & Cheminformatics (AREA)
  • Bioinformatics & Computational Biology (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Evolutionary Biology (AREA)
  • Evolutionary Computation (AREA)
  • General Engineering & Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The invention provides a collaborative data processing method and a collaborative data processing system suitable for an administrative office OA platform, wherein the collaborative data processing method comprises the following steps: obtaining a second item closest to the first item as a reference item; the method comprises the steps that a server obtains a first reference service flow and a first reference audit flow corresponding to a reference item in a database; modifying the service node in the first reference service flow according to the project distinction to obtain a corresponding second reference service flow; adjusting the first reference audit stream corresponding to each service node according to the level adjustment interval to obtain a second reference audit stream; determining an audit node corresponding to the newly added service node according to the item level of the first feature, and generating a corresponding third reference audit stream according to the newly added audit node; the server determines cooperative terminals corresponding to the service node and the audit node based on the second reference service flow, the second reference audit flow and the third reference audit flow, and completes the first project according to the cooperative information of all the cooperative terminals.

Description

Collaborative data processing method and system suitable for administrative office OA platform
Technical Field
The invention relates to a data processing technology, in particular to a collaborative data processing method and a collaborative data processing system suitable for an administrative office OA platform.
Background
In daily work, enterprises have more project tasks, and the distribution of the project tasks is of great importance. Generally, a cooperative combination of a service flow and an audit flow is required to be completed in one project task, different projects exist according to different service requirements, and the service flow and the audit flow of different projects are different.
In the prior art, the distribution of corresponding service nodes in the service flow and corresponding auditing nodes in the auditing flow is often performed by corresponding staff, and the distribution efficiency is lower when the enterprise staff is more and the nodes are more. Therefore, how to automatically and efficiently configure the business flow and the audit flow of the project in combination with the historical data and the project requirements becomes an urgent problem to be solved.
Disclosure of Invention
The embodiment of the invention provides a collaborative data processing method and a collaborative data processing system suitable for an administrative office OA platform, which can automatically and efficiently configure business flow and audit flow of projects by combining historical data and project requirements.
In a first aspect of the embodiments of the present invention, a collaborative data processing method applicable to an office OA platform is provided, including:
the method comprises the steps that a server extracts first characteristics of an input first item, compares the first characteristics with second characteristics of historical second items to obtain second items closest to the first items as reference items, wherein the first characteristics and the second characteristics at least comprise item types and item levels;
The method comprises the steps that a server obtains a first reference service flow and a first reference audit flow corresponding to a reference item in a database, wherein the reference service flow comprises service nodes of a plurality of departments, and the reference audit flow comprises audit nodes of different levels;
the server compares the item types of the first feature and the second feature to obtain item differences, and modifies the service node in the first reference service flow according to the item differences to obtain a corresponding second reference service flow;
the server compares the item levels of the first feature and the second feature to obtain a level adjustment interval, and adjusts the first reference audit stream corresponding to each service node according to the level adjustment interval to obtain a second reference audit stream;
the server determines that the second reference service flow is compared with the newly added service node in the first reference service flow, determines an audit node corresponding to the newly added service node according to the item level of the first characteristic, and generates a corresponding third reference audit flow according to the newly added audit node;
and the server determines the cooperative terminals corresponding to the service node and the audit node based on the second reference service flow, the second reference audit flow and the third reference audit flow, and completes the first project according to the cooperative information of all the cooperative terminals.
Optionally, in a possible implementation manner of the first aspect, the server extracts a first feature of the input first item, compares the first feature with a second feature of a second historical item, and obtains a second item closest to the first item as a reference item, where the first feature and the second feature at least include an item category and an item level, and includes:
if the item types in the first feature are identical to the item types in the second feature, generating a first type tag, wherein the first type tag corresponds to a first type similarity value;
if the item types in the first feature are different from the item types in the second feature, generating a second type label, and obtaining a second type similarity value according to the item types of the first feature and the second feature;
if the item level in the first feature is the same as the item level in the second feature, generating a first level tag, wherein the first level tag corresponds to a first level similarity value;
if the item level in the first feature is different from the item level in the second feature, generating a second level label, and obtaining a second level similarity value according to the item levels of the first feature and the second feature;
And obtaining the similarity coefficients of the first item and the second item according to the first class similarity value or the second class similarity value, and taking the second item corresponding to the maximum similarity coefficient as a reference item.
Optionally, in one possible implementation manner of the first aspect, if the item category in the first feature is different from the item category in the second feature, generating a second category label, and obtaining a second category similarity value according to the item categories of the first feature and the second feature includes:
if the item types in the first feature are different from the item types in the second feature, generating a second type tag;
traversing a preset type corresponding table to determine a first service node corresponding to the item type in the first feature and determine a second service node of the second feature, wherein the preset type corresponding table is internally provided with service nodes corresponding to each item type;
determining the number of the first service nodes and the second service nodes of the same department type to obtain the same department number, and determining the number of the first service nodes and the second service nodes of different department types to obtain different department numbers;
Calculating the sum of the same department number and different department numbers to obtain a department total number, dividing the same department number by the department total number to obtain a second type similarity value, and setting the second type similarity value corresponding to the second type label.
Optionally, in one possible implementation manner of the first aspect, if the item level in the first feature is different from the item level in the second feature, generating a second level tag, and obtaining a second level similarity value according to the item levels of the first feature and the second feature includes:
if the first item level in the first feature is different from the second item level in the second feature, generating a second level label, and respectively carrying out quantization treatment on the first item level and the second item level according to a preset level corresponding table to obtain a first quantized value and a second quantized value, wherein the preset level corresponding table is internally provided with quantized values corresponding to each item level;
calculating the difference between the first quantized value and the second quantized value to obtain a quantized difference value, dividing the quantized difference value by the first quantized value to obtain a first coefficient value, and dividing a preset constant value by the first coefficient value to obtain a second level similarity value.
Optionally, in one possible implementation manner of the first aspect, the server obtains a first reference service flow and a first reference audit flow corresponding to a reference item in a database, where the reference service flow includes service nodes of multiple departments, and the reference audit flow includes audit nodes of different levels, including:
the server acquires a first reference service flow corresponding to a reference item in a database, and decomposes the first reference service flow to obtain service nodes of a plurality of departments;
and determining a first reference audit stream corresponding to the service node of each department, wherein the first reference audit stream comprises audit nodes of different levels.
Optionally, in one possible implementation manner of the first aspect, the comparing, by the server, the item types of the first feature and the second feature to obtain an item distinction, and modifying a service node in the first reference service flow according to the item distinction to obtain a corresponding second reference service flow, where the modifying includes:
traversing each second service node in turn to compare with the first service node, and determining the second service node different from the first service node as the service node to be deleted;
Traversing each first service node in turn to compare with the second service node, and determining the first service node different from the second service node as the service node to be added;
and obtaining corresponding project distinction according to the service nodes to be deleted and the service nodes to be added, and modifying the service nodes in the first reference service flow according to the project distinction to obtain a corresponding second reference service flow.
Optionally, in one possible implementation manner of the first aspect, the obtaining a corresponding project distinction according to the service node to be deleted and the service node to be added, modifying the service node in the first reference service flow according to the project distinction, and obtaining a corresponding second reference service flow includes:
classifying the service nodes according to the connection relation of the service nodes in the first reference service flow to obtain non-relay nodes and relay nodes, and determining corresponding deletion modes in the service nodes according to different types of the service nodes;
acquiring a preset category of a service node to be added, wherein the preset category comprises parallel processing nodes or non-parallel processing nodes, and if the service node is a non-parallel processing node and has a corresponding front service node, adding the service node to be added into a first reference service flow according to the category of the service node to be added;
And after the service node in the first reference service flow is modified based on project distinction, a corresponding second reference service flow is obtained.
Optionally, in one possible implementation manner of the first aspect, the classifying the service nodes according to the connection relation of the service nodes in the first reference service flow to obtain the non-relay node and the relay node, and determining the corresponding deletion manner according to different types of the service nodes to delete the non-relay node and the relay node in the service nodes includes:
if the service node in the first reference service flow is connected with the other 1 service node, the corresponding service node is divided into non-relay nodes, and if the service node in the first reference service flow is connected with the other plurality of service nodes, the corresponding service node is divided into relay nodes;
if the service node to be deleted is judged to be a non-relay node, the service node to be deleted is directly deleted from the first reference service flow;
if the service node to be deleted is judged to be the relay node, deleting the service node to be deleted from the first reference service flow, determining a plurality of other nodes connected with the service node to be deleted, and connecting the plurality of other nodes.
Optionally, in one possible implementation manner of the first aspect, the obtaining a preset category of the service node to be added, where the preset category includes a parallel processing node or a non-parallel processing node, if the service node is a non-parallel processing node, the service node to be added is added to the first reference traffic flow according to the category of the service node to be added, including:
if the type of the service node to be added is a non-parallel service node, determining a pre-service node corresponding to the non-parallel service node in a first reference service flow, and connecting the non-parallel service node with the pre-service node;
if the type of the service node to be added is a parallel processing node or the first reference service flow does not have a front service node corresponding to the service node to be added, the service node to be added is connected with a preset starting node of the first reference service flow, and each first reference service flow has a corresponding preset starting node.
Optionally, in one possible implementation manner of the first aspect, the comparing, by the server, the item levels of the first feature and the second feature to obtain a level adjustment interval, and adjusting, according to the level adjustment interval, a first reference audit stream corresponding to each service node to obtain a second reference audit stream, where the step includes:
If the item levels of the first feature and the second feature are different and the item level of the first feature is smaller than the item level of the second feature, taking the item level corresponding to the first feature as a level adjustment interval;
acquiring the level of each audit node in the first reference audit stream, deleting audit nodes which are not located in a level adjustment interval from the first reference audit stream, and obtaining an adjusted second reference audit stream;
if the item levels of the first feature and the second feature are different and the item level of the first feature is larger than the item level of the second feature, an added auditing node is obtained according to the first feature and the second feature, and the added auditing node is added in the first reference auditing flow to obtain an adjusted second reference auditing flow.
Optionally, in a possible implementation manner of the first aspect, the determining, by the server, the second reference service flow compared to the newly added service node in the first reference service flow, determining an audit node corresponding to the newly added service node according to the item level of the first feature, and generating, according to the newly added audit node, a corresponding third reference audit flow includes:
The server determines a newly added service node of the second reference service flow compared with the first reference service flow, and determines an audit node corresponding to the newly added service node according to the item level of the first characteristic;
and generating a third reference audit stream corresponding to the newly added service node according to the audit sequence of the audit node.
In a second aspect of an embodiment of the present invention, there is provided a collaborative data processing system adapted for an administrative office OA platform, comprising:
the extraction module is used for enabling the server to extract first characteristics of the input first items, comparing the first characteristics with second characteristics of second historical items to obtain second items closest to the first items as reference items, wherein the first characteristics and the second characteristics at least comprise item types and item levels;
the system comprises an acquisition module, a reference verification module and a verification module, wherein the acquisition module is used for enabling a server to acquire a first reference service flow and a first reference verification flow corresponding to a reference item in a database, the reference service flow comprises service nodes of a plurality of departments, and the reference verification flow comprises verification nodes of different levels;
the modification module is used for enabling the server to compare the item types of the first feature and the second feature to obtain item differences, and modifying the service nodes in the first reference service flow according to the item differences to obtain corresponding second reference service flow;
The adjustment module is used for enabling the server to compare the item levels of the first feature and the second feature to obtain a level adjustment interval, and adjusting the first reference audit stream corresponding to each service node according to the level adjustment interval to obtain a second reference audit stream;
the generation module is used for enabling the server to determine a newly added service node of the second reference service flow compared with the first reference service flow, determining an audit node corresponding to the newly added service node according to the item level of the first characteristic, and generating a corresponding third reference audit flow according to the newly added audit node;
and the determining module is used for enabling the server to determine the cooperative terminals corresponding to the service node and the audit node based on the second reference service flow, the second reference audit flow and the third reference audit flow, and completing the first project according to the cooperative information of all the cooperative terminals.
Drawings
FIG. 1 is a schematic flow chart of a collaborative data processing method applicable to an office OA platform according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a service node according to an embodiment of the present invention;
fig. 3 is a schematic diagram of another service node according to an embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein.
It should be understood that, in various embodiments of the present invention, the sequence number of each process does not mean that the execution sequence of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.
It should be understood that in the present invention, "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements that are expressly listed or inherent to such process, method, article, or apparatus.
It should be understood that in the present invention, "plurality" means two or more. "and/or" is merely an association relationship describing an association object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship. "comprising A, B and C", "comprising A, B, C" means that all three of A, B, C comprise, "comprising A, B or C" means that one of the three comprises A, B, C, and "comprising A, B and/or C" means that any 1 or any 2 or 3 of the three comprises A, B, C.
It should be understood that in the present invention, "B corresponding to a", "a corresponding to B", or "B corresponding to a" means that B is associated with a, from which B can be determined. Determining B from a does not mean determining B from a alone, but may also determine B from a and/or other information. The matching of A and B is that the similarity of A and B is larger than or equal to a preset threshold value.
As used herein, "if" may be interpreted as "at … …" or "at … …" or "in response to a determination" or "in response to detection" depending on the context.
The technical scheme of the invention is described in detail below by specific examples. The following embodiments may be combined with each other, and some embodiments may not be repeated for the same or similar concepts or processes.
Referring to fig. 1, a flow chart of a collaborative data processing method applicable to an administrative office OA platform according to an embodiment of the present invention includes S1-S6:
s1, a server extracts first features of an input first item, compares the first features with second features of historical second items to obtain a second item closest to the first item as a reference item, wherein the first features and the second features at least comprise item types and item levels.
In order to quickly establish the nodes of the first item, the scheme can be combined with the second item of the history for comparison and analysis.
First, the present solution extracts the item category and item level of the first item input, and it is understood that different items, item category and item level, may be different. The scheme can be used for comparing and analyzing the item types and the item levels, and finding a second item closest to the first item to serve as a reference item.
In some embodiments, S1 (the server extracts a first feature of the input first item, compares the first feature with a second feature of a second item of the history, and obtains the second item closest to the first item as a reference item, where the first feature and the second feature include at least an item category and an item level) includes S11-S15:
s11, if the item types in the first feature are identical to the item types in the second feature, generating a first type label, wherein the first type label corresponds to the first type similarity value.
If the category of items in the first feature is exactly the same as the category of items in the second feature, e.g., both the first item and the second item are for category A, a first category label is generated, wherein the first category label corresponds to the first category similarity value. It will be appreciated that the first category similarity value is greater.
And S12, if the types of the items in the first feature are different from those in the second feature, generating a second type label, and obtaining a second type similarity value according to the types of the items in the first feature and the second feature.
If the item category in the first feature is not the same as the item category in the second feature, a second category label is generated and then a second category similarity value is obtained in combination with the item categories of the first and second features, it being understood that the second category similarity value is small relative to the first category similarity value.
In some embodiments, S12 (if the item category in the first feature is different from the item category in the second feature, generating a second category label, and obtaining a second category similarity value according to the item categories of the first feature and the second feature) includes S121-S124:
s121, if the item type in the first feature is different from the item type in the second feature, generating a second type tag.
When the item type in the first feature is different from the item type in the second feature, the scheme generates a second type tag.
S122, traversing a preset category corresponding table to determine a first service node corresponding to the category of the item in the first feature and determine a second service node of the second feature, wherein the preset category corresponding table is internally provided with service nodes corresponding to each category of the item.
The scheme is provided with a preset type corresponding table, and the preset type corresponding table is provided with service nodes corresponding to each item type.
The method includes determining a first service node corresponding to a category of an item in a first feature in combination with a predetermined category correspondence table. At the same time, the second service node that the second feature has is determined on the same principle.
S123, determining the number of the first service nodes and the second service nodes of the same department type to obtain the same department number, and determining the number of the first service nodes and the second service nodes of different department types to obtain different department numbers.
It is worth mentioning that in some cases, the service nodes may be different, but their corresponding department types are the same.
Therefore, the method can determine the number of the first service nodes and the second service nodes of the same department type to obtain the same department number, and determine the number of the first service nodes and the second service nodes of different department types to obtain different department numbers.
S124, calculating the sum of the same department number and different department numbers to obtain a department total number, dividing the same department number by the department total number to obtain a second type similarity value, and setting the second type similarity value and the second type label correspondingly.
After obtaining the same number of departments and different numbers of departments, the scheme calculates the sum of the same number of departments and different numbers of departments to obtain the total number of departments, and then divides the same number of departments by the total number of departments to obtain a second type of similarity value.
It can be understood that in this embodiment, whether the departments corresponding to the nodes are the same or not is used to calculate the second type similarity value of the type dimension, and after the second type similarity value is obtained, the second type similarity value may be set corresponding to the second type label.
And S13, if the item level in the first feature is the same as the item level in the second feature, generating a first level label, wherein the first level label corresponds to the first level similarity value.
Meanwhile, the method also calculates data of the level dimension, and if the item level in the first feature is the same as the item level in the second feature, for example, the items of the level A, a first level label is generated, wherein the first level label corresponds to the first level similarity value.
And S14, if the item level in the first feature is different from the item level in the second feature, generating a second level label, and obtaining a second level similarity value according to the item levels of the first feature and the second feature.
If the item level in the first feature is different from the item level in the second feature, a second level tag is generated, and then the scheme combines the item levels of the first feature and the second feature to obtain a second level similarity value.
In some embodiments, S14 (if the item level in the first feature is different from the item level in the second feature, generating a second level tag, obtaining a second level similarity value according to the item levels of the first and second features) includes S141-S142:
S141, if the first item level in the first feature is different from the second item level in the second feature, generating a second level label, and respectively carrying out quantization processing on the first item level and the second item level according to a preset level corresponding table to obtain a first quantized value and a second quantized value, wherein the preset level corresponding table is internally provided with quantized values corresponding to each item level.
The scheme is provided with a preset level corresponding table, wherein the preset level corresponding table is provided with a quantized value corresponding to each item level.
According to the scheme, a preset level corresponding table is combined to conduct quantization processing on a first item level and a second item level respectively to obtain a first quantized value and a second quantized value, wherein the first quantized value corresponds to the first item level, and the second quantized value corresponds to the second item level.
S142, calculating the difference between the first quantized value and the second quantized value to obtain a quantized difference value, dividing the quantized difference value by the first quantized value to obtain a first coefficient value, and dividing a preset constant value by the first coefficient value to obtain a second level similarity value.
After obtaining the first quantized value and the second quantized value, the scheme calculates a difference between the first quantized value and the second quantized value to obtain a quantized difference value, and divides the quantized difference value by the first quantized value to obtain a first coefficient value.
After the first coefficient value is obtained, the scheme divides the preset constant value by the first coefficient value to obtain a second level similarity value. It will be appreciated that the larger the quantized difference, the larger the first coefficient value and the smaller the corresponding second level similarity value, indicating a lower similarity.
S15, according to the first type similarity value or the second type similarity value, the first level similarity value or the second level similarity value obtains the similarity coefficient of the first item and the second item, and the second item corresponding to the largest similarity coefficient is used as the reference item.
After obtaining a first type similarity value or a second type similarity value, and the first level similarity value or the second level similarity value, the scheme can combine the data to perform comprehensive calculation to obtain similarity coefficients of the first item and the second item, and then the second item corresponding to the largest similarity coefficient is used as a reference item. When calculating the similarity coefficient, the similarity values of the two dimensions may be directly added, or weighted summation is performed, which is not described in detail.
S2, the server acquires a first reference service flow and a first reference audit flow corresponding to a reference item in a database, wherein the reference service flow comprises service nodes of a plurality of departments, and the reference audit flow comprises audit nodes of different levels.
It can be appreciated that for an item, a corresponding service node is required to perform service, and a corresponding auditing node is required to audit after the service is finished, so that a corresponding service flow and auditing flow exist.
After determining the reference item, the scheme can acquire a first reference service flow and a first reference audit flow corresponding to the reference item in the database, wherein the reference service flow comprises service nodes of a plurality of departments, and the reference audit flow comprises audit nodes with different levels, such as a group leader level, a manager level, a director level, a president level and the like.
In some embodiments, S2 (the server obtaining a first reference service flow and a first reference audit flow corresponding to a reference item in the database, where the reference service flow includes service nodes of multiple departments, and the reference audit flow includes audit nodes of different levels) includes S21-S22:
s21, the server acquires a first reference service flow corresponding to a reference item in the database, and decomposes the first reference service flow to obtain service nodes of a plurality of departments.
The server can obtain a first reference service flow corresponding to the reference item in the database, and then decompose the first reference service flow to obtain service nodes of a plurality of departments. It will be appreciated that one or more of the service nodes may belong to the same department.
S22, determining first reference audit flows corresponding to the service nodes of each department respectively, wherein the first reference audit flows comprise audit nodes of different levels.
After obtaining the service nodes, the scheme can determine first reference audit flows corresponding to the service nodes of each department respectively, wherein the first reference audit flows comprise audit nodes of different levels. For example, service node a corresponds to audit node 1, audit node 1 is at a manager level, service node B corresponds to audit node 2, audit node 2 is at a group leader level.
And S3, the server compares the item types of the first feature and the second feature to obtain item differences, and modifies the service node in the first reference service flow according to the item differences to obtain a corresponding second reference service flow.
The project types of the first feature and the second feature are compared to obtain project differences, and then service nodes in the first reference service flow are modified by combining the project differences to obtain corresponding second reference service flow.
In some embodiments, S3 (the server compares the item types of the first feature and the second feature to obtain an item distinction, and modifies a service node in the first reference service flow according to the item distinction to obtain a corresponding second reference service flow) includes S31-S33:
S31, comparing each second service node with the first service node in sequence, and determining the second service node different from the first service node as the service node to be deleted.
Firstly, the scheme can compare each second service node with the first service node, and then find a second service node different from the first service node as the service node to be deleted. It will be appreciated that a second service node, different from the first service node, is a service node not required for the first project and therefore needs to be deleted.
S32, comparing each first service node with the second service node in sequence, and determining the first service node different from the second service node as the service node to be added.
The scheme also traverses each first service node to be compared with the second service node, and determines the first service node different from the second service node as the service node to be added. It will be appreciated that the first service node, which is different from the second service node, is the service node required for the first project and therefore requires addition.
S33, obtaining corresponding project distinction according to the service nodes to be deleted and the service nodes to be added, and modifying the service nodes in the first reference service flow according to the project distinction to obtain a corresponding second reference service flow.
The scheme can summarize the service nodes to be deleted and the service nodes to be added to obtain corresponding project differences.
After the project distinction is obtained, the scheme modifies the service node in the first reference service flow according to the project distinction to obtain a corresponding second reference service flow, and a specific modification mode is described below.
In some embodiments, S33 (obtaining a corresponding project distinction according to the service node to be deleted and the service node to be added, and modifying the service node in the first reference service flow according to the project distinction to obtain a corresponding second reference service flow) includes S331-S333:
s331, classifying the service nodes according to the connection relation of the service nodes in the first reference service flow to obtain non-relay nodes and relay nodes, and determining corresponding deleting modes according to different types of the service nodes to delete the non-relay nodes and the relay nodes in the service nodes.
After deleting the corresponding service node, the connection relationship of other service nodes may be affected, so the scheme needs to classify the service nodes, and then determine the corresponding deletion mode according to different types of the service nodes to delete in the service nodes.
Based on the conception, the scheme classifies the service nodes by combining the connection relation of the service nodes to obtain the non-relay node and the relay node.
In some embodiments, S331 (the service nodes are classified according to the connection relation of the service nodes in the first reference service flow to obtain non-relay nodes and relay nodes, and the corresponding deletion modes are determined according to the types of the service nodes and deleted in the service nodes) includes S3311-S3313:
s3311, if the service node in the first reference traffic stream is connected to another 1 service node, the corresponding service node is divided into non-relay nodes, and if the service node in the first reference traffic stream is connected to another plurality of service nodes, the corresponding service node is divided into relay nodes.
The service nodes are classified based on the number of the connection nodes, if the service node in the first reference service flow is connected with the other 1 service node, the corresponding service node is classified as a non-relay node, and if the service node in the first reference service flow is connected with the other plurality of service nodes, the corresponding service node is classified as a relay node.
For example, referring to fig. 2, the service node 3 is connected with 2 service nodes, which are relay nodes, and the service node 2 and the service node 4 are connected with only one service node, which is a non-relay node. Wherein node 1 is a preset starting node.
And S3312, if the service node to be deleted is judged to be a non-relay node, the service node to be deleted is directly deleted from the first reference service flow.
It can be understood that if the service node to be deleted is a non-relay node, it is indicated that the service node to be deleted is only connected with one node, and at this time, the service node to be deleted can be directly deleted from the first reference service flow, and at this time, the deletion does not affect the connection relationship of other service nodes.
And S3313, if the service node to be deleted is judged to be the relay node, deleting the service node to be deleted from the first reference service flow, determining a plurality of other nodes connected with the service node to be deleted, and connecting the plurality of other nodes.
If the service node to be deleted is a relay node, deleting the service node to be deleted from the first reference service flow, determining a plurality of other nodes connected with the service node to be deleted, and connecting the plurality of other nodes.
For example, after deleting service node 3, service node 4 needs to be connected to node 1.
S332, obtaining preset types of service nodes to be added, wherein the preset types comprise parallel processing nodes or non-parallel processing nodes, and if the service nodes are non-parallel processing nodes and have corresponding front service nodes, adding the service nodes to be added into the first reference service flow according to the types of the service nodes to be added.
It should be noted that in the traffic flow, there are different types of service nodes, some of which may be performed in parallel, and some of which may be in sequential relationship (not parallel), and after the last node is served, the next node may start to serve, for example, see fig. 2, and after the service node 3 is completed, the service node 4 may perform service.
Therefore, the scheme can acquire the preset types of the service nodes to be added, namely judging whether the corresponding service nodes are parallel processing nodes or non-parallel processing nodes. If the service node is a non-parallel processing node and has a corresponding pre-service node, the service node to be added is added into the first reference service flow according to the type of the service node to be added.
In some embodiments, S332 (obtaining a preset category of a service node to be added, where the preset category includes parallel processing nodes or non-parallel processing nodes, and if the service node is a non-parallel processing node, the service node has a corresponding pre-service node, and adds the service node to be added to the first reference traffic stream according to the category of the service node to be added) includes S3321-S3322:
s3321, if the type of the service node to be added is a non-parallel service node, determining a pre-service node corresponding to the service node in the first reference service flow, and connecting the non-parallel service node with the pre-service node.
For example, referring to fig. 3, the service node to be added is a non-parallel service node 5, and the front node is a service node 4, so that the non-parallel service node 5 is directly connected with the service node 4.
S3322, if the type of the service node to be added is a parallel processing node, or the first reference service flow does not have a pre-service node corresponding to the service node to be added, the service node to be added is connected with a preset starting node of the first reference service flow, and each first reference service flow has a corresponding preset starting node.
If the type of the service node to be added is a parallel processing node, or the first reference service flow does not have a pre-service node corresponding to the service node to be added, the scheme connects the service node to be added with a preset starting node of the first reference service flow, and each first reference service flow has a corresponding preset starting node.
Referring to fig. 3, the node 1 is a preset starting node, and a parallel processing node 6 may be added in the scheme and connected to the preset starting node. In the above manner, the scheme can be modified for the service node in the first reference service flow by combining project distinction.
S333, after judging that the modification of the service node in the first reference service flow is completed based on the project distinction, obtaining a corresponding second reference service flow.
After the modification of the service node in the first reference service flow is completed based on project distinction, the scheme can obtain a second reference service flow corresponding to a new project.
And S4, the server compares the item levels of the first feature and the second feature to obtain a level adjustment interval, and adjusts the first reference audit stream corresponding to each service node according to the level adjustment interval to obtain a second reference audit stream.
The project levels of the first feature and the second feature are compared to obtain a level adjustment interval, and then the first reference audit stream corresponding to each service node is adjusted by combining the level adjustment interval to obtain a second reference audit stream.
In some embodiments, S4 (the server compares the item levels of the first feature and the second feature to obtain a level adjustment interval, and adjusts the first reference audit stream corresponding to each service node according to the level adjustment interval to obtain a second reference audit stream) includes S41-S43:
and S41, if the item levels of the first feature and the second feature are different, and the item level of the first feature is smaller than the item level of the second feature, taking the item level corresponding to the first feature as a level adjustment section.
It can be understood that if the item levels of the first feature and the second feature are different, and the item level of the first feature is smaller than the item level of the second feature, the item level corresponding to the first feature is used as the level adjustment interval in the scheme.
S42, acquiring the level of each audit node in the first reference audit stream, deleting audit nodes which are not located in the level adjustment interval from the first reference audit stream, and obtaining an adjusted second reference audit stream.
After the level adjustment interval is determined, the scheme can acquire the level of each audit node in the first reference audit stream, and then delete audit nodes which are not located in the level adjustment interval from the first reference audit stream to obtain an adjusted second reference audit stream. For example, the level of each audit node in the first reference audit stream includes a group leader, a director and a manager, the level adjustment interval is from the group leader to the director, and then the audit node of the manager can be deleted from the first reference audit stream.
S43, if the item levels of the first feature and the second feature are different and the item level of the first feature is larger than the item level of the second feature, obtaining an added auditing node according to the first feature and the second feature, and adding the added auditing node in the first reference auditing flow to obtain an adjusted second reference auditing flow.
If the item levels of the first feature and the second feature are different, and the item level of the first feature is greater than the item level of the second feature, the item level of the first feature is greater, and the corresponding audit stream is more strict, at this time, an added audit node is required to be obtained according to the first feature and the second feature, for example, a general supervision node is required to be added, and then the added audit node is added in the first reference audit stream to obtain an adjusted second reference audit stream.
S5, the server determines a newly added service node of the second reference service flow compared with the first reference service flow, determines an audit node corresponding to the newly added service node according to the item level of the first characteristic, and generates a corresponding third reference audit flow according to the newly added audit node.
In some embodiments, S5 (the server determining that the second reference traffic flow is compared with the newly added service node in the first reference traffic flow, determining an audit node corresponding to the newly added service node according to the item level of the first feature, and generating a corresponding third reference audit flow according to the newly added audit node) includes S51-S52:
s51, the server determines that the second reference service flow is compared with the newly added service node in the first reference service flow, and determines an audit node corresponding to the newly added service node according to the item level of the first feature.
Firstly, the scheme can determine the newly added service node of the second reference service flow compared with the first reference service flow, and then determine the auditing node corresponding to the newly added service node by combining the item level of the first feature.
S52, generating a third reference audit stream corresponding to the newly added service node according to the audit sequence of the audit node.
After the auditing node is obtained, the scheme can generate a third reference auditing flow corresponding to the newly added service node according to the auditing sequence of the auditing node.
And S6, the server determines the cooperative terminals corresponding to the service node and the audit node based on the second reference service flow, the second reference audit flow and the third reference audit flow, and completes the first project according to the cooperative information of all the cooperative terminals.
After the second reference service flow, the second reference audit flow and the third reference audit flow are obtained, the scheme can determine the cooperative terminals corresponding to the service node and the audit node, and then the first project is completed by combining the cooperative information of all the cooperative terminals.
Referring to fig. 2, a schematic structural diagram of a collaborative data processing system applicable to an office OA platform according to an embodiment of the present invention includes:
the extraction module is used for enabling the server to extract first characteristics of the input first items, comparing the first characteristics with second characteristics of second historical items to obtain second items closest to the first items as reference items, wherein the first characteristics and the second characteristics at least comprise item types and item levels;
the system comprises an acquisition module, a reference verification module and a verification module, wherein the acquisition module is used for enabling a server to acquire a first reference service flow and a first reference verification flow corresponding to a reference item in a database, the reference service flow comprises service nodes of a plurality of departments, and the reference verification flow comprises verification nodes of different levels;
the modification module is used for enabling the server to compare the item types of the first feature and the second feature to obtain item differences, and modifying the service nodes in the first reference service flow according to the item differences to obtain corresponding second reference service flow;
the adjustment module is used for enabling the server to compare the item levels of the first feature and the second feature to obtain a level adjustment interval, and adjusting the first reference audit stream corresponding to each service node according to the level adjustment interval to obtain a second reference audit stream;
The generation module is used for enabling the server to determine a newly added service node of the second reference service flow compared with the first reference service flow, determining an audit node corresponding to the newly added service node according to the item level of the first characteristic, and generating a corresponding third reference audit flow according to the newly added audit node;
and the determining module is used for enabling the server to determine the cooperative terminals corresponding to the service node and the audit node based on the second reference service flow, the second reference audit flow and the third reference audit flow, and completing the first project according to the cooperative information of all the cooperative terminals.
The present invention also provides a storage medium having stored therein a computer program for implementing the methods provided by the various embodiments described above when executed by a processor.
The storage medium may be a computer storage medium or a communication medium. Communication media includes any medium that facilitates transfer of a computer program from one place to another. Computer storage media can be any available media that can be accessed by a general purpose or special purpose computer. For example, a storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application specific integrated circuit (Application Specific Integrated Circuits, ASIC for short). In addition, the ASIC may reside in a user device. The processor and the storage medium may reside as discrete components in a communication device. The storage medium may be read-only memory (ROM), random-access memory (RAM), CD-ROMs, magnetic tape, floppy disk, optical data storage device, etc.
The present invention also provides a program product comprising execution instructions stored in a storage medium. The at least one processor of the device may read the execution instructions from the storage medium, the execution instructions being executed by the at least one processor to cause the device to implement the methods provided by the various embodiments described above.
In the above embodiments of the terminal or the server, it should be understood that the processor may be a central processing unit (english: central Processing Unit, abbreviated as CPU), or may be other general purpose processors, digital signal processors (english: digital Signal Processor, abbreviated as DSP), application specific integrated circuits (english: application Specific Integrated Circuit, abbreviated as ASIC), or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present invention may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in a processor for execution.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the invention.

Claims (12)

1. The collaborative data processing method suitable for the administrative office OA platform is characterized by comprising the following steps of:
the method comprises the steps that a server extracts first characteristics of an input first item, compares the first characteristics with second characteristics of historical second items to obtain second items closest to the first items as reference items, wherein the first characteristics and the second characteristics at least comprise item types and item levels;
the method comprises the steps that a server obtains a first reference service flow and a first reference audit flow corresponding to a reference item in a database, wherein the reference service flow comprises service nodes of a plurality of departments, and the reference audit flow comprises audit nodes of different levels;
the server compares the item types of the first feature and the second feature to obtain item differences, and modifies the service node in the first reference service flow according to the item differences to obtain a corresponding second reference service flow;
the server compares the item levels of the first feature and the second feature to obtain a level adjustment interval, and adjusts the first reference audit stream corresponding to each service node according to the level adjustment interval to obtain a second reference audit stream;
the server determines that the second reference service flow is compared with the newly added service node in the first reference service flow, determines an audit node corresponding to the newly added service node according to the item level of the first characteristic, and generates a corresponding third reference audit flow according to the newly added audit node;
And the server determines the cooperative terminals corresponding to the service node and the audit node based on the second reference service flow, the second reference audit flow and the third reference audit flow, and completes the first project according to the cooperative information of all the cooperative terminals.
2. The collaborative data processing method for an office OA platform of claim 1,
the server extracts a first feature of the input first item, compares the first feature with a second feature of a second item of the history, and obtains a second item closest to the first item as a reference item, wherein the first feature and the second feature at least comprise item types and item levels, and the method comprises the following steps:
if the item types in the first feature are identical to the item types in the second feature, generating a first type tag, wherein the first type tag corresponds to a first type similarity value;
if the item types in the first feature are different from the item types in the second feature, generating a second type label, and obtaining a second type similarity value according to the item types of the first feature and the second feature;
if the item level in the first feature is the same as the item level in the second feature, generating a first level tag, wherein the first level tag corresponds to a first level similarity value;
If the item level in the first feature is different from the item level in the second feature, generating a second level label, and obtaining a second level similarity value according to the item levels of the first feature and the second feature;
and obtaining the similarity coefficients of the first item and the second item according to the first class similarity value or the second class similarity value, and taking the second item corresponding to the maximum similarity coefficient as a reference item.
3. The collaborative data processing method for an office OA platform of claim 2,
if the item types in the first feature are different from the item types in the second feature, generating a second type tag, and obtaining a second type similarity value according to the item types of the first feature and the second feature, including:
if the item types in the first feature are different from the item types in the second feature, generating a second type tag;
traversing a preset type corresponding table to determine a first service node corresponding to the item type in the first feature and determine a second service node of the second feature, wherein the preset type corresponding table is internally provided with service nodes corresponding to each item type;
Determining the number of the first service nodes and the second service nodes of the same department type to obtain the same department number, and determining the number of the first service nodes and the second service nodes of different department types to obtain different department numbers;
calculating the sum of the same department number and different department numbers to obtain a department total number, dividing the same department number by the department total number to obtain a second type similarity value, and setting the second type similarity value corresponding to the second type label.
4. The collaborative data processing method for an office OA platform of claim 2,
and if the item level in the first feature is different from the item level in the second feature, generating a second level label, and obtaining a second level similarity value according to the item levels of the first feature and the second feature, wherein the method comprises the following steps:
if the first item level in the first feature is different from the second item level in the second feature, generating a second level label, and respectively carrying out quantization treatment on the first item level and the second item level according to a preset level corresponding table to obtain a first quantized value and a second quantized value, wherein the preset level corresponding table is internally provided with quantized values corresponding to each item level;
Calculating the difference between the first quantized value and the second quantized value to obtain a quantized difference value, dividing the quantized difference value by the first quantized value to obtain a first coefficient value, and dividing a preset constant value by the first coefficient value to obtain a second level similarity value.
5. A collaborative data processing method for an office OA platform according to any one of claims 3 or 4,
the server obtains a first reference service flow and a first reference audit flow corresponding to a reference item in a database, wherein the reference service flow comprises service nodes of a plurality of departments, and the reference audit flow comprises audit nodes of different levels and comprises the following steps:
the server acquires a first reference service flow corresponding to a reference item in a database, and decomposes the first reference service flow to obtain service nodes of a plurality of departments;
and determining a first reference audit stream corresponding to the service node of each department, wherein the first reference audit stream comprises audit nodes of different levels.
6. The collaborative data processing method for an office OA platform of claim 5,
the server compares the item types of the first feature and the second feature to obtain item differences, and modifies the service node in the first reference service flow according to the item differences to obtain a corresponding second reference service flow, including:
Traversing each second service node in turn to compare with the first service node, and determining the second service node different from the first service node as the service node to be deleted;
traversing each first service node in turn to compare with the second service node, and determining the first service node different from the second service node as the service node to be added;
and obtaining corresponding project distinction according to the service nodes to be deleted and the service nodes to be added, and modifying the service nodes in the first reference service flow according to the project distinction to obtain a corresponding second reference service flow.
7. The collaborative data processing method for an office OA platform of claim 6,
the obtaining corresponding project distinction according to the service node to be deleted and the service node to be added, modifying the service node in the first reference service flow according to the project distinction, and obtaining a corresponding second reference service flow, including:
classifying the service nodes according to the connection relation of the service nodes in the first reference service flow to obtain non-relay nodes and relay nodes, and determining corresponding deletion modes in the service nodes according to different types of the service nodes;
Acquiring a preset category of a service node to be added, wherein the preset category comprises parallel processing nodes or non-parallel processing nodes, and if the service node is a non-parallel processing node and has a corresponding front service node, adding the service node to be added into a first reference service flow according to the category of the service node to be added;
and after the service node in the first reference service flow is modified based on project distinction, a corresponding second reference service flow is obtained.
8. The collaborative data processing method for an office OA platform of claim 7,
the step of classifying the service nodes according to the connection relation of the service nodes in the first reference service flow to obtain non-relay nodes and relay nodes, and determining corresponding deletion modes in the service nodes according to different types of the service nodes, wherein the deletion modes comprise the following steps:
if the service node in the first reference service flow is connected with the other 1 service node, the corresponding service node is divided into non-relay nodes, and if the service node in the first reference service flow is connected with the other plurality of service nodes, the corresponding service node is divided into relay nodes;
If the service node to be deleted is judged to be a non-relay node, the service node to be deleted is directly deleted from the first reference service flow;
if the service node to be deleted is judged to be the relay node, deleting the service node to be deleted from the first reference service flow, determining a plurality of other nodes connected with the service node to be deleted, and connecting the plurality of other nodes.
9. The collaborative data processing method for an office OA platform of claim 7,
the obtaining a preset category of the service node to be added, where the preset category includes parallel processing nodes or non-parallel processing nodes, and if the service node is a non-parallel processing node, the service node to be added is added to the first reference service flow according to the category of the service node to be added, where the step includes:
if the type of the service node to be added is a non-parallel service node, determining a pre-service node corresponding to the non-parallel service node in a first reference service flow, and connecting the non-parallel service node with the pre-service node;
if the type of the service node to be added is a parallel processing node or the first reference service flow does not have a front service node corresponding to the service node to be added, the service node to be added is connected with a preset starting node of the first reference service flow, and each first reference service flow has a corresponding preset starting node.
10. The collaborative data processing method for an office OA platform of claim 7,
the server compares the item levels of the first feature and the second feature to obtain a level adjustment interval, and adjusts the first reference audit stream corresponding to each service node according to the level adjustment interval to obtain a second reference audit stream, including:
if the item levels of the first feature and the second feature are different and the item level of the first feature is smaller than the item level of the second feature, taking the item level corresponding to the first feature as a level adjustment interval;
acquiring the level of each audit node in the first reference audit stream, deleting audit nodes which are not located in a level adjustment interval from the first reference audit stream, and obtaining an adjusted second reference audit stream;
if the item levels of the first feature and the second feature are different and the item level of the first feature is larger than the item level of the second feature, an added auditing node is obtained according to the first feature and the second feature, and the added auditing node is added in the first reference auditing flow to obtain an adjusted second reference auditing flow.
11. The collaborative data processing method for an office OA platform of claim 10,
the server determining a new service node of the second reference service flow compared with the first reference service flow, determining an audit node corresponding to the new service node according to the item level of the first feature, and generating a corresponding third reference audit flow according to the new audit node, including:
the server determines a newly added service node of the second reference service flow compared with the first reference service flow, and determines an audit node corresponding to the newly added service node according to the item level of the first characteristic;
and generating a third reference audit stream corresponding to the newly added service node according to the audit sequence of the audit node.
12. Collaborative data processing system suitable for administrative office OA platform, characterized in that it comprises:
the extraction module is used for enabling the server to extract first characteristics of the input first items, comparing the first characteristics with second characteristics of second historical items to obtain second items closest to the first items as reference items, wherein the first characteristics and the second characteristics at least comprise item types and item levels;
The system comprises an acquisition module, a reference verification module and a verification module, wherein the acquisition module is used for enabling a server to acquire a first reference service flow and a first reference verification flow corresponding to a reference item in a database, the reference service flow comprises service nodes of a plurality of departments, and the reference verification flow comprises verification nodes of different levels;
the modification module is used for enabling the server to compare the item types of the first feature and the second feature to obtain item differences, and modifying the service nodes in the first reference service flow according to the item differences to obtain corresponding second reference service flow;
the adjustment module is used for enabling the server to compare the item levels of the first feature and the second feature to obtain a level adjustment interval, and adjusting the first reference audit stream corresponding to each service node according to the level adjustment interval to obtain a second reference audit stream;
the generation module is used for enabling the server to determine a newly added service node of the second reference service flow compared with the first reference service flow, determining an audit node corresponding to the newly added service node according to the item level of the first characteristic, and generating a corresponding third reference audit flow according to the newly added audit node;
and the determining module is used for enabling the server to determine the cooperative terminals corresponding to the service node and the audit node based on the second reference service flow, the second reference audit flow and the third reference audit flow, and completing the first project according to the cooperative information of all the cooperative terminals.
CN202310393598.4A 2023-04-13 2023-04-13 Collaborative data processing method and system suitable for administrative office OA platform Active CN116362692B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310393598.4A CN116362692B (en) 2023-04-13 2023-04-13 Collaborative data processing method and system suitable for administrative office OA platform

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310393598.4A CN116362692B (en) 2023-04-13 2023-04-13 Collaborative data processing method and system suitable for administrative office OA platform

Publications (2)

Publication Number Publication Date
CN116362692A true CN116362692A (en) 2023-06-30
CN116362692B CN116362692B (en) 2023-09-29

Family

ID=86921690

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310393598.4A Active CN116362692B (en) 2023-04-13 2023-04-13 Collaborative data processing method and system suitable for administrative office OA platform

Country Status (1)

Country Link
CN (1) CN116362692B (en)

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080312992A1 (en) * 2007-06-14 2008-12-18 Hitachi Ltd. Automatic business process creation method using past business process resources and existing business process
US20120072227A1 (en) * 2010-09-20 2012-03-22 International Business Machines Corporation Automatically generating high quality soa design from business process maps based on specified quality goals
CN109658042A (en) * 2018-10-08 2019-04-19 平安科技（深圳）有限公司 Review method, apparatus, equipment and storage medium based on artificial intelligence
KR102180377B1 (en) * 2019-12-27 2020-11-18 주식회사 호우캐스트 Integrated work management solution system
CN111986035A (en) * 2020-08-31 2020-11-24 平安医疗健康管理股份有限公司 Medical insurance service auditing method, device, equipment and storage medium
CN113902392A (en) * 2021-09-06 2022-01-07 特赞（上海）信息科技有限公司 Creative project management method, device, terminal and storage medium
CN113987466A (en) * 2021-12-27 2022-01-28 国网浙江省电力有限公司 Information sequencing auditing method and device based on middlebox and storage medium
CN115099792A (en) * 2022-08-24 2022-09-23 中科科界(北京)科技有限公司 Method, device and equipment for auditing project declaration form and storage medium
CN115600852A (en) * 2022-09-20 2023-01-13 长沙朗源电子科技有限公司（Cn） Project allocation method, terminal and storage medium

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080312992A1 (en) * 2007-06-14 2008-12-18 Hitachi Ltd. Automatic business process creation method using past business process resources and existing business process
US20120072227A1 (en) * 2010-09-20 2012-03-22 International Business Machines Corporation Automatically generating high quality soa design from business process maps based on specified quality goals
CN109658042A (en) * 2018-10-08 2019-04-19 平安科技（深圳）有限公司 Review method, apparatus, equipment and storage medium based on artificial intelligence
KR102180377B1 (en) * 2019-12-27 2020-11-18 주식회사 호우캐스트 Integrated work management solution system
CN111986035A (en) * 2020-08-31 2020-11-24 平安医疗健康管理股份有限公司 Medical insurance service auditing method, device, equipment and storage medium
CN113902392A (en) * 2021-09-06 2022-01-07 特赞（上海）信息科技有限公司 Creative project management method, device, terminal and storage medium
CN113987466A (en) * 2021-12-27 2022-01-28 国网浙江省电力有限公司 Information sequencing auditing method and device based on middlebox and storage medium
CN115099792A (en) * 2022-08-24 2022-09-23 中科科界(北京)科技有限公司 Method, device and equipment for auditing project declaration form and storage medium
CN115600852A (en) * 2022-09-20 2023-01-13 长沙朗源电子科技有限公司（Cn） Project allocation method, terminal and storage medium

Also Published As

Publication number Publication date
CN116362692B (en) 2023-09-29

Similar Documents

Publication Publication Date Title
US20210365963A1 (en) Target customer identification method and device, electronic device and medium
US5878398A (en) Method and system for managing workflow of electronic documents
US8768914B2 (en) System and method for searching and matching databases
CN111552870A (en) Object recommendation method, electronic device and storage medium
CN111368147B (en) Graph feature processing method and device
CN110457175B (en) Service data processing method and device, electronic equipment and medium
CN111652661B (en) Mobile phone client user loss early warning processing method
CN111768242A (en) Order-placing rate prediction method, device and readable storage medium
CN112925664A (en) Target user determination method and device, electronic equipment and storage medium
CN114398315A (en) Data storage method, system, storage medium and electronic equipment
CN116362692B (en) Collaborative data processing method and system suitable for administrative office OA platform
CN116738067B (en) Vendor recommendation method and system based on big data
CN116186286A (en) International logistics information recommendation method, system and medium based on enterprise knowledge graph
CN115204841A (en) Workflow generation method and device, electronic equipment and storage medium
CN115935231A (en) Data classification method, device, equipment and storage medium
CN111737371B (en) Data flow detection classification method and device capable of dynamically predicting
CN113554438B (en) Account identification method and device, electronic equipment and computer readable medium
CN111127043A (en) Credit scoring method, credit scoring device, computer equipment and storage medium
CN116932832B (en) Data asset catalog generation method, device and computer readable storage medium
CN110895564A (en) Potential customer data processing method and device
CN112801492B (en) Knowledge-hierarchy-based data quality inspection method and device and computer equipment
CN115576732B (en) Root cause positioning method and system
CN113190590A (en) Partner grade division method and device suitable for distribution system and storage medium
US10515341B2 (en) Computer communication network for routing communications based on identified information clusters
CN112783956A (en) Information processing method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant