Script Management Server Version Control via Meta Database
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing script management technologies lack the ability to manage original and user-specific script codes separately by version, leading to difficulties in using script files across different software versions, version control, and the loss of user-supplied scripts during software re-installation or upgrades.
Innovation Solution
A method for managing scripts that utilizes a script management server connected to user terminals, employing a meta database and multiple script databases classified by version to track and update script codes, provide bookmark functions, and enable backup and version control, allowing for the storage of identifiers and script lists, and the generation of script lists and codes in a tree structure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If script files are stored separately for different software versions, then users can use scripts in different version environments, but users must manually copy and paste script texts which is inconvenient and error-prone
Solution Approach 1:
The patent creates virtual copies of script files for different versions through a database system. Instead of manually copying script texts, the system stores script versions in a database and provides automated retrieval and application of the appropriate version, eliminating manual copying while maintaining version-specific compatibility
Solution Approach 2:
The patent introduces a database as an intermediary between users and script files. This intermediary manages version information and script content, automatically determining which script version to apply based on the software version, thereby simplifying the user interface and operation
2Ease of operation
If users edit script files and store them as new files, then users can modify scripts, but version control becomes difficult and original scripts may be lost
Solution Approach 1:
The patent implements a feedback mechanism where the system automatically tracks script modifications, determines the appropriate version, and provides feedback to users about version changes. This ensures that edits are properly recorded and associated with specific versions, maintaining version control integrity while allowing flexible editing
Solution Approach 2:
The patent performs preliminary actions by automatically determining script versions before users edit or modify scripts. The system pre-establishes versioning rules and automatically manages the versioning process, preventing version control issues before they arise
3Ease of operation
If users search for script files using list trees or search functions, then users can locate needed scripts, but the process is time-consuming and inconvenient
Solution Approach 1:
The patent creates virtual copies of script files in a database indexed by version and content. This allows the system to quickly locate and retrieve the appropriate script version without requiring users to manually search through file systems or list trees, significantly reducing search time
Solution Approach 2:
The patent replaces manual mechanical search processes (browsing list trees, searching files) with an automated database query system. The database efficiently indexes and retrieves script information based on version and content criteria, eliminating time-consuming manual search operations
4Reliability
If user-supplied scripts are removed during software re-installation or upgrade, then software can be properly reinstalled, but user scripts are lost and cannot be used
Solution Approach 1:
The patent creates a database copy of user scripts that is separate from the software installation. This database backup preserves user scripts even when software is reinstalled or upgraded, allowing users to retrieve and reapply their scripts without data loss
Solution Approach 2:
The patent implements beforehand cushioning by automatically backing up user scripts to a database before software installation or upgrade operations. This protective measure ensures that user scripts are preserved and can be restored if needed, preventing data loss during software maintenance operations
Data Source
AI summary
The present invention relates to a script management technology. Disclosed are approaches for managing scripts carried out in a script management server, which is connected to a user terminal and which manages script codes. Approaches comprise preparing a plurality of databases including a meta database and a plurality of script databases without necessarily separating physically the two types of databases; designating an active script database by providing the plurality of the original script lists to the user terminal; and storing identifiers of the user terminal and the designated active script database in the meta database, where the plurality of script databases are classified according to script version and each of them manages the original script code and user-specific script code, and the meta database manages a plurality of the original script lists related to the plurality of script databases and a list of user-specific scripts.