CN115658821B

CN115658821B - Method and device for managing digital entity and storage medium

Info

Publication number: CN115658821B
Application number: CN202211592370.XA
Authority: CN
Inventors: 陈洁; 张坚欣; 邹方勇
Original assignee: Jiajia Technology Co ltd
Current assignee: Jiajia Technology Co ltd
Priority date: 2022-12-13
Filing date: 2022-12-13
Publication date: 2023-04-07
Anticipated expiration: 2042-12-13
Also published as: CN115658821A

Abstract

The invention discloses a management method, a device and a storage medium of a digital entity, which can realize the unified management, historical change tracing and unified access way of different heterogeneous service data in different information systems, and the method comprises the following steps: constructing an entity relationship model comprising the incidence relationship among all digital entities; constructing a version management model for abstracting the change of the digital entity into a digital asset library after the digital entity is put into the digital asset library to manage the version update of the digital entity; providing a unified digital entity access interface for a digital asset library; after detecting that the first digital entity is put into a digital asset library through the unified digital entity access interface, abstracting the change of the first digital entity into the version update of the first digital entity through a version management model, and obtaining the version information corresponding to the first digital entity; the first digital entity is stored in the digital asset repository according to the entity relationship model and the version information.

Description

Management method, device and storage medium of digital entity

Technical Field

The present invention relates to the field of data storage technologies, and in particular, to a method and an apparatus for managing a digital entity, and a storage medium.

Background

With the development of the informatization technology, more and more enterprises digitalize and informationize the business management of the enterprises, which provides help for the enterprises to realize digital transformation and improve the operation efficiency. However, with the continuous evolution of the business management concept, more and more enterprises recognize that the business data stored in the information system is also an important asset of the enterprise, and the requirements for managing and controlling the business data are increased, and the appeal for changing and tracing the core business data is also stronger and stronger.

However, due to the time of information system construction and the limitations of the prior art, some old information systems do not consider the historical change tracing scenario of the service data at the beginning of construction, and currently, system modification is performed to meet the requirement of historical change tracing, which is very high in cost from the technical point of view. In addition, as enterprise management concepts become more advanced, big data analytics, business Intelligence (BI) tools, have begun to fall on the floor of enterprises, and although these advanced tools and techniques assist enterprise management and decision-making with visualization effects, business data and historical retrospection thereof are not left behind. And the historical change tracing of the business data relates to the most central management of various heterogeneous digital entities existing in different information systems.

In summary, it is necessary to design a scheme that can perform unified management, historical change tracing, and unified access to different heterogeneous service data in different information systems.

Disclosure of Invention

Based on this, the present invention provides a method, an apparatus, and a storage medium for managing a digital entity, which are used to perform unified management, history change tracing, and unified access to different heterogeneous service data in different information systems.

In a first aspect, the present invention provides a method for managing a digital entity, including:

constructing an entity relationship model, wherein the entity relationship model comprises an incidence relationship among digital entities, and the digital entities are service data objects in different information systems;

constructing a version management model, wherein the version management model is used for abstracting the change of the digital entity into the version update of the digital entity for management after the digital entity is put into a digital asset library;

providing a unified digital entity access interface of a digital asset library, wherein the unified digital entity access interface is used for supporting various operations of a digital entity on the digital asset library;

after a first digital entity is detected to be put into the digital asset library through the unified digital entity access interface, the change of the first digital entity is abstracted into the version update of the first digital entity through the version management model, and the version information corresponding to the first digital entity is obtained; the first digital entity is one of the digital entities;

storing the first digital entity in the digital asset library according to the entity relationship model and the version information.

In one possible design, an entity-relationship model is constructed, comprising:

according to business requirements, conducting investigation on each digital entity needing to be stored, determining investigation data corresponding to any one of the digital entities, and determining an incidence relation between the digital entities; the research data comprises an information system to which any digital entity belongs, each field contained by any digital entity, the data type of any field in each field and a primary key field in each field;

saving the research data and initializing any digital entity based on the research data;

and constructing the entity relationship model according to any initialized digital entity and the incidence relationship.

In one possible design, the version management model includes: a system table, an entity field table, a warehousing number and entity association relation table and an entity warehousing record table; the system table is used for managing and recording according to the attribution of the information system; the entity table is used for describing digital entities; the entity field table is used for describing field information in the middle of the digital entity; the warehousing number table is used for recording warehousing numbers generated by the digital entities in warehousing each time; the warehousing number and entity association relation table is used for information of the digital entity in warehousing every time; and the entity entry table is used for recording the information instantiated according to the entity field after the digital entity is entered into the digital asset library.

In one possible design, abstracting, by the version management model, a change to the first digital entity to a version update of the first digital entity to obtain version information corresponding to the first digital entity includes:

if the first digital entity is changed into a newly-added first digital entity, generating a warehousing number corresponding to the current warehousing operation of the first digital entity through the version management model, writing the warehousing number as a HEAD pointer to the first digital entity to obtain version information of the first digital entity, wherein the version information comprises the warehousing number which is used for pointing to a record of the current warehousing of the first digital entity; alternatively, the first and second electrodes may be,

if the first digital entity is changed into an updated first digital entity, when the first digital entity is changed after being updated, generating a warehousing number corresponding to the current warehousing operation of the first digital entity through the version management model, and writing the warehousing number as a HEAD pointer on the first digital entity to obtain version information of the first digital entity, wherein the version information comprises the warehousing number which is used for pointing to the latest record of the current warehousing of the first digital entity; alternatively, the first and second liquid crystal display panels may be,

and if the first digital entity is changed into the deletion of the first digital entity, generating a warehousing number corresponding to the current deletion operation of the first digital entity through the version management model, and interrupting the relationship between the first digital entity and the digital asset library through the warehousing number.

In one possible design, the version management model further includes a tag table, where the tag table is used to record tags added by user digital entities, and the tags are in one-to-one correspondence with the warehousing numbers in the warehousing number table; the method further comprises the following steps:

receiving a first label added by a user for the first digital entity at a first time point;

and pointing the first label to the nearest warehousing number of the first digital entity before the first time point.

In one possible design, after storing the first digital entity in the digital asset library according to the entity relationship model and the version information, the method further comprises:

when detecting that a user accesses a second digital entity by adopting a first warehousing number through the unified digital entity access interface, returning the record of the second digital entity corresponding to the first warehousing number to the user; the second digital entity is one of the digital entities stored in the digital asset library; alternatively, the first and second electrodes may be,

when detecting that a user accesses the second digital entity by adopting a second label through the unified digital entity access interface, returning the record of the second digital entity corresponding to the warehousing number pointed by the second label to the user; alternatively, the first and second electrodes may be,

and when detecting that the user accesses the second digital entity by adopting the first HEAD pointer through the unified digital entity access interface, returning the latest data of the second digital entity to the user.

In one possible design, the method further includes:

when detecting that a same third digital entity is referred by a plurality of external systems and conflicts are generated in the digital asset library in a warehousing mode, refining the conflicts to fields contained in the third digital entity to obtain conflict fields corresponding to the third digital entity; the third digital entity is one of the digital entities;

and outputting the conflict field to prompt the user to process.

In one possible design, the unified digital entity access interface includes: the method comprises the steps of inputting a digital entity into a warehouse, outputting the digital entity from the warehouse, resetting a HEAD interface, setting a label interface, deleting the label interface and modifying the label interface; the digital entity warehousing interface is used for supporting digital entity warehousing operation on the digital asset library, wherein the warehousing operation comprises a new adding operation, a repeated warehousing operation and a deleting operation; the digital entity ex-warehouse operation interface is used for supporting the ex-warehouse operation and the access operation of the digital entity on the digital entity stored in the digital asset library; the HEAD resetting interface is used for supporting the HEAD pointer in a specified information system stored in the digital asset library to be reset to a specified warehousing number; the setting label interface is used for supporting the setting label of the warehousing serial number of the specified digital entity stored in the digital asset library; the label deleting interface is used for supporting the deletion of a label set by the warehousing number of the specified digital entity stored in the digital asset library; and the modified tag interface is used for supporting modification of tags of the warehousing number setting of the specified digital entities stored in the digital asset library.

In a second aspect, the present invention provides a management device, comprising:

the system comprises a construction unit, a data processing unit and a data processing unit, wherein the construction unit is used for constructing an entity relationship model, the entity relationship model comprises incidence relations among digital entities, and the digital entities are service data objects in different information systems; constructing a version management model, wherein the version management model is used for abstracting the change of the digital entity into the version update of the digital entity for management after the digital entity is put into a digital asset library;

the system comprises a processing unit, a digital asset library management unit and a digital asset management unit, wherein the processing unit is used for providing a unified digital entity access interface of the digital asset library, and the unified digital entity access interface is used for supporting various operations of a digital entity on the digital asset library; after a first digital entity is detected to be put into the digital asset library through the unified digital entity access interface, the change of the first digital entity is abstracted into the version update of the first digital entity through the version management model, and the version information corresponding to the first digital entity is obtained; the first digital entity is one of the digital entities; storing the first digital entity in the digital asset library according to the entity relationship model and the version information.

In one possible design, the building unit is specifically configured to:

according to business requirements, investigating each digital entity to be stored, determining investigation data corresponding to any one of the digital entities, and determining an incidence relation between the digital entities; the research data comprises an information system to which the any digital entity belongs, each field contained by the any digital entity, the data type of any field in each field and a primary key field in each field;

storing the research data and initializing any digital entity based on the research data;

In one possible design, the version management model includes: a system table, an entity field table, a warehousing number and entity association relation table and an entity warehousing record table; the system table is used for managing and recording according to the attribution of the information system; the entity table is used for describing digital entities; the entity field table is used for describing field information in the middle of the digital entity; the warehousing serial number table is used for recording warehousing serial numbers generated by the digital entities in each warehousing; the warehousing number and entity association relation table is used for information of the digital entity in warehousing every time; and the entity entry table is used for recording the information instantiated according to the entity field after the digital entity is entered into the digital asset library.

In one possible design, the processing unit is specifically configured to:

if the first digital entity is changed into a newly-added first digital entity, generating a warehousing number corresponding to the current warehousing operation of the first digital entity through the version management model, and writing the warehousing number as a HEAD pointer to the first digital entity to obtain version information of the first digital entity, wherein the version information comprises the warehousing number which is used for pointing to a record of the current warehousing of the first digital entity; alternatively, the first and second liquid crystal display panels may be,

if the first digital entity is changed into an updated first digital entity, when the first digital entity is changed after being updated, generating a warehousing number corresponding to the current warehousing operation of the first digital entity through the version management model, and writing the warehousing number as a HEAD pointer on the first digital entity to obtain version information of the first digital entity, wherein the version information comprises the warehousing number which is used for pointing to the latest record of the current warehousing of the first digital entity; alternatively, the first and second electrodes may be,

In one possible design, the version management model further includes a tag table, where the tag table is used to record tags added by user digital entities, and the tags are in one-to-one correspondence with the warehousing numbers in the warehousing number table; the processing unit is further to:

In one possible design, the processing unit is further to:

when detecting that a user accesses the second digital entity by adopting a second label through the unified digital entity access interface, returning the record of the second digital entity corresponding to the warehousing number pointed by the second label to the user; alternatively, the first and second liquid crystal display panels may be,

In one possible design, the processing unit is further to:

and outputting the conflict field to prompt a user to process.

In a third aspect, the present invention further provides a management apparatus, including: at least one memory and at least one processor;

the at least one memory is for storing one or more programs;

the one or more programs, when executed by the at least one processor, implement the method as recited in any one of the possible designs of the first aspect above.

In a fourth aspect, the present invention also provides a computer-readable storage medium storing at least one program; the at least one program, when executed by a processor, performs the method of any one of the possible designs of the first aspect.

The invention has the following beneficial effects:

compared with the prior art, the method has the advantages that the entity relationship model is built, the entity relationship model comprises the incidence relation among all digital entities, and the digital entities are business data objects in different information systems; constructing a version management model, wherein the version management model is used for abstracting the change of the digital entity into the version update of the digital entity after the digital entity is put into a digital asset library and managing the version update of the digital entity; providing a uniform digital entity access interface of the digital asset library, wherein the uniform digital entity access interface is used for supporting various operations of a digital entity on the digital asset library; after detecting that the first digital entity is put into a digital asset library through the unified digital entity access interface, abstracting the change of the first digital entity into the version update of the first digital entity through a version management model, and obtaining the version information corresponding to the first digital entity; the first digital entity is one of the digital entities; the first digital entity is stored in the digital asset library according to the entity relationship model and the version information. By the method, the concept of the relational database table and the version control concept of the software source code management tool can be borrowed skillfully, the digital entity is managed by the version management model, and the unified management, historical change tracing and unified access to different heterogeneous service data in different information systems can be realized.

For a better understanding and practice, the invention is described in detail below with reference to the accompanying drawings.

Drawings

Fig. 1 is a schematic flow chart of a method for managing a digital entity according to the present invention;

FIG. 2 is a schematic diagram illustrating a storage of research data of customer information according to the present invention;

FIG. 3 is a diagram of a version management model provided by the present invention;

FIG. 4 is a diagram illustrating an example of warehousing and warehousing digital entities provided by the present invention;

FIG. 5 is an exemplary diagram of conflict identification and handling between digital entities provided by the present invention;

FIG. 6 is a schematic structural diagram of a management device according to the present invention;

fig. 7 is a schematic structural diagram of another management device provided in the present invention.

Detailed Description

The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of implementations consistent with certain aspects of the invention.

The terminology used in the description is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this specification, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in this specification refers to and encompasses any and all possible combinations of one or more of the associated listed items. Unless stated to the contrary, the terms "first," "second," and the like, as used herein, are used to distinguish one object from another, and are not used to limit the order, sequence, priority, or importance of the objects.

In order to facilitate understanding of the technical solutions provided by the present invention, before describing the present invention, some terms in the present invention are first explained to facilitate understanding of those skilled in the art.

The digital entities related to the invention refer to service data objects in different information systems, and the service data objects are usually determined from the use level of an actual user, for example, personal information and account information of the user can be regarded as two digital entities or one digital entity, and how to divide the digital entities depends on the needs of service scenes.

The digital asset library according to the present invention refers to a database that manages digital entities as digital assets. By storing digital entities in a digital asset repository, the importance of digital entities as core assets of an enterprise information system is highlighted.

The version management of the present invention refers to a traceable version control mechanism formed by changing the same digital entity for many times, that is, a version chain changing with time will be formed by changing information on the same digital entity for many times.

The data access related by the invention refers to accessing the digital entity through the access interface with unified specification, and provides a unified and standardized way for data source tracing, responsibility tracking and digital entity reutilization of enterprises.

The digital entity management related by the invention is essentially the management of the digital asset library of the enterprise, and the management concept of the digital asset library integrates the concept of the table in the relational database and the version concept of the software source code management (which will be specifically introduced below).

Referring to fig. 1, the present invention provides a method for managing a digital entity, which includes the following steps:

s11, constructing an entity relationship model, wherein the entity relationship model comprises the incidence relation among all digital entities.

In some embodiments, according to business requirements, each digital entity that needs to be stored may be investigated, investigation data corresponding to any one of the digital entities may be determined, and an association relationship between the digital entities may be determined. The research data may include, but is not limited to: the information system to which any digital entity belongs, each field contained by any digital entity, the data type of any field in each field, and the primary key field in each field.

In a specific implementation, the data type of any one of the above fields may include, but is not limited to: string, integer, floating point, date, time, datetime, boolean.

In particular implementations, only one field of a digital entity can be a primary key field.

In the embodiment of the invention, the digital entities to be stored are investigated, different digital entities divided according to business requirements can be abstracted, a foundation is laid for the subsequent storage of the digital entities, and the complex relationship among the digital entities in the real business can be cleared conveniently.

In some embodiments, after the research data corresponding to any one of the digital entities that needs to be stored is obtained, the research data may be saved.

As an example, taking a digital entity as customer information, the research data of the digital entity may be saved using a table as shown in fig. 2. That is, the information system to which the digital entity belongs is a Customer Relationship Management (CRM) information system, the fields included in the digital entity include an ID (the data type of the field is string), the latest contact time (the data type of the field is time), a mobile phone (the data type of the field is string), and the like, and the primary key field is an ID.

In some embodiments, the any digital entity may be initialized based on the research data. This process can be understood as similar to Entity-Relationship Diagram (ER Diagram) design in software development, that is, an original digital Entity is converted into a configurable operation that can be maintained and operated by a service staff through a higher-level abstraction.

In some embodiments, the entity relationship model may be constructed according to the initialized association relationship between any digital entity and each digital entity.

In specific implementation, the association relationship between the digital entities can be one-to-one, one-to-many, and many-to-many (convertible to one-to-many processing).

In specific implementation, the process of constructing the entity relationship model according to the initialized association relationship between any digital entity and each digital entity may be understood as similar to the determination of the foreign key relationship on the ER diagram in the existing software development process, or may be understood as the determination of the reference relationship between each digital entity to be stored. Wherein the primary key on one digital entity (referred to as a foreign key with respect to another digital entity) is always dependent on the primary key of another digital entity.

In the embodiment of the invention, the entity relationship model is constructed for the digital entity to be stored, so that the digital entity can be conveniently stored and accessed in a storage mode subsequently, and unified storage and historical change tracing of any heterogeneous service data are conveniently realized.

And S12, constructing a version management model, wherein the version management model is used for managing the change abstraction of the digital entity into the version update of the digital entity after the digital entity is put into a digital asset library.

In particular, the version management model may be understood as an abstract concept that can be used to manage changes (e.g., field changes) to digital entities after the digital entities are repeatedly warehoused in a digital asset library, and can generally support addition, update, deletion, access operations, and extension of conflict management (described in detail below).

In some embodiments, the version management model may include, but is not limited to: the system comprises a system table, an entity field table, a warehousing number and entity association relation table and an entity warehousing record table. As an example, the version management model may be as shown in FIG. 3.

In specific implementation, as shown in fig. 3, the system table may be used to manage records according to the attribution of the information system, that is, the digital entities managed in the digital asset library are managed according to the attribution of the system, where one information system may have a plurality of digital entities, and only one digital entity in one information system can be operated in one entry and exit. The entity table may be used to describe the digital entity, i.e., the entity table may create a description of the digital entity in the digital asset library using the research data described above. The entity field table can be used for describing field information in the middle of the digital entity, and is convenient to provide support for warehousing and warehousing of subsequent digital entities together with the entity table. The warehousing number table may be used to record a warehousing number generated by the digital entity each time the digital entity is warehoused, where each warehousing operation of the digital entity is a warehousing operation of the digital entity in one information system, and each warehousing operation generates a globally unique warehousing number. The warehousing number and entity association relation table can be used for information of digital entities during warehousing every time, wherein when a certain digital entity is in warehousing and any information is possibly not updated, the VIRTUAL _ INPUT field can be marked as true, and the VIRTUAL _ ID is associated to the warehousing number corresponding to the last updating of the digital entity which is traced forward and is corresponding to the last updating of the digital entity. The entity entry table can be used for recording the instantiation information of the digital entity entering the digital asset library according to the entity field, namely, according to the entity field table, the digital entity entering the library is instantiated into a record and stored in the entity entry record for subsequent ex-warehouse and data query.

In the embodiment of the invention, the digital entity is managed through the version management model, and based on the version management concept, the data of the digital asset library is in a constant increment process, namely, any data in the digital asset library cannot be deleted by any operation on the digital entity, and only a new warehousing number is generated and a new association relation is established with the new warehousing number, so that the method is different from the traditional business object management, and the unified storage and the historical change tracing of any heterogeneous business data are realized.

And S13, providing a unified digital entity access interface of the digital asset library, wherein the unified digital entity access interface is used for supporting various operations of the digital entity on the digital asset library.

In some embodiments, the unified digital entity access interface may include, but is not limited to: the unified digital entity access interface comprises: the system comprises a digital entity warehousing interface, a digital entity ex-warehouse interface, a HEAD resetting interface, a label setting interface, a label deleting interface and a label modifying interface, wherein the interfaces cover operations of adding, updating, deleting, accessing and the like of the digital entity.

In specific implementation, the digital entity warehousing interface can be used for supporting digital entity warehousing operation on a digital asset library, the warehousing operation comprises adding operation, repeated warehousing operation and deleting operation, and the digital entity warehousing interface can be set to only support digital entity warehousing in one information system at a time. The digital entity ex-warehouse operation interface can be used for supporting the ex-warehouse operation and the access operation of the digital entities on the digital entities stored in the digital asset library, wherein the digital entity ex-warehouse interface can be set to only support the ex-warehouse operation and the access operation of the digital entities in one information system at a time. The reset HEAD interface may be used to support the resetting of HEAD pointers in a specified information system stored in the digital asset library to a specified warehousing number. The set tag interface may be used to support tagging of a warehousing number of a specified digital entity stored in the digital asset library. The delete tag interface may be used to support the deletion of tags stored in the digital asset library that specify the warehousing number settings of the digital entity. The modify tag interface may be used to support modifying tags stored in the digital asset library that specify a binning numbering setting for a digital entity.

As an example, the digital entity access interface specification corresponding to the digital entity warehousing interface may be as follows:

(1) Interface address:

/api/v1/entity/import

(2) The request method comprises the following steps:

POST

(3) Request parameters:

(1) inquiring parameters: is free of

(2) Path parameters: is free of

(3) Request body parameters:

field(s)	Data type	Whether or not to fill	Description of the invention
				records	Array<Record>	Is that	Entities to be warehoused
sysVer	string	Whether or not	Digital entity management system version, normally returned by the system
				commitId	string	Whether or not	Requesting the last submission number recorded by the client system, and if the number is null, indicating that the file is put in storage for the first time

Record object:

field(s)	Data type	Whether or not to fill	Description of the invention
				system	string	Is that	Belonging system
entity	string	Is that	Belonging to the entity
				record	Array<FVPair>	Is that	A single entity

FVPair object:

field(s)	Data type	Whether or not to fill	Description of the invention
				field	string	Is that	Name of field
value	string	Is that	Field value

(4) A request head:

field(s)	Data type	Whether or not to fill	Description of the invention
				Content-Type	string	Is that	Default value is application/json
X-DES-TOKEN	string	Is that	Token issued by a digital entity management system
				X-TIMESTAMP	string	Is that	Timestamp of current requesting client

(4) And returning a result:

field(s)	Type of data	Description of the invention
			status	int	System response status code
data	string	The system responds to the message and, when the processing is successful,returning the new number generated in the warehouse, and drawing the corresponding digital entity according to the number
			message	string	System response messages, returning error messages from this field when processing fails or when there is an internal exception to the system
sys-ver	string	Digital entity management system version
			timestamp	string	Current server timestamp
traceId	string	Request tracking id

As an example, the digital entity access interface specification corresponding to the digital entity outbound interface may be as follows:

(1) Interface address:

/api/v1/entity/export/commit

(2) The request method comprises the following steps:

POST

(3) Request parameters:

(1) inquiring parameters: is composed of

(2) Path parameters: is composed of

(3) Request body parameters:

field(s)	Type of data	Whether or not to use Filling-in	Description of the preferred embodiment
				queryField	Array< QueryField>	Is that	Query parameters
sysVer	string	Whether or not	Digital entity management system version, usually returned by the system
				target	string	string	Warehouse-out mode, 0 represents warehouse-out through number, 1 represents warehouse-out through label
targetValue	string	Is that	Determining the number or label to be discharged according to the target field, and if the number is the number, filling the number or label Can fill in HEAD to indicate that the latest system of the corresponding digital entity management system is read Recording of submissions
				system	string	Is that	Belonging system
entity	string	Is that	Belonging entity

QueryField queries for field objects:

field(s)	Data type	Whether or not to fill	Description of the invention
				field	string	Is that	Name of section
value	string	Is that	Field value
				queryModel	string	Is that	Whether the matching is accurate or not, 1 represents accurate matching, and 0 represents fuzzy matching

(4) A request head:

field(s)	Type of data	Whether or not to fill	Description of the invention
				Content-Type	string	Is that	Default value is application/json
X-DES-TOKEN	string	Is that	Token issued by a digital entity management system
				X-TIMESTAMP	string	Is that	Timestamp of a currently requesting client

(4) And returning a result:

field(s)	Type of data	Description of the invention
			status	int	System response status code
data	Array<Record>	The system responds to the results and returns the queried digital entity when the processing is successful
			message	string	System response messages, returning error messages from this field when processing fails or when there is an internal exception to the system
sys-ver	string	Digital entity management system version
			timestamp	string	Current server timestamp
traceId	string	Request tracking id

Record object:

field(s)	Data type	Whether or not to fill	Description of the preferred embodiment
				system	string	Is that	Belonging system
entity	string	Is that	Belonging to the entity
				record	Array<FVPair>	Is that	A single entity

FVPair object:

field(s)	Data type	Whether or not to fill	Description of the preferred embodiment
				field	string	Is that	Name of field
value	string	Is that	Field value

As an example, resetting the digital entity access interface specification corresponding to the HEAD interface may be as follows:

(1) Interface address:

/api/v1/head/reset

(2) The request method comprises the following steps:

POST

(3) Request parameters:

(1) inquiring parameters: is free of

(2) Path parameters: is composed of

(3) Request body parameters:

field(s)	Type of data	Whether or not to fill	Description of the invention
				sysVer	string	Whether or not	Digital entity management system version, normally returned by the system
system	string	Is that	System for resetting HEAD pointer
				commitId	string	Is that	The HEAD pointer of the corresponding system is reset to the specified warehousing number for compiling

(4) A request head:

field(s)	Data type	Whether or not to fill	Description of the preferred embodiment
				Content-Type	string	Is that	Default value is application/json
X-DES-TOKEN	string	Is that	Token issued by a digital entity management system
				X-TIMESTAMP	string	Is that	Timestamp of a currently requesting client

(4) And returning a result:

field(s)	Data type	Description of the preferred embodiment
			status	int	System response status code
data	boolean	System response message, true indicates successful processing, false indicates failed processing
			message	string	System response message, when processing fails or system internal exception occurs, an error message is returned from the field
sys-ver	string	Digital entity management system version
			timestamp	string	Current server timestamp
traceId	string	Request tracking id

As an example, the digital entity access interface specification corresponding to the tag interface may be set as follows:

(1) Interface address:

/api/v1/label/create

(2) The request method comprises the following steps:

POST

(3) Request parameters:

(1) inquiring parameters: is free of

(2) Path parameters: is free of

(3) Request body parameters:

field(s)	Data type	Whether or not to fill	Description of the preferred embodiment
				sysVer	string	Whether or not	Digital entity management system version, normally returned by the system
commitId	string	Is that	The number of the last warehousing of the HEAD representation in the digital entity management system can be transmitted to the warehousing compiling to be labeled
				label	string	Is that	Tag name, length limited to 50 characters, unique in digital entity management system

(4) A request head:

(4) And returning a result:

field(s)	Data type	Description of the preferred embodiment
			status	int	System response status code
data	boolean	System response message, true indicates successful processing, false indicates failed processing
			message	string	System response messages, returning error messages from this field when processing fails or when there is an internal exception to the system
sys-ver	string	Digital entity management system version
			timestamp	string	Current server timestamp
traceId	string	Request tracking id

As an example, the digital entity access interface specification corresponding to the delete tag interface may be as follows:

(1) Interface address:

/api/v1/label/delete

(2) The request method comprises the following steps:

POST

(3) Request parameters:

(1) inquiring parameters: is free of

(2) Path parameters: is composed of

(3) Request body parameters:

field(s)	Data type	Whether or not to fill	Description of the preferred embodiment
				label	string	Is that	The labels to be deleted only support the deletion of one label at a time, the given label names are exactly matched when the labels are deleted, if the labels are hit, the labels are deleted, otherwise, error messages are ignored and returned
sysVer	string	Whether or not	Digital entity management system version, normally returned by the system
				system	string	Is that	Belonging system
entity	string	Is that	Belonging to the entity

(4) A request head:

field(s)	Data type	Whether or not to fill	Description of the invention
				Content-Type	string	Is that	Default value is application/json
X-DES-TOKEN	string	Is that	Token issued by a digital entity management system
				X-TIMESTAMP	string	Is that	Timestamp of a currently requesting client

(4) And returning a result:

field(s)	Data type	Description of the invention
			status	int	System response status code
data	boolean	System response message, true indicates successful processing, false indicates failed processing
			message	string	System response message, when processing fails or system internal exception occurs, an error message is returned from the field
sys-ver	string	Digital entity management system version
			timestamp	string	Current server timestamp
traceId	string	Request tracking id

As an example, modifying the digital entity access interface specification corresponding to the tag interface may be as follows:

(1) Interface address:

/api/v1/label/update

(2) The request method comprises the following steps:

POST

(3) Request parameters:

(1) inquiring parameters: is composed of

(2) Path parameters: is free of

(3) Request body parameters:

field(s)	Data type	Whether or not to fill	Description of the invention
				originLabel	string	Is that	The label name to be modified is limited in length to 50 characters
newLabel	string	Is that	The modified label name has a length limited to 50 characters and is unique in the digital entity management system
				sysVer	string	Whether or not	Digital entity management system version, normally returned by the system

(4) A request head:

field(s)	Data type	Whether or not to fill	Description of the preferred embodiment
				Content-Type	string	Is that	Default value is application/json
X-DES-TOKEN	string	Is that	Token issued by a digital entity management system
				X-TIMESTAMP	string	Is that	Timestamp of current requesting client

(4) And returning a result:

field(s)	Data type	Description of the invention
			status	int	System response status code
data	boolean	System response message, true indicates successful processing and false indicates failed processing
			message	string	System response message, when processing fails or system internal exception occurs, an error message is returned from the field
sys-ver	string	Digital entity management system version
			timestamp	string	Current server timestamp
traceId	string	Request tracking id

In the embodiment of the invention, by providing the uniform digital entity access interface of the digital asset library, the old information system in an enterprise can realize the storage and the update of the digital entity at extremely low cost without reconstructing a bottom data structure, so that the historical change and the trace of the data of the information systems can be managed in a centralized way at extremely low cost, the reconstruction cost of the information systems can be greatly reduced, and the asset application of the service data is realized.

And S14, after the first digital entity is detected to be put into the digital asset library through the unified digital entity access interface, the change of the first digital entity is abstracted into the version update of the first digital entity through the version management model, and the version information corresponding to the first digital entity is obtained.

In particular implementation, the first digital entity is one of the digital entities that needs to be stored.

In the implementation, the first digital entity is added and updated into two modification forms after the first digital entity is put into the digital asset library, and the digital entity stored in the digital asset library cannot be deleted from the aspect of asset management, so that the deletion of the first digital entity is a variant of the first digital updating operation.

In some embodiments, if the first digital entity is changed to be a newly added first digital entity, a warehousing number corresponding to the current warehousing operation of the first digital entity may be generated through the version management model, and the warehousing number is written to the first digital entity as a HEAD pointer to obtain version information of the first digital entity, so as to quickly query a latest record of the first digital entity from the perspective of the first digital entity. The version information comprises a warehousing number, and the warehousing number is used for pointing to the record of the first digital entity in warehousing at this time.

In specific implementation, a single first digital entity can be newly added to the warehousing digital asset library, or a plurality of first digital entities can be newly added to the warehousing digital asset library in batches.

As an example, as shown in fig. 4, taking the first digital entity as entity1 as an example, each warehousing of the first digital entity may be carried with a warehousing number corresponding to the last ex-warehouse.

In other embodiments, if the first digital entity is changed to be an updated first digital entity, when the first digital entity changes after being updated, a warehousing number corresponding to the current warehousing operation of the first digital entity is generated through the version management model, and the warehousing number is written to the first digital entity as a HEAD pointer to obtain version information of the first digital entity, so as to quickly query the latest record of the first digital entity from the perspective of the first digital entity. The version information comprises a warehousing number, and the warehousing number is used for pointing to the latest record of the current warehousing of the first digital entity. Or when the first digital entity is not changed after being updated, generating a warehousing number corresponding to the current warehousing operation of the first digital entity through the version management model, and associating the warehousing number of the current warehousing to the warehousing number of the first digital entity which is subjected to the last change of the previous source.

In implementation, a single first digital entity may be updated, or a plurality of first digital entities may be updated in batch.

In still other embodiments, if the change to the first digital entity is to delete the first digital entity, a warehousing number corresponding to the current deletion operation of the first digital entity is generated through the version management model, and the relationship between the first digital entity and the digital asset library is interrupted through the warehousing number.

In the embodiment of the invention, the digital entity is uniformly managed through the version management model by skillfully borrowing the concept of the relational database table and the version control concept of the software source code management tool, so that the problem of tracing the change history of the heterogeneous data is solved.

In an applicable scenario provided by the embodiment of the present invention, the version management model may further include a tag table, which may be as shown in fig. 3. In specific implementation, the tag table may be used to record tags added by the user digital entity, where the tags correspond to the warehousing numbers in the warehousing number table one to one, that is, one tag always corresponds to one unique warehousing number.

In specific implementation, a first tag added to the first digital entity by the user at the first time point is received, and then the first tag may point to the warehousing number of the first digital entity that is closest to the first time point. The first time point is any time point after the first digital entity is put in storage.

In the embodiment of the invention, the version management model can mark digital assets uniformly on key time nodes in batches, wherein the digital assets are collected by a user from the management side, and the uniformly marked digital assets are usually a digital entity set with a certain association relationship, and can acquire the required digital entity set in batches by using the tags from the management side.

And S15, storing the first digital entity into a digital asset library according to the entity relationship model and the version information corresponding to the first digital entity.

In implementation, by performing step S15, a determination basis for subsequent digital entity access can be determined.

In the implementation of the invention, the first digital entity is stored in the digital asset library according to the entity relationship model and the version information corresponding to the first digital entity, so that the concept of a relational database table and the version control concept of a software source code management tool can be skillfully borrowed, the digital entities are uniformly stored through the version management model, and the problem of uniform storage of heterogeneous data is solved.

In an applicable scenario provided in the embodiment of the present invention, the method for managing a digital entity provided in the embodiment of the present invention may further include the following steps:

and S16, when detecting that the user accesses the second digital entity through the unified digital entity access interface in a corresponding mode, returning corresponding data of the second digital entity to the user according to the corresponding mode.

In particular implementations, the second digital entity is one of the digital entities stored in the digital asset library.

In some embodiments, the execution manner of step S16 may include, but is not limited to, the following three:

in a first mode

And when detecting that the user accesses the second digital entity by adopting the first warehousing number through the unified digital entity access interface, returning the record of the second digital entity corresponding to the first warehousing number to the user.

Mode two

And when detecting that the user accesses the second digital entity by adopting the second label through the unified digital entity access interface, returning the record of the second digital entity corresponding to the warehousing number pointed by the second label to the user.

Mode III

In practical implementation, in step S16, for a specific certain digital entity, since the entity relationship model between digital entities is already recorded in the digital asset library, the associated data access capability thereof may also be provided.

In the implementation, in step S16, the digital entity access may also be extended, such as obtaining a version record of a single digital entity and deleting a tag.

In the embodiment of the invention, different ways are provided for accessing the digital entities stored in the digital asset library, so that the user can conveniently and uniformly access heterogeneous data.

As shown in fig. 4, when the same digital entity is referenced by multiple external systems and then warehoused, due to the constraint of the version management model, the warehousing-after operation may conflict with the warehousing-before operation on the digital entity. In view of this, in the embodiment of the present invention, when it is detected that a conflict occurs in the digital asset library put in storage after the same third digital entity is referred by a plurality of external systems, the conflict is refined to a field included in the third digital entity to obtain a conflict field corresponding to the third digital entity, and then the conflict field is output to prompt a user to perform processing, that is, a decision right of the conflict processing is provided to the user, so as to perform unified management and historical change tracing on the digital entity. Wherein, the third digital entity is one of the above digital entities to be stored.

For example, as shown in fig. 4 and fig. 5, when the user goes out of the warehouse for the first time, the user will simultaneously obtain the data and the warehouse-in number when the data going out of the warehouse corresponds to the warehouse-in number for the second time. And the user modifies the data of the digital entity after leaving the warehouse, and updates the data of the digital asset warehouse to the data corresponding to the third warehousing number when another user warehouses the data. And (4) when the current user operates the warehouse entry, the corresponding data before the warehouse entry is the second warehouse entry number, but at the moment, the data in the asset warehouse is corresponding to the third warehouse entry, the conflict is generated, and the user is prompted to process the data. And after the user finishes processing, continuously warehousing the processed data by adopting the mode, wherein the warehousing number corresponding to the warehousing number is the fourth warehousing number. And finishing the conflict processing and finishing the fourth warehousing.

As can be seen from the above description, compared with the prior art, in the present invention, an entity relationship model is constructed, where the entity relationship model includes an association relationship between digital entities, and the digital entities are service data objects in different information systems; constructing a version management model, wherein the version management model is used for abstracting the change of the digital entity into the version update of the digital entity after the digital entity is put into a digital asset library and managing the version update of the digital entity; providing a uniform digital entity access interface of the digital asset library, wherein the uniform digital entity access interface is used for supporting various operations of a digital entity on the digital asset library; after detecting that the first digital entity is put into a digital asset library through the unified digital entity access interface, abstracting the change of the first digital entity into the version update of the first digital entity through a version management model, and obtaining the version information corresponding to the first digital entity; the first digital entity is one of the digital entities; the first digital entity is stored in the digital asset library according to the entity relationship model and the version information. By the method, the concept of the relational database table and the version control concept of the software source code management tool can be borrowed skillfully, the digital entity is managed by the version management model, and the unified management, historical change tracing and unified access to different heterogeneous service data in different information systems can be realized.

Based on the same inventive concept, an embodiment of the present invention further provides a management device, as shown in fig. 6, the management device may include:

the building unit 21 is configured to build an entity relationship model, where the entity relationship model includes an association relationship between digital entities, and the digital entities are service data objects in different information systems; constructing a version management model, wherein the version management model is used for abstracting the change of the digital entity into the version update of the digital entity for management after the digital entity is put into a digital asset library;

the processing unit 22 is configured to provide a unified digital entity access interface of the digital asset library, where the unified digital entity access interface is configured to support various operations of the digital entity on the digital asset library; after detecting that a first digital entity is put into a digital asset library through a uniform digital entity access interface, abstracting the change of the first digital entity into the version update of the first digital entity through a version management model to obtain the version information corresponding to the first digital entity; the first digital entity is one of the digital entities; the first digital entity is stored in the digital asset library according to the entity relationship model and the version information.

In one possible design, the building unit 21 is specifically configured to:

and constructing an entity relationship model according to any initialized digital entity and the association relationship.

In one possible design, the version management model includes: a system table, an entity field table, a warehousing number and entity association relation table and an entity warehousing record table; the system table is used for managing and recording according to the attribution of the information system; the entity table is used for describing the digital entity; the entity field table is used for describing field information in the middle of the digital entity; the warehousing number table is used for recording warehousing numbers generated by the digital entities in each warehousing; the warehousing number and entity association relation table is used for information of the digital entity in warehousing each time; and the entity entry table is used for recording the information instantiated according to the entity fields after the digital entities are entered into the digital asset library.

In one possible design, the processing unit 22 is specifically configured to:

if the first digital entity is changed into a newly-added first digital entity, generating a warehousing number corresponding to the current warehousing operation of the first digital entity through a version management model, writing the warehousing number as an HEAD pointer to the first digital entity, and obtaining version information of the first digital entity, wherein the version information comprises the warehousing number which is used for pointing to a record of the current warehousing of the first digital entity; alternatively, the first and second electrodes may be,

if the first digital entity is changed into an updated first digital entity, when the first digital entity is changed after being updated, generating a warehousing number corresponding to the current warehousing operation of the first digital entity through a version management model, and writing the warehousing number as a HEAD pointer to the first digital entity to obtain version information of the first digital entity, wherein the version information comprises the warehousing number which is used for pointing to the latest record of the current warehousing of the first digital entity; alternatively, the first and second electrodes may be,

and if the first digital entity is changed into the deleted first digital entity, generating a warehousing number corresponding to the current deletion operation of the first digital entity through the version management model, and interrupting the relationship between the first digital entity and the digital asset library through the warehousing number.

In one possible design, the version management model further comprises a label table, wherein the label table is used for recording labels added by the user digital entities, and the labels correspond to the warehousing numbers in the warehousing number table one by one; the processing unit 22 is further configured to:

receiving a first label added by a user for a first digital entity at a first time point;

In one possible design, the processing unit 22 is further configured to:

when detecting that a user accesses a second digital entity by adopting a first warehousing number through a unified digital entity access interface, returning a record of the second digital entity corresponding to the first warehousing number to the user; the second digital entity is one of the digital entities stored in the digital asset library; alternatively, the first and second liquid crystal display panels may be,

when detecting that the user accesses the second digital entity by adopting the second label through the unified digital entity access interface, returning the record of the second digital entity corresponding to the warehousing number pointed by the second label to the user; alternatively, the first and second electrodes may be,

In one possible design, the processing unit 22 is further configured to:

when detecting that the same third digital entity is referred by a plurality of external systems and conflicts are generated in a warehousing digital asset library, refining the conflicts to fields contained in the third digital entity to obtain conflict fields corresponding to the third digital entity; the third digital entity is one of the digital entities;

and outputting a conflict field to prompt the user to process.

In one possible design, the unified digital entity access interface includes: the method comprises the steps of inputting a digital entity into a warehouse, outputting the digital entity from the warehouse, resetting a HEAD interface, setting a label interface, deleting the label interface and modifying the label interface; the digital entity warehousing interface is used for supporting digital entity warehousing operation on a digital asset library, wherein the warehousing operation comprises a new adding operation, a repeated warehousing operation and a deleting operation; the digital entity ex-warehouse operation interface is used for supporting the ex-warehouse operation and the access operation of the digital entity on the digital entity stored in the digital asset library; the reset HEAD interface is used for supporting the HEAD pointer in the appointed information system stored in the digital asset library to be reset to an appointed warehousing number; the label setting interface is used for supporting the setting of labels for warehousing serial numbers of specified digital entities stored in a digital asset library; the label deleting interface is used for supporting the deletion of a label set by the warehousing number of the specified digital entity stored in the digital asset library; the modified tag interface is used for supporting modification of tags of the warehousing number setting of the specified digital entities stored in the digital asset library.

The management apparatus in the embodiment of the present invention and the management method of the digital entity shown in fig. 1 are based on the same conception, and through the foregoing detailed description of the management method of the digital entity, a person skilled in the art can clearly understand the implementation process of the management apparatus in the embodiment, so for the sake of brevity of the description, details are not repeated here.

Based on the same inventive concept, an embodiment of the present invention further provides a management device, as shown in fig. 7, the management device may include: at least one memory 31 and at least one processor 32. Wherein:

the at least one memory 31 is used to store one or more programs.

The one or more programs, when executed by the at least one processor 32, implement the method of managing digital entities illustrated in fig. 1 and described above.

The management device may also optionally include a communication interface for communication and data exchange with external devices.

It should be noted that the memory 31 may include a high-speed RAM memory, and may also include a nonvolatile memory (nonvolatile memory), such as at least one disk memory.

In a specific implementation process, if the memory 31, the processor 32 and the communication interface are integrated on a chip, the memory 31, the processor 32 and the communication interface may complete mutual communication through an internal interface. If the memory 31, the processor 32 and the communication interface are implemented independently, the memory 31, the processor 32 and the communication interface may be connected to each other through a bus and perform communication with each other.

Based on the same inventive concept, embodiments of the present invention also provide a computer-readable storage medium, which may store at least one program, and when the at least one program is executed by a processor, the method for managing a digital entity as shown in fig. 1 is implemented.

It should be understood that the computer-readable storage medium is any data storage device that can store data or programs which can thereafter be read by a computer system. Examples of computer-readable storage media include: read-only memory, random access memory, CD-ROM, HDD, DVD, magnetic tape, optical data storage devices, and the like.

The computer readable storage medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

Program code embodied on a computer readable storage medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, radio Frequency (RF), etc., or any suitable combination of the foregoing.

The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is specific and detailed, but not to be understood as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention.

Claims

1. A method for managing digital entities, comprising:

storing the first digital entity into the digital asset library according to the entity relationship model and the version information;

wherein abstracting, by the version management model, a change to the first digital entity to a version update of the first digital entity to obtain version information corresponding to the first digital entity includes:

if the first digital entity is changed into an updated first digital entity, when the first digital entity is changed after being updated, generating a warehousing number corresponding to the current warehousing operation of the first digital entity through the version management model, writing the warehousing number as a HEAD pointer on the first digital entity, and obtaining version information of the first digital entity, wherein the version information comprises the warehousing number which is used for pointing to the latest record of the current warehousing of the first digital entity; alternatively, the first and second liquid crystal display panels may be,

2. The method of claim 1, wherein building an entity-relationship model comprises:

according to business requirements, conducting investigation on each digital entity needing to be stored, determining investigation data corresponding to any one of the digital entities, and determining an incidence relation between the digital entities; the research data comprises an information system to which the any digital entity belongs, each field contained by the any digital entity, the data type of any field in each field and a primary key field in each field;

3. The method of claim 1 or 2, wherein the version management model comprises: a system table, an entity field table, a warehousing number and entity association relation table and an entity warehousing record table; the system table is used for managing and recording according to the attribution of the information system; the entity table is used for describing digital entities; the entity field table is used for describing field information in the middle of the digital entity; the warehousing number table is used for recording warehousing numbers generated by the digital entities in warehousing each time; the warehousing number and entity association relation table is used for information of the digital entity in warehousing every time; and the entity entry table is used for recording the information instantiated according to the entity field after the digital entity is entered into the digital asset library.

4. The method of claim 3, wherein the version management model further comprises a tag table, the tag table is used for recording tags added by user digital entities, and the tags are in one-to-one correspondence with warehousing numbers in the warehousing number table; the method further comprises the following steps:

5. The method of claim 4, wherein after storing the first digital entity in the digital asset library according to the entity relationship model and the version information, the method further comprises:

when detecting that a user accesses a second digital entity by adopting a first warehousing number through the unified digital entity access interface, returning the record of the second digital entity corresponding to the first warehousing number to the user; the second digital entity is one of the digital entities stored in the digital asset library; alternatively, the first and second liquid crystal display panels may be,

6. The method of claim 5, wherein the method further comprises:

and outputting the conflict field to prompt the user to process.

7. The method of claim 3, wherein the unified digital entity access interface comprises: the method comprises the steps of inputting a digital entity into a warehouse, outputting the digital entity from the warehouse, resetting a HEAD interface, setting a label interface, deleting the label interface and modifying the label interface; the digital entity warehousing interface is used for supporting digital entity warehousing operation on the digital asset library, and the warehousing operation comprises a new adding operation, a repeated warehousing operation and a deleting operation; the digital entity ex-warehouse operation interface is used for supporting the ex-warehouse operation and the access operation of the digital entity on the digital entity stored in the digital asset library; the HEAD resetting interface is used for supporting the HEAD pointer in a specified information system stored in the digital asset library to be reset to a specified warehousing number; the setting label interface is used for supporting the setting label of the warehousing serial number of the specified digital entity stored in the digital asset library; the label deleting interface is used for supporting the deletion of a label set by a warehousing number of a specified digital entity stored in the digital asset library; and the modified tag interface is used for supporting modification of tags of the warehousing number setting of the specified digital entities stored in the digital asset library.

8. A management device, comprising: at least one memory and at least one processor;

the at least one memory is for storing one or more programs;

the one or more programs, when executed by the at least one processor, implement the method of any of claims 1-7.

9. A computer-readable storage medium characterized in that the computer-readable storage medium stores at least one program; the at least one program, when executed by a processor, implements the method of any of claims 1-7.