Disclosure of Invention
The embodiment of the application provides a method, a device, equipment and a medium for updating metadata, which are used for improving the accuracy of updating metadata.
In a first aspect, the present application provides a method of updating metadata, the method comprising a server receiving a request from a terminal to update metadata, the request to update metadata comprising attribute information of the metadata. And determining the data type of the metadata, and determining the attribute to be verified of the metadata according to the corresponding relation between the configured data type and the attribute to be verified. And sequentially verifying the attribute values of the attribute to be verified according to the attribute standard rule, wherein when the attribute values in the attribute to be verified do not meet the attribute standard rule, the attribute values which do not meet the attribute standard rule are changed into default values. Standard metadata of the metadata is generated according to attribute information of the metadata. The standard metadata is transmitted to the terminal. And updating the standard metadata according to the acquired updating indication information.
By adopting the method, the attribute to be verified of the metadata can be determined according to the data type of the metadata, so that verification of all the attributes of the metadata is avoided, and the efficiency of verifying the attributes of the metadata is improved to improve the efficiency of updating the metadata. Further, the attribute is verified according to the attribute standard rule corresponding to the attribute to be verified, so that accuracy of verifying whether the attribute meets requirements can be improved. And generating standard metadata according to the attribute information of the metadata and updating the standard metadata, so that maintainability of the subsequent metadata can be ensured.
In one possible embodiment, the attribute information of the metadata includes a definition field name, length, whether to fill, data type, description value, constraint, default value.
In one possible embodiment, the update indication information is sent to the server according to a preset period. Or the update instruction information is sent to the server according to the instruction of the user.
By adopting the design, the update indication information is sent to the server in different modes, so that the flexibility of updating metadata can be improved.
In one possible embodiment, before updating the standard metadata according to the acquired update indication information, the method further comprises determining a database for storing the standard metadata, and performing data format conversion on the standard metadata according to the corresponding relation between the database type and the data format.
By adopting the design, the data of the standard metadata are converted according to the type of the database of the standard metadata, and the standard metadata after data conversion meet the format of the database, so that the standard metadata are stored in multiple types of databases, and the compatibility of the system is improved.
In a second aspect, the present application provides an apparatus for updating metadata, the apparatus comprising a communication module for receiving a request from a terminal to update metadata, the request to update metadata comprising attribute information of the metadata. And the processing module is used for determining the data type of the metadata and determining the attribute to be verified of the metadata according to the corresponding relation between the configured data type and the attribute to be verified. And the processing module is also used for sequentially verifying the attribute values of the attribute to be verified according to the attribute standard rule, wherein when the attribute values in the attribute to be verified do not meet the attribute standard rule, the attribute values which do not meet the attribute standard rule are changed into default values. The processing module is also used for generating standard metadata of the metadata according to the attribute information of the metadata. The communication module is further configured to send the standard metadata to the terminal. The processing module is further used for updating the standard metadata according to the acquired updating indication information.
In one possible embodiment, the attribute information of the metadata includes a definition field name, a length, whether to fill, a data type, a description value, a constraint, a default value.
In a possible embodiment, the update indication information is sent to the server according to a preset period. Or the update instruction information is transmitted to the server according to the instruction of the user.
In a possible embodiment, before the standard metadata is updated according to the acquired update indication information, the processing module is further configured to determine a database storing the standard metadata, and perform data format conversion on the standard metadata according to a correspondence between a database type and a data format.
In a third aspect, the present application provides an electronic device comprising:
A memory for storing program instructions;
A processor for invoking program instructions stored in the memory and executing the steps comprised by the method according to any of the first aspects in accordance with the obtained program instructions.
In a fourth aspect, the present application provides a computer readable storage medium storing a computer program comprising program instructions which, when executed by a computer, cause the computer to perform the method of any one of the first aspects.
In a fifth aspect, the present application provides a computer program product comprising computer program code which, when run on a computer, causes the computer to perform the method of any of the first aspects.
The technical effects of the second aspect to the fifth aspect and any one of the designs thereof may be referred to as the technical effects of the corresponding designs in the first aspect, and will not be described herein.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application. Embodiments of the application and features of the embodiments may be combined with one another arbitrarily without conflict. Also, while a logical order of illustration is depicted in the flowchart, in some cases the steps shown or described may be performed in a different order than presented.
The terms first and second in the description and claims of the application and in the above-mentioned figures are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the term "include" and any variations thereof is intended to cover non-exclusive protection. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus. The term "plurality" in the present application may mean at least two, for example, two, three or more, and embodiments of the present application are not limited.
In the technical scheme of the application, the data is collected, transmitted, used and the like, and all meet the requirements of national relevant laws and regulations.
Before describing the method for updating metadata provided by the embodiment of the present application, for convenience of understanding, the following detailed description is first provided for the technical background of the embodiment of the present application.
How to update metadata is a key point in constructing a data normalization system. In the prior art, a scheme of updating metadata generally determines attribute information of metadata corresponding to a service manually according to the service information. For example, a technician may write metadata corresponding to the service information and attribute information of the metadata in an excel file according to the service information, and import the written excel file in a corresponding service system, so as to implement maintenance of the metadata. Or the technician directly adds, deletes or changes the metadata and the attribute information of the metadata in the service system, thereby realizing the update of the metadata. That is, in the existing technical solutions for updating metadata, the metadata is usually updated manually.
However, the scheme of manually updating metadata has the problems of low efficiency, large uncertainty, incapability of updating metadata in real time and the like, and needs to be improved.
In order to solve the above-mentioned drawbacks, embodiments of the present application provide a method, apparatus, device, and medium for updating metadata, which are used to improve the efficiency and accuracy of updating metadata.
In the application, the method comprises the steps that a server receives a request for updating metadata from a terminal, wherein the request for updating the metadata comprises attribute information of the metadata. And determining the data type of the metadata, and determining the attribute to be verified of the metadata according to the corresponding relation between the configured data type and the attribute to be verified. And sequentially verifying the attribute values of the attribute to be verified according to the attribute standard rule, wherein when the attribute values in the attribute to be verified do not meet the attribute standard rule, the attribute values which do not meet the attribute standard rule are changed into default values. Standard metadata of the metadata is generated according to attribute information of the metadata. The standard metadata is transmitted to the terminal. And updating the standard metadata according to the acquired updating indication information.
By adopting the method, the attribute to be verified of the metadata can be determined according to the data type of the metadata, so that verification of all the attributes of the metadata is avoided, and the efficiency of verifying the attributes of the metadata is improved to improve the efficiency of updating the metadata. Further, the attribute is verified according to the attribute standard rule corresponding to the attribute to be verified, so that accuracy of verifying whether the attribute meets requirements can be improved. And generating standard metadata according to the attribute information of the metadata and updating the standard metadata, so that maintainability of the subsequent metadata can be ensured.
In addition, the main body for performing the method of the present application may be a server, or may be a processing device, such as a processor or a processing module, in a computer system for performing the method of the present application, and the present application is not particularly limited.
Fig. 1 is a flowchart of a method for updating metadata according to an embodiment of the present invention. Taking the server and the terminal as an execution main body as an example, the process can include the following steps:
S101, the terminal sends a request for updating metadata to the server. Accordingly, the server receives a request from the terminal to update metadata. Wherein the request for updating the metadata includes attribute information of the metadata.
As one example, a user may trigger a terminal to send a request to update metadata to a server via an input device (e.g., keyboard, touch screen, etc.). Alternatively, the attribute information of the metadata included in the request for updating the metadata may include at least one of a definition field name of the metadata, a length of the metadata, whether the metadata is a padding item, a data type of the metadata, a description value of the metadata, a constraint condition of the metadata, and a default value of the metadata. It is understood that the attribute information of the metadata may also include other attribute information, and the present application is not particularly limited.
For example, a user may input attribute information of corresponding metadata through an input device of a terminal according to a service requirement. For example, a user inputs a standard text of metadata to a terminal, and the terminal may analyze the standard text of the metadata through a tool having a text analysis function to obtain attribute information of metadata corresponding to the standard text of the metadata. For another example, the user may select or input metadata and/or attribute information of metadata corresponding to the business requirements in the metadata configuration template. Accordingly, after obtaining metadata and/or attribute information of the metadata, the terminal may generate a request for the metadata according to the metadata and/or attribute information of the metadata, and send the request for the metadata to the server.
Optionally, the request for updating metadata may further include an update type. The update type may include adding metadata, modifying metadata, deleting metadata, among others. It is understood that the server can accurately perform the corresponding operation according to the update type of the update metadata. For example, when the update type is delete metadata, the server may delete the metadata directly from the database. For another example, when the update type is newly added metadata, the server may check the database for duplication based on the attribute information of the metadata, and if there is no duplicated metadata, add the metadata to the database.
S102, the server determines the data type of the metadata according to the request for updating the metadata, and determines the attribute to be verified of the metadata according to the corresponding relation between the configured data type and the attribute to be verified.
In one or more embodiments, metadata in the present application may include a plurality of metadata of different data types. The identification information of the data types corresponding to the different data types is different, that is, the identification information of one data type has uniqueness.
After receiving the request for updating the metadata, the server can determine the data type of the metadata according to the identification information of the data type carried in the request. For example, the information carried by the request for updating the metadata includes identification information of the data type of the metadata, and the server can determine the data type of the metadata according to the correspondence between the prestored data type and the identification information after acquiring the identification information. Or the attribute information included in the request for updating the metadata includes a data type and/or a data type identifier, and the server may acquire the data type and/or the data type identifier of the metadata from the attribute information of the metadata.
Further, the server may determine the attribute to be verified from the attribute information of the metadata according to the correspondence between the data type and the attribute to be verified.
It is understood that different data types may be different for the attribute to be verified in the present application. The attributes to be verified corresponding to different data types may also be the same. I.e. each data type corresponds to an attribute to be verified.
For example, the attribute of the metadata in the present application may have a corresponding tag, different tags may correspond to different data types, and the attribute of the different tag may be an attribute to be verified of the data type corresponding to the tag. For example, the tag corresponding to the attribute information of the metadata includes a, b, c, and the data type includes A, B, C. Wherein a corresponds to A, B corresponds to B, and C corresponds to C. The attribute with the label of a is the attribute to be verified of the data type A, the attribute with the label of B is the attribute to be verified of the data type B, and the attribute with the label of C is the attribute to be verified of the data type C.
Optionally, the attribute to be verified corresponding to the metadata may be set according to the service requirement. For example, attribute 1 is set as an attribute to be verified according to a business requirement, and when attribute 1 is included in the attribute of the metadata, verification of attribute 1 is required.
It can be understood that the corresponding attribute to be verified can be determined by adopting the method for the metadata of different data types, all the attributes of the metadata do not need to be verified, and the efficiency of verifying the attributes of the metadata is improved under the condition that the attribute values of the attributes of the metadata meet the set rules.
S103, the server verifies the attribute value of the attribute to be verified according to the attribute standard rule.
In one or more embodiments, the attribute criteria rules may be pre-set according to business needs. For example, the attribute criteria rules may be generated from a pre-set data dictionary. The attribute criteria rule may also be determined based on attribute values of attribute information of a plurality of history metadata. For example, attribute information of a plurality of history metadata may be input into a data model, and the data model outputs an attribute criterion rule corresponding to the attribute.
In one or more embodiments, the attribute criteria rules corresponding to attributes of metadata of different data types may be different. For example, the attribute criterion rule corresponding to the data length attribute of the metadata of the data type a may be 10 bytes, and the attribute criterion rule corresponding to the data length attribute of the metadata of the data type B may be 5 bytes. It is understood that the attribute criteria rules corresponding to attributes of metadata of different data types may also be the same.
In the process of verifying the attribute value of the attribute to be verified according to the attribute standard rule, when the attribute value in the attribute to be verified does not meet the attribute standard rule, the server can change the attribute value which does not meet the attribute standard rule into a default value. Wherein the default value of each attribute may be preset. For example, when the attribute standard rule of the "whether to fill in" attribute corresponding to the data type a is yes, and the data type of the metadata is a and the attribute value of the "whether to fill in" attribute is no, the server may change the attribute value of the "whether to fill in" attribute of the metadata to yes. For another example, the attribute criteria rule for the "length" attribute is that the data length is no more than 10 bytes, and the default value for the "length" attribute is 5 bytes. When the attribute value of the "length" attribute of the metadata is greater than 10 bytes, the server may change the attribute value of the "length" attribute to 5 bytes.
Optionally, when the attribute value in the attribute to be verified does not meet the attribute standard rule of the attribute, the server may further send information that the attribute value of the attribute does not meet the attribute standard rule. For example, in the process of verifying the attribute to be verified, when the attribute value of a certain attribute to be verified does not meet the information of the attribute standard rule, the server can immediately send the information to the terminal, so that the user is timely reminded. Or the server can also send all information which does not meet the attribute standard rule to the terminal after verifying all the attributes, so that the communication times between the server and the terminal are reduced, and the communication quantity is reduced. Wherein, the form of transmitting the rule information which does not satisfy the attribute criterion may be set according to the importance degree of the metadata.
It can be understood that when the terminal receives information that the attribute value of a certain attribute to be verified does not meet the attribute standard rule, the user can modify the attribute value of the attribute through the terminal, so that the attribute value of the modified attribute meets the attribute labeling rule. After the user modifies the attribute value of the attribute, the server can verify the attribute value of the attribute again according to the attribute standard rule so as to ensure that the attribute value of the attribute meets the attribute standard rule.
In addition, when the attribute to be verified is not included in the attribute standard rule, the server may send alert information to the terminal. The user can obtain the prompt information through the terminal and process the attribute according to the prompt information. The processing is, for example, determining a field name and/or identification error for the attribute and altering the field name and/or identification of the attribute. The processing mode may also be to determine the attribute as a new attribute and add an attribute standard rule of the attribute to the attribute standard rule. For example, the attribute standard rule is generated according to the data dictionary, when a new attribute appears, the attribute standard rule of the attribute can be added in the attribute standard rule, and meanwhile, the attribute standard rule of the attribute is synchronously added in the data dictionary, so that the consistency and the usability of the subsequent attribute standard rule are ensured.
S104, the server generates standard metadata of the metadata according to the attribute information of the metadata.
In one or more embodiments, after the server verifies the attribute of the metadata, standard metadata of the metadata may be generated according to the attribute information of the metadata. For example, after the server verifies the attribute of the metadata, the metadata may be encapsulated, and the metadata may be encapsulated as standard metadata. Or the server may process the attribute information of the metadata according to a preset standard metadata template to obtain standard metadata of the metadata.
It is understood that the completion of the attribute verification of the metadata by the server means that the server determines that the attribute values of the attributes of the metadata all satisfy the attribute standard rule.
S105, the server sends standard metadata to the terminal.
In one or more embodiments, after the server generates the standard metadata through step S104, the standard metadata may be transmitted to the terminal. Accordingly, the terminal receives standard metadata from the server. The terminal can display the standard metadata generated by the server to the user so that the user can confirm that the standard metadata meets the service requirement, and the accuracy of the standard metadata is ensured.
For example, after receiving standard metadata from the server, the terminal may present the standard metadata to the user in the form of a table. Or the terminal may present the standard metadata to the user in the form of a text description. It will be appreciated that the terminal may also present the standard metadata to the user in other forms, which are not examples of the application.
In one or more embodiments, the server may transmit metadata to the terminal in the form of a file. When the server generates the standard metadata, the server may generate a standard metadata file supporting the system according to the type of the system supported by the terminal. The server may also generate metadata files in different formats according to business requirements. For example, the format of the metadata file may be a "xlsx" format, a "doc" format, a "docx" format, a "pdf" format, or a "txt" format. It is understood that the format of the metadata file may be other formats, and the present application is not particularly limited.
Based on the embodiment, the server can generate metadata files supporting different systems and different formats according to requirements, so that flexibility of generating the metadata files is improved, service requirements are met, and maintainability of metadata is improved.
And S106, the server updates the standard metadata according to the acquired update indication information.
As an example, the update indication information may be transmitted to the server according to a preset period. The update indication information may be generated by the terminal and transmitted to the server according to a preset period. Or the update indication information may be generated by other devices and transmitted to the server. For example, the present application may further include a management device that may send update instruction information to the server periodically. Accordingly, the server may receive the update indication information and change the standard metadata according to the update indication information. It is understood that the update instruction information acquired in this manner may be used to instruct updating of a plurality of standard metadata. That is, the server may update all of the standard metadata to be updated according to the update instruction information.
As another example, the update indication information may be transmitted to the server according to an indication of the user. For example, in the course of performing the action of step S105, when the user determines that the standard metadata satisfies the service requirement, the user may transmit confirmation indication information to the server through the terminal. The server may generate update indication information for updating the standard metadata according to the confirmation indication information, and change the standard metadata according to the update indication information. It is understood that the update instruction information acquired in this manner may be used to instruct updating of specified standard metadata. That is, the update indication information corresponds to the standard metadata one by one. The server may update the standard metadata according to the correspondence between the update instruction information and the standard metadata.
For another example, the user may send update indication information to the server through the terminal, and the server may receive the update indication information and change the standard metadata according to the update indication information. It is understood that the update instruction information acquired in this manner may be used to instruct updating of a plurality of standard metadata. That is, the server may update all of the standard metadata to be updated according to the update instruction information.
The server update standard metadata is described as follows:
in one or more embodiments, the server may further determine a database storing the standard metadata before updating the standard metadata according to the acquired update instruction information, and perform data format conversion on the standard metadata according to a correspondence between a database type and a data format. The data format conversion may be, for example, transcoding, date and time format conversion, or the like.
In one or more embodiments, there may be a correspondence between a data type and a database for storing metadata, and the server may determine a database corresponding to standard metadata to be updated according to the correspondence between the data type and the database, and store the standard metadata to the corresponding database, so as to manage standard metadata of different data types.
In one or more embodiments, the server may store the standard metadata to be updated into the database with more remaining space according to the usage conditions of multiple databases, so as to avoid that the storage rate of a certain database is higher.
In one or more embodiments, the present application may further include a metadata platform, and after the server generates the standard metadata, the standard metadata may be pre-stored to the metadata platform, or the standard metadata may be transmitted to the metadata platform. After the server receives the update instruction information, standard metadata in the metadata platform can be updated to a corresponding database. The specific embodiment of updating the standard metadata by the server may refer to the foregoing, and will not be described herein.
In addition, after the server stores the standard metadata in the corresponding database, the user can query the metadata in the database according to the key information, so that the function of reverse query according to the information such as the metadata name or the data type is realized. The metadata query mode may include a basic query mode and an advanced query mode. The basic query mode may refer to querying metadata from a database according to preset keywords. Advanced query means may refer to user-defined query conditions according to requirements. The query conditions are, for example, data type, metadata update time, etc. The user can generate corresponding query sentences according to the self-defined query conditions so as to improve the accuracy of the query metadata.
Based on the above and the same ideas, the present application provides an apparatus for updating metadata. As shown in fig. 2, the apparatus includes a communication module 201 and a processing module 202.
A communication module 201 for receiving a request for updating metadata from a terminal, the request for updating metadata including attribute information of the metadata. The processing module 202 is configured to determine a data type of the metadata, and determine a property to be verified of the metadata according to a corresponding relationship between the configured data type and the property to be verified. The processing module 202 is further configured to sequentially verify the attribute values of the attribute to be verified according to an attribute standard rule, where when the attribute value in the attribute to be verified does not satisfy the attribute standard rule, the attribute value that does not satisfy the attribute standard rule is changed to a default value. The processing module 202 is further configured to generate standard metadata of the metadata according to attribute information of the metadata. The communication module 201 is further configured to send the standard metadata to the terminal. The processing module 202 is further configured to update the standard metadata according to the acquired update indication information.
In one possible embodiment, the attribute information of the metadata includes a definition field name, a length, whether to fill, a data type, a description value, a constraint, a default value.
In a possible embodiment, the update indication information is sent to the server according to a preset period. Or the update instruction information is transmitted to the server according to the instruction of the user.
In a possible embodiment, the processing module 202 is further configured to determine a database storing the standard metadata and perform data format conversion on the standard metadata according to a correspondence between a database type and a data format before updating the standard metadata according to the acquired update indication information.
Fig. 3 shows a schematic structural diagram of an electronic device according to an embodiment of the present application.
The electronic device in an embodiment of the application may comprise a processor 301. Processor 301 is the control center of the device and may connect the various parts of the device using various interfaces and lines by running or executing instructions stored in memory 303 and invoking data stored in memory 303. Alternatively, the processor 301 may include one or more processing units, and the processor 301 may integrate an application processor and a modem processor, wherein the application processor primarily processes an operating system and application programs, etc., and the modem processor primarily processes wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 301. In some embodiments, processor 301 and memory 303 may be implemented on the same chip, or they may be implemented separately on separate chips in some embodiments.
The processor 301 may be a general purpose processor such as a central processing unit (Central Processing Unit, CPU), digital signal processor, application specific integrated circuit, field programmable gate array or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, which may implement or perform the methods, steps and logic blocks disclosed in embodiments of the application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be performed directly by a hardware processor or by a combination of hardware and software modules in the processor.
In an embodiment of the present application, the memory 303 stores instructions executable by the at least one processor 301, and the at least one processor 301, by executing the instructions stored in the memory 303, may be used to perform the method steps disclosed in the embodiment of the present application.
The memory 303 is used as a non-volatile computer-readable storage medium for storing non-volatile software programs, non-volatile computer-executable programs, and modules. The Memory 303 may include at least one type of storage medium, and may include, for example, flash Memory, a hard disk, a multimedia card, card Memory, random access Memory (Random Access Memory, RAM), static random access Memory (Static Random Access Memory, SRAM), programmable Read-Only Memory (Programmable Read Only Memory, PROM), read-Only Memory (ROM), charged erasable programmable Read-Only Memory (ELECTRICALLY ERASABLE PROGRAMMABLE READ-Only Memory, EEPROM), magnetic Memory, magnetic disk, optical disk, and the like. Memory 303 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory 303 in embodiments of the present application may also be circuitry or any other device capable of implementing a memory function for storing program instructions and/or data.
In the embodiment of the application, the device may further include a communication interface 302, and the electronic device may transmit data through the communication interface 302.
Alternatively, the processing module 202 and/or the communication module 201 shown in fig. 2 may be implemented by the processor 301 (or the processor 301 and the communication interface 302) shown in fig. 3, that is, the actions of the processing module 202 and/or the communication module 201 may be performed by the processor 301 (or the processor 301 and the communication interface 302).
Based on the same inventive concept, embodiments of the present application also provide a computer-readable storage medium in which instructions may be stored, which when run on a computer, cause the computer to perform the operational steps provided by the above-described method embodiments. The computer readable storage medium may be the memory 303 shown in fig. 3.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.