A method and apparatus for project management

Abstract

The application provides a project management method and device, relates to the technical field of text duplication checking, and can accurately determine whether a to-be-reported project is repeatedly reported, so that resource waste caused by repeated reporting of the project is avoided. The method comprises the following steps: obtaining project information of a to-be-reported project, performing keyword extraction on the project information, obtaining a plurality of project keywords corresponding to the to-be-reported project, calculating the similarity between each project keyword and a plurality of project labels for each project keyword, taking the project label with the maximum similarity as the project label corresponding to the project keyword, and determining whether the to-be-reported project is repeatedly reported according to the similarity between each project keyword and the corresponding project label, the weight of the project label, and the project data source of a historical project corresponding to the project label. The plurality of project labels are obtained by performing keyword extraction on the project information of a plurality of historical projects, and the plurality of historical projects are obtained from a plurality of project data sources.

Description

Technical Field

[0001] This application relates to the field of text plagiarism detection technology, and in particular to a method and apparatus for project management. Background Technology

[0002] Sometimes, duplicate applications occur during the project application process. Duplicate applications negatively impact the quality and effectiveness of the results and waste time and effort. Therefore, to promptly identify duplicate applications, a technical search and analysis of the project proposal should be conducted before submission to avoid projects that have already been developed by others.

[0003] Currently, the common practice is to search patent literature databases to check if any technical points in the application project have already been applied for or published as patents, thereby determining the possibility of the application project being a duplicate. However, this method is not comprehensive enough in understanding existing research results and progress, and cannot accurately determine if the application project is a duplicate, which can easily lead to a waste of resources. Summary of the Invention

[0004] This application provides a project management method and apparatus that can accurately determine whether a project to be submitted is submitted repeatedly, thereby avoiding the waste of resources caused by repeated project submissions.

[0005] To achieve the above objectives, this application adopts the following technical solution: Firstly, this application provides a project management method, which includes: obtaining project information of a project to be submitted, and extracting keywords from the project information to obtain multiple project keywords corresponding to the project to be submitted. The project information includes one or more of the following: project name, project description information, project attribute information, and project content. The project attribute information is used to characterize the major to which the project to be submitted belongs. For each project keyword, the similarity between the project keyword and multiple project tags is calculated, and the project tag with the highest similarity is taken as the project tag corresponding to the project keyword. The multiple project tags are obtained by extracting keywords from the project information of multiple historical projects, and the multiple historical projects are obtained from multiple project data sources. Based on the similarity between each project keyword and the corresponding project tag, the weight of the project tag, and the project data source of the historical projects corresponding to the project tag, it is determined whether the project to be submitted is a duplicate submission.

[0006] Based on the method provided in the first aspect above, project information for projects to be submitted can be obtained, and keywords can be extracted from the project information to obtain multiple project keywords corresponding to the projects to be submitted. For each project keyword, the similarity between the project keyword and multiple project tags is calculated, and the project tag with the highest similarity is taken as the project tag corresponding to the project keyword. Based on the similarity between each project keyword and its corresponding project tag, the weight of the project tag, and the project data source of the historical projects corresponding to the project tag, it is determined whether the project to be submitted is a duplicate submission. Since multiple historical projects are obtained from multiple project data sources, historical projects can be obtained from different project data sources, providing a comprehensive understanding of the research results and progress of existing historical projects. This allows for accurate determination of whether the project to be submitted is a duplicate submission, thereby avoiding the waste of resources caused by duplicate project submissions and improving the success rate of project submissions.

[0007] One possible implementation involves determining whether a project to be submitted is a duplicate submission based on the similarity between each project keyword and its corresponding project tag, the weight of the project tag, and the project data source of historical projects corresponding to the project tag. This includes: determining the submission probability value of the project to be submitted based on the similarity between each project keyword and its corresponding project tag, the weight of the project tag, and the project data source of historical projects corresponding to the project tag; if the submission probability value is greater than or equal to a preset threshold, then the project to be submitted is determined to be a duplicate submission; if the submission probability value is less than the preset threshold, then the project to be submitted is determined not to be a duplicate submission.

[0008] One possible implementation involves determining the application probability value of a project based on the similarity between each project keyword and its corresponding project tag, the weight of the project tag, and the project data source of historical projects corresponding to the project tag. This includes: determining the coefficient corresponding to the project data source of historical projects corresponding to the project tag, where the project data source includes projects that have not been applied for, projects that have been applied for and approved, and projects that have been applied for but not approved; and calculating the application probability value of the project based on the similarity between each project keyword and its corresponding project tag, the weight of the project tag, and the coefficient corresponding to the project data source of historical projects corresponding to the project tag.

[0009] One possible implementation is that the probability value of the declaration satisfies a preset formula: R represents the probability of application, N is the total number of keywords, m represents the project data source, and n represents the number of keywords for multiple projects. This represents the coefficient corresponding to the project's data source. This indicates the weight of the project's tags. This indicates the similarity between each project keyword and its corresponding project tag.

[0010] One possible approach is to select a target project that matches the project tag from historical projects based on the project tags corresponding to multiple project keywords, when the target project is determined to be submitted again.

[0011] Secondly, this application provides a project management apparatus for implementing the above-mentioned method. The project management apparatus includes an acquisition module and a processing module. The acquisition module acquires project information for projects to be submitted, and extracts keywords from the project information to obtain multiple project keywords corresponding to the project to be submitted. The project information includes one or more of the following: project name, project description, project attribute information, and project content. The project attribute information characterizes the major to which the project to be submitted belongs. The processing module calculates the similarity between each project keyword and multiple project tags, and uses the project tag with the highest similarity as the project tag corresponding to the project keyword. The multiple project tags are obtained by extracting keywords from the project information of multiple historical projects, which are obtained from multiple project data sources. The processing module also determines whether the project to be submitted is a duplicate submission based on the similarity between each project keyword and its corresponding project tag, the weight of the project tag, and the project data source of the historical projects corresponding to the project tag.

[0012] Thirdly, this application provides a project management apparatus for implementing the above-described method. The project management apparatus includes modules, units, or means corresponding to the above-described method. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above-described functions.

[0013] Fourthly, this application provides a project management apparatus, the apparatus comprising: a processor; the processor being coupled to a memory, and after reading instructions from the memory, executing the method described in the first aspect above according to the instructions.

[0014] Fifthly, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the methods described in the first aspect or any possible implementation thereof.

[0015] In a sixth aspect, embodiments of this application provide a computer program product containing instructions that, when run on a computer, cause the computer to perform the methods described in the first aspect or any possible implementation thereof.

[0016] In a seventh aspect, embodiments of this application provide a chip including a processor for running computer programs or instructions to implement the methods described in the first aspect or any possible implementation thereof.

[0017] In one possible implementation, the chip provided in this application embodiment further includes a memory for storing computer programs or instructions.

[0018] The technical effects of any possible implementation of aspects two through seven can be found in the first aspect or the technical effects of different possible implementations of aspect one, and will not be repeated here. Attached Figure Description

[0019] Figure 1 A schematic diagram of the project management system provided in the embodiments of this application; Figure 2 A flowchart of a project management method provided in this application embodiment; Figure 3 A flowchart illustrating another project management method provided in this application embodiment; Figure 4 A schematic diagram of a project management device provided for an embodiment of this application; Figure 5 A schematic diagram of the hardware structure of a project management device provided for an embodiment of this application; Figure 6 This is a schematic diagram of the structure of a chip provided in an embodiment of this application. Detailed Implementation

[0020] The following describes in detail, with reference to the accompanying drawings, a project management method and apparatus provided in the embodiments of this application.

[0021] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0022] The terms "first" and "second," etc., used in the specification and drawings of this application are used to distinguish different objects or to distinguish different treatments of the same object, rather than to describe a specific order of objects.

[0023] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0024] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0025] In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0026] The method provided in this application can be used in various project management systems. The following examples illustrate this method. Figure 1 Taking the project management system 10 shown as an example, the method provided in the embodiments of this application will be described. Figure 1 This is merely an illustrative diagram and does not constitute a limitation on the applicable scenarios of the technical solutions provided in this application.

[0027] like Figure 1 The diagram shown is a schematic of the project management system 10 provided in an embodiment of this application. Figure 1 In this context, the project management system 10 may include a project management device 101 and a project management system 102.

[0028] The project management device in this embodiment, such as project management device 101, can be any device with computing, communication, and display functions. The project management device has a display interface with input functionality.

[0029] The project management system in this application embodiment, for example, project management system 102, is used to manage projects that have been declared and approved.

[0030] Figure 1 The project management system 10 shown is for illustrative purposes only and is not intended to limit the technical solutions of this application. Those skilled in the art should understand that in specific implementations, the project management system 10 may also include other devices, without limitation.

[0031] The methods provided in the embodiments of this application will be described in detail below.

[0032] like Figure 2The illustration shows a project management method provided in an embodiment of this application. The project management method includes the following steps: S201: Obtain project information for projects to be submitted, and extract keywords from the project information to obtain multiple project keywords corresponding to the projects to be submitted.

[0033] The project information includes one or more of the following: project name, project description, project attributes, and project content. The project description provides an overview of the project. Project attributes characterize the relevant field (e.g., fields may include wireless, transmission, pipeline, cloud pool, security, infrastructure, digitalization, and optimization). The project content includes the research and development content and / or expected research outcomes of the project.

[0034] The projects in this application embodiment are software development projects or technology development projects.

[0035] For example, the applicant for the project can upload project information in Excel format via an interface or enter the project information into the input interface of the project management device. The project management device receives the project information and extracts keywords from it through word segmentation to obtain multiple project keywords corresponding to the project.

[0036] Understandably, this application may determine the word segmentation method according to actual needs, without limitation. For example, the word segmentation method may be based on a language model or a neural network to segment the project information, etc.

[0037] S202: For each project keyword, calculate the similarity between the project keyword and multiple project tags, and take the project tag with the highest similarity as the project tag corresponding to the project keyword.

[0038] The similarity between project keywords and multiple project tags can be calculated using the cosine similarity method.

[0039] In this embodiment, the multiple project tags are obtained by extracting keywords from the project information of multiple historical projects. These historical projects are obtained from multiple project data sources. The project data sources include projects that have not been submitted, projects that have been submitted and approved, and projects that have been submitted but not approved.

[0040] The following describes the process by which the project management device acquires project information from multiple historical projects.

[0041] Unreported projects can be internal software development projects already launched within the enterprise (i.e., launched applications / systems). When the project data source is an unreported project, the project management system crawls data from the pages of launched applications to obtain project information for multiple historical projects. This project information includes one or more of the following: the project name, project description, project attributes, and project content. Optionally, the project information also includes the access path to the launched application. Understandably, providing the access path to the launched application facilitates viewing for applicants of projects to be reported.

[0042] Projects that have been submitted and approved can be software development projects that have already passed review and been approved by the company. When the project data source is submitted and approved projects, the project management device uses a timer to periodically collect project information from the project management system. This project information includes one or more of the following: project name, project description, project attributes, and project content. Optionally, the project information may also include the project's key performance indicators (KPIs). Understandably, KPIs represent the effectiveness of submitted and approved projects.

[0043] Projects that have been submitted but not approved can be those that failed the review. When the project data source is projects that have been submitted but not approved, the project management device obtains the project information for these projects by receiving an Excel spreadsheet uploaded by the innovation project contact person. This project information includes one or more of the following: project name, project description, project attributes, and project content. Optionally, the project information may also include the reason for the project's failure to pass the review. Understandably, providing the reason for failure allows applicants of projects awaiting approval to easily view it.

[0044] Furthermore, after acquiring project information from multiple historical projects, the project management device extracts keywords from the project information through word segmentation to obtain multiple project tags corresponding to the multiple historical projects.

[0045] Understandably, as shown in Table 1, different project tags have different scopes or different levels of differentiation, therefore, different project tags are assigned different weights. The greater the weight of a project tag, the greater the likelihood that the project management device will determine that the project content of the project to be submitted involves the R&D content represented by that project tag, if the project keyword of the project to be submitted is that project tag.

[0046] Table 1

[0047] For example, if the project tags include "inspection system" and "low carbon," with "inspection system" having a higher weight than "low carbon," then if the project keywords for the application are "inspection system" and "low carbon," the project management device will determine that the application is likely related to research and development of inspection systems. Optionally, the project management device can also determine if the application involves "low carbon" or green environmental protection and energy conservation, which can further confirm the application.

[0048] As an example, the weights of project labels can be pre-set by the project management apparatus. For instance, the pre-set weights of project labels by the project management apparatus are the average of the weights of the project labels determined by each member of the expert panel.

[0049] S203: Based on the similarity between each project keyword and its corresponding project tag, the weight of the project tag, and the project data source of the historical projects corresponding to the project tag, determine whether the project to be submitted is submitted repeatedly.

[0050] The coefficients for the historical project data sources corresponding to the project tags can be preset, and the coefficients differ for different project data sources. For example, as shown in Table 2, the coefficient for projects that have not been declared in the project data source is 0.5, the coefficient for projects that have been declared and approved is 0.6, and the coefficient for projects that have been declared but not approved is 0.4.

[0051] Table 2

[0052] One possible implementation is that the project management device determines the coefficient corresponding to the project data source of the historical project corresponding to the project tag, and calculates the application probability value of the project to be applied for based on the similarity between each project keyword and the corresponding project tag, the weight of the project tag, and the coefficient corresponding to the project data source of the historical project corresponding to the project tag.

[0053] In one example, the declaration probability value satisfies a preset formula: Where R represents the probability of application, N is the total number of keywords, and m represents the project data source. This represents the coefficient corresponding to the project's data source, where n represents the number of keywords for multiple projects. This indicates the weight of the project's tags. This indicates the similarity between each project keyword and its corresponding project tag.

[0054] One possible implementation involves the project management device determining the application probability value of a project based on the similarity between each project keyword and its corresponding project tag, the weight of the project tag, and the project data source of historical projects corresponding to the project tag. If the application probability value is greater than or equal to a preset threshold, the project management device determines that the project has been submitted repeatedly; if the application probability value is less than the preset threshold, the project management device determines that the project has not been submitted repeatedly.

[0055] The preset threshold can be set in advance according to actual needs and is not restricted. For example, the preset threshold can be 0.8.

[0056] In one example, if the probability of application is greater than or equal to a preset threshold, the project management device determines that the project to be applied for has been submitted repeatedly. In this case, the device selects a target project from its historical projects that matches the project tags corresponding to multiple project keywords. The target project is then compared with the project to be applied for to determine whether the project should be submitted. For example, the device displays the target project's information on its interface for easy viewing and reference by the applicant.

[0057] Optionally, if the probability of application is less than a preset threshold, the project management device determines that the project to be applied for has not been applied for repeatedly. If it is determined that the project to be applied for has not been applied for repeatedly, the project management device will display information such as the absence of repeated applications, the workflow for the next stage, and guidance on the relevant materials to be prepared on the display interface of the project management device.

[0058] based on Figure 2 The method described involves a project management device that acquires project information for projects to be submitted, extracts keywords from the project information to obtain multiple project keywords corresponding to the project to be submitted, calculates the similarity between each project keyword and multiple project tags for each project keyword, and uses the project tag with the highest similarity as the project tag corresponding to the project keyword. Based on the similarity between each project keyword and its corresponding project tag, the weight of the project tag, and the project data source of the historical projects corresponding to the project tag, it is determined whether the project to be submitted is a duplicate submission. Since multiple historical projects are obtained from multiple project data sources, historical projects can be obtained from different project data sources, providing a comprehensive understanding of the research results and progress of existing historical projects. This allows for accurate determination of whether the project to be submitted is a duplicate submission, thereby avoiding the waste of resources caused by duplicate project submissions and improving the success rate of project submissions.

[0059] This application embodiment can divide the project management device into functional modules or functional units according to the above method example. For example, each function can be divided into a separate functional module or functional unit, or two or more functions can be integrated into one module. The integrated module can be implemented in hardware or in software functional modules or functional units. The module or unit division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0060] like Figure 3 The diagram shown is a flowchart of another project management method provided in an embodiment of this application. Figure 3 In this process, the project management device collects and processes data from multiple historical project data sources, storing the collected and processed data in a project database. Next, the device performs word segmentation and keyword extraction on the data in the project database to obtain a project tag set. For the project to be submitted, multiple project keywords are extracted and combined with the project tags from the tag set to calculate the similarity between the submitted and the submitted projects. If the similarity is greater than or equal to a preset threshold, the duplicate information of the submitted project is displayed on the device's interface. Conversely, if the similarity is less than the threshold, the application is approved.

[0061] like Figure 4 The diagram shown is a structural schematic of a project management device 40 provided in an embodiment of this application. The device includes an acquisition module 401 and a processing module 402.

[0062] The acquisition module 401 is used to acquire project information of the project to be applied for, and to extract keywords from the project information to obtain multiple project keywords corresponding to the project to be applied for. The project information includes one or more of the following: project name, project description, project attribute information, and project content. The project attribute information is used to characterize the major to which the project to be applied belongs. For example, the acquisition module 401 is used to execute the above-mentioned S201.

[0063] Processing module 402 is used to calculate the similarity between each project keyword and multiple project tags, and to take the project tag with the highest similarity as the project tag corresponding to the project keyword. The multiple project tags are obtained by extracting keywords from the project information of multiple historical projects, which are obtained from multiple project data sources. For example, processing module 402 is used to execute the above S202.

[0064] Processing module 402 is further configured to determine whether a project to be submitted is a duplicate submission based on the similarity between each project keyword and its corresponding project tag, the weight of the project tag, and the project data source of historical projects corresponding to the project tag. For example, processing module 402 is configured to execute the above-mentioned S203.

[0065] One possible implementation is that processing module 402 is specifically used to determine the application probability value of the project to be submitted based on the similarity between each project keyword and its corresponding project tag, the weight of the project tag, and the project data source of the historical projects corresponding to the project tag. Processing module 402 is also specifically used to determine that the project to be submitted is a duplicate submission if the application probability value is greater than or equal to a preset threshold. Processing module 402 is also specifically used to determine that the project to be submitted is not a duplicate submission if the application probability value is less than the preset threshold.

[0066] One possible implementation is that the processing module 402 is further specifically used to determine the coefficients corresponding to the project data sources of historical projects corresponding to the project tags. The project data sources include projects that have not been submitted, projects that have been submitted and approved, and projects that have been submitted but not approved. The processing module 402 is also specifically used to calculate the application probability value of the project to be submitted based on the similarity between each project keyword and the corresponding project tag, the weight of the project tag, and the coefficients corresponding to the project data sources of historical projects corresponding to the project tags.

[0067] One possible implementation is that the probability value of the declaration satisfies a preset formula: R represents the probability of application, N is the total number of keywords, m is the project data source, and n is the number of keywords for multiple projects. The coefficients corresponding to the project's data source. The weight of the project tag, The similarity between each project keyword and its corresponding project tag.

[0068] In one possible implementation, the processing module 402 is further configured to, in the case of determining that the project to be declared has been declared repeatedly, select a target project that matches the project tag from the historical projects based on the project tags corresponding to multiple project keywords. The target project is used to compare with the project to be declared in order to determine whether the project to be declared should be declared.

[0069] Understandably, the aforementioned project management device can also be implemented in hardware. For example, in hardware implementation, the acquisition module 401 in this embodiment can be integrated on the communication interface, and the processing module 402 can be integrated on the processor. As another example, in hardware implementation, both the acquisition module 401 and the processing module 402 in this embodiment are integrated on the processor. The hardware structure can be as follows... Figure 5 As shown.

[0070] Figure 5 A schematic diagram of a possible hardware structure of the project management device involved in the above embodiments is shown. The project management device includes a processor 502. Optionally, the project management device may further include a communication interface 503, a memory 501, and a bus 504.

[0071] Processor 502 is used to control and manage the operation of the project management device, for example, executing the steps performed by processing module 402, and / or other processes for performing the techniques described herein. Optionally, processor 502 may also execute the steps performed by acquisition module 401. The processor 502 may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements computing functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0072] The communication interface 503 is used to support communication between the project management device and other network entities, for example, to perform the steps performed by the acquisition module 401 described above.

[0073] The memory 501 is used to store the program code and data of the cell handover device. For example, the memory 501 may be the memory in a project management device, and the memory may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as read-only memory, flash memory, hard disk or solid-state drive; the memory may also include a combination of the above types of memory.

[0074] Bus 504 can be an Extended Industry Standard Architecture (EISA) bus, etc. Bus 504 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 5 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0075] Figure 6 This is a schematic diagram of the structure of chip 60 provided in an embodiment of this application. Chip 60 includes one or more processors 601. Optionally, chip 60 also includes a communication interface 603, a bus 602, and a memory 604.

[0076] The processor 601 described above can implement or execute various exemplary logic blocks, units, and circuits described in conjunction with the disclosure of this application. The processor can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, units, and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0077] Memory 604 may include read-only memory and random access memory, and provides operation instructions and data to processor 601. A portion of memory 604 may also include non-volatile random access memory (NVRAM).

[0078] In some implementations, memory 604 stores elements such as execution modules or data structures, or subsets thereof, or extended sets thereof.

[0079] In this embodiment of the application, the corresponding operation is executed by calling the operation instructions stored in the memory 604 (which may be stored in the operating system).

[0080] The memory 604 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as read-only memory, flash memory, hard disk or solid-state drive; the memory may also include combinations of the above types of memory.

[0081] Bus 602 can be an Extended Industry Standard Architecture (EISA) bus, etc. Bus 602 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 6 The symbol is represented by only one line, but this does not mean that there is only one bus or one type of bus.

[0082] Through the above description of the embodiments, those skilled in the art will clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device, and unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0083] This application provides a computer program product containing instructions that, when run on a computer, cause the computer to execute the project management method described in the above method embodiments.

[0084] This application also provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the project management method in the method flow shown in the above method embodiments.

[0085] The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires; a portable computer disk drive; a hard disk drive; a random access memory (RAM); a read-only memory (ROM); an erasable programmable read-only memory (EPROM); a register; a hard disk drive; an optical fiber; a portable compact disc read-only memory (CD-ROM); an optical storage device; a magnetic storage device; or any suitable combination thereof; or any other form of computer-readable storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and the storage medium may reside in an application-specific integrated circuit (ASIC). In the embodiments of this application, the computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0086] Since the project management apparatus, computer-readable storage medium, and computer program product in the embodiments of this application can be applied to the above method, the technical effects that can be obtained can also be referred to the above method embodiments, and the embodiments of this application will not be repeated here.

[0087] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0088] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0089] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0090] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A project management method, characterized in that, The method includes: Obtain project information for projects to be submitted, and extract keywords from the project information to obtain multiple project keywords corresponding to the projects to be submitted. The project information includes one or more of the following: project name, project description information, project attribute information, and project content. The project attribute information is used to characterize the major to which the projects to be submitted belong. For each project keyword, the similarity between the project keyword and multiple project tags is calculated, and the project tag with the highest similarity is taken as the project tag corresponding to the project keyword. The multiple project tags are obtained by extracting keywords from the project information of multiple historical projects, and the multiple historical projects are obtained from multiple project data sources. Determine the coefficients corresponding to the project data sources of the historical projects associated with the project tags. The project data sources include projects that have not been declared, projects that have been declared and approved, and projects that have been declared but not approved. The application probability value of the project to be submitted is calculated based on the similarity between each project keyword and its corresponding project tag, the weight of the project tag, and the coefficient corresponding to the historical project data source of the project tag; the application probability value satisfies a preset formula: R represents the application probability value, N is the total number of keywords, m represents the project data source, and n represents the number of keywords for the multiple projects. This represents the coefficient corresponding to the data source of the project. This indicates the weight of the project label. This indicates the similarity between each project keyword and its corresponding project tag; If the probability value of the application is greater than or equal to a preset threshold, then it is determined that the application for the project is a duplicate application. If the probability value of the application is less than the preset threshold, it is determined that the application for the project has not been submitted repeatedly.

2. The method according to claim 1, characterized in that, The method further includes: If it is determined that the project to be submitted has been submitted repeatedly, a target project matching the project tag is selected from the historical projects based on the project tags corresponding to the multiple project keywords. The target project is used to compare with the project to be submitted in order to determine whether the project to be submitted should be submitted.

3. A project management device, characterized in that, The device includes: an acquisition module and a processing module; The acquisition module is used to acquire project information of the project to be applied for, and to extract keywords from the project information to obtain multiple project keywords corresponding to the project to be applied for. The project information includes one or more of the project name, project description information, project attribute information, and project content of the project to be applied for. The project attribute information is used to characterize the major to which the project to be applied belongs. The processing module is used to calculate the similarity between each project keyword and multiple project tags, and take the project tag with the highest similarity as the project tag corresponding to the project keyword. The multiple project tags are obtained by extracting keywords from the project information of multiple historical projects, and the multiple historical projects are obtained from multiple project data sources. The processing module is further configured to determine the coefficients corresponding to the project data sources of historical projects corresponding to the project tags, wherein the project data sources include projects that have not been declared, projects that have been declared and approved, and projects that have been declared but not approved; and to calculate the application probability value of the project to be declared based on the similarity between each project keyword and the corresponding project tag, the weight of the project tag, and the coefficients corresponding to the project data sources of historical projects corresponding to the project tags; the application probability value satisfies a preset formula: R represents the application probability value, N is the total number of keywords, m represents the project data source, and n represents the number of keywords for the multiple projects. This represents the coefficient corresponding to the data source of the project. This indicates the weight of the project label. This indicates the similarity between each project keyword and its corresponding project tag; if the application probability value is greater than or equal to a preset threshold, it is determined that the project to be applied for is a duplicate application; if the application probability value is less than the preset threshold, it is determined that the project to be applied for is not a duplicate application.

4. The apparatus according to claim 3, characterized in that, The processing module is further configured to, in the case of determining that the project to be submitted has been submitted repeatedly, select a target project from historical projects that matches the project tags corresponding to the multiple project keywords, and compare the target project with the project to be submitted to determine whether the project to be submitted should be submitted.

5. A project management device, characterized in that, include: A processor coupled to a memory for storing programs or instructions that, when executed by the processor, cause the apparatus to perform the method as described in any one of claims 1 to 2.

6. A chip, characterized in that, include: A processor coupled to a memory for storing programs or instructions that, when executed by the processor, cause the chip to perform the method as described in any one of claims 1 to 2.

7. A computer-readable storage medium storing instructions, characterized in that, When the computer executes the instruction, the computer performs the method described in any one of claims 1-2.

Images