Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the following detailed description of the embodiments of the present application will be given with reference to the accompanying drawings.
In designing the drawings, the following description refers to the same or similar elements in different drawings unless indicated otherwise. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the application as detailed in the accompanying claims.
In the description of the present application, it should be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. The specific meaning of the above terms in the present application will be understood in specific cases by those of ordinary skill in the art. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.
The present application will be described in detail with reference to specific examples.
FIG. 1 illustrates an exemplary system architecture 100 that may be employed in the resource management method of the present application.
As shown in fig. 1, a system architecture 100 may include a user 101, an electronic device 102, and a network 103. The network 103 is used as a medium to provide a communication link between the user 101 and the electronic device 102. The system architecture 100 may be applied to various practical application scenarios, for example, when the system architecture 100 is applied to online live broadcast, the user 101 may be a teacher or a student in online live broadcast courses, a research and development background, etc., the user 101 may be used to trigger various instructions on the electronic device 102, the electronic device 102 may be a teacher client, a student client, a background management server, etc., and the electronic device 102 may be used, but is not limited to, be responsible for reading various instructions triggered by the user 101, decoding the instructions, and executing the instructions. For example, in the process of performing an online live course, in order to explain a concept more intuitively, the user 101 (for example, but not limited to, a teacher's first) needs to upload a section of audio and video data, the user 101 (for example, but not limited to, a teacher's first) may click a load button through a mouse to trigger loading of the service of uploading the audio and video data 1, then the electronic device (for example, but not limited to, a teacher's client) obtains the target resource data of the audio and video data 1, determines a corresponding target data relationship based on a corresponding target model, then stores the target resource data and the target data relationship, and other users (for example, but not limited to, a student's first) may download the target resource data (i.e., the audio and video data 1) according to a unique code to obtain relevant operations such as a corresponding relationship of each resource data piece.
The electronic device 102 may be hardware or software. When the electronic device 102 is hardware, it may be a variety of electronic devices with code generation rules and sample model relationships, including but not limited to smartphones, tablets, laptop and desktop computers, and the like. When the electronic device 102 is software, it may be implemented as a plurality of software or software modules (e.g., to provide distributed storage services), or as a single software or software module, which is not specifically limited herein.
The network 103 may include various types of wired or wireless communication links, and data interactions between the user 101 and the electronic device 102 may be through the network 103, for example: the wired communication link includes an optical fiber, a twisted pair wire, or a coaxial cable, and the Wireless communication link includes a bluetooth communication link, a Wireless-Fidelity (Wi-Fi) communication link, a microwave communication link, or the like.
It should be understood that the number of users 101, electronic devices 102, and networks 103 in fig. 1 is merely illustrative. Any number of users 101, electronic devices 102, and networks 103 may be desired for implementation.
In the following method embodiments, for convenience of explanation, only the execution subject of each step will be described as an electronic device.
The resource management method provided by the embodiment of the application will be described in detail with reference to fig. 2 to 3.
Referring to fig. 2, an interaction schematic diagram of a resource management method is provided in an embodiment of the present application. The method may comprise the steps of:
S201, acquiring target resource data, and determining a corresponding target model based on the target resource data.
Generally, resource data may refer to resources in a computer network system, and may be divided into three general categories: data resources, software resources, and hardware resources. For example: the data resources may include data such as picture data, audio and video data, file data, domain names, etc., the software resources may include system software (such as but not limited to operation software, protocol software, etc.) and user software (such as but not limited to live course software, resource management software, middleware clusters, etc.), and the hardware resources may include various hardware such as a host, a storage hard disk, a display, etc. The resource data can be coordinated with each other to jointly complete various business requirements of users on the electronic equipment.
The target resource data may be any resource data in a computer network system, where the target resource data does not specifically refer to a specific resource data or a specific resource data, and is not specifically limited, and may be resource data obtained for the current operation of the user, so as to distinguish the resource data from other resource data of another purpose being invoked.
The target resource data may carry type information and attribute information, and the type information may be information for characterizing a type of the target resource data, and may include multiple types such as an application class, a host class, a service class, a middleware class, a domain name class, an interface class, and the like, and the electronic device may be classified into different types according to a specific application scenario, which is not limited herein. The attribute information may refer to information of a characteristic or property or state of the target resource data, and different types of resource data may include different attribute information, for example: the target resource data for the application class may include attribute information such as abstract, belonging department, message Queue (MQ) cluster, mySql cluster of relational database management system, service end identification number (Identity documen, ID), service end name, item group, service end, application name, target path, application responsible person, programming language, distributed version control system Git repository address, application template, application description, upload date, download update record, etc. The target resource data for the host class may include attribute information such as a digest, a department to which the target resource data belongs, a host name, a host type, a service provider, a product line, an operating system, a host environment, and the like. The attribute information may be inherent to the resource data, or may be customized by a user or a technician, which is helpful to increase the applicability of the present application, and is convenient for the technician to set according to actual requirements, which is not limited herein specifically.
The electronic device may determine the type information and attribute information of the target resource data by reading a header file of the target resource data and then parsing the header file, for example: the electronic device may determine that the type of the resource data is a data type by determining that the format of the resource data is a bmp format or a jpg format, and then may determine that the attribute information includes information such as a file type, an opening manner, a location, a size, an occupied space, a creation time, and the like by reading a header of the resource data in the bmp format or the jpg format. The electronic equipment can also preset the corresponding relation between the type information and the attribute information and the information identifier, then the electronic equipment can inquire out the specific type information and attribute information of the target resource data in the corresponding relation between the type information and the attribute information on the network server and the information identifier by determining the information identifier of the target resource data, and the electronic equipment can receive the inquiry result sent by the network server, so that the electronic equipment can be helped to quickly and accurately determine the information of the target resource data.
The manner in which the electronic device obtains the target resource data is various, and is not limited in detail herein, and the electronic device may receive the target resource data reported by other associated devices, for example: the electronic equipment can receive the pressure measurement scheme uploaded by the technician A in the live broadcast pressure measurement department by using the host computer a. The electronic device may also crawl target resource data meeting a certain condition on the internet through a crawler technology, for example: the live template material research department can crawl relevant resource data for explaining the dream of the red blood cells on the Internet. The electronic device may also receive target resource data uploaded by the user, such as: in the online live broadcast system, student A shares life videos and the like for other classmates and teachers, or the resource management platform server can receive six-grade first-school English class teaching templates uploaded by the teacher B, so that the electronic equipment can acquire target resource data more conveniently and variously.
After the electronic device acquires the target resource data, the electronic device can then determine a target model corresponding to the target resource data. The object model may be an abstract data structure for describing similar resource data, and may be understood as a table structure in a database, etc., and may include parameters or attributes such as code, display name, data type, description, name attribute, default value, and relationship information (such as, but not limited to, relationship metadata number, relationship type, source model, source attribute code, source display name, object model code, object display name, version), etc., which are used herein to distinguish between other types of models. The relationship information may be information for describing a relationship between the models, and the electronic device may determine the relationship between different models through the relationship information, so as to determine the relationship between the resource data, where the relationship may be a belonging relationship, a same project relationship, a same responsibility relationship, and other various custom relationships.
The electronic device may customize various properties of the target model, including additions, modifications, deletions, etc., which may be used to determine the unique encoding of the target resource data. The manner in which the electronic device determines the target resource data is various and is not particularly limited herein, for example: the electronic equipment can determine the target model corresponding to the target resource data through the type information carried by the target resource data, the electronic equipment determines the target resource data as a host type, and then can determine the target model as a target model of the host type through the corresponding relation between the type information and the target model, wherein the corresponding relation between the type information and the target model can be stored locally or in a cloud (such as a storage server but not limited to the cloud), so that the storage space of the electronic equipment is reduced, and the operation efficiency is improved.
The target model may include a corresponding target code generation rule, where the target code generation rule may refer to a rule, a method, a function, or the like for obtaining a corresponding code according to attribute information of resource data, and the target model and the code generation rule may have a one-to-one correspondence, where a correspondence manner is not specifically limited, and may be in a form of a correspondence table or the like. The code generation rule can also be one parameter of the target model, the logic relationship between the code generation rule and the target model is not particularly limited, and the code generation rule can be determined according to actual use conditions, so that the electronic equipment can quickly, conveniently and accurately determine the target code generation rule.
The target model may include a corresponding target model relationship, where the target model relationship may refer to a relationship, association, etc. between different corresponding models obtained according to attribute information of resource data, and the target model relationship may be a one-to-one correspondence relationship, where the correspondence manner is not specifically limited, and may be a relationship correspondence table, etc. The target model relationship can also be one parameter of the target model, and the logic relationship between the target model relationship and the target model is not particularly limited, so that the target model relationship can be determined according to actual use conditions, and the electronic equipment can be helped to quickly, conveniently and accurately determine the target model relationship.
In the existing resource relation acquisition scheme, because resources are distributed in different development departments for maintenance, the standards are not uniform, the relation among different resources is lost, a user needs to find the maintenance departments of different resources, the required resource data is exported by using an internal system, the resource data is standardized, the resource relation is manually arranged, the resource relation cannot be automatically generated, the quality of the resource relation data cannot be ensured, a large amount of development and maintenance codes are required, and the management of the resource data is complex. In the application, the resource relation among the resource data is determined by defining the corresponding models for different types of resource data, after the models are defined, the data standard of each type of resource data can be set manually, and the information such as attributes and the like does not need to be input, a new column, a table and other changed storage structures are not needed to be determined, the resource relation data is automatically calculated by the definition of the model relation, the maintenance and the change are convenient, the management attributes (new, deleted and modified) are defined, the requirements of technicians are convenient to meet, and the development workload is reduced.
S202, obtaining a target model relation between the target model and other models.
In general, the object model relationship may be an association relationship between description models or tables, and may be understood as an external key in a database, for example: the application may associate an application process, the application process and the host may be in a primary-secondary relationship, the application may associate an application domain name, the application domain name may associate a domain name, and so on. The relationship can be divided into a model relationship and a resource relationship, the model relationship is on a model level, a certain relationship exists between two models can be specified, the relationship can be described by relationship metadata, the resource relationship can refer to two specific resource data, and an actual relationship is generated according to rules defined by the model relationship. The relationship metadata may include metadata number, relationship type, source model, source attribute model, target attribute code, target end display name, version, etc., and the electronic device may determine the relationship between the resource data through the relationship metadata. There are many ways for an electronic device to obtain a target model relationship between the target model and other models, for example: the electronic equipment determines that the target model is the number A, other models are the numbers B, and the electronic equipment can inquire and determine that the model A and the model B are main-sub relations in a preset model relation table. In one possible embodiment, the electronic device may further determine the target model relationship through type information and attribute information of the target model and other models, for example: the electronic equipment determines that the target model C is of an application type, the attribute information comprises a live broadcast software 1 function document, other models D are of application types, and the attribute information also comprises the live broadcast software 1 function document, so that the electronic equipment can determine that the model relation between the target model C and the other models D is of the same kind and the same order, the electronic equipment is helped to quickly determine the target model relation, and the processing efficiency of the follow-up steps is improved.
S203, calculating and storing the target data relation between the target resource data and the corresponding resource data in other models according to the target model relation.
In general, the target data relationship may refer to a specific actual relationship between two resource data, may include a main sub relationship, an association relationship, a relationship of the two resource data, a loading relationship of the same application process, and the like, and may be defined in a user-defined manner, which is not specifically limited herein, so as to correspond to the target resource data and other resource data. After the electronic device obtains the target model relationship between the target model and other models, the electronic device may then determine the target data relationship between the target resource data and other specific resource data, for example: the electronic equipment determines that the target model relationship is a containing relationship, then can automatically calculate resource relationship data through attribute information of two models, and determines that the attribute information of the target model and the attribute information of other models both comprise creator A and product line 5, then the electronic equipment can calculate that the target resource data-the other resource data are the same-layer node relationship associated with the same cluster. The method for calculating the target data relationship is not particularly limited, and can be defined according to the actual use condition of the user, and the user can also input a modification instruction to modify the calculation method at any time. In a possible embodiment, the other models and the target model may be of the same type, or may be of different types, and are not particularly limited, so as to help improve adaptability of resource management.
In one possible embodiment, after the electronic device obtains the target data relationship corresponding to the target resource data, the target data relationship and other attribute information (such as, but not limited to, a storage address, etc.) of the target resource data may be set as a corresponding relationship, where a manner of setting the corresponding relationship includes uploading to a database in a storage server, etc. The electronic device can then perform processing such as calling on multiple departments and platforms through the unique coded information, thereby facilitating multi-department business processing and facilitating maintenance and management.
From the above, it can be seen that the target resource data is obtained, the corresponding target model is determined based on the target resource data, the target model relationship between the target model and other models is obtained, and the target data relationship between the target resource data and the corresponding resource data in other models is calculated and stored according to the target model relationship. The electronic equipment can quickly and conveniently determine the relation among the resource data according to the corresponding models and the corresponding model relations of each type of resource data by defining different models corresponding to different resource types and determining the relation among the different models, does not need to introduce additional complex secondary development, can modify the relation among the target models and the models at any time according to the requirements of users, realizes the modification of the relation among the resource data of different types, and reduces the complexity of multi-department resource data management.
Referring to fig. 3, another interactive schematic diagram of a resource management method is provided in an embodiment of the present application. The resource management method may include the steps of:
S301, acquiring sample type information of at least one type and sample sharing attribute information corresponding to each sample type information.
In general, sample type information may refer to type information used to define a corresponding model, and sample common attribute information may refer to attribute information commonly owned by similar resource data. For example: the electronic device can acquire two sample type information of a data type and a software type, the data type can comprise two pieces of resource data of a picture a and an audio/video b, wherein the picture a can comprise attribute information such as a file type, an opening mode, a position, an occupied space and the like, the video b can comprise attribute information such as a file type, a position, a frame rate, a format and the like, and the electronic device can share the attribute with the file type and the position as samples corresponding to the data type. In one possible embodiment, the electronic device may receive sample type information reported by a user and sample common attribute information corresponding to each sample type information. The electronic equipment can search all local resources to acquire sample type information and sample common attribute information corresponding to each sample type information, and the electronic equipment is facilitated to acquire resource data quickly and conveniently.
S302, determining corresponding sample models according to the sample type information, and determining sample code generation rules and sample model relations corresponding to the sample models according to the common attributes of the samples.
Generally, after the electronic device obtains at least one type of sample type information and sample common attribute information corresponding to each sample type information, each corresponding sample model may be determined according to each sample type information, and a sample code generation rule and a sample model relationship corresponding to each sample model may be determined according to each sample common attribute. For example: the electronic device may define a sample template of a data type to obtain a sample common attribute file type, a position, an opening mode, and the like, and the corresponding sample code generation rule may be set to add the first item and the second item, that is, add the file type and the position, so as to be helpful to generate a unique code according to the existing attribute information, and reduce the development workload. The electronic device may define a sample template of an application type for obtaining a sample common attribute application name type, development company and version number, etc., and the corresponding sample code generation rule may be set to add the first item and the third item, i.e. to add the name type and the version number. For example: the electronic device may set the relationship of the sample model as the association relationship with other sample models a, the relationship of the sample model with other sample templates B as the inclusion relationship, the relationship of the sample model with other sample templates C as the non-association relationship, the relationship of the sample model with other sample templates D as the same application dynamic library relationship, and the like. The sample model relation and the corresponding template model have a corresponding relation, can be one of attribute information in the corresponding sample model, can also be stored in a relation data table, and is beneficial to the electronic equipment to quickly and efficiently determine the sample code generation rule and the sample model relation corresponding to each sample model through query and acquisition.
S303, receiving newly-added resource data uploaded by a user, inquiring whether the newly-added resource data has a corresponding unique code, and if the newly-added resource data does not have the corresponding unique code, taking the newly-added resource data as target resource data.
In general, the newly added resource data may refer to resource data uploaded by a current user, which is not specifically limited to a certain resource or a certain class of resources, and is used for distinguishing other resources in the electronic device. After the electronic device determines the sample code generation rule corresponding to each sample model according to the common attribute of each sample, new resource data uploaded by the user can be received, as shown in fig. 4, the user can select the resource data (for example, but not limited to, file 1) to be uploaded first, and then the file 1 can be uploaded to the electronic device by clicking a "determine upload" button on the display screen of the electronic device. The electronic device may then query whether the newly added resource data has a corresponding unique code, where the query manner is not limited, for example: the electronic device can mark the resource data which has generated the unique code as 1 and the resource data which has not generated the unique code as 0, so that the electronic device can quickly traverse all the resource data to determine whether the newly added resource data has generated the unique code or not, thereby preventing the situation of repeated codes due to various reasons such as repeated uploading and the like and wasting computer resources.
After inquiring whether the corresponding unique code exists in the newly-added resource data, the electronic equipment does not need to regenerate the unique code corresponding to the newly-added resource data if the corresponding unique code exists in the newly-added resource data, and takes the newly-added resource data as target resource data if the corresponding unique code does not exist in the newly-added resource data, namely, the unique code corresponding to the newly-added resource data needs to be generated later.
In one possible embodiment, the electronic device may further query, at a preset time (for example, but not limited to, setting the time period to be 2 hours), all local resource information, query whether all the resource data have corresponding unique codes, and if the uncoded resource data exist in all the resource data, take the uncoded resource data as target resource data. As shown in fig. 5, assuming that the preset time is 12:00, at the non-preset time (for example and without limitation, 11:49), the electronic device does not execute the task of querying resources, the querying duration may be customized (for example and without limitation, 20 minutes) at the beginning of 12:00, the electronic device executes the query local all resource information service, the current query progress and the like on the electronic device, and the execution of the query service may also be performed in the background so as not to prevent the electronic device from executing the current service, which is helpful for the electronic device to reasonably allocate the service and avoid the operation condition of resource waste or resource shortage.
S304, determining corresponding target metadata based on the type information of the target resource data, and determining a target model corresponding to the target resource data according to the target metadata.
In general, the target resource data carries type information and attribute information, and the target metadata may be data describing data, mainly may be information describing attributes of the data, and may be used to support functions such as indicating a storage location, historical data, searching resources, and recording files, where the target metadata is not limited to one or a certain type of metadata, but is different from other types of corresponding metadata, for example: the target metadata may include metadata ID, name, resource type, description, version, etc. information. After the electronic device obtains the target resource data, the corresponding target metadata can be determined based on the type information, for example: the electronic device determines that the target resource data is an application (such as, but not limited to, live online software) type, and then determines that target metadata corresponding to the application type may include information such as a host type, a media access Control Address (Mac) Address, a host responsible person, an operating system kernel release version, and a product line.
The electronic device may then determine, according to the target metadata, an application target model corresponding to the application (e.g., without limitation, live online software) type, through which all specific parameters of target metadata of the target model corresponding to the target resource data may be obtained. After the electronic device receives the reported resource data, the corresponding target model can be loaded according to the type information carried by the resource data, then specific parameters (such as but not limited to each attribute information of the resource data and corresponding code generation rule and model relation) of metadata of the target model are determined, finally the electronic device can input the specific parameters of the metadata of the target model (namely attribute set data of the resource data) according to the code generation rule, calculate the code generation rule, generate unique codes, and calculate the actual data relation of the target resource data and other resource data according to the model relation, so that the electronic device can accurately and quickly determine the target model.
S305, receiving a model modification instruction, modifying target metadata of the target model based on the model modification instruction, wherein the target metadata corresponds to the target model relation, and taking the modified target model as a target model corresponding to the target resource data.
In general, a model modification instruction may refer to an instruction (such as, but not limited to, an instruction to add, delete, modify, etc.) that is used to modify metadata of a model corresponding to a certain type of resource data. After determining the target model corresponding to the target resource data, the electronic device may further receive a model modification instruction, and modify target metadata of the target model based on the model modification instruction, for example: the first item of the target model metadata (i.e. specific attribute information of the target resource data) determined by the electronic device through the target model is a service line: the service line No. 3, the second item is the area to which the machine belongs: the area B and the third item are the number of processor cores: and 4, the corresponding target model relationship is an association relationship with the model A and a main sub relationship with the model B.
Then, the electronic device determines, according to the model modification instruction, that the first item of modified target model metadata (i.e. specific attribute information of the target resource data) is a service line: service line No. 3, second term machine-described region: the area B and the third item are the number of processor cores: and 6, the corresponding target model relationship is a main-sub relationship with the model A and an association relationship with the model B. The target metadata corresponds to the target model relationship, which may be understood as the target model relationship is one item of metadata in the target model, for example: the fourth term is the object model relationship: the relationship with the model C is the association relationship with the model D is the main sub relationship, and the relationship between the target model relationship and the target model can be understood as the corresponding relationship, and the logic relationship and the specific corresponding manner are not particularly limited. As shown in FIG. 6, a user can modify the metadata of the target model on the model modification interface, for example, the initial business line is number 3, the target model relationship is the association relationship with the model 1, the current business line is number 2, the target model relationship is the main sub relationship with the model 1, and the modification is performed by clicking the "determine modification" button on the electronic device, and finally, the current information of the model can be checked on the current model metadata interface, so that the processing of the electronic device for calculating the resource relationship in batches of similar resource data is facilitated. And finally, the electronic equipment takes the modified target model as a target model corresponding to the target resource data.
S306, acquiring target metadata of the target model, and determining metadata relations in the target model and the other models based on the target metadata.
In general, metadata relationships may refer to relationship information between a target model and other models, and may be part of the data in the target metadata. After the electronic device uses the modified target model as the target model corresponding to the target resource data, the electronic device can determine the target data relationship through the target model, for example: the electronic device determines that the target metadata of the target model includes metadata numbers, names, resource types, descriptions, versions, code generation rules, model attribute metadata, metadata relationships and the like, wherein the metadata relationships may further include metadata relationship numbers: 123456, relationship type: main-sub relationship, source model: host type, source attribute encoding: abc, source display name number 1 host, target model: model 1 and object model coding: 456789, etc. The metadata relationship may include relationship information of one or more other models, where the data amount and specific information are not limited, and may be set in a customized manner according to the user's requirement.
S307, determining the target model relation between the target model and other models in the sample model relation according to the metadata relation in the target model and the other models.
In general, after determining the metadata relationships in the target model and the other models, the electronic device may determine target model relationships between the target model and the other models, for example: the electronic device determining metadata relationships in the target model and the other models includes corresponding models: model 1 and corresponding model coding: 456789 the sample model relationship determined in the target model before the electronic device comprises an association relationship with the model 1, a main sub relationship with the model 2, a same order relationship with the model 3, no loading of the same service relationship with the model 4, and the like, and the electronic device can quickly and accurately determine the target model relationship between the target model and other models as the association relationship by querying the corresponding model or random model coding and the like.
And S308, generating a unique code corresponding to the target resource data according to the target code generation rule and the attribute information, determining a target data relationship between the target resource data and the resource data corresponding to other models based on the target model relationship and the unique code, and storing the target data relationship.
Generally, after determining the target model relationship between the target model and the other models, the electronic device may determine the target data relationship between the target resource data and the corresponding resource data in the other models, for example: the electronic device determines that the first item of the modified target model metadata (i.e. the specific attribute information of the target resource data) is a service line: service line No. 3, second term machine-described region: the area B and the third item are the number of processor cores: and 6, adding the first item and the third item of the target metadata into b3631c65241c991c979bfddaad ef1e1 by the corresponding target code generation rule, and taking the value as a unique code corresponding to the target resource data by the electronic equipment. The electronic device can then determine that the target data relationship of the resource data a corresponding to the other models is a same-order library file relationship loading the same service, etc. through the target model relationship (such as, but not limited to, an association relationship) and attribute information (such as, but not limited to, a service provider, a usage description, a cluster name, etc.) of other resource data a.
After determining the target data relationship between the target resource data and the corresponding resource data in other models, the electronic device may also have the unique code corresponding to the target resource data and the corresponding resource data corresponding to other resource data, so that the user may determine the data relationship between different resource data according to different unique codes corresponding to different resource data, thereby facilitating the resource management as maintenance. As shown in fig. 7, the electronic device may customize the code generation rules (e.g., without limitation, rule 1 and rule 2), then may customize the selection attribute information at the code generation interface on the electronic device, and then generate the unique code corresponding to the target resource data by clicking the "ok" button. As shown in fig. 8, the data relationship may be represented by a model topology diagram with an application as a center, an application domain name and an application as an association relationship, an application domain name and a specific domain name as an association relationship, an MQ application and an application as an association relationship, an MQ cluster and an MQ application as a main sub relationship, an MQ cluster and an MQ node as a main sub relationship, and the like.
S309, storing the original data corresponding to the target resource data and the target data relation in a relation database, and updating an index database and a graph database based on the target data relation.
In general, the relational database may be a database (e.g., without limitation, mySql database) used to store raw data and data relationships of resource data, and may include model metadata, relational metadata, resource data, resource relational data, raw data, and the like. An index database may refer to a database (e.g., without limitation, an ES database) for searching for resource data, and actions may include indexing (automatic creation of each master model, support of sub-models, etc.), mapping (automatic creation of definitions from model attributes, etc.), and word segmentation (IK word segmentation, full-text indexing, etc.), updating the resource data in real-time, consistent with the original data, etc. The graph database may be a database (e.g., without limitation, a NEO4J database) for representing resource data relationships, may include nodes (which may correspond to resource data) and edges (which may represent relationship data between resource data), update resource data in real-time, agree with original data, and the like.
For example: after determining the target data relationship between the target resource data and the corresponding resource data in other models, the electronic device stores the original data (such as 30M data size) corresponding to the target resource data (such as, but not limited to, live courseware 1) and the target data relationship (such as association relationship with live courseware 2, inclusion relationship with picture 1, and the like) in a relationship database, and updates an index database and a picture database based on the target data relationship. As shown in fig. 9, if the electronic device acquires a message corresponding to the MQ data type and then determines the corresponding target data relationship, MQ nodes 2 may be added to the graph database.
S310, generating a corresponding data interface based on metadata of each model, receiving a query instruction based on the data interface, and acquiring a data relationship of resource data corresponding to the query code according to the query code.
Generally, the data interface may refer to acquiring resource data in the electronic device through hypertext transfer (Hypertext Transfer Protocol, HTTP) protocol, and the electronic device may call the data interface in external program code, and enter parameters to acquire specified resource data. The data interface may include: the universal interface and the custom interface can be automatically generated after each model definition is completed, for example: the method comprises the steps of adding, deleting, inquiring and modifying the resource data in the appointed 'model', and the calling mode, format and parameters of the universal interface can be fixed. If a third party has a personalized need, for example: the interface is not required to return all the resource attributes, only a part of the attributes are required to return, and the requirements cannot be met by the universal interface, so that the custom interface is required to support. The query instruction may be an instruction for querying a data relationship between different resource data, and the query instruction may carry a first query code and a second query code, where the first query code may correspond to the first resource data, and the second query code may correspond to the second resource data. For example: the electronic equipment analyzes the query instruction, determines that the first query code is 123456789 and the second query code is 987654321, and then can input the two query codes in a resource management platform of the electronic equipment to obtain relationship information which belongs to the same type of resource application, the same department development and the same project application. As shown in FIG. 10, the electronic device has determined two unique encodings (e.g., without limitation, 123456 and 456789) and can then query the electronic device for the data relationship of the corresponding two resource data by clicking on a "relationship query" button on the encoded relationship query interface.
As shown in fig. 11, the electronic device may customize query for resource data, for example: the electronic device may determine that the current model is an application type, and then may determine that the total amount of data for the valid application type is 1815 by clicking a "determine" button on a query interface on the electronic device, where 999 pieces of other resource data are not associated (may be represented by sector 2 portion), 816 pieces of other resource data are associated (may be represented by sector 1 portion), 19906 pieces of relational data for the application type are determined, 11663 pieces of resource data for the ES cluster (may be represented by sector 1 portion), 3469 pieces of resource data for the MySql cluster (may be represented by sector 2 portion), 678 pieces of resource data for the MQ cluster (may be represented by sector 3 portion), 468 pieces of resource data for the service (may be represented by sector 4 portion), and so on.
As shown in fig. 12, the electronic device may generate an interface path of the custom API through the custom API basic information (such as, but not limited to, name, object model, description, filtering condition, grouping, status, maximum number of returns per page, parameter, model attribute, operator, attribute, value master model attribute, and sub model attribute-application process list, etc.), and then the electronic device may pass the information of the requirements of the interface path. As shown in fig. 13, the electronic device may also customize setting input, display a resource list, and then display specific information by clicking on buttons such as "details", "modification records", "relationship calculation", "relationship topology", etc., or search for resource data satisfying the user's needs based on filtering conditions.
When the scheme of the embodiment of the application is executed, the target resource data is acquired, the corresponding target model is determined based on the target resource data, the target model relation between the target model and other models is acquired, and the target data relation between the target resource data and the corresponding resource data in other models is calculated and stored according to the target model relation. The electronic equipment can quickly and conveniently determine the relation among the resource data according to the corresponding models and the corresponding model relations of each type of resource data by defining different models corresponding to different resource types and determining the relation among the different models, does not need to introduce additional complex secondary development, can modify the relation among the target models and the models at any time according to the requirements of users, realizes the modification of the relation among the resource data of different types, and reduces the complexity of multi-department resource data management.
The following are examples of the apparatus of the present application that may be used to perform the method embodiments of the present application. For details not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the method of the present application.
Referring to fig. 14, a schematic structural diagram of a resource management device according to an exemplary embodiment of the present application is shown, and the resource management device 14 is hereinafter referred to as "management device". The management means 14 may be implemented as all or part of the terminal by software, hardware or a combination of both. Comprising the following steps:
a first obtaining module 1401, configured to obtain target resource data, and determine a corresponding target model based on the target resource data;
A second obtaining module 1402, configured to obtain a target model relationship between the target model and other models;
a storage module 1403, configured to calculate and store a target data relationship between the target resource data and the corresponding resource data in the other models according to the target model relationship.
In a possible embodiment, the management device 14 further comprises:
the third acquisition module is used for acquiring at least one type of sample type information and sample common attribute information corresponding to each type of sample type information;
And the first determining module is used for determining corresponding sample models according to the sample type information and determining sample code generation rules and sample model relations corresponding to the sample models according to the common attributes of the samples.
In one possible embodiment, the first acquiring module 1401 includes:
The first receiving unit is used for receiving newly-added resource data uploaded by a user and inquiring whether the newly-added resource data has a corresponding unique code or not;
and the first determining unit is used for taking the newly added resource data as target resource data if the corresponding unique code does not exist in the newly added resource data.
In one possible embodiment, the first acquiring module 1401 includes:
a second determining unit, configured to determine corresponding target metadata based on the type information of the target resource data;
and the third determining unit is used for determining a target model corresponding to the target resource data according to the target metadata.
In a possible embodiment, the management device 14 further comprises:
The first receiving module is used for receiving a model modification instruction, modifying target metadata of the target model based on the model modification instruction, wherein the target metadata correspond to the target model relation;
and the second determining module is used for taking the modified target model as a target model corresponding to the target resource data.
In one possible embodiment, the second obtaining module 1402 includes:
a first obtaining unit, configured to obtain target metadata of the target model, and determine a metadata relationship between the target model and the other model based on the target metadata;
And a fourth determining unit, configured to determine, in the sample model relationship, a target model relationship between the target model and the other model according to metadata relationships in the target model and the other model.
In one possible embodiment, the storage module 1403 includes:
The generating unit is used for generating a unique code corresponding to the target resource data according to the target code generating rule and the attribute information;
and a fifth determining unit, configured to determine a target data relationship between the target resource data and the resource data corresponding to the other models based on the target model relationship and the unique code, and store the target data relationship.
In one possible embodiment, the storage module 1403 further includes:
the storage unit is used for storing the original data corresponding to the target resource data and the target data relation in a relation database;
and the updating unit is used for updating the index database and the graph database based on the target data relationship.
In a possible embodiment, the management device 14 further comprises:
The generation module is used for generating a corresponding data interface based on the metadata of each model;
The second receiving module is used for receiving a query instruction based on the data interface; wherein, the inquiry instruction carries an inquiry code;
and the query module is used for acquiring the data relationship of the resource data corresponding to the query code according to the query code.
The embodiments of the present application and the embodiments of the methods of fig. 2 to 3 are based on the same concept, and the technical effects brought by the embodiments are the same, and the specific process can refer to the description of the embodiments of the methods of fig. 2 to 3, which is not repeated here.
The device 14 may be a field-programmable gate array (FPGA) implementing related functions, an application specific integrated chip (asic), a system on chip (SoC), a central processing unit (central processor unit, CPU), a network processor (network processor, NP), a digital signal processing circuit, a microcontroller (micro controller unit, MCU), a programmable controller (programmable logic device, PLD) or other integrated chips.
When the scheme of the embodiment of the application is executed, the target resource data is acquired, the corresponding target model is determined based on the target resource data, the target model relation between the target model and other models is acquired, and the target data relation between the target resource data and the corresponding resource data in other models is calculated and stored according to the target model relation. The electronic equipment can quickly and conveniently determine the relation among the resource data according to the corresponding models and the corresponding model relations of each type of resource data by defining different models corresponding to different resource types and determining the relation among the different models, does not need to introduce additional complex secondary development, can modify the relation among the target models and the models at any time according to the requirements of users, realizes the modification of the relation among the resource data of different types, and reduces the complexity of multi-department resource data management.
The embodiment of the present application further provides a computer storage medium, where the computer storage medium may store a plurality of instructions, where the instructions are suitable for being loaded by a processor and executed as described above, and the specific implementation process may refer to the specific description of the embodiment shown in fig. 2 or fig. 3, which is not repeated herein.
The present application also provides a computer program product storing at least one instruction that is loaded and executed by the processor to implement the template control method according to the above embodiments.
Referring to fig. 15, a schematic structural diagram of an electronic device is provided in an embodiment of the present application. As shown in fig. 15, the electronic device 15 may include: at least one processor 1501, at least one network interface 1504, a user interface 1503, a memory 1505, at least one communication bus 1502.
Wherein a communication bus 1502 is used to enable connected communications between these components.
The user interface 1503 may include a Display screen (Display) and a Camera (Camera), and the optional user interface 1503 may further include a standard wired interface and a standard wireless interface.
The network interface 1504 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface), among others.
Wherein the processor 1501 may include one or more processing cores. The processor 1501 uses various interfaces and lines to connect various portions of the overall terminal 1500, perform various functions of the terminal 1500 and process data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 1505, and invoking data stored in the memory 1505. Alternatively, the processor 1501 may be implemented in at least one hardware form of digital signal Processing (DIGITAL SIGNAL Processing, DSP), field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA), programmable logic array (Programmable Logic Array, PLA). The processor 1501 may integrate one or a combination of several of a central processing unit (Central Processing Unit, CPU), an image processor (Graphics Processing Unit, GPU), and a modem, etc. The CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing the content required to be displayed by the display screen; the modem is used to handle wireless communications. It will be appreciated that the modem may not be integrated into the processor 1501 and may be implemented on a single chip.
The Memory 1505 may include a random access Memory (Random Access Memory, RAM) or a Read-Only Memory (Read-Only Memory). Optionally, the memory 1505 includes a non-transitory computer readable medium (non-transitory computer-readable storage medium). Memory 1505 may be used to store instructions, programs, code, sets of codes, or sets of instructions. The memory 1505 may include a stored program region that may store instructions for implementing an operating system, instructions for at least one function (e.g., touch function, sound play function, image play function, etc.), instructions for implementing the various method embodiments described above, etc.; the storage data area may store data or the like referred to in the above respective method embodiments. Memory 1505 may also optionally be at least one memory device located remotely from the processor 1501. As shown in FIG. 15, an operating system, network communication module, user interface module, and resource management application may be included in memory 1505, which is one type of computer storage medium.
In the electronic device 1500 shown in fig. 15, the user interface 1503 is mainly used as an interface for providing input for a user, and obtains data input by the user; and processor 1501 may be operative to invoke the resource management application stored in memory 1505 and to perform the following operations in particular:
Acquiring target resource data and determining a corresponding target model based on the target resource data;
acquiring a target model relation between the target model and other models;
And calculating and storing the target data relation between the target resource data and the corresponding resource data in other models according to the target model relation.
In one embodiment, before the processor 1501 executes the obtaining the target resource data, the method further comprises:
Acquiring sample type information of at least one type and sample common attribute information corresponding to each sample type information;
And determining corresponding sample models according to the sample type information, and determining sample code generation rules and sample model relations corresponding to the sample models according to the common attributes of the samples.
In one embodiment, when the processor 1501 executes the acquisition target resource data, the specific execution is:
Receiving newly-added resource data uploaded by a user, and inquiring whether the newly-added resource data has a corresponding unique code or not;
and if the new resource data does not have the corresponding unique code, taking the new resource data as target resource data.
In one embodiment, when the processor 1501 executes the determining a corresponding target model based on the target resource data, the specific execution is:
determining corresponding target metadata based on the type information of the target resource data;
and determining a target model corresponding to the target resource data according to the target metadata.
In one embodiment, after executing the determining the corresponding target model based on the target resource data, the processor 1501 is further configured to execute:
Receiving a model modification instruction, and modifying target metadata of the target model based on the model modification instruction, wherein the target metadata corresponds to the target model relation;
And taking the modified target model as a target model corresponding to the target resource data.
In one embodiment, when the processor 1501 executes the process of obtaining the target model relationship between the target model and other models, the process specifically includes:
acquiring target metadata of the target model, and determining metadata relations in the target model and the other models based on the target metadata;
And determining a target model relation between the target model and other models in the sample model relation according to metadata relations in the target model and the other models.
In one embodiment, when the processor 1501 executes the target data relationship between the target resource data and the corresponding resource data in the other models according to the target model relationship, the specific execution is:
generating a unique code corresponding to the target resource data according to the target code generation rule and the attribute information;
And determining a target data relationship between the target resource data and corresponding resource data in other models based on the target model relationship and the unique code, and storing the target data relationship.
In one embodiment, when the processor 1501 executes the target data relationship between the target resource data and the corresponding resource data in the other models according to the target model relationship, the specific execution is:
storing the original data corresponding to the target resource data and the target data relation in a relation database;
and updating an index database and a graph database based on the target data relationship.
In one embodiment, after executing the target data relationship between the target resource data and the corresponding resource data in the other model according to the target model relationship, the processor 1501 is further configured to execute:
Generating a corresponding data interface based on metadata of each model;
receiving a query instruction based on the data interface; wherein, the inquiry instruction carries an inquiry code;
and acquiring the data relationship of the resource data corresponding to the query code according to the query code.
The technical concept of the embodiment of the present application is the same as that of fig. 2 or fig. 3, and the specific process may refer to the method embodiment of fig. 2 or fig. 3, which is not repeated here.
In the embodiment of the application, the target resource data is acquired, the corresponding target model is determined based on the target resource data, the target model relation between the target model and other models is acquired, and the target data relation between the target resource data and the corresponding resource data in other models is calculated and stored according to the target model relation. The electronic equipment can quickly and conveniently determine the relation among the resource data according to the corresponding models and the corresponding model relations of each type of resource data by defining different models corresponding to different resource types and determining the relation among the different models, does not need to introduce additional complex secondary development, can modify the relation among the target models and the models at any time according to the requirements of users, realizes the modification of the relation among the resource data of different types, and reduces the complexity of multi-department resource data management.
Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored on a computer readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory, a random access memory, or the like.
The foregoing disclosure is illustrative of the present application and is not to be construed as limiting the scope of the application, which is defined by the appended claims.