An ancestral temple building culture gene database management system

Abstract

The application relates to the field of cultural heritage digital management, and discloses a temple building culture gene database management system, which comprises a source access module, an identity analysis module, a structure signature module, a candidate merging module, a reverse search module and a write management module. The source access module is used for receiving multi-source temple building culture gene data and generating source evidence records. The identity analysis module is used for analyzing carrier relationships and culture expression roles. The structure signature module is used for generating carrier role structure signatures. The candidate merging module is used for generating the source evidence records. The reverse search module is used for generating an extended candidate set. The write management module is used for establishing a new temple culture gene instance when the updated identity merging result does not point to an existing temple culture gene instance. Through the conversion of multi-source temple building culture gene data into source evidence records, reverse search and candidate expansion are performed on the existing temple culture gene instances outside the candidate range according to the carrier role structure signatures, so that unified identity mapping and controlled writing between different source evidence records and the same temple culture gene instance are realized.

Description

Technical Field

[0001] This invention relates to the field of digital management technology for cultural heritage, specifically to a database management system for the cultural genes of ancestral hall architecture. Background Technology

[0002] With the development of digital acquisition and database management technologies for cultural heritage, the spatial layout, architectural components, decorative patterns, inscriptions, and cultural semantics of ancestral halls are gradually being preserved in the form of text, images, point clouds, surveying data, and 3D model data. To achieve unified organization of the above heterogeneous data, it is usually necessary to extract the identity of the ancestral hall, architectural object, cultural gene type, and cultural semantics from different data, and to establish the relationship between the original data, architectural carriers, and ancestral hall cultural gene instances.

[0003] Existing ancestral hall architectural culture data management typically involves retrieving existing instances based on ancestral hall identifiers, cultural gene names, type tags, or semantic similarity. If no matching instance is found, a new ancestral hall cultural gene instance is created. However, the same ancestral hall cultural gene may use different names, semantic expressions, and architectural object identifiers in different data sources. This prevents source records pointing to the same architectural carrier from entering the same candidate range, resulting in the same ancestral hall cultural gene instance being repeatedly created as multiple database objects. Summary of the Invention

[0004] To address the shortcomings of existing technologies, this invention provides a database management system for ancestral hall architectural culture genes, which solves the problem that existing ancestral hall architectural culture data management easily leads to the same ancestral hall cultural gene instance being repeatedly created as multiple database objects.

[0005] To achieve the above objectives, the present invention provides the following technical solution: a database management system for ancestral hall architectural culture genes, comprising:

[0006] The source access module is used to receive multi-source ancestral hall architectural cultural gene data and generate source evidence records;

[0007] The identity resolution module is used to receive the source evidence records and resolve the ancestral hall's main entity identifier, cultural gene type, cultural semantic proposition, architectural carrier role path, carrier relationship, and cultural expression role.

[0008] The structural signature module is used to receive the architectural carrier role path, carrier relationship and cultural expression role and generate carrier role structural signature;

[0009] The candidate merging module is used to receive the ancestral hall main entity identifier, cultural gene type, cultural semantic proposition, carrier role structure signature and existing ancestral hall cultural gene instance and generate the identity merging result of the source evidence record and the existing ancestral hall cultural gene instance;

[0010] The reverse retrieval module is used to receive the identity merging result and the carrier role structure signature. When the identity merging result indicates the formation of a proposed new ancestral hall cultural gene instance, it retrieves existing ancestral hall cultural gene instances outside the candidate range determined by the candidate merging module based on the carrier role structure signature and generates an extended candidate set.

[0011] The write management module is used to receive the expanded candidate set and the identity merging result, update the identity merging result according to the expanded candidate set, establish identity associations according to the updated identity merging result, and establish new ancestral hall culture gene instances when the updated identity merging result does not point to an existing ancestral hall culture gene instance.

[0012] By adopting the above technical solution, multi-source ancestral hall architectural cultural gene data is converted into source evidence records. An identity merging result is generated by combining the ancestral hall's main entity identifier, cultural gene type, cultural semantic proposition, and carrier role structure signature. Before writing the proposed new ancestral hall cultural gene instance, a reverse search and candidate expansion are performed on existing ancestral hall cultural gene instances outside the candidate range based on the carrier role structure signature. Based on the updated identity merging result, an identity association or a new ancestral hall cultural gene instance is selected. This achieves unified identity mapping and controlled writing between evidence records from different sources and the same ancestral hall cultural gene instance, solving the problem that existing ancestral hall architectural cultural data management easily leads to the same ancestral hall cultural gene instance being repeatedly created as multiple database objects.

[0013] Preferably, the source access module includes:

[0014] The data receiving unit is used to receive the multi-source ancestral hall architectural cultural gene data and read the data source identifier, original content and data location;

[0015] A fingerprint generation unit is used to generate an original data fingerprint based on the data source identifier, original content, and data location.

[0016] The duplicate import verification unit is used to compare the original data fingerprint with the existing original data fingerprint and generate a duplicate import flag.

[0017] The evidence record generation unit is used to write data that is not marked as a duplicate import into the source evidence record.

[0018] Preferably, the identity resolution module includes:

[0019] The ancestral hall main entity parsing unit is used to determine the ancestral hall main entity identifier based on the ancestral hall identity data in the source evidence record;

[0020] A type mapping unit is used to determine the cultural gene type based on the cultural semantic description and cultural gene type ontology in the source evidence record;

[0021] A semantic proposition generation unit is used to convert the cultural semantic descriptions in the source evidence records into cultural semantic propositions.

[0022] The carrier role parsing unit is used to generate architectural carrier role paths, carrier relationships, and cultural expression roles based on the architectural object hierarchy and cultural expression relationships in the source evidence record.

[0023] Preferably, the structural signature module includes:

[0024] The path normalization unit is used to normalize the roles and sort the paths of the building carrier roles.

[0025] A relation normalization unit is used to unify the relation type and relation direction of the carrier relations.

[0026] The structural signature generation unit is used to generate structural signatures for carrier roles based on the normalized architectural carrier role paths, carrier relationships, and cultural expression roles.

[0027] Preferably, the candidate merging module includes:

[0028] The initial candidate generation unit is used to generate an initial candidate instance set based on the ancestral hall main entity identifier, cultural gene type, and cultural semantic proposition.

[0029] A group-level evidence generation unit is used to generate group-level matching data based on the cultural semantic proposition and the carrier role structure signature.

[0030] The merge constraint generation unit is used to generate merge constraint data based on the main entity identifier of the ancestral hall, the relationship of cultural gene type, and the contradictory state of cultural semantics.

[0031] The global merging unit is used to generate a preferred merging result and a candidate merging result based on the initial candidate instance set, group-level matching data and merging constraint data, and to generate an identity merging result based on the preferred merging result.

[0032] Preferably, the candidate merging module further includes:

[0033] The source lineage processing unit is used to generate source lineage data and source independence data based on the derivation relationship between the source evidence records, and to update the group-level matching data based on the source independence data;

[0034] A stability gating unit is used to generate stable merge data based on the preferred merge result and the alternative merge result, and to generate a merge release flag for the identity merge result when the stable merge data meets the stability condition, and to generate a merge delay flag for the identity merge result when the stable merge data does not meet the stability condition.

[0035] Preferably, the reverse retrieval module includes:

[0036] A new marker unit is proposed to be used to determine, from the identity merging results with the merging and release marker, the proposed new ancestral hall cultural gene instance that does not point to an existing ancestral hall cultural gene instance.

[0037] The structural aggregation unit is used to generate an aggregated carrier role structural signature based on the carrier role structural signature corresponding to the cultural gene instance of the proposed new ancestral hall.

[0038] The reverse retrieval unit is used to retrieve existing ancestral hall culture gene instances outside the initial candidate instance set based on the aggregated carrier role structure signature.

[0039] The candidate extension unit is used to generate a duplicate creation conflict and write the existing ancestral hall cultural gene instance into the extension candidate set when the proposed new ancestral hall cultural gene instance has the same ancestral hall main entity identifier, compatible cultural gene type and matching carrier role structure signature as the retrieved existing ancestral hall cultural gene instance.

[0040] Preferably, the write management module includes:

[0041] The merge update unit is used to trigger the candidate merge module to regenerate the identity merge result and the merge release flag or merge postponement flag corresponding to the regenerated identity merge result based on the expanded candidate set.

[0042] The locked resource generation unit is used to generate locked resources based on the main entity identifier of the ancestral hall, the cultural gene type, the architectural carrier role path, and the extended candidate set.

[0043] The transaction review unit is used to re-perform candidate retrieval and duplicate creation conflict identification after obtaining the exclusive lock on the locked resource.

[0044] Preferably, the write management module further includes:

[0045] An identity association unit is used to establish an identity association between the source evidence record and the existing ancestral hall cultural gene instance when the regenerated identity merging result has the merging release mark and points to the existing ancestral hall cultural gene instance.

[0046] The instance establishment unit is used to establish a new ancestral hall culture gene instance when the regenerated identity merging result has the merging release mark, does not point to an existing ancestral hall culture gene instance, and does not have a duplicate creation conflict, and to establish the identity association between the source evidence record and the new ancestral hall culture gene instance.

[0047] The alias update unit is used to write the original cultural gene name in the source evidence record into the alias data of the associated ancestral hall cultural gene instance.

[0048] Preferably, it further includes a storage module, the storage module comprising:

[0049] The cultural gene type storage unit is used to store cultural gene type entities and their type relationship data;

[0050] The Ancestral Hall Cultural Gene Instance Storage Unit is used to store ancestral hall cultural gene instances and their instance main identifiers.

[0051] A source evidence storage unit is used to store the source evidence records and their original data locations;

[0052] An identity association storage unit is used to store identity association data between the source evidence record and the ancestral hall cultural gene instance.

[0053] This invention provides a database management system for the cultural genes of ancestral hall architecture. It has the following beneficial effects:

[0054] 1. This invention converts multi-source ancestral hall architectural cultural gene data into source evidence records, combines the ancestral hall main entity identifier, cultural gene type, cultural semantic proposition, and carrier role structure signature to generate identity merging results, and before writing the proposed new ancestral hall cultural gene instance, performs reverse retrieval and candidate expansion on existing ancestral hall cultural gene instances outside the candidate range based on the carrier role structure signature, thereby selecting to establish identity associations or new ancestral hall cultural gene instances based on the updated identity merging results. This achieves unified identity mapping and controlled writing between evidence records from different sources and the same ancestral hall cultural gene instance, solving the problem that existing ancestral hall architectural cultural data management easily leads to the same ancestral hall cultural gene instance being repeatedly established as multiple database objects.

[0055] 2. This invention independently preserves multi-source ancestral hall architectural cultural gene data in the form of source evidence records, and retains the data source identifier, original content, data location and original data fingerprint, so that ancestral hall cultural gene instances can be traced back to the corresponding original data, avoiding the overwriting or loss of the original descriptions in each data source during the merging process, and providing a complete data foundation for subsequent instance review, source verification and data updates.

[0056] 3. This invention standardizes the role paths, relationships, and cultural expression roles of architectural carriers, and corrects the merging evidence by combining source lineage and source independence. This makes it less likely that differences in names, description order, and repeated citations of the same source data in different materials will cause repeated interference in the merging judgment, thereby improving the stability of identity determination among multi-source heterogeneous data.

[0057] 4. This invention performs a reverse structural search outside the candidate range before writing the cultural gene instance of the proposed ancestral hall, and re-executes the candidate search and duplicate creation conflict identification after obtaining the exclusive lock, so that the candidate missed detection and the conflict caused by concurrent writing can be rediscovered and processed before the instance is established, thereby maintaining the consistency between the main identifier, source evidence association and alias data of the ancestral hall cultural gene instance. Attached Figure Description

[0058] Figure 1 This is an architecture diagram of a database management system for ancestral hall architectural culture genes proposed in this invention.

[0059] Figure 2 This is a flowchart of a method for managing a database of ancestral hall architectural cultural genes, as proposed in an embodiment of the present invention.

[0060] Figure 3 This is a flowchart of the source access module processing proposed in an embodiment of the present invention;

[0061] Figure 4 This is a flowchart of the reverse retrieval module processing proposed in an embodiment of the present invention;

[0062] Figure 5 This is a flowchart of the write management module processing according to an embodiment of the present invention. Detailed Implementation

[0063] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0064] Example 1:

[0065] In a first embodiment of the present invention, the present invention provides a database management system for ancestral hall architectural cultural genes, such as... Figure 1 As shown, it includes:

[0066] Please see the appendix Figure 3 The source access module is used to receive multi-source ancestral hall architectural cultural gene data and generate source evidence records;

[0067] Furthermore, the source access module includes:

[0068] The data receiving unit is used to receive multi-source ancestral hall architectural cultural gene data and read the data source identifier, original content and data location;

[0069] The fingerprint generation unit is used to generate the original data fingerprint based on the data source identifier, original content, and data location.

[0070] The duplicate import verification unit is used to compare the original data fingerprint with the existing original data fingerprint and generate a duplicate import flag.

[0071] The evidence record generation unit is used to write data that is not marked as a duplicate import into the source evidence record.

[0072] Specifically, the source access module is used to solidify the source of multi-source data entering the database and completely intercept duplicates, so that each data first forms a traceable source evidence record, instead of directly establishing an ancestral hall cultural gene instance, and provides the identity resolution module with data that has unified fields and retains the original source.

[0073] In this embodiment, the data receiving unit receives local gazetteers, genealogies, surveying and mapping data, image annotations, point cloud annotations, and 3D model attributes, and reads the data source identifier, original content, and data location. Specifically, the data source identifier is used to distinguish the source of the data, and the data location is used to indicate page numbers, image regions, point cloud objects, or model components. In some embodiments, textual data is encapsulated according to a unified character encoding, while image, point cloud, and model data are encapsulated according to raw byte streams.

[0074] The fingerprint generation unit generates the fingerprint according to the following formula. The original data fingerprint of each data point: ,in, Indicates the original content. Indicates the data source identifier. Indicates the data location. This indicates that the fields will be concatenated according to a preset field order. This indicates a 256-bit hash processing. This represents the original data fingerprint; in this embodiment, the text content is preferably encoded using UTF-8, and the length of the original data fingerprint is preferably 256 bits.

[0075] The duplicate import check unit generates duplicate import flags according to the following formula: ,in, This indicates that the original data fingerprint set has been stored. This indicates a duplicate import flag. A value of 1 indicates the existence of a fragment from the same source, while a value of 0 indicates that no fragment from the same source was found. The original data fingerprint is completely identical as the condition for determining duplicate imports.

[0076] Evidence record generation unit in When the value is zero, the data source identifier, original content, data location, original data fingerprint, import time, and data modality type are written into the source evidence record and output to the identity resolution module; To prevent the same data from being written to the database multiple times due to repeated uploads or format conversions, the import log is recorded and associated with existing source evidence records.

[0077] The identity resolution module is used to receive source evidence records and resolve the main entity identifier of the ancestral hall, cultural gene type, cultural semantic proposition, architectural carrier role path, carrier relationship and cultural expression role;

[0078] Furthermore, the identity resolution module includes:

[0079] The main entity analysis unit of the ancestral hall is used to determine the main entity identifier of the ancestral hall based on the ancestral hall identity data in the source evidence record.

[0080] Type mapping unit, used to determine cultural gene type based on cultural semantic description and cultural gene type ontology in source evidence records;

[0081] The semantic proposition generation unit is used to convert cultural semantic descriptions in source evidence records into cultural semantic propositions.

[0082] The carrier role analysis unit is used to generate architectural carrier role paths, carrier relationships, and cultural expression roles based on the architectural object hierarchy and cultural expression relationships in the source evidence records.

[0083] Specifically, the identity resolution module is used to convert the ancestral hall name, cultural description, and architectural object information in the source evidence record into unified identity data and maintain its association with the original source, providing standardized input for subsequent structural signature processing.

[0084] In this embodiment, the ancestral hall main entity parsing unit extracts the ancestral hall name, address, spatial location, and file number, and generates candidate ancestral halls in the ancestral hall main data table. (Regarding the first...) Article source evidence record and the first For each candidate ancestral hall, generate ancestral hall identity matching data: ,in, Indicates name consistency. Indicates address consistency. Indicates spatial proximity. Indicates the consistency of file numbers. This represents the ancestral hall identity matching data; in this embodiment, , , and The preferred values ​​are 0.3, 0.2, 0.3, and 0.2; when the highest ancestral hall identity matching data is not lower than 0.8, the corresponding main identifier will be determined as the main entity identifier of the ancestral hall; otherwise, a pending confirmation mark will be generated and the instance creation will be temporarily suspended.

[0085] The type mapping unit matches the cultural semantic description with the type semantics and hierarchical relationships in the cultural gene type ontology. The type that meets the preset conditions and has the highest degree of matching is determined as the cultural gene type. Spatial progression and ritual order correspond to the spatial ritual type, and component construction and craft inheritance correspond to the construction technique type.

[0086] The semantic proposition generation unit transforms cultural semantic descriptions into cultural semantic propositions that include semantic subjects, semantic relations, semantic objects, negation states, and limiting information. Specifically, the description of the progressive arrangement of the entrance hall, ancestral hall, and sleeping hall, reflecting the clan's ritual order, can be transformed into a cultural semantic proposition expressing the clan's hierarchical order through a progressive spatial sequence.

[0087] The carrier role analysis unit generates architectural carrier role paths along the object hierarchy of ancestral halls, individual buildings, spaces, components, and decorative carriers. It generates carrier relationships based on location, composition, progression, symmetry, and shared expression, and determines the cultural expression roles of each architectural carrier. These cultural expression roles include main carriers, auxiliary carriers, spatial sequence nodes, symbolic image carriers, and textual evidence carriers. Missing levels are marked with empty roles to preserve path positions. The analysis results are associated with source evidence records and output to the structural signature module to reduce the impact of naming differences on subsequent merging.

[0088] The structural signature module is used to receive the architectural carrier role path, carrier relationship and cultural expression role and generate the carrier role structural signature;

[0089] Furthermore, the structure signature module includes:

[0090] The path normalization unit is used to normalize the roles and sort the paths of building carrier roles.

[0091] The relation normalization unit is used to unify the relation type and relation direction of the carrier relations.

[0092] The structural signature generation unit is used to generate structural signatures for carrier roles based on the normalized architectural carrier role paths, carrier relationships, and cultural expression roles.

[0093] Specifically, the structural signature module is used to convert the architectural hierarchy information and cultural expression relationships output by the identity resolution module into stable structural identifiers, so that when different data sources use different names or different record orders to describe the same architectural expression structure, they can still form comparable and unified data.

[0094] In this embodiment, the path normalization unit maps building unit roles, space roles, component roles, decorative carrier roles, and cultural expression roles to normalized role codes based on a preset role vocabulary. When the semantic matching degree of a role is not less than 0.85, it is mapped to the corresponding normalized role; otherwise, the original role is retained and a supplementary mark is generated. When the main hall and the ancestral hall are mapped to the same building unit role, their original names are still saved in the source evidence record.

[0095] The relation normalization unit converts synonymous carrier relations into a unified relation type and determines the relation direction according to the standardized role coding. For adjacent and symmetrical relations, they are arranged according to the path coding order at both ends; for relations of location, composition, support, and joint expression, the preset master-slave direction is retained, and the relationship between the foyer and the ancestral hall and the ancestral hall being located after the foyer are uniformly converted into a forward-backward progressive relationship.

[0096] The structural signature generation unit records the normalized set of building carrier role paths as follows: The set of carrier relationships is denoted as The set of cultural expression roles is denoted as And generate the carrier role structure signature: ,in, This indicates that normalization processes such as role coding, path sorting, relationship direction unification, and relationship sorting are performed sequentially. Indicates the first Each piece of source evidence records the carrier role structure signature.

[0097] Further generate the signature index: ,in, This indicates that a 256-bit hash is performed on the carrier role structure signature. The signature index is represented in this embodiment. The signature index is preferably 256 bits long and is associated with the source evidence record and output to the candidate merging module to reduce the impact of name differences and record order differences on identity merging.

[0098] The candidate merging module is used to receive the ancestral hall main entity identifier, cultural gene type, cultural semantic proposition, carrier role structure signature and existing ancestral hall cultural gene instances, and generate the source evidence record and the identity merging result of the existing ancestral hall cultural gene instances.

[0099] Furthermore, the candidate merging module includes:

[0100] The initial candidate generation unit is used to generate an initial set of candidate instances based on the main entity identifier of the ancestral hall, the cultural gene type, and the cultural semantic proposition.

[0101] Group-level evidence generation unit is used to generate group-level matching data based on cultural semantic propositions and carrier role structure signatures;

[0102] The merge constraint generation unit is used to generate merge constraint data based on the main entity identifier of the ancestral hall, the relationship of cultural gene type, and the contradictory state of cultural semantics.

[0103] The global merge unit is used to generate preferred merge results and alternative merge results based on the initial candidate instance set, group-level matching data, and merge constraint data, and to generate identity merge results based on the preferred merge results.

[0104] Furthermore, the candidate merging module also includes:

[0105] The source lineage processing unit is used to generate source lineage data and source independence data based on the derivation relationship between source evidence records, and to update group-level matching data based on the source independence data;

[0106] The stability gating unit is used to generate stable merge data based on the preferred merge result and the alternative merge result, and to generate a merge release flag for the identity merge result when the stable merge data meets the stability condition, and to generate a merge delay flag for the identity merge result when the stable merge data does not meet the stability condition.

[0107] Specifically, the candidate merging module is used to establish a constrained identity correspondence between source evidence records and existing ancestral hall cultural gene instances, and to perform global verification of candidate results by combining cultural semantics, architectural carrier structure and source independence, so as to provide acceptable identity merging results for subsequent reverse retrieval of newly proposed instances.

[0108] In this embodiment, the initial candidate generation unit selects instances from existing ancestral hall cultural gene instances that belong to the same ancestral hall main entity as the current source evidence record, are compatible in cultural gene type, and have similar cultural semantics, forming an initial candidate instance set: ,in, Indicates the first The initial set of candidate instances of source evidence records, Indicates the first An example of existing ancestral hall cultural genes. and The main entity identifiers of the ancestral hall represent the source evidence records and existing examples of ancestral hall cultural genes, respectively. Indicates the compatibility of cultural gene types. Indicates the consistency of cultural semantic propositions. and These represent the type compatibility threshold and the semantic filtering threshold, respectively; in this embodiment, The preferred value is 0.7. The preferred value is 0.6.

[0109] The group-level evidence generation unit generates semantic group matching data and carrier structure group matching data respectively, and forms group-level matching data according to the following formula: ,in, This indicates the degree of consistency between the source evidence record and the carrier role structure signature of existing ancestral hall cultural gene instances. This indicates group-level matching data. and These represent the semantic group weight and the carrier structure group weight, respectively. In this embodiment, The preferred value is 0.4. The preferred value is 0.6. When the clan ritual order and the central axis ritual system have different names, but the corresponding progressive structures of the gate hall, ancestral hall and sleeping hall are consistent, the carrier structure group matching data is used to supplement the identity judgment deviation caused by semantic differences.

[0110] The source lineage processing unit imports relationships based on transcription, citation, replication, annotation, and model attributes to trace the root source set and calculates source independence: ,in, and Let each represent the root source set of the two compared objects. Indicates the degree of independence of the source. This represents a stable parameter to prevent the denominator from being zero; in this embodiment, The preferred value is 10 to the power of negative 6. The updated group-level matching data is represented as follows: ,in, This indicates the updated group-level matching data. The minimum retention factor for evidence of common origin is represented, which is preferably 0.3 in this embodiment.

[0111] The merging constraint generation unit imposes a unique constraint on the generation of nodes with different main entity identifiers, mutually exclusive cultural gene types, or contradictory cultural semantic propositions, and a common constraint on the generation of nodes with consistent precise carrier role structure signatures, compatible cultural gene types, and corresponding cultural semantic propositions.

[0112] The global merge unit generates the probability of the same instance based on the updated group-level matching data, and determines the preferred merge result and the second smallest alternative merge result with the minimum merge loss under the must-have-same-consistency constraint, must-have-different-consistency constraint and transitive consistency constraint. Global merge allows the removal of low-confidence matching relationships that cause relationship conflicts, and avoids the spread of a single erroneous match along the transitive relationship.

[0113] The stable gating unit generates merged stable data according to the following formula: ,in, and These represent nodes in the preferred merge result and the alternative merge result, respectively. With nodes The shared state of belonging This represents the set of nodes participating in the current merge. This represents merged stable data; in this embodiment, A merge release marker is generated when the time is no less than 0.9; otherwise, a merge postponement marker is generated. Source evidence records with merge postponement markers remain at the source evidence layer and are not included in the ancestral hall cultural gene instance writing process.

[0114] The candidate merging module is used to establish a constrained identity correspondence between source evidence records and existing ancestral hall cultural gene instances, and to verify the source dependency and the stability of the merging results. This allows records with different names but consistent cultural semantics and architectural carrier structure to be associated with the same instance, while preventing records with insufficient evidence from directly entering the instance writing process.

[0115] In this embodiment, the initial candidate generation unit uses the first... The source evidence records are the objects of processing. Instances with consistent main entity identifiers, compatible cultural gene types, and cultural semantics that meet preset conditions are retrieved from existing ancestral hall cultural gene instances to form an initial candidate instance set. ,in, Represents the initial set of candidate instances. Indicates the first An example of existing ancestral hall cultural genes. and The main entity identifiers of the ancestral hall, representing source evidence records and existing examples, are respectively... Indicates the compatibility of cultural gene types. Indicates the consistency of cultural semantic propositions. and These represent the type compatibility threshold and the semantic candidate threshold, respectively; in this embodiment, The preferred value is 0.8. The preferred value is 0.6.

[0116] The group-level evidence generation unit generates semantic group matching data and carrier structure group matching data respectively: ,in, This indicates group-level matching data. This indicates the structural consistency of the normalized path and carrier relationships in the carrier role structural signature. and These represent the semantic group weight and the carrier structure group weight, respectively; in this embodiment, The preferred value is 0.4. The preferred value is 0.6; when the names of the clan ritual order and the central axis ritual system differ, but both correspond to the progressive carrier structure of the gate hall, the ancestral hall and the sleeping hall, the carrier structure group forms corresponding matching data.

[0117] The source lineage processing unit determines the root source set based on transcription, citation, annotation, and model attribute import relationships, and calculates source independence: ,in, Indicates the degree of independence of the source. and This represents the root source set of the corresponding record. Indicates the root source weight. Indicates the stable parameter; in this embodiment, The preferred option is one. The preferred value is 10 to the power of negative 6. The updated group-level matching data is represented as follows: ,in, This indicates the updated group-level matching data. This represents the minimum retention factor for evidence of common origin; in this embodiment, The preferred value is 0.2.

[0118] The merging constraint generation unit sets nodes with different main entity identifiers, mutually exclusive cultural gene types, or contradictory cultural semantics as "must be different" constraints, and sets nodes with consistent precise carrier role structure signatures and corresponding core cultural semantics as "must be the same" constraints. Nodes with the same carrier do not constitute "must be the same" constraints on their own.

[0119] The global merge unit generates the probability that node pairs belong to the same instance based on the updated group-level matching data, and selects the preferred merge result and the second-lowest alternative merge result with the lowest merge loss under the must-have-same-must-dissimilar-must-different-must-different-must-different-others constraint and transitive constraint. The transitive constraint is expressed as: ,in, Represents a node With nodes Whether they belong to the same ancestral hall cultural gene instance, the global merging process allows breaking low-matching node relationships that cause overall conflicts, rather than directly performing continuous merging on local matching results.

[0120] The stabilization gating unit generates merge-stable data based on the loss difference between the preferred merge result and the alternative merge results: ,in, This indicates merging stable data. and These represent the merge loss of the preferred merge result and the alternative merge result, respectively. This represents the number of valid candidate relationships; in this embodiment, the stability threshold is preferably 0.05. A merge release flag is generated when the value is not lower than the stable threshold. When the value falls below a stable threshold, a merge pause marker is generated, thereby outputting the stable identity merging result to the reverse retrieval module.

[0121] Please see the appendix Figure 4The reverse retrieval module is used to receive the identity merging result and the carrier role structure signature. When the identity merging result indicates the formation of a proposed new ancestral hall cultural gene instance, it retrieves existing ancestral hall cultural gene instances outside the candidate range determined by the candidate merging module based on the carrier role structure signature and generates an extended candidate set.

[0122] Furthermore, the reverse retrieval module includes:

[0123] A new marker unit is proposed to identify proposed new ancestral hall cultural gene instances that do not point to existing ancestral hall cultural gene instances from the identity merging results with merging and release markers.

[0124] The structural aggregation unit is used to generate an aggregated carrier role structural signature based on the carrier role structural signature corresponding to the cultural gene instance of the proposed new ancestral hall.

[0125] The reverse retrieval unit is used to retrieve existing ancestral hall culture gene instances outside the initial candidate instance set based on the aggregation carrier role structure signature.

[0126] The candidate extension unit is used to generate a duplicate creation conflict and write the existing ancestral hall cultural gene instance into the extension candidate set when the proposed new ancestral hall cultural gene instance has the same ancestral hall main entity identifier, compatible cultural gene type and matching carrier role structure signature as the retrieved existing ancestral hall cultural gene instance.

[0127] Specifically, the reverse retrieval module is used to perform structural backtracking verification on existing instances that may have been missed in the initial candidate retrieval before new instances are created from the stable merging results. This allows existing instances that were not included in the initial candidate range due to differences in cultural names or semantic expressions to re-participate in identity merging and provides expanded candidate data for the writing management module.

[0128] In this embodiment, the proposed new marker unit reads the identity merging results with the merging release marker. When the identity merging result is not associated with an existing ancestral hall culture gene instance, the corresponding source evidence records are combined to form a proposed new ancestral hall culture gene instance, and a proposed new marker is generated. Identity merging results with the merging postponement marker do not enter the reverse retrieval process.

[0129] The structural aggregation unit extracts the carrier role structural signatures of evidence records from various sources within the cultural gene instance of the proposed ancestral hall, and determines the support of each normalized structural element based on the source credibility: ,in, Indicates the first An example of the cultural heritage of a proposed new ancestral hall. This indicates the source evidence record. Indicates the credibility of the source. Indicates the carrier role structure signature. This indicates the standardized carrier role path or carrier relationship. Indicates the support of structural elements. This represents a stable parameter. In this embodiment, The preferred value is 10 to the power of negative 6, and the preferred structural element support threshold is 0.6. Structural elements that reach the structural element support threshold are sorted by path and their relationship directions are unified to form an aggregate carrier role structural signature.

[0130] The reverse retrieval unit limits the retrieval scope by the main entity identifier of the ancestral hall, and calculates the structural compatibility based on the aggregate carrier role structure signature and existing ancestral hall cultural gene instances outside the initial candidate instance set: ,in, This indicates an example of the cultural genes of the proposed new ancestral hall and the first Structural compatibility of existing ancestral hall cultural gene examples Indicates the consistency of the carrier role path. Indicates the consistency of the carrier relationship. and This indicates the corresponding weight; in this embodiment, The preferred value is 0.6. The preferred value is 0.4, and the preferred structural compatibility threshold is 0.8.

[0131] When candidate extension units share the same ancestral hall main entity identifier, have a cultural gene type compatibility of no less than 0.8, and a structural compatibility of no less than 0.8, a duplicate creation conflict is generated. The corresponding existing ancestral hall cultural gene instance is then written into the extension candidate set. If there is a clear contradiction in the core cultural semantics of the two, no duplicate creation conflict is generated. The extension candidate set is output to the write management module to trigger the regeneration of the identity merging results.

[0132] Please see the appendix Figure 5 The management module receives the expanded candidate set and the identity merging result, updates the identity merging result based on the expanded candidate set, establishes identity associations according to the updated identity merging result, and establishes a new ancestral hall culture gene instance when the updated identity merging result does not point to an existing ancestral hall culture gene instance.

[0133] Furthermore, the write management module includes:

[0134] The merge update unit is used to trigger the candidate merge module to regenerate the identity merge result and the merge release flag or merge postponement flag corresponding to the regenerated identity merge result based on the expanded candidate set;

[0135] The locked resource generation unit is used to generate locked resources based on the main entity identifier of the ancestral hall, the cultural gene type, the architectural carrier role path, and the extended candidate set.

[0136] The transaction review unit is used to re-perform candidate retrieval and duplicate creation conflict identification after acquiring an exclusive lock on the locked resource.

[0137] Furthermore, the write management module also includes:

[0138] The identity association unit is used to establish an identity association between the source evidence record and the existing ancestral hall cultural gene instance when the regenerated identity merging result has a merging release mark and points to the existing ancestral hall cultural gene instance.

[0139] The instance creation unit is used to create a new ancestral hall culture gene instance when the regenerated identity merging result has a merging release mark, does not point to an existing ancestral hall culture gene instance, and there is no duplicate creation conflict, and to establish the identity association between the source evidence record and the new ancestral hall culture gene instance.

[0140] The alias update unit is used to write the original cultural gene name in the source evidence record into the alias data of the associated ancestral hall cultural gene instance.

[0141] Specifically, the write management module is used to receive the extended candidate set output by the reverse retrieval module, perform identity merging and concurrent write verification on the proposed new ancestral hall cultural gene instance again, and complete instance association or instance creation based on the verified merging status, so that the same ancestral hall cultural gene instance maintains a unified instance master identifier during continuous import and concurrent import.

[0142] In this embodiment, the merging and updating unit adds existing ancestral hall culture gene instances in the expanded candidate set to the candidate range of the corresponding source evidence record, calls the candidate merging module to regenerate the preferred merging result, alternative merging result, and identity merging result, and redetermines the merging stable data. When the regenerated merging stable data meets the stability condition, a merging release flag is generated; otherwise, a merging postponement flag is generated. Identity merging results with merging postponement flags do not enter the database writing process.

[0143] The locked resource generation unit extracts the building unit role, spatial role, component role, and cultural expression role from the building carrier role path to generate the first... The lock key corresponding to the anchor point of each carrier character: ,in, The identifier of the main entity of the ancestral hall in the cluster to be merged. Indicates cultural gene type, Indicates the first Anchor points for each carrier role, This indicates that the fields will be concatenated according to a preset field order. This indicates a 256-bit hash processing. This indicates the carrier role anchor point locking key; in this embodiment, the five carrier role anchor points with the highest support are selected first.

[0144] The locked resource set is represented as: ,in, Indicates locking the set of resources, Indicates the number of anchor points for the carrier role. Indicates an expanded candidate set. This indicates the instance master identifier of each existing ancestral hall cultural gene instance in the expanded candidate set. This indicates that the resources are arranged in order of their identifiers; in this embodiment, the preferred waiting time for the exclusive lock is five seconds.

[0145] The transaction review unit requests exclusive locks in the order of arrangement, and after obtaining all exclusive locks, it re-executes candidate retrieval and duplicate creation conflict identification. If a new existing ancestral hall culture gene instance is found during the locking period, it is added to the expanded candidate set and identity merging results are generated again.

[0146] When the regenerated identity merging result has a merging release mark and points to an existing ancestral hall cultural gene instance, the identity association unit establishes an identity association between the source evidence record and the existing ancestral hall cultural gene instance, and saves the merging time, carrier role structure signature and merging status.

[0147] The instance creation unit generates a new instance master identifier only when the regenerated identity merging result has a merging release mark, does not point to an existing ancestral hall culture gene instance, and there is no duplicate creation conflict. It then associates the source evidence record in the merged cluster with the new ancestral hall culture gene instance.

[0148] The alias update unit reads the original cultural gene names from the evidence records of each source and writes the original cultural gene names that are different from the instance normative names into the alias data. When the clan ritual order and the central axis ritual system are merged and point to the same ancestral hall cultural gene instance, one name is used as the instance normative name and the other name is saved as an alias.

[0149] It also includes a storage module, which includes:

[0150] The cultural gene type storage unit is used to store cultural gene type entities and their type relationship data;

[0151] The Ancestral Hall Cultural Gene Instance Storage Unit is used to store ancestral hall cultural gene instances and their instance main identifiers.

[0152] Source evidence storage unit, used to store source evidence records and the location of their original data;

[0153] The identity association storage unit is used to store identity association data between source evidence records and ancestral hall cultural gene instances.

[0154] Specifically, the storage module is used to receive the data generated by each processing module, and saves the cultural gene type, ancestral hall cultural gene instance, source evidence record and identity association respectively. It maintains the correspondence between multi-source evidence and unique instance through instance master identifier, and provides a data foundation for subsequent query, merging and verification and instance update.

[0155] In this embodiment, the cultural gene type storage unit stores type identifiers, standard names, superior types, subordinate types, compatibility relationships, and mutual exclusion relationships. Generally, type relationships are established using directed association records, enabling the type mapping unit to read type data based on a unified cultural gene type ontology.

[0156] The ancestral hall cultural gene instance storage unit stores the instance master identifier, the ancestral hall master entity identifier, the cultural gene type, the standard name, alias data, the carrier role structure signature, and the instance status. In some embodiments, the same valid instance master identifier corresponds to only one ancestral hall cultural gene instance.

[0157] The source evidence storage unit saves source evidence records, original data fingerprints, original content locations, data source identifiers, and merging status, and retains their location relationship with the original data.

[0158] The identity association storage unit generates the identity association index according to the following formula: ,in, Indicates the source evidence record identifier, The main identifier representing an example of ancestral hall cultural genes. Indicates the time when the identity association was established. This indicates concatenation by field order. The identity association index is represented in this embodiment. The identity association index is preferably 256 bits to avoid the repeated establishment of identity associations between evidence records from the same source and the same ancestral hall cultural gene instance.

[0159] Example 2:

[0160] In a second embodiment of the present invention, the present invention provides a method for managing a database of ancestral hall architectural cultural genes, such as... Figure 2 As shown, the process includes the following:

[0161] Receive multi-source ancestral hall architectural cultural gene data and generate source evidence records;

[0162] Receive source evidence records and analyze the main entity identifier of the ancestral hall, cultural gene type, cultural semantic proposition, architectural carrier role path, carrier relationship and cultural expression role;

[0163] Receive architectural carrier role paths, carrier relationships, and cultural expression roles, and generate carrier role structural signatures;

[0164] Receive the main entity identifier of the ancestral hall, the cultural gene type, the cultural semantic proposition, the carrier role structure signature, and the existing cultural gene instances of the ancestral hall, and generate the source evidence record and the identity merging result of the existing cultural gene instances of the ancestral hall;

[0165] Receive the identity merging result and the carrier role structure signature. When the identity merging result indicates the formation of a proposed new ancestral hall cultural gene instance, retrieve existing ancestral hall cultural gene instances outside the candidate range determined by the candidate merging module based on the carrier role structure signature and generate an extended candidate set.

[0166] Receive the expanded candidate set and the identity merging result, update the identity merging result according to the expanded candidate set, establish identity associations according to the updated identity merging result, and establish new ancestral hall culture gene instances if the updated identity merging result does not point to an existing ancestral hall culture gene instance.

[0167] During the continuous data collection and supplementation of ancestral hall architectural cultural gene data, the same cultural gene may be recorded separately in local chronicles, genealogies, surveying and mapping data, image annotations, point cloud annotations, and 3D model attributes. Due to differences in the names, object numbers, and descriptions used by different sources, directly creating instances using a single name or field can easily lead to multiple instances of cultural genes within the same ancestral hall that express the same architectural relationship, resulting in scattered associations of source data and duplicate query results. To solve the above problems, a database management method for ancestral hall architectural cultural genes provided by this invention is adopted, the process of which is as follows: Figure 2 As shown. The specific implementation process of this method is as follows:

[0168] First, receive multi-source ancestral hall architectural cultural gene data, generate original data fingerprints based on data source identifiers, original content and data location, exclude duplicate imported data, and write the remaining data into the source evidence record;

[0169] Subsequently, the main entity identifier and cultural gene type of the ancestral hall were determined from the source evidence records. The cultural semantic description was converted into a cultural semantic proposition. The architectural carrier role path, carrier relationship and cultural expression role were generated according to the hierarchical relationship of ancestral hall, building unit, space, component and decorative carrier.

[0170] Next, the roles and paths of the building carrier roles are normalized and sorted, the carrier relationships are unified in type and direction, and a carrier role structural signature is generated.

[0171] Then, based on the main entity identifier of the ancestral hall, the cultural gene type, and the cultural semantic proposition, existing ancestral hall cultural gene instances are retrieved to form an initial candidate instance set; group-level matching data is generated based on the cultural semantic proposition and the carrier role structure signature, and the group-level matching data is corrected based on the derivation relationship between the source evidence records;

[0172] Then, based on the main entity identifier of the ancestral hall, the relationship of cultural gene type, and the contradictory state of cultural semantics, merge constraint data is generated. Under the merge constraint, the preferred merge result and the alternative merge result are determined, and the stable state of the identity merge result is determined based on the difference between the two.

[0173] When the stable identity merging result does not point to an existing ancestral hall cultural gene instance, a proposed new ancestral hall cultural gene instance is formed. The carrier role structure signature is generated by aggregating the corresponding source evidence records, and existing ancestral hall cultural gene instances outside the initial candidate instance set are retrieved accordingly.

[0174] Finally, existing ancestral hall cultural gene instances that meet the duplicate creation conflict conditions are added to the expanded candidate set, and the identity merging result is regenerated. When the regenerated identity merging result points to an existing ancestral hall cultural gene instance, an identity association is established. When it does not point to an existing ancestral hall cultural gene instance and there is no duplicate creation conflict, a new ancestral hall cultural gene instance and its corresponding identity association are established.

[0175] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A database management system for ancestral hall architectural cultural genes, characterized in that, include: The source access module is used to receive multi-source ancestral hall architectural cultural gene data and generate source evidence records; The identity resolution module is used to receive the source evidence records and resolve the ancestral hall's main entity identifier, cultural gene type, cultural semantic proposition, architectural carrier role path, carrier relationship, and cultural expression role. The structural signature module is used to receive the architectural carrier role path, carrier relationship and cultural expression role and generate carrier role structural signature; The candidate merging module is used to receive the ancestral hall main entity identifier, cultural gene type, cultural semantic proposition, carrier role structure signature and existing ancestral hall cultural gene instance and generate the identity merging result of the source evidence record and the existing ancestral hall cultural gene instance; The reverse retrieval module is used to receive the identity merging result and the carrier role structure signature. When the identity merging result indicates the formation of a proposed new ancestral hall cultural gene instance, it retrieves existing ancestral hall cultural gene instances outside the candidate range determined by the candidate merging module based on the carrier role structure signature and generates an extended candidate set. The write management module is used to receive the expanded candidate set and the identity merging result, update the identity merging result according to the expanded candidate set, establish identity associations according to the updated identity merging result, and establish new ancestral hall culture gene instances when the updated identity merging result does not point to an existing ancestral hall culture gene instance.

2. The ancestral hall architectural cultural gene database management system according to claim 1, characterized in that: The source access module includes: The data receiving unit is used to receive the multi-source ancestral hall architectural cultural gene data and read the data source identifier, original content and data location; A fingerprint generation unit is used to generate an original data fingerprint based on the data source identifier, original content, and data location. The duplicate import verification unit is used to compare the original data fingerprint with the existing original data fingerprint and generate a duplicate import flag. The evidence record generation unit is used to write data that is not marked as a duplicate import into the source evidence record.

3. The ancestral hall architectural cultural gene database management system according to claim 1, characterized in that: The identity resolution module includes: The ancestral hall main entity parsing unit is used to determine the ancestral hall main entity identifier based on the ancestral hall identity data in the source evidence record; A type mapping unit is used to determine the cultural gene type based on the cultural semantic description and cultural gene type ontology in the source evidence record; A semantic proposition generation unit is used to convert the cultural semantic descriptions in the source evidence records into cultural semantic propositions. The carrier role parsing unit is used to generate architectural carrier role paths, carrier relationships, and cultural expression roles based on the architectural object hierarchy and cultural expression relationships in the source evidence record.

4. The ancestral hall architectural cultural gene database management system according to claim 1, characterized in that: The structure signature module includes: The path normalization unit is used to normalize the roles and sort the paths of the building carrier roles. A relation normalization unit is used to unify the relation type and relation direction of the carrier relations. The structural signature generation unit is used to generate structural signatures for carrier roles based on the normalized architectural carrier role paths, carrier relationships, and cultural expression roles.

5. The ancestral hall architectural cultural gene database management system according to claim 1, characterized in that: The candidate merging module includes: The initial candidate generation unit is used to generate an initial candidate instance set based on the ancestral hall main entity identifier, cultural gene type, and cultural semantic proposition. A group-level evidence generation unit is used to generate group-level matching data based on the cultural semantic proposition and the carrier role structure signature. The merge constraint generation unit is used to generate merge constraint data based on the main entity identifier of the ancestral hall, the relationship of cultural gene type, and the contradictory state of cultural semantics. The global merging unit is used to generate a preferred merging result and a candidate merging result based on the initial candidate instance set, group-level matching data and merging constraint data, and to generate an identity merging result based on the preferred merging result.

6. The ancestral hall architectural cultural gene database management system according to claim 5, characterized in that: The candidate merging module further includes: The source lineage processing unit is used to generate source lineage data and source independence data based on the derivation relationship between the source evidence records, and to update the group-level matching data based on the source independence data; A stability gating unit is used to generate stable merge data based on the preferred merge result and the alternative merge result, and to generate a merge release flag for the identity merge result when the stable merge data meets the stability condition, and to generate a merge delay flag for the identity merge result when the stable merge data does not meet the stability condition.

7. A database management system for ancestral hall architectural culture genes according to claim 6, characterized in that: The reverse retrieval module includes: A new marker unit is proposed to be used to determine, from the identity merging results with the merging and release marker, the proposed new ancestral hall cultural gene instance that does not point to an existing ancestral hall cultural gene instance. The structural aggregation unit is used to generate an aggregated carrier role structural signature based on the carrier role structural signature corresponding to the cultural gene instance of the proposed new ancestral hall. The reverse retrieval unit is used to retrieve existing ancestral hall culture gene instances outside the initial candidate instance set based on the aggregated carrier role structure signature. The candidate extension unit is used to generate a duplicate creation conflict and write the existing ancestral hall cultural gene instance into the extension candidate set when the proposed new ancestral hall cultural gene instance has the same ancestral hall main entity identifier, compatible cultural gene type and matching carrier role structure signature as the retrieved existing ancestral hall cultural gene instance.

8. The ancestral hall architectural cultural gene database management system according to claim 7, characterized in that: The write management module includes: The merge update unit is used to trigger the candidate merge module to regenerate the identity merge result and the merge release flag or merge postponement flag corresponding to the regenerated identity merge result based on the expanded candidate set. The locked resource generation unit is used to generate locked resources based on the main entity identifier of the ancestral hall, the cultural gene type, the architectural carrier role path, and the extended candidate set. The transaction review unit is used to re-perform candidate retrieval and duplicate creation conflict identification after obtaining the exclusive lock on the locked resource.

9. A database management system for ancestral hall architectural culture genes according to claim 8, characterized in that: The write management module also includes: An identity association unit is used to establish an identity association between the source evidence record and the existing ancestral hall cultural gene instance when the regenerated identity merging result has the merging release mark and points to the existing ancestral hall cultural gene instance. The instance establishment unit is used to establish a new ancestral hall culture gene instance when the regenerated identity merging result has the merging release mark, does not point to an existing ancestral hall culture gene instance, and does not have a duplicate creation conflict, and to establish the identity association between the source evidence record and the new ancestral hall culture gene instance. The alias update unit is used to write the original cultural gene name in the source evidence record into the alias data of the associated ancestral hall cultural gene instance.

10. A database management system for ancestral hall architectural culture genes according to claim 1, characterized in that: It also includes a storage module, which comprises: The cultural gene type storage unit is used to store cultural gene type entities and their type relationship data; The Ancestral Hall Cultural Gene Instance Storage Unit is used to store ancestral hall cultural gene instances and their instance main identifiers. A source evidence storage unit is used to store the source evidence records and their original data locations; An identity association storage unit is used to store identity association data between the source evidence record and the ancestral hall cultural gene instance.

Images