CN109726204B - Data management method and device based on user-defined data table - Google Patents
Data management method and device based on user-defined data table Download PDFInfo
- Publication number
- CN109726204B CN109726204B CN201811582126.9A CN201811582126A CN109726204B CN 109726204 B CN109726204 B CN 109726204B CN 201811582126 A CN201811582126 A CN 201811582126A CN 109726204 B CN109726204 B CN 109726204B
- Authority
- CN
- China
- Prior art keywords
- data
- module
- data table
- defining
- feature set
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Abstract
The invention discloses a data management method and a device based on a user-defined data table, wherein the method comprises the following steps: establishing a user-defined data table; selecting a corresponding user-defined data table according to the data information type to construct a feature set; data profiles are created from the feature sets. The data sheet and the table entry content thereof can be customized by the data sheet management method and the device based on the customized data sheet, the characteristic requirements of data materials in different industries can be flexibly met, the management requirements of different types of materials in enterprises can also be met, and when each data sheet is quoted and created, diversified constraint configurations such as necessary filling constraint, unique constraint, optional range of table entry content, whether a specific table entry content has a sub-characteristic data sheet and the like can be appointed, so that the conditions of excessive recording, less recording and error recording of operators are effectively avoided. In addition, information such as normalized and formatted data names, codes and the like can be automatically generated according to the spliced list items, and the communication efficiency of enterprises is improved.
Description
Technical Field
The invention relates to data management, in particular to a data management method and a data management device based on a user-defined data table.
Background
With the rapid development of software technology and internet economy, the influence of the software technology industry on the manufacturing industry is increased greatly, and with the development and expansion of business scale, the manufacturing enterprises also need to effectively control various production resources and human resources in the manufacturing enterprises, and the most effective method is to develop the safe driving and protection navigation for the enterprises by means of a software management system and an information management means.
At present, the common method is to manually input offline production data into a system in a form of documents by means of various software management systems, similar to ERP, CRM and the like, and to transfer the offline production data to the online production data in a document mode, so that electronization and informatization management is realized, the circulation and sharing of data information are improved, and the aim of improving the production efficiency is finally achieved. Such as: the system defaults to providing some universal data models for data management of various industries, can meet the most basic data management requirements of enterprises, and simultaneously provides a user-defined mode to supplement some new data fields, thereby solving the personalized management requirements of different enterprises.
The data input of the current system adopts manual input, and the system is lack of various effective verification means, so that the situations of wrong recording and less recording often occur. Moreover, different operators have different input habits, which may result in various data formats and bring inconvenience to the internal information communication of enterprises. In addition, the management system lacks cognition on the input data, the identification of the uniqueness of the data by the existing ERP is limited by the uniqueness of codes, but in practical application, the same article is easy to input two different codes due to the fact that an operator is mistaken, and therefore serious influence is brought to subsequent production instructions and inventory management.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provides a data management method and device based on a custom data table.
In order to achieve the purpose, the invention adopts the following technical scheme: a data material management method based on a custom data table comprises the following steps:
establishing a user-defined data table;
selecting a corresponding user-defined data table according to the data information type to construct a feature set;
a data profile is created from the feature set.
The further technical scheme is as follows: the step of establishing the user-defined data table specifically comprises the following steps:
defining a data table name;
judging whether the table name exists, if so, returning to the step of defining the data table name, and if not, entering the step of defining the field type of the data table;
defining a data table field type;
determining whether the content of the table entry in the data table is input in a user-defined mode;
if yes, entering the step of self-defining the table entry content;
if not, entering the step of acquiring the script by the content data of the configuration table entry;
self-defining the content of the table entry;
judging whether the table entry contents in the data table are repeated;
if not, the table entry content is saved;
configuring table item content data acquisition scripts;
verifying whether the script is legal or not;
if so, the script is saved.
The further technical scheme is as follows: the step of selecting the corresponding custom data table to construct the feature set according to the data material type specifically comprises the following steps:
selecting a plurality of data tables as a feature set;
defining constraint conditions for each section of features in the feature set;
defining a naming rule for the feature set;
judging whether a repeated data table exists in the feature set, if not, entering the step of storing the feature set;
a feature set is saved.
The further technical scheme is as follows: the step of creating data profiles according to the feature set specifically comprises the following steps:
acquiring a characteristic data table in a characteristic set;
initializing optional contents in the characteristic data table;
after initialization, selecting values of each section of characteristics in the characteristic data table according to requirements;
and checking and storing the data formed after the values are selected.
The further technical scheme is as follows: the step of verifying and storing the data material formed after the value selection specifically comprises the following steps:
judging whether all the characteristic fields to be filled in the data are assigned, if not, giving an assignment prompt, and if so, entering the step of extracting the unique characteristic field to generate the unique KEY of the data according to a set format;
extracting a unique characteristic field to generate a unique KEY of data information according to a set format;
and inquiring whether the unique KEY of the data information exists, if not, storing the data information and the corresponding unique KEY of the data information.
A data information management device based on a user-defined data table comprises a building unit, a selecting unit and a creating unit;
the establishing unit is used for establishing a user-defined data table;
the selection unit is used for selecting a corresponding custom data table to construct a feature set according to the data material type;
and the creating unit is used for creating data materials according to the feature set.
The further technical scheme is as follows: the establishing unit comprises a first definition module, a first judging module, a second definition module, a second judging module, a self-defining module, a third judging module, a configuration module, a checking module and a first storage module;
the first definition module is used for defining the name of the data table;
the first judging module is used for judging whether the table name exists or not;
the second definition module is used for defining the field type of the data table;
the second judgment module is used for determining whether the content of the table entry in the data table is input in a user-defined mode;
the self-defining module is used for self-defining the content of the table entry;
the third judging module is used for judging whether the contents of the table entries in the data table are repeated;
the configuration module is used for configuring the table entry content data acquisition script;
the checking module is used for checking whether the script is legal or not;
and the first storage module is used for storing the script and the table entry content.
The further technical scheme is as follows: the selection unit comprises a selection module, a third definition module, a fourth judgment module and a second storage module;
the selection module is used for selecting a plurality of data tables as a characteristic set;
the third definition module is used for defining constraint conditions for each section of features in the feature set;
the fourth definition module is used for defining a naming rule for the feature set;
the fourth judging module is used for judging whether a repeated data table exists in the feature set or not;
and the second storage module is used for storing the feature set.
The further technical scheme is as follows: the creating unit comprises an acquiring module, an initializing module, a value selecting module and a checking and storing module;
the acquisition module is used for acquiring a characteristic data table in the characteristic set;
the initialization module is used for initializing the optional contents in the characteristic data table;
the value selecting module is used for selecting the value of each section of characteristics in the characteristic data table according to the requirement after initialization;
and the checking and storing module is used for checking and storing the data formed after the values are selected.
The further technical scheme is as follows: the checking and storing module comprises a judging submodule, an extracting submodule, an inquiring submodule and a storing submodule;
the judging submodule is used for judging whether all the characteristic fields necessary to be filled in the data material are assigned;
the extraction submodule is used for extracting the unique characteristic field and generating a unique KEY of data according to a set format;
the query submodule is used for querying whether the unique KEY of the data material exists;
and the storage submodule is used for storing the data information and the corresponding data information unique KEY.
Compared with the prior art, the invention has the beneficial effects that: the data management method and the device based on the user-defined data table can define the data table and the table entry content thereof by user, can flexibly meet the characteristic requirements of data in different industries and can also meet the management requirements of different types of data in enterprises, and when each data is quoted to create the data, diversified constraint configurations such as necessary filling constraint, unique constraint, optional range of the table entry content, whether a specific table entry content has a sub-characteristic data table and the like can be appointed, so that the conditions of excessive recording, less recording and error recording of operators are effectively avoided. The submitted data material table entry can be checked, so that the same data material is ensured to be unique all the time, and the occurrence of repeated data is effectively avoided. In addition, naming rules can be customized, information such as normalized and formatted data names and codes can be automatically generated according to the spliced list items, and the communication efficiency of enterprises is improved.
The foregoing description is only an overview of the technical solutions of the present invention, and in order to make the technical means of the present invention more clearly understood, the present invention may be implemented according to the content of the description, and in order to make the above and other objects, features, and advantages of the present invention more apparent, the following detailed description will be given of preferred embodiments.
Drawings
FIG. 1 is a flow chart of a specific embodiment of a data management method based on a custom data table according to the present invention;
FIG. 2 is a flow chart of a custom data table in an embodiment of a method for managing data based on a custom data table of the present invention;
FIG. 3 is a flow chart of feature set construction in an embodiment of a method for data management based on a custom data table of the present invention;
FIG. 4 is a flow chart of creating data in an embodiment of a method for managing data based on a custom data table of the present invention;
FIG. 5 is a flow chart of the data management method for checking and saving data according to the embodiment of the invention;
FIG. 6 is a block diagram of a data management apparatus based on a custom data table according to an embodiment of the present invention;
FIG. 7 is a block diagram of a building unit in an embodiment of a custom data table-based data management apparatus;
FIG. 8 is a block diagram of a selecting unit in an embodiment of a data management apparatus based on a custom data table according to the present invention;
FIG. 9 is a block diagram of a creating unit in an embodiment of a custom data table-based data management apparatus according to the invention;
FIG. 10 is a block diagram of a verification save module in an embodiment of a custom data table-based data management apparatus according to the present invention;
FIG. 11 is a table one in accordance with an embodiment of the present invention; FIG. 12 is a table two in accordance with an embodiment of the present invention; FIG. 13 is a table three in an embodiment of the present invention; FIG. 14 is a table four in an embodiment of the present invention; FIG. 15 is a table five in an embodiment of the present invention; FIG. 16 is a table six in an embodiment of the present invention; FIG. 17 is a table seven in accordance with an embodiment of the present invention; FIG. 18 is a table eight in an embodiment of the present invention; FIG. 19 is a table nine in an embodiment of the present invention; FIG. 20 is a table ten in accordance with an embodiment of the present invention; FIG. 21 is a table eleven in an embodiment of the present invention.
Detailed Description
In order to more fully understand the technical content of the present invention, the technical solution of the present invention will be further described and illustrated with reference to the following specific embodiments, but not limited thereto.
As shown in fig. 1-5, the present invention provides a data management method based on a custom data table, which comprises the following steps:
s10, establishing a custom data table;
s20, selecting a corresponding custom data table according to the data type to construct a feature set;
s30, creating data according to the feature set;
specifically, the data table can be defined according to different industries or different types of data, so that the flexibility degree is high, and the application is wide. In addition, by checking the data materials, repeated data can be effectively avoided, and the accuracy of the data materials is improved.
Further, step S10 specifically includes the following steps:
s101, defining a data table name;
s102, judging whether the table name exists, if so, returning to the step S101, and if not, entering the step S103;
s103, defining the field type of the data table;
s104, determining whether the content of the table entry in the data table is input in a user-defined mode;
if yes, go to step S1041;
if not, go to step S1042;
s1041, self-defining the content of the table entry;
s105, judging whether the contents of the table entries in the data table are repeated; if not, S107, the table entry content is saved; if so, prompting the illegal;
s1042, configuring table entry content data acquisition scripts;
s106, checking whether the script is legal or not; if yes, S108, saving the script, otherwise, prompting illegal.
Specifically, as shown in fig. 11, a newly defined table code and a table name are input to form a table name, such as: TABLE1, model number TABLE. And judging whether the TABLE code TABLE1 exists or not, and if so, prompting that the TABLE code TABLE1 cannot be created. If the TABLE code TABLE1 is not used, entering a set TABLE field type page, and fixing the TABLE with: the table entry comprises fields such as table entry codes, table entry names, table entry abbreviations, table entry descriptions and states, wherein the two fields such as the table entry names and the table entry descriptions can be used for specifying specific data types by a user, and the specific data types comprise multiple common data types such as negative numbers, positive numbers, integers, decimal numbers (accurate digits), dates, universal texts, english characters and the like.
After the field type is specified, the table entry content source of the data table is continuously specified, and the method has two modes of self-definition and script configuration.
A user-defined mode: and the user performs operations such as adding, modifying, deleting, disabling, enabling and the like on the table entry content of the data table.
Script configuration mode: the configuration can be performed from the existing other system database tables in an SQL query script mode, for example, a system table A exists: the library position information table has fields: the method comprises the following steps of library position coding, library position name, library position address, library position remarks, warehouse personnel, contact information and library position state, wherein in order to reduce repeated data definition, entry maintenance and other work, a user-defined data table B can be defined: the library bit table sets a data source as script configuration, and the script is as follows: SELECT library bit code AS 'entry code', library bit name AS 'entry name', library bit remark AS 'entry description', 'valid' AS 'state' FROM a WHERE library bit state = 'valid'.
Judging the validity of the script content when submitting the configuration script: firstly, whether the script accords with the SQL grammar or not and whether the script can be executed or not are judged; secondly, inquiring whether the result field is in one-to-one correspondence with the user-defined data table field; whether the data type of the field query result of the third table item name, the table item description and the like is consistent with the data type specified in the user-defined data table or not; in the fourth query result, whether the table entry codes and the table entry names are repeated or not must meet the principle that the table entry codes are unique and the table entry names are unique;
assume that TABLE1 is defined and its entry name field is specified as a plain text type and the data source is: if it is self-defined, specific table entry contents can be defined for the data table, such as: table entry coding: 001, list item brevity code: none, entry name: type A, list item abbreviation: none. After the input, the entry code and the name are divided into a TABLE1 TABLE for duplication checking, if the entry exists, the entry cannot be submitted for storage, and the code and the name are ensured to be unique in the same data TABLE.
In addition, for data sources: in the script configuration, the user can not maintain the contents of the list items by adding and deleting, and only can check the contents, and the data is obtained by directly inquiring the system table by the script.
As shown in fig. 12 to 14, the present embodiment further defines three additional TABLEs, which are TABLE2 and data TABLE name: color table, name field input type is plain text. TABLE3, data TABLE name: and in the table processing process, the input type of the name field is a common text. TABLE4, data TABLE name: electroplating color, the input type of the name field is a common text:
further, step S20 specifically includes the following steps:
s201, selecting a plurality of data tables as a feature set;
s202, defining constraint conditions for each section of features in the feature set;
s203, defining a naming rule for the feature set;
s204, judging whether a repeated data table exists in the feature set, if so, not storing, returning to the step S201, and if not, entering the step S205;
and S205, storing the feature set.
The data management can be completed by the defined data table and the table item content. Specifically, the characteristics required for describing the data are abstracted for the data of a certain category, the characteristic attributes all consist of a self-defined data table (if the data table does not have the data table, the data table and the table entry content are defined firstly) or a text input type, and the like, and one data table can only appear once in the same characteristic set. Such as: profile class A defines a feature set consisting of TABLE1, TABLE2, and TABLE 3.
After the feature set is clarified, constraints can be defined for each segment of features, including bound-fill constraints, cascade features, table entry ranges, uniqueness features, usage constraints, and so on, as well as naming rules such as codes, names, and specifications.
Specifically, the bound constraint: specifying which features in the feature set must be filled and which are not, and for the constraints of filling, the features must have values when subsequently referencing the feature set to create the data profile.
Setting a cascade characteristic: for example, the feature set has a feature 1 input type of a custom data table a, and when the content of some specific entries in the feature selected data table a can be specified, a cascading feature occurs, and the cascading feature input types are all data tables, so that a custom data table is selected for the cascading feature, for example: the feature set has a process feature, and the table entries have: electroplating and antifogging, wherein when electroplating is selected, a cascade characteristic 'electroplating color' can be set and an electroplating color number data table appears for selection, and when antifogging is selected, a cascade characteristic 'antifogging requirement' can be set and an antifogging process data table appears for specifying specific antifogging process requirements.
Setting a feature table item selection range: when the contents of the table entries of some data tables are many and are suitable for different types of data materials, the selectable table entry range can be specified for the different types of data materials, the selection range is narrowed, the error probability is reduced, and the selectable range is set to provide modes such as a fixed table entry set and SQL script configuration.
The unique characteristic: and specifying which features in the feature set participate in the uniqueness check, wherein fields set as the uniqueness features must be simultaneously bound for filling, and when data materials are subsequently created, the table entry content selected by the uniqueness features is used for the material uniqueness check.
And (3) use constraint: specifying a use for each feature in the feature set, comprising: engineering, business, production, process, working hours, cost, market, and the like, or not.
The naming rule is the necessary attribute of the feature set, can clarify how information such as data codes, data names, specifications and the like is generated after data creation, can be formed by automatically extracting table entry codes and names of certain features from the feature set through configuring the specifications, and can also be set to be self-defined (self-definition is that a user self-defines and inputs naming information when creating the data).
Specifically, the encoding rule is as follows: when the data information is needed to generate coding information after being created, the input type can be selected from the feature set to be combined with the features of the data table for automatically generating codes, and the coding information can be combined by the table entry codes, the table entry names, various separators and the like of the user-defined data table.
Name rule: when name information is needed to be generated after data information is created, all the characteristics can be selected from the characteristic set to be combined to automatically generate an information name, and the information name can be combined by the table entry codes, the table entry names, the text information of the input types and various separators of the user-defined data table.
Specification rules: when the specification is needed to be generated after the data is created, all the features can be selected from the feature set to be combined to automatically generate a data name, and the data name can be combined by the table entry codes, the table entry names, the text information of the input types and various separators of the user-defined data table.
When generating corresponding codes, names and specifications, if the table item content in the naming rules has corresponding brevity codes or abbreviation, then when extracting the table item codes or table item names, the brevity codes or abbreviation codes are preferentially used, and if not, the table item codes and table item names are used.
TABLE1, TABLE2 and TABLE3 are all the essential fill features defined in the TABLE of fig. 15; TABLE3 has cascade characteristics, and the condition of the cascade characteristics is that TABLE4 characteristics appear when TABLE3 selects entry code = 01; TABLE1, TABLE2, TABLE3 are all unique features; TABLE2 sets the selectable TABLE entry range, only red; data encoding rules: the table entry coding of the data type A, the model table and the table entry coding of the table processing technology, and has a 2-bit stream number, "-" as a separator; data name rules: the table item name of the model table, the table item name of the table processing technology, the table item name of the color table and the name of the electroplating color table item, and the '/' is used as a separator; specification rules are as follows: self-defining, and inputting by the user.
Further, step S30 specifically includes the following steps:
s301, acquiring a feature data table in a feature set;
s302, initializing optional contents in the characteristic data table;
s303, after initialization, selecting values of each section of characteristics in the characteristic data table according to requirements;
s304, checking and storing the data formed after the values are selected.
Specifically, when the data is created by referring to the feature set, the user-defined data tables corresponding to the features contained in the feature set are displayed, and optional contents of the data tables are initialized, but the data tables of the cascade features are not initialized. When creating data profiles by referring to the feature set defined in the above step, TABLE1 type TABLE, TABLE3 processing technology, TABLE2 color TABLE (red can be selected) are listed as shown in fig. 16.
In addition, after the initialization of each feature data table of the feature set is finished, a user can select values of each segment of features according to actual needs, data creation is carried out in a mode of clear value selection step by step, after the values are selected, a system can judge whether the features are set with cascade features, if yes, the system judges whether the conditions for leading out the cascade features are met, the cascade features are set in the feature set defined above, and the feature processing process features set with the cascade features are set, so when the user selects the values of the features, when the table entry code =01 is selected, the electroplating color feature appears, the user is required to select the electroplating color, and if the table entry code selected by the table processing process is not 01, the cascade feature of the electroplating color does not appear.
Further, step S304 specifically includes the following steps:
s3401, judging whether all the characteristic fields to be filled in the data material are assigned, if not, S3042, giving an assignment prompt, and if so, entering the step S3043;
s3043, extracting the unique characteristic field to generate a unique KEY of the data information according to a set format;
s3044, inquiring whether the unique KEY of the data information exists, if not, S3045, saving the data information and the corresponding unique KEY of the data information. If yes, the data is not stored.
Specifically, after selecting values one by one, when submitting data information, a user performs preliminary verification according to input information such as the bound constraint feature and the uniqueness feature set by the feature set, all the characteristic fields of the bound constraint and the uniqueness must have selected values, and otherwise, a prompt is given.
After the legality is verified, the system verifies the uniqueness of the created data, firstly, the characteristics are defined in a centralized mode as fields of the uniqueness characteristics, all the selected contents are extracted, the selected contents are sorted in an ascending order according to the format of table entry codes of a data table and then spliced into a complete character string, the top of the character string is added with a data type to serve as the only KEY of the data, and the I is used as a separator when all the characteristics are spliced.
If the selected content for each feature of the created data material is as shown in fig. 17, then the unique KEY for the generated material is: data type A | model table 001| table processing technique 02| color table RED.
And after the unique KEY of the data material is generated, comparing the data material with the unique KEY of the existing data material, if the data material is repeated, indicating that the data material exists, and the data material cannot be repeatedly created, otherwise, the data material can be created, and storing the data material.
After uniqueness verification, according to the naming rule defined by the feature set, information such as data material codes, names, specifications and the like is automatically generated for a user to preview, if the naming rule is self-defined, the user can automatically input the information, and if the naming rule is self-defined, the specification of the preview page is an editable text box, and the user can input the specification content. But for the information automatically generated by the rule, attention needs to be paid to the generation modes of data coding repetition, stepless connection characteristic, short code short form and the like,
wherein the data encoding repeats: when feature set constraints are configured in a feature set, if the uniqueness feature does not participate in the encoding rule, the uniqueness KEY may not be repeated, but if the automatically generated data material is repeatedly encoded, the uniqueness KEY may need to be distinguished by a serial number. As shown in fig. 18 and 19, both data are legal, the unique KEY of the data material is not repeated, but the data encoding is repeated, so that the data are distinguished by serial numbers.
The characteristics of stepless connection: the naming convention in the feature set definition may reference a cascaded feature data table, but in some cases the cascaded feature table may not be present, and the segment of information in the naming convention is replaced with a null value, and if a delimiter exists before, the delimiter is removed at the same time. As shown in fig. 20, the anti-fog process data was created without the appearance of cascade features: plating color, then when the data material name is generated, the last segment of plating color is empty and preceded by a separator/removed.
The simplified code is adopted for short: when extracting corresponding characteristic values according to the naming rules for naming, if the characteristic values have brevity codes or abbreviation codes in the corresponding self-defined data table, the list item codes/list item names need to be replaced by the brevity codes/abbreviation codes. As shown in fig. 21, if the electroplating process data is created and the value of entry code 03 is selected, which has MR for short in the table processing process data table, then when the data name is automatically generated, the second segment: the table processing technology [ name ] needs to be replaced by short names, and the method can better avoid the method by means of the short codes and the short names in order to simplify the generation of the codes and the names of the data when the table entry codes and the table entry names are relatively long.
And after the data preview page is submitted, the created data can be stored. Specifically, the data table name and the table entry code corresponding to each section of characteristic value are stored, so that the data can be quickly and accurately retrieved through characteristic combination in the follow-up process; storing information such as data codes, names, specifications and the like; and storing the unique KEY information of the data information for direct use when the subsequent system verifies the unique KEY, and regenerating a new unique KEY for duplicate checking if the data information is changed.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
Corresponding to the data management method based on the user-defined data table in the embodiment, the invention also provides a data management device based on the user-defined data table. As shown in fig. 6-10, the apparatus includes an establishing unit 1, a selecting unit 2, and a creating unit 3, where the establishing unit 1 is configured to establish a custom data table; the selection unit 2 is used for selecting a corresponding custom data table to construct a feature set according to the data material type; and the creating unit 3 is used for creating data materials according to the feature set.
Specifically, the data table can be defined according to different industries or different types of data, so that the flexibility degree is high, and the application is wide. In addition, by checking the data materials, repeated data can be effectively avoided, and the accuracy of the data materials is improved.
Further, the establishing unit 1 includes a first defining module 11, a first determining module 12, a second defining module 13, a second determining module 14, a self-defining module 15, a third determining module 16, a configuring module 17, a verifying module 18, and a first saving module 19.
The first defining module 11 is configured to define a data table name;
a first judging module 12, configured to judge whether a table name exists;
a second defining module 13, configured to define a field type of the data table;
the second judging module 14 is configured to determine whether entry content in the data table is entered in a user-defined manner;
the self-defining module 15 is used for self-defining the content of the table entry;
a third judging module 16, configured to judge whether the contents of the entries in the data table are repeated;
a configuration module 17, configured to configure the table entry content data acquisition script;
a checking module 18 for checking whether the script is legal;
and the first saving module 19 is used for saving the script and the table entry content.
Specifically, as shown in fig. 11, a newly defined table code and a table name are input to form a table name, such as: TABLE1, model number TABLE. And judging whether the TABLE code TABLE1 exists or not, and if so, prompting that the TABLE code TABLE1 cannot be created. If the TABLE code TABLE1 is not used, entering a set TABLE field type page, and fixing the TABLE with: the table entry comprises fields of table entry codes, table entry names, table entry abbreviation, table entry descriptions, states and the like, wherein the two fields of the table entry names and the table entry descriptions can be specified by a user to specific data types, including various common data types such as negative numbers, positive numbers, integers, decimal numbers (precise digits), dates, general texts, english characters and the like.
After the field type is specified, the table entry content source of the data table is continuously specified, and the method has two modes of self-definition and script configuration.
A user-defined mode: and the user performs operations such as adding, modifying, deleting, disabling, enabling and the like on the table entry content of the data table.
Script configuration mode: the configuration can be performed from the existing other system database tables in an SQL query script mode, for example, a system table A exists: the library position information table has fields: the library position code, the library position name, the library position address, the library position remark, the warehouse personnel, the contact way and the library position state can define a self-defined data table B in order to reduce the work of repeated data definition, entry maintenance and the like: and the library bit table sets a data source as script configuration, and the script is as follows: SELECT library bit code AS 'entry code', library bit name AS 'entry name', library bit remark AS 'entry description', 'valid' AS 'state' FROM a WHERE library bit state = 'valid'.
Judging the validity of the script content when submitting the configuration script: firstly, whether the script accords with the SQL grammar or not and whether the script can be executed or not are judged; secondly, inquiring whether the result field is in one-to-one correspondence with the user-defined data table field; whether the data type of the field query result of the third table item name, the table item description and the like is consistent with the data type specified in the user-defined data table or not; in the fourth query result, whether the table entry codes and the table entry names are repeated or not must meet the principle that the table entry codes are unique and the table entry names are unique;
assume that TABLE1 is defined and its entry name field is specified as a plain text type and the data source is: if the data table is self-defined, specific table entry contents can be defined for the data table, such as: table entry coding: 001, list item brevity code: none, entry name: type A, list item abbreviation: none. After the input, the entry code and the name are divided into the TABLE1 TABLE for duplication checking, if the entry exists, the entry cannot be submitted for storage, and the code and the name are ensured to be unique in the same data TABLE.
In addition, for data sources: in the script configuration, the user can not maintain the contents of the list items by adding and deleting, and only can check the contents, and the data is obtained by directly inquiring the system table by the script.
Further, the selecting unit 2 includes a selecting module 21, a third defining module 22, a fourth defining module 23, a fourth determining module 24, and a second storing module 25.
A selecting module 21, configured to select multiple data tables as a feature set;
a third defining module 22, configured to define a constraint condition for each segment of features in the feature set;
a fourth defining module 23, configured to define a naming rule for the feature set;
a fourth judging module 24, configured to judge whether there is a duplicate data table in the feature set;
a second saving module 25 for saving the feature set.
The data management can be completed by the defined data table and the table entry content. Specifically, the characteristics required for describing the data are abstracted for the data of a certain category, and the characteristic attributes comprise a custom data table (if the data table does not have, the data table and the table entry content are defined in advance) or a text input type, and one data table can only appear once in the same characteristic set. Such as: profile class A defines a feature set consisting of TABLE1, TABLE2, and TABLE 3.
After the feature set is clarified, constraints can be defined for each segment of features, including bound-fill constraints, cascade features, table entry ranges, uniqueness features, usage constraints, and the like, as well as naming rules such as codes, names, and specifications.
Specifically, the bound constraint: specifying which features in the feature set must be filled and which are not, and for the constraints of filling, the features must have values when subsequently referencing the feature set to create the data profile.
Setting a cascade characteristic: for example, the feature set has a feature 1 input type of a custom data table a, and when the content of some specific entries in the feature selected data table a can be specified, a cascading feature occurs, and the cascading feature input types are all data tables, so that a custom data table is selected for the cascading feature, for example: the feature set has a process feature, and the table entries have: electroplating and antifogging, wherein when electroplating is selected, a cascade characteristic 'electroplating color' can be set and an electroplating color number data table appears for selection, and when antifogging is selected, a cascade characteristic 'antifogging requirement' can be set and an antifogging process data table appears for specifying specific antifogging process requirements.
Setting a feature table item selection range: when the contents of the table entries of some data tables are many and are suitable for different types of data materials, selectable table entry ranges can be designated for the different types of data materials, the selection range is narrowed, the error probability is reduced, and the selectable range is set to provide modes such as a fixed table entry set and SQL script configuration.
Unique characteristics: and specifying which features in the feature set participate in the uniqueness check, wherein the field set as the uniqueness feature must be a bound for filling at the same time, and when the data material is subsequently created, the content of the table entry selected by the uniqueness feature is used for the material uniqueness check.
And (3) restricting the use: specifying a use for each feature in the feature set, comprising: engineering, business, production, process, working hours, cost, market, and the like, or not.
The naming rule is the necessary attribute of the feature set, can clarify how information such as data codes, data names and specifications is generated after data is created, can be formed by automatically extracting table entry codes and name combinations of certain characteristics from the feature set through configuring the specifications, and can also be set to be self-defined (self-defining means that a user self-defines and inputs naming information when creating data).
Specifically, the encoding rule: when the coding information is needed to be generated after the data information is created, the input type is selected from the feature set and combined with the features of the data table for automatically generating the codes, and the codes can be combined by the table entry codes, the table entry names, various separators and the like of the user-defined data table.
Name rule: when name information is needed after data information is created, all features can be selected from the feature set to be combined to automatically generate an information name, and the information name can be combined by the table entry code, the table entry name, the text information of the input type and various separators of the user-defined data table.
Specification rules are as follows: when the specification is needed to be generated after the data material is created, all the characteristics can be selected from the characteristic set to be combined to automatically generate a material name, and the data can be formed by combining the table entry codes, the table entry names, the text information of the input types and various separators of the user-defined data table.
When generating corresponding codes, names and specifications, if the table item content in the naming rule has corresponding brevity codes or abbreviation codes, when extracting the table item codes or table item names, the brevity codes or abbreviation codes are preferentially used, and if not, the table item codes and the table item names are used.
TABLE1, TABLE2 and TABLE3 are all the essential fill features defined in the TABLE of fig. 15; TABLE3 has cascade characteristics, and the condition of the cascade characteristics is that TABLE4 characteristics appear when TABLE3 selects entry code = 01; TABLE1, TABLE2, TABLE3 are all unique features; TABLE2 sets the selectable TABLE entry range, only red; the data encoding rule is as follows: the table entry coding of the data type A, the model table and the table entry coding of the table processing technology, and has a 2-bit stream number, "-" as a separator; data name rules: the table item name of the model table, the table item name of the table processing technology, the table item name of the color table and the name of the electroplating color table item, and the '/' is used as a separator; specification rules are as follows: self-defining, and inputting by the user.
Further, the creating unit 3 includes an acquiring module 31, an initializing module 32, a selecting module 33, and a checking and saving module 34.
The acquiring module 31 is configured to acquire a feature data table in a feature set;
an initialization module 32, configured to initialize optional contents in the feature data table;
a value selecting module 33, configured to select a value for each segment of features in the feature data table according to needs after initialization;
and the checking and storing module 34 is used for checking and storing the data formed after the value selection.
Specifically, when the data is created by referring to the feature set, the user-defined data tables corresponding to the features contained in the feature set are displayed, and the optional contents of each data table are initialized, but the data tables of the cascading features are not initialized. When creating data profiles by referring to the feature set defined in the above steps, TABLE1 type TABLE, TABLE3 processing technique, TABLE2 color TABLE (red can be selected) are listed as shown in fig. 16.
In addition, after the initialization of each feature data table of the feature set is finished, a user can select values of each segment of features according to actual needs, data creation is carried out in a mode of clear value selection step by step, after the values are selected, a system can judge whether the features are set with cascade features, if yes, the system judges whether the conditions for leading out the cascade features are met, the cascade features are set in the feature set defined above, and the feature processing process features set with the cascade features are set, so when the user selects the values of the features, when the table entry code =01 is selected, the electroplating color feature appears, the user is required to select the electroplating color, and if the table entry code selected by the table processing process is not 01, the cascade feature of the electroplating color does not appear.
Further, the verification storage module 34 includes a judgment sub-module 341, an extraction sub-module 342, a query sub-module 343, and a storage sub-module 344;
the judging submodule 341 is configured to judge whether all the characteristic fields that must be filled in the data are assigned;
the extraction submodule 342 is used for extracting the unique characteristic field and generating a unique KEY of the data according to a set format;
the query submodule 343 is configured to query whether the unique KEY for data information already exists;
the saving sub-module 344 is configured to save the data and the corresponding unique KEY of the data.
Specifically, after the user selects values one by one, when submitting data materials, performing preliminary verification according to input information such as mandatory fill constraint characteristics and uniqueness characteristics set by the characteristic set, wherein all characteristic fields of mandatory fill constraint and uniqueness must have selected values, otherwise, giving a prompt.
After the legality is verified, the system verifies the uniqueness of the created data, firstly, the characteristics are defined in a centralized mode as fields of the uniqueness characteristics, all the selected contents are extracted, the selected contents are sorted in an ascending order according to the format of table entry codes of a data table and then spliced into a complete character string, the top of the character string is added with a data type to serve as the only KEY of the data, and the I is used as a separator when all the characteristics are spliced.
If the selected content for each feature of the created data material is as shown in fig. 17, then the unique KEY for the generated material is: data type A | model table 001| table processing technique 02| color table RED.
And after the unique KEY of the data material is generated, comparing the data material with the unique KEY of the existing data material, if the data material is repeated, indicating that the data material exists, and the data material cannot be repeatedly created, otherwise, the data material can be created, and storing the data material.
After uniqueness verification, according to the naming rule defined by the feature set, information such as data material codes, names, specifications and the like is automatically generated for a user to preview, if the naming rule is self-defined, the user can automatically input the information, and if the naming rule is self-defined, the specification of the preview page is an editable text box, and the user can input the specification content. But for the information automatically generated by the rule, attention needs to be paid to the generation modes of data coding repetition, stepless connection characteristic, short code short form and the like,
wherein the data encoding repeats: when feature set constraints are configured in a feature set, the uniqueness feature does not participate in the encoding rule, so that the uniqueness KEY is not repeated, but the automatically generated data material is repeatedly encoded, and then the data material is required to be distinguished through serial numbers. As shown in fig. 18 and 19, both data are legal, the data material unique KEY is not repeated, but the data coding is repeated, so that the data are distinguished by serial numbers.
The characteristics of stepless connection: the naming convention in the feature set definition may reference a cascaded feature data table, but in some cases the cascaded feature table may not be present, and the segment of information in the naming convention is replaced with a null value, and if a delimiter exists before, the delimiter is removed at the same time. As shown in fig. 20, the antifogging process data file is created without the appearance of cascading features: plating color, then when generating the data name, the last segment of plating color is empty and preceded by a separator/also removed.
The simplified code is adopted for short: when extracting corresponding characteristic values according to the naming rules for naming, if the characteristic values have brevity codes or abbreviation codes in the corresponding self-defined data table, the list item codes/list item names need to be replaced by the brevity codes/abbreviation codes. As shown in fig. 21, the electroplating process data is created, the value of entry code 03 is selected, and the entry has MR for short in the table processing process data table, then when the data name is automatically generated, the second segment: the table processing technology [ name ] needs to be replaced by a short form, and the method can be well avoided by means of the short code and short form in order to simplify the generation of the codes and the names of the data when the table entry codes and the table entry names are relatively long.
And after the data preview page is submitted, the created data can be stored. Specifically, the data table name and the table entry code corresponding to each section of characteristic value are stored, so that the data can be quickly and accurately retrieved through characteristic combination in the follow-up process; storing information such as data codes, names, specifications and the like; and storing the unique KEY information of the data information for direct use when the subsequent system verifies the unique KEY, and regenerating a new unique KEY for duplicate checking if the data information is changed.
The technical contents of the present invention are further illustrated by the examples only for the convenience of the reader, but the embodiments of the present invention are not limited thereto, and any technical extension or re-creation based on the present invention is protected by the present invention. The protection scope of the invention is subject to the claims.
Claims (4)
1. A data material management method based on a custom data table is characterized by comprising the following steps:
establishing a user-defined data table;
selecting a corresponding custom data table according to the data material type to construct a feature set;
creating data according to the feature set;
the step of selecting the corresponding custom data table to construct the feature set according to the data material type specifically comprises the following steps:
selecting a plurality of data tables as a characteristic set;
defining constraint conditions for each section of features in the feature set;
defining a naming rule for the feature set;
judging whether a repeated data table exists in the feature set, if not, entering a step of storing the feature set;
saving the feature set;
the step of creating data profiles from the feature sets specifically comprises the steps of:
acquiring a characteristic data table in a characteristic set;
initializing optional contents in the characteristic data table;
after initialization, selecting values of each section of characteristics in the characteristic data table according to requirements;
checking and storing data formed after value selection;
the step of checking and storing the data formed after the value selection specifically comprises the following steps:
judging whether all the characteristic fields which need to be filled in the data information are assigned, if not, giving an assignment prompt, and if so, entering a step of extracting the unique characteristic fields to generate a unique KEY of the data information according to a set format;
extracting a unique characteristic field to generate a unique KEY of data according to a set format;
and inquiring whether the unique KEY of the data information exists or not, if not, storing the data information and the corresponding unique KEY of the data information.
2. The method for managing data information based on a custom data table as claimed in claim 1, wherein the step of establishing a custom data table specifically comprises the following steps:
defining a data table name;
judging whether the table name exists, if so, returning to the step of defining the data table name, and if not, entering the step of defining the field type of the data table;
defining a data table field type;
determining whether the content of the table entry in the data table is input in a user-defined mode;
if yes, entering a step of self-defining the content of the table entry;
if not, entering a step of configuring table item content data acquisition scripts;
self-defining the content of the table entry;
judging whether the table entry contents in the data table are repeated;
if not, saving the table entry content;
configuring table item content data acquisition scripts;
verifying whether the script is legal or not;
if so, the script is saved.
3. A data information management device based on a user-defined data sheet is characterized by comprising a building unit, a selecting unit and a creating unit;
the establishing unit is used for establishing a user-defined data table;
the selection unit is used for selecting a corresponding custom data table to construct a feature set according to the data material type;
the creation unit is used for creating data materials according to the feature set;
the selection unit comprises a selection module, a third definition module, a fourth judgment module and a second storage module;
the selection module is used for selecting a plurality of data tables as a characteristic set;
the third definition module is used for defining constraint conditions for each section of features in the feature set;
the fourth definition module is used for defining a naming rule for the feature set;
the fourth judging module is used for judging whether a repeated data table exists in the feature set;
the second saving module is used for saving the feature set;
the creating unit comprises an acquiring module, an initializing module, a value selecting module and a checking and storing module;
the acquisition module is used for acquiring a characteristic data table in the characteristic set;
the initialization module is used for initializing the optional contents in the characteristic data table;
the value selecting module is used for selecting the value of each section of characteristics in the characteristic data table according to the requirement after initialization;
the check storage module is used for checking and storing data information formed after value selection;
the checking and storing module comprises a judging submodule, an extracting submodule, an inquiring submodule and a storing submodule;
the judging submodule is used for judging whether all the characteristic fields which need to be filled in the data material are assigned;
the extraction submodule is used for extracting the unique characteristic field and generating a unique KEY of data according to a set format;
the query submodule is used for querying whether the unique KEY of the data material exists;
and the storage submodule is used for storing the data information and the corresponding data information unique KEY.
4. The device according to claim 3, wherein the establishing unit comprises a first defining module, a first determining module, a second defining module, a second determining module, a self-defining module, a third determining module, a configuring module, a verifying module, and a first saving module;
the first definition module is used for defining the name of the data table;
the first judging module is used for judging whether the table name exists or not;
the second definition module is used for defining the field type of the data table;
the second judgment module is used for determining whether the content of the table entry in the data table is input in a user-defined mode;
the self-defining module is used for self-defining the content of the table entry;
the third judging module is used for judging whether the contents of the table entries in the data table are repeated;
the configuration module is used for configuring the table entry content data acquisition script;
the checking module is used for checking whether the script is legal or not;
and the first storage module is used for storing the script and the table entry content.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811582126.9A CN109726204B (en) | 2018-12-24 | 2018-12-24 | Data management method and device based on user-defined data table |
| CN202211477527.4A CN115827627A (en) | 2018-12-24 | 2018-12-24 | Data management method and device based on user-defined data table |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811582126.9A CN109726204B (en) | 2018-12-24 | 2018-12-24 | Data management method and device based on user-defined data table |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211477527.4A Division CN115827627A (en) | 2018-12-24 | 2018-12-24 | Data management method and device based on user-defined data table |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109726204A CN109726204A (en) | 2019-05-07 |
| CN109726204B true CN109726204B (en) | 2023-01-31 |
Family
ID=66296404
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211477527.4A Pending CN115827627A (en) | 2018-12-24 | 2018-12-24 | Data management method and device based on user-defined data table |
| CN201811582126.9A Active CN109726204B (en) | 2018-12-24 | 2018-12-24 | Data management method and device based on user-defined data table |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211477527.4A Pending CN115827627A (en) | 2018-12-24 | 2018-12-24 | Data management method and device based on user-defined data table |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN115827627A (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110210253A (en) * | 2019-05-08 | 2019-09-06 | 北京机电工程总体设计部 | EBOM method of calibration between a kind of enterprise based on PDM system |
| CN113722335B (en) * | 2021-09-16 | 2023-07-21 | 宇宙世代信息技术（深圳）有限公司 | Trigger display method, device and equipment for geographic position and content management |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101241434A (en) * | 2008-03-04 | 2008-08-13 | 浪潮集团山东通用软件有限公司 | Form self-defining method |
| CN101425060A (en) * | 2007-11-02 | 2009-05-06 | 英业达股份有限公司 | Database data table generating method |
| CN102346785A (en) * | 2011-11-15 | 2012-02-08 | 北京创腾科技有限公司 | Method and device for directly self-defining field of database |
| CN103631570A (en) * | 2012-08-21 | 2014-03-12 | 镇江雅迅软件有限责任公司 | Form self-definition method |
| CN104156348A (en) * | 2014-08-11 | 2014-11-19 | 中国人民解放军军械工程学院 | IETM process data entry device and method based on templates |
| CN104268272A (en) * | 2014-10-14 | 2015-01-07 | 青岛海尔软件有限公司 | Method and device for checking uniqueness of data |
| CN104346377A (en) * | 2013-07-31 | 2015-02-11 | 克拉玛依红有软件有限责任公司 | Method for integrating and exchanging data on basis of unique identification |
| CN108229921A (en) * | 2017-09-05 | 2018-06-29 | 杭州孚嘉科技有限公司 | National tax land tax combines data collecting system and its operating method |
| CN108776702A (en) * | 2018-06-11 | 2018-11-09 | 浪潮软件股份有限公司 | A kind of data make a report on page user-defined visual configuration method |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6154753A (en) * | 1995-09-15 | 2000-11-28 | Cable & Wireless, Inc. | Document management system and method for business quality modeling |
| CN102467704A (en) * | 2010-11-10 | 2012-05-23 | 金蝶软件（中国）有限公司 | Method and system for generating data table of just-in-time inventory management |
| WO2016191995A1 (en) * | 2015-05-31 | 2016-12-08 | 华为技术有限公司 | Method and device for partitioning association table in distributed database |
| CN105653732A (en) * | 2016-02-02 | 2016-06-08 | 优品财富管理有限公司 | Automatic table establishment method and system based on metadata |
| CN108932268B (en) * | 2017-05-26 | 2020-09-04 | 华为技术有限公司 | Data processing method and device |
-
2018
- 2018-12-24 CN CN202211477527.4A patent/CN115827627A/en active Pending
- 2018-12-24 CN CN201811582126.9A patent/CN109726204B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101425060A (en) * | 2007-11-02 | 2009-05-06 | 英业达股份有限公司 | Database data table generating method |
| CN101241434A (en) * | 2008-03-04 | 2008-08-13 | 浪潮集团山东通用软件有限公司 | Form self-defining method |
| CN102346785A (en) * | 2011-11-15 | 2012-02-08 | 北京创腾科技有限公司 | Method and device for directly self-defining field of database |
| CN103631570A (en) * | 2012-08-21 | 2014-03-12 | 镇江雅迅软件有限责任公司 | Form self-definition method |
| CN104346377A (en) * | 2013-07-31 | 2015-02-11 | 克拉玛依红有软件有限责任公司 | Method for integrating and exchanging data on basis of unique identification |
| CN104156348A (en) * | 2014-08-11 | 2014-11-19 | 中国人民解放军军械工程学院 | IETM process data entry device and method based on templates |
| CN104268272A (en) * | 2014-10-14 | 2015-01-07 | 青岛海尔软件有限公司 | Method and device for checking uniqueness of data |
| CN108229921A (en) * | 2017-09-05 | 2018-06-29 | 杭州孚嘉科技有限公司 | National tax land tax combines data collecting system and its operating method |
| CN108776702A (en) * | 2018-06-11 | 2018-11-09 | 浪潮软件股份有限公司 | A kind of data make a report on page user-defined visual configuration method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109726204A (en) | 2019-05-07 |
| CN115827627A (en) | 2023-03-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108090073B (en) | Configurable bill of material conversion method and device | |
| US7739249B2 (en) | Data generator apparatus testing data dependent applications, verifying schemas and sizing systems | |
| CN103838672A (en) | Automated testing method and device for all-purpose financial statements | |
| CN110309125A (en) | Data verification method, electronic device and storage medium | |
| CN109067704B (en) | Satellite remote control instruction format design and coding management system and method | |
| CN109726204B (en) | Data management method and device based on user-defined data table | |
| CN115061721A (en) | Report generation method and device, computer equipment and storage medium | |
| CN110543303B (en) | Visual service platform | |
| CN113672230B (en) | Industrial element identification coding method | |
| CN115293106A (en) | BIM bill of materials-based three-code system cost application method | |
| CN111475511A (en) | Data storage method, data access method, data storage device, data access device and data access equipment based on tree structure | |
| CN113486418B (en) | BIM model cloud coding method and system | |
| CN110647564A (en) | Hive table establishing method, electronic device and computer readable storage medium | |
| CN112182021B (en) | User data query method, device and system | |
| CN112230900A (en) | Development engine system and method for self-defining setting form model | |
| CN105912723A (en) | Storage method of custom field | |
| CN113887171A (en) | Measuring point code standardization automatic conversion method for wind power generation system | |
| CN103488616B (en) | A kind of embedded font processing method and device | |
| CN115544132A (en) | Data import method and system and electronic equipment | |
| CN113254457B (en) | Account checking method, account checking system and computer readable storage medium | |
| CN112487198A (en) | Physical model processing method and device, electronic equipment and computer storage medium | |
| CN116263770A (en) | Method, device, terminal equipment and medium for storing business data based on database | |
| CN114519050A (en) | Vehicle part configuration logic constraint relation generation method, device, equipment and medium | |
| CN114691722B (en) | Method and system for rapidly selecting package detection standard | |
| CN109408510A (en) | A kind of method for normalizing and device of data model |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |