CN115617781A - Digital object creating and data management method and device - Google Patents
Digital object creating and data management method and device Download PDFInfo
- Publication number
- CN115617781A CN115617781A CN202211014469.1A CN202211014469A CN115617781A CN 115617781 A CN115617781 A CN 115617781A CN 202211014469 A CN202211014469 A CN 202211014469A CN 115617781 A CN115617781 A CN 115617781A
- Authority
- CN
- China
- Prior art keywords
- digital object
- data
- object management
- management node
- node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
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/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/215—Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a method and a device for creating a digital object, wherein the method comprises the following steps: determining data specification information of an information base maintained by the primary digital object management node; creating a normalized digital object in the primary digital object management node according to the data specification information; according to the technical scheme of the application, under the condition that the normalized digital object is successfully established in the primary digital object management node, the normalized digital object is established in the secondary digital object management node according to the data specification information, so that all digital object management nodes can normalize heterogeneous data into a uniform format according to the normalized digital object and store the data. Therefore, the data processing flow of the primary digital object management node after receiving the data reported by each secondary digital object management node is reduced, the data publishing efficiency is improved, and the storage space of the primary digital object management node is saved.
Description
Technical Field
The application relates to the technical field of big data, in particular to the field of data governance and/or the field of data transmission. The application provides a digital object creating method, a digital object data managing method and a digital object data managing device.
Background
With the development of society, the informatization degree is continuously improved, and the data sharing requirements among various industries are stronger and stronger. Particularly, in the government affair industry, along with the advance of information engineering construction, in order to provide government affair services for citizens, it is important to integrate, clean and convert government affairs between provinces and cities to construct an information base facing a certain business field.
In the information base construction process of the related technology, a lower level data node (a city level unit) directly provides data to an upper level data node (a provincial level unit), the upper level data node collects the data reported by each lower level data node, and processes such as data cleaning, processing and conversion are uniformly carried out, so that the information base data is finally formed to provide services to the outside. The superior data node needs to store at least three data of the collected original data, the data in the processing process and the final information base data, and the storage space needed to be occupied is large. And in the process that the lower node transmits the data to the upper data for data summarization, the data safety is difficult to guarantee.
Disclosure of Invention
In view of the above, the present application provides a method and an apparatus for creating a digital object and managing data, so as to solve the above problems.
Specifically, the method is realized through the following technical scheme:
according to a first aspect of the present application, a digital object creating method is provided, which is applied to an information base data management platform, where the information base data management platform is used to manage a digital object management system, the digital object management system is used to manage digital objects and store data associated with the digital objects, and the digital object management system includes multiple levels of digital object management nodes, and includes:
determining data specification information of an information base maintained by the primary digital object management node;
and creating a normalized digital object in each digital object management node according to the data specification information.
According to a second aspect of the present application, there is provided a digital object creating apparatus applied to an information base data management platform for managing a digital object management system for managing digital objects and storing data associated with the digital objects, the digital object management system including a plurality of hierarchical levels of digital object management nodes, including:
a determining module configured to determine data specification information for an information repository maintained by the primary digital object management node;
a creation module configured to create a normalized digital object in each digital object management node according to the data specification information.
According to a third aspect of the present application, there is provided an electronic apparatus comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the method as described in the embodiments of the first aspect and/or the second aspect by executing the executable instructions.
According to a fourth aspect of embodiments herein, there is provided a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method as described in embodiments of the first and/or second aspect above.
According to the technical scheme provided by the application, the normalized digital object is constructed in each digital object management node of the digital object management system according to the normalized data information of the information base by defining the normalized data information of the information base, so that each digital object management node can normalize heterogeneous data into a uniform format according to the normalized digital object for storage, and efficient access to data associated with the digital object can be realized through the identifier of the digital object. Therefore, the data processing flow of the primary digital object management node after receiving the data reported by each secondary digital object management node is reduced, the data publishing efficiency is improved, and the whole data does not need to be reported to the primary digital object management node for storage, so that the data security can be ensured, and the storage space of the primary digital object management node is saved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
FIG. 1 is a flow chart illustrating a method of digital object creation according to an exemplary embodiment of the present application;
FIG. 2 is a schematic diagram of a network architecture of a digital object management system according to an exemplary embodiment of the present application;
FIG. 3 is a schematic diagram of a network structure of a digital object creation system to which an embodiment of the present application is applied;
FIG. 4 is a multi-party interaction flow diagram illustrating a method of digital object creation according to an exemplary embodiment of the present application;
FIG. 5 is a flow chart illustrating yet another method of digital object creation according to an exemplary embodiment of the present application;
FIG. 6 is a multi-party interaction flow diagram illustrating yet another digital object creation method according to an exemplary embodiment of the present application;
FIG. 7 is a schematic diagram of a digital object creation electronic device shown in accordance with an exemplary embodiment of the present application;
fig. 8 is a block diagram of a digital object creation apparatus shown in accordance with an exemplary embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. The following description refers to the accompanying drawings in which the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as primary information, and similarly, the primary information may also be referred to as first information, without departing from the scope of the present application. The word "if," as used herein, may be interpreted as "at \8230; \8230when" or "when 8230; \823030when" or "in response to a determination," depending on the context.
Next, examples of the present application will be described in detail.
In the related art, the information base is usually constructed by reporting stored data to an upper data node by a lower data node, collecting and processing the received data by the upper data node, and constructing the information base according to the processed data. For example, taking the information base for constructing the provincial government affair information in zhejiang province as an example, each city level department in zhejiang province needs to report the data stored in each business system to the zhejiang province level department, and the zhejiang province level department collects the received data. However, the types of data stored in the business systems of the local authorities may not be consistent, and the provincial authorities need to further process the data after receiving different types of heterogeneous data. Therefore, for the provincial authorities, in addition to the finally issued information base data, the data in the original data and the data in the data processing process reported by the respective local authorities need to be stored, and the stored data is more.
When the information base data is updated, the provincial organization needs to perform the processes of data collection, processing and release, and each process can be executed only after the last process is completed, so that the provincial organization can update the released information base data the next day after the city organization reports the updated data to the provincial organization, and the data updating efficiency is low.
In order to solve the above problem, fig. 1 is a flowchart illustrating a digital object creation method according to an exemplary embodiment of the present application. As shown in fig. 1, the method is applied to an information base data management platform for managing a digital object management system for managing a digital object and storing data associated with the digital object, the digital object management system including a plurality of levels of digital object management nodes, and may include the following steps:
step 102: determining data specification information of an information base maintained by the primary digital object management node;
step 104: and creating a normalized digital object in each digital object management node according to the data specification information.
In some embodiments, the digital Object management system may be a Handle system under a DOA (digital Object Architecture) Architecture, and is composed of one GHR (Global Handle Registry) and multiple LHSs (Local Handle services), where the digital Object management node may be a LHS node in the Handle system, and the LHSs are distributed systems and may dynamically expand according to requirements to provide good query and storage performance.
DOA is a logical architecture that supports interactions between systems and can be used to manage and maintain digital objects, DO, i.e., digital objects, where an object can be viewed as a data entity and each object has a unique identifier to distinguish between other objects. The DOA platform is a secure third-party service, and can interact with objects such as service providers and service users, for example, process service call requests issued by the service users, manage rights of digital objects defined by the service providers, and facilitate data interaction between the service providers and the service users through data objects. The digital object corresponding to the service provider is managed through the DOA platform, so that the service user does not need to directly request the service provider when calling the service deployed by the service provider, but the digital object managed in the DOA platform is called by the DOA platform agent, so that the service provider does not need to pay attention to whether the service provider is symmetrical to the information of the service user calling the service when developing the service deployed by the service provider, and the development complexity of the service provider is simplified.
In some embodiments, each digital object management node in the digital object management system may correspond to one or more business systems, respectively, and the business systems may synchronize the latest data to the corresponding digital object management nodes in real time. Fig. 2 is a schematic diagram illustrating a network structure of a digital object management system according to an exemplary embodiment of the present application, and as shown in fig. 2, the digital object management system may include a provincial LHS node 201 (primary digital object management node), a city-level first department LHS node 202a (secondary digital object management node 202 a), a city-level second department LHS node 202b (secondary digital object management node 202 b), and a city-level third department LHS node 202c (secondary digital object management node 202 c). The LHS node 202a of the market-level first department corresponds to the market-level first department system, and can acquire and store data in the market-level first department system according to the digital object; the second department in the market LHS node 202b corresponds to the second department in the market system, and can acquire and store data in the second department in the market system according to the digital object; the LHS node 202c of the third department in market level corresponds to the third department in market level system, and can acquire and store data in the third department in market level system. And the market-level first department LHS node 202a, the market-level second department LHS node 202b, and the market-level third department LHS node 202c may all report the stored data to the provincial LHS node 201.
In some embodiments, the information library may include a theme library, a basic library, a theme library, and the like, which may be configured as required by a person skilled in the art, and the present application is not limited thereto.
In some embodiments, the data specification information includes at least one of: data composition, data size, data format, data source, data priority. Before constructing the information base, the information base data management platform needs to define the data specification of the data content to be contained in the information base to be constructed in advance. For example, if the information base to be constructed is a "human basic information" subject base, the data specification information of the subject base can be predetermined as shown in table 1 below:
TABLE 1
The field names can be equivalent to data in data specification information, namely, the information base data management platform defines a human basic information thematic base in advance and can mainly comprise a first identity number, a name and a gender; the field format can be equivalent to the data format in the data specification information, and the field length is equivalent to the data size in the data specification information, namely the information base data management platform defines the field format of the first identity number recorded in the 'human basic information' subject library as string in advance, and the field length is 32; the priority may be equivalent to the data priority in the data specification information, that is, the information base data management platform defines in advance that the information of the "first identity number" recorded in the "human basic information" subject base is determined according to the information of the first identity number recorded in the first department system.
According to this embodiment, the information base data management platform defines the canonical data information of the information base, and constructs a normalized digital object in each digital object management node of the digital object management system according to the canonical data information of the information base, so that each digital object management node can normalize heterogeneous data into a uniform format according to the normalized digital object for storage, and efficient access to data associated with the digital object can be achieved through an identifier of the digital object. Therefore, in the process of constructing the information base, the data processing flow of the primary digital object management node after receiving the data reported by each secondary digital object management node can be reduced, the data publishing efficiency is improved, and the whole data does not need to be reported to the primary digital object management node for storage, so that the data security can be ensured, and the storage space of the primary digital object management node can be saved.
In some embodiments, the multi-hierarchy digital object management nodes include a primary digital object management node and at least one secondary digital object management node, and the creating a normalized digital object in each digital object management node according to the data specification information includes: creating a normalized digital object in the primary digital object management node according to the data specification information; and under the condition that the normalized digital object is successfully created in the primary digital object management node, creating the normalized digital object in the secondary digital object management node according to the data specification information. The normalized digital object is preferentially established in the first-level digital object management node, so that the digital object management node at the lower level can determine whether to establish the normalized digital object according to the establishment result of the digital object of the first-level digital object management node, and the first-level digital object management node can check the normalized digital object to determine that the normalized digital object meets the requirement of the information base to be maintained.
In some embodiments, the database data management platform is further configured to manage a blockchain system, the digital object management node corresponding to a blockchain node in the blockchain system, the creating a normalized digital object in the secondary data object management node according to the data specification information including:
triggering the block chain node corresponding to the primary digital object management node to generate a digital object creation event corresponding to the data specification information, enabling other block chain nodes in the block chain system to receive the digital object creation event through consensus, and informing the digital object management nodes corresponding to the other block chain nodes to create the normalized digital object according to the digital object creation event.
Blockchains are an emerging technology where several computing devices participate together in "billing" to maintain a complete distributed database. Because the blockchain technology is based on basic characteristics such as a consensus mechanism, signature verification and the like, the data security, transparency and non-falsification on the blockchain network can be ensured, and each data change in the blockchain can trigger the generation of a credible change record.
Therefore, after the normalized digital object in the primary digital object management node is successfully created, the normalized data information may be uplink-stored, and by recording a corresponding digital object creation event in the block chain node corresponding to the primary digital object management node, other block chain nodes in the block chain system may acquire the digital object creation event based on the self-characteristics of the block chain system, so as to notify the digital object management nodes corresponding to the other block chain nodes in the block chain system. Thereby creating the normalized digital object in other digital object management nodes (secondary digital object management nodes) and storing the data specification information in the blockchain in a credible mode.
Fig. 3 is a schematic diagram of a network structure of a digital object creation system to which an embodiment of the present invention is applied, and as shown in fig. 3, the digital object creation system includes an information base data management platform 301, a digital object management system, and a blockchain system. The network architecture in the digital object management system may refer to the related description in the embodiment shown in fig. 2, and is not described herein again. The blockchain system may include blockchain link point 302 corresponding to provincial LHS node 201 (primary digital object management node 201), blockchain link point 303a corresponding to municipality first department LHS node 202a (secondary digital object management node 202 a), blockchain link point 303b corresponding to municipality second department LHS node 202b (secondary digital object management node 202 b), and blockchain link point 303c corresponding to municipality third department LHS node 202c (secondary digital object management node 202 c).
In the technical scheme of the application, before the information base maintained by the primary digital object management node is constructed, the data specification information of the information base can be defined through the information base data management platform, so that the normalized digital object is created in the digital object management node according to the defined data specification information. This is explained in detail below with reference to fig. 4. FIG. 4 is a multi-party interaction flow diagram illustrating a method for creating a digital object according to an exemplary embodiment of the present application. As shown in fig. 4, the interactive process of the db data management platform 301, the primary digital object management node 201, the secondary digital object management nodes 202a to 202c, the block chain node 302, and the block chain nodes 303a to 303c includes the following steps:
step 401, the information base data management platform 301 determines the data specification information of the information base.
Step 402, the information base data management platform 301 creates a normalized digital object in the primary digital object management node 201 according to the data specification information.
In step 403, the information base data management platform 301 receives the creation success information returned by the primary digital object management node 201.
In step 404, the repository data management platform 301 triggers the blockchain node 302 to generate a digital object creation event.
In step 405, the block link points 303a to 303c obtain digital object creation events that are commonly recognized by the block chain node 302.
In step 406, block link points 303a 303c determine whether the digital object creation time is associated with itself.
In step 407, block link points 303a to 303c send digital object creation notifications to the corresponding secondary digital object management nodes 202a to 202c, if it is determined that the digital object creation time is relevant to itself.
At step 408, the secondary digital object management nodes 202 a-202 c create a normalized digital object.
In some embodiments, the digital object includes an object identification corresponding to the digital object and data associated with the digital object, the method further comprising: each secondary digital object management node determines target data to be reported according to the object identification of the digital object managed by the primary digital object management node and the object identification of the digital object managed by the secondary digital object management node, and reports the target data to the primary digital object management node; and the primary digital object management node summarizes the target data reported by each secondary digital object management node.
Under the condition that the digital object management nodes at all levels successfully create the standardized digital objects, when the information base is created for the first time, each secondary digital object management node can determine a target digital object of the digital objects managed by the secondary digital object management node, wherein the object identifier of the target digital object corresponds to the object identifier of the digital object managed by the primary digital object management node. And taking the data associated with the target digital object as target data and reporting the target data to a primary digital object management node.
After receiving the target data reported by each secondary digital object management node, the primary digital object management node can summarize the received target data and store the summarized target data in the digital object managed by the primary digital object management node, thereby realizing the creation of the information base.
FIG. 5 is a flow chart illustrating yet another method of digital object creation according to an exemplary embodiment of the present application. As shown in fig. 5, on the basis that the digital object creating method according to any one of the foregoing embodiments creates a digital object and stores data associated with the digital object, the information base data management platform corresponds to a digital object management system and a blockchain system, the digital object management system is used for managing the digital object created according to the digital object creating method according to any one of the foregoing embodiments and stores data associated with the digital object, the digital object management system comprises a primary digital object management node and at least one secondary digital object management node, and the digital object management node in the digital object management system corresponds to a blockchain node in the blockchain system, and the method may include the following steps:
step 502: receiving target data reported by any secondary digital object management node, wherein the target data is associated with a target digital object;
step 504: judging whether to update the data associated with the target digital object in the primary digital object management node according to the target data;
step 506: under the condition that data related to a target digital object in the primary digital object management node is updated according to the target data, triggering block chain link points corresponding to the primary digital object management node to record data updating events corresponding to the target data, so that other block chain nodes in the block chain system acquire the data updating events through consensus, and notifying digital object management nodes corresponding to the other block chain link points according to the data updating information.
In the related art, data updating of an information base is usually performed by reporting, by a lower data node, data to be updated to an upper data node, and performing, by the upper data node, data updating on an information base maintained by the upper data node according to received data. In this process, only the upgrade data node and the lower level data node that reports the update data can perceive the modification of the data. The other lower-level data nodes may still store the data before updating because the other lower-level data nodes cannot perceive the data updating, so that the data stored in the other lower-level data nodes is inconsistent with the data stored in the upper-level data node.
In order to solve the above problem, in this embodiment, by combining the digital object management system with the blockchain system, after a higher-level digital object management node (a first-level digital object management node) in the digital object management system performs data update according to data reported by a lower-level digital object management node (a second-level digital object management node), data update information related to the current data update may be uplink-stored in the blockchain system by generating data update time in a blockchain node corresponding to the higher-level digital object management node. Due to the self-recognition characteristic of the blockchain system, when data update information is recorded in a blockchain link point in the blockchain system, other blockchain nodes in the blockchain system can also acquire the data update information, so that the acquired data update information can be notified to the corresponding digital object management nodes, and each digital object management node in the digital object management system can know the data update.
Because each digital object management node in the digital object management system can know the data update in the digital object management system, each digital object management node in the digital object management system can participate in the construction process of the information base, and the non-uniformity of the data associated with the same digital object in different digital object management nodes is avoided.
In some embodiments, the blockchain system is further configured to receive an API call request sent by a specific application, and return data update information stored in the blockchain system for the data update event to the specific application according to the API call request. Since a digital object management node in the digital object management system can generate a data update event in the blockchain system each time a data update is performed, each time the update data and update operation are maintained and trusted by the blockchain system storage. Therefore, when a specific application needs to acquire a data update record of the information base, the update data and the update operation stored in the blockchain system can be acquired by sending an API call request to the blockchain system.
In some embodiments, said determining whether to update data associated with a target digital object in said primary digital object management node based on said target data comprises:
examining and approving the data updating authority of any two-level digital object management node according to the pre-configured data updating authority information;
in the event that it is determined that there is a data update permission for the primary digital object management node for any of the secondary digital object management nodes and a data update permission for the target digital object, updating data associated with the target digital object in the primary digital object management node in accordance with the target data.
In this embodiment, the information base data management platform further has a rights management function, and rights information of each digital object management node may be preset. After receiving the target data reported by the secondary digital object management node, the information base data management platform can firstly judge whether the second digital object management node has the authority for updating the data of the target digital object in the first digital object management node according to the authority information, and can update the data which is stored in the first digital object management node and is associated with the target digital object only under the condition that the second digital object management node is determined to have the authority for updating the data of the target digital object in the first digital object management node, so that the reliability of the data stored in the information base is improved.
In some embodiments, before reporting the target data to the information base data management platform, the secondary digital object management node may first send a query request for data associated with the target digital object to the information base data management platform. And the thematic data management platform returns the data associated with the target digital object in the primary digital object management node to the secondary digital object management node according to the received data query request. The second-level digital object management node determines whether the received data is consistent with the target data maintained by the second-level digital object management node and whether the target data maintained by the second-level digital object management node needs to be reported to the information base data management platform according to the data priority predefined by the second-level digital object management node.
In some embodiments, the digital object management node corresponding to the other blockchain node may determine whether to update the local data after receiving the target data sent by the other blockchain node. The digital object management node corresponding to the other block link point may determine whether the data stored by the digital object management node and managed by the target digital object is consistent with the target data, and in case of determining that the data is inconsistent, further perform a determination according to uniqueness and predefined data priority of the data associated with the target digital object.
For example, it will be understood by those skilled in the art that a person may have multiple second identities at the same time, i.e. the second identity information of a person is not unique. If a digital object management node determines that the updated second identity information received from the block link node is inconsistent with the second identity information maintained locally, the digital object management node does not necessarily need to update the second identity information maintained locally to the target data.
For another example, the information base data management platform may preset that the first identity number information provided by the first department system has a higher priority than the first identity number information provided by the third department system. Under the condition that the digital object management node corresponding to the first department system determines that the updated first identity number information received from the block chain node is not consistent with the locally maintained first identity number information, if the updated first identity number information provided by the block chain node is provided by the third department system and the locally maintained first identity number information is provided by the first department system, the locally maintained first identity number information does not need to be modified. Even further, the digital object management node may report the first identity number information maintained by the digital object management node to the information base data management platform, so as to modify the first identity number information provided by the third department and currently maintained in the information base.
A schematic network structure of a data management system shown in an exemplary embodiment of the present application is the same as the schematic network structure of the data management system shown in fig. 3, and is not described herein again. This is explained in detail below with reference to fig. 6. FIG. 6 is a multi-party interaction flow diagram illustrating yet another method for creating a digital object according to an exemplary embodiment of the present application. As shown in fig. 6, the interactive process of the db data management platform 301, the primary digital object management node 201, the secondary digital object management nodes 202a to 202c, the block chain node 302, and the block chain nodes 303a to 303c includes the following steps:
step 601: secondary digital object management node 202a sends a data query request to repository data management platform 301.
For example, the data associated with the target digital object stored in the provincial LHS node is shown in Table 2 below:
TABLE 2
The data associated with the target digital object stored in the market level first department LHS node is shown in table 3 below:
TABLE 3
The data associated with the target digital object stored in the market level second department LHS node is shown in table 4 below:
TABLE 4
The data associated with the target digital object stored in the LHS node of the third department of the market is shown in table 5 below:
TABLE 5
The market level first department LHS node may send a data query request to the information repository data management platform 301 for second identity number information associated with a digital object having an identifier of 86.100/330100 XXX.
Step 602: secondary digital object management node 202a receives data information returned by information repository data management platform 301.
As shown in table 2 above, the second identity number information stored in the provincial LHS node is EA1234567. The LHS node in the first department in the city level may receive the second identity number information returned by the information base data management platform 301 as EA1234567.
Step 603: secondary digital object management node 202a determines whether data needs to be updated.
Although the second identity number information stored locally by the first department LHS node can be determined to be inconsistent with the second identity number information stored in the information base maintained by the provincial LHS node through comparison. However, since the second id information is not unique, the LHS node in the first department in the city class may add new second id information EA1234567 on the basis of the locally stored second id information E12345678.
Step 604: secondary digital object management node 202a sends the target data to repository data management platform 301.
The LHS node of the first department in the market can send the second identity number information E12345678 stored locally to the information base data management platform 301.
Step 605: the repository data management platform 301 determines whether the secondary digital object management node 202a has update rights.
The information base data management platform 301 may determine, according to preset permission information, whether the data update permission for the second identity number information in the provincial LHS node exists in the local first department LHS node.
Step 606: the repository data management platform 301 sends the target data to the primary digital object management node 201.
And under the condition that the information base data management platform 301 determines that the LHS node of the first department in the market level has the updating authority, sending second identity number information E12345678 to the LHS node in the province level.
Step 607: primary digital object management node 201 updates the data associated with the target digital object based on the target data.
After receiving the second identity number information E12345678 reported by the LHS node of the first department at the market level, the LHS node at the province level can add E12345678 to the second identity number information associated with the digital object with the identifier of 86.100/330100 XXX.
Step 608: primary digital object management node 201 sends update success information to repository data management platform 301.
The update success information may be sent to the information repository data management platform 301 after the second identity number information associated with the digital object having the identifier of 86.100/330100XXX is successfully updated by the provincial LHS node.
Step 609: the repository data management platform 301 triggers the blockchain node 302 to generate a data update event.
Step 610: the blockchain nodes 303a to 303c acquire the data update event recorded in the blockchain node 302 by consensus.
Step 611: block link points 303 a-303 c notify secondary digital object management nodes 202 a-202 c, respectively, of data update events.
Step 612: secondary digital object management nodes 202 a-202 c update the local data based on the received data update event.
After the data update event notified by the local-level first department LHS node, the local-level second department LHS node, and the local-level third department LHS node at the block link point, second identity number information E12345678 updated in the data update event may be obtained, and the second identity number information E12345678 is compared with the second identity number information stored locally. Data associated with the digital objects with the identifiers of 86.100/330100XXX in the first department LHS node at the market level, the second department LHS node at the market level and the third department LHS node at the market level do not contain the second identity number, so that data updating operation is not needed.
Corresponding to the method embodiments, the present specification also provides an embodiment of an apparatus.
Fig. 7 is a schematic structural diagram of a digital object creation electronic device according to an exemplary embodiment of the present application. Referring to fig. 7, at the hardware level, the electronic device includes a processor 702, an internal bus 704, a network interface 706, a memory 708, and a non-volatile storage 710, although it may also include hardware required for other services. The processor 702 reads the corresponding computer program from the non-volatile storage 710 into the memory 708 and then runs it. Of course, besides the software implementation, the present application does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.
Fig. 8 is a block diagram illustrating a digital object creation apparatus according to an exemplary embodiment of the present application. Referring to fig. 8, the apparatus is applied to an information repository data management platform for managing a digital object management system for managing a digital object and storing data associated with the digital object, the digital object management system comprising a primary digital object management node and at least one secondary digital object management node, the apparatus comprising a determining module 802 and a creating module 804, wherein:
determining module 802 is configured to determine data specification information for a repository maintained by the primary digital object management node;
a creation module 804 is configured to create a normalized digital object in each digital object management node according to the data specification information.
Optionally, the creating a normalized digital object in each digital object management node according to the data specification information includes:
creating a normalized digital object in the primary digital object management node according to the data specification information;
and under the condition that the normalized digital object is successfully established in the primary digital object management node, establishing the normalized digital object in the secondary digital object management node according to the data specification information.
Optionally, the database data management platform is further configured to manage a blockchain system, a digital object management node in the digital object management system corresponds to a blockchain node in the blockchain system, and the second creating module 906 is configured to trigger the blockchain node corresponding to the primary digital object management node to generate a digital object creating event corresponding to the data specification information, so that other blockchain nodes in the blockchain system receive the digital object creating event through consensus and notify the digital object management nodes corresponding to the other blockchain nodes to create a specified digital object according to the digital object creating event.
Optionally, the data specification information includes at least one of: data composition, data size, data format, data source, data priority.
Optionally, the digital object includes an object identifier and data associated with the object identifier, and the apparatus further includes:
the reporting module is configured to determine target data information to be reported by each secondary digital object management node according to the object identifier of the digital object managed by the primary digital object management node and the object identifier of the digital object managed by the secondary digital object management node, and report the target data to the primary digital object management node;
and the summarizing module is configured to summarize the target data reported by the secondary digital object management nodes by the primary digital object management nodes.
Optionally, on the basis of the apparatus for creating a digital object as described above, the information base data management platform corresponds to a digital object management system and a blockchain system, the digital object management system includes a primary digital object management node and at least one secondary digital object management node, the digital object management node in the digital object management system corresponds to a blockchain node in the blockchain system, and the apparatus further includes:
the receiving module is configured to receive target data reported by any secondary digital object management node, wherein the target data is associated with a target digital object;
a judging module configured to judge whether to update data associated with a target digital object in the primary digital object management node according to the target data;
the trigger module is configured to trigger block chain nodes corresponding to the primary digital object management nodes to record data update events corresponding to the target data when data associated with a target digital object in the primary digital object management nodes are updated according to the target data, so that other block chain nodes in the block chain system acquire the data update events through consensus, and notify digital object management nodes corresponding to the other block chain nodes according to the data update information.
Optionally, the determining module is configured to approve the data updating right of any secondary digital object management node according to preconfigured data updating right information; in the event that it is determined that there is a data update permission for the primary digital object management node for any of the secondary digital object management nodes and a data update permission for the target digital object, updating data associated with the target digital object in the primary digital object management node in accordance with the target data.
Optionally, the blockchain system is further configured to receive an API call request sent by a specific application, and return data update information for the data update event stored in the blockchain system to the specific application according to the API call request.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and 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 modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
In an exemplary embodiment, there is also provided a non-transitory computer readable storage medium, e.g. a memory, comprising instructions executable by a processor of a digital object management device to implement a method as described in any of the above embodiments, such as the method may comprise:
determining data specification information of an information base maintained by the primary digital object management node; creating a normalized digital object in the primary digital object management node according to the data specification information; and under the condition that the normalized digital object is successfully created in the primary digital object management node, creating the normalized digital object in the secondary digital object management node according to the data specification information.
The non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like, which are not limited in this application.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (11)
1. A digital object creation method applied to an information base data management platform for managing a digital object management system for managing a digital object and storing data associated with the digital object, the digital object management system including a plurality of hierarchical levels of digital object management nodes, the method comprising:
determining data specification information of an information base;
and creating a normalized digital object in each digital object management node according to the data specification information.
2. The method of claim 1, wherein the multiple hierarchical levels of digital object management nodes include a primary digital object management node and at least one secondary digital object management node, and wherein creating a canonical digital object in each digital object management node based on the data specification information comprises:
creating a normalized digital object in the primary digital object management node according to the data specification information;
and under the condition that the normalized digital object is successfully created in the primary digital object management node, creating the normalized digital object in the secondary digital object management node according to the data specification information.
3. The method of claim 2, wherein the repository data management platform further corresponds to a blockchain system, wherein a digital object management node in the digital object management system corresponds to a blockchain node in the blockchain system, and wherein creating a normalized digital object in the secondary data object management node according to the data specification information comprises:
triggering block chain nodes corresponding to the primary digital object management node to generate digital object creation events corresponding to the data specification information, enabling other block chain nodes in the block chain system to receive the digital object creation events through consensus, and informing the digital object management nodes corresponding to the other block chain nodes to create the normalized digital objects according to the digital object creation events.
4. The method of claim 2, wherein the digital object includes an object identification corresponding to the digital object and data associated with the digital object, the method further comprising:
determining target data information to be reported by each secondary digital object management node according to the object identification of the digital object managed by the primary digital object management node and the object identification of the digital object managed by the secondary digital object management node, and reporting the target data to the primary digital object management node;
and summarizing the target data reported by each secondary digital object management node through the primary digital object management node.
5. The method of claim 1, wherein the data specification information comprises at least one of:
data composition, data size, data format, data source, data priority.
6. The method of creating a digital object according to any of claims 1 to 5, wherein the repository data management platform corresponds to a digital object management system and a blockchain system, the digital object management system comprises a primary digital object management node and at least one secondary digital object management node, the digital object management node in the digital object management system corresponds to a blockchain node in the blockchain system, and the method comprises:
receiving target data reported by any two-level digital object management node, wherein the target data is associated with a target digital object;
judging whether to update the data associated with the target digital object in the primary digital object management node according to the target data;
under the condition that data related to a target digital object in the primary digital object management node is updated according to the target data, triggering block chain link points corresponding to the primary digital object management node to record data updating events corresponding to the target data, so that other block chain nodes in the block chain system acquire the data updating events through consensus, and notifying digital object management nodes corresponding to the other block chain link points according to the data updating information.
7. The method of claim 6, wherein said determining whether to update data associated with a target digital object in said primary digital object management node based on said target data comprises:
examining and approving the data updating authority of any two-level digital object management node according to the pre-configured data updating authority information;
in the event that it is determined that there is a data update permission for the primary digital object management node for any of the secondary digital object management nodes and a data update permission for the target digital object, updating data associated with the target digital object in the primary digital object management node in accordance with the target data.
8. The method of claim 6, wherein the blockchain system is further configured to receive an API call request sent by a specific application, and return data update information stored in the blockchain system for the data update event to the specific application according to the API call request.
9. A digital object creation apparatus for use in an information repository data management platform for managing a digital object management system for managing digital objects and storing data associated with the digital objects, the digital object management system including a plurality of hierarchical levels of digital object management nodes, the apparatus comprising:
a determination module configured to determine data specification information of an information repository;
a creation module configured to create a normalized digital object in each digital object management node according to the data specification information.
10. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the method of any one of claims 1-8 by executing the executable instructions.
11. A computer-readable storage medium having stored thereon computer instructions, which, when executed by a processor, carry out the steps of the method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211014469.1A CN115617781A (en) | 2022-08-23 | 2022-08-23 | Digital object creating and data management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211014469.1A CN115617781A (en) | 2022-08-23 | 2022-08-23 | Digital object creating and data management method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115617781A true CN115617781A (en) | 2023-01-17 |
Family
ID=84856434
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211014469.1A Pending CN115617781A (en) | 2022-08-23 | 2022-08-23 | Digital object creating and data management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115617781A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116303458A (en) * | 2023-03-17 | 2023-06-23 | 北京信源电子信息技术有限公司 | Management method for data objects in handle system |
-
2022
- 2022-08-23 CN CN202211014469.1A patent/CN115617781A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116303458A (en) * | 2023-03-17 | 2023-06-23 | 北京信源电子信息技术有限公司 | Management method for data objects in handle system |
| CN116303458B (en) * | 2023-03-17 | 2023-10-13 | 北京信源电子信息技术有限公司 | Management method for data objects in handle system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108965289B (en) | A kind of network security collaboration means of defence and system | |
| CN105610987A (en) | Method, application and system for managing server cluster | |
| CN101202751B (en) | System and method for providing SNMP data for virtual networking devices | |
| CN111814089A (en) | Page rendering method and device, rendering server and storage medium | |
| CN108600163B (en) | Cloud environment distributed hash chain architecture and cloud data integrity verification method | |
| US7398284B2 (en) | Policy based system management | |
| JP2005346543A (en) | Method of inheriting community, community management apparatus, and community management program | |
| CN102741845A (en) | URL reputation system | |
| CN110266872B (en) | Address book data management and control method and device, cloud address book system, computer equipment and computer readable storage medium | |
| CN104636437B (en) | A kind of processing method and processing device of event notification method, monitor | |
| CN107111510B (en) | Method and device for operating VNF packet | |
| CN111447069B (en) | Low-frequency access data processing method based on block chain | |
| CN112685499B (en) | Method, device and equipment for synchronizing flow data of working service flow | |
| CN116601630A (en) | Generating defensive target database attacks through dynamic honey database responses | |
| CN115617781A (en) | Digital object creating and data management method and device | |
| CN113722114A (en) | Data service processing method and device, computing equipment and storage medium | |
| US8224933B2 (en) | Method and apparatus for case-based service composition | |
| CN113438317B (en) | Gateway data processing method and device | |
| CN112199200A (en) | Resource scheduling method and device, computer equipment and storage medium | |
| CN112069529A (en) | Block chain-based volume management method and device, computer and storage medium | |
| CN116074376A (en) | Content management system | |
| CN115174529B (en) | Network processing method and device, electronic equipment and storage medium | |
| CN112118290B (en) | Program analysis-based data resource management and control method | |
| CN114710350A (en) | Allocation method and device for callable resources | |
| CN111782615A (en) | Block chain-based large file storage method and system and computer equipment |
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 |