CN112905586A - Data processing and accessing method, device, computer system and readable storage medium - Google Patents

Data processing and accessing method, device, computer system and readable storage medium Download PDF

Info

Publication number
CN112905586A
CN112905586A CN201911222491.3A CN201911222491A CN112905586A CN 112905586 A CN112905586 A CN 112905586A CN 201911222491 A CN201911222491 A CN 201911222491A CN 112905586 A CN112905586 A CN 112905586A
Authority
CN
China
Prior art keywords
data
tag
content
access request
data object
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.)
Pending
Application number
CN201911222491.3A
Other languages
Chinese (zh)
Inventor
代伟超
陈金玉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to CN201911222491.3A priority Critical patent/CN112905586A/en
Publication of CN112905586A publication Critical patent/CN112905586A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22Indexing; Data structures therefor; Storage structures
    • G06F16/2282Tablespace storage structures; Management thereof
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/245Query processing
    • G06F16/2455Query execution
    • G06F16/24553Query execution of query operations
    • G06F16/24558Binary matching operations
    • G06F16/2456Join operations
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25Integrating or interfacing systems involving database management systems
    • G06F16/256Integrating or interfacing systems involving database management systems in federated or virtual databases

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computational Linguistics (AREA)
  • Software Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The embodiment of the disclosure discloses a data processing and accessing method, a device, a computer system and a readable storage medium, wherein the data processing method comprises the steps of establishing a label corresponding to a data object; displaying the label; receiving a data access request automatically generated after a user selects the tag; providing the content of the data object corresponding to the tag to the user in response to the data access request.

Description

Data processing and accessing method, device, computer system and readable storage medium
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a data processing and accessing method, an apparatus, a computer system, and a readable storage medium.
Background
In a data processing system, data is typically stored in a physical table of a database. A physical table typically includes a plurality of records, each record corresponding to a particular object. Each record, in turn, includes a plurality of fields for describing different characteristics of the particular object. In the course of making this disclosure, the inventor finds that business persons understand business concepts and business processes, and easily understand models, concepts, objects, business processes and indexes in business, but business persons are not familiar with methods of accessing databases and looking up tables, and also have difficulty in understanding data expressed in table form. Therefore, a gap exists between the current data storage situation and the demands of business personnel, and inconvenience is brought to the business personnel for inquiring, analyzing and using the data.
Disclosure of Invention
In order to solve the problems in the related art, embodiments of the present disclosure provide a data processing and accessing method, apparatus, computer system and readable storage medium.
In a first aspect, an embodiment of the present disclosure provides a data processing method.
Specifically, the data processing method includes: establishing a label corresponding to the data object;
displaying the label;
receiving a data access request automatically generated after a user selects the tag;
providing the content of the data object corresponding to the tag to the user in response to the data access request.
With reference to the first aspect, in a first implementation manner of the first aspect, the content of the data object is a physical table content or a result obtained by performing an operation on the physical table content; or
The content of the data object is a proper subset of the content of the physical table or a result obtained by operating on the proper subset; or
The content of the data object is field content in a physical table or a result obtained by operating on the field content.
With reference to the first aspect, in a second implementation manner of the first aspect, the creating a tag corresponding to a data object includes:
for data objects associated with a particular subject, a corresponding tag is established.
With reference to the second implementation manner of the first aspect, in a third implementation manner of the first aspect, the establishing a corresponding tag for a data object associated with a specific subject includes:
generating a respective tag for a data object associated with a particular principal and binding the respective tag with the particular principal; or
Binding an existing tag with the particular principal.
With reference to the second implementation manner of the first aspect, in a fourth implementation manner of the first aspect, the specific subject includes an entity or a relationship.
With reference to the fourth implementation manner of the first aspect, in a fifth implementation manner of the first aspect, the establishing a corresponding tag for a data object associated with a specific subject includes:
when the specific subject is an entity, establishing a main label aiming at a data object for uniquely identifying the entity, and establishing a common label aiming at other data objects related to the entity;
when the specific subject is a relationship, respectively establishing main tags for a plurality of data objects for uniquely identifying the relationship to form a main tag group for uniquely identifying the relationship, and establishing common tags for other data objects related to the relationship.
With reference to the first aspect, in a sixth implementation manner of the first aspect, the establishing tags corresponding to the data objects includes respectively establishing corresponding tags for different data objects distributed in different data sources.
With reference to the sixth implementation manner of the first aspect, in a seventh implementation manner of the first aspect, the data processing method further includes:
generating a federated data source based on the different data sources when the data access request involves the different data sources;
obtaining content of the data object corresponding to the tag from the federated data source.
With reference to the seventh implementation manner of the first aspect, in an eighth implementation manner of the first aspect, the generating a joint data source based on the different data sources includes:
when the different data sources are of different types, generating the federated data source based on the different types of data sources, the data in the federated data source complying with the same storage and access rules.
With reference to the first aspect, in a ninth implementation manner of the first aspect, the data access request is generated based on a tag selected by a user and a type of a data source where a data object corresponding to the tag is located.
In a second aspect, an embodiment of the present disclosure provides a data processing method.
Specifically, the data processing method includes:
establishing a label corresponding to the data object;
receiving a data access request automatically generated based on a selection for the tag;
providing content of the data object corresponding to the tag in response to the data access request.
In a third aspect, an embodiment of the present disclosure provides a data access method.
Specifically, the data access method includes: displaying a label corresponding to the data object;
automatically generating a data access request in response to a user selecting the tag;
receiving the content of the data object corresponding to the tag returned in response to the data access request.
With reference to the third aspect, in a first implementation manner of the third aspect, the content of the data object is a physical table content or a result obtained by performing an operation on the physical table content; or
The content of the data object is a proper subset of the content of the physical table or a result obtained by operating on the proper subset; or
The content of the data object is field content in a physical table or a result obtained by operating on the field content.
With reference to the third aspect, in a second implementation manner of the third aspect, the data access method further includes: a particular subject associated with the tag is presented.
With reference to the third aspect, in a third implementation manner of the third aspect, the automatically generating a data access request in response to the user selecting the tag includes: and when the data objects corresponding to the tags are distributed in different data sources, automatically generating a cross-data-source data access request.
In a fourth aspect, an embodiment of the present disclosure provides a data processing apparatus.
Specifically, the data processing apparatus includes: the tag establishing module is used for establishing tags corresponding to the data objects;
the label display module is used for displaying the label;
the data access request receiving module is used for receiving a data access request automatically generated after the user selects the tag;
and the data object content providing module is used for responding to the data access request and providing the content of the data object corresponding to the label to the user.
With reference to the fourth aspect, in a first implementation manner of the fourth aspect, the content of the data object is a physical table content or a result obtained by performing an operation on the physical table content; or
The content of the data object is a proper subset of the content of the physical table or a result obtained by operating on the proper subset; or
The content of the data object is field content in a physical table or a result obtained by operating on the field content.
With reference to the fourth aspect, in a second implementation manner of the fourth aspect, the creating a tag corresponding to the data object includes:
for data objects associated with a particular subject, a corresponding tag is established.
With reference to the second implementation manner of the fourth aspect, in a third implementation manner of the fourth aspect, the establishing a corresponding tag for a data object associated with a specific subject includes:
generating a respective tag for a data object associated with a particular principal and binding the respective tag with the particular principal; or
Binding an existing tag with the particular principal.
With reference to the second implementation manner of the fourth aspect, in a fourth implementation manner of the fourth aspect, the specific subject includes an entity or a relationship.
With reference to the fourth implementation manner of the fourth aspect, in a fifth implementation manner of the fourth aspect, the establishing respective tags for the data objects associated with the specific subject includes:
when the specific subject is an entity, establishing a main label aiming at a data object for uniquely identifying the entity, and establishing a common label aiming at other data objects related to the entity;
when the specific subject is a relationship, respectively establishing main tags for a plurality of data objects for uniquely identifying the relationship to form a main tag group for uniquely identifying the relationship, and establishing common tags for other data objects related to the relationship.
With reference to the fourth aspect, in a sixth implementation manner of the fourth aspect, the establishing tags corresponding to the data objects includes respectively establishing corresponding tags for different data objects distributed in different data sources.
With reference to the sixth implementation manner of the fourth aspect, in a seventh implementation manner of the fourth aspect, the data processing apparatus further includes:
generating a federated data source based on the different data sources when the data access request involves the different data sources;
obtaining content of the data object corresponding to the tag from the federated data source.
With reference to the seventh implementation manner of the fourth aspect, in an eighth implementation manner of the fourth aspect, the generating a federated data source based on the different data sources includes:
when the different data sources are of different types, generating the federated data source based on the different types of data sources, the data in the federated data source complying with the same storage and access rules.
With reference to the fourth aspect, in a ninth implementation manner of the fourth aspect, the data access request is generated based on a tag selected by a user and a type of a data source where a data object corresponding to the tag is located.
In a fifth aspect, the disclosed embodiments provide a data access apparatus.
Specifically, the data access device includes: the label display module is used for displaying labels corresponding to the data objects;
the data access request generation module is used for responding to the label selected by the user and automatically generating a data access request;
a data object content return module for receiving the content of the data object corresponding to the tag returned in response to the data access request.
With reference to the fifth aspect, in a first implementation manner of the fifth aspect, the content of the data object is a physical table content or a result obtained by performing an operation on the physical table content; or
The content of the data object is a proper subset of the content of the physical table or a result obtained by operating on the proper subset; or
The content of the data object is field content in a physical table or a result obtained by operating on the field content.
With reference to the fifth aspect, in a second implementation manner of the fifth aspect, the data access apparatus further includes: a specific body display module for displaying a specific body associated with the tag.
With reference to the fifth aspect, in a third implementation manner of the fifth aspect, the automatically generating a data access request in response to the user selecting the tag includes: and when the data objects corresponding to the tags are distributed in different data sources, automatically generating a cross-data-source data access request.
In a sixth aspect, a computer system is provided in embodiments of the present disclosure. Specifically, the computer system includes: a processor; a memory storing executable instructions that, when executed by the processor, perform the method steps of:
displaying the label;
receiving a data access request automatically generated after a user selects the tag;
providing the content of the data object corresponding to the tag to the user in response to the data access request.
With reference to the sixth aspect, in a first implementation manner of the sixth aspect, the content of the data object is a physical table content or a result obtained by performing an operation on the physical table content; or
The content of the data object is a proper subset of the content of the physical table or a result obtained by operating on the proper subset; or
The content of the data object is field content in a physical table or a result obtained by operating on the field content.
With reference to the sixth aspect, in a second implementation manner of the sixth aspect, the creating a label corresponding to the data object includes:
for data objects associated with a particular subject, a corresponding tag is established.
With reference to the second implementation manner of the sixth aspect, in a third implementation manner of the sixth aspect, the establishing a corresponding tag for a data object associated with a specific subject includes:
generating a respective tag for a data object associated with a particular principal and binding the respective tag with the particular principal; or
Binding an existing tag with the particular principal.
With reference to the second implementation manner of the sixth aspect, in a fourth implementation manner of the sixth aspect, the specific subject includes an entity or a relationship.
With reference to the fourth implementation manner of the sixth aspect, in a fifth implementation manner of the sixth aspect, the establishing respective tags for the data objects associated with the specific subject includes:
when the specific subject is an entity, establishing a main label aiming at a data object for uniquely identifying the entity, and establishing a common label aiming at other data objects related to the entity;
when the specific subject is a relationship, respectively establishing main tags for a plurality of data objects for uniquely identifying the relationship to form a main tag group for uniquely identifying the relationship, and establishing common tags for other data objects related to the relationship.
With reference to the sixth aspect, in a sixth implementation manner of the sixth aspect, the establishing tags corresponding to the data objects includes respectively establishing corresponding tags for different data objects distributed in different data sources.
With reference to the sixth implementation manner of the sixth aspect, in a seventh implementation manner of the sixth aspect of the present disclosure, the data processing method further includes:
generating a federated data source based on the different data sources when the data access request involves the different data sources;
obtaining content of the data object corresponding to the tag from the federated data source.
With reference to the seventh implementation manner of the sixth aspect, in an eighth implementation manner of the sixth aspect, the generating a federated data source based on the different data sources includes:
when the different data sources are of different types, generating the federated data source based on the different types of data sources, the data in the federated data source complying with the same storage and access rules.
With reference to the sixth aspect, in a ninth implementation manner of the sixth aspect, the data access request is generated based on a tag selected by a user and a type of a data source where a data object corresponding to the tag is located.
In a seventh aspect, a computer system is provided in the disclosed embodiments. Specifically, the computer system includes: a processor; a memory storing executable instructions that, when executed by the processor, perform the method steps of:
automatically generating a data access request in response to a user selecting the tag;
receiving the content of the data object corresponding to the tag returned in response to the data access request.
With reference to the seventh aspect, in a first implementation manner of the seventh aspect, the content of the data object is a physical table content or a result obtained by performing an operation on the physical table content; or
The content of the data object is a proper subset of the content of the physical table or a result obtained by operating on the proper subset; or
The content of the data object is field content in a physical table or a result obtained by operating on the field content.
With reference to the seventh aspect, in a second implementation manner of the seventh aspect, the data access method further includes: a particular subject associated with the tag is presented.
With reference to the seventh aspect, in a third implementation manner of the seventh aspect, the automatically generating a data access request in response to the user selecting the tag includes: and when the data objects corresponding to the tags are distributed in different data sources, automatically generating a cross-data-source data access request.
In an eighth aspect, a computer-readable storage medium is provided in embodiments of the present disclosure.
In particular, the computer-readable storage medium stores executable instructions that, when executed by a processor, implement the method according to any one of the first aspect, the first implementation manner of the first aspect to the ninth implementation manner of the first aspect, the second aspect, the third aspect, and the first implementation manner of the third aspect to the third implementation manner of the third aspect.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects: the method and the system abstract the data objects associated with the entities and the relations according to the requirements of business personnel on the basis of the data objects of the concrete database table, and establish labels for the data objects. In the process of accessing the database, business personnel only need to operate the entities, the relations and the labels directly related to the business, and do not need to directly access the tables and the fields of the underlying database. The embodiment of the disclosure converts the operation of business personnel on entities, relationships and labels into the operation on tables and fields in the bottom database. Further, entities, relationships, and tags may be associated to multiple different tables in multiple different databases. By the method, business personnel can access the bottom database at the business level, database details which cannot be understood and do not need to be understood by the business personnel are shielded, the multi-database access capability is achieved, and the working efficiency is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
Other labels, objects and advantages of the present disclosure will become more apparent from the following detailed description of non-limiting embodiments when taken in conjunction with the accompanying drawings. In the drawings:
FIG. 1 illustrates a diagram of a correspondence between an exemplary business model and a physical table, according to an embodiment of the disclosure;
FIG. 2 illustrates a schematic diagram of an exemplary user interface for data statistics using tags, according to an embodiment of the present disclosure;
FIG. 3A shows a flow diagram of a data processing method according to an embodiment of the present disclosure;
FIG. 3B shows a flow diagram of a data processing method according to another embodiment of the present disclosure;
FIG. 4 shows a flow diagram of a data access method according to an embodiment of the present disclosure;
FIG. 5 shows a flow diagram of a data access method according to an embodiment of the present disclosure;
FIG. 6 shows a block diagram of a data processing apparatus according to an embodiment of the present disclosure;
FIG. 7 shows a block diagram of a data access device according to an embodiment of the present disclosure;
FIG. 8 shows a block diagram of a data access device according to an embodiment of the present disclosure;
FIG. 9 shows a block diagram of a computer system according to an embodiment of the present disclosure;
fig. 10 shows a schematic structural diagram of a computer system suitable for implementing a data processing method and/or a data access method according to an embodiment of the present disclosure.
Detailed Description
Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily implement them. Also, for the sake of clarity, parts not relevant to the description of the exemplary embodiments are omitted in the drawings.
In the present disclosure, it is to be understood that terms such as "including" or "having," etc., are intended to indicate the presence of the disclosed features, numbers, steps, behaviors, components, parts, or combinations thereof, and are not intended to preclude the possibility that one or more other features, numbers, steps, behaviors, components, parts, or combinations thereof may be present or added.
It should be further noted that the embodiments and features of the embodiments in the present disclosure may be combined with each other without conflict. The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
FIG. 1 illustrates a diagram of a correspondence between an exemplary business model and a physical table, including entities represented by circles, relationships represented by diamonds, and physical tables used to describe the entities and relationships, respectively, according to an embodiment of the disclosure.
As shown in FIG. 1, in the exemplary business model, buyers 110, sellers 120, and commodities 130 are associated with one another via relationships 140, where the relationships 140 may be, for example, a deal relationship 150. Table a user base information table 111 and table B user contribution preference table 112 are used to describe the buyer 110. Table a has fields uid (user id), gender, and age, and table B has fields uid (user id), avg _ span (average monthly consumption amount), and avg _ bills (average monthly consumption stroke number). Table C the seller information table 121 is used to describe the seller 120, and has fields shop _ id (store identification), s _ name (store name), s _ star (store star), s _ play (platform), and s _ rate (store goodness). The product information table 131 is used to describe the product 130, and has fields item _ id (product identification), shop _ id (store identification), item _ title (product title), item _ prop (product attribute), cat _ id (category identification), cat _ name (category name), and price (product price). Table E order table 151 is used to describe the deal relationship 150, and has fields cid (order id), uid (user id), shop id (store id), item _ id (item id), datetime (deal date), and amt _ pay (deal amount).
As can be seen from fig. 1, to perform business modeling, data in multiple physical tables may be involved, and it is very difficult and burdensome for a user unfamiliar with database operations to write a database query statement such as an SQL statement to perform database access.
FIG. 2 illustrates a schematic diagram of an exemplary user interface for data statistics using tags, according to an embodiment of the present disclosure.
As shown in FIG. 2, the exemplary user interface includes a candidate tab area 201, a chart configuration area 202, and a chart display area 203.
As an example, the candidate tag area shows 4 different tags, each tag corresponding to a different field in the physical table, and the number and specific content of the tags can be automatically configured according to the current business scenario of the user. For example, a service scenario to which the tag is applicable may be set when the tag is established, so that the tag to be displayed may be automatically determined according to the current service scenario.
For example, when a user is to perform a statistical analysis on the user's power usage, the candidate tag area 201 may display tags: the client status (status _ code), client number (cons _ no), town and country category (urban _ road), and settlement mode (sette _ mode) respectively correspond to the fields in the physical table: status _ code, cons _ no, url _ run, and search _ mode.
Assuming that the data that the user wants to Count is the number of users in different user states, the tab user state (status _ code) may be dragged to the "select X-axis" input box of the chart configuration area 202, the tab client number (cons _ no) may be dragged to the "select Y-axis" input box of the chart configuration area 202, and then the Count "may be selected in the" aggregation function "input box, and the" histogram "may be selected in the" statistical chart "input box. According to the label selected by the user, the system automatically determines the field in the physical table corresponding to the label, generates a database query statement and acquires field data. The field data is processed according to the aggregation function selected by the user and displayed in the graph display area 203 in the form of a histogram.
As can be seen from the above examples, according to the embodiments of the present disclosure, a user does not need to know the underlying technology of database access, but can conveniently access database data simply by selecting a tag, which provides great convenience to the user. Particularly, due to the rapid development of computer technology, the update iteration of database technology is also very rapid, and business personnel are required to be skilled in the latest database technology like professional developers, which undoubtedly will seriously affect the production and operation efficiency and increase the enterprise cost for enterprises. Through the technology disclosed by the invention, the database bottom technology can be shielded for business personnel, when the database technology is updated, only developers need to modify the label system correspondingly, the business system is less affected, and the business personnel also do not need to be trained additionally.
Fig. 3A illustrates a flow diagram of a data processing method according to an embodiment of the present disclosure.
As shown in fig. 3A, the data processing method according to an embodiment of the present disclosure includes the following steps S301 to S304.
In step S301, a tag corresponding to the data object is established;
in step S302, the label is presented;
in step S303, a data access request automatically generated after the user selects the tag is received;
in step S304, the content of the data object corresponding to the tag is provided to the user in response to the data access request.
For example, in the example shown in fig. 1, according to the business requirements, a tag may be established: the user identifier (f _ uid), the age (f _ age), the store identifier (f _ shop _ id), the date of the deal (f _ datetime), and the amount of the deal (f _ amt _ pay). f _ uid corresponds to field uid in table a; f _ age corresponds to field age in Table A; f _ shop _ id corresponds to field shop _ id in table C; f _ datetime corresponds to field datetime in table E; f _ amt _ pay corresponds to field amt _ pay in table E. In the example shown in fig. 2, the tag configuration area 202 presents tags: the client status (status _ code), client number (cons _ no), town and country category (urban _ road), and settlement mode (sette _ mode) respectively correspond to the fields in the physical table: status _ code, cons _ no, url _ run, and search _ mode. After the user selects the tag, a database SQL query statement may be automatically generated to obtain the content of the corresponding data object in the database.
By the method, the user can access the bottom database through the label without knowing the details of the table and the field of the bottom database, and the analysis related to the service is completed.
Fig. 3B illustrates a flow diagram of a data processing method according to another embodiment of the present disclosure.
As shown in fig. 3B, the data processing method includes the following steps S305 to S307.
In step S305, a tag corresponding to the data object is established.
In step S306, a data access request automatically generated based on the selection for the tag is received.
In step S307, in response to the data access request, the content of the data object corresponding to the tag is provided.
According to the embodiment of the present disclosure, the main body for selecting the tag may be an automatic selection in the program execution process, except for the user, for example, in the program execution process, the tag is automatically selected according to a certain calculation result or judgment result obtained before, so as to realize access to the data object corresponding to the tag. The data object is accessed through the tag, the technical details of a bottom data source (such as a database) can be shielded for the main body of the accessed data object, and complex access sentences do not need to be written for the bottom database in the data access process, so that convenience is brought to users, the program design is simplified, and the program operation efficiency is improved.
According to an embodiment of the present disclosure, in the method described with reference to fig. 3A or 3B, the data access request is generated based on a user-selected tag and a type of data source in which a data object corresponding to the tag is located. Specifically, the data sources may be of different types, and the user may specify the data source or the type of the data source that the user wants to access while selecting the tag, or may automatically determine the data source or the type of the data source according to the tag attribute, and automatically generate a data access request in a corresponding query language and syntax according to the type of the data source, thereby implementing access to multiple data sources of different types.
According to an embodiment of the present disclosure, the content of the data object is a physical table content or a result obtained by performing an operation on the physical table content; or the content of the data object is a proper subset of the content of the physical table or a result obtained by operating on the proper subset; or the content of the data object is field content in a physical table or a result obtained by operating the field content.
The content of the data object may be the content of the entire physical table, or may be a proper subset of the content of the physical table, such as a set of several field contents or a set of specific records in several field contents, or may be the content of a single field in the physical table. According to an embodiment of the present disclosure, a field may be a column in a physical table and a record may be a row in the physical table. Alternatively, the contents of the data object may be the result of an operation on the contents of the physical table or a proper subset of the contents of the physical table or the contents of a field. For example, assume that the physical table includes two fields: and (3) establishing a label of 'monthly average consumption amount' according to the registration date and the total consumption amount, wherein the content of the data object corresponding to the label can be calculated according to the contents of the two fields of the registration date and the total consumption amount. Alternatively, assume that the physical table includes the fields: the average daily visitation amount may be set up as a label, "average monthly visitation amount", and the content of the data object corresponding to the label may be calculated according to the content of the field, average daily visitation amount. Therefore, labels can be established more flexibly according to business requirements on the basis of existing database records, and business personnel can use the labels more conveniently.
According to an embodiment of the present disclosure, the creating a tag corresponding to a data object includes: for data objects associated with a particular subject, a corresponding tag is established.
The particular subject associated with a data object may be an entity or a relationship. For example, the tag f _ shop _ id may correspond to the field shop _ id of the table C of the seller 120 (entity) in fig. 1, and the tag f _ shop _ id may correspond to the field shop _ id of the table E of the relationship 150 (relationship). The label is established for the data object associated with the specific main body, so that the user can conveniently identify the label needed to be used and can conveniently carry out classification management on the label.
According to an embodiment of the present disclosure, the establishing a corresponding tag for a data object associated with a specific subject includes: generating, for data objects associated with a particular subject, respective tags; or binding an existing tag to the particular principal.
According to the embodiment of the present disclosure, a data object associated with a specific subject may have a corresponding tag, and at this time, the tag may be bound to the specific subject, or a data object associated with a specific subject may not have a corresponding tag, and at this time, a corresponding tag needs to be generated for the data object associated with the specific subject, and then, the tag may be bound to the specific subject.
According to an embodiment of the present disclosure, the establishing a corresponding tag for a data object associated with a specific subject includes: when the specific subject is an entity, establishing a main label aiming at a data object for uniquely identifying the entity, and establishing a common label aiming at other data objects related to the entity; when the specific subject is a relationship, respectively establishing main tags for a plurality of data objects for uniquely identifying the relationship to form a main tag group for uniquely identifying the relationship, and establishing common tags for other data objects related to the relationship.
For example, in table a and table B of fig. 1, uid (user identification) is a field that uniquely identifies a user, and thus the tag f _ uid is a master tag, and the other tags are ordinary tags. The shop _ id (store identification) in table C is a field that uniquely identifies the store, so f _ shop _ id is the master tag. When modeling a relationship, the relationship may consist of two or more associated entities, and the primary tags of the two or more entities may be grouped into a primary tag group of the relationship for uniquely identifying a relationship. The relationship may also be associated with only one entity, and then several main tags and the main tags of the entity may be assigned to form a main tag group of the relationship. For example, if a person runs red light at the xx place at xx time, if only the main tag (person id) of the person is used, if the person runs red light for multiple times, multiple records are recorded, and the requirement that the main tag uniquely determines an object is not met, a field (such as 'red light running time') can be selected from the relation data and combined with the person id to form a main tag group, so that the red light running record (relation) of the person can be uniquely agreed by the person id + the red light running time. By establishing the main tags and the main tag groups, each record in the database table can be distinguished conveniently, and the operation efficiency of the database is improved.
According to an embodiment of the present disclosure, the establishing the tags corresponding to the data objects includes respectively establishing corresponding tags for different data objects distributed in different data sources.
According to an embodiment of the present disclosure, the data source may be a physical table. For example, in FIG. 1, for the entity buyer 110, a tag may be established: the system comprises a user identification (f _ uid), an age (f _ age) and an average monthly consumption amount (f _ avg _ sped), wherein fields corresponding to the f _ uid and the f _ age are in a table A, fields corresponding to the f _ avg _ sped are in a table B, and the table A and the table B are different data sources. Because the fields of the physical tables are relatively fixed and the business models are very different, a single physical table may not meet the requirements of the business models, and the diversified requirements of the business models can be met by establishing the labels for the specific main bodies in a cross-table mode.
According to an embodiment of the present disclosure, when the data access request relates to the different data sources, generating a federated data source based on the different data sources; obtaining content of the data object corresponding to the tag from the federated data source.
For example, in the above example, when a data query request requiring a cross-table query is received, for example, when a data query request simultaneously relating to the age (age) of the user and the average monthly consumption amount (avg _ sped) is received, a large data table is generated by combining the table a and the table B, and the field contents corresponding to the above tags are obtained from the large data table. This can avoid repeated queries in multiple data tables, improve system execution efficiency, and avoid omissions. Moreover, the user only needs to select the label without paying attention to the bottom cross-table access details, and does not need to write cross-table access statements by himself, so that great convenience is brought to the user.
According to an embodiment of the present disclosure, the generating a federated data source based on the different data sources includes: when the different data sources are of different types, generating the federated data source based on the different types of data sources, the data in the federated data source complying with the same storage and access rules. In particular, when the types of data sources to be accessed are different, federated data sources may first be generated based on these different types of data sources, with the data in the federated data sources following the same storage and access rules, thereby enabling access across the different types of data sources. For example, the two databases to be accessed are an Oracle database and an SQL database, respectively, the SQL union database may be generated based on the association and correspondence between the data in the two databases, and the SQL union database may be accessed. In this way, access to different types of data sources may be achieved.
According to an embodiment of the present disclosure, the data access request is generated based on a user-selected tag and a type of a data source in which a data object corresponding to the tag is located.
FIG. 4 shows a flow diagram of a data access method according to an embodiment of the present disclosure.
As shown in fig. 4, the data access method according to the embodiment of the present disclosure includes steps S401 to S403.
In step S401, a tag corresponding to the data object is presented;
in step S402, in response to the user selecting the tag, a data access request is automatically generated;
in step S403, the content of the data object corresponding to the tag returned in response to the data access request is received.
According to the embodiment of the disclosure, the user may be a business person of an enterprise, or may be another person who wants to use the database.
For example, as shown in FIG. 2, the exemplary user interface includes a candidate tab area 201, a chart configuration area 202, and a chart display area 203. As an example, the candidate tag area shows 4 different tags, each tag corresponding to a different field in the physical table, and the number and specific content of the tags can be automatically configured according to the current business scenario of the user. For example, a service scenario to which the tag is applicable may be set when the tag is established, so that the tag to be displayed may be automatically determined according to the current service scenario.
For example, when a user is to perform a statistical analysis on the user's power usage, the candidate tag area 201 may display tags: the client status (status _ code), client number (cons _ no), town and country category (urban _ road), and settlement mode (sette _ mode) respectively correspond to the fields in the physical table: status _ code, cons _ no, url _ run, and search _ mode.
Assuming that the data that the user wants to Count is the number of users in different user states, the tab user state (status _ code) may be dragged to the "select X-axis" input box of the chart configuration area 202, the tab client number (cons _ no) may be dragged to the "select Y-axis" input box of the chart configuration area 202, and then the Count "may be selected in the" aggregation function "input box, and the" histogram "may be selected in the" statistical chart "input box. According to the label selected by the user, the system automatically determines the field in the physical table corresponding to the label, generates a data access request and acquires field data. The field data is processed according to the aggregation function selected by the user and displayed in the graph display area 203 in the form of a histogram.
As can be seen from the above examples, according to the embodiments of the present disclosure, a user does not need to know the underlying technology of database access, but can conveniently access database data simply by selecting a tag, which provides great convenience to the user. Particularly, due to the rapid development of computer technology, the update iteration of database technology is also very rapid, and business personnel are required to be skilled in the latest database technology like professional developers, which undoubtedly will seriously affect the production and operation efficiency and increase the enterprise cost for enterprises. Through the technology disclosed by the invention, the database bottom technology can be shielded for business personnel, when the database technology is updated, only developers need to modify the label system correspondingly, the business system is less affected, and the business personnel also do not need to be trained additionally.
According to an embodiment of the present disclosure, the content of the data object is a physical table content or a result obtained by performing an operation on the physical table content; or the content of the data object is a proper subset of the content of the physical table or a result obtained by operating on the proper subset; or the content of the data object is field content in a physical table or a result obtained by operating the field content.
The content of the data object may be the content of the entire physical table, or may be a proper subset of the content of the physical table, such as a set of several field contents or a set of specific records in several field contents, or may be the content of a single field in the physical table. According to an embodiment of the present disclosure, a field may be a column in a physical table and a record may be a row in the physical table. Alternatively, the contents of the data object may be the result of an operation on the contents of the physical table or a proper subset of the contents of the physical table or the contents of a field. For example, assume that the physical table includes two fields: and (3) establishing a label of 'monthly average consumption amount' according to the registration date and the total consumption amount, wherein the content of the data object corresponding to the label can be calculated according to the contents of the two fields of the registration date and the total consumption amount. Alternatively, assume that the physical table includes the fields: the average daily visitation amount may be set up as a label, "average monthly visitation amount", and the content of the data object corresponding to the label may be calculated according to the content of the field, average daily visitation amount. Therefore, labels can be established more flexibly according to business requirements on the basis of existing database records, and business personnel can use the labels more conveniently.
FIG. 5 shows a flow diagram of a data access method according to an embodiment of the present disclosure.
Fig. 5 includes step S404, in addition to steps S401 to S403 which are the same as those of fig. 4.
In step S404, a particular subject associated with the tag is presented.
For example, while presenting the tag user identification (f _ uid), age (f _ age), the entities associated with these two tags may also be presented: the buyer 110, while displaying the label deal date (f _ datetime) and the deal amount (f _ amt _ pay), may also display the deal relationship 150 associated with the two labels. In this way, it is convenient for the user to know to which entity or relationship the tag corresponds.
According to an embodiment of the present disclosure, the automatically generating a data access request in response to a user selecting the tag includes: and when the data objects corresponding to the tags are distributed in different data sources, automatically generating a cross-data-source data access request.
According to an embodiment of the present disclosure, the data source may be a physical table. For example, in FIG. 1, for the entity buyer 110, a tag may be established: the system comprises a user identification (f _ uid), an age (f _ age) and an average monthly consumption amount (f _ avg _ sped), wherein fields corresponding to the f _ uid and the f _ age are in a table A, fields corresponding to the f _ avg _ sped are in a table B, and the table A and the table B are different data sources. Because the fields of the physical tables are relatively fixed and the business models are very different, a single physical table may not meet the requirements of the business models, and the diversified requirements of the business models can be met by establishing the labels for the specific main bodies in a cross-table mode.
According to the embodiment of the disclosure, when the data objects corresponding to the tags are distributed in different data sources, cross-data-source data access requests are automatically generated.
For example, in the above example, a data access request across data sources is automatically generated upon receiving a data query request that requires a cross-table query, such as upon receiving a data query request that relates to both the user age (age) and the average monthly consumption amount (avg _ span). This can avoid repeated queries in multiple data tables, improve system execution efficiency, and avoid omissions. Moreover, the user only needs to select the label without paying attention to the bottom cross-table access details, and does not need to write cross-table access statements by himself, so that great convenience is brought to the user.
Fig. 6 shows a block diagram of a data processing apparatus according to an embodiment of the present disclosure.
As shown in fig. 6, a data processing apparatus 600 according to an embodiment of the present disclosure includes:
a tag establishing module 601, configured to establish a tag corresponding to a data object;
a label display module 602, configured to display the label;
a data access request receiving module 603, configured to receive a data access request automatically generated after the user selects the tag;
a data object content providing module 604 for providing the content of the data object corresponding to the tag to the user in response to the data access request.
According to an embodiment of the present disclosure, the content of the data object is a physical table content or a result obtained by performing an operation on the physical table content; or the content of the data object is a proper subset of the content of the physical table or a result obtained by operating on the proper subset; or the content of the data object is field content in a physical table or a result obtained by operating the field content.
According to an embodiment of the present disclosure, the creating a tag corresponding to a data object includes: for data objects associated with a particular subject, a corresponding tag is established.
According to an embodiment of the present disclosure, the establishing a corresponding tag for a data object associated with a specific subject includes: generating a respective tag for a data object associated with a particular principal and binding the respective tag with the particular principal; or binding an existing tag to the particular principal.
According to an embodiment of the present disclosure, the specific subject includes an entity or a relationship.
According to an embodiment of the present disclosure, the establishing a corresponding tag for a data object associated with a specific subject includes: when the specific subject is an entity, establishing a main label aiming at a data object for uniquely identifying the entity, and establishing a common label aiming at other data objects related to the entity; when the specific subject is a relationship, respectively establishing main tags for a plurality of data objects for uniquely identifying the relationship to form a main tag group for uniquely identifying the relationship, and establishing common tags for other data objects related to the relationship.
According to an embodiment of the present disclosure, the establishing the tags corresponding to the data objects includes respectively establishing corresponding tags for different data objects distributed in different data sources.
According to an embodiment of the present disclosure, when the data access request relates to the different data sources, generating a federated data source based on the different data sources; obtaining content of the data object corresponding to the tag from the federated data source.
According to an embodiment of the present disclosure, the generating a federated data source based on the different data sources includes: when the different data sources are of different types, generating the federated data source based on the different types of data sources, the data in the federated data source complying with the same storage and access rules. In particular, when the types of data sources to be accessed are different, federated data sources may first be generated based on these different types of data sources, with the data in the federated data sources following the same storage and access rules, thereby enabling access across the different types of data sources. For example, the two databases to be accessed are an Oracle database and an SQL database, respectively, the SQL union database may be generated based on the association and correspondence between the data in the two databases, and the SQL union database may be accessed. In this way, access to different types of data sources may be achieved.
According to an embodiment of the present disclosure, the data access request is generated based on a user-selected tag and a type of a data source in which a data object corresponding to the tag is located.
Fig. 7 shows a block diagram of a data access device according to an embodiment of the present disclosure.
As shown in fig. 7, a data access apparatus 700 according to an embodiment of the present disclosure includes:
a tag display module 701 for displaying tags corresponding to the data objects;
a data access request generation module 702, configured to automatically generate a data access request in response to a user selecting the tag;
a data object content returning module 703, configured to receive the content of the data object corresponding to the tag returned in response to the data access request.
According to an embodiment of the present disclosure, the content of the data object is a physical table content or a result obtained by performing an operation on the physical table content; or the content of the data object is a proper subset of the content of the physical table or a result obtained by operating on the proper subset; or the content of the data object is field content in a physical table or a result obtained by operating the field content.
FIG. 8 shows a block diagram of a data access device according to an embodiment of the present disclosure.
In FIG. 8, the data access device 800 includes additional modules in addition to the same modules 701-703 as in FIG. 7:
a specific subject display module 704 for displaying a specific subject associated with the label.
According to an embodiment of the present disclosure, the automatically generating a data access request in response to a user selecting the tag includes: and when the data objects corresponding to the tags are distributed in different data sources, automatically generating a cross-data-source data access request.
Fig. 9 shows a block diagram of a computer system according to an embodiment of the present disclosure.
As shown in fig. 9, the computer system 900 includes a memory 901 and a processor 902. The memory 901 is used for storing one or more computer instructions, wherein the one or more computer instructions are executed by the processor 902 for implementing the following method steps:
establishing a label corresponding to the data object;
displaying the label;
receiving a data access request automatically generated after a user selects the tag;
providing the content of the data object corresponding to the tag to the user in response to the data access request.
According to an embodiment of the present disclosure, the content of the data object is a physical table content or a result obtained by performing an operation on the physical table content; or
The content of the data object is a proper subset of the content of the physical table or a result obtained by operating on the proper subset; or
The content of the data object is field content in a physical table or a result obtained by operating on the field content.
According to embodiments of the present disclosure, respective tags are established for data objects associated with a particular subject.
According to an embodiment of the present disclosure, the establishing a corresponding tag for a data object associated with a specific subject includes:
generating a respective tag for a data object associated with a particular principal and binding the respective tag with the particular principal; or
Binding an existing tag with the particular principal.
According to an embodiment of the present disclosure, the specific subject includes an entity or a relationship.
According to an embodiment of the present disclosure, the establishing a corresponding tag for a data object associated with a specific subject includes:
when the specific subject is an entity, establishing a main label aiming at a data object for uniquely identifying the entity, and establishing a common label aiming at other data objects related to the entity;
when the specific subject is a relationship, respectively establishing main tags for a plurality of data objects for uniquely identifying the relationship to form a main tag group for uniquely identifying the relationship, and establishing common tags for other data objects related to the relationship.
According to an embodiment of the present disclosure, the establishing the tags corresponding to the data objects includes respectively establishing corresponding tags for different data objects distributed in different data sources.
According to an embodiment of the present disclosure, the method further comprises:
generating a federated data source based on the different data sources when the data access request involves the different data sources;
obtaining content of the data object corresponding to the tag from the federated data source.
According to an embodiment of the present disclosure, the generating a federated data source based on the different data sources includes:
when the different data sources are of different types, generating the federated data source based on the different types of data sources, the data in the federated data source complying with the same storage and access rules.
According to the embodiment of the disclosure, the data access request is generated based on the label selected by the user and the type of the data source where the data object corresponding to the label is located.
The one or more computer instructions, when executed by the processor 902, may further implement the method steps of:
displaying a label corresponding to the data object;
automatically generating a data access request in response to a user selecting the tag;
receiving the content of the data object corresponding to the tag returned in response to the data access request.
According to an embodiment of the present disclosure, the content of the data object is a physical table content or a result obtained by performing an operation on the physical table content; or the content of the data object is a proper subset of the content of the physical table or a result obtained by operating on the proper subset; or the content of the data object is field content in a physical table or a result obtained by operating the field content.
According to an embodiment of the present disclosure, the method further comprises: a particular subject associated with the tag is presented.
According to an embodiment of the present disclosure, the automatically generating a data access request in response to a user selecting the tag includes: and when the data objects corresponding to the tags are distributed in different data sources, automatically generating a cross-data-source data access request.
Fig. 10 shows a schematic structural diagram of a computer system suitable for implementing a data processing method and/or a data access method according to an embodiment of the present disclosure.
As shown in fig. 10, the computer system 1000 includes a Central Processing Unit (CPU)1001 that can execute various processes in the above-described embodiments in accordance with a program stored in a Read Only Memory (ROM)1002 or a program loaded from a storage section 1009 into a Random Access Memory (RAM) 1003. In the RAM1003, various programs and data necessary for the operation of the system 1000 are also stored. The CPU1001, ROM1002, and RAM1003 are connected to each other via a bus 1004. An input/output (I/O) interface 1005 is also connected to bus 1004.
The following components are connected to the I/O interface 1005: an input section 1006 including a keyboard, a mouse, and the like; an output section 1007 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 1008 including a hard disk and the like; and a communication section 1009 including a network interface card such as a LAN card, a modem, or the like. The communication section 1009 performs communication processing via a network such as the internet. The driver 1010 is also connected to the I/O interface 1005 as necessary. A removable medium 1011 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1010 as necessary, so that a computer program read out therefrom is mounted into the storage section 1008 as necessary.
In particular, the above described methods may be implemented as computer software programs according to embodiments of the present disclosure. For example, embodiments of the present disclosure include a computer program product comprising a computer program tangibly embodied on a readable medium thereof, the computer program containing program code for performing the above-described data processing and/or accessing methods. In such an embodiment, the computer program may be downloaded and installed from a network through the communication part 1009 and/or installed from the removable medium 1011.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowcharts or block diagrams may represent a module, a program segment, or a portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units or modules described in the embodiments of the present disclosure may be implemented by software or by programmable hardware. The units or modules described may also be provided in a processor, and the names of the units or modules do not in some cases constitute a limitation of the units or modules themselves.
As another aspect, the present disclosure also provides a readable storage medium, which may be a readable storage medium contained in the electronic device or the computer system in the above embodiments; or may be a separately present, non-built-in, readable storage medium. The readable storage medium stores one or more programs for use by one or more processors in performing the methods described in the present disclosure.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by a person skilled in the art that the scope of the invention as referred to in the present disclosure is not limited to the specific combination of the above-mentioned features, but also covers other embodiments formed by any combination of the above-mentioned features or their equivalents without departing from the inventive concept. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.

Claims (20)

1. A data processing method, comprising:
establishing a label corresponding to the data object;
displaying the label;
receiving a data access request automatically generated after a user selects the tag;
providing the content of the data object corresponding to the tag to the user in response to the data access request.
2. The method of claim 1, wherein:
the content of the data object is the content of a physical table or a result obtained by operating the content of the physical table; or
The content of the data object is a proper subset of the content of the physical table or a result obtained by operating on the proper subset; or
The content of the data object is field content in a physical table or a result obtained by operating on the field content.
3. The method of claim 1, wherein the creating tags corresponding to data objects comprises:
for data objects associated with a particular subject, a corresponding tag is established.
4. The method of claim 3, wherein establishing respective tags for data objects associated with a particular subject comprises:
generating a respective tag for a data object associated with a particular principal and binding the respective tag with the particular principal; or
Binding an existing tag with the particular principal.
5. The method of claim 3, wherein the particular principal comprises an entity or a relationship.
6. The method of claim 5, wherein establishing respective tags for data objects associated with a particular subject comprises:
when the specific subject is an entity, establishing a main label aiming at a data object for uniquely identifying the entity, and establishing a common label aiming at other data objects related to the entity;
when the specific subject is a relationship, respectively establishing main tags for a plurality of data objects for uniquely identifying the relationship to form a main tag group for uniquely identifying the relationship, and establishing common tags for other data objects related to the relationship.
7. The method of claim 1, wherein establishing tags corresponding to the data objects comprises establishing corresponding tags for different data objects distributed in different data sources.
8. The method of claim 7, further comprising:
generating a federated data source based on the different data sources when the data access request involves the different data sources;
obtaining content of the data object corresponding to the tag from the federated data source.
9. The method of claim 8, wherein generating the federated data source based on the disparate data sources comprises:
when the different data sources are of different types, generating the federated data source based on the different types of data sources, the data in the federated data source complying with the same storage and access rules.
10. The method of claim 1, wherein the data access request is generated based on a user-selected tag and a type of data source in which a data object corresponding to the tag is located.
11. A data processing method, comprising:
establishing a label corresponding to the data object;
receiving a data access request automatically generated based on a selection for the tag;
providing content of the data object corresponding to the tag in response to the data access request.
12. A method of data access, comprising:
displaying a label corresponding to the data object;
automatically generating a data access request in response to a user selecting the tag;
receiving the content of the data object corresponding to the tag returned in response to the data access request.
13. The method of claim 12, wherein:
the content of the data object is the content of a physical table or a result obtained by operating the content of the physical table; or
The content of the data object is a proper subset of the content of the physical table or a result obtained by operating on the proper subset; or
The content of the data object is field content in a physical table or a result obtained by operating on the field content.
14. The method of claim 12, further comprising:
a particular subject associated with the tag is presented.
15. The method of claim 12, wherein automatically generating a data access request in response to a user selecting the tag comprises:
and when the data objects corresponding to the tags are distributed in different data sources, automatically generating a cross-data-source data access request.
16. A data processing apparatus, comprising:
the tag establishing module is used for establishing tags corresponding to the data objects;
the label display module is used for displaying the label;
the data access request receiving module is used for receiving a data access request automatically generated after the user selects the tag;
and the data object content providing module is used for responding to the data access request and providing the content of the data object corresponding to the label to the user.
17. A data access device, comprising:
the label display module is used for displaying labels corresponding to the data objects;
the data access request generation module is used for responding to the label selected by the user and automatically generating a data access request;
a data object content return module for receiving the content of the data object corresponding to the tag returned in response to the data access request.
18. The apparatus of claim 17, further comprising:
a specific body display module for displaying a specific body associated with the tag.
19. A computer system comprising a memory and a processor; wherein the memory is to store one or more computer instructions, wherein the one or more computer instructions are to be executed by the processor to implement the method steps of any one of claims 1-15.
20. A readable storage medium having stored thereon computer instructions, characterized in that the computer instructions, when executed by a processor, carry out the method steps of any of claims 1-15.
CN201911222491.3A 2019-12-03 2019-12-03 Data processing and accessing method, device, computer system and readable storage medium Pending CN112905586A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911222491.3A CN112905586A (en) 2019-12-03 2019-12-03 Data processing and accessing method, device, computer system and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911222491.3A CN112905586A (en) 2019-12-03 2019-12-03 Data processing and accessing method, device, computer system and readable storage medium

Publications (1)

Publication Number Publication Date
CN112905586A true CN112905586A (en) 2021-06-04

Family

ID=76104724

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911222491.3A Pending CN112905586A (en) 2019-12-03 2019-12-03 Data processing and accessing method, device, computer system and readable storage medium

Country Status (1)

Country Link
CN (1) CN112905586A (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104572813A (en) * 2014-11-26 2015-04-29 国家电网公司 Report generation method and device
CN105159920A (en) * 2015-07-28 2015-12-16 卡斯柯信号有限公司 Attribute tag based database access method
CN107515866A (en) * 2016-06-15 2017-12-26 阿里巴巴集团控股有限公司 A kind of data manipulation method, device and system
CN108153808A (en) * 2017-11-22 2018-06-12 链家网(北京)科技有限公司 Big data data warehouse data access method and device
CN109144501A (en) * 2018-08-30 2019-01-04 杭州数澜科技有限公司 A kind of method and system generating API by label
CN109840257A (en) * 2018-12-15 2019-06-04 中国平安人寿保险股份有限公司 Data base query method, device, computer installation and readable storage medium storing program for executing
CN110377649A (en) * 2019-06-17 2019-10-25 中国平安财产保险股份有限公司 Building, querying method, device, equipment and the storage medium of labeling data

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104572813A (en) * 2014-11-26 2015-04-29 国家电网公司 Report generation method and device
CN105159920A (en) * 2015-07-28 2015-12-16 卡斯柯信号有限公司 Attribute tag based database access method
CN107515866A (en) * 2016-06-15 2017-12-26 阿里巴巴集团控股有限公司 A kind of data manipulation method, device and system
CN108153808A (en) * 2017-11-22 2018-06-12 链家网(北京)科技有限公司 Big data data warehouse data access method and device
CN109144501A (en) * 2018-08-30 2019-01-04 杭州数澜科技有限公司 A kind of method and system generating API by label
CN109840257A (en) * 2018-12-15 2019-06-04 中国平安人寿保险股份有限公司 Data base query method, device, computer installation and readable storage medium storing program for executing
CN110377649A (en) * 2019-06-17 2019-10-25 中国平安财产保险股份有限公司 Building, querying method, device, equipment and the storage medium of labeling data

Similar Documents

Publication Publication Date Title
US20180292959A1 (en) Systems and methods for analyzing performance of an entity
Ponniah Data warehousing fundamentals for IT professionals
US7634478B2 (en) Metadata driven intelligent data navigation
US7818342B2 (en) Tracking usage of data elements in electronic business communications
US9075859B2 (en) Parameterized database drill-through
US8819075B2 (en) Facilitation of extension field usage based on reference field usage
CN110674228A (en) Data warehouse model construction and data query method, device and equipment
US20080294596A1 (en) System and method for processing queries for combined hierarchical dimensions
US20110145286A1 (en) Distributed platform for network analysis
CN102541867A (en) Data dictionary generating method and system
US7970735B2 (en) Cross varying dimension support for analysis services engine
US7720842B2 (en) Value-chained queries in analytic applications
US20070239742A1 (en) Determining data elements in heterogeneous schema definitions for possible mapping
US11868406B2 (en) Smart interactions for a digital duplicate
JP2008511928A (en) Metadata management
JP2008511936A (en) Method and system for semantic identification in a data system
US20180018372A1 (en) Semantic tagging of nodes
CN110675238A (en) Client label configuration method, system, readable storage medium and electronic equipment
US9336245B2 (en) Systems and methods providing master data management statistics
CN111414410A (en) Data processing method, device, equipment and storage medium
US8707262B2 (en) Code scoring
CN113535966A (en) Knowledge graph creating method, information obtaining method, device and equipment
CN112905586A (en) Data processing and accessing method, device, computer system and readable storage medium
US20130325867A1 (en) Ide integrated catalog and ddic-bridge for in-memory database views
US11068138B2 (en) Report management system

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