CN109471904B - Method and system for organizing labels - Google Patents
Method and system for organizing labels Download PDFInfo
- Publication number
- CN109471904B CN109471904B CN201811297517.6A CN201811297517A CN109471904B CN 109471904 B CN109471904 B CN 109471904B CN 201811297517 A CN201811297517 A CN 201811297517A CN 109471904 B CN109471904 B CN 109471904B
- Authority
- CN
- China
- Prior art keywords
- label
- tag
- foreground view
- background
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method and a system for organizing labels. A method for organizing tags, comprising: selecting a label in the background category of the label to form a foreground view of the label; analyzing the label foreground view to obtain an execution plan, wherein the execution plan comprises task nodes; and executing the task node in the execution plan to generate label data corresponding to the label foreground view.
Description
Technical Field
The invention relates to big data technology, in particular to a method and a system for organizing labels on a big data development platform.
Background
In large data systems, data needs to be tagged. The definition, use and access to tags is an important implementation of data services. As scenes become more and more complex, the demand for labels also becomes more and more, and higher requirements are placed on the way in which labels are used. The traditional label using mode is to define label categories according to requirements, then develop labels and finally apply the labels to scenes. However, with the rapid change of the scene, the traditional label using mode cannot adapt to the development of the service well. Therefore, a more flexible way of using the tag is needed.
The prior art has taught solutions to the above-mentioned problems. For example, one existing way of using tags is to define tag categories and specific tags according to the requirements of the business; or developing the label according to specific logic and putting the label on line; or selecting and using the label of the corresponding category in the online service.
However, in the prior art solutions, there are still some problems. Firstly, in the process from label definition to label use, the life cycle of the label is too long, and the service requirement is difficult to meet. Second, even a simple attempt in one data scenario requires a significant amount of time and cost to produce the tag. Third, tags are all used with a single category as a basic unit, so that the tags cannot be flexibly organized and used.
Disclosure of Invention
One aspect of the invention is a method for organizing tags, comprising: selecting a label in the background category of the label to form a foreground view of the label; analyzing the label foreground view to obtain an execution plan, wherein the execution plan comprises task nodes; and executing the task node in the execution plan to generate label data corresponding to the label foreground view.
The step of selecting the label in the label background category to form the label foreground view further comprises: forming meta-information of the label foreground view from the label background category, a label background instance, and an entity associated with the label selected from the label background category.
The meta information includes: source information for recording the tag background category from which the tag foreground view originates, the selected tag, the tag background instance, and a tag entity associated with the tag background category; the association information is used for recording the association relation between at least two categories of the label background category; and output information for recording a storage location to which the tag data of the tag foreground view is output.
The step of parsing the foreground view of the label to obtain an execution plan further comprises: (1) reading the meta-information, and generating a script file and a dependency relationship of the label foreground view, wherein the dependency relationship is a dependency relationship between tasks related to the label background instance; (2) generating a first task node containing the script file; (3) generating a data synchronization script file, wherein the data synchronization script file describes the specification of writing data into a data source; and (4) generating a second task node containing the data synchronization script file, wherein the first task node is to be executed before the second task node.
The execution plan includes at least one workflow having an effective time, an ineffective time, and a scheduling period.
And at least two task nodes are included in the workflow, and have respective scheduling periods, dependency relationships and code positions.
The step of selecting the label in the label background category to form the label foreground view further comprises: and forming the label foreground view according to the same entity columns of the label entities respectively related to different label background instances.
The step of selecting the label in the label background category to form the label foreground view further comprises: and forming the label foreground view according to different entity columns of label entities respectively related to different label background instances, wherein mapping relations exist among the different entity columns.
In another aspect of the invention, a system for organizing tags is disclosed, comprising: a tag background category module that organizes tags by level; a tag backend instance module that includes a tag backend instance; a label foreground view module which presents at least one label selected by a user from the labels of the label background category module as a label foreground view; the label plan translator analyzes the label foreground view to obtain an execution plan; and a tag workflow execution engine that executes the execution plan to generate tag data corresponding to the tag foreground view.
The label foreground view module or the label background category module can form the meta-information of the label foreground view from the label background category, the label background instance and the entity related to the label selected from the label background category.
The meta information includes: source information for recording the tag background category from which the tag foreground view originates, the selected tag, the tag background instance, and a tag entity associated with the tag background category; the association information is used for recording the association relation between at least two categories of the label background category; and output information for recording a storage location to which the tag data of the tag foreground view is output.
The tag plan translator further comprises: a module for reading the meta-information and generating a script file and a dependency relationship of the label foreground view, wherein the dependency relationship is a dependency relationship between tasks related to the label background instance; means for generating a first task node containing the script file; a module for generating a data synchronization script file, the data synchronization script file describing a specification for writing data to a data source; and means for generating a second task node containing the data synchronization script file, wherein the first task node is to be executed before the second task node.
The execution plan includes at least one workflow having an effective time, an ineffective time, and a scheduling period.
And at least two task nodes are included in the workflow, and have respective scheduling periods, dependency relationships and code positions.
The label foreground view module further comprises: means for forming the foreground view of the label from the same entity columns of label entities with which different background instances of the label are respectively associated.
The label foreground view module further comprises: and the module is used for forming the label foreground view according to different entity columns of label entities respectively related to different label background instances, wherein mapping relations exist among the different entity columns.
Yet another aspect of the present invention discloses a computer readable medium having stored thereon computer readable instructions capable of executing the method for organizing tags, when executed by a computer.
The embodiment of the invention can realize the automatic organization of the labels across categories, can realize the flexible organization and use among a plurality of label categories, and can meet the diversified service requirements.
Furthermore, embodiments of the present invention may automatically organize and use different label categories without reworking new label categories.
Furthermore, the embodiment of the invention can shorten the life cycle of the tag and can meet the data service requirement.
Drawings
FIG. 1 illustrates components of a label system according to an embodiment of the present invention.
FIG. 2 shows a flow diagram of automatic organization of tags according to an embodiment of the invention.
FIG. 3 illustrates a flow diagram of a tag plan translator according to an embodiment of the present invention.
FIG. 4 shows a schematic diagram of an execution plan generated by the tag plan translator, according to an embodiment of the invention.
FIG. 5 illustrates a schematic diagram of the automatic organization of labels across columns of taxonomic entities, according to an embodiment of the present invention.
FIG. 6 illustrates a schematic diagram of an execution plan based on an automated organization schematic diagram of tags across taxonomic and physical columns, according to an embodiment of the present invention.
FIG. 7 illustrates a schematic diagram of the automatic organization of labels across categories of different columns of entities, according to an embodiment of the invention.
FIG. 8 illustrates a schematic diagram of an execution plan based on an automated organization of labels across categories of different columns of entities, according to an embodiment of the invention.
Detailed Description
The content of the invention will now be discussed with reference to a number of exemplary embodiments. It is to be understood that these examples are discussed only to enable those of ordinary skill in the art to better understand and thus implement the teachings of the present invention, and are not meant to imply any limitations on the scope of the invention.
As used herein, the term "include" and its variants are to be read as open-ended terms meaning "including, but not limited to. The term "based on" is to be read as "based, at least in part, on". The terms "one embodiment" and "an embodiment" are to be read as "at least one embodiment". The term "another embodiment" is to be read as "at least one other embodiment". As used herein, the term "task" may refer to any kind of executable unit, including but not limited to a process, a thread, a module, or a collection thereof.
In this disclosure, "tag" refers to a description of a particular object that can be implemented with a data structure in a computer system; the "tag data" is the content of the tag.
The logical composition of one embodiment of the present invention is shown in fig. 1, and includes the following parts: the system comprises a label foreground view module, a label background category module, a label background instance module, a label entity and a label workflow execution engine. The function and implementation of each part are explained as follows:
the label foreground view module: and combining the labels of different background classes selected by the user to present the labels in a uniform label foreground view.
Tag background category module: this module organizes the tags in a hierarchical (category) manner. The tag background category is a way of organizing tags by their level (e.g., one, two, three). There are usually multiple tags under a tag background class. The tag background category is stored in the database in the form of metadata.
The tag background instance module: which includes a tag background instance. The tag background instance is data corresponding to a tag under the background category, which may be organized in the form of a data table of a relational database. One tag background instance uniquely corresponds to one tag background category, and one tag background category may be embodied on a plurality of tag background instances.
The tag entity: the tag entity represents an object described by a tag, such as a person, company, country, cell, etc. The tag entity contains one or more entity columns (or fields), for example, the entity column of the tag entity, such as "person", may include a mailbox, an identification number, a mobile phone number, and the like.
The tag workflow execution engine: this engine schedules, executes tasks in the tagged workflow,
thereby generating label data for (the label of) the label foreground view.
In one embodiment of the invention, automatic organization of cross-category tags can be achieved without pre-defining the categories of the tag foreground. As shown in fig. 2, the flow of this embodiment includes the following steps:
(a) selecting a label from the label background category to form a label foreground view (an empty label view and no view data);
(b) analyzing a label foreground view through a label plan translator to obtain an execution plan, wherein the execution plan is a workflow comprising a plurality of task nodes;
(c) and the label workflow execution engine schedules and executes the task nodes in the plan according to the execution plan and generates label data of the labels contained in the label foreground view.
In one embodiment of the invention, the core module of the tag schema translator is the execution schema conversion function. Referring to fig. 3, the workflow of the tag schema translator is: reading the meta information of the label foreground view in the database, and obtaining the execution plan through an execution plan conversion function containing specific program logic. The execution plan is submitted to the workflow execution engine and scheduled and executed by the workflow execution engine.
The meta information of the foreground view of the tag, the execution plan conversion function, and the execution plan will be described in detail below.
(1) Meta information of foreground view of label
The meta information of the foreground view of the tag is data used to describe attributes of the foreground view of the tag, such as source, storage location, logical relationship, etc., according to specific requirements. The meta-information may be generated by the tag foreground view module or the tag background category module. The meta-information may also be referred to as meta-data, for example, it may record data of a tag background category and a tag background instance from which the tag foreground view originates, and a relationship between related tag entities and the tag foreground view, such as the following four kinds of information: tag background category (category), tag background instance (category _ instance), entity (entity), store (storage).
According to one embodiment of the present invention, the meta-information in json format according to which the process of forming the foreground view of the tag from the background category of the tag, the background instance of the tag, and the entity of the tag is described as follows:
the whole meta information is divided into three parts, which are sourceList, relation, and outputList. Wherein, the source list (sourceList) (source information) records the label background category information of the source of the current label foreground view, the selected label field information, the label background instance information and the entity information related to the label background category; an association (relation) describes an association between at least two related categories in the tag background categories; an output list (output information) describes a storage location where data of the tag foreground view is output.
The above data protocol describes the procedure as follows:
1. the label foreground view is derived from two label background categories, and the category ids of the two label background categories are 34 and 37 respectively;
2. respectively keeping four tags of 'c _ id', 'is _ car', 'is _ house' and 'is _ child' under the tag background category with id 34 and three tags of 'card', 'location' and 'sex' under the tag background category with id 37 as tags under the tag foreground view;
3. tag background category 34 is associated to an entity with id 17, whose c _ id is associated with the card _ id in that entity; the tag background category 37 associates 17 this entity, its card with the card _ id in the entity;
4. the two label background categories are associated through an instruction inner _ join, and the ids of the corresponding category instances are 138 and 168 respectively;
5. the tag data associated with the foreground view of the tag is output to type hive memory with id 276, the output mode is overwrite, and the output mode is to the partition with ds 20180903.
(2) Execution plan
An execution plan is a data protocol described in the xml language. According to one embodiment of the invention, the data protocol for executing the plan is as follows:
referring to fig. 4, the respective partial statements of the execution plan are explained as follows:
project contains a flow;
the flow comprises a plurality of flows, wherein each flow comprises attributes such as effective time (start _ effect _ date), dead time (end _ effect _ date), scheduling cycle (schedule _ expression) and the like;
and 3, the flow comprises a plurality of nodes, the nodes are nodes to be executed specifically, and the nodes comprise scheduling periods (schedule _ expression), parent node dependency information (entries), specific code positions (file _ path) and other information.
According to the above data protocol, the meaning expressed by the execution plan is: nodes c1 and c2 are parents of the node tag _ sql _ process, which is a parent of the node output; c1 and c2 are two tasks corresponding to the two related examples and are completed; the node tag _ sql _ process is completed first, and then the node output is completed.
(3) Executing a plan transfer function
The execution plan conversion function takes the meta information in the label foreground view as input, and outputs the execution plan in the xml format through the operation of program logic. Referring to the above example, the work steps to perform the planning transfer function are as follows:
(1) reading the meta information in the json format, and generating an sql script file and a dependency relationship (for example, the dependency relationship of the node tag _ sql _ process to the nodes c1 and c2 in the previous example) of the label foreground view according to the related information in the relation and the sourceList;
(2) generating a node tag _ sql _ process with the type of hive _ sql, generating the dependency relationship of the node tag _ sql _ process (for the nodes c1 and c2), wherein the dependency relationship comprises the sql script file generated in the step (1), and the parent node of the sql script file is from the step (1);
(3) acquiring information of a related data source according to the storageId of the outputList in the meta information, and generating a data synchronization script file, wherein the file describes a specification of writing data into the data source;
(4) generating a data synchronization node output with the type of datax, wherein the data synchronization node output contains the data synchronization script file generated in the step (3), and a parent node of the data synchronization script file is the node tag _ sql _ process generated in the step (2);
(5) and (4) generating an execution plan in an xml format according to the steps (1) to (4).
In one embodiment of the invention, the tag plan translator further comprises: a module for reading the meta-information and generating a script file and a dependency relationship of the label foreground view, wherein the dependency relationship is a dependency relationship between tasks related to the label background instance; means for generating a first task node containing the script file; a module for generating a data synchronization script file, the data synchronization script file describing a specification for writing data to a data source; and means for generating a second task node containing the data synchronization script file, wherein the first task node is to be executed before the second task node.
Two ways of automatic tag organization included in the aforementioned translator and tag workflow execution engines will be described below: automatic organization of columns of entities across categories, and automatic organization of columns of entities across categories. The detailed description is as follows:
automatic organization of cross-category homogeneous entity columns
An exemplary method for automatic organization of columns of entities across categories includes the steps of:
(1) selecting different labels from different label background examples (which can only correspond to a label background category) to construct a new foreground label view: as shown in fig. 5, based on the "person" entity, the identity card number, the vehicle family, and the room family are selected from the tag background example 1, and the identity card number, the working location, and the gender tag are selected from the tag background example 2, so as to finally form a new organized foreground tag view of the identity card number, the vehicle family, the room family, the gender, and the working location;
(2) the label background categories corresponding to different label background instances are all related to the same entity column of the same entity: e.g. tag background category 1, tag background category 2 are associated to the card _ id of the person entity;
(3) different tag background instances can query the tag task associated with the instance: if the label background example 1 is associated to the label task 1, the label background example 2 is associated to the label task 2;
(4) and generating an execution plan of the label foreground view through a label plan translator according to the meta-information of the label foreground view, and executing the execution plan by a label workflow execution engine.
And aiming at the scenes of the same entity column, generating a new label foreground view and an execution plan of the label thereof. As shown in fig. 6, the label plan translator will translate the label foreground view into an execution plan of a label containing a plurality of task nodes, and the final label execution plan information is as follows:
(a) the meta information of the tag foreground view generated according to the above step (1) is as follows:
(b) reading sourceList information, and querying corresponding tag tasks of c1 and c2 according to tag background instances 1 and 2(category _ instance _ id:138 and category _ instance _ id:168), respectively.
(c) According to the relation and sourceList information, generating an sql script corresponding to the label foreground view, wherein the content is as follows: create table front _ tag _ c1_ c2_1as select c1.card _ id, c1.car, c1.house, c2.sex, c2.work _ place from c1, c2where c1.card _ id is c2.card _ id, the corresponding name is front _ tag _ c1_ c2_1.sql, which depends on two tasks of c1 and c2
(d) Generating a tag data synchronization script datax _ front _ tag _ c1_ c2_1.json of a tag foreground view according to an outputlist, wherein the tag data synchronization script depends on a front _ tag _ c1_ c2_1 task, and the content is as follows:
(e) the label execution plan generated according to the information of the steps (b), (c) and (d) is as follows:
(f) the execution plan is transmitted to the tagged workflow execution engine for execution in a dynamic schedule.
In an embodiment of the present invention, the label foreground view module further includes: means for forming the foreground view of the label from the same entity columns of label entities with which different background instances of the label are respectively associated.
Automatic organization of different entity columns across categories
The scenarios of automatic organization across different entity columns of a category differ from the scenarios of automatic organization across the same entity column of a category by: first, the entity columns of the entities are different; secondly, the workflow execution engine has a corresponding entity column mapping (mapping) task; thirdly, the label execution plans are different.
The automatic organization of different columns of entities across categories according to one embodiment of the invention is as follows:
(1) selecting different labels from different label background examples (which can only correspond to a label background category) to construct a new foreground label view: as shown in fig. 7, based on the "person" entity, the identity card number, the tag of the vehicle family and the tag of the house family are selected from the tag background example 1, and the mailbox, the office location and the sex tag are selected from the tag background example 2, so that a new organized foreground tag view of the identity card number, the mailbox, the vehicle family, the house family, the sex and the office location is finally formed.
(2) The label background categories corresponding to different label background instances are all related to the same entity, but are related to different entity columns: for example, the tag background category 1 and the tag background category 2 are respectively associated with the card _ id and email columns of the person entity.
(3) Different tag background instances can query the tag task associated with the instance: if the label background example 1 is associated to the label task 1, the label background example 2 is associated to the label task 2; an entity column mapping (mapping) task to entity associations may be queried.
(4) And organizing and generating an execution plan of the label view through a label plan translator according to the meta-information of the label foreground view, and executing the execution plan by a label workflow execution engine.
And generating a new label foreground view and an execution plan thereof aiming at the scenes of different entity columns. As shown in fig. 8, the label plan translator will translate the label foreground view into an execution plan containing a plurality of task nodes, and the final label execution plan information is as follows:
(a) the label foreground view meta-information generated according to the above step (1) is as follows:
(b) reading sourceList information, and inquiring corresponding label tasks of c1 and c3 according to the label background instances 1 and 2(category _ instance _ id:138 and category _ instance _ id: 169); and obtaining an associated entity column mapping (mapping) task c4 according to the entityId information of the entity.
(c) According to the relation and sourceList information, generating an sql script corresponding to the label foreground view, wherein the content is as follows: create table front _ tag _ d _ c1_ c3_1as select c1.card _ id, c3.email, c1.car, c1.house, c3.sex, c3.work _ place from c1, c3, c4where c1.card _ id ═ c4.card _ id and c2.email ═ c4.email, corresponding name is front _ tag _ d _ c1_ c3_1.sql, which depends on three tasks of c1, c3, c4.
(d) Generating a tag data synchronization script datax _ front _ tag _ c1_ c3_1.json of a tag foreground view according to an outputlist, wherein the tag data synchronization script depends on a front _ tag _ c1_ c3_1 task, and the content is as follows:
(e) the execution plan generated from the information of steps (b), (c), and (d) is as follows:
(f) transmitting the execution plan to a tagged workflow execution engine to execute the execution plan in a dynamic schedule
And executing the plan.
In an embodiment of the present invention, the label foreground view module further includes: and the module is used for forming the label foreground view according to different entity columns of label entities respectively related to different label background instances, wherein mapping relations exist among the different entity columns.
The following objects can be achieved by implementing embodiments of the present invention: firstly, a cross-category label automatic organization system is provided; secondly, the embodiment of the invention can realize the self-screening combination of cross-category labels, support the automatic generation of an execution plan and quickly support the requirement on a new data scene; thirdly, the whole automatic organization and execution flow is completed through the label plan translator and the label workflow execution engine.
The system, method and apparatus of the embodiments of the present invention can be implemented as pure software (e.g., a software program written in Java and SQL), as pure hardware (e.g., a dedicated ASIC chip or FPGA chip), as desired, or as a system combining software and hardware (e.g., a firmware system storing fixed code or a system with a general-purpose memory and a processor).
Another aspect of the invention is a computer-readable medium having computer-readable instructions stored thereon that, when executed, perform a method of embodiments of the invention.
While various embodiments of the present invention have been described above, the above description is intended to be illustrative, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The scope of the claimed subject matter is limited only by the attached claims.
Claims (17)
1. A method for organizing tags, comprising:
selecting a label in a label background category to form a label foreground view and meta-information of the label foreground view, wherein the meta-information is used for describing the attribute of the label foreground view and comprises at least two categories used for recording the label background category;
parsing the label foreground view to obtain an execution plan, the execution plan including task nodes, wherein the parsing reads and uses the meta-information to generate dependencies between the task nodes; and
and executing the task nodes in the execution plan according to the dependency relationship, and generating label data corresponding to the label foreground view.
2. The method of claim 1, wherein the selecting a tag in a tag background category to form a tag foreground view further comprises:
forming the meta-information from the tag background category, tag background instances, entities related to the tag selected from the tag background category.
3. The method of claim 2, wherein the meta information further comprises:
source information for recording the tag background category from which the tag foreground view originates, the selected tag, the tag background instance, and a tag entity associated with the tag background category; and
output information for recording a storage location to which the tag data of the tag foreground view is output.
4. The method of claim 2, wherein the step of parsing the foreground view of tags for an execution plan further comprises:
(1) reading the meta-information, and generating a script file and a dependency relationship of the label foreground view, wherein the dependency relationship is a dependency relationship between tasks related to the label background instance;
(2) generating a first task node containing the script file;
(3) generating a data synchronization script file, wherein the data synchronization script file describes the specification of writing data into a data source; and
(4) generating a second task node containing the data synchronization script file, wherein the first task node is to be executed before the second task node.
5. The method of claim 1, wherein the execution plan includes at least one workflow having an effective time, an ineffective time, and a scheduling period.
6. The method of claim 5, wherein at least two task nodes are included in the workflow, the at least two task nodes having respective scheduling periods, dependencies, and code positions.
7. The method of claim 2, wherein the selecting a tag in a tag background category to form a tag foreground view further comprises:
and forming the label foreground view according to the same entity columns of the label entities respectively related to different label background instances.
8. The method of claim 2, wherein the selecting a tag in a tag background category to form a tag foreground view further comprises:
and forming the label foreground view according to different entity columns of label entities respectively related to different label background instances, wherein mapping relations exist among the different entity columns.
9. A system for organizing tags, comprising:
the label background category module organizes labels according to the label background category;
a tag backend instance module that includes a tag backend instance;
the system comprises a label foreground view module, a label background category module and a display module, wherein the label foreground view module is used for displaying at least one label selected by a user from the labels of the label background category module as a label foreground view and forming meta-information of the label foreground view, and the meta-information is used for describing the attribute of the label foreground view and comprises at least two categories used for recording the label background category;
a tag plan translator that parses the tag foreground view to derive an execution plan, wherein the parsing reads and uses the meta-information to generate dependencies between task nodes; and
and the label workflow execution engine executes the task nodes in the execution plan according to the dependency relationship and generates label data corresponding to the label foreground view.
10. The system of claim 9, wherein the label foreground view module or the label background category module is capable of forming the meta-information from the label background category, a label background instance, an entity related to the label selected from the label background category.
11. The system of claim 10, wherein the meta information further comprises:
source information for recording the tag background category from which the tag foreground view originates, the selected tag, the tag background instance, and a tag entity associated with the tag background category; and
output information for recording a storage location to which the tag data of the tag foreground view is output.
12. The system of claim 10, wherein the tag plan translator further comprises:
a module for reading the meta-information and generating a script file and a dependency relationship of the label foreground view, wherein the dependency relationship is a dependency relationship between tasks related to the label background instance;
means for generating a first task node containing the script file;
a module for generating a data synchronization script file, the data synchronization script file describing a specification for writing data to a data source; and
means for generating a second task node containing the data synchronization script file, wherein the first task node is to be executed before the second task node.
13. The system of claim 9, wherein the execution plan includes at least one workflow having an effective time, an ineffective time, and a scheduling period.
14. The system of claim 13, wherein at least two task nodes are included in the workflow, the at least two task nodes having respective scheduling periods, dependencies, and code positions.
15. The system of claim 10, wherein the label foreground view module further comprises:
means for forming the foreground view of the label from the same entity columns of label entities with which different background instances of the label are respectively associated.
16. The system of claim 10, wherein the label foreground view module further comprises:
and the module is used for forming the label foreground view according to different entity columns of label entities respectively related to different label background instances, wherein mapping relations exist among the different entity columns.
17. A computer readable medium having computer readable instructions stored thereon which, when executed by a computer, are capable of performing the method of any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811297517.6A CN109471904B (en) | 2018-11-01 | 2018-11-01 | Method and system for organizing labels |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811297517.6A CN109471904B (en) | 2018-11-01 | 2018-11-01 | Method and system for organizing labels |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109471904A CN109471904A (en) | 2019-03-15 |
| CN109471904B true CN109471904B (en) | 2021-07-20 |
Family
ID=65666786
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811297517.6A Active CN109471904B (en) | 2018-11-01 | 2018-11-01 | Method and system for organizing labels |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109471904B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110110224A (en) * | 2019-04-16 | 2019-08-09 | 中科金联（北京）科技有限公司 | A kind of data migration method and system based on the multiple label of data |
| CN111787084A (en) * | 2020-06-23 | 2020-10-16 | 杭州数澜科技有限公司 | Method and device for selecting object |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101699393B (en) * | 2009-10-09 | 2013-03-20 | 中国电子科技集团公司第二十八研究所 | Network-facing intelligent software interface dynamic generation method |
| CN102236669B (en) * | 2010-04-30 | 2014-09-24 | 腾讯科技（深圳）有限公司 | Recommendation list generation method, device, media server, client and method |
| CN103164476A (en) * | 2011-12-16 | 2013-06-19 | 中国移动通信集团公司 | Execution method and execution device of applying metadata to describe files in business intelligence (BI) |
| CN105404509B (en) * | 2015-11-11 | 2019-06-21 | 平湖神州数码博海科技有限公司 | Method based on ExtJS UI Visual Production code |
| CN107872589B (en) * | 2016-09-26 | 2020-01-14 | 中国电信股份有限公司 | User characteristic display method and system |
| CN108629608B (en) * | 2017-03-22 | 2023-02-24 | 腾讯科技（深圳）有限公司 | User data processing method and device |
-
2018
- 2018-11-01 CN CN201811297517.6A patent/CN109471904B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN109471904A (en) | 2019-03-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107341262B (en) | Serialization and deserialization method and device for object type column in database | |
| US9128996B2 (en) | Uniform data model and API for representation and processing of semantic data | |
| US9208212B2 (en) | Field extensibility in a multi-tenant environment with columnar database support | |
| US7779386B2 (en) | Method and system to automatically regenerate software code | |
| JP5008878B2 (en) | Mapping file system models to database objects | |
| CN108228817A (en) | Data processing method, device and system | |
| US20110173220A1 (en) | Generating web services from business intelligence queries | |
| US20130166563A1 (en) | Integration of Text Analysis and Search Functionality | |
| US11334549B2 (en) | Semantic, single-column identifiers for data entries | |
| CN109815242B (en) | Data processing method and system | |
| CN112148788A (en) | Data synchronization method and system for heterogeneous data source | |
| US20100057760A1 (en) | Generic data retrieval | |
| CN109471904B (en) | Method and system for organizing labels | |
| US20100131565A1 (en) | Method for creating a self-configuring database system using a reusable custom-defined nestable compound data type | |
| US9652740B2 (en) | Fan identity data integration and unification | |
| CN103577483A (en) | Data storage method, data storage system, data access method and data access system | |
| CN110888878A (en) | Service-oriented main data management method and system | |
| US20080168083A1 (en) | Taxonomy object modeling | |
| CN110879799B (en) | Method and device for labeling technical metadata | |
| CN112463986A (en) | Information storage method and device | |
| CN112699282A (en) | Industrial internet data processing method and device, electronic equipment and storage medium | |
| CN113535966A (en) | Knowledge graph creating method, information obtaining method, device and equipment | |
| CN114895875B (en) | Zero-code visual information system metadata production application method and system | |
| CN111476010B (en) | High-flexibility reporting method and system | |
| CN112699251A (en) | Data aggregation method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |