Digital content creation file management system, method and equipment and storage medium

Abstract

The invention discloses a digital content creation file management system, method and device and a storage medium, and the system comprises a data layer which communicates with a database, a file system and an external system, and stores and reads file versions and task information; the business logic layer is used for carrying out file management on the digital content creation file; wherein the file management comprises version control, file uploading, file downloading and cross-platform adaptation; the interface layer is used for providing a cross-platform graphical user interface so as to obtain interactive operation of a user; wherein the interface layer is provided with a dynamic menu unit, an information display unit and a version list unit; the plug-in layer is used for providing an adaptive plug-in for the digital content creation file management platform; and the interface layer is used for providing a unified API interface. According to the digital content creation file management system, the multi-layer digital content creation file management system is constructed, and the functions of all layers are effectively integrated, so that many problems of an existing management mode are effectively solved, and the overall management effect of the digital content creation file is improved.

Description

Technical Field

[0001] This invention relates to the field of computer software technology, and in particular to a digital content creation file management system, method, device and storage medium. Background Technology

[0002] In current 3D animation and film production workflows, collaborative production scenarios generally involve the management and version control of a large number of asset files, shot files, and special effects caches. Because the production workflow relies on various Digital Content Creation (DCC) platforms such as Maya, Houdini, and Blender, and these different DCC software programs have significantly different operating logics, supported file formats, and workflow management mechanisms, lacking a unified standard, this directly leads to core problems such as chaotic file naming, inadequate version control, and low operational efficiency that are prevalent in the industry. Currently, small and medium-sized production teams are limited by factors such as cost and technical barriers, and mostly adopt manual naming and local script tools combined with cloud storage sharing to carry out file workflow management. This management model lacks systematic design and is difficult to adapt to the collaborative needs of multiple users, multiple tasks, and multiple DCC platforms, resulting in a series of workflow management pain points. At the file version management level, the existing model lacks a unified version control mechanism and naming rules. In addition, the file format differences between multiple DCC platforms are significant, which makes it easy for file versions to be overwritten, accidentally deleted or lost in a collaborative environment. At the same time, the lack of a complete version history management and rollback mechanism makes it impossible to track the entire life cycle of file versions, which further exacerbates the version chaos problem.

[0003] At the DCC platform adaptation level, the operation methods, file formats and script interfaces of various software differ greatly. Most existing tools are customized for a single platform, which not only has poor reusability, but also lacks the ability to automatically identify the current DCC environment and adapt to the corresponding functions, making it difficult to form a unified management interface and adaptation mechanism across platforms. In terms of workflow collaboration, core operations such as file upload, download, and version switching lack a unified entry point and workflow control. Users need to manually switch between multiple systems or tools, which is cumbersome and inefficient. At the same time, the lack of auxiliary functions such as resume download, automatic version recognition, and file integrity verification further reduces workflow efficiency.

[0004] At the information retrieval level, key information such as shots, scenes, assets, episodes, and project tasks lacks structured management. The existing model does not support efficient retrieval functions such as multi-condition filtering and fuzzy search, making it difficult for team members to quickly locate the required files and task status, resulting in extremely low transparency of project structure and task status.

[0005] In terms of system scalability and maintenance, existing management tools mostly adopt a closed architecture with high coupling between functional modules. This not only makes it difficult to quickly integrate new DCC platforms or functional modules, but also results in high maintenance and upgrade costs. At the same time, the lack of modular and plug-in design limits the reusability and flexibility of the system, making it unable to flexibly adapt to the new platform or functional requirements brought about by industry technology iterations.

[0006] In terms of user interaction experience, the operation interface is inconsistent across different DCC platforms, resulting in significant differences in experience. Furthermore, it lacks efficient interactive designs such as right-click menus and shortcut operations, and it does not have the intelligent adaptation capability to dynamically generate operation options based on the current context (such as selected assets, camera, and tasks), further reducing user operation efficiency. While mature project management systems such as Shotgun and FTrack exist in the industry, they generally suffer from high costs, reliance on network platforms, and complex integration processes. These systems struggle to meet the core needs of small and medium-sized production teams for localized deployment, high controllability, and lightweight deployment, failing to effectively address the aforementioned pain points in process management. Therefore, the 3D animation and film production industry urgently needs a localized management solution that is compatible with multiple DCC platforms, possesses unified version control and process management capabilities, supports efficient information retrieval, and is flexibly scalable and lightweight, to overcome the many difficulties of the existing management model. Summary of the Invention

[0007] This invention provides a digital content creation file management system, method, computer device, and storage medium, aiming to improve the management effect of digital content creation files.

[0008] In a first aspect, embodiments of the present invention provide a digital content creation file management system, comprising: The data layer is used to communicate with databases, file systems, and external systems, and to store and retrieve file versions and task information; The business logic layer is used for file management of digital content creation files; wherein, the file management includes: version control, file upload, file download and cross-platform adaptation; The interface layer provides a cross-platform graphical user interface to facilitate user interaction; the interface layer includes dynamic menu units, information display units, and version list units. The plugin layer provides compatible plugins for different digital content creation and file management platforms. The interface layer provides a unified API interface for the interface layer and the plugin layer to call.

[0009] Secondly, embodiments of the present invention provide a method for managing digital content creation files, including: In response to the user's software startup operation, the system identifies the current digital content creation file platform and loads the corresponding plugins and configuration files; In response to user operations on the digital content creation platform, the system manages the digital content creation files on the platform using the plugins and configuration files.

[0010] Thirdly, embodiments of the present invention provide a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the digital content creation file management method as described in the second aspect.

[0011] Fourthly, embodiments of the present invention provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the digital content creation file management method as described in the second aspect.

[0012] This invention provides a digital content creation file management system, method, computer device, and storage medium. The system includes: a data layer for communicating with databases, file systems, and external systems, and storing and retrieving file versions and task information; a business logic layer for managing digital content creation files, including version control, file uploading, file downloading, and cross-platform adaptation; a user interface layer for providing a cross-platform graphical user interface for user interaction, including dynamic menu units, information display units, and version list units; a plugin layer for providing adaptation plugins for different digital content creation file management platforms; and an interface layer for providing a unified API interface for communication between the interface layer and the plugin layer. This invention effectively integrates the functions of each layer by constructing a multi-layered digital content creation file management system. The data layer, as the foundation, ensures stable storage and efficient retrieval of file versions and task information, providing solid support for the data flow of the entire system, thereby effectively solving many difficulties in existing management models and improving the overall management effect of digital content creation files. Attached Figure Description

[0013] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 A schematic diagram of the principle architecture of a digital content creation file management system provided in an embodiment of the present invention; Figure 2 A flowchart illustrating a digital content creation file management method provided in an embodiment of the present invention; Figure 3 A schematic block diagram of a digital content creation file management system provided in an embodiment of the present invention; Figure 4 A first example diagram of a digital content creation file management method provided in an embodiment of the present invention; Figure 5 This is a second example diagram of a digital content creation file management method provided in an embodiment of the present invention. Detailed Implementation

[0015] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0016] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0017] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0018] It should also be further understood that the term "and / or" as used in this specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0019] Please see below. Figure 1 This invention provides a digital content creation file management system, comprising: The data layer is used to communicate with databases, file systems, and external systems, and to store and retrieve file versions and task information; The business logic layer is used for file management of digital content creation files; wherein, the file management includes: version control, file upload, file download and cross-platform adaptation; The interface layer provides a cross-platform graphical user interface to facilitate user interaction; the interface layer includes dynamic menu units, information display units, and version list units. The plugin layer provides compatible plugins for different digital content creation and file management platforms. The interface layer provides a unified API interface for the interface layer and the plugin layer to call.

[0020] The digital content creation file management system described in this embodiment specifically includes a data layer, a business logic layer, a user interface layer, a plugin layer, and an interface layer. The data layer not only enables stable communication with databases, file systems, and external systems, but also stores and retrieves file versions and task information. This ensures the accuracy and efficiency of the system when processing large amounts of data, providing reliable data support for subsequent business operations.

[0021] The business logic layer undertakes the core tasks of file management, enabling core functions such as version control, file upload and download, and cross-platform adaptation. The version control function of the business logic layer ensures that each version of a file is clearly recorded and managed, avoiding version confusion and loss issues. During file upload and download, the business logic layer optimizes the process, improves operational efficiency, and ensures file integrity and security. The cross-platform adaptation function further solves compatibility issues between different digital content creation platforms, enabling the system to operate stably in various environments.

[0022] The UI layer provides users with an interactive interface, enabling a cross-platform GUI. The dynamic menu unit within the interface can dynamically generate operation options based on user actions and the current context; for example, a user can directly right-click to display a dynamic menu, effectively improving the convenience and flexibility of user operations. The information display unit clearly shows relevant file information, allowing users to quickly understand the file's status and content. The version list unit facilitates users in viewing historical versions of files, performing version comparisons, and rolling back.

[0023] The plugin layer provides strong support for the system's scalability, enabling it to provide compatible plugins for different digital content creation and file management platforms. This allows the system to quickly integrate new functions and platforms to meet ever-changing business needs.

[0024] The unified API provided by the interface layer enables efficient calls and communication between the interface layer and the plugin layer, which not only improves the development efficiency of the system, but also enhances the maintainability and scalability of the system.

[0025] In summary, the digital content creation file management system provided in this embodiment effectively solves the problems of chaotic file naming, lack of version control, and low operational efficiency in the existing management model through collaborative work at all levels. It improves the management effect of digital content creation files and provides strong support for collaborative production in industries such as 3D animation and film and television production.

[0026] In practical applications, the digital content creation file management system is developed based on Python and PySide2. Specifically, the main interface can be built using PySide2, supporting controls such as windows, buttons, tables, and tree structures. A PostgreSQL database is used for persistent data management, ActiveMQ is used for inter-module communication, and a signal and slot mechanism is used to achieve loosely coupled communication between modules. A plug-in system is used to adapt to the DCC platform, with one plug-in module corresponding to each DCC platform.

[0027] Of course, in other embodiments, other methods can also be considered to build the digital content creation file management system. For example, at the development language level, Python can be replaced with C++ / C# or JavaScript / TypeScript+Electron. Specifically, C++ / C# can be combined with Qt (C++) or WPF (C#) to write the core logic and interface, which can improve running efficiency and have better compatibility with native DCC plugins, but the development efficiency is low and the cross-platform flexibility is insufficient; JavaScript / TypeScript+Electron relies on the front-end technology stack to build cross-platform desktop applications, with a more modern interface and a rich front-end ecosystem, but it is difficult to deeply integrate with DCC software and has a high performance overhead. In terms of interface framework, PySide2 can be replaced with PySide6 / PyQt5, which have similar functions but different version licenses, or the lightweight Tkinter (adapted to simple interfaces) that comes with Python or Kivy, which is suitable for cross-platform touch interaction, can be selected according to needs. File version control mechanisms can be integrated with mature tools like Git / SVN, leveraging their robust distributed collaboration capabilities. However, these tools have poor support for binary files and are unsuitable for frequent commits of large files. Alternatively, custom lightweight version control can be implemented using file snapshots, symbolic links, and timestamps, adapting to scenarios with high performance requirements and simple functionalities. Communication mechanisms can be replaced with RPC frameworks like gRPC / Thrift, improving modularity, communication efficiency, and a clear structure, but with higher development and debugging complexity. Message queues like RabbitMQ and Kafka can also be used, adapting to distributed deployments or large team collaboration scenarios, offering strong scalability but with complex deployment and high resource consumption. A plugin architecture can be replaced with a method based on Python's importlib to dynamically load modules, enabling the dynamic import of functional modules.

[0028] like Figure 2 As shown, this embodiment of the invention provides a digital content creation file management method, specifically including steps S101~S102.

[0029] Step S101: In response to the user's software startup operation, identify the current digital content creation file platform and load the corresponding plugins and configuration files; Step S102: In response to the user's operation on the digital content creation file platform, manage the digital content creation files on the digital content creation file platform in conjunction with the plugin and configuration file.

[0030] In this embodiment, when a user launches the software, the system automatically identifies the currently used digital content creation platform and loads the corresponding plugins and configuration files, ensuring seamless integration with the specific platform. Then, based on the user's specific operations on the digital content creation platform, and combined with the loaded plugins and configuration files, the system comprehensively manages the digital content creation files. This management method not only improves the efficiency of digital content creation file management but also enhances the system's flexibility and scalability. By adapting to different digital content creation platforms, the system can meet diverse business needs, providing strong support for team collaboration in industries such as 3D animation and film production. Simultaneously, the system maintains stability and efficiency when processing large numbers of files and complex operations, effectively solving many problems existing in current management models.

[0031] In one embodiment, the step of responding to the user's software startup operation, identifying the current digital content creation file platform, and loading the corresponding plugins and configuration files includes: Read platform-related information during the software startup process; The current digital content creation file platform is identified based on the platform-related information, and the corresponding plugins and configuration files are loaded based on the platform-related information.

[0032] In this embodiment, the identification of the current digital content creation platform is based on platform-related information read during software startup. This information may include the platform's name, version number, and specific identifiers. Through precise analysis of this information, the system can accurately determine the currently used digital content creation platform. Once the specific platform is identified, the corresponding plugins and configuration files can be loaded based on the platform-related information, thereby displaying the main interface, connecting to the database, and loading project information. Different digital content creation platforms have different characteristics and functional requirements, therefore the corresponding plugins and configuration files also differ. For example, some platforms may require specific image processing plugins to support their unique image editing functions, while other platforms may require dedicated audio processing plugins to meet the needs of audio creation.

[0033] Furthermore, when loading plugins, corresponding plugin modules can be integrated into the system based on the platform's characteristics and requirements. These plugins provide additional functionality and support, enabling the system to better adapt to different platform operating environments. Meanwhile, the configuration file contains various parameters and settings required for the system to run on that platform, such as file storage paths and API call methods. By loading appropriate configuration files, the system can be optimized according to the platform's characteristics, ensuring stable and efficient operation on different platforms.

[0034] In practical applications, other methods can also be used to implement DCC platform identification and adaptation mechanisms. For example, DCC platforms can be identified through environment variables. This approach does not rely on runtime detection but directly identifies the currently used DCC platform using startup scripts or plugin configuration files, offering the advantage of flexible configuration. However, its automation level is low, requiring manual intervention. Another approach is to use Python's `sys.modules` to check loaded modules. By determining whether modules related to the DCC platform, such as `maya` and `hou`, exist in the current Python environment, the DCC platform can be identified. This approach does not require additional external dependencies, but it has limitations and may not achieve accurate identification for some DCC platforms.

[0035] In one embodiment, the step of managing digital content creation files on the digital content creation platform in response to user operations on the platform, in conjunction with the plugins and configuration files, includes: In response to a user's file upload operation on the digital content creation platform, the selected digital content creation file or the digital content creation file for the current scenario is obtained; The file type of the digital content creation file is identified based on the configuration file; Add notes to the digital content creation file based on the file type, generate a version number, and then perform the file upload operation.

[0036] In this embodiment, when a user needs to upload a file, the system first retrieves the digital content creation file selected by the user or the digital content creation file in the current scenario. Then, it identifies the type of these files based on a configuration file; different file types may correspond to different processing methods and management requirements. For example, for image files, information such as resolution and color mode may need to be considered; for video files, factors such as format and frame rate need to be taken into account.

[0037] After identifying the file type, add notes to the digital content creation files based on that type. These notes can include key descriptions of the file, its creation background, and intended use, helping users better understand and manage the files. Simultaneously, a unique version number is generated for each file. The generation rules for this version number can be set according to actual needs, such as chronological order or the number of version iterations. Through the version number, users can clearly understand the file's historical versions and update status, facilitating version comparison and rollback operations.

[0038] After adding remarks and generating a version number, the file upload operation is performed, and metadata is recorded. During the upload process, the upload flow can be optimized according to relevant rules from the business logic layer to ensure that the file can be transferred to the specified storage location quickly and securely. Simultaneously, integrity checks can be performed on the uploaded file to prevent corruption or loss during transmission.

[0039] In practical applications, file upload failures may occur. When an upload fails, an error message can be displayed, informing the user of the reason for the failure, such as network connection problems or unsupported file format. Furthermore, a retry mechanism can be provided, allowing users to easily re-upload the file. Additionally, upload failure logs can be recorded for subsequent troubleshooting and analysis, continuously optimizing the file upload function.

[0040] In one embodiment, the step of managing digital content creation files on the digital content creation platform in response to user operations on the platform, in conjunction with the plugin and configuration file, further includes: In response to a user's search operation on the digital content creation file platform, the corresponding results are returned to the user based on the search operation; In response to a user's download request for the search results, the search results are filtered based on the current digital content creation file platform to output the available versions of the current digital content creation file platform.

[0041] In this embodiment, when a user needs to perform a search, the database is searched according to the user's search criteria, and the matching results are returned to the user. These results specifically include the file itself and its name, creation time, version number, remarks, etc., making it convenient for the user to quickly locate the digital content creation file they need.

[0042] When users download search results, the results can be filtered based on the characteristics and requirements of the current digital content creation platform. Different digital content creation platforms may have specific requirements for file formats, versions, etc. Filtering ensures that the output is a file version compatible with the current platform. For example, some platforms may only support specific file formats; version filtering can select file versions that meet those format requirements for users to download.

[0043] During the filtering process, platform-related information stored in configuration files and plugins can be used for judgment. If a file version in the search results does not meet the requirements of the current platform, it is excluded, and only usable versions are retained. This prevents users from downloading files that cannot be used on the current platform, improving the accuracy and efficiency of the download operation.

[0044] To enhance user experience, the filtered results can be clearly displayed on the download interface, including detailed file information and available versions. Users can then select the appropriate version to download based on their needs. Furthermore, during the download process, the rules from the business logic layer can be followed to optimize the download flow and ensure that files are securely and stably transferred to the user's device. Real-time feedback on the download progress can also be provided, allowing users to stay informed about the download status.

[0045] In a specific embodiment, the step of responding to a user's retrieval operation on the digital content creation file platform and returning corresponding results to the user based on the retrieval operation includes: Determine whether the search difficulty of the search operation reaches a preset difficulty threshold; If it is determined that the retrieval difficulty of the retrieval operation does not reach the preset difficulty threshold, then a basic structured query is performed based on the SQLite database, and the corresponding retrieval results are output. If the retrieval difficulty of the retrieval operation is determined to reach a preset difficulty threshold, then the Elasticsearch search engine is used to perform high-performance full-text retrieval and fuzzy matching, and the corresponding retrieval results are output.

[0046] In this embodiment, when performing a search operation on the digital content creation file platform, the search difficulty can be determined first. The search difficulty can be specifically measured based on factors such as the complexity of the search criteria and the amount of data involved. A preset difficulty threshold is a pre-defined standard used to distinguish search operations of different difficulty levels.

[0047] If the search difficulty does not reach the preset difficulty threshold, it indicates that the search is relatively simple, and a basic structured query can be performed based on the SQLite database. SQLite is a lightweight database with advantages such as ease of operation and low resource consumption, making it suitable for handling simple structured data queries. The system will perform an exact match query in the SQLite database based on the user's input search criteria and output the results to the user. This query method is relatively fast and can meet most simple search needs.

[0048] If the search difficulty reaches a preset threshold, it indicates a complex search requiring more powerful capabilities. In this case, the Elasticsearch search engine can be used for high-performance full-text search and fuzzy matching. Elasticsearch is a distributed search and analytics engine with powerful full-text search and fuzzy matching capabilities, capable of quickly handling complex queries on large amounts of data. It can perform full-text searches on file content, notes, etc., and even with imprecise search criteria, it can find relevant results through fuzzy matching. The system sends the user's search criteria to the Elasticsearch search engine, which performs the search and matching, and outputs the final search results to the user.

[0049] In practical applications, this strategy of selecting different search methods based on search difficulty can fully leverage the advantages of different search tools, improving search efficiency and accuracy. For simple search operations, using an SQLite database can quickly obtain results, reducing system resource consumption; for complex search operations, the Elasticsearch search engine can meet users' needs for full-text search and fuzzy matching, providing more comprehensive and accurate search results. Furthermore, the system can adjust the preset difficulty threshold according to actual usage to better adapt to different business scenarios and user needs.

[0050] In one embodiment, the step of managing digital content creation files on the digital content creation platform in response to user operations on the platform, in conjunction with the plugin and configuration file, further includes: In response to a user's historical viewing operation on the digital content creation file platform, the historical version of the current digital content creation file is returned based on the configuration file; In response to the user's comparison operation, the current version of the current digital content creation file is compared with historical versions and displayed.

[0051] In this embodiment, when a user needs to perform version control operations, the first step is to view the history. Based on the configuration file, the system searches the database for all historical version information of the current digital content creation file and returns it to the user. This historical version information may include version number, creation time, and remarks, allowing the user to understand the file's development history and modifications. For example, in a graphic design project, designers can review design ideas and modification directions at different stages by viewing historical versions. In practical applications, users can roll back to any historical version with a single click to meet different operational needs. For instance, when a user is interested in a particular historical version or discovers a problem with the current version and needs to restore it to a previous state, they can quickly locate and restore that historical version, ensuring the continuity and stability of their work.

[0052] When users perform a comparison, the system provides a detailed comparison between the current version and historical versions of the digital content creation file, including file size, modification time, and author information. For example, for text files, it can compare line by line, marking added, deleted, and modified content; for image files, it can compare differences in color, resolution, layers, etc.; and for video files, it can compare changes in elements such as visuals, audio, and effects. The comparison results are displayed to the user in an intuitive way, such as using different colors to mark the differences, or generating a comparison report so that the user can clearly see the specific changes between the two versions.

[0053] In collaborative team projects, different members may modify the same file. By reviewing version history and comparing differences, team members can understand each other's changes, avoiding duplication of work and conflicts. Furthermore, if project issues arise, version rollback can be used to restore to a previous stable version, minimizing losses. Moreover, version control helps users review and summarize projects, learning from the modification process to improve efficiency and quality.

[0054] To further optimize version control, the system offers version annotation functionality, allowing users to add detailed descriptions for each version, explaining the reasons and purpose of the modifications. Version permissions can also be set, with different user roles having different access rights to different versions of files, ensuring file security and standardized management. Additionally, the system can periodically clean up historical versions, deleting unnecessary older versions to save storage space.

[0055] In one embodiment, the step of managing digital content creation files on the digital content creation platform in response to user operations on the platform, in conjunction with the plugin and configuration file, further includes: The plugin and configuration file are combined to generate a dynamic function menu, enabling users to perform corresponding operations on the digital content creation platform based on the dynamic function menu.

[0056] To improve interaction efficiency, this embodiment generates a dynamic function menu by combining plugins, configuration files, and context (such as current assets, shots, and tasks). Users can access this menu through right-clicking or other operations. The dynamic function menu can be dynamically adjusted based on factors such as the type and status of the digital content creation file being operated on, as well as the user's operating habits. For example, when a user selects a video file, the menu may display related function options such as video editing, format conversion, and adding subtitles; while when an image file is selected, the menu may display functions such as image editing, color adjustment, and resizing.

[0057] This dynamically adjustable menu allows users to more easily access the desired operation options, such as file upload, download, and open paths, avoiding the inconvenience caused by too many options in traditional fixed menus. Furthermore, the combined use of plugins and configuration files makes menu generation more flexible and personalized. Plugins can add new operation options to the menu based on different business needs and functional expansions; configuration files can customize the menu's display rules, sorting methods, and other aspects.

[0058] Furthermore, the dynamic function menu supports shortcuts and custom settings. Users can set frequently used operations as shortcuts for quick access when needed. Moreover, users can personalize the menu according to their own habits, such as adjusting the layout, adding or deleting certain function options. In this way, each user can have a customized function menu that suits their operating habits, further improving the convenience and efficiency of operation.

[0059] In practical applications, other solutions can be used to replace the dynamic right-click menu design. For example, one approach is to use a static menu combined with access control. This solution first provides a fixed set of menu items, and then dynamically enables or disables these items based on the user's permission level or the context of the current operation. Its advantage lies in its simple and clear logical architecture, making subsequent maintenance and iteration easier; however, its shortcomings are also obvious: the interaction lacks flexibility, cannot accurately match diverse operating scenarios, and results in a poor user experience. Another approach is to extend the menu system built into DCC software. For different DCC platforms such as Maya and Houdini, the required menu items are added to their native menus via script injection. The core advantage of this approach is that it maintains consistency with the native interface style of DCC software, reducing the learning and adaptation costs for users; however, due to differences in the menu system architecture of different DCC platforms, this approach has poor compatibility, and the menu extension functions of various DCC platforms are difficult to manage uniformly, increasing the system's maintenance complexity.

[0060] In summary, compared with the prior art, this embodiment has the following advantages: (1) Unified version control mechanism: realizes functions such as version naming rules, version history, version comparison and rollback, and enhances the security and traceability of file management; (2) Cross-platform automatic identification and adaptation mechanism: The system can automatically identify the currently running DCC software and load the corresponding plugins and user interface (UI) to achieve a unified operating experience; (3) Unified interface and modular design: By using a unified application programming interface (API) and modular architecture, low coupling between modules is achieved, which facilitates system expansion and reuse; (4) Dynamic right-click menu and context-aware interaction: The right-click menu is dynamically generated based on the context of the user's current operation to improve interaction efficiency; (5) Efficient information retrieval and query mechanism: Supports multi-dimensional retrieval, structured display, task status visualization and other functions; (6) Automatic file filtering mechanism: Automatically filters available file types and versions based on the current DCC platform to avoid accidental operation; (7) Plug-in and decoupled architecture: The system adopts an event-driven and interface communication mechanism to achieve high scalability, high reusability and low coupling.

[0061] In practical applications, such as Figure 4The diagram shown illustrates the startup interface of the digital content creation file management system provided in this embodiment. This interface displays a list of selectable projects to the user after system startup, including project names, project cover images, and other information. Users can select a target project to enter the corresponding project environment. The interface includes a search bar, a project icon area, and a system version information display area at the bottom of the screen. Figure 5 The diagram shown illustrates the task file management interface provided in this embodiment. The left side of the interface displays the project's shot hierarchy, including sequences, shots, and various task nodes under each shot. The right side displays a list of file versions corresponding to the currently selected task, including version thumbnails, version names, submitting users, creation times, and descriptive notes. This interface supports browsing, searching, version viewing, and version management of task files. The bottom area displays the currently running system version number.

[0062] Figure 3 A schematic block diagram of a digital content creation file management system 300 provided in an embodiment of the present invention. The system 300 includes: The platform identification unit 301 is used to identify the current digital content creation file platform in response to the user's software startup operation, and load the corresponding plugins and configuration files; The file management unit 302 is used to manage the digital content creation files on the digital content creation file platform in response to the user's operation on the digital content creation file platform, in conjunction with the plugins and configuration files.

[0063] In one embodiment, the platform identification unit 301 includes: The information reading unit is used to read platform-related information during the software startup process; The identification and loading unit is used to identify the current digital content creation file platform based on the platform-related information, and load the corresponding plugins and configuration files based on the platform-related information.

[0064] In one embodiment, the file management unit 302 includes: The file acquisition unit is used to acquire the selected digital content creation file or the digital content creation file of the current scene in response to the user's file upload operation on the digital content creation file platform. A type identification unit is used to identify the file type of the digital content creation file based on the configuration file. The file upload unit is used to add notes to the digital content creation file based on the file type, generate a version number, and then perform the file upload operation.

[0065] In one embodiment, the file management unit 302 further includes: The retrieval response unit is used to respond to the user's retrieval operation on the digital content creation file platform and return the corresponding results to the user according to the retrieval operation; The result filtering unit is used to filter the search results based on the current digital content creation file platform in response to the user's download operation of the search results, so as to output the available version of the current digital content creation file platform.

[0066] In one embodiment, the retrieval response unit includes: The difficulty judgment unit is used to determine whether the search difficulty of the search operation reaches a preset difficulty threshold. The first determination unit is used to perform a basic structured query based on the SQLite database and output the corresponding search results if it determines that the search difficulty of the search operation does not reach a preset difficulty threshold. The second determination unit is used to perform high-performance full-text search and fuzzy matching using the Elasticsearch search engine if the search difficulty of the search operation reaches a preset difficulty threshold, and output the corresponding search results.

[0067] In one embodiment, the file management unit 302 further includes: The version viewing unit is used to respond to the user's historical viewing operation on the digital content creation file platform and return the historical version of the current digital content creation file based on the configuration file; The difference comparison unit is used to respond to the user's difference comparison operation, compare the current version of the current digital content creation file with the historical versions, and display the differences.

[0068] In one embodiment, the file management unit 302 further includes: The menu generation unit is used to combine the plugin and configuration file to generate a dynamic function menu, so that the user can perform corresponding operations on the digital content creation file platform based on the dynamic function menu.

[0069] Since the embodiments of the system part correspond to the embodiments of the method part, please refer to the description of the embodiments of the method part for the embodiments of the system part, and they will not be repeated here.

[0070] This invention also provides a computer-readable storage medium storing a computer program thereon, which, when executed, can perform the steps provided in the above embodiments. The storage medium may include various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0071] This invention also provides a computer device, which may include a memory and a processor. The memory stores a computer program, and when the processor calls the computer program in the memory, it can implement the steps provided in the above embodiments. Of course, the computer device may also include various network interfaces, power supplies, and other components.

[0072] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the systems disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple; relevant parts can be referred to in the method section. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from the principles of this application, and these improvements and modifications also fall within the protection scope of the claims of this application.

[0073] It should also be noted that, in this specification, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

Claims

1. A digital content creation file management system, characterized in that, include: The data layer is used to communicate with databases, file systems, and external systems, and to store and retrieve file versions and task information; The business logic layer is used for file management of digital content creation files; wherein, the file management includes: version control, file upload, file download and cross-platform adaptation; The interface layer provides a cross-platform graphical user interface to facilitate user interaction; the interface layer includes dynamic menu units, information display units, and version list units. The plugin layer provides compatible plugins for different digital content creation and file management platforms. The interface layer provides a unified API interface for the interface layer and the plugin layer to call.

2. A method for managing digital content creation files, applied to the digital content creation file management system as described in claim 1, characterized in that, The method includes: In response to the user's software startup operation, the system identifies the current digital content creation file platform and loads the corresponding plugins and configuration files; In response to user operations on the digital content creation platform, the system manages the digital content creation files on the platform using the plugins and configuration files.

3. The digital content creation file management method according to claim 2, characterized in that, The process of responding to the user's software startup operation, identifying the current digital content creation file platform, and loading the corresponding plugins and configuration files includes: Read platform-related information during the software startup process; The current digital content creation file platform is identified based on the platform-related information, and the corresponding plugins and configuration files are loaded based on the platform-related information.

4. The digital content creation file management method according to claim 2, characterized in that, The management of digital content creation files on the digital content creation platform in response to user operations includes: (1) Using the plugins and configuration files, the management of digital content creation files on the platform. In response to a user's file upload operation on the digital content creation platform, the selected digital content creation file or the digital content creation file for the current scenario is obtained; The file type of the digital content creation file is identified based on the configuration file; Add notes to the digital content creation file based on the file type, generate a version number, and then perform the file upload operation.

5. The digital content creation file management method according to claim 2, characterized in that, The method of responding to user operations on the digital content creation platform and managing digital content creation files on the platform in conjunction with the plugins and configuration files also includes: In response to a user's search operation on the digital content creation file platform, the corresponding results are returned to the user based on the search operation; In response to a user's download request for the search results, the search results are filtered based on the current digital content creation file platform to output the available versions of the current digital content creation file platform.

6. The digital content creation file management method according to claim 5, characterized in that, The step of responding to a user's search operation on the digital content creation file platform and returning corresponding results to the user based on the search operation includes: Determine whether the search difficulty of the search operation reaches a preset difficulty threshold; If it is determined that the retrieval difficulty of the retrieval operation does not reach the preset difficulty threshold, then a basic structured query is performed based on the SQLite database, and the corresponding retrieval results are output. If the retrieval difficulty of the retrieval operation is determined to reach a preset difficulty threshold, then the Elasticsearch search engine is used to perform high-performance full-text retrieval and fuzzy matching, and the corresponding retrieval results are output.

7. The digital content creation file management method according to claim 2, characterized in that, The method of responding to user operations on the digital content creation platform and managing digital content creation files on the platform in conjunction with the plugins and configuration files also includes: In response to a user's historical viewing operation on the digital content creation file platform, the historical version of the current digital content creation file is returned based on the configuration file; In response to the user's comparison operation, the current version of the current digital content creation file is compared with historical versions and displayed.

8. The digital content creation file management method according to claim 2, characterized in that, The method of responding to user operations on the digital content creation platform and managing digital content creation files on the platform in conjunction with the plugins and configuration files also includes: The plugin and configuration file are combined to generate a dynamic function menu, enabling users to perform corresponding operations on the digital content creation platform based on the dynamic function menu.

9. A computer device, characterized in that, The method includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the digital content creation file management method as described in any one of claims 2 to 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the digital content creation file management method as described in any one of claims 2 to 8.

Images