Multi-warehouse model design review method, system and equipment, storage medium and product

Abstract

The invention discloses a data warehouse model design review method, system and device, a storage medium and a product, and relates to the technical field of data processing.The data warehouse model design review method comprises the steps that when a field review request sent by a client side is received, a target data warehouse field after normative self-inspection is obtained, the target data warehouse field is sent to a large model application, and the large model application sends the target data warehouse field to the client side; according to the method and the system, the large model application is used for outputting a corresponding preliminary review result, and the preliminary review result is sent to the client for review personnel to perform field review and storage, so that developers can directly view the field review result at the client. According to the method, the number of fields needing to be corrected is reduced through normative self-inspection before field review, review personnel are helped to quickly perform field review and review result storage through the preliminary review result of the large model application, and developers can directly view the corresponding review result. Therefore, the normativity of model design and the efficiency of model review can be improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, in particular to a data warehouse model design review method, system, device, storage medium and product. BACKGROUND

[0002] The data warehouse model is a framework for organizing, storing and managing data in the data warehouse. The current data warehouse model design review method is usually that the developer completes the preliminary design of the data warehouse model, and the reviewer reviews the designed data warehouse model to ensure the standardization of the data warehouse model design.

[0003] However, there are many specification clauses related to field Chinese name naming in the data warehouse model design specification, and the developer is difficult to completely follow the naming specification, resulting in low standardization of the data warehouse model design. Therefore, the reviewer needs to spend a lot of time on review task processing, and needs to communicate with the developer many times about review feedback, information synchronization and model delivery, resulting in low review efficiency. That is, the current data warehouse model design review method has the problems of low design standardization and low review efficiency. SUMMARY

[0004] The main purpose of the present application is to provide a data warehouse model design review method, system, device, storage medium and product, which aims to solve the technical problems of low design standardization and low review efficiency of the current data warehouse model design review method.

[0005] To achieve the above purpose, the present application provides a data warehouse model design review method applied to a field review middle station in a data warehouse model design review system, the data warehouse model design review system further comprising a client, the client and the local communication connection, and the method comprising:

[0006] When receiving the field review request sent by the client, the target data warehouse model stored in the data warehouse model design review system is acquired, wherein the field review request is sent to the local by the client in response to the field review request sending operation triggered by the developer;

[0007] The target data warehouse field in the target data warehouse model is extracted, wherein the target data warehouse field is obtained by modifying the initial data warehouse field in the target data warehouse model by the data warehouse model design review system in response to the field modification operation triggered by the developer before the client sends the field review request, and the field modification operation is determined by the developer based on a preset large model application;

[0008] The target data warehouse field is sent to the large model application for the large model application to preliminarily review the target data warehouse field and output the corresponding preliminary review result;

[0009] obtaining the preliminary review result, sending the preliminary review result to the client for display of the preliminary review result by the client, obtaining a corresponding final review result in response to a review result determination operation triggered by the reviewer, and saving the final review result in the client in response to a review result saving operation triggered by the reviewer for viewing of the final review result by the developer in the client.

[0010] In an embodiment, before the step of obtaining the target data warehouse model stored in the data warehouse model design review system when the field review request sent by the client is received, the method further comprises:

[0011] determining a target blank table in response to a blank table selection operation of a developer;

[0012] recording a self-check field corresponding to a field input operation of a developer in a target blank table to obtain a target field table, wherein the self-check field is a field in the initial data warehouse field;

[0013] sending the target self-check field in the target field table to the large model application for review of the self-check field by the large model application, and outputting a corresponding self-check field review result in response to a field self-check operation triggered by a developer;

[0014] obtaining the self-check field review result, and sending the field self-check review result to the client for modification of the self-check field by the developer based on the self-check field review result.

[0015] In an embodiment, before the step of determining a target blank table in response to a blank table selection operation of a developer, the method further comprises:

[0016] obtaining a corresponding large model prompt in response to a prompt word input operation of a user, wherein the large model prompt includes a preset field structure rule, a preset field attribute classification rule, and a preset field content restriction rule, the field structure rule includes a preset field element rule and a preset field element association rule, and the attribute classification rule includes a preset field end word rule;

[0017] sending the large model prompt to the large model application to optimize the large model application in response to a model optimization confirmation operation triggered by a user.

[0018] In an embodiment, after the steps of obtaining the preliminary review result and sending the preliminary review result to the client, the method further comprises:

[0019] In response to a model selection operation triggered by a user, a corresponding version of a to-be-exported data warehouse model is obtained, wherein the to-be-exported data warehouse model includes to-be-exported fields and to-be-exported review results, and the to-be-exported review results are final review results saved when the to-be-exported fields are reviewed;

[0020] In response to a record export operation triggered by a user, the to-be-exported fields and the to-be-exported review results are exported as field review documents, so that the user can perform model design specification revision and large model application optimization based on the field review documents.

[0021] To achieve the above-mentioned purpose, the present application also proposes a data warehouse model design review method applied to a client in a data warehouse model design review system, wherein the data warehouse model design review system also includes a field review front-end, a field review middle-end and a local communication connection, and the method includes:

[0022] In response to a field review request sending operation triggered by a developer, a field review request is sent to the field review middle-end, so that the field review middle-end obtains a target data warehouse model stored in the data warehouse model design review system, extracts a target data warehouse field in the target data warehouse model, sends the target data warehouse field to a large model application, so that the large model application performs preliminary review on the target data warehouse field, outputs a corresponding preliminary review result, the field review middle-end obtains the preliminary review result, and sends the preliminary review result to the local, wherein the target data warehouse field is obtained by the developer modifying an initial data warehouse field in the target data warehouse model based on a preset large model application before sending the field review request to the local;

[0023] The preliminary review result sent by the field review middle-end is received and displayed;

[0024] In response to a review result determination operation triggered by a reviewer, a corresponding final review result is obtained;

[0025] In response to a review result saving operation triggered by a reviewer, the final review result is saved in the local, so that the developer can view the final review result in the local.

[0026] In an embodiment, the step of obtaining the corresponding final review result in response to the review result determination operation triggered by the reviewer includes:

[0027] In response to a review option selection operation triggered by the reviewer, a first review result is determined, wherein the first review result includes a review state and a review suggestion;

[0028] In response to the review content input operation of the reviewer, the reviewer input content is determined as a second review result;

[0029] The final review result is obtained in combination with the first review result and the second review result.

[0030] In addition, to achieve the above-mentioned purpose, the present application also proposes a data warehouse model design review system, which comprises a client and a field review middle office, wherein the client and the field review middle office are communicatively connected;

[0031] The field review middle office is configured to, when receiving a field review request sent by the client, acquire a target data warehouse model stored in the data warehouse model design review system, extract a target data warehouse field in the target data warehouse model, send the target data warehouse field to a large model application, acquire a preliminary review result output by the large model application, and send the preliminary review result to the client, wherein the field review request is sent to the local by the client in response to a field review request sending operation triggered by a developer, the target data warehouse field is obtained by modifying an initial data warehouse field in the target data warehouse model by the data warehouse model design review system in response to a field modification operation triggered by a developer before the client sends the field review request, and the field modification operation is determined by the developer based on a preset large model application;

[0032] The client is configured to, in response to a field review request sending operation triggered by a developer, send a field review request to the field review middle office, receive a preliminary review result sent by the field review middle office, and display the preliminary review result, in response to a review result determination operation triggered by a reviewer, obtain a corresponding final review result, and in response to a review result saving operation triggered by a reviewer, save the final review result in the local.

[0033] In addition, to achieve the above-mentioned purpose, the present application also proposes a data warehouse model design review device, which comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the data warehouse model design review method as described above.

[0034] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer readable storage medium, and the storage medium stores a computer program, wherein the computer program is executed by a processor to implement the steps of the data warehouse model design review method as described above.

[0035] In addition, to achieve the above object, the present application also provides a computer program product, which comprises a computer program, and the computer program implements the steps of the data warehouse model design review method when executed by a processor.

[0036] The one or more technical solutions provided in the present application have at least the following technical effects:

[0037] When the field review request sent by the client is received, the target data warehouse model stored in the data warehouse model design review system is obtained, the target data warehouse field in the target data warehouse model is extracted, the target data warehouse field is sent to the large model application, the large model application performs preliminary review on the target data warehouse field, outputs the corresponding preliminary review result, obtains the preliminary review result, sends the preliminary review result to the client for the client to display the preliminary review result, obtains the corresponding final review result in response to the review result determination operation triggered by the reviewer, saves the final review result in the client in response to the review result saving operation triggered by the reviewer, and the developer can view the final review result on the client.

[0038] The present application uses a pre-set large model application, so that the developer can modify the initial data warehouse field based on the large model before initiating the field review request, reducing the number of fields that need to be modified subsequently, and improving the standardization of the data warehouse model. After receiving the field review request, the present application first obtains the preliminary field review result through the large model application, so that the developer can perform field review based on the preliminary field review result, without spending a lot of time on field review, thereby improving the review efficiency. By saving the review result made by the reviewer in the client, the developer can directly view the review result on the client and modify the field, so that the developer and the reviewer do not need to communicate repeatedly, further improving the standardization of the data warehouse model design and the review efficiency. Therefore, the present application can improve the standardization of the model design and the efficiency of the model review. BRIEF DESCRIPTION OF DRAWINGS

[0039] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments consistent with the present application and serve to explain the principles of the present application together with the specification.

[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, those skilled in the art can obtain other drawings from these drawings without creative labor.

[0041] Figure 1 A flowchart provided by the first embodiment of the method for reviewing a data warehouse model design of the application is shown in FIG. 1.

[0042] Figure 2 A first scenario diagram provided by the first embodiment of the method for reviewing a data warehouse model design of the application is shown in FIG. 2.

[0043] Figure 3 A second scenario diagram provided by the first embodiment of the method for reviewing a data warehouse model design of the application is shown in FIG. 3.

[0044] Figure 4 A third scenario diagram provided by the first embodiment of the method for reviewing a data warehouse model design of the application is shown in FIG. 4.

[0045] Figure 5 A flowchart provided by the second embodiment of the method for reviewing a data warehouse model design of the application is shown in FIG. 5.

[0046] Figure 6 A first scenario diagram provided by the second embodiment of the method for reviewing a data warehouse model design of the application is shown in FIG. 6.

[0047] Figure 7 A second scenario diagram provided by the second embodiment of the method for reviewing a data warehouse model design of the application is shown in FIG. 7.

[0048] Figure 8 A device structure diagram of a hardware running environment involved in the method for reviewing a data warehouse model design in the embodiments of the application is shown in FIG. 8.

[0049] The object, function features and advantages of the application will be further explained with reference to the embodiments and the accompanying drawings. DETAILED DESCRIPTION

[0050] It should be understood that the specific embodiments described herein are merely intended to explain the technical solutions of the application, and not to limit the application.

[0051] In order to better understand the technical solutions of the application, the following will be described in detail with reference to the accompanying drawings and specific embodiments.

[0052] It should be noted that the execution subject of the embodiments can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device, a data warehouse model design review device, etc. capable of realizing the above functions. The embodiments and the following embodiments will be described below taking the data warehouse model design review device as an example.

[0053] The data warehouse model is a framework for organizing, storing and managing data in a data warehouse. The current data warehouse model design and review process is usually as follows: the data warehouse developer completes the model design according to the data warehouse model design specification, the reviewer audits the rationality and standardization of the model according to the design specification and proposes optimization suggestions, the developer iteratively modifies the model according to the review opinions, and finally forms a landing model that meets the specification.

[0054] However, there are many specification clauses related to field Chinese name naming in the data warehouse model design specification, and the developers have difficulty in completely following the naming specification, resulting in low standardization of the data warehouse model design. Therefore, the reviewer needs to spend a lot of time on review task processing and communicate with the developer many times about review feedback, information synchronization and model delivery, resulting in low review efficiency. In addition, since there is no process archiving mechanism in the current model review link, it is difficult to trace the problem and the review experience is difficult to be deposited.

[0055] Based on this, the data warehouse model design review method provided by the embodiments of the present application is applied to the field review in the data warehouse model design review system, and the data warehouse model design review system further includes a client, the client and the local communication connection, referring to Figure 1 , Figure 1 The flowchart of the first embodiment of the data warehouse model design review method of the present application is shown.

[0056] In this embodiment, the data warehouse model design review method includes steps S10-S40:

[0057] Step S10, when receiving the field review request sent by the client, the target data warehouse model stored in the data warehouse model design review system is obtained, wherein the field review request is sent to the local by the client in response to the field review request sending operation triggered by the developer;

[0058] It should be noted that the field review request refers to the request signal initiated by the developer after completing the data warehouse model design to start the model field naming standardization check and review process. The client is a model review management page used by the developer and the reviewer. The data warehouse model design review system is a system for data warehouse model design, review and management, and further includes field-level and table-level responsible persons and theme management pages, field-level and table-level model mapping management pages, etc. The target data warehouse model is the data warehouse model that the developer currently wants to review.

[0059] It can be understood that in the current data warehouse model review, the developer and the reviewer need to communicate multiple times through email, telephone or offline meeting, the communication efficiency is low, and the model submission process is not unified. Different projects and teams may use different ways to submit the model, resulting in low efficiency of model review.

[0060] Therefore, the embodiment establishes the data warehouse model design review system, changes the original offline model review process to online, and improves the communication efficiency. The embodiment unifies the design and submission method of the model to the data warehouse model design review system, preventing the reduction of review efficiency caused by different model submission methods. When model review is needed, the developer only needs to initiate a review request on the client side, and the field review middle platform will automatically obtain the target data warehouse model stored in the data warehouse model design review system, thereby reducing the time for obtaining the model in the model review process and improving the efficiency of model review. The architecture of the data warehouse model design review process in the embodiment can refer to Figure 2 .

[0061] In step S20, a target data warehouse field in the target data warehouse model is extracted, wherein the target data warehouse field is obtained by modifying an initial data warehouse field in the target data warehouse model in response to a field modification operation triggered by the developer before the client sends the field review request, and the field modification operation is determined by the developer based on a preset large model application;

[0062] It should be noted that the target data warehouse field is the field of the data warehouse model to be reviewed after being modified by the developer, and the initial data warehouse field is the data warehouse field of the model after being designed by the developer without modification by the large model application. The field modification operation is an operation of modifying the data warehouse field according to the suggestion generated by the large model application. The preset large model application is a large language model, which is used to understand the field semantics and judge the naming specification, locate the field problem and generate the corresponding improvement suggestion in the embodiment.

[0063] It can be understood that in the current model design specification, there are many specification clauses related to the naming of Chinese field names, and it is difficult for the developer to completely follow the naming specification. Therefore, the data warehouse model preliminarily completed by the developer will have a large number of non-standard fields, resulting in low specification of the model. Non-standard model fields need to be reviewed by the reviewer, and when there are many non-standard fields to be reviewed, the reviewer needs to review a large number of fields, thereby reducing the efficiency of model review.

[0064] Therefore, the embodiment can help the development to perform self-inspection on the model fields in the data warehouse by the preset large model application, so that the developer can determine the fields to be modified in the model by the large model application before initiating a review request for the model fields, and perform preliminary modification on the model fields. The model that passes the preliminary modification has a large number of non-standard fields reduced, and in the subsequent model field review process, the reviewer only needs to review a small number of error fields after modification, thereby reducing the time spent by the reviewer and improving the efficiency of model review.

[0065] In an embodiment, the target data warehouse field includes a field level, a field element, and a field type, and the field level includes a table-level field and an intra-table field. The embodiment further performs hierarchical and classified extraction of the field according to the field level, the field element, and the field type when extracting the field, so that the developer and the reviewer can quickly review only the fields that need to be reviewed without reviewing all the fields or manually screening the fields that need to be reviewed, thereby improving the freedom and efficiency of field review.

[0066] Specifically, if the developer only needs to review the table-level fields, the extracted table-level fields can be directly selected by one key, and the selected table-level fields are sent to the large model application for preliminary review of the fields.

[0067] In an embodiment, the specific implementation of hierarchical and classified extraction of the field according to the field level, the field element, and the field type can also be: determining the level of the field based on the naming format of the field, determining the field element of the field based on the element information in the field structure, determining the field type based on the end word type in the field structure, and extracting the field based on the field level, the field element, and the field type.

[0068] In a feasible implementation, when the field review request sent by the client is received, the specific implementation of the target data warehouse model before the data warehouse model design review system can also be:

[0069] In response to a blank table selection operation of the developer, a target blank table is determined, in response to a field input operation of the developer, a self-check field corresponding to the field input operation is recorded in the target blank table to obtain a target field table, wherein the self-check field is a field in the initial data warehouse field, in response to a field self-check operation triggered by the developer, the target self-check field in the target field table is sent to the large model application, so that the large model application reviews the self-check field, and outputs a corresponding self-check field review result, the self-check field review result is obtained, and the field self-check review result is sent to the client, so that the developer modifies the self-check field based on the self-check field review result.

[0070] It should be noted that the blank table is a template table without filled fields, the self-check field is a field input by the developer that needs to be checked for specification, and the target field table is a table filled with fields that need to be checked for specification.

[0071] It can be understood that, in order to reduce the fields with specification problems, reduce the time that the reviewer needs to review, and improve the efficiency of the review, it is necessary to perform a self-check of the field based on the large model application before starting the field review operation. Since there are many fields that need to be checked, if each field is input into the large model application for self-check, the self-check efficiency will be low. Therefore, the blank table of the field review middle platform records the fields that need to be reviewed by the developer. After the developer inputs the fields, the fields in the target field table are input into the large model application, and the field review results output by the large model application are also aggregated and displayed by the field review middle platform. The developer can view the corresponding field review results in the field review middle platform, and perform preliminary modification of the fields based on the field review results.

[0072] Therefore, by recording and sending the fields of the blank table, the fields that need to be self-checked can be quickly self-checked by the large language application, and the efficiency of the field self-check is improved. By aggregating and displaying the field review results output by the large model application in the field review middle platform, the developer can quickly view the fields and their review results, and further improve the efficiency of the field self-check of the developer.

[0073] In a feasible implementation manner, before the target blank table is determined in response to the blank table selection operation of the developer, the specific implementation manner can also be:

[0074] In response to the user's prompt word input operation, a corresponding large model prompt word is obtained, wherein the large model prompt word includes a preset field structure rule, a preset field attribute classification rule, and a preset field content restriction rule, the field structure rule includes a preset field element rule and a preset field element association rule, and the attribute classification rule includes a preset field end word rule. In response to a model optimization confirmation operation triggered by the user, the large model prompt word is sent to the large model application to optimize the large model application.

[0075] It should be noted that the large model prompt word is an instructive text for guiding the large model application to output a result that meets the business requirements, and includes a field structure rule, a field attribute classification rule, and a field content restriction rule.

[0076] The field structure rule represents the elements that the field needs to include and the composition logic between the elements, and in this embodiment includes a field element rule and a field element association rule. The field element rule specifically refers to the naming of the field Chinese name satisfying the "modifier + subject + attribute classification end word" three-element form and the specific meanings of the three elements in this embodiment, and the field element association rule specifically refers to the relationship between the three elements.

[0077] The field attribute classification rule refers to the end word of the field in this embodiment, and the field content restriction rule refers to rules such as not being all English letters, not containing special characters, bracket usage specifications, and suggestions for regular use of "code" and "logo".

[0078] It can be understood that there are many field naming rules in the data warehouse model design specification, and using original descriptions will affect the focusing ability of the large model on key information and reduce the understanding effect of the model on the context, thereby affecting the field review result of the large model application and reducing the design specification of the data warehouse model. Therefore, the rules in the data warehouse model design specification need to be reorganized, and the key rules and error-prone rules summarized in combination with expert review requirements during core data warehouse reconstruction are input into the model to improve the accuracy of the model in field review.

[0079] Specifically, there are 15 categories and 74 types of end words in the attribute classification specification, and the original definition and case description are not easy to understand in the large model. Therefore, in this embodiment, the 74 types are summarized into an end word list in the prompt word, and a "strictly follow" prompt convention is developed to enable the large model to accurately identify the task and strictly follow the rules.

[0080] The embodiment summarizes the reviewed requirements through the above steps, takes the field structure rule, the preset field attribute classification rule and the preset field content restriction rule as prompt words, inputs them into the large model application, optimizes the model, and enables the large model application to strictly review according to the above rules when performing field review, thereby improving the accuracy of the large model application field review, and further improving the standardization of the designed data warehouse model.

[0081] The embodiment further performs binary classification experiment effect evaluation according to whether it conforms to the specification, takes non-conformance to the specification as a positive class, obtains a recall rate of 95% in the experimental result, that is, 95% of the non-standard fields can be accurately identified, and the recall rate refers to the proportion of samples that are actually positive classes and are correctly predicted as positive classes by the model.

[0082] In step S30, the target data warehouse field is sent to the large model application for the large model application to perform preliminary review on the target data warehouse field, and output corresponding preliminary review results.

[0083] It should be noted that the preliminary review is an operation of reviewing the model field by the optimized large model application before the review personnel review the data warehouse field.

[0084] It can be understood that in the current model review method, the review personnel need to view the field naming one by one, and review the data warehouse model field based on the review design specification, so that the review personnel need to spend a lot of time for review each time, resulting in low review efficiency. However, in most field review processes, the reason for the non-standard model field is common, so that the review personnel has unnecessary repetitive work when reviewing the field.

[0085] Before the review personnel performs field review, the embodiment first performs preliminary review on the model field by the large model application, and points out the common model field errors in the preliminary review. Since the field to be reviewed in the embodiment is a field that has been self-checked by the developer, the non-standard fields that need to be corrected are relatively few, and the preliminary review by the large model application can point out the common field non-standard problems, so that the review personnel can only handle a small part of the field review. Therefore, the embodiment combines the self-checking of the model field and the preliminary review of the model field, and further improves the efficiency of the model field review.

[0086] In an embodiment, the large model application further includes a plurality of large model sub-applications for reviewing fields of different categories, and the large model application identifies the field level, field element, and field type of the target data warehouse field when performing the preliminary review of the target data warehouse field; determines the field category of the field that needs to be identified based on the identified field level, field element, and field type; determines the target large model sub-application for field review based on the field category, and reviews the field through the target large model sub-application, wherein the field category of the field that needs to be identified includes an error-prone field, a high-usage field, a low-usage field, and a financial field, and the target large model sub-application is trained based on the target field category.

[0087] Since the target large model sub-application is trained based on the target field category, the corresponding category of the field is reviewed through the target large model sub-application, which can further improve the accuracy of the preliminary review of the field, thereby reducing the time spent by the reviewer, improving the review efficiency, and improving the standardization of the modified field through more accurate preliminary review results, thereby improving the standardization of the data warehouse model design.

[0088] In step S40, the preliminary review result is obtained, the preliminary review result is sent to the client for the client to display the preliminary review result, the corresponding final review result is obtained in response to the review result determination operation triggered by the reviewer, and the final review result is saved in the client in response to the review result saving operation triggered by the reviewer, so that the developer can view the final review result in the client.

[0089] It should be noted that the review result determination operation is an operation of determining the final review result by the reviewer based on the output result of the large model application. The review result saving operation is an operation of the reviewer clicking a save button in the client to save the corresponding final review result in the client.

[0090] It can be understood that the current field review needs the developer and the reviewer to communicate repeatedly offline multiple times, and the offline communication needs the developer and the reviewer to spend corresponding time, resulting in high communication cost, affecting the efficiency of the data warehouse model field review, and further affecting the efficiency and standardization of the data warehouse model design.

[0091] Therefore, the preliminary review result is obtained, and the preliminary review result is sent to the client, so that the reviewer can determine a final review result on the client, and the final review result is saved on the client. In this embodiment, the developer and the reviewer can both view the content of the client, and the viewed content is the same. Therefore, by saving the final review result, the developer can view the saved final review result at any time, without the developer and the reviewer spending a lot of time on offline communication, thereby improving the efficiency of model field review, and further improving the standardization and efficiency of model design.

[0092] In a feasible implementation, the specific implementation of obtaining the preliminary review result and sending the preliminary review result to the client can also be:

[0093] In response to a model selection operation triggered by a user, a corresponding version of a to-be-exported data warehouse model is obtained, wherein the to-be-exported data warehouse model includes to-be-exported fields and to-be-exported review results, the to-be-exported review results are final review results saved when the to-be-exported fields are reviewed, and in response to a record export operation triggered by a user, the to-be-exported fields and the to-be-exported review results are exported as a field review document, so that the user performs model design specification revision and large model application optimization based on the field review document.

[0094] It should be noted that the model selection operation is an operation of selecting a corresponding version of a data warehouse model by a user through an interface. The to-be-exported data warehouse model is a data warehouse model selected for export, and includes corresponding fields and field review results. The to-be-exported fields are a set of specific fields in the data warehouse model that need to be exported.

[0095] It can be understood that in the current data warehouse model design and review method, different versions of models and corresponding field review results are not saved, which causes difficulty in problem tracing and makes it difficult to accumulate review experience. Therefore, the embodiment realizes recording and saving of models and field review results through the data warehouse model design and review system, so as to facilitate history tracing and experience summary.

[0096] In this embodiment, the design, modification and review of the data warehouse model are all performed in the data warehouse model design and review system. Therefore, the embodiment can automatically save different versions of models and corresponding field review records, and export them as documents when needed, thereby tracing historical versions and providing data support for review experience accumulation. The interface for field viewing and exporting in the field review middle platform is shown in FIG. 8, and a specific field viewing interface is shown in FIG. 9. Figure 3 Figure 4

[0097] ​​And since the design, modification and review of the data warehouse model are all carried out in the data warehouse model design review system, the embodiment can quickly determine the required data warehouse model in the corresponding page of the data warehouse model design review system, and can quickly select the part to be exported, thereby realizing the quick and accurate export of the data warehouse model document. The exported document includes the fields and review records of the corresponding model, so the embodiment can also use the above-mentioned document for optimization of large model application, further improving the accuracy of field review by large model application.

[0098] In summary, when the field review request sent by the client is received, the target data warehouse model stored in the data warehouse model design review system is obtained, the target data warehouse field in the target data warehouse model is extracted, the target data warehouse field is sent to the large model application for preliminary review of the target data warehouse field by the large model application, and the corresponding preliminary review result is output. The preliminary review result is obtained, and the preliminary review result is sent to the client for display of the preliminary review result by the client. In response to the review result determination operation triggered by the reviewer, the corresponding final review result is obtained, and in response to the review result saving operation triggered by the reviewer, the final review result is saved in the client for the developer to view the final review result in the client.

[0099] The embodiment makes the developer can modify the initial data warehouse field based on the large model before initiating the field review request, reduces the number of fields that need to be modified subsequently, and improves the standardization of the data warehouse model. After receiving the field review request, the embodiment first obtains the preliminary field review result through the large model application, so that the developer can perform field review based on the preliminary field review result without spending a lot of time on field review, thereby improving the efficiency of the review. By saving the review result made by the reviewer in the client, the developer can directly view the review result in the client and modify the field, so that the developer and the reviewer do not need to communicate repeatedly, further improving the standardization of the data warehouse model design and the efficiency of the review. Therefore, the embodiment can improve the standardization of the model design and the efficiency of the model review.

[0100] Based on this, the embodiment of the present application also provides a data warehouse model design review method applied to a client in a data warehouse model design review system, wherein the data warehouse model design review system further includes a field review front-end, a field review middle-end and a local communication connection, and the field review front-end is connected to the field review middle-end through the local communication connection. Figure 5 , Figure 5 The flowchart of the second embodiment of the data warehouse model design review method of the present application.

[0101] In the embodiment, the data warehouse model design review method comprises steps A10-A40.

[0102] In step A10, in response to a field review request sent by a developer, a field review request is sent to the field review middle platform to obtain a target data warehouse model stored in the data warehouse model design review system, extract a target data warehouse field in the target data warehouse model, send the target data warehouse field to a large model application for preliminary review of the target data warehouse field by the large model application, and output a corresponding preliminary review result. The field review middle platform obtains the preliminary review result and sends the preliminary review result to a local terminal. The target data warehouse field is obtained by the developer based on a preset large model application and modified from an initial data warehouse field in the target data warehouse model before the field review request is sent to the local terminal.

[0103] It can be understood that in the current data warehouse model design review method, when a model field review is needed, the developer needs to contact the reviewer through offline contact. If the reviewer cannot review temporarily, the developer needs to contact the reviewer again, which results in low efficiency of model review. Therefore, the embodiment performs field review online through the data warehouse model design review system.

[0104] The data warehouse model design review system enables the developer to directly initiate a field review request on the client terminal after self-inspection of the field. The initiated field review request is sent to the field review middle platform to call the large model application for preliminary review and synchronize the preliminary review result of the field review middle platform, so that the reviewer can quickly process the field review task. In the above steps of the embodiment, the developer only needs to send a field review request when the review is needed, without the need to contact the reviewer or contact the reviewer again when the reviewer cannot review temporarily, thereby improving the efficiency of field review.

[0105] In step A20, the preliminary review result sent by the field review middle platform is received and displayed.

[0106] It should be noted that the preliminary review result is a result obtained by preliminary review of all fields.

[0107] It can be understood that after the developer initiates the field review request, the field review middle platform calls the large model application for preliminary review, and the reviewer needs to perform final field review based on the preliminary review result. Therefore, the embodiment receives the preliminary review result sent by the field review middle platform and displays the preliminary review result, so that the reviewer can view the preliminary review result and perform final review based on the preliminary review result, thereby improving the review efficiency.

[0108] Step A30, in response to the review result determination operation triggered by the reviewer, obtaining the corresponding final review result;

[0109] It should be noted that the review result determination operation is an operation in which the reviewer selects the preset review state and review suggestion and supplements additional review opinions.

[0110] In a feasible implementation, the specific implementation of the operation of obtaining the corresponding final review result in response to the review result determination operation triggered by the reviewer can also be:

[0111] In response to the review option selection operation triggered by the reviewer, a first review result is determined, wherein the first review result includes a review state and a review suggestion, in response to the review content input operation of the reviewer, the content input by the reviewer is determined as a second review result, and the final review result is obtained by combining the first review result and the second review result.

[0112] It should be noted that the review option selection operation is an operation in which the reviewer clicks a drop-down menu, selects a review state, and clicks a preset review suggestion label on a client interface, the first review result is a review result determined by the reviewer after the above operation, the second review result is a review result obtained by the reviewer inputting additional review suggestions, and the interface for the reviewer to perform review is as shown in Figure 6 .

[0113] It can be understood that most of the field non-standard problems are common problems, and the current review method requires the reviewer to manually write or input the review result, which causes the reviewer to spend a lot of time on repeated common field problem review. Therefore, the present embodiment provides the preset review state option and the review suggestion label, so that the reviewer can directly select the corresponding state and label, thereby eliminating the need for repeated manual input, improving the efficiency of the review, and increasing the readability of the review opinions by using standardized review labels, improving the accuracy of the developer's modification, and thus improving the standardization of the review.

[0114] For uncommon field standardization problems, the present embodiment provides an input interface for additional review opinions, so that the reviewer can manually input additional review opinions, thereby achieving review of uncommon field problems and improving the accuracy of field review.

[0115] Step A40, in response to the review result saving operation triggered by the reviewer, saving the final review result locally for the developer to view the final review result locally.

[0116] It should be noted that the operation of the developer locally viewing the final review result means that the developer can directly view the review opinion saved by the reviewer on the client side.

[0117] It can be understood that in the current review method, the reviewer needs to contact the developer again after reviewing the field to inform the developer of the review opinion, thereby causing repeated contact and communication between the developer and the reviewer. The field saving operation of the reviewer in the embodiment enables the final review result to be saved in the client side, so that the developer can directly view the review result on the client side, thereby improving the efficiency of review opinion feedback and field modification by the developer. The interface for the developer and the reviewer to view the field in the client side is as shown in Figure 7

[0118] In summary, the embodiment responds to the field review request sending operation triggered by the developer to send the field review request to the field review middle platform, receives the preliminary review result sent by the field review middle platform, and displays the preliminary review result. In response to the review result determination operation triggered by the reviewer, the corresponding final review result is obtained. In response to the review result saving operation triggered by the reviewer, the final review result is saved locally for the developer to locally view the final review result.

[0119] In view of the problem that the current data warehouse model field design review system needs frequent communication between the developer and the reviewer, and the reviewer needs to spend a lot of time on field review. The review state option and the review suggestion label in the embodiment enable the reviewer to quickly review common field problems, thereby improving the review efficiency. By saving the final review opinion locally, the developer can directly view the review opinion on the client side without additional repeated communication with the reviewer, thereby improving the efficiency of data warehouse model field modification. Therefore, the embodiment can improve the efficiency of data warehouse model field review and modification.

[0120] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the data warehouse model design review method of the present application. More simple transformations based on this technical concept are within the protection scope of the present application.

[0121] The present application provides a data warehouse model design review device, which comprises at least one processor and a memory in communication connection with the at least one processor. The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the data warehouse model design review method in Embodiment I.

[0122] The following will be described with reference to​ Figure 8 , which shows a schematic diagram of the structure of a data warehouse model design and review device suitable for implementing the embodiments of the present application. The data warehouse model design and review device in the embodiments of the present application may include, but is not limited to, mobile terminals such as mobile phones, tablet computers, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PMPs (Portable Media Players), in-vehicle terminals (such as in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 8 The data warehouse model design review device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0123] like Figure 8 As shown, the data warehouse model design and review device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. Various programs and data required for the operation of the data warehouse model design and review device are also stored in RAM 1004. The processing device 1001, ROM 1002, and RAM 1004 are connected to each other via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 1003 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 1009. The communication device 1009 can allow the data warehouse model design review device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a data warehouse model design review device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have instead.

[0124] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer readable medium, the computer program containing program codes for executing the method shown in the flowchart. In such embodiments, the computer program can be downloaded and installed from a network through a communication device, or installed from the storage device 1003, or installed from the ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiments disclosed in the present application are executed.

[0125] The data warehouse model design review device provided by the present application adopts the data warehouse model design review method in the above-mentioned embodiments, and can solve the technical problems of low design specification and low review efficiency of the current data warehouse model design review method. Compared with the prior art, the data warehouse model design review device provided by the present application has the same beneficial effects as the data warehouse model design review method provided by the above-mentioned embodiments, and other technical features in the data warehouse model design review device are the same as the features disclosed in the previous embodiment method, which will not be repeated here.

[0126] It should be understood that parts of the present application can be realized by hardware, software, firmware or a combination thereof. In the description of the above-mentioned embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0127] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

[0128] The present application provides a computer readable storage medium having stored thereon computer readable program instructions (i.e. computer program) for executing the data warehouse model design review method in the above-mentioned embodiments.

[0129] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0130] The above-mentioned computer-readable storage medium may be included in the data warehouse model design and review device; or it may exist independently without being assembled into the data warehouse model design and review device.

[0131] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the data warehouse model design and review device, the data warehouse model design and review device executes the data warehouse model design and review method.

[0132] Computer program code for performing the operations of the present application may be written in one or more programming languages, or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0133] The flow diagrams and the block diagrams in the drawings are illustrations of architectures, functionalities, and operations of possible implementations of systems, methods, and computer program products according to various embodiments of present application. In this regard, each block in the flow diagrams or block diagrams can represent a module, a segment, or a portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and / or flow diagrams, and combinations thereof, can be implemented by special purpose hardware-based systems that perform the specified functions or operations, or combinations of special purpose hardware and computer instructions.

[0134] The modules involved in the embodiments of the present application can be implemented in the form of software or in the form of hardware. In some cases, the name of the module does not constitute a limitation on the module itself.

[0135] The readable storage medium provided by the present application is a computer readable storage medium, which stores computer readable program instructions (i.e. computer program) for executing the above-mentioned data warehouse model design review method, and can solve the technical problems of low design specification and low review efficiency of the current data warehouse model design review method. Compared with the prior art, the computer readable storage medium provided by the present application has the same beneficial effects as the data warehouse model design review method provided by the above-mentioned embodiments, and will not be described here.

[0136] The present application also provides a computer program product, comprising a computer program, which, when executed by a processor, implements the steps of the data warehouse model design review method as described above.

[0137] The computer program product provided by the present application can solve the technical problems of low design specification and low review efficiency of the current data warehouse model design review method. Compared with the prior art, the computer program product provided by the present application has the same beneficial effects as the data warehouse model design review method provided by the above-mentioned embodiments, and will not be described here.

[0138] The user-related data (for example, user attribute data, user behavior data, and user geographic location, etc., which can be modified according to the scheme content) involved in the present application are obtained after obtaining the permission or consent of the user; that is, when the present application is applied to a specific product or technology, the permission of the user needs to be obtained to realize the acquisition and processing of the related data, and the processing of the related data needs to comply with the relevant laws, regulations and supervision standards of the country and region.

[0139] The above only describes some embodiments of the present application, and does not limit the patent scope of the present application. Any equivalent structural transformation made by using the content of the present application specification and drawings, or direct / indirect application in other related technical fields is included in the patent protection scope of the present application.

Claims

1. A data warehouse model design review method, characterized in that: A field review platform is applied to a data warehouse model design and review system, wherein the data warehouse model design and review system further includes a client, and the client is connected to a local communication. The method includes: When receiving a field review request sent by the client, obtaining a target data warehouse model stored in the data warehouse model design review system, wherein the field review request is sent locally by the client in response to a field review request sending operation triggered by a developer; Extracting a target data warehouse field from the target data warehouse model, wherein the target data warehouse field is obtained by modifying an initial data warehouse field in the target data warehouse model by the data warehouse model design review system in response to a field modification operation triggered by a developer before the client sends the field review request, wherein the field modification operation is determined by the developer based on a preset large model application; Sending the target data warehouse field to the large model application, so that the large model application performs a preliminary review of the target data warehouse field and outputs a corresponding preliminary review result; Obtain the preliminary review result, send the preliminary review result to the client so that the client can display the preliminary review result, obtain the corresponding final review result in response to the review result confirmation operation triggered by the reviewer, and save the final review result in response to the review result save operation triggered by the reviewer, so that the developer can view the final review result on the client.

2. The method according to claim 1, wherein Before the step of obtaining the target data warehouse model stored in the data warehouse model design and review system upon receiving the field review request sent by the client, the method further includes: In response to a blank table selection operation by a developer, determining a target blank table; In response to a field input operation by a developer, a self-check field corresponding to the field input operation is recorded in the target blank table to obtain a target field table, wherein the self-check field is a field in the initial data warehouse field; In response to a field self-check operation triggered by a developer, the target self-check field in the target field table is sent to the large model application, so that the large model application reviews the self-check field and outputs a corresponding self-check field review result; The self-check field review result is obtained, and the field self-check review result is sent to the client, so that the developer can modify the self-check field based on the self-check field review result.

3. The method according to claim 2, wherein Before the step of determining the target blank table in response to the developer's blank table selection operation, the method further includes: In response to a user's prompt word input operation, a corresponding large model prompt word is obtained, wherein the large model prompt word includes a preset field structure rule, a preset field attribute classification rule, and a preset field content restriction rule, the field structure rule includes a preset field element rule and a preset field element association rule, and the attribute classification rule includes a preset field ending word rule; In response to a model tuning confirmation operation triggered by a user, the large model prompt word is sent to the large model application to tune the large model application.

4. The method according to claim 1, wherein: After the step of obtaining the preliminary review result and sending the preliminary review result to the client, the method further includes: In response to a model selection operation triggered by a user, a corresponding version of a data warehouse model to be exported is obtained, wherein the data warehouse model to be exported includes fields to be exported and review results to be exported, and the review results to be exported are the final review results saved when reviewing the fields to be exported; In response to a record export operation triggered by a user, the fields to be exported and the review results to be exported are exported as a field review document, so that the user can revise the model design specifications and optimize the large model application based on the field review document.

5. A data warehouse model design review method, characterized in that: The method is applied to a client in a data warehouse model design and review system, wherein the data warehouse model design and review system further includes a field review front end, the field review middle end and a local communication connection, and the method includes: In response to a field review request sending operation triggered by a developer, the field review request is sent to the field review center, so that the field review center obtains the target data warehouse model stored in the data warehouse model design review system, extracts the target data warehouse field in the target data warehouse model, and sends the target data warehouse field to the big model application, so that the big model application performs a preliminary review on the target data warehouse field and outputs a corresponding preliminary review result. The field review center obtains the preliminary review result and sends the preliminary review result to the local. The target data warehouse field is obtained by the developer modifying the initial data warehouse field in the target data warehouse model based on the preset big model application before sending the field review request locally. Receive the preliminary review results sent by the field review center and display the preliminary review results; In response to the review result determination operation triggered by the reviewer, the corresponding final review result is obtained; In response to the review result saving operation triggered by the reviewer, the final review result is saved locally, so that the developer can view the final review result locally.

6. The method according to claim 5, wherein The step of obtaining the corresponding final review result in response to the review result determination operation triggered by the reviewer includes: In response to a review option selection operation triggered by the reviewer, determining a first review result, wherein the first field review result includes a review status and a review suggestion; In response to the reviewer's review content input operation, determining the content input by the reviewer as a second review result; The final review result is obtained by combining the first review result and the second review result.

7. A data warehouse model design review system, characterized by: The system includes: a client and a field review center, wherein the client and the field review center are in communication connection; A field review center is configured to, upon receiving a field review request sent by the client, obtain a target data warehouse model stored in the data warehouse model design and review system, extract target data warehouse fields from the target data warehouse model, send the target data warehouse fields to the large model application, obtain a preliminary review result output by the large model application, and send the preliminary review result to the client, wherein the field review request is sent locally by the client in response to a field review request sending operation triggered by a developer, and the target data warehouse fields are obtained by modifying the initial data warehouse fields in the target data warehouse model by the data warehouse model design and review system in response to a field modification operation triggered by a developer before the client sends the field review request, and the field modification operation is determined by the developer based on a preset large model application; The client is used to respond to the field review request sending operation triggered by the developer, send the field review request to the field review center, receive the preliminary review results sent by the field review center, and display the preliminary review results, respond to the review result determination operation triggered by the reviewer, obtain the corresponding final review result, and respond to the review result saving operation triggered by the reviewer to save the final review result locally.

8. A data warehouse model design review device, characterized in that: The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the data warehouse model design and review method according to any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the data warehouse model design and review method according to any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product includes a computer program, and when the computer program is executed by a processor, the steps of the data warehouse model design and review method according to any one of claims 1 to 6 are implemented.

Images