CN113495753A - Project label acquisition method and device, electronic equipment and storage medium - Google Patents

Abstract

The present disclosure provides a method, device, electronic device and storage medium for obtaining a label of a project, which relate to the field of data management, and in particular, to the field of project label management. The specific implementation scheme is: parsing the annotation information from the project file, wherein the project file includes at least one item, the annotation information is used to describe the label content of the project, and is pre-added in the project file; and at least one item is determined from the annotation information. The label of the project; the label of at least one project is recorded according to the preset data format. Since the project file of any computer language type project can allow adding annotation information, the above label acquisition method can label any type of project; moreover, the type of label content described by the annotation information can be unlimited, so the above The label get method can label items with various types of labels.

Description

Project label acquisition method, device, electronic device and storage medium

technical field

The present disclosure relates to the field of data management, and in particular, to the field of label management.

Background technique

Labeling some items is helpful to realize the scientific management of these items. In the prior art, the items are usually automatically tagged by using a tagging program corresponding to the item. However, the existing labeling programs have fewer types of labels, and the scope of labeling types has greater constraints; moreover, some projects of computer language types do not have corresponding labeling programs, resulting in some computer language types. Items cannot be automatically tagged.

SUMMARY OF THE INVENTION

The present disclosure provides a method, device, electronic device, and storage medium for obtaining a tag of an item.

According to an aspect of the present disclosure, there is provided a method for obtaining a tag of an item, including:

Parse the annotation information from the project file, wherein the project file includes at least one item, and the annotation information is used to describe the label content of the project and is pre-added in the project file;

determining the label of the at least one item from the annotation information;

The label of the at least one item is recorded according to a preset data format.

According to another aspect of the present disclosure, there is provided a tag acquisition device for an item, comprising:

An annotation parsing module, configured to parse out annotation information from a project file, wherein the project file includes at least one item, and the annotation information is used to describe the label content of the project and is pre-added in the project file;

A label determination module, configured to determine the label of the at least one item from the annotation information;

The label recording module is configured to record the label of the at least one item according to a preset data format. The evaluation value extraction module is used to extract the evaluation value of each evaluable event in a plurality of preset evaluable events from the historical resources produced by the resource producer, and the plurality of evaluable events at least include historical resources based on Evaluable events based on characteristics of , and evaluable events based on user feedback from historical resources;

a target evaluation value calculation module, configured to calculate the target evaluation value of the historical resource based on the evaluation value of each evaluable event in the plurality of preset evaluable events;

A resource quality determination module, configured to determine the quality level of the historical resource based on the target evaluation value.

According to another aspect of the present disclosure, there is provided an electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the above-described method for obtaining a tag of an item.

According to another aspect of the present disclosure, there is provided a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause the computer to perform the above-described method for obtaining a tag of an item.

According to another aspect of the present disclosure, there is provided a computer program product comprising a computer program that, when executed by a processor, implements the above-described method for obtaining a tag of an item.

It should be understood that what is described in this section is not intended to identify key or critical features of embodiments of the disclosure, nor is it intended to limit the scope of the disclosure. Other features of the present disclosure will become readily understood from the following description.

The beneficial effects brought by the technical solutions provided by the present disclosure are:

The solution provided by the implementation of the present disclosure allows adding annotation information for describing the label content of the project in advance in the project file. When the project needs to be labeled, the label of each project can be obtained by parsing the annotation information. Since the project file of any computer language type project can allow adding annotation information, the above-mentioned tag acquisition method can tag any type of project, so that the tag acquisition method has high universality; The type of the described tag content can be unlimited, so the above tag acquisition method can tag the item with various types of tags, which increases the tag richness of the item.

Description of drawings

The accompanying drawings are used for better understanding of the present solution, and do not constitute a limitation to the present disclosure. in:

1 shows a schematic flowchart of a method for obtaining a label of an item provided by an embodiment of the present disclosure;

FIG. 2 shows a schematic flowchart of another method for obtaining a label of an item provided by an embodiment of the present disclosure;

FIG. 3 shows a schematic diagram of partial content of a project file provided by an embodiment of the present disclosure;

FIG. 4 shows one of the schematic structural diagrams of a device for obtaining a label of an item provided by an embodiment of the present disclosure;

FIG. 5 shows the second schematic structural diagram of a device for obtaining a label of an item provided by an embodiment of the present disclosure;

6 shows a schematic block diagram of an example electronic device that may be used to implement the tag acquisition method of an embodiment item of the present disclosure.

Detailed ways

Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding and should be considered as exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted from the following description for clarity and conciseness.

Tagging some items is helpful to realize scientific management of these items. In the prior art, a tagging program corresponding to the item is usually used to automatically tag the item. However, the existing labeling programs have fewer types of labels, and the scope of labeling types has greater constraints; moreover, some projects of computer language types do not have corresponding labeling programs, resulting in some computer language types. Items cannot be automatically tagged.

Taking the project to be labeled as a test case as an example, the prior art usually uses the test framework of the test case to automatically label the test case. For example, the pytest framework of the test case of the python computer language can use @pytest.mark.* to mark the test case; the ginkgo framework of the test case of the golang computer language can mark the test case through the use case parameters. However, there are few types of tags tagged by the test framework, and the range of tag types has greater constraints. For example, some test frameworks can only tag test cases at the project level. Moreover, the test framework of some computer language type test cases does not have the ability to tag, so that this part of the computer language type test cases cannot be automatically tagged.

The method, device, electronic device, and storage medium for obtaining a tag of an item provided by the embodiments of the present disclosure are intended to solve at least one of the above technical problems in the prior art.

FIG. 1 shows a schematic flowchart of a method for obtaining a label of an item provided by an embodiment of the present disclosure. As shown in FIG. 1 , the method may mainly include the following steps:

S110: Parse out the comment information from the project file.

In this embodiment of the present disclosure, the project file may include at least one project, and the specific number of projects in the project file may be determined according to actual needs, which is not limited here. The items described in the embodiments of the present disclosure may be any objects that can be stored by a computer, such as data segments, fields, and code segments (eg, test cases) written in a computer language. The comment information may be pre-added in the project file. For example, in the process of writing the project in the project file, the related comment information may be written, and the comment information may be used to describe the label content of the project. When adding annotation information, the content of the annotation information can be written according to a preset format, so that the annotation information can be parsed from the project file according to the preset format during the parsing process.

Optionally, the annotation information in the project file may be divided into multiple levels, and the annotation information of each level is used to describe the label of the corresponding level of the project. For example, the annotation information in the project file may include at least one of directory-level annotation information, file-level annotation information, category-level annotation information, and project-level annotation information. In the embodiment of the present disclosure, multiple levels of annotation information are set, which helps to record multiple levels of tags and improves the richness of item tag types.

When parsing annotation information, at least one level of annotation information can be parsed from the project file. After parsing out at least one level of annotation information from the project file, a node tree including parent-child relationships may also be generated based on the level information of each annotation information in the at least one level of annotation information.

S120: Determine the label of at least one item from the annotation information.

As mentioned above, the annotation information in the project file can be divided into multiple levels, and the annotation information of each level is used to describe the label of the corresponding level of the project. Therefore, the label can be divided into multiple levels. For example, the label can include At least one of a directory-level tag corresponding to the directory-level annotation information, a file-level tag corresponding to the file-level annotation information, a category-level tag corresponding to the category-level annotation information, and an item-level tag corresponding to the item-level annotation information. The embodiment of the present disclosure sets tags of various levels, which can improve the richness of tag types of an item. When the label is determined in the determination of the annotation information, the label of at least one level of at least one item may be parsed from the annotation information of at least one level.

S130: Record the label of at least one item according to a preset data format.

In the embodiment of the present disclosure, the preset data format may be any data storage form, for example, the label of at least one item may be recorded in the form of a node tree, or the label of at least one item may be recorded in the form of a table. In the embodiment of the present disclosure, the label of at least one item may be recorded in the form of a node tree, so as to clearly represent the hierarchical relationship between the labels of the project. It will be appreciated that after the tags of the items are recorded, the tags may be stored in the preset library.

Optionally, when labeling an item, the node corresponding to each label in the node tree can be determined according to the annotation information corresponding to each label in the labels of at least one level; each label is bound to the corresponding node in the node tree. on the node.

In the embodiment of the present disclosure, after the label of at least one item is recorded according to the preset data format, the target label selected by the user may also be determined in response to the user's label selection operation; the label of the at least one item is recorded based on the preset data format , to determine at least one target item with a target tag.

The present disclosure implements a method for obtaining a label of an item, which allows to add annotation information for describing the content of the label of the project in the project file in advance, and when the project needs to be tagged, the label of each item can be obtained by parsing the annotation information. . Since the project file of any computer language type project can allow adding annotation information, the above-mentioned tag acquisition method can tag any type of project, so that the tag acquisition method has high universality; The type of the described tag content can be unlimited, so the above tag acquisition method can tag the item with various types of tags, which increases the tag richness of the item.

FIG. 2 shows a schematic flowchart of a method for obtaining a label of an item provided by an embodiment of the present disclosure. As shown in FIG. 2 , the method may mainly include the following steps:

S210: Parse out at least one level of annotation information from the project file.

As mentioned above, the annotation information in the project file can be divided into multiple levels, and the annotation information of each level is used to describe the label of the corresponding level of the project. For example, the annotation information in the project file may include at least one of directory-level annotation information, file-level annotation information, category-level annotation information, and project-level annotation information.

Optionally, the directory-level comment information can describe the label content related to the level of the directory where the project file is located, the file-level comment information can describe the label content related to the project file level, and the category-level comment information can describe the category to which the project belongs. The label content related to this level, and the item-level annotation information can describe the label content related to this level of the project.

FIG. 3 shows a schematic diagram of part of the content of a project file provided by an embodiment of the present disclosure. As shown in FIG. 3 , the content of box A is file-level annotation information, the content of box B is category-level annotation information, and the content of box B is category-level annotation information. The content of C and the content of box D are respectively two item-level annotation information, and the content corresponding to the print in Figure 3 is the item. It can be understood that a project file does not necessarily contain all levels of comment information. For example, the project file shown in FIG. 3 does not belong to any directory, so the project file may not contain directory-level comment letters.

S220: Based on the level information of each annotation information in the annotation information of at least one level, generate a node tree including a parent-child relationship.

In the embodiment of the present disclosure, annotation information of different levels corresponds to nodes of different levels in the node tree, wherein the annotation information with the highest level corresponds to the root node in the node tree, and the annotation information with the lowest level corresponds to the nodes in the node tree. leaf node. Optionally, the levels of the above directory-level annotation information, file-level annotation information, category-level annotation information, and item-level annotation information are sequentially decreased. Generally speaking, the item-level annotation information corresponds to a leaf node in the node tree.

Assume that directory-level comment information, file-level comment information, category-level comment information, and project-level comment information are parsed from a project file. Here, the directory-level comment information corresponds to the root node in the node tree, and the file-level comment information corresponds to the node. The second-level node at the next level of the root node in the tree, the category-level annotation information corresponds to the third-level node at the next level of the second-level node in the node tree, and the item-level annotation information corresponds to the leaf node in the node tree. According to the above The corresponding relationship between annotation information and nodes generates a node tree containing parent-child relationships.

S230: From the annotation information of at least one level, parse out at least one level label of at least one item.

As mentioned above, the annotation information in the project file can be divided into multiple levels, and the annotation information of each level is used to describe the label of the corresponding level of the project. Therefore, the label can be divided into multiple levels. For example, the label can include At least one of a directory-level tag corresponding to the directory-level annotation information, a file-level tag corresponding to the file-level annotation information, a category-level tag corresponding to the category-level annotation information, and an item-level tag corresponding to the item-level annotation information.

Optionally, in this embodiment of the present disclosure, a corresponding tag may be matched according to certain matching rules (such as complete matching and upgrade matching) annotation information, and the content of the tag may be divided into enumeration content and text content. Optionally, the enumeration content needs to be in a preset value list, and the tag value of the text content can be any data.

It should be noted here that, from an annotation information, at least one label at the same level can be parsed. Taking Fig. 3 as an example, the item to be labeled in Fig. 3 is a test case, and the file-level label parsed from the file-level comment information may include: the file name label "a certain function test set", the file function label "is a certain Function test, including adding, deleting, modifying, and checking tests"; the category-level tags parsed from category-level annotation information can include: category name tag "use case set 1"; parsed from the first item-level annotation information The project-level annotation labels can include: use case name label "create", test type label "single test", priority label "p1"; project-level annotation labels parsed from the second project-level annotation information can include: use case Name label "test_update", test type label "single test", priority label "p0"; execution method label "auto".

S240: Determine the node corresponding to each label in the node tree according to the annotation information corresponding to each label in the labels of at least one level.

It can be understood that the node in the node tree corresponding to each label is consistent with the node of the annotation information to which the label belongs. Assume that directory-level comment information, file-level comment information, category-level comment information, and project-level comment information are parsed from a project file. Here, the directory-level comment information corresponds to the root node in the node tree, and the directory-level comment information is parsed out. The directory-level label also corresponds to the root node; the file-level annotation information corresponds to the second-level node below the root node in the node tree, and the file-level label parsed from the file-level annotation information also corresponds to the second-level node; The category-level annotation information corresponds to the third-level node next to the second-level node in the node tree, and the category-level label parsed from the category-level annotation information also corresponds to the third-level node; the item-level annotation information corresponds to the node A leaf node in the tree, and the item-level label parsed from the item-level annotation information also corresponds to the leaf node.

S250: Bind each label to the corresponding node in the node tree.

For example, for a directory-level label corresponding to the root node in the node tree, the directory-level label can be bound to the root node in the node tree, and the binding methods of other labels are not described here. It can be understood that after the label binding is completed, the node tree and each label can be stored in the database. Optionally, the unique identifier of the project file may be stored in the database in association with the node tree, and the unique identifier of each node in the node tree may be stored in the database in association with the corresponding label.

In the disclosed embodiment, after each label is bound to the corresponding node in the node tree, the project label can be queried based on the obtained label, and the project label can be queried based on the label to reasonably manage the project, such as Items are classified, filtered and filtered, for example, some items are accurately filtered out by a certain target tag, and then all items with the target tag are executed. Optionally, to query the specific process based on the tag, refer to step S260.

S260: In response to the user's tag selection operation, determine the target tag selected by the user; and determine at least one target item with the target tag based on the tag of the at least one item recorded in the preset data format.

In the embodiment of the present disclosure, the user can select at least one target tag as required, then determine all target items with the at least one target tag based on the node tree and each tag stored in the database, and call these targets in the project file. project and show it.

In the embodiment of the present disclosure, a virtual executor may be pre-built to execute the corresponding steps in the method for obtaining the label of the above item. For example, the file dispatcher, annotation parser, and tag parser can be pre-generated.

Optionally, the file type of the project file is determined by a file distributor, and the project file is sent to an annotation parser corresponding to the file type, and then the annotation information is parsed from the project file by using the annotation parser.

Here, different annotation parsers can be set according to different file types. The file type is the computer language type of the project in the project file. When building the annotation parser, you can first define the word segmentation information of each type of computer language, and then use the word segmentation information of each type of computer language to write the corresponding annotation parsing device. Using an annotation parser matching the file type of the project file to parse the annotation information can improve the accuracy of the parsed annotation information.

The comment parser is compatible with all keywords and grammars of the corresponding type of computer language. Optionally, Antlr4 can be used to generate the corresponding accessor according to the written code parser. The accessor can traverse and parse the project file and parse out the comment information. . Here, for a specific description of parsing the annotation information, reference may be made to the corresponding description in the above steps, and details are not repeated here.

After the annotation information is parsed from the project file by using the annotation parser, the label of at least one project can be determined from the annotation information by using the label parser, and the label of the at least one project can be recorded according to a preset data format. Here, for the specific description of determining the label of the item from the annotation information and recording the label, reference may be made to the corresponding description in the above steps, which will not be repeated here.

A project targeted by the method for obtaining a project label provided by the embodiment of the present disclosure is a project file including at least one project. In actual situations, some project files do not contain projects, and there is no project-level annotation information in the project files, but only directory-level labels and/or file-level annotation information. The project's label acquisition method parses the project file, but the parsed label cannot be used as the label of a certain project.

Based on the same principle as the above-mentioned method for obtaining a label of an item, FIG. 4 shows one of the schematic structural diagrams of a device for obtaining a label of an item provided by an embodiment of the present disclosure, and FIG. 5 shows a schematic diagram of a device provided by an embodiment of the present disclosure The second schematic diagram of the structure of the label acquisition device of the project. As shown in FIG. 4 , the device 400 for obtaining a tag of an item includes an annotation parsing module 410 , a tag determining module 420 and a tag recording module 430 .

The annotation parsing module 410 is configured to parse out annotation information from the project file, wherein the project file includes at least one item, and the annotation information is used to describe the label content of the project and is pre-added in the project file.

The tag determination module 420 is used to determine the tag of at least one item from the annotation information.

The tag recording module 430 is configured to record the tag of at least one item according to a preset data format.

The device for obtaining a label of a project provided by the implementation of the present disclosure allows to add comment information for describing the label content of the project in the project file in advance, and when the project needs to be labeled, the label of each project can be obtained by parsing the comment information . Since the project file of any computer language type project can allow adding annotation information, the above-mentioned tag acquisition method can tag any type of project, so that the tag acquisition method has high universality; The type of the described tag content can be unlimited, so the above tag acquisition method can tag the item with various types of tags, which increases the tag richness of the item.

In this embodiment of the present disclosure, when the annotation parsing module 410 is used to parse out the annotation information from the project file, it is specifically configured to: parse out at least one level of annotation information from the project file, wherein the at least one level of annotation information includes At least one of directory-level annotation information, file-level annotation information, category-level annotation information, and item-level annotation information, each level of annotation information is used to describe the label of the corresponding level of the project.

In the embodiment of the present disclosure, the annotation parsing module 410 is further configured to: generate a node tree including a parent-child relationship based on the level information of each annotation information in the at least one level of annotation information.

In this embodiment of the present disclosure, when the label determination module 420 is used to determine the label of at least one item from the annotation information, it is specifically configured to: parse out at least one level of at least one item from the at least one level of annotation information. Labels; wherein, the labels of at least one level include directory-level labels corresponding to directory-level annotation information, file-level labels corresponding to file-level annotation information, category-level labels corresponding to category-level annotation information, and item-level labels corresponding to item-level annotation information. at least one of.

In the embodiment of the present disclosure, when the tag recording module 430 is used to record the tag of at least one item according to the preset data format, it is specifically used for:

According to the annotation information corresponding to each label in the labels of at least one level, determine the node corresponding to each label in the node tree;

Bind each label to the corresponding node in the node tree.

In the embodiment of the present disclosure, when the annotation parsing module 410 is used to parse out the annotation information from the project file, it is specifically used to:

Use the file distributor to determine the file type of the project file, and send the project file to the annotation parser corresponding to the file type;

Use the annotation parser to parse the annotation information from the project file.

In the embodiment of the present disclosure, as shown in FIG. 5 , the device 400 for obtaining a label of an item further includes an item query module 440, and the item query module 440 is used for:

In response to the user's tag selection operation, determining the target tag selected by the user;

At least one target item having a target tag is determined based on the tag of the at least one item recorded in the preset data format.

It can be understood that the above-mentioned modules of the device for obtaining a label of an item in the embodiment of the present disclosure have the function of implementing the corresponding steps of the above-mentioned method for obtaining a label of an item. This function can be implemented by hardware or by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions. The above-mentioned modules may be software and/or hardware, and the above-mentioned modules may be implemented independently, or multiple modules may be integrated and implemented. For the functional description of each module of the label obtaining apparatus of the above item, reference may be made to the corresponding description of the above-mentioned project label obtaining method, which will not be repeated here.

It should be noted here that, in the technical solution of the present disclosure, the acquisition, storage and application of the user's personal information involved all comply with the relevant laws and regulations, and do not violate public order and good customs.

According to embodiments of the present disclosure, the present disclosure also provides an electronic device, a readable storage medium, and a computer program product.

6 shows a schematic block diagram of an example electronic device that may be used to implement the tag acquisition method of an embodiment item of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. Electronic devices may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are by way of example only, and are not intended to limit implementations of the disclosure described and/or claimed herein.

As shown in FIG. 6 , the device 500 includes a computing unit 501 that can be executed according to a computer program stored in a read only memory (ROM) 502 or loaded into a random access memory (RAM) 503 from a storage unit 508 Various appropriate actions and handling. In the RAM 503, various programs and data necessary for the operation of the device 500 can also be stored. The computing unit 501 , the ROM 502 , and the RAM 503 are connected to each other through a bus 504 . An input/output (I/O) interface 505 is also connected to bus 504 .

Various components in the device 500 are connected to the I/O interface 505, including: an input unit 506, such as a keyboard, mouse, etc.; an output unit 507, such as various types of displays, speakers, etc.; a storage unit 508, such as a magnetic disk, an optical disk, etc. ; and a communication unit 509, such as a network card, a modem, a wireless communication transceiver, and the like. The communication unit 509 allows the device 500 to exchange information/data with other devices through a computer network such as the Internet and/or various telecommunication networks.

Computing unit 501 may be various general-purpose and/or special-purpose processing components with processing and computing capabilities. Some examples of computing units 501 include, but are not limited to, central processing units (CPUs), graphics processing units (GPUs), various specialized artificial intelligence (AI) computing chips, various computing units that run machine learning model algorithms, digital signal processing processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 501 executes the various methods and processes described above, such as a tag acquisition method of an item. For example, in some embodiments, the tag acquisition method for an item may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 508 . In some embodiments, part or all of the computer program may be loaded and/or installed on device 500 via ROM 502 and/or communication unit 509 . When the computer program is loaded into the RAM 503 and executed by the computing unit 501, one or more steps of the tag acquisition method of the item described above may be performed. Alternatively, in other embodiments, the computing unit 501 may be configured by any other suitable means (eg, by means of firmware) to perform the item's tag acquisition method.

Various implementations of the systems and techniques described herein above may be implemented in digital electronic circuitry, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips system (SOC), load programmable logic device (CPLD), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include being implemented in one or more computer programs executable and/or interpretable on a programmable system including at least one programmable processor that The processor, which may be a special purpose or general-purpose programmable processor, may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device an output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming computer languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, performs the functions/functions specified in the flowcharts and/or block diagrams. Action is implemented. The program code may execute entirely on the machine, partly on the machine, partly on the machine and partly on a remote machine as a stand-alone software package or entirely on the remote machine or server.

In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in connection with the instruction execution system, apparatus or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media would include one or more wire-based electrical connections, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), fiber optics, compact disk read only memory (CD-ROM), optical storage, magnetic storage, or any suitable combination of the foregoing.

To provide interaction with a user, the systems and techniques described herein may be implemented on a computer having a display device (eg, a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user ); and a keyboard and pointing device (eg, a mouse or trackball) through which a user can provide input to the computer. Other kinds of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (eg, visual feedback, auditory feedback, or tactile feedback); and can be in any form (including acoustic input, voice input, or tactile input) to receive input from the user.

The systems and techniques described herein may be implemented on a computing system that includes back-end components (eg, as a data server), or a computing system that includes middleware components (eg, an application server), or a computing system that includes front-end components (eg, a user's computer having a graphical user interface or web browser through which a user may interact with implementations of the systems and techniques described herein), or including such backend components, middleware components, Or any combination of front-end components in a computing system. The components of the system may be interconnected by any form or medium of digital data communication (eg, a communication network). Examples of communication networks include: Local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

A computer system can include clients and servers. Clients and servers are generally remote from each other and usually interact through a communication network. The relationship of client and server arises by computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, a distributed system server, or a server combined with blockchain.

It should be understood that steps may be reordered, added or deleted using the various forms of flow shown above. For example, the steps described in the present disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved, no limitation is imposed herein.

The above-mentioned specific embodiments do not constitute a limitation on the protection scope of the present disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent replacements, and improvements made within the spirit and principles of the present disclosure should be included within the protection scope of the present disclosure.

Claims (17)

1. A method for acquiring a label of an item comprises the following steps:

parsing annotation information from a project file, wherein the project file comprises at least one project, and the annotation information is used for describing tag content of the project and is pre-added in the project file;

determining a tag of the at least one item from the annotation information;

and recording the label of the at least one item according to a preset data format.

2. The method of claim 1, wherein said parsing out annotation information from the project file comprises:

parsing out at least one level of annotation information from the project file, wherein the at least one level of annotation information comprises at least one of directory level annotation information, file level annotation information, category level annotation information, and project level annotation information, and the annotation information of each level is used for describing a tag of a corresponding level of the project.

3. The method of claim 2, further comprising, after said parsing out at least one level of annotation information from the project file:

and generating a node tree containing a parent-child relationship based on the level information of each piece of annotation information in the at least one level of annotation information.

4. The method of claim 3, wherein said determining a tag for said at least one item from said annotation information comprises:

parsing out tags of at least one level of the at least one item from the annotation information of the at least one level;

wherein the at least one level of tags includes at least one of a directory level tag corresponding to the directory level annotation information, a file level tag corresponding to the file level annotation information, a category level tag corresponding to the category level annotation information, and a project level tag corresponding to the project level annotation information.

5. The method of claim 4, wherein the recording the tag of the at least one item in a preset data format comprises:

determining a node corresponding to each label in the node tree according to the annotation information corresponding to each label in the at least one level of labels;

and binding each label to the corresponding node in the node tree.

6. The method of any of claims 1 to 5, wherein the parsing out annotation information from the project file comprises:

determining the file type of a project file by using a file distributor, and sending the project file to an annotation parser corresponding to the file type;

and analyzing annotation information from the project file by using the annotation analyzer.

7. The method of any of claims 1 to 5, further comprising, after said recording the tag of the at least one item in a preset data format:

in response to a tag selection operation by a user, determining that the user selected;

and determining at least one target item with the target label based on the label of the at least one item recorded by the preset data format.

8. A tag acquisition apparatus for an item, comprising:

the annotation analysis module is used for analyzing annotation information from a project file, wherein the project file comprises at least one project, and the annotation information is used for describing tag content of the project and is added in the project file in advance;

a tag determination module for determining a tag of the at least one item from the annotation information;

and the label recording module is used for recording the label of the at least one item according to a preset data format.

9. The apparatus of claim 8, wherein the annotation parsing module, when configured to parse annotation information from a project file, is specifically configured to:

parsing out at least one level of annotation information from the project file, wherein the at least one level of annotation information comprises at least one of directory level annotation information, file level annotation information, category level annotation information, and project level annotation information, and the annotation information of each level is used for describing a tag of a corresponding level of the project.

10. The apparatus of claim 8, the annotation parsing module to further:

and generating a node tree containing a parent-child relationship based on the level information of each piece of annotation information in the at least one level of annotation information.

11. The apparatus according to claim 10, wherein the tag determining module, when configured to determine the tag of the at least one item from the annotation information, is specifically configured to:

parsing out tags of at least one level of the at least one item from the annotation information of the at least one level;

wherein the at least one level of tags includes at least one of a directory level tag corresponding to the directory level annotation information, a file level tag corresponding to the file level annotation information, a category level tag corresponding to the category level annotation information, and a project level tag corresponding to the project level annotation information.

12. The apparatus according to claim 11, wherein the tag recording module, when configured to record the tag of the at least one item according to a preset data format, is specifically configured to:

determining a node corresponding to each label in the node tree according to the annotation information corresponding to each label in the at least one level of labels;

and binding each label to the corresponding node in the node tree.

13. The apparatus according to any one of claims 8 to 12, wherein the annotation parsing module, when configured to parse annotation information from a project file, is specifically configured to:

determining the file type of a project file by using a file distributor, and sending the project file to an annotation parser corresponding to the file type;

and analyzing annotation information from the project file by using the annotation analyzer.

14. The apparatus of any of claims 8 to 12, further comprising an item query module to:

responding to a label selection operation of a user, and determining a target label selected by the user;

and determining at least one target item with the target label based on the label of the at least one item recorded by the preset data format.

15. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.

16. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-7.

17. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1-7.

Images