Project space-based asset collection method and related device

By creating and managing asset cards in the project space, various asset forms management problems have been solved, effective collection and precipitation of assets have been achieved, and team collaboration efficiency has been improved.

CN118917786APending Publication Date: 2024-11-08BEIJING CHUANGZUOMEIHAO TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410934250.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-12
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

During project delivery, existing technology fails to effectively manage multiple asset forms, resulting in team members spending more time and energy when finding and using assets, affecting team collaboration efficiency.

Method used

By creating asset cards in the project space, loading design drawings, super documents, thinking cloud diagrams and external links, and supporting editing, moving, deleting, alignment, grouping and permission allocation operations, real-time storage and management of assets are achieved.

Benefits of technology

It reduces information asymmetry within the team, enables project members to obtain project information at the lowest cost, realizes effective collection and precipitation of assets, and improves team collaboration efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118917786A_ABST
    Figure CN118917786A_ABST
Patent Text Reader

Abstract

The invention discloses an asset collection method based on a project space and a related device.The method comprises the steps that an asset card of the project space is created through a canvas page, and the asset card comprises thumbnails, names, descriptions and annotation information; loading a design drawing, a super document, a thinking cloud picture and an external link of a design file entity through the asset card; editing operation is conducted on the corresponding design file entity through the asset card, and the operation of the asset card comprises movement, deletion, alignment, grouping and permission distribution operation; and storing the asset card and the corresponding design file entity in real time. According to the method, more diversified asset bearing forms are introduced into the same canvas, so that a user can obtain related information of a project at the lowest cost in the design delivery process, team assets are effectively collected and precipitated, project members can freely visit all data in the project, and information asymmetry in the team is reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of software design, and in particular to an asset collection method based on project space and related devices. Background Art

[0002] Design delivery refers to the process in which designers deliver design drawings to R&D engineers, thereby helping R&D engineers to convert the design drafts into code. Design delivery tools generally support asset management of design drawings and their code information during the project delivery process, but do not provide unified collection management for more diverse asset forms. In the product development process, in addition to design drawings and code information, many other asset forms are involved, such as documents, pictures, etc., which also need to be effectively managed to ensure the smooth progress of the project. Due to the lack of unified collection management for more diverse asset forms, team members need to spend more time and energy to find and use these assets, which affects the efficiency of team collaboration.

[0003] To solve the above problems, the present invention not only displays the design drawings, but also introduces more diverse asset carrying forms in the same canvas, so that project members can obtain relevant information about the project at the lowest cost during the design delivery process, and the team assets can be effectively collected and accumulated. Summary of the invention

[0004] In view of the above problems, an asset collection method based on project space and related devices are proposed to enable project members to obtain relevant information of the project at the lowest cost during the design delivery process, so that team assets can be effectively collected and accumulated.

[0005] According to one aspect of the present invention, there is provided a project space-based asset collection method, comprising:

[0006] Create an asset card for the project space through a canvas page, wherein the asset card includes a thumbnail, a name, a description, and annotation information;

[0007] Loading design drawings, super documents, mind cloud maps and external links of design file entities through the asset cards;

[0008] Performing editing operations on the corresponding design file entity through the asset card, wherein the operations of the asset card include moving, deleting, aligning, grouping and authority allocation operations;

[0009] The asset card and the corresponding design file entity are stored in real time.

[0010] In an optional manner, the asset card is displayed in the canvas page in a scaled-down form via a thumbnail.

[0011] In an optional manner, the external link card supports opening the link in a new tab, renaming the link, and recycling it to the recycle bin after deletion;

[0012] The external link card is prohibited from merging status diagrams, sharing, and downloading operations.

[0013] In an optional manner, the link name of the external link card is displayed differently according to whether the address can obtain a title and a description;

[0014] Among them, when the web page title and description are obtained, the web page title, logo, description and domain name are displayed; when the web page description cannot be obtained, the web page title, logo and domain name are displayed; when the web page title and description cannot be obtained, only the link is displayed.

[0015] In an optional manner, the method further includes:

[0016] The mind cloud maps and external links created on the canvas page belong to the project. Their seats and roles are consistent with the project, and the operation permissions of the corresponding files are consistent with the operation permissions of the project.

[0017] In an optional manner, the editing operation on the corresponding design file entity through the asset card further includes:

[0018] For design drawings, super documents and mind cloud maps, edit the corresponding design file entities;

[0019] For external links, move, delete, align, and group them.

[0020] In an optional manner, the functions of the super document include but are not limited to: team documents, knowledge base space, content writing and collaboration, basic functions, management background, enterprise information and management, organizational structure, role permissions, security management, information access, approval center, system settings, disk monitoring, open platform, login and organizational structure synchronization functions.

[0021] According to another aspect of the present application, there is provided an asset collection device based on project space, comprising:

[0022] A creation module, used to create an asset card of a project space through a canvas page, wherein the asset card includes a thumbnail, a name, a description, and annotation information;

[0023] A loading module, used to load the design drawings, super documents, mind cloud maps and external links of the design file entity through the asset card;

[0024] An editing module, used to perform editing operations on the corresponding design file entity through the asset card, wherein the operations of the asset card include moving, deleting, aligning, grouping and permission allocation operations;

[0025] The storage module is used to store the asset card and the corresponding design file entity in real time.

[0026] According to another aspect of the present application, there is provided a computing device, comprising: a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus;

[0027] The memory is used to store at least one executable instruction, and the executable instruction enables the processor to execute operations corresponding to the above-mentioned project space-based asset collection method.

[0028] According to another aspect of the present application, a computer program product is provided, comprising at least one executable instruction, wherein the executable instruction enables a processor to perform operations corresponding to the above-mentioned project space-based asset aggregation method.

[0029] The solution provided by the above embodiment of the present invention is to create an asset card of the project space through a canvas page, wherein the asset card includes a thumbnail, name, description and annotation information; load the design drawing, super document, mind cloud map and external link of the design file entity through the asset card; edit the corresponding design file entity through the asset card, wherein the operations of the asset card include moving, deleting, aligning, grouping and permission allocation operations; and store the asset card and the corresponding design file entity in real time. The present invention introduces more diverse asset carrying forms in the same canvas, allowing users to obtain relevant information about the project at the lowest cost during the design delivery process, so that team assets can be effectively collected and precipitated, and project members can freely browse all the materials in the project, reducing information asymmetry within the team.

[0030] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above description and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0032] Figure 1 A schematic diagram showing a flow chart of an asset collection method based on project space according to an embodiment of the present invention;

[0033] Figures 2 to 3 A schematic diagram of a design diagram of an embodiment of the present invention is shown;

[0034] Figure 4 A thumbnail of an asset card according to an embodiment of the present invention is shown;

[0035] Figure 5 A mind cloud map / super document display diagram of an embodiment of the present invention is shown;

[0036] Figure 6 A schematic diagram of super document editing according to an embodiment of the present invention is shown;

[0037] Figure 7 A thought cloud diagram display diagram of an embodiment of the present invention is shown;

[0038] Figure 8a to Figure 8b A general operation diagram of a link card element according to an embodiment of the present invention is shown;

[0039] Fig. 9 A schematic diagram of a recycling station according to an embodiment of the present invention is shown;

[0040] Fig.10 A schematic diagram of a new tab page of a link card element according to an embodiment of the present invention is shown;

[0041] Fig.11 A functional structure diagram of a project space-based asset aggregation method and device according to an embodiment of the present invention is shown;

[0042] Fig.12 A schematic diagram of the structure of a computing device according to an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0043] The exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present invention and to enable the scope of the present invention to be fully communicated to those skilled in the art.

[0044] Embodiment 1:

[0045] Figure 1 FIG. 1 is a functional structure diagram of an asset collection method based on project space according to an embodiment of the present invention. Specifically, Figure 1 As shown, the following steps are included:

[0046] Step S101, creating an asset card of the project space through a canvas page, wherein the asset card includes a thumbnail, a name, a description, and annotation information.

[0047] In this embodiment, by creating asset cards of the project space through the canvas page, various assets in the project can be effectively organized and managed. Among them, the asset card, as a visual information display method, can clearly present the key information of the asset.

[0048] According to the project requirements and display effects, set the canvas size of the canvas page in the UI software design system, such as Figure 2 , Figure 3 As shown in the figure, plan an area on the canvas page for displaying asset cards, and adjust the size and position of the area as needed. Create asset cards for the project space on the canvas page. Asset cards contain thumbnails, names, descriptions, and annotation information. Optionally, you can copy asset cards according to project needs and adjust the size and spacing of each asset card.

[0049] Step S102, loading the design drawings, super documents, mind cloud maps and external links of the design file entity through the asset card.

[0050] For example, find and click "Load Design" or "Load Super Document" on the asset card to load the design according to the design file path or link stored in the asset card. The design file can be obtained from local storage, cloud storage or other sources. After loading, the design is opened in the specified preview area or new window for users to view and edit.

[0051] In an optional manner, the asset card is displayed in the canvas page in a scaled-down form via a thumbnail.

[0052] like Figures 4 to 5 As shown, after the asset card is successfully created, the canvas page displays the mind map / super document. The size of the asset card is fixed. When the canvas is zoomed in or out, the asset card is zoomed in or out in the same proportion. Optionally, the asset card can also be zoomed in or out separately. Among them, the strategy for obtaining the cover image is: when the cover is a mind map / super document file, it is a thumbnail (such as PNG format) of all elements in the full view state.

[0053] In this embodiment, the link name of the external link card is displayed differently according to whether the address can obtain the title and description.

[0054] Among them, when the web page title and description are obtained, the web page title, logo, description and domain name are displayed; when the web page description cannot be obtained, the web page title, logo and domain name are displayed; when the web page title and description cannot be obtained, only the link is displayed.

[0055] In an optional manner, the functions of the super document include but are not limited to: team documents, knowledge base space, content writing and collaboration, basic functions, management background, enterprise information and management, organizational structure, role permissions, security management, information access, approval center, system settings, disk monitoring, open platform, login and organizational structure synchronization functions.

[0056] Super Docs are multi-person real-time collaborative documents. They are not only a carrier for information expression and transmission, but also a tool for efficient organizational collaboration, knowledge accumulation, and project management in the work scenarios of production and research. In a team, team members can create independent documents or organize multiple documents into a knowledge tree as data accumulation within the team to increase information transmission efficiency. Super Docs can be used throughout all roles in production and research, and can be seamlessly connected with commonly used production and research tools.

[0057] In this embodiment, creating a super document in the asset card significantly improves the work efficiency and effectiveness of the organization in scenarios such as knowledge base accumulation, project management, and real-time collaboration. By creating a super document in the asset card, the knowledge, experience, cases, etc. within the organization can be stored in a structured form, so that the knowledge base is no longer a pile of scattered documents, but forms a hierarchical and structured knowledge system. In addition, the super document in the asset card can be quickly retrieved by labeling, classification, etc., and team members can quickly find the information they need. At the same time, document sharing has become very simple, and team members can easily view, edit and comment on documents, which promotes the circulation and sharing of knowledge. By creating a super document related to the project in the asset card, the documents of various stages such as project requirements, design, development, and testing can be centrally managed, which helps team members to understand the progress and status of the project at any time and promotes communication and collaboration between team members.

[0058] Step S103, editing the corresponding design file entity through the asset card, wherein the operations of the asset card include moving, deleting, aligning, grouping and permission allocation operations.

[0059] In this embodiment, by editing the corresponding design file entity on the asset card, the team can efficiently manage the design file. The operation functions of the asset card include moving, deleting, aligning, grouping and permission allocation, which greatly improves the flexibility and security of design file management. Among them, the deletion operation allows the user to delete the asset cards and their corresponding design files that are no longer needed from the system, keeping the design file library neat and orderly. The alignment operation can help users arrange multiple asset cards according to specific rules, such as left alignment, right alignment, center alignment, etc., so that the design files are more visually neat and beautiful, and improve the user's immersive experience. At the same time, it helps users find the required files faster and improves work efficiency. The grouping operation allows users to combine multiple related asset cards into a group, thereby realizing the classified management of design files. For example, different groups can be created according to the requirements of the project or the attributes of the design file (such as type, status, person in charge, etc.). Through permission allocation, the access and editing permissions of different users or user groups to design files can be accurately controlled to ensure that team members work within their respective responsibilities, further improving the security of the files.

[0060] In an optional manner, the external link card supports opening the link in a new tab, renaming the link, and recycling it to the recycle bin after deletion;

[0061] The external link card is prohibited from merging status diagrams, sharing, and downloading operations.

[0062] like Fig.10 As shown in the figure, when a user clicks an external link card, the link will be opened in a new browser tab to avoid affecting the use of the current page. Rename the external link card to make it more in line with the naming habits of individuals or teams. When a user deletes an external link card, the card is not immediately permanently deleted from the system, but is moved to the recycle bin. Fig. 9 As shown, in the recycle bin, you can retrieve and restore the accidentally deleted link cards, or completely delete the cards that are no longer needed. Since the external link card itself does not contain graphical elements such as state diagrams, it does not support the operation of merging state diagrams with other cards or elements to ensure the independence of the external link card. The external link card itself is just a reference to a link and does not contain the actual file content, so it does not support download operations.

[0063] In an optional manner, the method further includes:

[0064] The mind cloud maps and external links created on the canvas page belong to the project. Their seats and roles are consistent with the project, and the operation permissions of the corresponding files are consistent with the operation permissions of the project.

[0065] The mind cloud maps and external links created on the canvas page belong to the project, and their seats and roles are consistent with the project, ensuring that team members have permissions that match the project when accessing, editing or managing these elements. The operating permissions of the corresponding files are consistent with the operating permissions of the project. In other words, if a team member has specific permissions in the project (such as editing, viewing, deleting, etc.), he or she will have the same permissions when operating the mind cloud maps or external links related to the project. By closely associating mind cloud maps, external links and their files with projects and setting consistent operating permissions, the security and convenience of team collaboration are improved.

[0066] In an optional manner, the editing operation on the corresponding design file entity through the asset card further includes:

[0067] For design drawings, super documents and mind cloud maps, edit the corresponding design file entities;

[0068] For external links, move, delete, align, and group them.

[0069] In this embodiment, for the design drawing, the editing operation includes opening the design drawing editor to make various design modifications, such as adding, deleting, and moving graphic elements, adjusting properties such as color and font, saving and updating the design drawing version, etc. For super documents, the editing operation covers the addition, deletion, modification, and query of text content, format adjustment (such as paragraph format, title level, font style, etc.), insertion of multimedia content such as pictures, tables, and charts, and adjustment of document structure (such as adding chapters, adjusting paragraph order, etc.). For the mind cloud map, the editing operation includes adding new nodes and connections, editing the text content of the node, adjusting the position of the node, changing the color or shape of the node, and updating the layout of the entire cloud map. For external links, as shown in 8a to 8b, the link cards can be moved, deleted, aligned, and grouped in the canvas, but operations such as merging state diagrams, sharing, and downloading cannot be performed.

[0070] Step S104: storing the asset card and the corresponding design file entity in real time.

[0071] For example, create a table to store asset card information, including fields such as asset ID, name, type, description, creation time, and modification time. Create a separate table for each design file type (such as design drawings, super documents, mind cloud maps, etc.) to store the specific content of the file, metadata (such as file name, size, creator, creation time, etc.) and the relationship with the asset card. Establish an association field (such as a foreign key) between the asset card table and the design file entity table so that the corresponding design file entity can be quickly found through the asset card. For a large amount of unstructured data in the design file entity (such as design drawings, document content, etc.), organize the data by column. In order to ensure the real-time nature of the data, a real-time update mechanism can be used to ensure that when the asset card or design file entity changes, it can be updated immediately in the database.

[0072] The solution provided by the above embodiment of the present invention is to create an asset card of the project space through a canvas page, wherein the asset card includes a thumbnail, name, description and annotation information; load the design drawing, super document, mind cloud map and external link of the design file entity through the asset card; edit the corresponding design file entity through the asset card, wherein the operations of the asset card include moving, deleting, aligning, grouping and permission allocation operations; and store the asset card and the corresponding design file entity in real time. The present invention introduces more diverse asset carrying forms in the same canvas, allowing users to obtain relevant information about the project at the lowest cost during the design delivery process, so that team assets can be effectively collected and precipitated, and project members can freely browse all the materials in the project, reducing information asymmetry within the team.

[0073] Embodiment 2:

[0074] Fig.11 The functional structure diagram of the device provided in the embodiment of the present application is shown. Fig.11 As shown, the device comprises:

[0075] A creation module 1101 is used to create an asset card of a project space through a canvas page, wherein the asset card includes a thumbnail, a name, a description, and annotation information;

[0076] A loading module 1102, used to load the design drawings, super documents, mind cloud maps and external links of the design file entity through the asset card;

[0077] The editing module 1103 is used to perform editing operations on the corresponding design file entity through the asset card, wherein the operations of the asset card include moving, deleting, aligning, grouping and permission allocation operations;

[0078] The storage module 1104 is used to store the asset card and the corresponding design file entity in real time.

[0079] The solution provided by the above embodiment of the present invention is to create an asset card of the project space through a canvas page, wherein the asset card includes a thumbnail, name, description and annotation information; load the design drawing, super document, mind cloud map and external link of the design file entity through the asset card; edit the corresponding design file entity through the asset card, wherein the operations of the asset card include moving, deleting, aligning, grouping and permission allocation operations; and store the asset card and the corresponding design file entity in real time. The present invention introduces more diverse asset carrying forms in the same canvas, allowing users to obtain relevant information about the project at the lowest cost during the design delivery process, so that team assets can be effectively collected and precipitated, and project members can freely browse all the materials in the project, reducing information asymmetry within the team.

[0080] Embodiment three:

[0081] Fig.12 A schematic diagram of the structure of an embodiment of a computing device of the present application is shown. The specific embodiment of the present application does not limit the specific implementation of the computing device.

[0082] like Fig.12 As shown, the computing device may include: a processor (processor) 1202 , a communication interface (Communications Interface) 1204 , a memory (memory) 1206 , and a communication bus 1208 .

[0083] The processor 1202, the communication interface 1204, and the memory 1206 communicate with each other via the communication bus 1208. The communication interface 1204 is used to communicate with other devices such as a client or other server network elements. The processor 1202 is used to execute the program 1210, which can specifically execute the relevant steps in the above-mentioned embodiment of the asset collection method based on the project space for the computing device.

[0084] Specifically, the program 1210 may include program codes, which include computer operation instructions.

[0085] The processor 1202 may be a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application. The one or more processors included in the computing device may be processors of the same type, such as one or more CPUs; or may be processors of different types, such as one or more CPUs and one or more ASICs.

[0086] The memory 1206 is used to store the program 1210. The memory 1206 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0087] The program 1210 may be specifically configured to enable the processor 1202 to perform the following operations:

[0088] Create an asset card for the project space through a canvas page, wherein the asset card includes a thumbnail, a name, a description, and annotation information;

[0089] Loading design drawings, super documents, mind cloud maps and external links of design file entities through the asset cards;

[0090] Performing editing operations on the corresponding design file entity through the asset card, wherein the operations of the asset card include moving, deleting, aligning, grouping and authority allocation operations;

[0091] The asset card and the corresponding design file entity are stored in real time.

[0092] Optionally, the program 1210 enables the processor to perform the following operations:

[0093] The asset cards are displayed in the canvas page in a scaled-down form through thumbnails.

[0094] Optionally, the program 1210 enables the processor to perform the following operations:

[0095] The external link card supports opening the link in a new tab, renaming the link, and recycling it to the recycle bin after deletion;

[0096] The external link card is prohibited from merging status diagrams, sharing, and downloading operations.

[0097] Optionally, the program 1210 enables the processor to perform the following operations:

[0098] The link name of the external link card is displayed differently according to whether the address can obtain the title and description;

[0099] Among them, when the web page title and description are obtained, the web page title, logo, description and domain name are displayed; when the web page description cannot be obtained, the web page title, logo and domain name are displayed; when the web page title and description cannot be obtained, only the link is displayed.

[0100] Optionally, the program 1210 enables the processor to perform the following operations:

[0101] The mind cloud maps and external links created on the canvas page belong to the project. Their seats and roles are consistent with the project, and the operation permissions of the corresponding files are consistent with the operation permissions of the project.

[0102] Optionally, the program 1210 enables the processor to perform the following operations:

[0103] For design drawings, super documents and mind cloud maps, edit the corresponding design file entities;

[0104] For external links, move, delete, align, and group them.

[0105] Optionally, the functions of the super document include but are not limited to: team documents, knowledge base space, content writing and collaboration, basic functions, management background, enterprise information and management, organizational structure, role permissions, security management, information access, approval center, system settings, disk monitoring, open platform, login and organizational structure synchronization functions.

[0106] The solution provided by the above embodiment of the present invention is to create an asset card of the project space through a canvas page, wherein the asset card includes a thumbnail, name, description and annotation information; load the design drawing, super document, mind cloud map and external link of the design file entity through the asset card; edit the corresponding design file entity through the asset card, wherein the operations of the asset card include moving, deleting, aligning, grouping and permission allocation operations; and store the asset card and the corresponding design file entity in real time. The present invention introduces more diverse asset carrying forms in the same canvas, allowing users to obtain relevant information about the project at the lowest cost during the design delivery process, so that team assets can be effectively collected and precipitated, and project members can freely browse all the materials in the project, reducing information asymmetry within the team.

[0107] The algorithm or display provided herein is not inherently related to any particular computer, virtual system or other equipment. Various general purpose systems can also be used together with the teachings based on this. According to the above description, it is obvious to construct the structure required for this type of system. In addition, the embodiment of the present invention is not directed to any specific programming language yet. It should be understood that various programming languages ​​can be utilized to realize the content of the present invention described herein, and the description made to specific languages ​​above is for disclosing the best mode of the present invention.

[0108] In the description provided herein, a large number of specific details are described. However, it is understood that embodiments of the present invention can be practiced without these specific details. In some instances, well-known methods, structures and techniques are not shown in detail so as not to obscure the understanding of this description.

[0109] Similarly, it should be understood that in order to streamline the present invention and aid in understanding one or more of the various inventive aspects, in the above description of exemplary embodiments of the present invention, the various features of the embodiments of the present invention are sometimes grouped together into a single embodiment, figure, or description thereof. However, this disclosed method should not be interpreted as reflecting the following intention: that the claimed invention requires more features than the features explicitly recited in each claim. More specifically, as reflected in the claims below, inventive aspects lie in less than all the features of the individual embodiments disclosed above. Therefore, the claims that follow the specific embodiment are hereby expressly incorporated into the specific embodiment, with each claim itself serving as a separate embodiment of the present invention.

[0110] Those skilled in the art will appreciate that the modules in the devices in the embodiments may be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments may be combined into one module or unit or component, and in addition they may be divided into a plurality of submodules or subunits or subcomponents. Except that at least some of such features and / or processes or units are mutually exclusive, all features disclosed in this specification (including the accompanying claims, abstracts and drawings) and all processes or units of any method or device disclosed in this manner may be combined in any combination. Unless otherwise expressly stated, each feature disclosed in this specification (including the accompanying claims, abstracts and drawings) may be replaced by an alternative feature providing the same, equivalent or similar purpose.

[0111] In addition, those skilled in the art will appreciate that, although some embodiments herein include certain features included in other embodiments but not other features, the combination of features of different embodiments is meant to be within the scope of the present invention and form different embodiments. For example, in the claims below, any one of the claimed embodiments may be used in any combination.

[0112] The various component embodiments of the present invention can be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It should be understood by those skilled in the art that a microprocessor or digital signal processor (DSP) can be used in practice to implement some or all functions of some or all components according to embodiments of the present invention. The present invention can also be implemented as a device or apparatus program (e.g., computer program and computer program product) for executing part or all of the methods described herein. Such a program implementing the present invention can be stored on a computer-readable medium, or can have the form of one or more signals. Such a signal can be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.

[0113] It should be noted that the above embodiments illustrate the present invention rather than limit it, and that those skilled in the art may devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference symbol between brackets shall not be construed as a limitation on the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "one" or "an" preceding an element does not exclude the presence of a plurality of such elements. The present invention may be implemented by means of hardware comprising a number of different elements and by means of a suitably programmed computer. In a unit claim enumerating a number of devices, several of these devices may be embodied by the same hardware item. The use of the words first, second, and third, etc. does not indicate any order. These words may be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be understood as limitations on the order of execution.

Claims

1. A project space-based asset collection method, characterized in that: include: Create an asset card for the project space through a canvas page, wherein the asset card includes a thumbnail, a name, a description, and annotation information; Loading design drawings, super documents, mind cloud maps and external links of design file entities through the asset cards; Performing editing operations on the corresponding design file entity through the asset card, wherein the operations of the asset card include moving, deleting, aligning, grouping and authority allocation operations; The asset card and the corresponding design file entity are stored in real time.

2. The asset collection method based on project space according to claim 1 is characterized in that: The asset cards are displayed in the canvas page in a scaled-down form through thumbnails.

3. The asset collection method based on project space according to claim 1 or 2, characterized in that: The external link card supports opening the link in a new tab, renaming the link, and recycling it to the recycle bin after deletion; The external link card is prohibited from merging status diagrams, sharing, and downloading operations.

4. The asset collection method based on project space according to claim 3 is characterized in that: The link name of the external link card is displayed differently according to whether the address can obtain the title and description; Among them, when the web page title and description are obtained, the web page title, logo, description and domain name are displayed; when the web page description cannot be obtained, the web page title, logo and domain name are displayed; when the web page title and description cannot be obtained, only the link is displayed.

5. The asset collection method based on project space according to claim 1 is characterized in that: The method further comprises: The mind cloud maps and external links created on the canvas page belong to the project. Their seats and roles are consistent with the project, and the operation permissions of the corresponding files are consistent with the operation permissions of the project.

6. The asset collection method based on project space according to claim 1 is characterized in that: The editing operation of the corresponding design file entity through the asset card further includes: For design drawings, super documents and mind cloud maps, edit the corresponding design file entities; For external links, move, delete, align, and group them.

7. The asset collection method based on project space according to claim 1 is characterized in that: The functions of the super document include but are not limited to: team documents, knowledge base space, content writing and collaboration, basic functions, management background, enterprise information and management, organizational structure, role permissions, security management, information access, approval center, system settings, disk monitoring, open platform, login and organizational structure synchronization functions.

8. An asset collection device based on project space, characterized in that: include: A creation module, used to create an asset card of a project space through a canvas page, wherein the asset card includes a thumbnail, a name, a description, and annotation information; A loading module, used to load the design drawings, super documents, mind cloud maps and external links of the design file entity through the asset card; An editing module, used to perform editing operations on the corresponding design file entity through the asset card, wherein the operations of the asset card include moving, deleting, aligning, grouping and permission allocation operations; The storage module is used to store the asset card and the corresponding design file entity in real time.

9. A computing device comprising: A processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform operations corresponding to the project space-based asset aggregation method as described in any one of claims 1-7.

10. A computer program product, comprising at least one executable instruction, wherein the executable instruction enables a processor to execute operations corresponding to the project space-based asset aggregation method as described in any one of claims 1 to 7.