CN108170867B - Metadata service system - Google Patents
Metadata service system Download PDFInfo
- Publication number
- CN108170867B CN108170867B CN201810098956.8A CN201810098956A CN108170867B CN 108170867 B CN108170867 B CN 108170867B CN 201810098956 A CN201810098956 A CN 201810098956A CN 108170867 B CN108170867 B CN 108170867B
- Authority
- CN
- China
- Prior art keywords
- metadata
- xml
- service
- layer
- xsd
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
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/80—Information retrieval; Database structures therefor; File system structures therefor of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML
- G06F16/84—Mapping; Conversion
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/13—File access structures, e.g. distributed indices
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present application provides a metadata service system, including: a metadata service layer, and a user layer; the metadata service layer is used for providing storage service and query service for XSD files corresponding to different service data respectively and XML files taking the XSD files as standards; and the metadata service layer is used for generating a corresponding service interface based on the service provided by the metadata service layer and providing the service interface for the user layer.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a metadata service system.
Background
An Extensible Markup Language (XML) file is a Markup Language used for marking an electronic file to make the electronic file have a structure, can be used for marking data and defining data types, and is a source Language allowing a user to define the own Markup Language. And multiple XML files may be generated based on one XSD file.
However, different service data may correspond to different XSD files, each XSD file may generate multiple XML files, and for the case that the number of XSD files is large and the number of XML files corresponding to each XSD file is also large, the prior art does not provide a special system for effectively managing the XSD files and the XML files, which brings inconvenience to content query of the XML files.
Disclosure of Invention
In view of the above, an object of the present application is to provide a metadata service system, which is used to solve the problem of inconvenient query of XML file content in the prior art.
In a first aspect, an embodiment of the present application provides a metadata service system, where the system includes: a metadata service layer, and a user layer;
the metadata service layer is used for providing storage service and query service for XSD files corresponding to different service data respectively and XML files taking the XSD files as standards;
and the metadata service layer is used for generating a corresponding service interface based on the service provided by the metadata service layer and providing the service interface for the user layer.
Optionally, the system further comprises: a metadata storage layer, the metadata service layer comprising: the system comprises a metadata standard service module and a metadata management service module;
the metadata standard service module is used for analyzing each XSD file aiming at the XSD files respectively corresponding to different service data and extracting XML element nodes in each XSD file;
the metadata management service module is used for analyzing an XML value corresponding to an XML element node of the corresponding XSD file aiming at the XML file taking each XSD file as a standard;
and the metadata storage layer is specifically used for correspondingly storing the XML values and the XML element nodes.
Optionally, the metadata standard service module is further configured to determine a corresponding node identifier for the extracted XML element node;
and the metadata storage layer is specifically used for correspondingly storing the extracted XML values and the node identifiers of the XML element nodes.
Optionally, the metadata standard service module is specifically configured to determine a path of the extracted XML element node in the belonging XSD file as a corresponding node identifier.
Optionally, the metadata standard service module is further configured to set, for each XSD file, an access point for a node identifier of each XML element node of the XSD file;
the metadata storage layer is specifically used for correspondingly storing the node identifier and the access point of the XML element node of the XSD file and the identifier of the database corresponding to the XSD file; and
and for each XSD file, correspondingly storing the extracted XML value and the node identifier of the XML element node extracted from the XSD file into a database corresponding to the XSD file.
Optionally, the metadata standard service module is further configured to receive an XML query request sent through a query interface provided by the metadata service layer, where the XML query request includes an access point and a database identifier; and
determining node identifiers of XML element nodes corresponding to the access points and the database identifiers contained in the query request according to node identifiers and access points of XML element nodes of the corresponding stored XSD file and identifiers of a database corresponding to the XSD file; and
and determining an XML value which accords with the query condition from XML values which are stored in the database corresponding to the metadata storage layer and correspond to the node identification of the determined XML element node, and feeding back the XML value.
Optionally, the metadata standard service module is further configured to register the XSD file in the system after parsing the XSD file.
Optionally, the metadata standard service module is further configured to, for each XSD file, determine whether at least two XML files in the XML using the XSD file as a standard meet the following conditions:
at least two XML element nodes exist for the XML element nodes extracted from the XSD file, and the XML values corresponding to the XML element nodes in the at least two XML files are the same for each XML element node;
and if so, processing according to a preset duplication checking processing rule.
Optionally, the metadata service layer further includes: a metadata base management module;
the metadata base management module is used for performing at least one of the following operations on the metadata base in the metadata storage layer: create, delete, clear, and query.
Optionally, the metadata service layer further includes: a metadata user authorization management module;
and the metadata user authorization management module is used for adding, deleting, modifying and authorizing metadata users.
The metadata service system provided by the embodiment of the application provides storage service and query service for XSD files respectively corresponding to different service data and XML files taking the XSD files as standards through the metadata service layer, generates a corresponding service interface based on the service provided by the metadata service layer through the metadata service layer, and provides the service interface for the user layer. Therefore, a simple and easy-to-operate metadata service system is provided for the user, the user experience is improved, meanwhile, different XML documents can be managed in a unified mode, and convenience is brought to XML file content query.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a schematic diagram of a logical architecture of a metadata service system according to an embodiment of the present application;
fig. 2 is a first structural diagram of a metadata service system according to an embodiment of the present application;
fig. 3 is a second structural diagram of a metadata service system according to an embodiment of the present application;
fig. 4 is a relationship diagram of a correspondence between XML element nodes and paths of the XSD file of the XML element nodes according to the embodiment of the present application;
fig. 5 is a schematic structural diagram of a metadata service system according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a computing device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application.
The logic architecture of the metadata service system provided by the application comprises a user layer, a service layer and a data layer, wherein as shown in fig. 1, the user layer generally refers to a system administrator, and the service layer is mainly used for performing metadata standard management, metadata base management, metadata service management, metadata user authorization management and the like; the service layer is used for providing metadata standard service, metadata base service, metadata management service, metadata service and metadata user authorization service; the data layer comprises a metadata base, a metadata standard base, a user base and the like. The details are described below.
An embodiment of the present application provides a metadata service system, as shown in fig. 2, the system includes: a metadata service layer 11, a metadata service layer 12, and a user layer 13.
The metadata service layer 11 is configured to provide storage services and query services for XSD files corresponding to different service data respectively and XML files using each XSD file as a standard;
the metadata service layer 12 is configured to generate a corresponding service interface based on the service provided by the metadata service layer 11, and provide the service interface to the user layer 13.
Here, the metadata in the embodiment of the present application may refer to XML data. The business data can be data provided by metadata users, such as basic information of school students; an extensible markup language schema Definition (XML schema Definition, XSD) file is generally a metadata standard file, and the metadata standard file includes XML element nodes and a path of each XML element node in the XSD file, where the path is also called a hierarchical structure, for example, when service data is basic information of a school student, the hierarchical structure may be beijing, a-eighth middle school, a-first second year, a-3 class, and the XML element nodes may be names; in an Extensible Markup Language (XML) file, corresponding XML values (metadata) are stored in advance according to corresponding XML element nodes of an XSD file, which is exemplified as follows:
the service interface provided by the metadata service layer generally includes an internal interface and an external interface, the internal interface may be a data storage interface, and the interface is used for enabling each layer in the metadata service system to store data to the database; the external interface is generally a metadata service interface, and systems such as a data open system and a data directory service system acquire metadata service information required by respective systems by calling the metadata service interface provided by the metadata service system. When the metadata service system stores data through the internal interface, the request initiated by the metadata service system is generally a TCP request, and when other systems acquire metadata service information through the external interface, the query request initiated by other systems is generally an HTTP request.
The user layer generally refers to a system administrator, and the system administrator is mainly responsible for configuration of the metadata service system, management of the metadata standard files, management of the metadata database, management of the metadata and management of metadata user permissions.
The metadata service system provided by the embodiment of the application provides storage service and query service for XSD files respectively corresponding to different service data and XML files taking the XSD files as standards through the metadata service layer, generates a corresponding service interface based on the service provided by the metadata service layer through the metadata service layer, and provides the service interface for the user layer. Therefore, a simple and easily-operated metadata service system is provided for the user, the user experience is improved, meanwhile, different XML documents can be managed in a unified mode, the work complexity and the repeatability of research and development personnel are reduced, and the workload of the research and development personnel is reduced.
Another embodiment of the present application provides a metadata server system, as shown in fig. 3, which, compared with the metadata server system in fig. 2, includes: a metadata storage layer 14, the metadata service layer 11 including: a metadata standard service module 112 and a metadata management service module 114;
the metadata standard service module 112 is configured to parse each XSD file according to the XSD files corresponding to different service data, and extract an XML element node in each XSD file;
the metadata management service module 114 is configured to, for an XML file that takes each XSD file as a standard, analyze an XML value corresponding to an XML element node of the corresponding XSD file;
the metadata storage layer 14 is specifically configured to store the XML values and the XML element nodes correspondingly.
Here, there are many methods for parsing XSD files and XML files in the prior art, for example, the XSD file may be parsed by DOM4J, and the XML file may be parsed by Document Object Model (DOM), XML event driven Model (Simple API for XML, SAX), JDOM, DOM4J, etc., which are described in detail in the prior art and will not be described herein too much.
The metadata standard service module 112 registers the XSD file with the present system after parsing the XSD file. When registering the XSD file, storing the corresponding relationship among the node identification, the access point, the database identification, the XSD file identification and the key searching point corresponding to the XML element node obtained by analysis in a relational database, wherein each XSD file can correspond to one relational database. Wherein, the relational database is generally a Derby database.
After extracting the XML element nodes in each XSD file, the metadata standard service module 112 is further configured to determine corresponding node identifiers for the extracted XML element nodes;
the metadata storage layer 14 is specifically configured to store the extracted XML values in correspondence with node identifiers of the XML element nodes.
Here, the path of the extracted XML element node in the belonging XSD file may be determined as the corresponding node identifier; for each XSD file, an access point is set for the node identification of each XML element node of the XSD file.
In a specific implementation, referring to fig. 4, when parsing the XSD file, in addition to obtaining the XML element nodes, an element type corresponding to each XML element node may also be obtained, where the element type is a type of metadata stored in a current XML element node, and for example, the element type may be string, int, float, or the like. The local elements (XML elements) are generally paths of access point titles in the XSD file to which the access point titles belong, and the corresponding paths of each XML element node in the XSD file to which the access point titles belong are unique, so that the paths can be used as node identifiers of each XML element node, and meanwhile, an access point can be set for each XML element node of each XSD file, at least one access point can be selected from the access points based on user requirements, and the selected at least one access point is set as a query point, so that the metadata base is prevented from storing the same XML value. The access point corresponding to each XSD file XML element node is unique, and the access points corresponding to different XSD file XML element nodes may be the same, which may be determined according to specific situations.
The metadata storage layer 14 is specifically configured to correspondingly store the node identifier and the access point of the XML element node of the XSD file and the identifier of the database corresponding to the XSD file; and
and for each XSD file, correspondingly storing the extracted XML value and the node identifier of the XML element node extracted from the XSD file into a database corresponding to the XSD file.
Here, the node identifier, the access point, and the database identifier of the XML element node are generally stored in a relational database, and the database identifier stored in the relational database is generally a database storing XML values, which may be referred to as a metadata database, and the metadata database is generally created from an XSD file. And the identifications of the metadata bases corresponding to different XSD files are unique.
Because there may be multiple XML values corresponding to each XML element node in the XML file, and the XML file is generally generated using one XSD file as a standard, each XSD file may correspond to one relational database and one or more metadata bases, for example, the XML value corresponding to each XML element node in the XML file using the XSD file as the standard includes a normal value and an abnormal value, the XSD file corresponds to two metadata bases, the two metadata bases respectively store the normal value and the abnormal value, the hierarchical structure in each metadata base is the same, that is, the access point is the same, and the identifier of the metadata base corresponding to the XSD file is stored in the relational database.
When storing XML values, the metadata standard service module judges whether at least two XML files in the XML taking the XSD file as a standard meet the following conditions or not according to each XSD file:
at least two XML element nodes exist for the XML element nodes extracted from the XSD file, and the XML values corresponding to the XML element nodes in the at least two XML files are the same for each XML element node;
and if so, processing according to a preset duplication checking processing rule.
Here, the predetermined duplication check processing rule is generally defined in advance, and for example, the XML file is deleted, the XML value in the XML file is cleared, and the like, as the case may be.
In specific implementation, if the XML values in the multiple XML files are required to be put into a library in the corresponding XSD file, whether the XML values corresponding to the query points of the multiple XML files are the same is searched according to the query points stored in the relational database corresponding to the XSD file, and if the XML values corresponding to the query points are found to be the same in at least two files, the same XML values in the two XML files can be removed. If a plurality of query points are provided, the at least two files need to satisfy that the XML values corresponding to each query point are the same, and then the preset query processing rule is executed.
If only one XML file is required to be put in a storage corresponding to the XSD file, at the moment, according to the query point stored in the relational database corresponding to the XSD file, whether the XML value corresponding to the query point in the metadata base corresponding to the XSD file is the same as the XML value in the XML file or not is searched, and if the XML value is the same, the XML file can be deleted.
In addition, the metadata standard service module is further configured to receive indications of an import metadata standard file or a metadata file, an export metadata standard file or metadata, a delete metadata file (XML file) and a metadata standard file (XSD file), a delete database, and the like of the user layer. And if a metadata standard file deleting instruction is received, deleting the corresponding XSD file, and correspondingly deleting the relational database and the metadata database corresponding to the XSD file, if a metadata database deleting instruction is received, searching the XSD file corresponding to the deleted metadata database and the corresponding relational database, deleting the searched XSD file, and further deleting the relational database and the metadata database corresponding to the XSD file.
When other systems or metadata service systems need to query themselves, the metadata standard service module 112 is further configured to receive an XML query request sent through a query interface provided by the metadata service layer 12, where the XML query request includes an access point and a database identifier;
determining node identifiers of XML element nodes corresponding to the access points and the database identifiers contained in the query request according to node identifiers and access points of XML element nodes of the corresponding stored XSD file and identifiers of a database corresponding to the XSD file; and
and determining an XML value which accords with the query condition from XML values which are stored in the database corresponding to the metadata storage layer and correspond to the node identification of the determined XML element node, and feeding back the XML value.
Here, since the access points stored in the relational databases corresponding to different XSD files may be the same, and the identifiers of the metadata databases are unique, the database identifiers included in the XML query request are generally identifiers of the metadata databases, so that the relational database including the database identifiers can be determined by the database identifiers carried in the XML query request, and further, the node identifiers corresponding to the access points are determined.
In specific implementation, after receiving an XML query request of another system, querying a relational database corresponding to an identifier (e.g., 100) of a metadata database carried in the XML query request, after finding the relational database, searching a node identifier of an XML element node corresponding to an access point (e.g., 10.1.1.1) carried in the XML query request in the relational database, after finding a corresponding node identifier, searching an XML value corresponding to the node identifier in the metadata database with the identifier of 100, and returning the XML value to the other system.
In yet another embodiment of the present application, a metadata service system is provided, as shown in fig. 5, compared with the metadata service system in fig. 3, a metadata service layer 11 in the system further includes: a metadata repository management module 116 and a metadata user authorization management module 118;
a metadata database management module 116, configured to perform at least one of the following operations on the metadata database in the metadata storage layer 14: create, delete, clear, and query.
And the metadata user authorization management module 118 is used for adding, deleting, modifying and authorizing metadata users.
In specific implementation, the metadata management module may create a metadata base corresponding to the XSD file according to an instruction of the user layer, where the metadata base is used to store an XML value in the XML file, and the user layer may delete the metadata base according to an actual requirement, or empty data in the metadata base, or query metadata stored in the metadata base.
Because the metadata service system can provide different services for different metadata users, and the like, when providing storage services for new metadata users, a user layer can add new users through a metadata user authorization management module, and if one or more metadata users in the current metadata users do not use the services provided by the metadata service system any more, the user layer can delete the one or more metadata users through the metadata user authorization management module; if the metadata user needs to modify the user information, the user layer can modify the metadata user information through the metadata user authorization management module; meanwhile, the user layer can also set the authority of the metadata user to access the metadata database through the metadata user authorization management module. The metadata user may be a data open system, a data directory service system, or the like.
Corresponding to the metadata service system in fig. 2, an embodiment of the present application further provides a computer device, as shown in fig. 6, the computer device includes a memory 1000, a processor 2000 and a computer program stored on the memory 1000 and executable on the processor 2000, wherein the processor 2000 implements the metadata service system when executing the computer program.
Specifically, the memory 1000 and the processor 2000 may be general memories and processors, which are not specifically limited herein, and when the processor 2000 runs a computer program stored in the memory 1000, the metadata service system may be executed to solve the problem of inconvenient content query of the current XML file, provide storage services and query services for XSD files corresponding to different service data through the metadata service layer and XML files using each XSD file as a standard, generate corresponding service interfaces based on services provided by the metadata service layer through the metadata service layer, and provide service interfaces for the user layer. Therefore, different XML documents can be managed in a unified mode, the work complexity and the repeatability of research and development personnel are reduced, the workload of the research and development personnel is reduced, meanwhile, a simple and easy-to-operate metadata service system can be provided for a user, and convenience is brought to XML file content query.
Corresponding to the metadata service system in fig. 2, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and the computer program is executed by a processor to execute the metadata service system.
Specifically, the storage medium can be a general storage medium, such as a mobile disk, a hard disk, and the like, and when a computer program on the storage medium is run, the metadata service system can be executed, so as to solve the problem of inconvenient content query of the XML file, provide storage service and query service for XSD files corresponding to different service data respectively through a metadata service layer and XML files using each XSD file as a standard, generate a corresponding service interface based on the service provided by the metadata service layer through the metadata service layer, and provide the service interface to a user layer. Therefore, different XML documents can be managed in a unified mode, the work complexity and the repeatability of research and development personnel are reduced, the workload of the research and development personnel is reduced, meanwhile, a simple and easy-to-operate metadata service system can be provided for a user, and convenience is brought to XML file content query.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments provided in the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus once an item is defined in one figure, it need not be further defined and explained in subsequent figures, and moreover, the terms "first", "second", "third", etc. are used merely to distinguish one description from another and are not to be construed as indicating or implying relative importance.
Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present application, and are used for illustrating the technical solutions of the present application, but not limiting the same, and the scope of the present application is not limited thereto, and although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope disclosed in the present application; such modifications, changes or substitutions do not depart from the spirit and scope of the present disclosure, which should be construed in light of the above teachings. Are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A metadata service system, comprising: a metadata service layer, and a user layer;
the metadata service layer is used for providing storage service and query service for XSD files corresponding to different service data respectively and XML files taking the XSD files as standards;
the metadata service layer is used for generating a corresponding service interface based on the service provided by the metadata service layer and providing the service interface for the user layer; the service interface comprises a data storage interface and a metadata service interface, the data storage interface is used for enabling each layer in the metadata service system to store data to the database, and the metadata service interface is used for providing metadata service information required by different systems.
2. The system of claim 1, further comprising: a metadata storage layer, the metadata service layer comprising: the system comprises a metadata standard service module and a metadata management service module;
the metadata standard service module is used for analyzing each XSD file aiming at the XSD files respectively corresponding to different service data and extracting XML element nodes in each XSD file;
the metadata management service module is used for analyzing an XML value corresponding to an XML element node of the corresponding XSD file aiming at the XML file taking each XSD file as a standard;
and the metadata storage layer is specifically used for correspondingly storing the XML values and the XML element nodes.
3. The system of claim 2, wherein the metadata standard service module is further configured to determine a corresponding node identifier for the extracted XML element node;
and the metadata storage layer is specifically used for correspondingly storing the extracted XML values and the node identifiers of the XML element nodes.
4. The system according to claim 3, wherein the metadata standard service module is specifically configured to determine a path of the extracted XML element node in the XSD file as the corresponding node identifier.
5. The system according to any one of claims 2 to 4, wherein the metadata standard service module is further configured to set, for each XSD file, an access point for a node identification of each XML element node of the XSD file;
the metadata storage layer is specifically used for correspondingly storing the node identifier and the access point of the XML element node of the XSD file and the identifier of the database corresponding to the XSD file; and
and for each XSD file, correspondingly storing the extracted XML value and the node identifier of the XML element node extracted from the XSD file into a database corresponding to the XSD file.
6. The system according to claim 2, wherein the metadata standard service module is further configured to receive an XML query request sent through a query interface provided by the metadata service layer, where the XML query request includes an access point and a database identifier; and
determining node identifiers of XML element nodes corresponding to the access points and the database identifiers contained in the query request according to node identifiers and access points of XML element nodes of the corresponding stored XSD file and identifiers of a database corresponding to the XSD file; and
and determining an XML value which accords with the query condition from XML values which are stored in the database corresponding to the metadata storage layer and correspond to the node identification of the determined XML element node, and feeding back the XML value.
7. The system of claim 2, wherein the metadata standard service module is further configured to register the XSD file with the system after parsing the XSD file.
8. The system according to claim 2, wherein the metadata standard service module is further configured to determine, for each XSD file, whether at least two XML files in the XML standard to the XSD file satisfy the following condition:
at least two XML element nodes exist for the XML element nodes extracted from the XSD file, and the XML values corresponding to the XML element nodes in the at least two XML files are the same for each XML element node;
and if so, processing according to a preset duplication checking processing rule.
9. The system of claim 2, wherein the metadata service layer further comprises: a metadata base management module;
the metadata base management module is used for performing at least one of the following operations on the metadata base in the metadata storage layer: create, delete, clear, and query.
10. The system of claim 1, wherein the metadata service layer further comprises: a metadata user authorization management module;
and the metadata user authorization management module is used for adding, deleting, modifying and authorizing metadata users.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810098956.8A CN108170867B (en) | 2018-01-31 | 2018-01-31 | Metadata service system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810098956.8A CN108170867B (en) | 2018-01-31 | 2018-01-31 | Metadata service system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108170867A CN108170867A (en) | 2018-06-15 |
| CN108170867B true CN108170867B (en) | 2020-12-25 |
Family
ID=62512525
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810098956.8A Active CN108170867B (en) | 2018-01-31 | 2018-01-31 | Metadata service system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108170867B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110297869B (en) * | 2019-05-30 | 2022-11-25 | 北京百度网讯科技有限公司 | AI data warehouse platform and operation method |
| CN116701053B (en) * | 2023-05-30 | 2024-03-19 | 杭州政云数据技术有限公司 | Method, device, equipment and medium for restoring data backup of production environment database |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101557385A (en) * | 2008-04-09 | 2009-10-14 | 北京闻言科技有限公司 | Uniform data format verification method |
| CN102662997A (en) * | 2012-03-15 | 2012-09-12 | 北京播思软件技术有限公司 | Method of storing XML data into relational database |
| CN103530538A (en) * | 2012-07-03 | 2014-01-22 | 沈阳高精数控技术有限公司 | XML safety view querying method based on Schema |
| CN103559321A (en) * | 2013-11-22 | 2014-02-05 | 方正国际软件有限公司 | Document format conversion system |
-
2018
- 2018-01-31 CN CN201810098956.8A patent/CN108170867B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101557385A (en) * | 2008-04-09 | 2009-10-14 | 北京闻言科技有限公司 | Uniform data format verification method |
| CN102662997A (en) * | 2012-03-15 | 2012-09-12 | 北京播思软件技术有限公司 | Method of storing XML data into relational database |
| CN103530538A (en) * | 2012-07-03 | 2014-01-22 | 沈阳高精数控技术有限公司 | XML safety view querying method based on Schema |
| CN103559321A (en) * | 2013-11-22 | 2014-02-05 | 方正国际软件有限公司 | Document format conversion system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108170867A (en) | 2018-06-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11281793B2 (en) | User permission data query method and apparatus, electronic device and medium | |
| CN111258989B (en) | Database migration evaluation method and device, storage medium and computer equipment | |
| CN102054025B (en) | Traffic information resource integration processing method and system | |
| US10180984B2 (en) | Pivot facets for text mining and search | |
| US9483464B2 (en) | Method and system for managing semantic and syntactic metadata | |
| US6772137B1 (en) | Centralized maintenance and management of objects in a reporting system | |
| US11030242B1 (en) | Indexing and querying semi-structured documents using a key-value store | |
| US20140337287A1 (en) | Virtual repository management | |
| US10169491B2 (en) | Query servicing with access path security in a relational database management system | |
| US20170357710A1 (en) | Clustering log messages using probabilistic data structures | |
| CN107103011B (en) | Method and device for realizing terminal data search | |
| CN112307512A (en) | Log desensitization method, device and storage medium | |
| US10445370B2 (en) | Compound indexes for graph databases | |
| CN112434015B (en) | Data storage method and device, electronic equipment and medium | |
| CN108170867B (en) | Metadata service system | |
| US10193974B2 (en) | Managing collaboration of shared content using collaborator indexing | |
| CN116226166A (en) | Data query method and system based on data source | |
| CN115544183A (en) | Data visualization method and device, computer equipment and storage medium | |
| CN117407414A (en) | Method, device, equipment and medium for processing structured query statement | |
| CN113495978B (en) | Data retrieval method and device | |
| US20180349443A1 (en) | Edge store compression in graph databases | |
| KR20160050930A (en) | Apparatus for Processing Transaction with Modification of Data in Large-Scale Distributed File System and Computer-Readable Recording Medium with Program | |
| CN116186116A (en) | Asset problem analysis method based on equal protection assessment | |
| CN113934729A (en) | Data management method based on knowledge graph, related equipment and medium | |
| US11770413B2 (en) | Domain-independent resource security and management |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 100070, No. 101-8, building 1, 31, zone 188, South Fourth Ring Road, Beijing, Fengtai District Applicant after: Guoxin Youyi Data Co., Ltd Address before: 100070, No. 188, building 31, headquarters square, South Fourth Ring Road West, Fengtai District, Beijing Applicant before: SIC YOUE DATA Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |