CN110704455A

CN110704455A - Method, device, terminal and storage medium for generating data asset directory

Info

Publication number: CN110704455A
Application number: CN201910990339.3A
Authority: CN
Inventors: 滕飞; 郑永升; 田清; 刘松茂; 陈立明; 周文博; 吕小敬; 徐祥; 焦峰; 王丽明
Original assignee: CNPC Beijing Richfit Information Technology Co Ltd
Current assignee: China National Petroleum Corp
Priority date: 2019-10-17
Filing date: 2019-10-17
Publication date: 2020-01-17
Anticipated expiration: 2039-10-17
Also published as: CN110704455B

Abstract

The application discloses a method, a device, a terminal and a storage medium for generating a data asset directory, and belongs to the technical field of data management. The method comprises the following steps: creating a business asset parent directory of a target business, adding business subdirectories of all levels in the business asset parent directory, and adding corresponding business contents in each business object subdirectory, wherein each business object subdirectory is the lowest business subdirectory in each business asset directory branch, and associating each business object subdirectory with a corresponding first technical data table to obtain the business asset directory. According to the method and the system, the enterprise can sort and control the data assets based on the business process, business personnel can check related technical data through the business asset directory, and the efficiency of accurately acquiring the required data is improved.

Description

Method, device, terminal and storage medium for generating data asset directory

Technical Field

The present application relates to the field of data management technologies, and in particular, to a method, an apparatus, a terminal, and a storage medium for generating a data asset directory.

Background

The data asset directory comprises a technical asset directory and a business asset directory and is used for displaying aspects of data combing, metadata acquisition, classified directory management, business object description, visual application and the like. The metadata refers to data describing data, such as table information, field information, and the like. Business objects can be extracted from the business domain, such as customers, orders, and goods.

In the related art, for the technical asset directory and the business asset directory of the same business, the technical asset directory only contains technical data, and the business asset directory only contains business data. The technical personnel can obtain the related technical data from the technical asset directory, and the business personnel can obtain the related business data from the business asset directory. When the service personnel has the requirement of acquiring the related technical data, the service personnel can also search the corresponding content from the technical asset directory.

In the course of implementing the present application, the inventors found that the related art has at least the following problems:

when a service person has a need to acquire related technical data, the service person can only search corresponding contents from the technical asset directory, and the service person is unfamiliar with the aspects of the technical asset directory, such as the frame, and the like, so that the efficiency of acquiring the technical data by the service person is low.

Disclosure of Invention

The embodiment of the application provides a method, a device, a terminal and a storage medium for generating a data asset directory, and can solve the problems of error, high communication cost and poor enterprise data asset management effect in communication between two parties. The technical scheme is as follows:

in one aspect, a method of generating a data asset directory is provided, the method comprising:

creating a service asset parent directory of a target service, and adding service subdirectories of all levels in the service asset parent directory;

adding corresponding business contents in each business object subdirectory, wherein the business object subdirectory is the lowest business subdirectory in each business asset directory branch;

and associating each business object subdirectory with the corresponding first technical data table to obtain a business asset directory.

Optionally, the method further includes:

creating a technical asset parent directory of the target service, and adding technical sub-directories at different levels in the technical asset parent directory;

and adding a corresponding second technical data table in each technical object subdirectory to obtain a technical asset directory, wherein the technical object subdirectory is the lowest technical subdirectory in each technical asset directory branch.

Optionally, before adding the corresponding second technical data table in each technical object subdirectory, the method further includes:

importing the original data corresponding to the target service into a mapping relation type database to obtain a technical data summary table;

and determining a second technical data table corresponding to each technical object subdirectory in the technical data summary table.

Optionally, each technical object subdirectory corresponds to a business subdirectory;

before associating each business object subdirectory with the corresponding first technical data table, the method further comprises the following steps:

determining a second technical data table corresponding to the business subdirectory based on a second technical data table corresponding to each technical object subdirectory and the business subdirectory;

and determining a first technical data table corresponding to each service object subdirectory in the service subdirectory in a second technical data table corresponding to each service subdirectory.

Optionally, after the corresponding second technical data table is added in each technical object subdirectory, the method further includes:

generating a data blood relationship map of the technical data in each second technical data table;

and adding a data blood margin map of the technical data in the corresponding second technical data table in each technical object subdirectory.

Optionally, the service content includes a service object name, a service module, a service description, an owner, an administrator, a maintainer and related data assets.

Optionally, the adding corresponding business content in each business object subdirectory includes:

and for each business object subdirectory, adding the name of each metadata in the business object subdirectory, and associating the business object subdirectory with the metadata of the data in the corresponding first technical data table, wherein the metadata is used for describing the data in the first technical data table.

Alternatively to this, the first and second parts may,

the creating of the business asset parent directory of the target business adds business subdirectories of all levels in the business asset parent directory, and comprises the following steps:

creating a service asset parent directory of a purchasing system, and adding a primary purchasing system sub-directory in the service asset parent directory;

adding a plurality of second-level subdirectories in the first-level purchasing system subdirectory, wherein the plurality of second-level subdirectories comprise a commodity subdirectory, a purchasing subdirectory, an order subdirectory and a user subdirectory;

adding a plurality of third-level subdirectories in the commodity subdirectory, wherein the plurality of third-level subdirectories comprise a unit price subdirectory and a sales subdirectory;

adding corresponding business contents in each business object subdirectory comprises the following steps:

respectively adding corresponding business contents in the unit price subdirectory, the sales subdirectory, the purchase subdirectory, the order subdirectory and the user subdirectory;

associating each business object subdirectory with the corresponding first technical data table to obtain a business asset directory, which comprises the following steps:

and associating the unit price subdirectory, the sales subdirectory, the purchase subdirectory, the order subdirectory and the user subdirectory with corresponding first technical data tables to obtain the business asset directory.

In another aspect, an apparatus for generating a data asset directory is provided, the apparatus comprising:

the first creating module is used for creating a service asset father directory of a target service and adding service subdirectories of each level in the service asset father directory;

the adding module is used for adding corresponding business contents in each business object subdirectory, wherein the business object subdirectory is the lowest business subdirectory in each business asset directory branch;

and the association module is used for associating each business object subdirectory with the corresponding first technical data table to obtain a business asset directory.

Optionally, the apparatus further comprises:

the second creating module is used for creating a technical asset parent directory of the target service, and adding technical sub-directories at different levels in the technical asset parent directory;

and the adding module is also used for adding a corresponding second technical data table in each technical object subdirectory to obtain a technical asset directory, wherein the technical object subdirectory is the lowest technical subdirectory in each technical asset directory branch.

Optionally, the apparatus further comprises:

the import module is used for importing the original data corresponding to the target service into a mapping relation type database to obtain a technical data summary table;

and the determining module is used for determining a second technical data table corresponding to each technical object subdirectory in the technical data summary table.

the determining module is further configured to:

Optionally, the apparatus further comprises:

the generating module is used for generating a data blood relationship graph of the technical data in each second technical data table;

the adding module is further used for adding the corresponding data blood edge map of the technical data in the second technical data table in each technical object subdirectory.

Optionally, the apparatus further comprises:

and the supplement module is used for adding the name of each metadata in each business object subdirectory and associating the business object subdirectory with the metadata of the data in the corresponding first technical data table, wherein the metadata is used for describing the data in the first technical data table.

Alternatively to this, the first and second parts may,

the first creating module is further configured to:

the adding module is further configured to:

the association module is further configured to:

In yet another aspect, a terminal is provided, where the terminal includes a processor and a memory, where the memory stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the operations performed by the method for generating a data asset directory.

In yet another aspect, a computer-readable storage medium is provided, wherein at least one instruction is stored in the computer-readable storage medium, and is loaded and executed by a processor to implement the operations performed by the method for generating a data asset directory.

The technical scheme provided by the embodiment of the application has the following beneficial effects:

the method comprises the steps of creating a business asset parent directory of a target business, adding business sub-directories at different levels in the business asset parent directory, adding corresponding business contents in each business object sub-directory, and associating each business object sub-directory with a corresponding first technical data table to obtain a business asset directory. The business personnel can check the related technical data through the business asset directory, and the efficiency of obtaining the technical data by the business personnel is improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a flow chart of a method of generating a directory of data assets provided by an embodiment of the present application;

FIG. 2 is a flow chart of a method of generating a directory of data assets provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of a technical asset directory structure provided by an embodiment of the present application;

FIG. 4 is a flow chart of adding technical data according to an embodiment of the present application;

FIG. 5 is a schematic diagram of an information presentation interface of a technical data sheet according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a data blooding chart according to an embodiment of the present application;

FIG. 7 is a functional architecture diagram of a business asset directory provided by an embodiment of the present application;

FIG. 8 is a flowchart of adding name and interface information of metadata according to an embodiment of the present disclosure;

FIG. 9 is a schematic diagram illustrating a structure of a business asset directory provided by an embodiment of the present application;

FIG. 10 is a block diagram illustrating steps in a method for generating a directory of data assets according to an embodiment of the present application;

FIG. 11 is a flow chart of a query for a data asset directory provided by an embodiment of the present application;

FIG. 12 is a block diagram of an apparatus for generating a data asset directory according to an embodiment of the present disclosure;

fig. 13 is a block diagram of a terminal according to an embodiment of the present disclosure.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

The method for generating the data asset directory provided by the embodiment of the application can be implemented by a computer device, and the computer device can be a server or a terminal. The terminal can be a mobile phone, a tablet computer, a desktop computer, a notebook computer and the like.

The method for generating the data asset directory is mainly applied to the technical field of data management, the data asset directory comprises a technical asset directory and a business asset directory, and each level of technical subdirectories and business subdirectories are respectively added. The technical asset directory mainly displays technical data information through a technical data sheet, the business asset directory can be classified according to the details of each business, and the lowest business subdirectory in each business asset directory branch is associated with the corresponding technical data sheet.

According to the method for generating the data asset directory, association can be performed after data integration and management are performed on technical personnel and business personnel respectively. The original data are imported into a database to obtain a technical data table, a technical asset directory is created, the technical data table is added into the technical asset directory, and the technical data table is displayed in a tree structure. And creating a business asset directory, adding business contents in the business asset directory, and mapping and associating the business contents with the technical data table to obtain the business asset directory, wherein the business asset directory is displayed in the form of a data asset card. In the embodiment of the present application, the procurement system is taken as an example for explanation, and other situations are similar and will not be described again.

Fig. 1 is a flowchart of a method for generating a data asset directory according to an embodiment of the present application, and referring to fig. 1, the embodiment includes:

in step 101, a service asset parent directory of a target service is created, and service sub-directories at different levels are added in the service asset parent directory;

in step 102, adding corresponding business contents in each business object subdirectory, wherein the business object subdirectory is the lowest business subdirectory in each business asset directory branch;

in step 103, each business object subdirectory is associated with a corresponding first technical data table to obtain a business asset directory.

Fig. 2 is a flowchart of a method for generating a data asset directory according to an embodiment of the present application. Referring to fig. 2, the embodiment includes:

in step 201, a technical asset parent directory of the target service is created, and technical sub-directories at different levels are added in the technical asset parent directory.

The technical asset parent directory is the top directory of the technical asset directory, and the technical asset parent directory can also be a technical asset parent directory.

In implementation, a technical asset parent directory of a target service is created under a directory creation module, and various levels of technical subdirectories are added in the technical asset directory. For example, a plurality of first-level technology sub-directories are added in a technology asset parent directory, and a plurality of second-level technology sub-directories are respectively added in the plurality of first-level technology sub-directories.

For example, when the target service is a purchasing system, a plurality of second-level subdirectories may be added in the first-level subdirectory purchasing system, and the second-level subdirectories may be a goods subdirectory, a purchasing subdirectory, an order subdirectory, a user subdirectory, and the like.

In step 202, a corresponding second technical data table is added to each technical object subdirectory to obtain a technical asset directory.

The technical object subdirectory is the lowest technical subdirectory in each technical asset directory branch, and the technical object subdirectory does not have a lower technical subdirectory. The technical asset directory mainly displays technical data information of a target service, wherein the technical data information can be metadata information, and comprises table field information, data overview in a table, table statistical information, table building sentences of the table and the like. Metadata refers to data describing data, table field information refers to information contained in a column in a table, data overview in the table refers to preview data information, table statistical information refers to information such as the number of statistical fields, the size of data volume, historical information and changes of the data table, and table building statements refer to statements used for building the tables in a database.

In implementation, firstly, a technician may import the raw data corresponding to the target service into a mapping relation type database by filling information such as detailed connection of the raw data corresponding to the target service, so as to obtain a technical data summary table, where the mapping relation type database has functions of storing, querying and analyzing large-scale data, and is capable of mapping the raw data into the technical data summary table. Then, the metadata management module can automatically acquire detailed technical data information in the mapping relation type database. And finally, determining a second technical data table corresponding to each technical object subdirectory in the technical data summary table, wherein the second technical data table comprises technical data information such as table field information, data overview in the table, table statistical information, table building statements and the like. And adding a corresponding second technical data table in each technical object subdirectory, and directly displaying the technical data tables in an information display interface of the technical data tables to obtain the technical asset directory. The original data refers to technical data in a source database, includes a large amount of technical data information, and may be in the form of a data file.

For example, fig. 3 is a schematic structural diagram of a technical asset directory provided in an embodiment of the present application, where when a target service is a purchasing system, as shown in fig. 3, when a commodity subdirectory, a purchasing subdirectory, an order subdirectory, and a user subdirectory are added in a first-level purchasing system subdirectory, a corresponding second technical data table, that is, a commodity technical data table, is added in the commodity subdirectory, a corresponding second technical data table, that is, a purchasing technical data table, is added in the purchasing subdirectory, a corresponding second technical data table, that is, an order technical data table, is added in the order subdirectory, and a corresponding second technical data table, that is, a user technical data table, is added in the user subdirectory, so as to obtain the technical asset directory.

Optionally, in the technical asset directory, a plurality of directory hierarchies, such as a base layer, a process layer, a specification layer, and a specification layer, may be created, and the corresponding technical data may be added in the plurality of directory hierarchies.

For example, fig. 4 is a flowchart of adding technical data according to an embodiment of the present application, and as shown in fig. 4, a technician may select a manner of adding a connection database, fill in data source information, create a plurality of directory hierarchies, and add corresponding technical data in each directory hierarchy.

Fig. 5 is a schematic diagram of an information presentation interface of a technical data table provided in an embodiment of the present application, and as shown in fig. 5, fig. 5 includes a table name and technical data information, i.e., metadata information, of the table, where the table name is erp. When the user clicks the table information, the information display interface of the table information includes basic information and permission information as shown in fig. 5, and the basic information includes information such as a table name, a tag of the table name, a creator, creation time, a database to which the table name belongs, a type, a format, and a location. When the user is an authorized user, the authority information is displayed in the interface.

Optionally, a data blood-level graph of the technical data in each second technical data table is generated, and the corresponding data blood-level graph of the technical data in the second technical data table is added to each technical subject subdirectory.

The data blood relationship graph is one kind of metadata information, and refers to a relationship from generation, processing fusion and circulation to final. Fig. 6 is a schematic diagram of a data consanguinity graph provided in an embodiment of the present application, where the data consanguinity graph includes an exterior consanguinity and a field consanguinity, and when a user clicks the exterior consanguinity, an information display interface of the exterior consanguinity is as shown in fig. 6, and a data relationship is displayed in a graph form, which reflects a relationship flow direction between data tables.

In step 203, a service asset parent directory of the target service is created, and service sub-directories at different levels are added in the service asset parent directory.

The service asset parent directory refers to the uppermost directory of the service asset directories.

In implementation, a service asset parent directory of a target service is created under a directory creation module, and service subdirectories at different levels are added in the service asset directory. For example, a plurality of first-level business subdirectories are added in a business asset parent directory, a plurality of second-level business subdirectories are respectively added in the plurality of first-level business subdirectories, and the grading is continued downwards according to the target business.

For example, when the target business is a purchasing system, a plurality of second-level subdirectories are added in the first-level subdirectory purchasing system, and the second-level subdirectories comprise a commodity subdirectory, a purchasing subdirectory, an order subdirectory and a user subdirectory. And a third-level subdirectory can be added in the second-level subdirectory, and a third-level subdirectory related to the second-level subdirectory can be respectively added in the commodity subdirectory, the purchasing subdirectory, the order subdirectory and the user subdirectory, and is the lowest-level subdirectory if no third-level subdirectory related to the third-level subdirectory exists. For example, when the second-level subdirectory is a commodity subdirectory, a unit price subdirectory and a sales volume subdirectory are added into the commodity subdirectory.

In step 204, corresponding business contents are added to each business object subdirectory.

The business object subdirectory is the lowest level business subdirectory in each business asset directory branch, and the business object subdirectory does not have a lower level business subdirectory. The business content includes business object name, business module, business description, owner, manager, maintainer and related data assets, etc. The owner refers to the leader in the system corresponding to each target service. The administrator can centrally manage the user authorization and the role distribution, and reduce the related problems of data security caused by unauthorized users. The maintainer refers to a worker in the system corresponding to each target service. Related data assets refer to business relationships between a target data table and other data tables.

In implementation, in each business object subdirectory, business contents such as a business object name, a business module, a business description, an owner, a manager, a maintainer, related data assets and the like are added, fig. 7 is a functional architecture diagram of a business asset directory provided in the embodiment of the present application, as shown in fig. 7, a multi-level subdirectory can be added to the business asset directory, a business object 1, a business object 2 and the like can be included in the business object subdirectory, that is, the lowest level subdirectory of the business asset directory, and business contents can be added to each business object.

For example, when the secondary subdirectory is a commodity subdirectory, the commodity subdirectory includes a unit price subdirectory and a sales volume subdirectory, and business contents such as business object names, business modules, business descriptions, owners, managers, maintainers and related data assets are respectively added in the unit price subdirectory and the sales volume subdirectory.

Optionally, for each business object subdirectory, the name of each metadata is added in the business object subdirectory, and the business object subdirectory is associated with the metadata of the data in the corresponding first technical data table.

The metadata is used for describing data in the first technical data table, namely names such as table field information, data overview in the table, table statistical information and table building sentences of the table.

Specifically, for each business object subdirectory, names of metadata such as table field information, data overview in the table, table statistical information, and table building statements of the table may be added to the business object subdirectory for a user to view the metadata in the technical data table. For the name of each metadata in the business object subdirectory, the name of the metadata can be associated with the metadata of the data in the corresponding first technical data table by adding the corresponding interface information. When a user wants to view the metadata corresponding to the metadata name, the user can click the metadata name, call the metadata corresponding to the metadata name in the first technical data table through the interface information corresponding to the metadata name, and display the metadata on the information display interface. And when the name of the metadata does not have corresponding metadata, displaying nothing or blank on an information display interface of the name of the metadata.

The data asset directory provided by the embodiment of the application can be operated through a data asset directory management platform, and the data asset directory management platform comprises a plurality of modules, such as a content supplement module, a content approval module, a content release module and the like. Each module is divided into a front-end service and a back-end service, the front-end service is developed and realized by a certain front-end based on a running environment of a browser and the like, and the back-end service can be realized by programming software. The front end calls the back-end service to provide an interface, and the back-end services are mutually called through the interface. Fig. 8 is a flowchart of adding names and interface information of metadata according to an embodiment of the present application, and as shown in fig. 8, a service person may select a batch adding manner or a single adding manner. When the batch adding mode is selected, the template is downloaded and filled in, and then the template is uploaded and sent to the content supplement module to be fed back to the user. When the mode of adding the single strip is selected, the single strip information is filled in and submitted to the content supplement module to be fed back to the user. The name and interface information of the metadata of the added business object subdirectory can be supplemented in the content supplement module, and the name and interface information are submitted and sent to the content approval module. And checking details in the content approval module, performing approval by an administrator, selecting approval or refusal, and if the approval is performed, sending the technical information and the interface information to the content publishing module and feeding back to the user. If yes, adding the reason of rejection and feeding back to the user. And checking details in the content publishing module, examining and approving by an administrator, selecting to publish or not publish temporarily, and if the details are published, publishing the technical information and the interface information in a business asset directory, so that a user can inquire the information in the business asset directory. And if the publication is not published for the moment, adding the reason of not publishing for the moment and feeding back the reason to the user.

In step 205, each business object sub-directory is associated with a corresponding first technical data table to obtain a business asset directory.

Each technical object subdirectory corresponds to a business subdirectory, such as the commodity subdirectory in the technical asset directory of fig. 3 and the commodity subdirectory in the business asset directory of fig. 9.

In implementation, each technical object subdirectory corresponds to one business subdirectory, and a second data table corresponding to the business subdirectory is determined based on the second technical data table and the business subdirectory corresponding to each technical object subdirectory. And determining a first technical data table corresponding to each service object subdirectory in the service subdirectory in a second technical data table corresponding to each service subdirectory. For each business object subdirectory, the business object subdirectory can be associated with the corresponding first technical data table by adding the corresponding interface information. When a user wants to view the first technical data table corresponding to the business object subdirectory, the corresponding first technical data table can be called through the interface information corresponding to the business object subdirectory, and the first technical data table is displayed on the information display interface, so that the business asset directory is obtained.

For example, fig. 9 is a schematic structural diagram of a business asset directory provided in an embodiment of the present application, and when a target business is a purchasing system, as shown in fig. 9, a plurality of secondary subdirectories, such as a goods subdirectory, a purchasing subdirectory, an order subdirectory, and a user subdirectory, are added in a primary subdirectory purchasing system. And when the second-level subdirectory is a commodity subdirectory, a unit price subdirectory and a sales volume subdirectory can be added, and when the unit price subdirectory and the sales volume subdirectory are not reclassified, namely the lowest-level subdirectory, the unit price subdirectory is associated with the corresponding unit price technical data table, and the sales volume subdirectory is associated with the corresponding sales volume technical data table to obtain the business asset directory. Similarly, in fig. 3, the second-level subdirectories such as the purchasing subdirectory, the order subdirectory, and the user subdirectory can also be added in a hierarchical manner, which is not described herein again.

Optionally, after each business object subdirectory is associated with the corresponding first technical data table, operations such as label remark and the like can be performed in the associated business object subdirectory, so that a user can understand technical data more clearly.

Fig. 10 is a block diagram of steps of a method for generating a data asset directory according to an embodiment of the present application, where a technical data table is obtained by importing raw data into a database, a technical asset directory is created, and a technical data table is added to the technical asset directory. And creating a business asset directory, adding business contents in the business asset directory, and mapping and associating the business contents with the technical data table to obtain the business asset directory, thereby obtaining the data asset directory. After generating the data asset directory according to the above steps 201 to 205, the user may query the technical data information or the business information in the technical asset directory query or the business asset directory. Fig. 11 is a flowchart of querying a data asset directory according to an embodiment of the present application, and as shown in fig. 11, a user may expand the data asset directory by clicking a tree graph directory and then click a node directory for detailed viewing. The user can also find the corresponding directory by searching the directory name, and then click the node directory to check the details. The user can also click the search result to check the details through the name of the search table, the name of the business object and the like.

the method comprises the steps of creating a business asset parent directory of a target business, adding business sub-directories at different levels in the business asset parent directory, adding corresponding business contents in each business object sub-directory, and associating each business object sub-directory with a corresponding first technical data table to obtain a business asset directory. According to the method and the system, the business asset directory and the technical asset directory are combined to obtain the data asset directory, so that the data assets are sorted and controlled by an enterprise based on a business process, users such as business personnel and technical personnel can check related data through the data asset directory, and the data acquisition efficiency is improved.

All the above optional technical solutions may be combined arbitrarily to form the optional embodiments of the present disclosure, and are not described herein again.

An apparatus for generating a data asset directory is provided in an embodiment of the present application, where the apparatus may be a terminal or a server in the foregoing embodiments, as shown in fig. 12, fig. 12 is a schematic structural diagram of an apparatus for generating a data asset directory provided in an embodiment of the present application, and the apparatus includes:

a first creating module 1201, configured to create a service asset parent directory of a target service, and add service subdirectories of each level in the service asset parent directory;

an adding module 1202, configured to add corresponding business content in each business object subdirectory, where the business object subdirectory is a lowest-level business subdirectory in each business asset directory branch;

an associating module 1203, configured to associate each business object sub-directory with the corresponding first technical data table, so as to obtain a business asset directory.

Optionally, the apparatus further comprises:

the second creating module is used for creating a technical asset parent directory of the target service and adding technical subdirectories of each level in the technical asset parent directory;

the adding module 1202 is further configured to add a corresponding second technical data table in each technical object subdirectory to obtain a technical asset directory, where the technical object subdirectory is a lowest technical subdirectory in each technical asset directory branch.

Optionally, the apparatus further comprises:

the import module is used for importing the original data corresponding to the target service into the mapping relation type database to obtain a technical data summary table;

a determination module further configured to:

determining a second technical data table corresponding to the business subdirectory based on a second technical data table and a business subdirectory corresponding to each technical object subdirectory;

and for the second technical data table corresponding to each service subdirectory, determining the first technical data table corresponding to each service object subdirectory in the service subdirectory in the second technical data table.

Optionally, the apparatus further comprises:

the adding module 1202 is further configured to add a data edge map of the technical data in the corresponding second technical data table in each technical object subdirectory.

Optionally, the apparatus further comprises:

Alternatively to this, the first and second parts may,

a first creating module 1201, further configured to:

creating a service asset father directory of a purchasing system, and adding a first-level purchasing system sub-directory in the service asset father directory;

an adding module 1202, further configured to:

respectively adding corresponding business contents in a unit price subdirectory, a sales subdirectory, a purchasing subdirectory, an order subdirectory and a user subdirectory;

an association module 1203, further configured to:

and associating the unit price subdirectory, the sales volume subdirectory, the purchase subdirectory, the order subdirectory and the user subdirectory with the corresponding first technical data table to obtain the business asset directory.

It should be noted that: in the apparatus for generating a data asset directory according to the foregoing embodiment, when generating the data asset directory, only the division of the functional modules is illustrated, and in practical applications, the function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the apparatus for generating a data asset directory and the method for generating a data asset directory provided in the foregoing embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments and are not described herein again.

Fig. 13 shows a block diagram of a terminal 1300 according to an exemplary embodiment of the present application. The terminal 1300 may be: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio layer iii, motion video Experts compression standard Audio layer 3), an MP4 player (Moving Picture Experts Group Audio layer IV, motion video Experts compression standard Audio layer 4), a notebook computer, or a desktop computer. Terminal 1300 may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, etc.

In general, terminal 1300 includes: a processor 1301 and a memory 1302.

Processor 1301 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The processor 1301 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 1301 may also include a main processor and a coprocessor, where the main processor is a processor for processing data in an awake state, and is also referred to as a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 1301 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing content that the display screen needs to display. In some embodiments, processor 1301 may further include an AI (Artificial Intelligence) processor for processing computational operations related to machine learning.

Memory 1302 may include one or more computer-readable storage media, which may be non-transitory. The memory 1302 may also include high speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 1302 is used to store at least one instruction for execution by processor 1301 to implement the method of generating a data asset directory provided by method embodiments herein.

In some embodiments, terminal 1300 may further optionally include: a peripheral interface 1303 and at least one peripheral. Processor 1301, memory 1302, and peripheral interface 1303 may be connected by a bus or signal line. Each peripheral device may be connected to the peripheral device interface 1303 via a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of radio frequency circuitry 1304, touch display 1305, camera 1306, audio circuitry 1307, positioning component 1308, and power supply 1309.

Peripheral interface 1303 may be used to connect at least one peripheral associated with I/O (Input/Output) to processor 1301 and memory 1302. In some embodiments, processor 1301, memory 1302, and peripheral interface 1303 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 1301, the memory 1302, and the peripheral device interface 1303 may be implemented on a separate chip or circuit board, which is not limited in this embodiment.

The Radio Frequency circuit 1304 is used to receive and transmit RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuitry 1304 communicates with communication networks and other communication devices via electromagnetic signals. The radio frequency circuit 1304 converts an electrical signal into an electromagnetic signal to transmit, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 1304 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuitry 1304 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: metropolitan area networks, various generation mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the radio frequency circuit 1304 may also include NFC (Near Field Communication) related circuits, which are not limited in this application.

The display screen 1305 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display screen 1305 is a touch display screen, the display screen 1305 also has the ability to capture touch signals on or over the surface of the display screen 1305. The touch signal may be input to the processor 1301 as a control signal for processing. At this point, the display 1305 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, display 1305 may be one, providing the front panel of terminal 1300; in other embodiments, display 1305 may be at least two, either on different surfaces of terminal 1300 or in a folded design; in still other embodiments, display 1305 may be a flexible display disposed on a curved surface or on a folded surface of terminal 1300. Even further, the display 1305 may be arranged in a non-rectangular irregular figure, i.e., a shaped screen. The Display 1305 may be made of LCD (Liquid Crystal Display), OLED (Organic Light-Emitting Diode), or the like.

The camera assembly 1306 is used to capture images or video. Optionally, camera assembly 1306 includes a front camera and a rear camera. Generally, a front camera is disposed at a front panel of the terminal, and a rear camera is disposed at a rear surface of the terminal. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and VR (Virtual Reality) shooting functions or other fusion shooting functions. In some embodiments, camera assembly 1306 may also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.

The audio circuit 1307 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 1301 for processing, or inputting the electric signals to the radio frequency circuit 1304 for realizing voice communication. For stereo capture or noise reduction purposes, multiple microphones may be provided, each at a different location of terminal 1300. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 1301 or the radio frequency circuitry 1304 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, audio circuitry 1307 may also include a headphone jack.

The positioning component 1308 is used for positioning the current geographic position of the terminal 1300 to implement navigation or LBS (location based Service). The positioning component 1308 may be a positioning component based on a GPS (global positioning System) of the united states, a beidou System of china, a graves System of russia, or a galileo System of the european union.

Power supply 1309 is used to provide power to various components in terminal 1300. The power source 1309 may be alternating current, direct current, disposable or rechargeable. When the power source 1309 comprises a rechargeable battery, the rechargeable battery may support wired or wireless charging. The rechargeable battery may also be used to support fast charge technology.

In some embodiments, terminal 1300 also includes one or more sensors 1310. The one or more sensors 1310 include, but are not limited to: acceleration sensor 1311, gyro sensor 1312, pressure sensor 1313, fingerprint sensor 1314, optical sensor 1315, and proximity sensor 1316.

The acceleration sensor 1311 can detect the magnitude of acceleration on three coordinate axes of the coordinate system established with the terminal 1300. For example, the acceleration sensor 1311 may be used to detect components of gravitational acceleration in three coordinate axes. The processor 1301 may control the touch display screen 1305 to display the user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 1311. The acceleration sensor 1311 may also be used for acquisition of motion data of a game or a user.

The gyro sensor 1312 may detect the body direction and the rotation angle of the terminal 1300, and the gyro sensor 1312 may cooperate with the acceleration sensor 1311 to acquire a 3D motion of the user with respect to the terminal 1300. Processor 1301, based on the data collected by gyroscope sensor 1312, may perform the following functions: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization at the time of photographing, game control, and inertial navigation.

Pressure sensor 1313 may be disposed on a side bezel of terminal 1300 and/or underlying touch display 1305. When the pressure sensor 1313 is disposed on the side frame of the terminal 1300, a user's holding signal to the terminal 1300 may be detected, and the processor 1301 performs left-right hand recognition or shortcut operation according to the holding signal acquired by the pressure sensor 1313. When the pressure sensor 1313 is disposed at a lower layer of the touch display screen 1305, the processor 1301 controls an operability control on the UI interface according to a pressure operation of the user on the touch display screen 1305. The operability control comprises at least one of a button control, a scroll bar control, an icon control and a menu control.

The fingerprint sensor 1314 is used for collecting the fingerprint of the user, and the processor 1301 identifies the identity of the user according to the fingerprint collected by the fingerprint sensor 1314, or the fingerprint sensor 1314 identifies the identity of the user according to the collected fingerprint. When the identity of the user is identified as a trusted identity, the processor 1301 authorizes the user to perform relevant sensitive operations, including unlocking a screen, viewing encrypted information, downloading software, paying, changing settings, and the like. The fingerprint sensor 1314 may be disposed on the front, back, or side of the terminal 1300. When a physical button or vendor Logo is provided on the terminal 1300, the fingerprint sensor 1314 may be integrated with the physical button or vendor Logo.

The optical sensor 1315 is used to collect the ambient light intensity. In one embodiment, the processor 1301 can control the display brightness of the touch display screen 1305 according to the intensity of the ambient light collected by the optical sensor 1315. Specifically, when the ambient light intensity is high, the display brightness of the touch display screen 1305 is increased; when the ambient light intensity is low, the display brightness of the touch display 1305 is turned down. In another embodiment, the processor 1301 can also dynamically adjust the shooting parameters of the camera assembly 1306 according to the ambient light intensity collected by the optical sensor 1315.

Proximity sensor 1316, also known as a distance sensor, is typically disposed on a front panel of terminal 1300. Proximity sensor 1316 is used to gather the distance between the user and the front face of terminal 1300. In one embodiment, the processor 1301 controls the touch display 1305 to switch from the bright screen state to the dark screen state when the proximity sensor 1316 detects that the distance between the user and the front face of the terminal 1300 gradually decreases; the touch display 1305 is controlled by the processor 1301 to switch from the rest state to the bright state when the proximity sensor 1316 detects that the distance between the user and the front face of the terminal 1300 gradually becomes larger.

Those skilled in the art will appreciate that the configuration shown in fig. 13 is not intended to be limiting with respect to terminal 1300 and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components may be employed.

In an exemplary embodiment, a computer-readable storage medium, such as a memory, including instructions executable by a processor in a terminal to perform the method of generating a data asset directory in the above embodiments is also provided. For example, the computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

It will be understood by those skilled in the art that all or part of the steps of implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The present invention is not intended to be limited to the particular embodiments shown and described, but is to be accorded the widest scope consistent with the principles and novel features herein disclosed.

Claims

1. A method of generating a data asset directory, the method comprising:

2. The method of claim 1, further comprising:

3. The method of claim 2, wherein before adding the corresponding second technical data table in each technical object subdirectory, further comprising:

4. A method according to claim 3, wherein each technical object subdirectory corresponds to a business subdirectory;

5. The method of claim 2, wherein after adding the corresponding second technical data table in each technical object subdirectory, further comprising:

6. The method of claim 1, wherein the business content comprises business object names, business modules, business descriptions, owners, managers, maintainers, and related data assets.

7. The method according to claim 1, wherein the adding corresponding business content in each business object subdirectory comprises:

8. The method of claim 1, wherein the creating a business asset parent directory of the target business, adding business subdirectories at different levels in the business asset parent directory, comprises:

9. An apparatus for generating a directory of data assets, the apparatus comprising:

10. A terminal, comprising a processor and a memory, wherein the memory has stored therein at least one instruction that is loaded and executed by the processor to perform operations performed by the method of generating a data asset directory as claimed in any one of claims 1 to 8.