CN115936017A - Main data management method supporting interface multiple languages and data multiple languages - Google Patents

Main data management method supporting interface multiple languages and data multiple languages Download PDF

Info

Publication number
CN115936017A
CN115936017A CN202310040170.1A CN202310040170A CN115936017A CN 115936017 A CN115936017 A CN 115936017A CN 202310040170 A CN202310040170 A CN 202310040170A CN 115936017 A CN115936017 A CN 115936017A
Authority
CN
China
Prior art keywords
data
interface
language
main data
managed
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.)
Granted
Application number
CN202310040170.1A
Other languages
Chinese (zh)
Other versions
CN115936017B (en
Inventor
金震
张京日
张宪涛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing SunwayWorld Science and Technology Co Ltd
Original Assignee
Beijing SunwayWorld Science and Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing SunwayWorld Science and Technology Co Ltd filed Critical Beijing SunwayWorld Science and Technology Co Ltd
Priority to CN202310040170.1A priority Critical patent/CN115936017B/en
Publication of CN115936017A publication Critical patent/CN115936017A/en
Application granted granted Critical
Publication of CN115936017B publication Critical patent/CN115936017B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Machine Translation (AREA)

Abstract

The invention provides a main data management method supporting interface multiple languages and data multiple languages, which comprises the following steps: s1: generating interface element translation data and to-be-managed translation main data of each language in a preset multilingual list based on an interface model of a functional module created in a main data management platform and the to-be-managed translation main data; s2: storing the interface element translation data and the translation main data to be managed in data tables of corresponding languages in a preset database to obtain a translation data table of each language in a preset multilingual list; s3: calling a target translation data table corresponding to a target language from a preset database based on a language selection instruction received in a multi-language definition conversion interface to obtain a target language display result; the method is used for realizing the display mode of interface multilingual and data multilingual in the main data system management platform by generating the interface model and the translation data of the main data to be managed under multiple languages in advance, and better meeting the management requirements of the multinational enterprises on the main data.

Description

Main data management method supporting interface multiple languages and data multiple languages
Technical Field
The invention relates to the technical field of data management, in particular to a main data management method supporting interface multiple languages and data multiple languages.
Background
At present, aiming at the main data management requirements of transnational enterprises, the main data is generally required to be managed and maintained in different languages, and taking Chinese and English languages as an example (supporting more language types), one type of requirements is that a certain type of main data only maintains Chinese or English data; the other type of requirement is that some type of main data needs to maintain Chinese and English data at the same time, and the switching of Chinese and English data and the keeping of the same main data coding need to be realized for the same main data.
However, the existing main data management platform supporting interface multilingual and data multilingual supports a default language in most cases, and when a user needs an interface of other languages or a main data display mode, interface elements or main data of the main data management platform are translated in real time through a language selection instruction or a data editing instruction input by the user, so that language conversion of the interface and the data of the main data management platform is time-consuming, low in efficiency and not intelligent enough.
Therefore, the invention provides a main data management method supporting interface multiple languages and data multiple languages.
Disclosure of Invention
The invention provides a main data management method supporting interface multiple languages and data multiple languages, which is used for generating an interface model and translation data of main data to be managed under multiple languages in advance, so that a display mode of the interface multiple languages and the data multiple languages in a main data system management platform is realized, and the management requirements of cross-country enterprises on the main data are better met.
The invention provides a main data management method supporting interface multiple languages and data multiple languages, which comprises the following steps:
s1: generating interface element translation data and to-be-managed translation main data of each language in a preset multilingual list on the basis of an interface model of a functional module created in a main data management platform and the to-be-managed translation main data;
s2: storing the interface element translation data and the translation main data to be managed in data tables of corresponding languages in a preset database to obtain a translation data table of each language in a preset multilingual list;
s3: and calling a target translation data table corresponding to the target language from a preset database based on the language selection instruction received in the multi-language definition conversion interface to obtain a target language display result.
Preferably, the main data management method supporting interface multiple languages and data multiple languages includes, S1: generating interface element translation data and main data to be managed of each language in a preset multilingual list based on an interface model of a functional module created in a main data management platform and the main data to be managed, wherein the interface element translation data and the main data to be managed comprise:
s101: translating interface elements in an interface model of a functional module created by a user on a main data management platform into each language in a preset multilingual list to obtain interface element translation data of each language in the preset multilingual list;
s102: classifying the main data to be managed based on a preset data attribute list to obtain a first part of main data to be managed of each data attribute in a preset multilingual list;
s103: determining a corresponding translation data generation strategy based on the display mode of the main data of each data attribute in different languages;
s104: generating a strategy based on the translation data of each data attribute and the first part of main data to be managed of each data attribute, and generating part of main data to be managed of each data attribute of each language;
s105: and summarizing part of the main data to be managed of all data attributes of each language to obtain the main data to be managed of each language in a preset multi-language list.
Preferably, the main data management method supporting interface multiple languages and data multiple languages, S2: storing the interface element translation data and the main data of the translation to be managed in the data tables of the corresponding languages in the preset database, and obtaining the translation data table of each language in the preset multilingual list, wherein the method comprises the following steps:
s201: storing the interface element translation data in an interface element translation data storage area in a data table of a corresponding language in a preset database, and storing the translation main data to be managed in a translation main data storage area in a data table of a corresponding language in the preset database to obtain an initial storage result;
s202: determining unit translation main data of each unit main data in the main data to be managed under each language from the main data to be managed under all languages;
s203: performing main key association on the unit translation main data of each unit main data in the main data to be managed under each language based on the storage positions of all the unit translation main data of each unit main data in the main data to be managed in the initial storage result to obtain a main key association result;
s204: and obtaining a translation data table of each language in the preset multilingual list based on the primary key association result and the initial storage result.
Preferably, the main data management method supporting interface multiple languages and data multiple languages includes, in S201: storing the interface element translation data in an interface element translation data storage area in a data table of a corresponding language in a preset database, and storing the main data to be managed in a main data storage area in a data table of a corresponding language in the preset database to obtain an initial storage result, wherein the initial storage result comprises:
determining an interface partition strategy of an interface model and a data partition strategy of main data to be managed;
partitioning the interface model based on an interface partitioning strategy to obtain a plurality of partial interface area models, and partitioning the interface element translation data based on the interface partitioning strategy to obtain a plurality of partial interface element translation data of each language;
generating an interface partition index of each partial interface area model based on an interface partition strategy, and storing all partial interface element translation data of each language and the corresponding interface partition index in an interface element translation data storage area in a data table of the corresponding language in a preset database in an associated manner to obtain a first storage result;
storing the translation main data to be managed in a main data storage area to be managed in a data table of a corresponding language in a preset database based on a data partitioning strategy of the main data to be managed, and obtaining a second storage result;
based on the first stored result and the second stored result, an initial stored result is obtained.
Preferably, the method for managing main data supporting interface multiple languages and data multiple languages, which determines an interface partition policy of an interface model and a data partition policy of main data to be managed, includes:
generating an interface element distribution diagram based on all interface elements in the interface model, and determining a plurality of pairs of adjacent interface elements based on the interface element distribution diagram;
determining the co-occurrence frequency of each pair of adjacent interface elements in all partial interface region models in an interface model library, determining the total co-occurrence frequency of all partial interface region models in the interface model library, and determining the co-occurrence preference coefficient of the corresponding pair of adjacent interface elements based on the co-occurrence frequency and the total co-occurrence frequency of the interface elements;
calculating a central coefficient of each interface element based on the co-occurrence preference coefficient of each interface element and all corresponding adjacent interface elements in the interface element distribution diagram;
sorting the center coefficients of all the interface elements in the interface element distribution diagram based on the sequence from big to small to obtain a center coefficient sequence, and taking the interface elements corresponding to all the center coefficients before the first abrupt change point in the center coefficient sequence as the center interface elements;
determining an interface partitioning strategy of the interface model based on the central interface element;
and determining the data partition strategy based on the attribute field of the main data to be managed.
Preferably, the method for managing master data supporting multiple languages of the interface and multiple languages of the data, which determines the interface partition strategy of the interface model based on the central interface element, includes:
randomly dividing all non-central interface elements in the interface element distribution diagram by taking the central interface element as a center to obtain an interface element cluster containing a single central interface element;
calculating a co-occurrence evaluation value of the interface element cluster based on the co-occurrence preference coefficient of each interface element in the interface element cluster and all corresponding adjacent interface elements in the interface element cluster, and calculating a partition evaluation value based on the co-occurrence evaluation values of all the interface element clusters;
judging whether the partition evaluation value is not less than a partition evaluation threshold value, if so, generating an interface partition strategy of the interface model based on the current interface element cluster;
and if not, re-dividing all non-central interface elements in the interface element distribution diagram by taking the central interface element as the center to obtain a new interface element cluster containing a single central interface element, calculating a new partition evaluation value, and generating an interface partition strategy of the interface model based on the newly obtained interface element cluster until the new partition evaluation value is not less than the partition evaluation threshold.
Preferably, the method for managing main data supporting multiple languages of the interface and multiple languages of the data determines the data partitioning policy based on the attribute field of the main data to be managed, and includes:
determining a correlation coefficient between adjacent attribute fields of main data to be managed based on attribute fields contained in all main data sets contained in a main data history management base;
and determining a data partitioning strategy based on the correlation coefficient between the attribute fields of the main data to be managed.
Preferably, the method for managing master data supporting interface multiple languages and data multiple languages includes, based on a data partitioning policy of the master data to be managed, storing the translation master data to be managed in a master data storage area to be managed in a data table of a corresponding language in a preset database, and obtaining a second storage result, where the method includes:
dividing the main data to be managed based on a data partitioning strategy to obtain a plurality of second parts of main data to be managed;
dividing the main data to be managed and translated based on a data partitioning strategy to obtain a plurality of parts of main data to be managed and translated of each language;
and generating a data partition index of each second part of the main data to be managed based on the data partition strategy, and storing all parts of the translation main data to be managed of each language and the corresponding data partition indexes in a main data storage area to be managed in a data table of a corresponding language in a preset database in an associated manner to obtain a second storage result.
Preferably, the main data management method supporting interface multiple languages and data multiple languages comprises, in S3: based on a language selection instruction received in a multi-language definition conversion interface, calling a target translation data table corresponding to a target language from a preset database to obtain a target language display result, wherein the target language display result comprises the following steps:
generating a multi-language conversion window of a multi-language definition conversion interface, and receiving a language selection instruction input by a user at the multi-language conversion window;
calling out a target translation data table corresponding to a target language based on a first target area in an interface model obtained after analyzing a language selection instruction or a target main data set in main data to be managed and the target language;
and importing the target translation data table into a display configuration setting program of the main data management platform to obtain a target language display result.
Preferably, the method for managing main data supporting interface multiple languages and data multiple languages includes, based on a first target area in an interface model obtained after analyzing a language selection instruction or a target main data set and a target language in main data to be managed, retrieving a target translation data table corresponding to the target language, including:
judging whether the analysis language selection instruction is an interface language selection instruction or not, if so, analyzing the language selection instruction to obtain a first target area and a target language in an interface model, generating a target interface partition index based on the first target area, and calling out a target translation data table of the first target area under the corresponding target language from an interface element translation data storage area in a translation data table of the target language in a preset database based on the target interface partition index;
otherwise, analyzing the language selection instruction to obtain a target main data set and a target language in the main data to be managed, generating a target data partition index based on the target main data set, and calling out a target translation data table of the target main data set under the corresponding target language from a target main data to be managed storage area in a translation data table of the target language in a preset database based on the target data partition index.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
The technical solution of the present invention is further described in detail by the accompanying drawings and embodiments.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention and not to limit the invention. In the drawings:
FIG. 1 is a flowchart of a method for managing main data supporting multiple languages of interface and multiple languages of data according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a method for managing master data supporting multiple languages of interface and multiple languages of data according to another embodiment of the present invention;
FIG. 3 is a flowchart of a main data management method supporting multiple languages of interface and multiple languages of data according to another embodiment of the present invention.
Detailed Description
The preferred embodiments of the present invention will be described in conjunction with the accompanying drawings, and it should be understood that they are presented herein only to illustrate and explain the present invention and not to limit the present invention.
Example 1:
the invention provides a main data management method supporting interface multiple languages and data multiple languages, which comprises the following steps with reference to a figure 1:
s1: generating interface element translation data and to-be-managed translation main data of each language in a preset multilingual list based on an interface model of a functional module created in a main data management platform and the to-be-managed translation main data;
s2: storing the interface element translation data and the translation main data to be managed in data tables of corresponding languages in a preset database to obtain a translation data table of each language in a preset multilingual list;
s3: and calling a target translation data table corresponding to the target language from a preset database based on the language selection instruction received in the multi-language definition conversion interface to obtain a target language display result.
In this embodiment, the master data management platform is a platform loaded with an application program for implementing master data management by using the master data management method in this embodiment.
In this embodiment, the functional module is a module (for example, a user management module and a department management module) created by a user in the master data management platform and configured to manage master data of different types or different dimensions, and the functional module is composed of data selection windows of different attribute fields.
In this embodiment, the interface model is an interface model of a functional module in the master data management platform, which performs data interaction with a user (that is, the user selects and calls data in a preset database through data selection windows of different attribute fields in the functional module).
In this embodiment, the master data to be managed is the master data that needs to be subjected to data management by the master data management method, and is generally displayed in a table form.
In this embodiment, the preset multilingual list is a preset list including all kinds of languages available in the interface multilingual and data multilingual function.
In this embodiment, the interface element translation data is translation data (text data) of an interface element in a corresponding language, which is generated in advance based on the interface model and the to-be-managed master data and is used for providing data interaction with a user in the master data management platform for the interface model.
In this embodiment, the to-be-managed translation master data is translation data that is generated in advance based on the interface model and the to-be-managed master data and is used for providing display data in a corresponding language for a user to perform operations such as editing and interaction on the master data.
In this embodiment, the preset database is an SQL database prepared in advance for storing interface element translation data generated in advance and main translation data to be managed.
In this embodiment, the translation data table is a data table for providing multiple interface languages and data languages for the master data management platform, which is obtained after the interface element translation data and the translation master data are stored in the data table of the corresponding language in the preset database.
In this embodiment, the multi-language definition conversion interface is an interface for receiving a language selection instruction input by a user and implementing a language conversion setting for the language of the interface displayed by the main data management platform and the language of the main data.
In this embodiment, the target language display result is a final display result of the language conversion setting obtained by calling a target translation data table corresponding to the target language based on the language conversion instruction received at the multi-language definition conversion interface and importing the called target translation data table into a display configuration setting program of the main data management platform (i.e., a program component which is built in the main data management platform and sets interface configuration for data interaction with a user in the main data management platform).
In this embodiment, the target language is a language type of the interface model or the main data display selected by the user in the language selection instruction.
In this embodiment, the interface multiple languages refer to presenting elements in the interface according to a language selected by a user, for example, a field name in a form and a column in a table, and the interface multiple languages are implemented by a general information system.
In this embodiment, the data multilingual refers to multiple data items in different languages for the same main data, and the language may be selected to perform query and management on the main data.
In the embodiment, in the interface multilingual, translation names in different languages are respectively input aiming at interface elements during model maintenance, so that interfaces in different languages are generated, and corresponding interfaces are displayed according to the language specified by a user;
the data multilingual is that when main data is created, data of each language is stored in tables of different languages respectively, main keys of the same main data in the tables of different languages are the same, and the main data of different languages are related through the main keys.
In this embodiment, the language selection instruction is an instruction input by the user to select a language for displaying different areas in the interface model or part of the main data in the main data to be managed, for example, the language for displaying the main data in the corresponding column about the name of the supplier in the data set to be managed is selected as chinese.
The beneficial effects of the above technology are: the interface model and the translation data table of the main data set under multiple languages are generated in advance, stored in the data table of the corresponding language in the preset database, and the target translation data table of the corresponding target language is called based on the language conversion instruction input by the user and received in the multi-language definition conversion interface, so that the display mode of the interface multi-language and the data multi-language in the main data system management platform is realized, and the management requirement of cross-country enterprises on the main data is better met.
Example 2:
on the basis of the embodiment 1, the main data management method supporting interface multiple languages and data multiple languages comprises the following steps of S1: generating interface element translation data and main data to be managed for each language in a preset multilingual list based on an interface model of a functional module created in a main data management platform and the main data to be managed, with reference to fig. 2, including:
s101: translating interface elements in an interface model of a functional module created by a user on a main data management platform into each language in a preset multilingual list to obtain interface element translation data of each language in the preset multilingual list;
s102: classifying the main data to be managed based on a preset data attribute list to obtain a first part of main data to be managed of each data attribute in a preset multilingual list;
s103: determining a corresponding translation data generation strategy based on the display mode of the main data of each data attribute in different languages;
s104: generating a strategy based on the translation data of each data attribute and the first part of main data to be managed of each data attribute, and generating part of main data to be managed of each data attribute of each language;
s105: and summarizing part of the main data to be managed of all data attributes of each language to obtain the main data to be managed of each language in a preset multi-language list.
In this embodiment, the interface element is a text element that needs to be translated when the user selects a different display language in the interface model.
In this embodiment, the preset data attribute list is a list including preset data attributes, for example, data attributes classified according to display policies of data in different languages:
1. the data dictionary attribute supports different languages, and when the main data is switched among different languages, the data dictionary can be automatically stored and converted in the corresponding language;
2. general attributes whose data, such as vendor names, are maintained in the corresponding languages, respectively;
3. general attributes, when data are consistent under different languages, the data can be automatically synchronized to other languages only by maintaining under one language, for example, digital attributes (height, width and the like) are maintained in an Arabic numeral mode under different languages;
4. and model attributes are referred, and when different main data models have reference relations, the referred models can be automatically switched to the language specified by the reference models for displaying and maintaining (namely when the language type selected by the user for the main data A is A, the display language of the main data table B referred by the main data table A is also set as the language type A).
In this embodiment, the first part of the to-be-managed main data is the main data corresponding to each data attribute obtained by classifying the to-be-managed main data based on the preset data attribute list.
In this embodiment, the display modes of the main data of each data attribute in different languages, for example, are as follows:
1. the data dictionary attribute supports different languages, and when the main data is switched among different languages, the data dictionary can be automatically stored and converted in the corresponding language;
2. general attributes, data of which is maintained in a corresponding language, such as a supplier name;
3. general attributes, when data are consistent under different languages, the data can be automatically synchronized to other languages only by maintaining under one language, for example, digital attributes (height, width and the like) are maintained in an Arabic numeral mode under different languages;
4. and when reference relations exist among different main data models, the referenced models can be automatically switched to the language specified by the reference model for displaying and maintaining.
In this embodiment, the translation data generation policy is a generation manner of partial to-be-managed translation main data of data corresponding to data attributes, which is determined based on display manners of main data of each data attribute in different languages;
for example, the main data of the general attributes is displayed in a language, which is a part of the main data to be managed and translated under all languages, for example: all adopt Arabic numerals mode;
and the main data with the common attributes is translated into each language format in the preset multi-language list to obtain partial main data to be managed and translated in each language.
In this embodiment, the partial to-be-managed translation master data is a translation data table required when each data attribute generated based on the translation data generation policy of each data attribute and the first partial to-be-managed master data of each data attribute is selected to be displayed according to each language.
In this embodiment, the to-be-managed translation master data is complete translated master data obtained by aggregating part of the to-be-managed translation master data of all data attributes in the same language of all data attributes in the to-be-managed master data.
The beneficial effects of the above technology are: the method and the device realize translation of the interface elements in the interface model based on the language types contained in the language catalog to generate corresponding interface element translation data, classify the main data to be managed based on the corresponding display strategies of the main data when different languages are switched, and generate part of the main data to be managed of each data attribute according to the display strategies of each data attribute, thereby realizing generation of the translation data of each language in advance and improving the language switching efficiency.
Example 3:
on the basis of the embodiment 1, the main data management method supporting interface multiple languages and data multiple languages includes that S2: storing the interface element translation data and the main data of the translation to be managed in the data tables of the corresponding languages in the preset database, and obtaining the translation data table of each language in the preset multilingual list, referring to fig. 3, the method includes:
s201: storing the interface element translation data in an interface element translation data storage area in a data table of a corresponding language in a preset database, and storing the translation main data to be managed in a main data storage area to be managed in a data table of a corresponding language in the preset database to obtain an initial storage result;
s202: determining unit translation main data of each unit main data in the main data to be managed under each language from the main data to be managed under all languages;
s203: performing main key association on the unit translation main data of each unit main data in the main data to be managed under each language based on the storage positions of all the unit translation main data of each unit main data in the main data to be managed in the initial storage result to obtain a main key association result;
s204: and obtaining a translation data table of each language in the preset multilingual list based on the primary key association result and the initial storage result.
In this embodiment, the data table is a data table corresponding to each language in the preset database, and interface element translation data and to-be-managed translation main data of the corresponding language are stored in the data table.
In this embodiment, the interface element translation data storage area is a table storage area for storing interface element translation data in a data table in a preset database.
In this embodiment, the translation master data storage area to be managed is a table storage area used for storing the translation master data to be managed in a data table in the preset database.
In this embodiment, the initial storage result is a storage result obtained after the interface element translation data is stored in the interface element translation data storage area in the data table of the corresponding language in the preset database, and the to-be-managed translation main data is stored in the to-be-managed translation main data storage area in the data table of the corresponding language in the preset database.
In this embodiment, the unit main data is the main data of the unit data amount in the main data to be managed.
In this embodiment, the unit translation master data is the translation master data of the unit master data in a single language.
In this embodiment, the unit translation main data of each unit main data in the main data to be managed in each language is subjected to main key association, that is, the main key association is:
and setting the unit translation main data of all languages of the same main data as the same main key, and correspondingly associating the unit translation main data corresponding to each main data in all language data tables in the preset database.
In this embodiment, the primary key association result is a result obtained by performing primary key association on the unit translation main data of each unit main data in each language in the main data to be managed.
In this embodiment, based on the primary key association result and the initial storage result, the translation data table of each language in the preset multilingual list is obtained, that is:
and taking the new data table generated in the initial storage result and the latest data table obtained after the association of the primary key as a translation data table.
The beneficial effects of the above technology are: the main key association is carried out after the unit translation main data of each unit main data in the main data to be managed under each language is stored, and the interface element translation data and the main data to be managed are respectively stored in an interface element translation data storage area and a main data storage area to be managed in a data table of a corresponding language in a preset database, so that the corresponding storage of the translation data is realized, and the corresponding unit translation main data of each main data in translation data tables of all languages in the preset database are correspondingly associated.
Example 4:
on the basis of the embodiment 3, in the main data management method supporting interface multiple languages and data multiple languages, S201: storing the interface element translation data in an interface element translation data storage area in a data table of a corresponding language in a preset database, and storing the main data to be managed in a main data storage area in a data table of a corresponding language in the preset database to obtain an initial storage result, wherein the initial storage result comprises:
determining an interface partition strategy of an interface model and a data partition strategy of main data to be managed;
partitioning the interface model based on an interface partitioning strategy to obtain a plurality of partial interface area models, and partitioning the interface element translation data based on the interface partitioning strategy to obtain a plurality of partial interface element translation data of each language;
generating an interface partition index of each partial interface area model based on an interface partition strategy, and storing all partial interface element translation data of each language and the corresponding interface partition index in an interface element translation data storage area in a data table of the corresponding language in a preset database in an associated manner to obtain a first storage result;
storing the translation main data to be managed in a main data storage area to be managed in a data table of a corresponding language in a preset database based on a data partitioning strategy of the main data to be managed, and obtaining a second storage result;
based on the first stored result and the second stored result, an initial stored result is obtained.
In this embodiment, the interface partitioning policy is a policy for partitioning the interface model.
In this embodiment, the data partitioning policy is a policy for partitioning the main data to be managed.
In this embodiment, the partial interface region model is a partial region in the interface model obtained by performing partition processing on the interface model based on the interface partition policy.
In this embodiment, the partial interface element translation data is partial interface element translation data corresponding to each partial interface region model in the interface element translation data, which is obtained by dividing the interface element translation data based on the interface partition policy.
In this embodiment, the interface partition index is an index of the partial interface area model.
In this embodiment, the first storage result is obtained by associating and storing all part of the interface element translation data of each language with the corresponding interface partition index in the interface element translation data storage area in the data table of the corresponding language in the preset database.
In this embodiment, the second storage result is a storage result obtained after the to-be-managed translation main data is stored in the to-be-managed translation main data storage area in the data table of the corresponding language in the preset database.
The beneficial effects of the above technology are: the interface model and the interface element translation data are synchronously divided based on an interface partition strategy of a standard interface and a data partition strategy of main data to be managed, a plurality of partial interface area models, corresponding interface partition indexes and corresponding partial interface element translation data are obtained, the interface element translation data and the corresponding interface partition indexes are further stored in an interface element translation data storage area in a data table of a corresponding language in a preset database in an associated mode, the main data to be managed are stored in a main data storage area to be managed in a data table of a corresponding language in the preset database, the interface element translation data and the main data to be managed are stored in an associated mode, and therefore the target translation table can be selectively called based on a language selection instruction input by a user.
Example 5:
on the basis of the embodiment 4, the method for managing the main data supporting the interface multiple languages and the data multiple languages determines an interface partition strategy of an interface model and a data partition strategy of the main data to be managed, and comprises the following steps:
generating an interface element distribution diagram based on all interface elements in the interface model, and determining a plurality of pairs of adjacent interface elements based on the interface element distribution diagram;
determining the co-occurrence frequency of each pair of adjacent interface elements in all partial interface region models in an interface model library, determining the total co-occurrence frequency of all partial interface region models in the interface model library, and determining the co-occurrence preference coefficient of the corresponding pair of adjacent interface elements based on the co-occurrence frequency and the total co-occurrence frequency of the interface elements;
calculating a central coefficient of each interface element based on the co-occurrence mass preference coefficients of each interface element and all corresponding adjacent interface elements in the interface element distribution diagram;
sorting the center coefficients of all the interface elements in the interface element distribution diagram based on the sequence from big to small to obtain a center coefficient sequence, and taking the interface elements corresponding to all the center coefficients before the first abrupt change point in the center coefficient sequence as the center interface elements;
determining an interface partitioning strategy of the interface model based on the central interface element;
and determining the data partition strategy based on the attribute field of the main data to be managed.
In this embodiment, the interface element distribution map is a distribution map including positions of all interface elements in the interface model.
In this embodiment, the adjacent interface element pair is an interface element pair having an adjacent position relationship in the interface element distribution diagram.
In this embodiment, the interface model library is a database for storing all partitioned interface models.
In this embodiment, the co-occurrence frequency is the frequency of co-occurrence of adjacent interface element pairs in all partial interface region models in the interface model library, and when the adjacent interface element pairs simultaneously occur in a certain partial interface region model in the interface model library, the co-occurrence frequency is once.
In this embodiment, the total number of co-occurrence interface elements is the total number of co-occurrence of all interface element pairs in all partial interface region models in the interface model library, which is the factorial of the total number of all interface elements in the interface model library.
In this embodiment, the co-occurrence preference coefficient is a numerical value representing the co-occurrence degree of the corresponding adjacent interface element pair in all the interface region models in the interface model library.
In this embodiment, the co-occurrence preference coefficient of the corresponding adjacent interface element pair is determined based on the co-occurrence frequency and the total co-occurrence interface element frequency, and is: and taking the ratio of the co-occurrence times to the total co-occurrence interface element times as a co-occurrence preference coefficient of the corresponding adjacent interface element pair.
In this embodiment, based on the co-occurrence preference coefficient of each interface element and all corresponding adjacent interface elements in the interface element distribution diagram, the center coefficient of the corresponding interface element is calculated, that is:
and taking the average value of the co-occurrence preference coefficients of each interface element and all corresponding adjacent interface elements as the center coefficient of the corresponding interface element.
In this embodiment, the center coefficient sequence is a sequence obtained by sorting the center coefficients of all the interface elements in the interface element distribution diagram based on the descending order.
In this embodiment, the central interface element is the interface element corresponding to all central coefficients before the first abrupt change point in the central coefficient sequence.
The beneficial effects of the above technology are: the central coefficient of the interface element is determined by determining the co-occurrence preference coefficient of the adjacent interface elements in the interface model to all partial interface region models in the interface model library, and the central interface element is screened out by screening the central coefficient sequence generated based on the central coefficient, so that the interface element positioned at the center in the partial interface region model with the preference division mode is determined based on the co-occurrence frequency of the interface element and the corresponding adjacent interface element in the interface model library, an important basis is provided for subsequently determining an interface division strategy, and the data division strategy is determined based on the attribute field of the main data to be managed.
Example 6:
on the basis of the embodiment 5, the main data management method supporting interface multiple languages and data multiple languages determines an interface partition strategy of an interface model based on a central interface element, and comprises the following steps:
randomly dividing all non-central interface elements in the interface element distribution diagram by taking the central interface element as a center to obtain an interface element cluster containing a single central interface element;
calculating a co-occurrence evaluation value of the interface element cluster based on the co-occurrence preference coefficient of each interface element in the interface element cluster and all corresponding adjacent interface elements in the interface element cluster, and calculating a partition evaluation value based on the co-occurrence evaluation values of all the interface element clusters;
judging whether the partition evaluation value is not less than a partition evaluation threshold value, if so, generating an interface partition strategy of the interface model based on the current interface element cluster;
and if not, re-dividing all non-central interface elements in the interface element distribution diagram by taking the central interface element as the center to obtain a new interface element cluster containing a single central interface element, calculating a new partition evaluation value, and generating an interface partition strategy of the interface model based on the newly obtained interface element cluster until the new partition evaluation value is not less than the partition evaluation threshold.
In this embodiment, the interface element cluster is a cluster that is obtained by randomly dividing all non-central interface elements in the interface element distribution map by taking the central interface element as a center and includes a single central interface element and at least one other non-central interface element.
In this embodiment, the non-center interface element is the remaining interface element except the center interface element in the interface element distribution diagram.
In this embodiment, calculating a co-occurrence evaluation value of an interface element cluster based on a co-occurrence preference coefficient of each interface element in the interface element cluster and all corresponding adjacent interface elements in the interface element cluster includes:
Figure BDA0004050597510000171
in the formula, P gx The co-occurrence evaluation value of the interface element cluster is shown, i is the ith interface element in the interface element cluster, n is the total number of the interface elements in the interface element cluster, j is the total number of the interface elements in the interface element cluster i For the j adjacent interface element m of the ith interface element in the interface element cluster i The total number of adjacent interface elements in the interface element cluster, alpha, of the ith interface element in the interface element cluster gx Co-occurrence preference coefficients for the ith interface element in the interface element cluster and the jth adjacent interface element in the interface element cluster;
based on the formula, the co-occurrence evaluation value of the interface element cluster, which represents the co-occurrence degree of all interface elements in the interface element cluster, in all interface area models in the interface model library can be accurately calculated.
In this embodiment, calculating the partition evaluation value based on the common evaluation values of all the interface element clusters includes:
Figure BDA0004050597510000181
in the formula, P fq As partition evaluation value, q is interface element clusterP is the P-th interface element cluster, P gx·p The common evaluation value is the p interface element cluster;
based on the formula, the partition evaluation value representing the dividing goodness of all current interface element clusters can be accurately calculated.
In this embodiment, the partition evaluation threshold is a preset judgment threshold used for judging whether the partition of the interface model based on the currently obtained multiple interface element clusters meets the requirement.
In this embodiment, the interface partitioning policy for generating the interface model based on the current interface element cluster is:
and taking a partial interface area model containing all interface elements in a single interface element cluster in the interface model as a partial interface area model, and further taking the partition mode as an interface partition strategy.
In this embodiment, the new interface element cluster is an interface element cluster including a single central interface element, which is obtained by repartitioning all non-central interface elements in the interface element distribution map with the central interface element as the center.
In this embodiment, the new partition evaluation value is the partition evaluation value calculated based on the new interface element cluster.
The beneficial effects of the above technology are: all non-central interface elements in the interface element distribution diagram are divided through the determined central interface element, partition evaluation values corresponding to the interface element division results are calculated through calculating the common evaluation values of the interface element clusters obtained after division, and partition cut-off judgment thresholds for all the non-central interface elements are set in combination with preset partition evaluation thresholds, so that the interface partition strategy is determined through the partition evaluation values calculated based on the common occurrence preference coefficients of each interface element in the interface element clusters and all the corresponding adjacent interface elements in the interface element clusters.
Example 7:
on the basis of embodiment 5, the method for managing master data supporting multiple languages of the interface and multiple languages of the data determines a data partitioning policy based on an attribute field of master data to be managed, and includes:
determining a correlation coefficient between adjacent attribute fields of main data to be managed based on attribute fields contained in all main data sets contained in a main data history management base;
and determining a data partitioning strategy based on the correlation coefficient between the attribute fields of the main data to be managed.
In this embodiment, the master data history management library is a database for storing history management conditions of master data (i.e., history data obtained by partitioning a master data set to be managed).
In this embodiment, the master data set is a set of master data obtained by partitioning the master data set to be managed, which is stored in the master data history management library.
In this embodiment, the attribute field is an attribute field of data in the master data set, for example: supplier name, product price, etc.
In this embodiment, based on the attribute fields included in all the main data sets included in the main data history management library, the correlation coefficient between adjacent attribute fields of the main data to be managed is determined, that is, the correlation coefficient is:
determining all adjacent attribute fields of the main data to be managed in all main data sets contained in the main data history management library and the frequency of common occurrence of each adjacent attribute field;
and taking the ratio of the co-occurrence times of the attribute field of the main data to be managed and the corresponding adjacent attribute field to the total occurrence times of the corresponding attribute field in all main data sets contained in the main data history management base as a correlation coefficient between the adjacent attribute fields, and further accurately determining the correlation coefficient between the adjacent attribute fields of the main data to be managed based on the history division condition in the history management base.
In this embodiment, based on the correlation coefficient between the attribute fields of the main data to be managed, the data partitioning policy is determined, that is:
sorting the correlation coefficients from small to large to obtain a correlation coefficient sequence, and taking adjacent attribute fields corresponding to all correlation coefficients before a first abrupt change point in the correlation coefficient sequence as attribute field groups to be divided;
and taking the boundary between the attribute field groups to be divided as a partition boundary of the main data to be managed, dividing the main data to be managed based on the partition boundary, taking the partition method as a corresponding data partition strategy, and further determining the data partition strategy of the main data to be managed based on the historical division condition in the historical management library.
The beneficial effects of the above technology are: the method and the device realize that the correlation coefficient among the attribute fields of the main data to be managed is determined based on the attribute fields contained in all the main data sets contained in the main data history management base, and the data partitioning strategy is determined based on the correlation coefficient among the attribute fields of the main data to be managed.
Example 8:
on the basis of embodiment 5, the method for managing master data supporting interface multiple languages and data multiple languages includes, based on a data partitioning policy of master data to be managed, storing the master data to be managed for translation in a master data storage area to be managed in a data table of a corresponding language in a preset database, and obtaining a second storage result, including:
dividing the main data to be managed based on a data partitioning strategy to obtain a plurality of second parts of main data to be managed;
dividing the main data to be managed and translated based on a data partitioning strategy to obtain a plurality of parts of main data to be managed and translated of each language;
and generating a data partition index of each second part of main data to be managed based on the data partition strategy, associating all parts of main data to be managed of each language with the corresponding data partition indexes, and storing the associated main data to be managed and translated in a main data storage area to be managed in a data table of the corresponding language in a preset database to obtain a second storage result.
In this embodiment, the second part of the master data to be managed is a set formed by master data obtained by dividing the master data to be managed based on a data partitioning policy.
In this embodiment, part of the translation master data to be managed is a part of the translation master data to be managed obtained after the translation master data to be managed is divided based on the data partitioning policy.
In this embodiment, the data partition index is an index of the second part of the main data to be managed, and is also an index for providing a search basis for the partial translation main data to be managed of the second part of the main data to be managed.
The beneficial effects of the above technology are: the method and the device realize synchronous division of the main data to be managed and the main translation data to be managed based on the data partition strategy, associate the main data to be managed and the main translation data to be managed with the corresponding data partition indexes and store the main data to be managed in the main data storage area of the translation data to be managed in the data table of the corresponding language in the preset database, and realize division and storage of the main data to be managed.
Example 9:
on the basis of the embodiment 8, the main data management method supporting interface multiple languages and data multiple languages includes, by the steps of S3: based on a language selection instruction received in a multi-language definition conversion interface, calling a target translation data table corresponding to a target language from a preset database to obtain a target language display result, wherein the target language display result comprises the following steps:
generating a multi-language conversion window of a multi-language definition conversion interface, and receiving a language selection instruction input by a user at the multi-language conversion window;
calling out a target translation data table corresponding to a target language based on a first target area in an interface model obtained after analyzing a language selection instruction or a target main data set in main data to be managed and the target language;
and importing the target translation data table into a display configuration setting program of the main data management platform to obtain a target language display result.
In this embodiment, the multilingual conversion window is a window provided in the multilingual definition conversion interface for receiving a language selection instruction input by a user.
In this embodiment, the first target area is an interface area that is determined after the language selection instruction is parsed and that is displayed in a certain language selected by the user in the interface model.
In this embodiment, the target master data set is a set formed by master data displayed in a certain language selected by a user from the master data to be managed, which is determined after the language selection instruction is analyzed.
In this embodiment, the target language is a target language obtained by converting the user-selected core language of the interface model or a part of the main data set in the main data to be managed, after the language selection instruction is parsed.
In this embodiment, the target translation data table is a translation data table that is used for displaying the first target area or the target main data set according to the target language and is obtained based on the target main data set in the first target area or the main data to be managed in the interface model obtained after the language analysis selection instruction and the target language call.
In this embodiment, the display configuration setting program is a program component that is built in the master data management platform and is used for setting the display configuration of the master data management platform.
The beneficial effects of the above technology are: the method comprises the steps of determining a first target area in an interface model or a target main data set and a target language in main data to be managed based on a language selection instruction input by a user and received by a multi-language conversion window in a multi-language definition conversion interface, calling out a corresponding target translation data table, and then importing the target translation data table into a display configuration setting program of a main data management platform, so that efficient setting display of the interface language and the data language of the main data management platform is realized.
Example 10:
on the basis of embodiment 9, the method for managing main data supporting multiple languages of the interface and multiple languages of the data calls a target translation data table corresponding to a target language based on a first target area in an interface model obtained after a language selection instruction is analyzed or a target main data set and the target language in main data to be managed, and includes:
judging whether the analysis language selection instruction is an interface language selection instruction or not, if so, analyzing the language selection instruction to obtain a first target area and a target language in an interface model, generating a target interface partition index based on the first target area, and calling out a target translation data table of the first target area under the corresponding target language from an interface element translation data storage area in a translation data table of the target language in a preset database based on the target interface partition index;
otherwise, analyzing the language selection instruction to obtain a target main data set and a target language in the main data to be managed, generating a target data partition index based on the target main data set, and calling out a target translation data table of the target main data set under the corresponding target language from a target translation main data storage area in a translation data table of the target language in a preset database based on the target data partition index.
In this embodiment, the interface language selection instruction is an instruction for selecting a display language of a partial region in the interface model.
In this embodiment, the target interface partition index is an index used for retrieving a target translation data table corresponding to the first target region from a target to-be-managed translation main data storage region in a translation data table of a target language in a preset database.
In this embodiment, the target data partition index is an index used for retrieving a target translation data table corresponding to the target main data set from a target to-be-managed translation main data storage area in a translation data table of a target language in a preset database.
The beneficial effects of the above technology are: and respectively analyzing a first target area in the interface model or a target main data set and a target language in main data to be managed based on the type of the language selection instruction, generating a corresponding target interface partition index or a corresponding target data partition index, and calling a target translation data table of the first target area under the corresponding target language or a target translation data table of the target main data set under the corresponding target language from a translation data table of a target conversion language in a preset database based on the target interface partition index or the target data partition index.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims (10)

1. A master data management method supporting interface multiple languages and data multiple languages is characterized by comprising the following steps:
s1: generating interface element translation data and to-be-managed translation main data of each language in a preset multilingual list on the basis of an interface model of a functional module created in a main data management platform and the to-be-managed translation main data;
s2: storing the interface element translation data and the translation main data to be managed in data tables of corresponding languages in a preset database to obtain a translation data table of each language in a preset multilingual list;
s3: and calling a target translation data table corresponding to the target language from a preset database based on the language selection instruction received in the multi-language definition conversion interface to obtain a target language display result.
2. The master data management method supporting interface multiple languages and data multiple languages according to claim 1, wherein S1: generating interface element translation data and to-be-managed translation main data of each language in a preset multilingual list based on an interface model of a functional module created in a main data management platform and the to-be-managed translation main data, and the method comprises the following steps of:
s101: translating interface elements in an interface model of a functional module created by a user on a main data management platform into each language in a preset multilingual list to obtain interface element translation data of each language in the preset multilingual list;
s102: classifying the main data to be managed based on a preset data attribute list to obtain a first part of main data to be managed of each data attribute in a preset multi-language list;
s103: determining a corresponding translation data generation strategy based on the display mode of the main data of each data attribute in different languages;
s104: generating a strategy based on the translation data of each data attribute and the first part of main data to be managed of each data attribute, and generating part of main data to be managed of each data attribute of each language;
s105: and summarizing part of the main data to be managed of all data attributes of each language to obtain the main data to be managed of each language in a preset multi-language list.
3. The master data management method supporting interface multiple languages and data multiple languages according to claim 1, wherein S2: storing the interface element translation data and the main data of the translation to be managed in data tables of corresponding languages in a preset database to obtain a translation data table of each language in a preset multilingual list, wherein the method comprises the following steps:
s201: storing the interface element translation data in an interface element translation data storage area in a data table of a corresponding language in a preset database, and storing the translation main data to be managed in a main data storage area to be managed in a data table of a corresponding language in the preset database to obtain an initial storage result;
s202: determining unit translation main data of each unit main data in the main data to be managed under each language from the main data to be managed under all languages;
s203: performing main key association on the unit translation main data of each unit main data in the main data to be managed under each language based on the storage positions of all the unit translation main data of each unit main data in the main data to be managed in the initial storage result to obtain a main key association result;
s204: and obtaining a translation data table of each language in the preset multilingual list based on the primary key association result and the initial storage result.
4. The master data management method supporting interface multiple languages and data multiple languages according to claim 3, wherein S201: storing the interface element translation data in an interface element translation data storage area in a data table of a corresponding language in a preset database, and storing the main data to be managed in a main data storage area in a data table of a corresponding language in the preset database to obtain an initial storage result, wherein the initial storage result comprises:
determining an interface partition strategy of an interface model and a data partition strategy of main data to be managed;
partitioning the interface model based on an interface partitioning strategy to obtain a plurality of partial interface area models, and partitioning the interface element translation data based on the interface partitioning strategy to obtain a plurality of partial interface element translation data of each language;
generating an interface partition index of each partial interface area model based on an interface partition strategy, and storing all partial interface element translation data of each language and the corresponding interface partition index in an interface element translation data storage area in a data table of the corresponding language in a preset database in an associated manner to obtain a first storage result;
storing the translation main data to be managed in a main data storage area to be managed in a data table of a corresponding language in a preset database based on a data partitioning strategy of the main data to be managed, and obtaining a second storage result;
based on the first stored result and the second stored result, an initial stored result is obtained.
5. The method for managing the main data supporting the interface multiple languages and the data multiple languages according to claim 4, wherein the determining of the interface partition policy of the interface model and the data partition policy of the main data to be managed comprises:
generating an interface element distribution diagram based on all interface elements in the interface model, and determining a plurality of pairs of adjacent interface elements based on the interface element distribution diagram;
determining the co-occurrence frequency of each pair of adjacent interface elements in all partial interface region models in an interface model library, determining the total co-occurrence frequency of all partial interface region models in the interface model library, and determining the co-occurrence preference coefficient of the corresponding pair of adjacent interface elements based on the co-occurrence frequency and the total co-occurrence frequency of the interface elements;
calculating a central coefficient of each interface element based on the co-occurrence preference coefficient of each interface element and all corresponding adjacent interface elements in the interface element distribution diagram;
sorting the center coefficients of all the interface elements in the interface element distribution diagram based on the sequence from big to small to obtain a center coefficient sequence, and taking the interface elements corresponding to all the center coefficients before the first abrupt change point in the center coefficient sequence as the center interface elements;
determining an interface partitioning strategy of the interface model based on the central interface element;
and determining the data partition strategy based on the attribute field of the main data to be managed.
6. The method for master data management supporting multiple languages of interface and multiple languages of data according to claim 5, wherein determining the interface partitioning policy of the interface model based on the central interface element comprises:
randomly dividing all non-central interface elements in the interface element distribution diagram by taking the central interface element as a center to obtain an interface element cluster containing a single central interface element;
calculating a co-occurrence evaluation value of the interface element cluster based on the co-occurrence preference coefficient of each interface element in the interface element cluster and all corresponding adjacent interface elements in the interface element cluster, and calculating a partition evaluation value based on the co-occurrence evaluation values of all the interface element clusters;
judging whether the partition evaluation value is not less than a partition evaluation threshold value, if so, generating an interface partition strategy of the interface model based on the current interface element cluster;
and if not, re-dividing all non-central interface elements in the interface element distribution diagram by taking the central interface element as the center to obtain a new interface element cluster containing a single central interface element, calculating a new partition evaluation value, and generating an interface partition strategy of the interface model based on the newly obtained interface element cluster until the new partition evaluation value is not less than the partition evaluation threshold.
7. The method for managing the main data supporting multiple languages of the interface and multiple languages of the data according to claim 5, wherein the determining of the data partitioning policy based on the attribute field of the main data to be managed comprises:
determining a correlation coefficient between adjacent attribute fields of main data to be managed based on attribute fields contained in all main data sets contained in a main data history management base;
and determining a data partitioning strategy based on the correlation coefficient between the attribute fields of the main data to be managed.
8. The method for managing the main data supporting multiple languages of the interface and the multiple languages of the data according to claim 5, wherein the method for managing the main data of the translation to be managed stores the main data of the translation to be managed in a main data storage area to be managed in a data table of a corresponding language in a preset database based on a data partitioning policy of the main data to be managed, and obtains a second storage result, comprising:
dividing the main data to be managed based on a data partitioning strategy to obtain a plurality of second parts of main data to be managed;
dividing the translation master data to be managed based on a data partitioning strategy to obtain a plurality of parts of translation master data to be managed of each language;
and generating a data partition index of each second part of main data to be managed based on the data partition strategy, associating all parts of main data to be managed of each language with the corresponding data partition indexes, and storing the associated main data to be managed and translated in a main data storage area to be managed in a data table of the corresponding language in a preset database to obtain a second storage result.
9. The master data management method supporting interface multiple languages and data multiple languages according to claim 8, wherein S3: based on a language selection instruction received in a multi-language definition conversion interface, calling a target translation data table corresponding to a target language from a preset database to obtain a target language display result, wherein the target language display result comprises the following steps:
generating a multi-language conversion window of a multi-language definition conversion interface, and receiving a language selection instruction input by a user in the multi-language conversion window;
calling out a target translation data table corresponding to a target language based on a first target area in an interface model obtained after analyzing a language selection instruction or a target main data set in main data to be managed and the target language;
and importing the target translation data table into a display configuration setting program of the main data management platform to obtain a target language display result.
10. The method according to claim 9, wherein the retrieving the target translation data table corresponding to the target language based on the target language and the target main data set in the interface model or the target main data set in the main data to be managed obtained after parsing the language selection command comprises:
judging whether the analysis language selection instruction is an interface language selection instruction or not, if so, analyzing the language selection instruction to obtain a first target area and a target language in an interface model, generating a target interface partition index based on the first target area, and calling out a target translation data table of the first target area under the corresponding target language from an interface element translation data storage area in a translation data table of the target language in a preset database based on the target interface partition index;
otherwise, analyzing the language selection instruction to obtain a target main data set and a target language in the main data to be managed, generating a target data partition index based on the target main data set, and calling out a target translation data table of the target main data set under the corresponding target language from a target main data to be managed storage area in a translation data table of the target language in a preset database based on the target data partition index.
CN202310040170.1A 2023-01-12 2023-01-12 Main data management method supporting interface multilingual and data multilingual Active CN115936017B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310040170.1A CN115936017B (en) 2023-01-12 2023-01-12 Main data management method supporting interface multilingual and data multilingual

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310040170.1A CN115936017B (en) 2023-01-12 2023-01-12 Main data management method supporting interface multilingual and data multilingual

Publications (2)

Publication Number Publication Date
CN115936017A true CN115936017A (en) 2023-04-07
CN115936017B CN115936017B (en) 2023-07-25

Family

ID=86557784

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310040170.1A Active CN115936017B (en) 2023-01-12 2023-01-12 Main data management method supporting interface multilingual and data multilingual

Country Status (1)

Country Link
CN (1) CN115936017B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117711593A (en) * 2024-02-05 2024-03-15 苏州绿华科技有限公司 Intelligent pharmacy medicine inlet and outlet management system

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050137845A1 (en) * 2003-12-23 2005-06-23 Carroll Timothy J. Method and structures to enable national language support for dynamic data
CN102880602A (en) * 2012-10-12 2013-01-16 国电南瑞科技股份有限公司 Multi-language dynamic switching method in substation monitoring system
CN105138350A (en) * 2015-07-29 2015-12-09 北京四方继保自动化股份有限公司 International multi-language implement method of configuration software
CN111324597A (en) * 2020-03-19 2020-06-23 北京三维天地科技股份有限公司 Main data management method and system
CN112328348A (en) * 2020-11-05 2021-02-05 深圳壹账通智能科技有限公司 Application program multi-language support method and device, computer equipment and storage medium
CN114416107A (en) * 2022-01-26 2022-04-29 湖南快乐阳光互动娱乐传媒有限公司 Method, device, storage medium and equipment for translating logic

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050137845A1 (en) * 2003-12-23 2005-06-23 Carroll Timothy J. Method and structures to enable national language support for dynamic data
CN102880602A (en) * 2012-10-12 2013-01-16 国电南瑞科技股份有限公司 Multi-language dynamic switching method in substation monitoring system
CN105138350A (en) * 2015-07-29 2015-12-09 北京四方继保自动化股份有限公司 International multi-language implement method of configuration software
CN111324597A (en) * 2020-03-19 2020-06-23 北京三维天地科技股份有限公司 Main data management method and system
CN112328348A (en) * 2020-11-05 2021-02-05 深圳壹账通智能科技有限公司 Application program multi-language support method and device, computer equipment and storage medium
CN114416107A (en) * 2022-01-26 2022-04-29 湖南快乐阳光互动娱乐传媒有限公司 Method, device, storage medium and equipment for translating logic

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117711593A (en) * 2024-02-05 2024-03-15 苏州绿华科技有限公司 Intelligent pharmacy medicine inlet and outlet management system
CN117711593B (en) * 2024-02-05 2024-04-19 苏州绿华科技有限公司 Intelligent pharmacy medicine inlet and outlet management system

Also Published As

Publication number Publication date
CN115936017B (en) 2023-07-25

Similar Documents

Publication Publication Date Title
CN110292775B (en) Method and device for acquiring difference data
US6681218B1 (en) System for managing RDBM fragmentations
US6708166B1 (en) Method and apparatus for storing data as objects, constructing customized data retrieval and data processing requests, and performing householding queries
US5442784A (en) Data management system for building a database with multi-dimensional search tree nodes
CN111339421A (en) Information search method, device, equipment and storage medium based on cloud technology
US20020133476A1 (en) Database system
US20030212960A1 (en) Computer-implemented system and method for report generation
US20080228783A1 (en) Data Partitioning Systems
US9129010B2 (en) System and method of partitioned lexicographic search
CN108664509A (en) A kind of method, apparatus and server of extemporaneous inquiry
CN115936017B (en) Main data management method supporting interface multilingual and data multilingual
US8290950B2 (en) Identifying locale-specific data based on a total ordering of supported locales
US20070100876A1 (en) Methods, systems and computer program products for segmented presentation of service order status information
CN110874366A (en) Data processing and query method and device
CN114385679A (en) Meter structure inspection method, meter structure inspection device and electronic equipment
US6269359B1 (en) Relational data base system and method for rapidly realizing a query to a database
US20080148220A1 (en) System infrastructure structure formulation supporting system and supporting method
KR20020089677A (en) Method for classifying a document automatically and system for the performing the same
CN111309704B (en) Database operation method and database operation system
US8171006B1 (en) Retrieval of searchable and non-searchable attributes
CN106776704A (en) Statistical information collection method and device
CN111159991A (en) Report modeling design device and method
CN115438236B (en) Unified hybrid search method and system
US11615237B2 (en) Processing method for presenting indicator hierarchy and classification of data in spreadsheet
KR102374287B1 (en) Method for generating test data, apparatus for the same, computer program for the same, and recording medium storing computer program thereof

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