CN114090653A

CN114090653A - Resource data statistical method and device, meta-platform equipment and storage medium

Info

Publication number: CN114090653A
Application number: CN202111364567.3A
Authority: CN
Inventors: 陈志鸿; 郭孔泉; 倪鹏; 裴连火; 黄忠魁
Original assignee: China Communication Service Application And Solution Technology Co ltd
Current assignee: China Communication Service Application And Solution Technology Co ltd
Priority date: 2021-11-17
Filing date: 2021-11-17
Publication date: 2022-02-25

Abstract

The invention relates to the technical field of data application, and discloses a resource data statistical method, a device, a meta-platform device and a storage medium, namely, after a metadata model which is used for establishing a resource database according to a large modeling principle and can cover all entity information and a database storage mode is established, a pre-designed template which can configure the metadata is used for page configuration, the metadata and corresponding conditions which need to be counted are extracted by configuring entity specifications, statistical conditions and statistical attributes, SQL sentences used for database statistics are spliced according to statistical rules, and finally, SQL sentences are executed through a database to realize the statistical requirement of application page configurability, so that the purposes of application intensive management, model configurability and metadata driving interface can be realized by using a metadata model example business language, and the reusability of statistical application can be improved to the maximum extent, complicated development details are shielded, development cost is finally reduced, and operation efficiency is improved.

Description

Resource data statistical method and device, meta-platform device and storage medium

Technical Field

The invention belongs to the technical field of data application, particularly relates to the aspects of application and implementation of entity datamation and application of a data updating algorithm, and particularly provides a resource data statistical method, a device, meta-platform equipment and a storage medium.

Background

In a simple way, the meta-platform describes the business model through the metadata and realizes mapping from the entity, the relationship and the component to the relationship model, so that the upper-layer application can directly realize the application through the metadata, the complex details of the database are shielded, the application development burden is reduced, and the statistical report is displayed on the corresponding data.

In the enterprise development process, various enterprise data statistics applications have the characteristics of diversification and business complexity, and a statistics tool needing to provide support must have the characteristics of quickness, readiness, flexibility, configurability and support of business diversity. However, the traditional resource data model is based on a one-to-one 'hard modeling' mode, and the relationship construction is very complex, so that the traditional statistical application method has the following defects: (1) because the real concepts are subjected to one-to-one tabled 'hard modeling', the relationships among the concepts are dispersed in each storage table of the real concepts; (2) the concept addition and change can affect the data table; (3) both the new addition and the change of the relationship can influence the Schema of the data table; (4) the application cannot be supported through metadata drive, and the problems of modification of a meta-table structure and shutdown and restart are caused; (5) the statistics of the entity requirements cannot be directly carried out, and additional development of functions is required.

Disclosure of Invention

In order to solve the above-mentioned deficiency problem of the traditional statistical application method, the present invention aims to provide a novel resource data statistical method, apparatus, meta-platform device and computer readable storage medium, which can use a metadata model instance service language to achieve the purposes of application intensive management, model configuration and metadata driven interface, and further can quickly support the statistical functions of data extraction and multidimensional reporting, thereby maximally improving the reusability of statistical application, shielding complex development details, finally reducing development cost and improving operation efficiency.

In a first aspect, the present invention provides a resource data statistics method, including:

establishing a metadata model of a resource database according to a major modeling principle, wherein the resource database is used for storing data information of all product entities, the metadata model comprises database table metadata, field metadata, entity specification metadata, relationship specification metadata and relationship metadata, a base table in the database table metadata comprises all tables in the resource database, fields in the field metadata comprise all fields in the resource database, an entity specification in the entity specification metadata comprises major entities, fine entities and specification entities, the major entities are entity classes distinguished according to different product functions, product attributes and/or product characteristics, the fine entities are entity classes distinguished according to different product purposes for the major entities, and the specification entities are entity classes distinguished according to different specific service objects and relationships for the fine entities The relationship specification in the relationship specification metadata comprises a large-class relationship, a fine-class relationship and a specification relationship, the large-class relationship refers to the relationship between one large-class entity and another large-class entity, the fine-class entity refers to the relationship between one fine-class entity and another fine-class entity, the specification relationship refers to the relationship between one specification entity and another specification entity, and the relationship in the relationship metadata comprises the relationship between a library table and an entity specification and the relationship between the library table and a relationship specification;

responding to user operation, and acquiring a template to be configured, which meets the requirement of a user statistical form, from a template model, wherein the template model comprises a plurality of pre-designed templates which are used for transmitting required metadata to the metadata model after parameter configuration;

displaying the template to be configured on a man-machine interaction page;

obtaining a configured template according to configuration parameters input on the template to be configured, wherein the configuration parameters comprise a selection result aiming at an entity specification, a selection result aiming at a statistical condition and a selection result aiming at a statistical attribute;

transmitting required metadata to the metadata model according to the configured template to obtain metadata to be counted, wherein the metadata to be counted comprises base table metadata and field metadata searched according to the configuration parameters;

splicing Structured Query Language (SQL) statements used for database statistics according to statistical rules and the metadata needing to be counted;

and executing the Structured Query Language (SQL) statement on the resource database to obtain a statistical result.

Based on the invention content, a meta-platform service scheme for carrying out resource data statistics based on metadata and templates is provided, namely, after a metadata model which is used for a resource database and can cover all entity information and database storage modes is established according to a large modeling principle, a pre-designed template which enables the metadata to be configurable is used for carrying out page configuration, the metadata and corresponding conditions which need to be counted are extracted by configuring entity specifications, statistical conditions and statistical attributes, SQL sentences used for database statistics are spliced according to statistical rules, and finally, SQL sentences are executed through a database to realize the statistical requirements of the application page configurability, so that the purposes of application intensive management, model configurability and metadata driving interfaces can be realized by using a metadata model instance business language, and further the statistical functions of data extraction, multi-dimensional reports and the like can be supported rapidly, the reusability of statistical application is improved to the maximum extent, complex development details are shielded, the development cost is finally reduced, and the operation efficiency is improved. And the direct access of the application code to the database can be shielded, the translation is carried out by adopting the metadata, the shutdown is not needed, the model can be thermally deployed, and the flexible and quick expansion of the model is ensured. In addition, compared with the conventional statistical application method, the resource data statistical method provided by the embodiment further has the following detailed advantages: (1) modeling is carried out through the major category and the metadata, the relationship between concepts is concentrated on a major table of the major category, and dynamic expansion is carried out by utilizing the metadata; (2) defining the convergence dimension and the convergence granularity of the large-class modeling, and theoretically ensuring the rationality of the large-class modeling; (3) triggering from the perspective of resource application, determining the management granularity of a resource business object, and constructing a resource specification catalog; (4) the result of the large-scale modeling can be demonstrated and verified, and the IT language can be effectively translated into the business language; (5) the cloud platform can basically keep the stability of the core large class and the relationship entity, only inherits and expands the relationship and the attribute of the large class entity, updates the metadata on line and adds the expansion table (optional) for support without stopping the cloud platform! (6) All business entities and database attributes are summarized on the cloud platform based on the support of two sets of models, and correct SQL statements are driven to access the database to realize statistics by directly operating the necessary information provided in the metadata.

In one possible design, the metadata model further includes specification attribute metadata, where a specification attribute in the specification attribute metadata is used to record whether an attribute component is shown, filled, readable, updatable, multiple options supported, and/or default values, and the attribute component refers to a component formed by grouping attributes of an entity specification/relationship specification.

In one possible design, the metadata model further includes dictionary value metadata and dictionary type metadata, where a dictionary value in the dictionary value metadata includes a stored data key and entry pair, and a dictionary type in the dictionary type metadata includes all grouping classifications for a dictionary value required for an attribute;

the relationship in the relationship metadata further includes a relationship between the specification attribute and the dictionary value and a relationship between the dictionary type and the dictionary value.

In one possible design, the metadata model further includes domain metadata, where a domain in the domain metadata includes different regions of all product entities;

the relationship in the relationship metadata further includes a relationship between the domain and the entity specification.

In one possible design, the template model further includes a menu and a menu application template, where the menu is used to record a required menu directory name and a display tree level, and the menu application template is used to record a relationship between the menu and the template to be configured.

In one possible design, the template to be configured includes template subject information, template relationship information, template attribute information, attribute verification information, template form information, form grouping information, grouping element information, template form information, form element information, and query condition information, wherein the template subject information is used to record template names and associated entity specifications in the metadata model, the template relationship information is used to record relationship specifications used by the template, the template attribute information is used to record specification attributes used by the template, the attribute validation information is used to record attribute verification conditions, the template form information is used to record length, width, and height of a template display form, the form grouping information is used to record page form grouping display names, the grouping element information is used to record attributes and control length, width, and height in a grouping form, the template table information is used for recording the line number of the template table, the table elements are used for recording the attributes displayed by the table, and the query condition information is used for recording the query conditions and the sequence of the template.

In one possible design, after the statistical result is obtained by executing the SQL statement on the resource database, the method further includes:

and displaying the statistical result on the human-computer interaction page, wherein the statistical result comprises a report type statistical result and/or a graphical statistical result, and the graphical statistical result comprises a pie chart statistical result and/or a histogram statistical result.

In a second aspect, the invention provides a resource data statistical device, which comprises a model establishing unit, an operation response unit, a template display unit, a parameter configuration unit, a data transmission unit, a statement splicing unit and a statistical execution unit, wherein the operation response unit, the template display unit, the parameter configuration unit, the data transmission unit, the statement splicing unit and the statistical execution unit are sequentially connected in a communication manner;

the model establishing unit is used for establishing a metadata model of a resource database according to a major modeling principle, wherein the resource database is used for storing data information of all product entities, the metadata model comprises database table metadata, field metadata, entity specification metadata, relationship specification metadata and relationship metadata, a base table in the database table metadata comprises all tables in the resource database, fields in the field metadata comprise all fields in the resource database, an entity specification in the entity specification metadata comprises major entities, minor entities and specification entities, the major entities refer to entity categories distinguished according to different product functions, product attributes and/or product characteristics, and the minor entities refer to entity categories distinguished according to different product purposes for the major entities, the specification entities refer to entity types distinguished according to different specific business objects and relations aiming at the thin-class entities, the relation specifications in the relation specification metadata comprise large-class relations, thin-class relations and specification relations, the large-class relations refer to the relations between one large-class entity and another large-class entity, the thin-class entities refer to the relations between one thin-class entity and another thin-class entity, the specification relations refer to the relations between one specification entity and another specification entity, and the relations in the relation metadata comprise the relations between a base table and an entity specification and the relations between the base table and the relation specification;

the operation response unit is used for responding to user operation and acquiring a template which meets the requirement of a user statistical form and is to be configured from a template model, wherein the template model comprises a plurality of pre-designed templates which are used for transmitting required metadata to the metadata model after parameter configuration;

the template display unit is used for displaying the template to be configured on a man-machine interaction page;

the parameter configuration unit is used for obtaining a configured template according to configuration parameters input on the template to be configured, wherein the configuration parameters comprise a selection result aiming at an entity specification, a selection result aiming at a statistical condition and a selection result aiming at a statistical attribute;

the data transmission unit is used for transmitting required metadata to the metadata model according to the configured template to obtain metadata to be counted, wherein the metadata to be counted comprises base table metadata and field metadata which are searched according to the configuration parameters;

the statement splicing unit is used for splicing Structured Query Language (SQL) statements used for database statistics according to statistical rules and the metadata needing to be counted;

and the statistic execution unit is used for executing the Structured Query Language (SQL) statement on the resource database to obtain a statistic result.

In a third aspect, the present invention provides a meta platform device, including a memory, a processor and a transceiver, which are sequentially connected in communication, wherein the memory is used for storing a computer program, the transceiver is used for transceiving data, and the processor is used for reading the computer program and executing the resource data statistical method according to the first aspect or any possible design of the first aspect.

In a fourth aspect, the present invention provides a computer-readable storage medium having stored thereon instructions which, when run on a computer, perform a resource data statistics method as described in the first aspect or any possible design of the first aspect above.

In a fifth aspect, the present invention provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the resource data statistics method as described in the first aspect or any possible design of the first aspect.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic flow chart of a resource data statistics method provided by the present invention.

FIG. 2 is a schematic diagram of the design patterns and access modes of the broad modeling principles provided by the present invention.

FIG. 3 is a schematic diagram of the application of the broad modeling principle provided by the present invention.

FIG. 4 is a schematic structural diagram of a metadata model provided by the present invention.

FIG. 5 is an exemplary diagram of a metadata model provided by the present invention.

Fig. 6 is a first exemplary diagram of a template management page provided by the present invention.

Fig. 7 is a diagram of a second example of a template management page provided by the present invention.

Fig. 8 is a third exemplary diagram of a template management page provided by the present invention.

Fig. 9 is a schematic structural diagram of the template model provided by the present invention.

Fig. 10 is a functional point diagram of the template provided by the present invention.

FIG. 11 is a functional diagram of a metadata-based implementation provided by the present invention.

FIG. 12 is an exemplary diagram of a design state and an operation state of a template provided by the present invention.

FIG. 13 is a table page display example diagram provided by the present invention.

FIG. 14 is a diagram of a form page display example provided by the present invention.

FIG. 15 is a diagram illustrating a statistical page provided by the present invention.

FIG. 16 is a diagram showing an example of statistical results of a pie chart and a histogram provided by the present invention.

Fig. 17 is a schematic structural diagram of a resource data statistics apparatus provided in the present invention.

Fig. 18 is a schematic structural diagram of a meta-platform device provided by the present invention.

Detailed Description

The invention is further described with reference to the following figures and specific embodiments. It should be noted that the description of the embodiments is provided to help understanding of the present invention, but the present invention is not limited thereto. Specific structural and functional details disclosed herein are merely representative of exemplary embodiments of the invention. This invention may, however, be embodied in many alternate forms and should not be construed as limited to the embodiments set forth herein.

It will be understood that, although the terms first, second, etc. may be used herein to describe various objects, these objects should not be limited by these terms. These terms are only used to distinguish one object from another. For example, a first object may be referred to as a second object, and similarly, a second object may be referred to as a first object, without departing from the scope of example embodiments of the present invention.

It should be understood that, for the term "and/or" as may appear herein, it is merely an associative relationship that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, B exists alone or A and B exist at the same time; for the term "/and" as may appear herein, which describes another associative object relationship, it means that two relationships may exist, e.g., a/and B, may mean: a exists singly or A and B exist simultaneously; in addition, with respect to the character "/" which may appear herein, it generally means that the former and latter associated objects are in an "or" relationship.

As shown in fig. 1 to 16, the resource data statistical method provided in the first aspect of the embodiment can be executed by, but not limited to, a Computer device with certain computing resources, for example, a Personal Computer (PC, which refers to a multipurpose Computer with a size, price and performance suitable for Personal use, and electronic devices such as a desktop Computer, a notebook Computer, a mini-notebook Computer, a tablet Computer, a super Computer, and the like, all belong to a Personal Computer), a smart phone, a Personal digital assistant (PAD), or a wearable device, so as to perform page configuration by using a pre-designed template capable of configuring metadata after establishing a metadata model of a resource database according to a large modeling principle and capable of covering all entity information and database storage modes, and extract metadata and corresponding conditions that need to be counted by configuring entity specifications, statistical conditions, and statistical attributes, then, SQL sentences used for database statistics are spliced according to statistical rules, and finally, the SQL sentences are executed through the database to meet the configurable statistical requirements of application pages, so that metadata model instance business languages can be used, the purposes of application intensive management, model configuration and metadata driving interfaces are achieved, further, the statistical functions of data extraction, multi-dimensional reports and the like can be supported rapidly, the reusability of statistical application is improved to the maximum extent, complex development details are shielded, the development cost is reduced finally, and the operation efficiency is improved. As shown in FIG. 1, the resource data statistics method may include, but is not limited to, the following steps S1-S7.

S1, establishing a metadata model of a resource database according to a major modeling principle, wherein the resource database is used for storing data information of all product entities, the metadata model comprises but is not limited to database table metadata, field metadata, entity specification metadata, relationship metadata and the like, a database table in the database table metadata comprises all tables in the resource database, fields in the field metadata comprise all fields in the resource database, an entity specification in the entity specification metadata comprises major entities, minor entities and specification entities, the major entities refer to entity categories distinguished according to different product functions, product attributes and/or product characteristics, the minor entities refer to entity categories distinguished according to different product purposes of the major entities, the specification entities refer to entity types distinguished according to different specific business objects and relations aiming at the thin-class entities, the relation specifications in the relation specification metadata include a large-class relation, a thin-class relation and a specification relation, the large-class relation refers to the relation between one large-class entity and another large-class entity, the thin-class entity refers to the relation between one thin-class entity and another thin-class entity, the specification relation refers to the relation between one specification entity and another specification entity, and the relations in the relation metadata include but are not limited to the relation between a library table and an entity specification, the relation between a library table and a relation between a relation standard and the relation between the library table and the relation specification, and the like.

In step S1, the large class modeling principle refers to that the large class is divided by a metadata technique and then combined to form a data model of the management object. The design mode and access mode of the large-class modeling principle provided by this embodiment can be as shown in fig. 2, and the structural relationship and application mode can be as shown in fig. 3, and the object is to stabilize the object large class and the relationship large class, further stabilize the physical storage (i.e., the main table and the relationship table), and extend the business object and the business relationship, without adjusting the physical main table and the relationship main table, only do the configuration of metadata, increase the business object and the usage relationship to the main table attribute, and add or use the management attribute of the existing physical extension table if necessary.

In step S1, each metadata in the metadata model is used to describe attribute information of a corresponding object (i.e., a library table, a field, an entity specification, a relationship specification or a relationship, etc.). In detail, the metadata model further includes, but is not limited to, specification attribute metadata, dictionary value metadata, dictionary type metadata, and/or domain metadata, where the specification attributes in the specification attribute metadata are used to record whether attribute components are shown, whether the attribute components must be filled, whether the attribute components are readable, whether the attribute components are updatable, whether multiple choices are supported, and/or default values, the attribute components refer to components formed by grouping attributes of the entity specification/relationship specification, the dictionary values in the dictionary value metadata include storage data key words and entry pairs, the dictionary types in the dictionary type metadata include all grouping classifications for dictionary values required for attributes, the domains in the domain metadata include different regions of all product entities, and the relationships in the relationship metadata further include relationship between the specification attributes and the dictionary values, Dictionary type to dictionary value relationships and/or domain to entity specification relationships. The metadata model structure relationship based on the aforementioned multiple objects is shown in fig. 4 and 5, and the metadata rules of the respective objects and under the broad modeling principle are described one by one below.

(1) Base table (mm _ table): to further embody the purpose and function of managing database tables, a table model is formed: confirming the table name, the primary key and the table type, wherein the table type can be classified into four types: the upper layer application can read out the main key and the purpose of the corresponding table type to judge the application according to the confirmed table name. In addition, the main horizontal table and the extension vertical table can be managed by a large-class entity, and a specification entity can only inherit and redefine and is not allowed to exceed the range of the large-class entity.

(2) Field (mm _ flex): in a database, most of the time, a "column" of a table is called "field", each field contains information of a certain topic, and therefore, corresponding field metadata records attributes of the database field, such as a table, a field size, a format, a default value, whether a field is necessary to be filled, a validity rule, a validity text and/or an index, and the like.

(3) Physical specification (mm _ entity _ spec): an entity is an abstraction of people for physical, logical, and things in the real world; entities can be defined as abstract entities and concrete entities, and there is an inherited relationship between the entities, so this embodiment divides the entities into three categories: the system comprises a large-class entity, a fine-class entity and a specification entity, wherein the large-class entity is a top-level abstraction of a resource model and can be used for managing a main table and a longitudinal table, the fine-class entity is used for managing business objects and relations and constraining an extended table, the management efficiency is improved, the management difficulty is reduced, and the specification entity is content used and understood by business personnel and is used for managing relations, attributes and the extended table.

(4) Relationship specification (mm _ relationship _ spec): relationships are used to describe the relationship between two entity instances, and a variety of relationships can be applied to relationships, such as: container/particle relationships, connection relationships, hierarchical relationships, and the like; for some application scenarios, it is desirable to document the relevant properties on a relationship instance of two entities. For the A and B entities, if their relationship is a one-to-many relationship or a many-to-one relationship, the relationship table may be defined on some attribute of the A entity, and if the A and B entities are many-to-many relationships, an independent relationship table manner is adopted.

(5) Relation of library table and entity/relation specification (mr _ table _ spec): which is used to record the relationship in which the entity specification and relationship specification are specifically stored. Specifically, the relationship rule between the library table and the entity specification is as follows: (a) the large entity can be associated with the main table and the longitudinal table, but can not be associated with two tables of the same type at the same time; (b) the subclass entity is not allowed to associate any table; (c) the specification entity only allows association of extension tables, and can associate 2 extension tables at most. The relation rules of the library table and the relation specification are as follows: (a) the large-class relation only allows to associate one main table or relation table, and the relation which is not allowed at present is stored as an expansion table; (b) the subclass relationships and specification relationships are not associated with any table.

(6) Specification Attribute (mm _ Spec _ Attribute): for convenience of management and reusability, the attributes of the entity specification and the relationship specification are grouped to form a component, and one component comprises one or more specific attributes and methods; components can be reused across different physical specifications (relationship specifications) or can be dependent only on a certain physical specification (relationship specification). Such as an identification group, a base component, a lifecycle group, etc. The system is composed of attributes and is used for describing aspect characteristics of entity specifications (relation specifications). The component supports inheritance, i.e., the children's entity specification (relationship specification) automatically inherits all the properties of the large class of specifications. Specifically, the attribute rule of the entity specification is as follows: (a) the large-class entity can only configure the attributes of the main table and the attributes of the longitudinal table, and the attributes must be configured on the premise of configuring the tables; (b) the subclass entity is not associated with any attribute; (c) the attribute of the extended table is associated with the specification entity, and simultaneously the attribute of the large class entity can be configured independently, and at the moment, the large class attribute defined on the specification entity covers the attribute defined on the large class entity to which the specification entity belongs. The attribute rules of the relationship specification are: (a) the large-class relationship configures the attribute only when stored as a relationship table; (b) the thin class relation and the specification relation are not configured with attributes, and directly inherit the large class relation.

(7) Dictionary value (mm _ dichlue): the dictionary value object is used to store data key and entry pairs (i.e., a form like "key value"). It can access any form of entry of data. Each entry is associated with a unique key. The key is used to retrieve a single item, typically an integer or a string, and may be of any type other than the group.

(8) Dictionary type (mm _ dichttype): and classifying dictionary values required by the attributes in groups, managing the dictionary values by using the dictionary types, and facilitating attribute confirmation that the high-dimensional data is composed of data of types corresponding to key values and is organized in an object mode.

(9) Dictionary type-dictionary value relationship (mr _ dichiptype _ dichalue): the method is used for recording the relation between the dictionary type and the dictionary value, so that different dictionary types can multiplex the same dictionary value, and the redundancy of the dictionary value is avoided.

(10) Relation of specification attribute to dictionary value (mr _ dichlue _ attr): used for recording specific dictionary values under the specification attribute.

(11) Domain (mm _ domain): multiple regions of multiple enterprises can be divided into domains, metadata management can be carried out according to different domains, and mutual management can be carried out according to requirements, so that sharing and management of data resources among different domains are realized.

(12) Relationship of domain to entity specification (mr _ domain _ object): and recording the relation between the domain and the meta-model, and determining the meta-model according to the requirements of the domain to build and apply, so that the different requirements of a plurality of domains are diversified.

Based on the above metadata rule description, since the management of entities, components, attributes, and entity relationship models is based on metadata, the invocation of various methods in the table refresh algorithm is also based on it.

And S2, responding to user operation, and acquiring a template to be configured, which meets the requirement of the user statistical form, from a template model, wherein the template model comprises a plurality of pre-designed templates which are used for transmitting required metadata to the metadata model after parameter configuration.

In step S2, the user operation refers to a human-computer interaction operation performed on a template management page (a main menu is displayed on the left side, and a configuration page is displayed on the right side) such as those shown in fig. 6 to 8. In the template management page, the following contents are included but not limited to: the method comprises the steps of selecting a left-side main menu (obtaining a main menu directory tree by default), menu item information (displaying menu configuration information by default after clicking the left-side menu), query conditions (used for querying an unassociated entity management template), an unassociated entity management template (used for displaying a query result and moving into a right-side associated entity management template list in a moving-in mode to carry out an association template), an associated entity management template (used for displaying associated entity management template information, wherein a resource character string must be input), and the like. Parameter configuration is added in template application, corresponding parameters can be transmitted in the page loading process and used for controlling different templates to be displayed under the same specification of the same page through different parameter control. Currently, the module control parameter is in a text mode, and whether the parameter is added or not can be selected and filled in the template application. And controlling the display template, searching the corresponding template according to the parameters under the condition that the input parameters are not empty, defaulting to display in a mode without the parameters if the parameters do not have the corresponding template, and defaulting to display the searched first piece of template data under the condition that a plurality of templates are found. And corresponding template control parameters are transmitted into the parameter in the page data dataset and are used for distinguishing and displaying different templates. The key of the parameter increasing parameter of the page dataset is param _ value, and when the page is displayed, the data obtained from the page and the template application table field param _ value are used for judging, distinguishing and selecting to display different templates.

In step S2, in order to implement interface configurability, the present embodiment develops a set of template models as shown in fig. 9, so as to configure templates for the entity specification. Specifically, the template model further includes a menu and a menu application template, wherein the menu is used for recording a required menu directory name and a display tree level, and the menu application template is used for recording a relationship between the menu and the template to be configured. The template to be configured comprises template subject information, template relation information, template attribute information, attribute checking information, template form information, form grouping information, grouping element information, template form information, form element information and query condition information, wherein the template subject information is used for recording template names and associated entity specifications in the metadata model, the template relation information is used for recording relation specifications used by the template, the template attribute information is used for recording specification attributes used by the template, the attribute validation information is used for recording attribute checking conditions (namely, the attributes cannot be null or the relations must be selected, and the like), the template form information is used for recording length and width of a template display form, the form grouping information is used for recording page form grouping display names, the grouping element information is used for recording attributes in the grouping forms and length and width control, the template table information is used for recording the line number of the template table, the table elements are used for recording the attributes displayed by the table, and the query condition information is used for recording the query conditions and the sequence of the template.

In the step S2, the template is a general interface configuration function provided based on the element and the frame, so as to control the presentation of the interface through the template description attribute for the entity object. The contents controlled by the template mainly include query conditions, form display and table display of the object, as shown in fig. 10, the template attribute function points include: the method comprises the following steps of field checking (for checking a field in an entity entry function, including field length, checking in a non-empty and regular expression mode, and the like), whether the field is queried or not (for controlling whether the field is queried or not, if so, the field is queried or not, whether the field is read only or not is controlled in a management interface, and/or a display name (for controlling the overall display name of a certain field in the interface) and the like; the template relation function points are as follows: whether the relation is queried or not (namely, a relation opposite-end entity of the current entity is used as a query condition), a pre-parameter is queried (namely, the pre-parameter can be configured when the relation is queried, and condition selection operation is reduced), a relation display name (namely, a query condition name is defined by using the relation opposite-end entity of the current entity as the query condition), and/or a self-defined universal query interface (namely, when the general relation is used as the query condition, the universal query interface is opened, but the query interface can be independently written to replace the universal query interface), and the like; the template form has the following functional points: form grouping (used for grouping and displaying entity object attributes, putting related attributes in a group for convenient searching and maintenance), form element management (used for adding, deleting and sequencing attributes in a form), display names (used for controlling a field to display names in the form), control types (used for: 1, editing text 2, multi-line text), whether to be read only (used for controlling whether the form attributes are allowed to be changed) and/or custom element hiding (used for hiding and developing custom fields), and the like; the template form functional points are as follows: the method comprises the following steps of displaying a name (used for controlling a certain field to display the name in a form), maintaining table attributes (used for adding, deleting and sorting attributes in the table), configuring a combined column (namely, a related attribute set has a large header), only reading (used for controlling whether the table attributes are allowed to be changed), displaying multiple attributes of a relation object (namely, displaying multiple attributes of a relation opposite-end entity) and/or hiding custom attributes (used for hiding and developing custom fields), and the like; the template copying, deleting and template application functions include template copying (for copying all template attributes such as attributes, attribute check, relationship, query conditions, forms and tables of the templates), template deleting (for deleting the templates and corresponding cache data), template application (for controlling the templates to take effect on a certain page) and template application control parameters (namely, different display modes are provided for the same specification data on certain pages, and different templates are displayed according to different parameters by controlling the parameters).

In step S2, according to the function implemented based on metadata as shown in fig. 11, all the service layers may be recorded in the form of a form, and then the meta platform established by the metadata and the template renders the presentation layer, so as to implement interface configurability, drive the meta platform, and achieve the functions of the form, the table, and the statistical report that meet the configuration requirements. Specifically, for template design and rendering, referring to the template design state and operation state examples shown in fig. 12, the metadata and the template configuration are sequentially read to realize the display of the form, the form and the query condition, and the display presentation of the whole interface can be completed only by configuration, that is, the page rendering process is as follows: rendering in sequence according to the mode of the attribute type, the query condition, the form related control and the form related control, and reading the rendering of the menu and the button according to the authority of the user to finish the loading of the whole interface. For example, the table page display may be as shown in fig. 13, where the upper side displays the template configuration query condition; the middle is a button; the lower side displays the template configuration table display. The form page display can be as shown in fig. 14, the upper left is that the form group names are configured according to the template, and the click shielding can be clicked and expanded; the middle is shown by grouping elements according to the template configuration form. The statistical page display can be as shown in fig. 15, and the upper side displays the template configuration query conditions; and displaying the statistical form on the lower side.

And S3, displaying the template to be configured on a man-machine interaction page.

And S4, obtaining the configured template according to configuration parameters input on the template to be configured, wherein the configuration parameters comprise a selection result aiming at the entity specification, a selection result aiming at the statistical condition and a selection result aiming at the statistical attribute.

In step S4, the statistical condition is a determination condition for filtering objects required for statistics, for example, a certain statistical condition requires that the marketing life of a product entity is within one year, i.e., metadata related to all entities whose marketing life is within one year can be filtered and obtained based on the statistical condition. The statistical attribute refers to the first line in the form. Furthermore, in a parameter configuration process, all metadata in the metadata model may be conveyed through templates in order to provide a precise selectable range of the entity specification, the statistical conditions, and the statistical attributes.

And S5, transmitting required metadata to the metadata model according to the configured template to obtain metadata to be counted, wherein the metadata to be counted comprises but is not limited to base table metadata and field metadata searched according to the configuration parameters.

In step S5, the database table metadata and the field metadata found according to the configuration parameters include, but are not limited to: confirming that the base table metadata and the field metadata meet the selection result aiming at the entity specification, the selection result aiming at the statistical condition and the selection result aiming at the statistical attribute.

And S6, splicing Structured Query Language (SQL) statements used for database statistics according to the statistical rules and the metadata needing to be counted.

In the step S6, the statistical rules are predefined rules for database statistics, and may be predefined in the template, and further the Structured Query Language SQL (Structured Query Language), which is a special purpose programming Language and is a database Query and programming Language for accessing data and querying, updating, and managing relational database system) statements, may be spliced in a conventional manner.

And S7, executing the Structured Query Language (SQL) statement on the resource database to obtain a statistical result.

In the step S7, the process of executing the structured query language SQL statement is a conventional process. After the step S7, the method further includes, but is not limited to: and displaying the statistical result on the human-computer interaction page, wherein the statistical result comprises but is not limited to a reported statistical result and/or a graphical statistical result, and the graphical statistical result comprises but is not limited to a pie chart statistical result and/or a histogram statistical result. As shown in fig. 16, both pie chart statistics and histogram statistics may be presented.

Thus, based on the resource data statistical method described in the foregoing steps S1 to S7, a meta-platform service scheme for performing resource data statistics based on metadata and templates is provided, that is, after a metadata model that is a resource database and can cover all entity information and database storage modes is established according to a broad modeling principle, a pre-designed template that enables metadata to be configurable is used for page configuration, metadata and corresponding conditions that need to be counted are extracted by configuring entity specifications, statistical conditions and statistical attributes, SQL statements for database statistics are spliced out according to statistical rules, and finally SQL statements are executed through a database to achieve statistical requirements for application page configurability, so that the purposes of application intensive management, model configurability and metadata driving interfaces can be achieved by using a metadata model instance service language, and further statistical functions such as data extraction and multidimensional reports can be rapidly supported, the reusability of statistical application is improved to the maximum extent, complex development details are shielded, the development cost is finally reduced, and the operation efficiency is improved. And the direct access of the application code to the database can be shielded, the translation is carried out by adopting metadata, the shutdown is not needed, the model can be thermally deployed, and the flexible and quick expansion of the model is ensured. In addition, compared with the conventional statistical application method, the resource data statistical method provided by the embodiment further has the following detailed advantages: (1) modeling is carried out through the major category and the metadata, the relationship between concepts is concentrated on a major table of the major category, and dynamic expansion is carried out by utilizing the metadata; (2) the convergence dimension and the convergence granularity of the large-class modeling are determined, and the rationality of the large-class modeling is ensured theoretically; (3) triggering from the perspective of resource application, determining the management granularity of a resource business object, and constructing a resource specification catalog; (4) the result of the large-scale modeling can be demonstrated and verified, and the IT language can be effectively translated into the business language; (5) the cloud platform can basically keep the stability of the core large class and the relationship entity, only inherits and expands the relationship and the attribute of the large class entity, updates the metadata on line and adds the expansion table (optional) for support without stopping the cloud platform! (6) All business entities and database attributes are summarized on the cloud platform based on the support of the two models, and correct SQL statements can be driven to access the database to realize statistics by directly operating the necessary information provided in the metadata.

As shown in fig. 17, a second aspect of this embodiment provides a virtual device for implementing the resource data statistics method in the first aspect, including a model building unit, and an operation response unit, a template display unit, a parameter configuration unit, a data transmission unit, a statement splicing unit, and a statistics execution unit, which are sequentially connected in communication;

the model establishing unit is used for establishing a metadata model of a resource database according to a major modeling principle, wherein the resource database is used for storing data information of all product entities, the metadata model comprises database table metadata, field metadata, entity specification metadata, relationship specification metadata and relationship metadata, a base table in the database table metadata comprises all tables in the resource database, fields in the field metadata comprise all fields in the resource database, an entity specification in the entity specification metadata comprises major entities, fine entities and specification entities, the major entities refer to entity classes distinguished according to different product functions, product attributes and/or product characteristics, and the fine entities refer to entity classes distinguished according to different product purposes for the major entities, the specification entities refer to entity types distinguished according to different specific business objects and relations aiming at the thin-class entities, the relation specifications in the relation specification metadata comprise large-class relations, thin-class relations and specification relations, the large-class relations refer to the relations between one large-class entity and another large-class entity, the thin-class entities refer to the relations between one thin-class entity and another thin-class entity, the specification relations refer to the relations between one specification entity and another specification entity, and the relations in the relation metadata comprise the relations between a base table and an entity specification and the relations between the base table and the relation specification;

the operation response unit is used for responding to user operation and acquiring a template to be configured, which meets the requirement of a user statistical report form, from a template model, wherein the template model comprises a plurality of pre-designed templates which are used for transmitting required metadata to the metadata model after parameter configuration;

For the working process, working details and technical effects of the foregoing apparatus provided in the second aspect of this embodiment, reference may be made to the resource data statistics method described in the first aspect, which is not described herein again.

As shown in fig. 18, a third aspect of this embodiment provides a meta platform device for performing the resource data statistics method according to the first aspect, including a memory, a processor, and a transceiver, which are sequentially and communicatively connected, where the memory is used to store a computer program, the transceiver is used to transmit and receive data, and the processor is used to read the computer program and perform the resource data statistics method according to the first aspect. For example, the Memory may include, but is not limited to, a Random-Access Memory (RAM), a Read-Only Memory (ROM), a Flash Memory (Flash Memory), a First-in First-out (FIFO), and/or a First-in Last-out (FILO), and the like; the processor may be, but is not limited to, a microprocessor of the model number STM32F105 family. In addition, the meta-platform device may also include, but is not limited to, a power module, a display screen, and other necessary components.

For the working process, working details, and technical effects of the meta-platform device provided in the third aspect of this embodiment, reference may be made to the resource data statistics method in the first aspect, which is not described herein again.

A fourth aspect of the present embodiment provides a computer-readable storage medium storing instructions including the resource data statistics method according to the first aspect, that is, the computer-readable storage medium has instructions stored thereon, and when the instructions are executed on a computer, the resource data statistics method according to the first aspect is executed. The computer-readable storage medium refers to a carrier for storing data, and may include, but is not limited to, a computer-readable storage medium such as a floppy disk, an optical disk, a hard disk, a flash Memory, a flash disk and/or a Memory Stick (Memory Stick), and the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.

For the working process, the working details, and the technical effects of the foregoing computer-readable storage medium provided in the fourth aspect of this embodiment, reference may be made to the resource data statistics method in the first aspect, which is not described herein again.

A fifth aspect of the present embodiments provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of resource data statistics as described in the first aspect. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable devices.

Finally, it should be noted that the present invention is not limited to the above alternative embodiments, and that various other forms of products can be obtained by anyone in light of the present invention. The above detailed description should not be taken as limiting the scope of the invention, which is defined in the claims, and which the description is intended to be interpreted accordingly.

Claims

1. A resource data statistical method, comprising:

displaying the template to be configured on a man-machine interaction page;

2. The resource data statistical method of claim 1, wherein the metadata model further comprises specification attribute metadata, wherein the specification attributes in the specification attribute metadata are used to record whether attribute components are shown, filled, readable, updatable, multi-choice supported and/or default values, and the attribute components are components formed by grouping attributes of entity specification/relationship specification.

3. The resource data statistics method of claim 2, wherein the metadata model further comprises dictionary value metadata and dictionary type metadata, wherein dictionary values in the dictionary value metadata comprise stored data key and entry pairs, and dictionary types in the dictionary type metadata comprise all grouping classifications made to dictionary values required for attributes;

4. The resource data statistical method of claim 1, wherein the metadata model further comprises domain metadata, wherein a domain in the domain metadata comprises different regions of all product entities;

the relationship in the relationship metadata also contains the relationship between the domain and the entity specification.

5. The resource data statistical method according to claim 1, wherein the template model further comprises a menu for recording a required menu directory name and a display tree hierarchy, and a menu application template for recording a relationship between the menu and the template to be configured.

6. The resource data statistical method according to claim 1, wherein the template to be configured includes template topic information, template relationship information, template attribute information, attribute verification information, template form information, form grouping information, grouping element information, template form information, form element information, and query condition information, wherein the template topic information is used for recording template names and associated entity specifications in the metadata model, the template relationship information is used for recording relationship specifications of template use, the template attribute information is used for recording specification attributes of template use, the attribute validation information is used for recording attribute verification conditions, the template form information is used for recording length, width and height of template display forms, the form grouping information is used for recording page form grouping display names, the grouping element information is used for recording attributes in grouping forms and control length, width and height, the template table information is used for recording the line number of the template table, the table elements are used for recording the attributes displayed by the table, and the query condition information is used for recording the query conditions and the sequence of the template.

7. The resource data statistical method of claim 1, wherein after executing the Structured Query Language (SQL) statement on the resource database to obtain a statistical result, the method further comprises:

8. A resource data statistical device is characterized by comprising a model establishing unit, an operation response unit, a template display unit, a parameter configuration unit, a data transmission unit, a statement splicing unit and a statistical execution unit which are sequentially in communication connection;

the model establishing unit is used for establishing a metadata model of a resource database according to a major modeling principle, wherein the resource database is used for storing data information of all product entities, the metadata model comprises database table metadata, field metadata, entity specification metadata, relationship specification metadata and relationship metadata, a base table in the database table metadata comprises all tables in the resource database, fields in the field metadata comprise all fields in the resource database, an entity specification in the entity specification metadata comprises major entities, fine entities and specification entities, the major entities refer to entity classes distinguished according to different product functions, product attributes and/or product characteristics, and the fine entities refer to entity classes distinguished according to different product purposes for the major entities, the specification entities refer to entity types distinguished according to different specific business objects and relations aiming at the thin type entities, the relation specifications in the relation specification metadata comprise large type relations, thin type relations and specification relations, the large type relations refer to the relations between one large type entity and another large type entity, the thin type entities refer to the relations between one thin type entity and another thin type entity, the specification relations refer to the relations between one specification entity and another specification entity, and the relations in the relation metadata comprise the relations between a base table and an entity specification and the relations between the base table and the relation specification;

9. Meta-platform device, comprising a memory, a processor and a transceiver, wherein the memory, the processor and the transceiver are sequentially connected in communication, the memory is used for storing a computer program, the transceiver is used for transceiving data, and the processor is used for reading the computer program and executing the resource data statistical method according to any one of claims 1 to 7.

10. A computer-readable storage medium having stored thereon instructions for performing the resource data statistics method of any one of claims 1-7 when the instructions are run on a computer.