[go: up one dir, main page]

CN117931438A - Data resource management method and system for business team - Google Patents

Data resource management method and system for business team Download PDF

Info

Publication number
CN117931438A
CN117931438A CN202410082418.5A CN202410082418A CN117931438A CN 117931438 A CN117931438 A CN 117931438A CN 202410082418 A CN202410082418 A CN 202410082418A CN 117931438 A CN117931438 A CN 117931438A
Authority
CN
China
Prior art keywords
management
team
data
file
api
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202410082418.5A
Other languages
Chinese (zh)
Inventor
辛全艳
孙权
刘思琪
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhongxing Smart Cloud Enterprise Shandong Technology Co ltd
Original Assignee
Zhongxing Smart Cloud Enterprise Shandong Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Zhongxing Smart Cloud Enterprise Shandong Technology Co ltd filed Critical Zhongxing Smart Cloud Enterprise Shandong Technology Co ltd
Priority to CN202410082418.5A priority Critical patent/CN117931438A/en
Publication of CN117931438A publication Critical patent/CN117931438A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/50Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

A data resource management method and system for business team, physical model management, logical model management, file metadata management and index metadata management are carried out through metadata management; adding basic information and field information to the created physical model through physical model management, and performing blood margin analysis and influence analysis on the created physical model; creating a logic table through logic model management to form a logic model; performing API approval, API authorization, application authorization and component arrangement through data opening processing; performing release state management on released services through API approval; exposing the applied service through API authorization; granting access to the specified service to the current application by application authorization; user access verification, access parameter conversion, access parameter decoding and return transcoding are performed through component arrangement. The invention realizes the efficient management of the data among team members and reduces the data redundancy.

Description

Data resource management method and system for business team
Technical Field
The invention belongs to the technical field of data processing, and particularly relates to a data resource management method and system for a business team.
Background
Data management, i.e., management of data resources. Data resource management, as defined by the international data management association, aims to develop appropriate constructs, policies, practices and procedures for handling enterprise data lifecycles. Data management is commonly performed by data analysis, data modeling, database management, data warehouse, data mining, data security, data integration, data movement, data quality assurance, metadata management, strategic data architecture, and the like.
At present, for team users, a large amount of data is usually involved in the process of service development, each team has own resources such as models and files, and in the practical process, the same data resources are usually kept in one part for each team member, so that great data redundancy is caused. In the prior art, a data resource management scheme suitable for a business team is lacked, so that each link of team members in the data management process is opened, and the data redundancy among the team members is reduced.
Disclosure of Invention
Therefore, the invention provides a data resource management method and a system for business team to open each link of team members in the data management process and reduce the data redundancy among team members.
In order to achieve the above object, the present invention provides the following technical solutions: a data resource management method for a business team, comprising:
Metadata management including physical model management, logical model management, file metadata management, and index metadata management; adding basic information and field information to the created physical model through the physical model management, and performing blood margin analysis and influence analysis on the created physical model; creating a logic table through the logic model management to form a logic model, and storing model information, field information and field mapping data by utilizing the logic table; managing file metadata through the file metadata management, wherein the file metadata comprises a server, a file theme, a file directory and a file source; managing index metadata through the index metadata management comprises managing the index metadata, wherein the index metadata comprises business basic information and format information;
Data opening processing, through which API approval, API authorization, application authorization and component arrangement are performed; performing release state management on the released service through the API approval; carrying out API coding, API name, application name, user, effective time, failure time and authorization status display on the applied service through the API authorization; granting, by the application authorization, rights to access a specified service to a current application; user access verification, access parameter conversion, access parameter decoding and return transcoding are performed through the component arrangement.
The data resource management method for the business team also comprises a control center design, wherein the control center is used for carrying out system menu management, system authority management, system resource management, system team management and flow management;
in the system menu management process, the menu types comprise a main menu, a left tree menu, a middle filling menu and a new window menu;
In the system authority management process, a menu is accessed through a role management page in a role distribution manner, and then a role with menu authority is assigned to a user through a user management page;
In the system resource management process, the database and the server resource are configured, maintained and managed;
In the system team management process, checking the current team and all sub-teams of the current team, managing team users, editing team information, and modifying team names, superordinate teams and team state information;
in the process of flow management, the logical model, the physical model and the program are managed in an online-offline mode.
As a preferred scheme of the data resource management method for the business team, arranging contents for user access verification through the component, including whether Token information and AppKey of the user are correct or not, and whether the request user is granted permission to access the designated API or not;
When the user access verification is passed, the next process node is executed, the user access verification fails, and a message prompt that the Token is incorrect or the AppKey is illegal is returned.
As a data resource management method preferred scheme for a business team, verifying whether parameters carried in an access request lack parameters necessary for inputting parameter configuration and whether parameter names are consistent with the parameter configuration in the process of checking the access parameters through the component arrangement;
After the parameter verification is passed, the execution of the next flow node is transferred, the verification fails, and a message prompt of 'incorrect parameter' or 'no necessary specified parameter' is returned.
As a preferred scheme of the data resource management method for the business team, in the process of carrying out access parameter conversion through the component arrangement, the appointed parameters of the service request are converted into appointed columns through an encryption or decryption algorithm appointed in API parameter configuration.
As a data resource management method preferred scheme for a business team, decoding parameter information received by an API service in the process of decoding access parameters through the component arrangement;
And in the process of returning the transcoding through the arrangement of the components, the data returned by the service request is integrally encrypted and transcoded.
As a preferred scheme of the data resource management method for the business team, the method further comprises the steps of file agent, hbase inquiry, http agent, JS script execution, sql inquiry, file uploading and webService agent through the component arrangement.
As a preferred scheme of the data resource management method for the business team, the method further comprises standardized management, wherein the standardized management comprises theme configuration, table field naming standard management, table naming standard management, dimension code value mapping, business standard management and meta-model standard management;
The quality management comprises quality inspection reports, logic/physical model rule configuration and quality inspection details; logical/physical model rule configuration includes rule configuration specification, null check, referential integrity check, value field check, script check, specification check, and fluctuation check;
Subscription management is also included, including model subscription management, file subscription management, and file subscription approval.
The invention also provides a data resource management system for a business team, comprising:
The metadata management module is used for performing metadata management, wherein the metadata management comprises physical model management, logical model management, file metadata management and index metadata management; adding basic information and field information to the created physical model through the physical model management, and performing blood margin analysis and influence analysis on the created physical model; creating a logic table through the logic model management to form a logic model, and storing model information, field information and field mapping data by utilizing the logic table; managing file metadata through the file metadata management, wherein the file metadata comprises a server, a file theme, a file directory and a file source; managing index metadata through the index metadata management comprises managing the index metadata, wherein the index metadata comprises business basic information and format information;
The data opening module is used for data opening processing, and performing API approval, API authorization, application authorization and component arrangement through the data opening processing; performing release state management on the released service through the API approval; carrying out API coding, API name, application name, user, effective time, failure time and authorization status display on the applied service through the API authorization; granting, by the application authorization, rights to access a specified service to a current application; user access verification, access parameter conversion, access parameter decoding and return transcoding are performed through the component arrangement.
The system is characterized by also comprising a control center module, a control center module and a data management module, wherein the control center module is used for designing a control center and carrying out system menu management, system authority management, system resource management, system team management and flow management through the control center;
in the system menu management process, the menu types comprise a main menu, a left tree menu, a middle filling menu and a new window menu;
In the system authority management process, a menu is accessed through a role management page in a role distribution manner, and then a role with menu authority is assigned to a user through a user management page;
In the system resource management process, the database and the server resource are configured, maintained and managed;
In the system team management process, checking the current team and all sub-teams of the current team, managing team users, editing team information, and modifying team names, superordinate teams and team state information;
in the process of flow management, the logical model, the physical model and the program are managed in an online-offline mode.
As a preferred scheme of the data resource management system for the business team, the content for user access verification through the component arrangement in the data opening module comprises whether Token information and AppKey of the user are correct or not and whether the request user is granted permission for accessing the appointed API or not;
In the data opening module, when user access verification passes, the execution of the next flow node is shifted, the user access verification fails, and a message prompt that the Token is incorrect or the AppKey is illegal is returned;
In the data opening module, verifying whether parameters carried in the access request lack parameters necessary for inputting parameter configuration and whether parameter names are consistent with the parameter configuration;
In the data opening module, after the parameter verification is passed, the execution of the next flow node is transferred, the verification fails, and a message prompt of incorrect parameter or unnecessary specified parameter is returned;
In the data opening module, specified parameters of the service request are converted into specified columns through an encryption or decryption algorithm specified in API parameter configuration;
In the data opening module, decoding parameter information received by the API service; carrying out integral encryption transcoding on the data returned by the service request;
the data opening module is also used for carrying out file proxy, hbase inquiry, http proxy, JS script execution, sql inquiry, file uploading and webService proxy through the component arrangement.
As a preferred scheme of the data resource management system for the business team, the system further comprises a standardized management module for standardized management, wherein the standardized management comprises theme configuration, table field naming standard management, table naming standard management, dimension code value mapping, business standard management and meta-model standard management.
As a preferred scheme of the data resource management system for the business team, the system further comprises a quality management module for quality management, wherein the quality management comprises quality inspection report, logic/physical model rule configuration and quality inspection detail; logical/physical model rule configurations include rule configuration specification, null check, referential integrity check, value field check, script check, specification check, and fluctuation check.
As a preferred scheme of the data resource management system for the business team, the system further comprises a subscription management module for carrying out subscription management, wherein the subscription management comprises model subscription management, file subscription management and file subscription approval.
The invention has the following advantages: physical model management, logical model management, file metadata management and index metadata management are performed through metadata management; adding basic information and field information to the created physical model through the physical model management, and performing blood margin analysis and influence analysis on the created physical model; creating a logic table through the logic model management to form a logic model, and storing model information, field information and field mapping data by utilizing the logic table; managing file metadata through the file metadata management, wherein the file metadata comprises a server, a file theme, a file directory and a file source; managing index metadata through the index metadata management comprises managing the index metadata, wherein the index metadata comprises business basic information and format information; performing API approval, API authorization, application authorization and component arrangement through data opening processing; performing release state management on the released service through the API approval; carrying out API coding, API name, application name, user, effective time, failure time and authorization status display on the applied service through the API authorization; granting, by the application authorization, rights to access a specified service to a current application; user access verification, access parameter conversion, access parameter decoding and return transcoding are performed through the component arrangement. The invention realizes the efficient management of data among team members, achieves the aim of sharing team resources, and further solves the problem of data redundancy; and each link of data management is conveniently opened, and various different data management scenes of enterprises are rapidly met.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below. It will be apparent to those skilled in the art from this disclosure that the drawings described below are merely exemplary and that other embodiments may be derived from the drawings provided without undue effort.
Fig. 1 is a schematic flow chart of a data resource management method for a business team according to an embodiment of the present invention;
Fig. 2 is a schematic diagram of a data resource management system architecture for a business team according to an embodiment of the present invention.
Detailed Description
Other advantages and advantages of the present invention will become apparent to those skilled in the art from the following detailed description, which, by way of illustration, is to be read in connection with certain specific embodiments, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Example 1
Referring to fig. 1, embodiment 1 of the present invention provides a data resource management method for a business team, including the following steps:
S1, metadata management, wherein the metadata management comprises physical model management, logical model management, file metadata management and index metadata management; adding basic information and field information to the created physical model through the physical model management, and performing blood margin analysis and influence analysis on the created physical model; creating a logic table through the logic model management to form a logic model, and storing model information, field information and field mapping data by utilizing the logic table; managing file metadata through the file metadata management, wherein the file metadata comprises a server, a file theme, a file directory and a file source; managing index metadata through the index metadata management comprises managing the index metadata, wherein the index metadata comprises business basic information and format information;
S2, data opening processing, namely performing API approval, API authorization, application authorization and component arrangement through the data opening processing; performing release state management on the released service through the API approval; carrying out API coding, API name, application name, user, effective time, failure time and authorization status display on the applied service through the API authorization; granting, by the application authorization, rights to access a specified service to a current application; user access verification, access parameter conversion, access parameter decoding and return transcoding are performed through the component arrangement.
In this embodiment, in step S1, metadata management is to uniformly manage and control metadata objects. The metadata objects controlled comprise tables, files, indexes and the like, and the specific objects controlled are based on actual requirements of the site. Metadata objects can be visually seen through metadata management (providing conditional query functionality), and various attribute values of the metadata objects can be viewed and modified, added and deleted.
In the metadata management process, a new physical model is created through a new model, basic information of the model and field information of the model are required to be filled in by adding the physical model, the selected physical model can be modified through editing icons, the selected physical model is deleted through deleting icons, and the blood-edge analysis, the influence analysis, the field blood-edge and the field influence of the physical model can be checked through blood-edge and influence.
Specifically, the basic information of the "newly added model" needs to select information such as a database, a user theme, a hierarchy, a period, a life cycle, and the like, in addition to filling in a model name. The field information is added through the newly added field, and besides the field English name and the field Chinese name, the field information also comprises information such as field type, length precision primary key constraint, non-null constraint, default value, remarks and the like. The blood edge graph (comprising the relationship among the three data of the table, the associated object and the field) of the current physical model is checked through blood edge analysis. The results of the current model impact analysis can be viewed through the impact analysis.
In this embodiment, in step S1, in the logical model management process, the newly created logical model is a model table, for example, a certain model table is created as User, instead of actually creating a table in the database, only the model information, the field information and the field information mapped to a specific certain table of a specific database are recorded.
The newly added logic model needs to be input information comprises basic information, field information and field mapping of the logic model, once the logic model is successfully connected with the line, a physical model generated by mapping the logic model is successfully connected with the line, and input items of the logic model are displayed according to form items input in standardized management, so that basic information of the meta model needing to be input can be expanded. Mapping fields are implemented in filling in the table names in the database by selecting the database to which the logical model field information maps.
In this embodiment, in step S1, file metadata is managed, including management of file metadata information configuration such as server, theme, file directory, and file source. The file metadata can be deleted in batches by multiple options, and the corresponding file metadata can be edited and deleted in operation.
Wherein, a file metadata can be newly added through the 'newly added' button, and the file metadata comprises:
filename ]: i.e. the name of the file;
[ located server ]: the server where the file is located, namely the source of the file;
folder path: the path of the file;
file type: the types of the files comprise csv and txt;
[ File Divider ]: dividing symbols between a plurality of files;
life cycle: lifecycle of the file;
[ character set ]: the character set of the file comprises UTF-8, GBK and GB2312.
In this embodiment, in step S1, the index metadata is managed, including basic information such as meaning of service, service range, service condition, calculation formula of service, etc., format information such as index format, length accuracy, etc., and information such as attribution department, formulation basis, etc.
In this embodiment, in the process of data open processing in step S2, the functions of displaying, adding, modifying, deleting, testing and publishing services are implemented through service management, after one service is published, all services with the status of "in-publish" are approved and displayed through API, service classification is displayed through service names, and by clicking a button in a service state of a certain publish state, a prompt box for changing the service into the status of "publish" is popped up.
In the process of API authorization, a user can apply for service in a resource catalog page, the API authorization process displays all applied services and related information, and main information comprises API codes, API names, application names, users, effective time, expiration time and authorization states, and the application names of the applicant are filtered and displayed.
By clicking an editing icon behind a certain service application form, a modification frame of information such as the state of the application form is popped up, and specific information of the modification frame comprises service names, application names, users, API call times limitation, effective dates, expiration dates and states. After the information is set, changing the state into authorized state, and realizing approval operation of the service application form through a 'determination' button.
The user can apply for related service resources on the resource catalog page, and then the administrator approves the service application form in the background, so that the authorization operation of the service to the user is realized. The background manager can also directly authorize the application to a certain user in the background without requiring the user to apply for related resources on the resource catalog page. And clicking the newly added icon on the service authorization information display page to pop up a service authorization pop-up box, wherein the specific information of the pop-up box comprises a service name, an application name, a user, an API call frequency limit, an effective date, an expiration date and a state.
In this embodiment, in step S2, the current application is granted with the right to access the specified service, the activated or deactivated application may be checked, the input search content may be queried in a related manner, the application may be authorized by the corresponding new button, the authorization information may be modified by the corresponding edit button at the information back end, and the corresponding authorization information may be deleted by the corresponding delete button.
Wherein, click the newly added button, newly add the authorization, fill information according to the requirement, click "confirm" button and save. Clicking a modification button to edit the selected authorization information, and clicking a 'determination' button to save the authorization information after modification is completed. Clicking the delete button to delete the corresponding authorization information. Clicking the "ok" button confirms the deletion of this information.
In this embodiment, in step S2, the user access authentication node is a module for authenticating whether the access request has authority to use the specified API. The authentication content includes whether the Token information and AppKey of the user are correct, and whether the requesting user is granted rights to access the specified API. After passing the access verification, the next process node is transferred to execute, and if the access verification fails, message prompts such as incorrect Token or illegal AppKey are returned
In step S2, the parameter check is used to verify whether the parameters carried in the access request meet the requirements of the API in the input parameter configuration. If yes, whether the optional parameters are absent, whether the parameter names are consistent with the parameter configuration, and the like. After the parameter verification is passed, the execution of the lower flow node is transferred, and if the verification fails, message prompts such as 'incorrect parameters' or 'unnecessary xxx parameters' are returned.
In step S2, the parameter conversion refers to a process of converting specified parameters of the service request into specified columns by an encryption or decryption algorithm specified in the API parameter configuration. The node can be used by being dragged into the function arrangement area without setting the node. But the ticket specifies the encryption or decryption policy of the parameter in the input parameter configuration. Encryption or decryption policies may be set in security management-rule management.
In step S2, in order to avoid interception and analysis of the information of the API service request during network transmission, a specified algorithm is provided to encrypt the parameters in its entirety. And decoding the parameter information received by the API service through parameter decoding, wherein the parameter decoding nodes can be used after being dragged into the function arrangement area, and node setting is not needed. But this step requires the API service requestor to encrypt the parameters in their entirety using a system-specific algorithm. In step S2, the return transcoding refers to a process of performing overall encryption transcoding on the data returned by the service request. The node can be used by being dragged into the function arrangement area without setting the node.
In one possible embodiment, the system further comprises a control center design, wherein the control center is used for carrying out system menu management, system authority management, system resource management, system team management and flow management;
in the system menu management process, the menu types comprise a main menu, a left tree menu, a middle filling menu and a new window menu;
In the system authority management process, a menu is accessed through a role management page in a role distribution manner, and then a role with menu authority is assigned to a user through a user management page;
In the system resource management process, the database and the server resource are configured, maintained and managed;
In the system team management process, checking the current team and all sub-teams of the current team, managing team users, editing team information, and modifying team names, superordinate teams and team state information;
in the process of flow management, the logical model, the physical model and the program are managed in an online-offline mode.
Specifically, in the system menu management page, the menu types are divided into: main menu, left tree menu, middle filling menu, new window menu, and the like. Main Menu: a channel page menu. [ left tree menu ]: after clicking the main menu, entering the menu of the page. [ middle fill menu ]: after clicking, the left tree menu is not available. New window menu: after clicking, a new window is opened. Clicking the new main menu can add the system menu and clicking the adding submenu, clicking the menu for the corresponding menu adding submenu, then editing the icon, editing the corresponding menu, clicking the deleting icon, and deleting the corresponding menu and submenu. [ Menu type ]: the various menu types are described in detail above. [ Menu Address ]: the jump address after clicking the menu. State (state): whether the menu is used. The enabling indicates that the menu can be used normally, and the disabling indicates that the menu cannot be used. Picture (c): icons representing menus. [ Menu order ]: representing the position of a menu in a menu bar, wherein 0 is arranged at the forefront; remarks @. Menu related remark information.
Specifically, the menu is allocated to the corners through the role management page, then the roles with menu authority are given to the user through the user management page, and the user can have the authority to access the menu module. The role management page may view the roles owned by the current team, as well as the menu access rights owned by the personal roles. The method can manage the roles and modify the menu authorities corresponding to the roles, and after the menu authorities are modified, the key point is to click a save button to save the modification so as to take effect. Clicking the "new" button to add a character and clicking the "modify" button to modify the selected character information. [ role coding ]: i.e. the code of the character, which code value is unique. [ character name ]: the Chinese name of the character is roughly described by the diagonal color. [ team to whom ]: when the affiliated team selects all teams, the role is described as a public role of the system, and when a certain appointed team is selected, the role is described as a private role of the team. [ role State ]: indicating whether the character can be used normally.
Specifically, the system resource management refers to configuration maintenance management of system resources such as databases and server resources. All database resources in the current system can be viewed in the database resource management page. Clicking on the "Add" button may add the database to the current team, and clicking on the "modify" button may modify the basic information of the selected database. After the database is selected, a right side 'add' button can be clicked to add the database user for the database. The server management page can check the server of the current system to maintain and manage the server host information which can be used in the development work. For example, the data processing module involves uploading and uploading files, and FTP host information required for uploading and downloading the files is recorded and maintained here. Clicking the "newly added" button to add new server resources for the current team, and filling in the system type of the server (if the operating system is Linux, information such as IP address, port number, user information, transmission protocol, character set, file transmission type, etc. needs to be filled in, and if the operating system type is Windows, information such as file catalogue, etc. needs to be filled in). Clicking on the "modify" button may modify the selected server resource.
Specifically, for better system rights management, the platform is operated in team units, and the user operated data must be data that has been authorized for the current team, or created by the current team itself. Team management can view the current team and all sub-teams of the current team, can manage team users, edit team information, modify related information such as team names, superior teams, team states and the like. Clicking on the blank card creates a new team. Team coding: the team is in the system, and the code value is unique. Team name: team's chinese name, this value is unique. [ superordinate team ]: which team the team belongs to. [ affiliated administrative division ]: which administrative district the team belongs to. [ team user ]: and managing team users and adding team users. [ team status ]: indicating whether the team can use it normally. The team user manages all users in the page under the team to which the user belongs, and can maintain the roles of the users and move the users out of the team. Clicking on the "Add user" button may add or remove users for the team. Clicking on "role maintenance" assigns the user role. And clicking logic model authorization to authorize data in the data authorization page to authorize a logic model for the team and granularity to a field. After the logical model is authorized for a team, the team may create an API service for this logical model (authorized field). Database resources and server resources that have been authorized for the individual team can be viewed in the team resource configuration page. The team may also be assigned configured database resources and server resources in system resource management. After selecting the team, the "allocate public library" and "allocate public server" buttons may be clicked to allocate database resources and server resources for the team.
In one possible embodiment, the method further comprises the steps of file proxy, hbase query, http proxy, JS script execution, sql query, file upload and webService proxy through the component orchestration.
Specifically, the file proxy may obtain the file existing on the server through the API. After the node is dragged into the function arrangement area, whether the server address, the source file type and the file separator output the compressed file or not needs to be set on the setting page. The API with this node needs to include flePath parameters in the service request, otherwise it will return "file address is empty" and when this file is not present on the server, the system will return "file not present".
Specifically, hbase inquiry directly inquires hbase by using a get/scan mode, and after the node acquires the data returned by hbase and drags the data into a function arrangement area, the inquiry mode of setting a data source and timeout time (default not timeout) in a set page is needed. The scan-style query is provided by setting parameters htable, startRowKey, endRowKey and the get-style query is provided by setting parameters htable, rowkey.
Specifically, after the data returned by the proxy service is obtained through the http protocol and the node is dragged into the function arrangement area, the proxy address and the overtime (default not overtime) request type are required to be set on the set page. The proxy API request may proxy the parameters of the service consumer to the service provider. This functionality may be used when an http request needs to be proxied through the open platform.
Specifically, the JS script opens a function of embedding and executing the JS script in order to meet a specific application scenario, and after the node drags into the function arrangement area, the JS script that can be executed in the system needs to be input in the setting page. And directly querying the relational database by using the SQL script, and after the function of acquiring the data returned by the SQL script is dragged into a function arrangement area by the node, setting SQL sentences and data source information on a setting page. The SQL may contain zero to multiple dynamic parameters in the format @ PPARAM NAME ], where PARAM NAME (parameter name) needs to be configured in the input parameter configuration.
Specifically, after the node drags into the function arrangement area, the FTP address and the file parameter name need to be set on the setting page. After the node drags into the functionally orchestrated area, it needs to set proxy address, request mode, timeout time (default not timeout) at the setup page to request type proxy API requests to proxy the parameters of the service consumer to the service provider.
In one possible embodiment, the method further comprises standardized management, wherein the standardized management comprises theme configuration, table field naming standard management, table naming standard management, dimension code value mapping, service standard management and meta-model standard management.
Specifically, related objects such as related topic association databases, programs and the like are selected for topic configuration of the data. More careful sorting of the data makes it easier to find and use the relevant data. By clicking the new theme of the new theme set, sub-level themes, peer themes, editing themes and deleting themes can be added in the operation column. Clicking the "add" button in the topic association object may add binding objects for the topic, including objects such as databases, logical models, file metadata, and the like. Modifying the associated object requires clicking on "save" the modification to take effect.
Specifically, the table field naming standard management performs naming standards on table names, table fields and the like, words with extremely high frequency use are designated as standard elements, the naming standards have guiding effects on standard formulation after users and certain naming recommendation functions of the system, and the data can be conveniently searched, so that the whole system is clearer and more beneficial to operation and maintenance. Clicking "add" can newly add field standard configuration, the field Chinese name is unique, if the newly added field Chinese name is the field already contained in the system, the newly added field fails.
Specifically, not only is the specification of naming the table fields needed, but also the specification of naming the table names, for example, naming the table names in the mode of theme database xxx, and displaying which theme the table names belong to and which database more clearly. The source of the data is more clear and visible, and the whole system is clearer and more beneficial to operation and maintenance. Clicking the new rule can add the table naming standard, selecting one rule, clicking the back-end editing button can edit and modify the rule information, clicking the deleting button can delete the rule information.
Specifically, the system is set in each dimension, so that management and maintenance of various data are facilitated. Clicking the "add" button adds a new main dimension. The icon is added in the operation column to add a child dimension for the main dimension, edit the icon to edit the corresponding dimension, and delete the icon to delete the corresponding main dimension and the related dimension. The dimension code value mapping realizes the mapping corresponding relation between the dimension code value and each service system.
Specifically, standard management is performed on the service. Basic information such as coding, topic classification, standard meaning and the like of the service standard is contained, and meanwhile, data category information such as data category, data length precision, measurement units and the like is also included. The meta-model standard management adds and maintains the attributes of the system, such as the theme, the life cycle and the like, and is convenient for users to master and use the data.
In one possible embodiment, further comprising quality management including quality inspection reports, logical/physical model rule configurations, and quality inspection details; logical/physical model rule configurations include rule configuration specification, null check, referential integrity check, value field check, script check, specification check, and fluctuation check.
Specifically, the data quality dimensions include consistency, accuracy, integrity, rationality, integrity, uniqueness. The quality management is that the data is configured by the rules of the data, then the corresponding rules are executed on the data, whether the data is qualified or not is detected, and the checking result of the data is intuitively displayed in a chart mode, so that the composition of the data is conveniently known. The unqualified data are marked, so that a user can accurately know which data are unqualified and do not accord with what rules, and the unqualified data can be conveniently tidied and modified in the later period.
Specifically, the quality inspection report is implemented by a data quality trend table, and includes information such as an inspected database, the total number of inspections, the number of anomalies inspected, and the percentage of the number of anomalies.
Specifically, the logical/physical model rule configuration is divided into two dimensions, tables/rules. Looking up the table of configured rules and the table of unconfigured rules. Clicking on the table name may perform operations such as adding check rules, configuring schedules, executing (immediately checking), removing (canceling checking), etc. Adding a checking rule: each rule configuration refers to a physical table and a configuration of rules. Description of the inspection content of the rule is described, which is equivalent to a general title, so that the inspection content and intention of the rule inspection can be intuitively understood. The minimum granularity of the execution check is executed according to a physical table, the priority execution check with high importance level is executed by checking only partial data, and the field is English name XXX.
After the execution time is configured on the table, the quality inspection is executed by taking the table as a unit according to the configured execution time, and the scheduled configuration information can be checked in the scheduling management of the operation and maintenance monitoring channel page.
Wherein, look over according to the rule: the left side shows the name of the configurable rule in the system and the number of configurations of the corresponding rule. The right side is the data on which the rule is configured.
Specifically, the rule configuration indicates that data quantity comparison is realized, a data table (a target table and an original table) to be compared is selected, fields of the table are selected to be filtered, and then the data of the target table and the original table are compared. Null value checking is performed by selecting a field that cannot be null, the field is multi-selected, and if the checked field is null, the piece of data is abnormal.
Specifically, in the process of checking the referential integrity, whether a field of the check list belongs to a certain dimension or not, or in the customized query data, the field is a single choice. [ reference type ]: dimension/custom, dimension is the dimension defined in the dimension standard management of standardized management. Wherein the reference field refers to the content of which field in the query result in the cited sql script.
Specifically, in the value range checking process, whether the field value in the physical table is in the value range is checked, a plurality of fields can be configured for checking, and if the checked field value of a certain piece of data is not in the value range, the value is the abnormal data value range.
Specifically, the script checking process checks whether the script is successfully queried and has data. The check field format is checked to be standard in the standard check process, a plurality of check fields can be selected, and if not, the check field format is abnormal data.
Specifically, in the process of fluctuation inspection, whether the cycle of ring ratio/homocycle of data in a certain field is normal or not is counted. The comparison type is that the same ratio/ring ratio is compared with the same month of the last year, the ring ratio is compared with the previous month [ fluctuation range ]: the increase rate of the same ratio ring ratio according to the statistical result of the statistical function, and the data passing the examination are in the fluctuation range. [ time field ]: when comparing with the ring ratio, the time field [ time field format ] is referred to: the format of the selected time field. Subscription management is also included, including model subscription management, file subscription management, and file subscription approval.
Specifically, the quality inspection details are the states of the data (normal and abnormal part data does not accord with the rule) which are executed by inspecting the table data according to the configured rule.
In a possible embodiment, the system further comprises a subscription management module, wherein the subscription management module is used for carrying out subscription management, and the subscription management comprises model subscription management, file subscription management and file subscription approval.
Specifically, each team has its own resources such as models and files, and if the same resources are kept in one share, then a large data redundancy will be caused. The method can share the resources such as the own model and the file with other teams, so as to achieve the purpose of resource sharing, and further solve the problem of data redundancy. And browsing basic profiles of the team data through the home page, wherein the basic profiles comprise resource profiles, data profiles, team resource conditions of data exchange and data catalogs, subscription conditions and the like.
The model subscription management process subscribes to resources from other teams, and can click on 'newly added subscription' to enter a data catalog to newly added subscription. Clicking an operation bar editing icon to edit and modify the subscribed model, clicking a deleting icon to delete the subscribed model.
In the file subscription management process, the subscribed file resources are checked, and the new subscription can be clicked to enter the data directory subscription file. Clicking an operation bar editing icon to enter a file subscription flow to modify the flow of subscribed files, clicking a deletion icon to delete the subscribed files. In the file subscription approval process, after the file subscription application is proposed, approval personnel are required to approve the application and control the application.
In summary, the present invention includes metadata management, including physical model management, logical model management, file metadata management, and index metadata management; adding basic information and field information to the created physical model through the physical model management, and performing blood margin analysis and influence analysis on the created physical model; creating a logic table through the logic model management to form a logic model, and storing model information, field information and field mapping data by utilizing the logic table; managing file metadata through the file metadata management, wherein the file metadata comprises a server, a file theme, a file directory and a file source; managing index metadata through the index metadata management comprises managing the index metadata, wherein the index metadata comprises business basic information and format information; data opening processing, through which API approval, API authorization, application authorization and component arrangement are performed; performing release state management on the released service through the API approval; carrying out API coding, API name, application name, user, effective time, failure time and authorization status display on the applied service through the API authorization; granting, by the application authorization, rights to access a specified service to a current application; user access verification, access parameter conversion, access parameter decoding and return transcoding are carried out through the assembly arrangement; the system also comprises a control center design, and performs system menu management, system authority management, system resource management, system team management and flow management through the control center; in the system menu management process, the menu types comprise a main menu, a left tree menu, a middle filling menu and a new window menu; in the system authority management process, a menu is accessed through a role management page in a role distribution manner, and then a role with menu authority is assigned to a user through a user management page; in the system resource management process, the database and the server resource are configured, maintained and managed; in the system team management process, checking the current team and all sub-teams of the current team, managing team users, editing team information, and modifying team names, superordinate teams and team state information; in the process of flow management, performing on-line and off-line management of a logic model, a physical model and a program; content for user access verification through the component arrangement comprises whether Token information and AppKey of the user are correct or not and whether the request user is granted permission for accessing a specified API or not; when the user access verification is passed, the next process node is executed, the user access verification fails, and a message prompt that the Token is incorrect or the AppKey is illegal is returned; in the process of checking the access parameters through the component arrangement, verifying whether the parameters carried in the access request lack the parameters necessary for inputting the parameter configuration and whether the parameter names are consistent with the parameter configuration; after the parameter verification is passed, the execution of the next flow node is transferred, the verification fails, and a message prompt of 'incorrect parameter' or 'no necessary specified parameter' is returned; in the process of carrying out access parameter conversion through the component arrangement, converting appointed parameters of a service request into appointed columns through an appointed encryption or decryption algorithm in API parameter configuration; decoding parameter information received by the API service in the process of decoding the access parameters through the component arrangement; in the process of returning the rotary codes through the arrangement of the components, the data returned by the service request is subjected to integral encryption transcoding; the method also comprises the steps of file agent, hbase inquiry, http agent, JS script execution, sql inquiry, file uploading and webService agent through the component arrangement. The invention realizes the efficient management of data among team members, achieves the aim of sharing team resources, and further solves the problem of data redundancy; and each link of data management is conveniently opened, and various different data management scenes of enterprises are rapidly met.
It should be noted that the method of the embodiments of the present disclosure may be performed by a single device, such as a computer or a server. The method of the embodiment can also be applied to a distributed scene, and is completed by mutually matching a plurality of devices. In the case of such a distributed scenario, one of the devices may perform only one or more steps of the methods of embodiments of the present disclosure, the devices interacting with each other to accomplish the methods.
It should be noted that the foregoing describes some embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments described above and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
Example 2
Referring to fig. 2, embodiment 2 of the present invention further provides a data resource management system for a business team, including:
A metadata management module 001 for performing metadata management including physical model management, logical model management, file metadata management, and index metadata management; adding basic information and field information to the created physical model through the physical model management, and performing blood margin analysis and influence analysis on the created physical model; creating a logic table through the logic model management to form a logic model, and storing model information, field information and field mapping data by utilizing the logic table; managing file metadata through the file metadata management, wherein the file metadata comprises a server, a file theme, a file directory and a file source; managing index metadata through the index metadata management comprises managing the index metadata, wherein the index metadata comprises business basic information and format information;
the data opening module 002 is used for data opening processing, and performing API approval, API authorization, application authorization and component arrangement through the data opening processing; performing release state management on the released service through the API approval; carrying out API coding, API name, application name, user, effective time, failure time and authorization status display on the applied service through the API authorization; granting, by the application authorization, rights to access a specified service to a current application; user access verification, access parameter conversion, access parameter decoding and return transcoding are performed through the component arrangement.
In this embodiment, the system further includes a control center module 003, configured to perform system menu management, system authority management, system resource management, system team management, and flow management through the control center;
in the system menu management process, the menu types comprise a main menu, a left tree menu, a middle filling menu and a new window menu;
In the system authority management process, a menu is accessed through a role management page in a role distribution manner, and then a role with menu authority is assigned to a user through a user management page;
In the system resource management process, the database and the server resource are configured, maintained and managed;
In the system team management process, checking the current team and all sub-teams of the current team, managing team users, editing team information, and modifying team names, superordinate teams and team state information;
in the process of flow management, the logical model, the physical model and the program are managed in an online-offline mode.
In this embodiment, in the data opening module 002, the content for user access verification through the component arrangement includes whether the Token information and the AppKey of the user are correct, and whether the request user is granted permission to access the specified API;
In the data opening module 002, when the user access verification passes, the execution of the next flow node is shifted, the user access verification fails, and a message prompt that the Token is incorrect or the AppKey is illegal is returned;
in the data opening module 002, it is verified whether the parameters carried in the access request lack the parameters necessary for inputting the parameter configuration, and whether the parameter names are consistent with the parameter configuration;
in the data opening module 002, after the parameter verification is passed, the execution of the next flow node is transferred, the verification fails, and a message prompt of "incorrect parameter" or "no necessary specified parameter" is returned;
in the data opening module 002, the specified parameters of the service request are converted into specified columns through an encryption or decryption algorithm specified in the API parameter configuration;
The data opening module 002 decodes the parameter information received by the API service; carrying out integral encryption transcoding on the data returned by the service request;
The data opening module 002 is further configured to perform file proxy, hbase query, http proxy, JS script execution, sql query, file upload, and webService proxy through the component arrangement.
In this embodiment, the system further includes a standardized management module 004, configured to perform standardized management, where the standardized management includes theme configuration, table field naming standard management, table naming standard management, dimension code value mapping, service standard management, and meta-model standard management.
In this embodiment, the system further includes a quality management module 005, configured to perform quality management, where the quality management includes quality inspection reports, logic/physical model rule configurations, and quality inspection details; logical/physical model rule configurations include rule configuration specification, null check, referential integrity check, value field check, script check, specification check, and fluctuation check.
In this embodiment, the system further includes a subscription management module 006, configured to perform subscription management, where the subscription management includes model subscription management, file subscription management, and file subscription approval.
It should be noted that, because the content of information interaction and execution process between the modules of the above system is based on the same concept as the method embodiment in the embodiment 1 of the present application, the technical effects brought by the content are the same as the method embodiment of the present application, and the specific content can be referred to the description in the foregoing illustrated method embodiment of the present application, which is not repeated herein.
Example 3
Embodiment 3 of the present invention provides a non-transitory computer readable storage medium having stored therein program code for a data resource management method for a business team, the program code comprising instructions for performing the data resource management method for a business team of embodiment 1 or any possible implementation thereof.
Computer readable storage media can be any available media that can be accessed by a computer or data storage devices, such as servers, data centers, etc., that contain an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (Solid STATE DISK, SSD)), etc.
Example 4
Embodiment 4 of the present invention provides an electronic device, including: a memory and a processor;
The processor and the memory complete communication with each other through a bus; the memory stores program instructions executable by the processor, which invokes the program instructions to perform the data resource management method for a business team of embodiment 1 or any possible implementation thereof.
Specifically, the processor may be implemented by hardware or software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor, implemented by reading software code stored in a memory, which may be integrated in the processor, or may reside outside the processor, and which may reside separately.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present invention, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.).
It will be appreciated by those skilled in the art that the modules or steps of the invention described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may alternatively be implemented in program code executable by computing devices, so that they may be stored in a memory device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than that shown or described, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps within them may be fabricated into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.
While the invention has been described in detail in the foregoing general description and specific examples, it will be apparent to those skilled in the art that modifications and improvements can be made thereto. Accordingly, such modifications or improvements may be made without departing from the spirit of the invention and are intended to be within the scope of the invention as claimed.

Claims (10)

1. A method for data resource management for a business team, comprising:
Metadata management including physical model management, logical model management, file metadata management, and index metadata management; adding basic information and field information to the created physical model through the physical model management, and performing blood margin analysis and influence analysis on the created physical model; creating a logic table through the logic model management to form a logic model, and storing model information, field information and field mapping data by utilizing the logic table; managing file metadata through the file metadata management, wherein the file metadata comprises a server, a file theme, a file directory and a file source; managing index metadata through the index metadata management comprises managing the index metadata, wherein the index metadata comprises business basic information and format information;
Data opening processing, through which API approval, API authorization, application authorization and component arrangement are performed; performing release state management on the released service through the API approval; carrying out API coding, API name, application name, user, effective time, failure time and authorization status display on the applied service through the API authorization; granting, by the application authorization, rights to access a specified service to a current application; user access verification, access parameter conversion, access parameter decoding and return transcoding are performed through the component arrangement.
2. The method for data resource management for a business team according to claim 1, further comprising a control center design for performing system menu management, system authority management, system resource management, system team management and flow management by the control center;
in the system menu management process, the menu types comprise a main menu, a left tree menu, a middle filling menu and a new window menu;
In the system authority management process, a menu is accessed through a role management page in a role distribution manner, and then a role with menu authority is assigned to a user through a user management page;
In the system resource management process, the database and the server resource are configured, maintained and managed;
In the system team management process, checking the current team and all sub-teams of the current team, managing team users, editing team information, and modifying team names, superordinate teams and team state information;
in the process of flow management, the logical model, the physical model and the program are managed in an online-offline mode.
3. The data resource management method for a business team according to claim 1, wherein the contents of user access authentication through the component arrangement include whether Token information and AppKey of the user are correct, and whether the request user is granted a right to access a designated API;
When the user access verification is passed, the next process node is executed, the user access verification fails, and a message prompt that the Token is incorrect or the AppKey is illegal is returned.
4. The method for managing data resources for a business team according to claim 1, wherein in the process of checking access parameters by the component arrangement, it is verified whether the parameters carried in the access request lack the parameters necessary for inputting the parameter configuration, and whether the parameter names are consistent with the parameter configuration;
After the parameter verification is passed, the execution of the next flow node is transferred, the verification fails, and a message prompt of 'incorrect parameter' or 'no necessary specified parameter' is returned.
5. A data resource management method for a business team according to claim 1, wherein in the process of access parameter conversion by the component arrangement, specified parameters of a service request are converted to specified columns by an encryption or decryption algorithm specified in an API parameter configuration.
6. The method for managing data resources for a business team according to claim 1, wherein the parameter information received by the API service is decoded in the process of decoding access parameters by the component arrangement;
And in the process of returning the transcoding through the arrangement of the components, the data returned by the service request is integrally encrypted and transcoded.
7. The method of claim 1, further comprising scheduling file agents, hbase queries, http agents, JS script execution, sql queries, file uploads, and webService agents through the component.
8. The method of claim 1, further comprising a standardized management including a theme configuration, a table field naming standard management, a table naming standard management, a dimension code value mapping, a business standard management, and a meta model standard management;
The quality management comprises quality inspection reports, logic/physical model rule configuration and quality inspection details; logical/physical model rule configuration includes rule configuration specification, null check, referential integrity check, value field check, script check, specification check, and fluctuation check;
Subscription management is also included, including model subscription management, file subscription management, and file subscription approval.
9. A data resource management system for a business team, comprising:
The metadata management module is used for performing metadata management, wherein the metadata management comprises physical model management, logical model management, file metadata management and index metadata management; adding basic information and field information to the created physical model through the physical model management, and performing blood margin analysis and influence analysis on the created physical model; creating a logic table through the logic model management to form a logic model, and storing model information, field information and field mapping data by utilizing the logic table; managing file metadata through the file metadata management, wherein the file metadata comprises a server, a file theme, a file directory and a file source; managing index metadata through the index metadata management comprises managing the index metadata, wherein the index metadata comprises business basic information and format information;
The data opening module is used for data opening processing, and performing API approval, API authorization, application authorization and component arrangement through the data opening processing; performing release state management on the released service through the API approval; carrying out API coding, API name, application name, user, effective time, failure time and authorization status display on the applied service through the API authorization; granting, by the application authorization, rights to access a specified service to a current application; user access verification, access parameter conversion, access parameter decoding and return transcoding are performed through the component arrangement.
10. The system for data resource management for a business team according to claim 9, further comprising a control center module for control center design, system menu management, system rights management, system resource management, system team management and flow management by the control center;
in the system menu management process, the menu types comprise a main menu, a left tree menu, a middle filling menu and a new window menu;
In the system authority management process, a menu is accessed through a role management page in a role distribution manner, and then a role with menu authority is assigned to a user through a user management page;
In the system resource management process, the database and the server resource are configured, maintained and managed;
In the system team management process, checking the current team and all sub-teams of the current team, managing team users, editing team information, and modifying team names, superordinate teams and team state information;
in the process of flow management, performing on-line and off-line management of a logic model, a physical model and a program;
In the data opening module, the content for user access verification through the component arrangement comprises whether Token information and AppKey of the user are correct or not and whether the request user is granted permission for accessing the appointed API or not;
In the data opening module, when user access verification passes, the execution of the next flow node is shifted, the user access verification fails, and a message prompt that the Token is incorrect or the AppKey is illegal is returned;
In the data opening module, verifying whether parameters carried in the access request lack parameters necessary for inputting parameter configuration and whether parameter names are consistent with the parameter configuration;
In the data opening module, after the parameter verification is passed, the execution of the next flow node is transferred, the verification fails, and a message prompt of incorrect parameter or unnecessary specified parameter is returned;
In the data opening module, specified parameters of the service request are converted into specified columns through an encryption or decryption algorithm specified in API parameter configuration;
In the data opening module, decoding parameter information received by the API service; carrying out integral encryption transcoding on the data returned by the service request;
The data opening module is also used for carrying out file proxy, hbase inquiry, http proxy, JS script execution, sql inquiry, file uploading and webService proxy through the assembly arrangement;
The system also comprises a standardized management module, a standard management module and a control module, wherein the standardized management module is used for carrying out standardized management, and the standardized management comprises theme configuration, table field naming standard management, table naming standard management, dimension code value mapping, service standard management and meta-model standard management;
The system also comprises a quality management module, a quality control module and a quality control module, wherein the quality management module is used for quality management, and the quality management comprises a quality check report, logic/physical model rule configuration and quality check details; logical/physical model rule configuration includes rule configuration specification, null check, referential integrity check, value field check, script check, specification check, and fluctuation check;
the system also comprises a subscription management module which is used for carrying out subscription management, wherein the subscription management comprises model subscription management, file subscription management and file subscription approval.
CN202410082418.5A 2024-01-19 2024-01-19 Data resource management method and system for business team Pending CN117931438A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202410082418.5A CN117931438A (en) 2024-01-19 2024-01-19 Data resource management method and system for business team

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202410082418.5A CN117931438A (en) 2024-01-19 2024-01-19 Data resource management method and system for business team

Publications (1)

Publication Number Publication Date
CN117931438A true CN117931438A (en) 2024-04-26

Family

ID=90755164

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202410082418.5A Pending CN117931438A (en) 2024-01-19 2024-01-19 Data resource management method and system for business team

Country Status (1)

Country Link
CN (1) CN117931438A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118332531A (en) * 2024-06-13 2024-07-12 金现代信息产业股份有限公司 Intensive application authority definition method and system based on zero code platform

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN118332531A (en) * 2024-06-13 2024-07-12 金现代信息产业股份有限公司 Intensive application authority definition method and system based on zero code platform

Similar Documents

Publication Publication Date Title
US11477238B1 (en) Viewing aggregate policies for authorizing an API
US20200067791A1 (en) Client account versioning metadata manager for cloud computing environments
US10754932B2 (en) Centralized consent management
US9565260B2 (en) Account state simulation service for cloud computing environments
US9210178B1 (en) Mixed-mode authorization metadata manager for cloud computing environments
US8856077B1 (en) Account cloning service for cloud computing environments
US8805971B1 (en) Client-specified schema extensions in cloud computing environments
US8316005B2 (en) Network-accessible database of remote services
US9430449B2 (en) Systems, methods, and media for managing editable previews of webpages
US20240362190A1 (en) Data asset sharing
US9450985B2 (en) Server validation with dynamic assembly of scripts
US11044256B1 (en) Classification management
US20030033255A1 (en) License repository and method
CA2615523A1 (en) Managing network-accessible services
CN117931438A (en) Data resource management method and system for business team
US11321792B2 (en) Enforceable contract generation
EP1354289A2 (en) Distributed management and administration of licensing of multi function offering applications
CN111459907A (en) Method, system and storage medium for configuring master data through model
US8229882B2 (en) System and method for business intelligence metadata exchange
Scaglioso et al. Modern standard-based access control in network services: XACML in action
US20240094993A1 (en) Method and system for dynamic configuration of a policy model as a dynamic authorization implementation
US20250111001A1 (en) Self-diagnosing link stabilizer
Soueidi Microsoft Azure Storage Essentials
Becker Learning Azure DocumentDB
Wehrberger HappyFace Meta-Monitoring for ATLAS in the Worldwide LHC Computing Grid

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination