CN104866603B - The call method and metadata management system of metadata - Google Patents
The call method and metadata management system of metadata Download PDFInfo
- Publication number
- CN104866603B CN104866603B CN201510294145.1A CN201510294145A CN104866603B CN 104866603 B CN104866603 B CN 104866603B CN 201510294145 A CN201510294145 A CN 201510294145A CN 104866603 B CN104866603 B CN 104866603B
- Authority
- CN
- China
- Prior art keywords
- field
- model
- metadata
- data
- tenant
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/907—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
Abstract
The present embodiments relate to a kind of call method of metadata and metadata management system, the call method includes：When application call data, according to the model definition stored in application and relationship model, the required model called is determined；According to the attribute for providing field under the model terms of the model, is inquired from tenant's metadatabase and call respective field；The model terms of field will be called, has been spliced into data.
Description
Technical field
The present invention relates to the call methods and metadata management system of computer realm more particularly to a kind of metadata.
Background technology
Metadata (Metedata) refers to describing the data (data about data) of data, it is possible to understand that for than general
The more extensive data of data category of meaning not only indicate the information such as type, title, the value of data, also further carry
The context-descriptive information of data, such as domain, data source etc. described in data are supplied.In management information system, metadata
It is the basis of enterprise intelligent information construction, is the minimum unit of data.Metadata can specifically include technology metadata and industry
Business metadata.
In management information system, metadata can help enterprise customer easily to find their numbers of concern
According to.When obtaining the meaning of data from service metadata and technology metadata, can more effectively summarize and integrated data.Letter
Yan Zhi, when effectively management metadata, data just become more valuable.Therefore, metadata how is effectively managed and using member
Data are highly inquire into the problem of.
Invention content
An embodiment of the present invention provides a kind of call method of metadata and metadata management systems, according to application memory
Model defines and relationship model, accurately calling model field and can be spliced into the number of application request from tenant's metadatabase
According to effective management and accurate use, the data accuracy of Support Management Information System to realize metadata make system have
Good professional ability.
In a first aspect, an embodiment of the present invention provides a kind of call method of metadata, the method includes：
When application call data, according to the model definition stored in application and relationship model, the required mould called is determined
Type；
According to the attribute for providing field under the model terms of the model, is inquired from tenant's metadatabase and call corresponding word
Section；
The model terms of field will be called, has been spliced into data.
Preferably, further include before the calling data：
According to the regulation of metadata dictionary, imported into tenant's metadatabase the field in data and with metadata form into
Row storage.
It is further preferred that the regulation according to metadata dictionary, the word in data is imported into tenant's metadatabase
Section and with metadata form carry out storage include：
Determine whether the field meets the regulation of metadata dictionary；
When the field meets the regulation of metadata dictionary, the field is stored with metadata form；
When the field does not meet the regulation of metadata dictionary, according to mapping relations, by field against regulation into
After row meeting processing, by meeting, treated that field is stored with metadata form.
Further preferred, field from the metadatabase to tenant that imported in data in is simultaneously also wrapped before storing
It includes：
Based on application build model, and Definition Model relationship.
It is further preferred that being based on application build model described, and further include before Definition Model relationship：
Define the metadata dictionary.
Preferably, it is described be spliced into data after, the method further includes：
The interactive interface that the data are provided by application, is shown to tenant.
Second aspect, an embodiment of the present invention provides a kind of metadata management system, the system comprises：
At least one application, each application includes multiple models and relationship model；The model terms of wherein each model
Include defined field down, the field has field attribute；The relationship model is used to provide between the multiple model
Correspondence；
Tenant's metadatabase, for storing tenant's metadata；
Data dictionary database, for storing metadata dictionary；The metadata dictionary includes the attribute to metadata
Standardization definition.
Preferably, the attribute of the metadata includes：The data item of metadata, data structure, data flow, data storage,
Handle the definition and description of logic and external entity.
Preferably, the application further includes：
Interactive interface towards tenant.
The call method and metadata management system of metadata proposed by the present invention, according to the model of application memory definition and
Relationship model accurately calling model field and can be spliced into the data of application request, to realize from tenant's metadatabase
Effective management of metadata and accurate use, the data accuracy of Support Management Information System make system have good business
Ability.
Description of the drawings
Fig. 1 is the call method flow chart of metadata provided in an embodiment of the present invention；
Fig. 2 is the block diagram of metadata management system provided in an embodiment of the present invention.
Specific implementation mode
To make the object, technical solutions and advantages of the present invention clearer, the present invention is embodied below in conjunction with the accompanying drawings
Example is described in further detail.
The call method for the metadata that embodiment that the present invention will be described in detail by taking Fig. 1 as an example below provides, Fig. 1 are that the present invention is real
The call method flow chart of the metadata of example offer is provided.The subject of implementation of present invention method is the fortune of management information system
Seek platform.Fig. 2 shows the block diagram for the metadata management system that the embodiment of the present invention proposes.In conjunction with shown in Fig. 1 and Fig. 2, the party
Method includes the following steps：
Step 110, when application call data, according to stored in application model definition and relationship model, determine needed for
The model of calling；
Specifically, in management information system, there are multiple applications that can provide user interface, in each application
In, it is pre-defined to have model and relationship model.Model includes the field under model terms.Include answering using 1 than as shown in Figure 2
Model 1 with 1 and model 2 include field 1 and field 2 under the model terms of model 1, include 3 He of field under the model terms of model 2
Field 4, it further includes the relationship model of model 1 and model 2 to apply 1 in addition, and in this case, it is one-to-many relationships.In order to preferably
Understand, with a specific example explanation.For example it is department internal staff management, the field 1 in the model terms of model 1 to apply 1
For department name, such as " department A ", field 2 is department's total number of persons, such as " 30 "；Field 3 in one model terms of model 2 is portion
Door personnel's name, field 4 are the job site of departmental staff.Because in a department, departmental staff's number is usually all more than 1
It is a.Therefore in application 1, the correspondence of model 1 and model 2 is one-to-many relationship.That is, in application 1, it is based on
Model terms can show for example following information：Department A, 30 (people)；Zhang, Beijing；Lee, Beijing；Fourth, Beijing；Etc..
Include model 1 and the model 2 (being different with the model 1 and model 2 applied under 1) for applying 2 using 2, model 1
Include field 6 and field 1 (field 1 here is same with the field 1 under 1 drag 1 of application) under model terms, model 2
Include field 2 (field 2 here is same with the field 2 under 1 drag 1 of application) and field 4 under model terms, applies in addition
2 further include the relationship model of model 1 and model 2, and in this case, it is one-to-one relationships.In order to better understand, equally with one
A specific example explanation.For example using 2 be statistical management of the personnel department to each department employee, in the model terms of model 1
Field 6 be industry number, such as " 003 ", field 1 be department name；Field 2 in one model terms of model 2 is that department is total
Number, field 4 are the job site of departmental staff.Because the number and department name of each department are one-to-one, departments
Number is also uniquely corresponding with industry number and department name, it is assumed that job site there are one each departments in this example, that
Model 1 and model 2 in application 2 are exactly a pair of with one relationship.That is, in application 2, model terms are based on, it can be with
For example following information of displaying：003, department A, 30 (people), Beijing；004, department B, 25 (people), Shanghai；Etc..
It, can be according to the model of one or several models under of application memory when some application call data
Definition and relationship model, to determine model that needs call.
Step 120, it according to the attribute for providing field under the model terms of the model, inquires and adjusts from tenant's metadatabase
Use respective field；
Specifically, after determining the model that needs call, according to the attribute of the field under model terms, in metadata lookup phase
The field answered.For example, needing calling model 1 using 1, therefore can searching data attribute be department in the metadatabase of the tenant
The field of title, and searching data attribute is the field of department's number in the metadatabase of the tenant.Certainly, in department people
The attribute of affiliated function's title is also had in several field attributes, therefore can be by the multiple department names found and multiple portions
Door number is corresponded.
Step 130, the model terms that will call field, are spliced into data.
Specifically, after the above-mentioned field found is called, required data are combined by application.Also, pass through
Using the interactive interface of offer, the displaying of data is carried out to tenant.
Data mentioned here can be specifically to record.Data entity can be the form of table, and a line of table is exactly one
Record, the row in going are exactly a field.There is critical field in record.For example, a record includes employee name, property
Not, age, employee code.Regulation employee code is critical field, then when retrieving employee information, just by employee code
All relevant informations of the employee can be all retrieved.
Certainly, for the method for realizing the present invention, in step 110 before application call data, pre-defined member is needed
Data dictionary, and according to the regulation of metadata dictionary, the field in data is imported into tenant's metadatabase and with metadata shape
Formula is stored.Wherein, the detailed process of storage can be as follows：
Whether meet the regulation of metadata dictionary firstly the need of the determining field stored；When field meets first number
According to dictionary regulation when, directly field can be stored with metadata form；When the field does not meet metadata dictionary
Regulation when, then need according to pre-set mapping relations, will after field against regulation is carried out meeting processing
Treated stores field with metadata form for meeting.One specific example, it is assumed that in metadata dictionary, data
Attribute is the field of " job site ", should be only city name according to the rules, such as " Beijing ".And the field stored
For " Beijing ", then will be when storage according to preset mapping relations " Beijing->Beijing " is by field " Beijing "
The meeting processing for carrying out data dictionary, handles as field " Beijing " and then is stored.This have the advantage that
In tenant's metadatabase standardization storage field, avoid substantive content identical but because literary style difference caused by repeat store, with
And data call less than or call situations such as inaccurate.
In addition, for application, it is also necessary to carry out the structure using drag, and Definition Model relationship in advance.
In above-mentioned steps 130, after the field of calling is spliced into data, can also be handed over by the provided user of application
Mutual interface or display interface, are shown to tenant.
When system developer or there is the user of write-in/modification authority to increase standardization definition newly into metadata dictionary
Field when, need to register this metadata fields.Firstly the need of a data structure is defined, the data are then defined
Relationship between structure and other data structures does standardization judgement finally according to the rule of data dictionary to newly-increased field,
To legal, directly it is added in metadata dictionary；To not being inconsistent normally, need to add after being standardized
Metadata dictionary.
When newly-increased data model, first confirm that whether field specified in newly-increased data model is to meet data with existing
Model.Directly increase the data model if meeting, if wherein there is field not exist in existing data dictionary,
Increase field in data dictionary, carries out being then assembled into data model after field expands.In other words, system is opened to user
To field level, support user as needed from group data.The call method of metadata in the embodiment of the present invention, provides to the user
Expansible metadatabase, any one data model definitions out after is likely to realize in this system.
The call method of metadata provided in an embodiment of the present invention, according to the model of application memory definition and relationship model,
Accurately calling model field and the data of application request can be spliced into from tenant's metadatabase, to realize having for metadata
Effect management and accurate use, the data accuracy of Support Management Information System make system have good professional ability.
Correspondingly, the embodiment of the present invention additionally provides metadata management system as shown in Figure 2.As shown in Fig. 2, metadata
Management system includes：It is at least one application (it is shown in Figure 2 be include using 1 and application 2 two apply the case where), Zu Huyuan
Database 3, data dictionary database 4 and the interactive interface (being not shown in Fig. 2) towards tenant.
Wherein, each application includes multiple models and relationship model；Include defined under the model terms of wherein each model
Field, field have field attribute；Relationship model is used to provide the correspondence between multiple models of the application；
Tenant's metadatabase 3, the metadata for storing tenant；
Data dictionary database 4, for storing metadata dictionary；Metadata dictionary includes the specification to the attribute of metadata
Change definition；Wherein, the attribute of metadata may include：The data item of metadata, data structure, data flow, data storage, processing
Definition and description of logic and external entity etc..
The system for the discrete management of each tenant, multiple tenants can with the application of common sparing or whole, with
And data dictionary database 4.It is entirely to be made according to tenant but in tenant's metadatabase 3 and the metadata that wherein stores
Depending on application.
For example, situation shown in Fig. 2：Include using 1 and to apply 2 in the management information system of certain tenant, wherein applying 1
Two models under field respectively included " field 1 ", " field 2 ", " field 3 " and " field 4 ", using under 2 two models
Field has respectively included " field 6 ", " field 1 ", " field 2 " and " field 3 ", thus in tenant's metadatabase to " field 1 ",
" field 2 ", " field 3 ", " field 4 " and " field 6 " is stored.
Assuming that there is another tenant, pertain only to apply 2, then in tenant's metadatabase in management information system
" field 1 ", " field 2 ", " field 3 " and " field 6 " is stored.
The metadata call method of above-described embodiment may be implemented, specifically in metadata management system based on the present embodiment
Implementation procedure repeats no more.
When increasing data model newly in metadata management system, field specified in newly-increased data model is first confirmd that
Whether data with existing model is met.Directly increase the data model under application if meeting, if wherein there is field
Do not exist in existing data dictionary database 4, then increase field in data dictionary database 4, carries out field and expand it
After be then assembled into data model.In other words, system opens into field level to user, supports user as needed from group data.
Metadata management system provided in an embodiment of the present invention can realize effective management of metadata and accurate use,
The data accuracy of Support Management Information System makes system have good professional ability.Also, it provides to the user expansible
Tenant's metadatabase, to provide flexible Metadata registry mechanism.
Professional should further appreciate that, described in conjunction with the examples disclosed in the embodiments of the present disclosure
Unit and algorithm steps, can be realized with electronic hardware, computer software, or a combination of the two, hard in order to clearly demonstrate
The interchangeability of part and software generally describes each exemplary composition and step according to function in the above description.
These functions are implemented in hardware or software actually, depend on the specific application and design constraint of technical solution.
Professional technician can use different methods to achieve the described function each specific application, but this realization
It is not considered that the range beyond the embodiment of the present invention.
The step of method described in conjunction with the examples disclosed in this document or algorithm, can use hardware, processor to execute
The combination of software module or the two is implemented.Software module can be placed in random access memory (RAM), memory, read-only memory
(ROM), electrically programmable ROM, electrically erasable ROM, register, hard disk, moveable magnetic disc, CD-ROM or technical field
In any other form of storage medium well known to interior.
Above-described specific implementation mode, to the embodiment of the present invention, technical solution and advantageous effect carried out into one
Step is described in detail, it should be understood that the foregoing is merely the specific implementation mode of the embodiment of the present invention, is not used to limit
Determine the protection domain of the embodiment of the present invention, all any modifications within the spirit and principle of the embodiment of the present invention, made are equal
Replace, improve etc., it should be included within the protection domain of the embodiment of the present invention.
Claims (4)
1. a kind of call method of metadata, which is characterized in that the call method includes：
According to the regulation of metadata dictionary, field from data to tenant's metadatabase that imported in is simultaneously deposited with metadata form
Storage；
When application call data, according to the model definition stored in application and relationship model, the required model called is determined；
According to the attribute for providing field under the model terms of the model, is inquired from tenant's metadatabase and call respective field；
The model terms of field will be called, has been spliced into data；
Wherein, the regulation according to metadata dictionary imports the field in data into tenant's metadatabase and with metadata
Form carries out storage：
Determine whether the field meets the regulation of metadata dictionary；
When the field meets the regulation of metadata dictionary, the field is stored with metadata form；
When the field does not meet the regulation of metadata dictionary, according to mapping relations, field against regulation is accorded with
After combination processing, by meeting, treated that field is stored with metadata form.
2. call method according to claim 1, which is characterized in that imported in data in the metadatabase to tenant
Field and further include before being stored：
Based on application build model, and Definition Model relationship.
3. call method according to claim 2, which is characterized in that be based on application build model described, and define mould
Further include before type relationship：
Define the metadata dictionary.
4. call method according to claim 1, which is characterized in that it is described be spliced into data after, the method is also
Including：
The interactive interface that the data are provided by application, is shown to tenant.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510294145.1A CN104866603B (en) | 2015-06-01 | 2015-06-01 | The call method and metadata management system of metadata |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510294145.1A CN104866603B (en) | 2015-06-01 | 2015-06-01 | The call method and metadata management system of metadata |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104866603A CN104866603A (en) | 2015-08-26 |
| CN104866603B true CN104866603B (en) | 2018-09-25 |
Family
ID=53912429
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510294145.1A Active CN104866603B (en) | 2015-06-01 | 2015-06-01 | The call method and metadata management system of metadata |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104866603B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108170752B (en) * | 2017-12-21 | 2020-10-16 | 山东合天智汇信息技术有限公司 | Template-based metadata management method and system |
| CN109446190B (en) * | 2018-11-07 | 2022-11-01 | 湖北省标准化与质量研究院 | Data processing method of standard metadata |
| CN111239529A (en) * | 2020-03-05 | 2020-06-05 | 西南交通大学 | Excitation test method and system supporting predictive maintenance of electromechanical equipment |
| CN113687881A (en) * | 2021-08-20 | 2021-11-23 | 广东电网有限责任公司 | Metadata calling method and device, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101770518A (en) * | 2010-01-29 | 2010-07-07 | 华东电网有限公司 | Metadata management method of power grid enterprise integrated information die |
| CN101908040A (en) * | 2010-07-01 | 2010-12-08 | 千乡万才科技(中国)有限公司 | Data report system |
| CN102737033A (en) * | 2011-03-31 | 2012-10-17 | 国际商业机器公司 | Data processing equipment and data processing method thereof |
| CN103729471A (en) * | 2014-01-21 | 2014-04-16 | 华为软件技术有限公司 | Method and device for database query |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7181450B2 (en) * | 2002-12-18 | 2007-02-20 | International Business Machines Corporation | Method, system, and program for use of metadata to create multidimensional cubes in a relational database |
| CN103049521B (en) * | 2012-12-19 | 2015-11-11 | 广东电子工业研究院有限公司 | Virtual table directory system and the method for many attributes multiple condition searching can be realized |
-
2015
- 2015-06-01 CN CN201510294145.1A patent/CN104866603B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101770518A (en) * | 2010-01-29 | 2010-07-07 | 华东电网有限公司 | Metadata management method of power grid enterprise integrated information die |
| CN101908040A (en) * | 2010-07-01 | 2010-12-08 | 千乡万才科技(中国)有限公司 | Data report system |
| CN102737033A (en) * | 2011-03-31 | 2012-10-17 | 国际商业机器公司 | Data processing equipment and data processing method thereof |
| CN103729471A (en) * | 2014-01-21 | 2014-04-16 | 华为软件技术有限公司 | Method and device for database query |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104866603A (en) | 2015-08-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8095618B2 (en) | In-memory caching of shared customizable multi-tenant data | |
| CN104866603B (en) | The call method and metadata management system of metadata | |
| Barado et al. | A mathematical model for simulating daily bed occupancy in an intensive care unit | |
| US7421740B2 (en) | Managing user authorizations for analytical reporting based on operational authorizations | |
| US20080104008A1 (en) | Common data broker method, system, and program product | |
| CN107025411B (en) | A kind of system and method for fine-grained data permission dynamic control | |
| US20130232582A1 (en) | Need-to-know information access using quantified risk | |
| JP2019144723A (en) | Anonymity processing device and information anonymity method and program | |
| US9053143B2 (en) | Allowing updates to database objects | |
| US7505993B2 (en) | Database schema for content managed data | |
| US7797626B2 (en) | Managing different representations of information | |
| US20140075028A1 (en) | Centralized Data Provisioning | |
| WO2023103815A1 (en) | Contextual dialogue framework over dynamic tables | |
| US8832110B2 (en) | Management of class of service | |
| CN108388610B (en) | Data ETL processing method and device | |
| US11151477B2 (en) | Training a customer service system | |
| US11580125B2 (en) | Information system with temporal data | |
| US20080177772A1 (en) | Smart identifiers | |
| US20150019451A1 (en) | Decision basis for benefits program | |
| TW497051B (en) | Database having table for storing queries | |
| CN110096653A (en) | Construction method, device, equipment and the storage medium of space time information service architecture | |
| JP6948299B2 (en) | Data registration device and data registration method | |
| US20070162492A1 (en) | Reconstruction of historic business object state | |
| US20230067107A1 (en) | Managing vertex level access in a graph via user defined tag rules | |
| EP3582157A1 (en) | Method for providing context based artefact access |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| EXSB | Decision made by sipo to initiate substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 100027 Beijing city Chaoyang District Sanyuanqiao Xiaguang Ruipu Hospital No. 5 Building 1 layer 101 Applicant after: Ming Yuan Technology (Beijing) Limited by Share Ltd Address before: 100027 Beijing city Chaoyang District Sanyuanqiao Xiaguang Ruipu Hospital No. 5 Building 1 layer 101 Applicant before: Beijing Yuantong Huida Management Software Development Co., Ltd. |
|
| COR | Change of bibliographic data | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |