SCORM courseware using method for insurance company
By using SCORM courseware, the problem of internal resource integration and management within insurance companies was solved, enabling cross-platform resource sharing and validity period management, thereby improving training efficiency and security.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-10
- Publication Date
- 2026-03-24
AI Technical Summary
The lack of an LMS (Location Management System) within the insurance company resulted in the inability to effectively integrate internal learning resources such as course videos, PPTs, and PDFs for courseware sharing. Furthermore, the lack of expiration date control and a mechanism for cleaning up long-unused resources led to resource waste and security risks.
The SCORM courseware usage method is adopted, including generating SCORM courseware creation function interfaces, performing parameter verification and encapsulation, setting the validity period of sharing links, periodically deleting courseware, and designing an obsolescence handling process to ensure the standardization and security of resource management.
It enables cross-platform resource sharing and management, reduces resource waste, improves training efficiency, ensures resource flexibility and security, and avoids storage space waste through expiration date management and regular cleanup.
Smart Images
Figure CN121723969A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of [unclear - possibly related to a specific area or field], and more particularly to a method for using SCORM courseware for insurance companies. Background Technology
[0002] With the rapid development of information technology, enterprises and educational institutions are increasingly relying on multimedia courseware for knowledge transfer, especially in the insurance industry, where training and learning are important means of improving employee capabilities. Training instructors typically need to share courseware, which comes in various formats such as PPT, PDF, and video. In the traditional courseware sharing process, different software such as WPS and video players are needed to open the corresponding format files, requiring frequent switching between software to maintain continuous delivery. This is cumbersome and disrupts the continuity of the presentation. Furthermore, there is no dedicated solution designed for the training scenarios of insurance companies, making it impossible to effectively integrate the company's internal learning resources such as course videos, PPTs, and PDFs. To address this issue, the SCORM (Sharable Content Object Reference Model) standard, as an international learning content standard, has been widely applied in various online learning systems. SCORM's greatest advantage lies in its ability to ensure smooth operation of courseware content across various Learning Management Systems (LMS), guaranteeing the preservation of learning progress, modular content management, and a clear learning architecture. Therefore, SCORM courseware provides greater flexibility and compatibility for cross-platform learning, making the sharing and utilization of learning resources more convenient and efficient. However, insurance companies currently lack LMS deployment, resulting in the absence of courseware sharing expiration control, mechanisms for cleaning up inaccessible resources, and expiration notification functions, which can easily lead to resource waste and security risks. Therefore, a local SCORM courseware creation method adapted to their training needs is urgently needed to integrate internal learning resources and optimize courseware usage processes. Summary of the Invention
[0003] The purpose of this invention is to address the shortcomings of existing technologies by proposing a method for using SCORM courseware for insurance companies.
[0004] To achieve the above objectives, the present invention adopts the following technical solution: A method for using SCORM courseware for insurance companies includes the following steps: S1: Generate the SCORM courseware creation function interface and save it to the database; S11: Receive parameters and encapsulate them; Based on the data model ScormMakeBean, determine the parameters that the SCORM courseware creation function interface needs to receive; The parameters include file ID, file name, file type, file path, etc. The file ID is a unique identifier, and the file type includes PPT, PDF, video, etc. The required parameters are passed to the SCORM courseware creation function interface. The SCORM courseware creation function interface receives the parameters and maps them to the ScormMakeBean instance, performing centralized encapsulation of the parameters. Each parameter corresponds to a field in the ScormMakeBean instance. S12: Verify the parameters; This includes parameter integrity verification, format validity verification, and unique constraint verification; S13: Initialize parameters and assign values to file types; Initialize the parameters after verification, including uniformly converting file path separators and completing file type extensions; ScormMakeBean pre-sets a mapping rule table, which contains the input file type and a unified standard format identifier. The file type and the standard format identifier correspond one-to-one. The received file type is matched with the corresponding standard format identifier in the mapping rule table, and the file type is updated to the standard format identifier to complete the file type assignment. S14: Add a new record to the database as the creation record; The production record includes information such as the courseware ID, parameter details, verification results, production status, courseware creator ID, and access time; The ID of the created courseware is unique; The parameter details are the parameters initialized in step S113; The verification result is "passed"; The production status is "pending processing"; The courseware creator ID should be filled in according to the actual production needs; S2: Prepare courseware; Sort existing or newly uploaded learning / training resources by chapter and directory, and obtain the corresponding file paths; Call the SCORM courseware creation function interface generated in step S11 to create a new temporary folder, and copy the SCORM standard template files (such as index.html and data.js) into the temporary folder; Download the files to a temporary folder based on the obtained file paths, and store them in order of chapter or table of contents; write the corresponding information such as the chapter structure in the files into the SCORM standard template file, compress the temporary folder and upload it to the file server, and delete the local temporary folder; once the courseware is completed, add a new production record in the database through the SCORM courseware production function interface; modify the file path in the production record to the path corresponding to the file server, update the production status of this courseware to "production completed", and synchronize the access time to the production completion timestamp.
[0005] Furthermore, when users discover that there are missing or redundant files in the courseware they have created, they can perform operations such as adding missing files or deleting redundant files in the courseware management interface. The front end calls the SCORM courseware creation function interface to overwrite the corresponding courseware in the file server based on the created courseware ID, and updates the creation status of this courseware in the database to "overwritten".
[0006] S3: Set up a sharing link for courseware; The courseware sharing link is generated through the generateShareLink component, and the courseware sharing link is associated with the courseware ID. The validity period of the courseware sharing link is set through the calculateDefaultExpiry component, and the validity period is converted into the corresponding expiration time based on the update time in the creation record. The expiration time is then bound to the courseware sharing link through the bindExpiryToLink component. Preferably, if a longer validity period needs to be set according to actual needs, the handleLongTermSelection component receives the validity period selected by the user, converts the validity period into an expiration time, and updates the expiration time of the corresponding courseware sharing link through the updateLinkExpiry component.
[0007] S4: Regularly delete courseware; Pre-set the duration of the warning period and the expiration period; The scheduled task is set up through the scheduleCoursewareCleanupTask function and started periodically. The filterSoonToExpireCoursewares component uses a time difference algorithm to filter courseware that has not been accessed for a period of time and has a warning period remaining before its expiration. The cloud assistant sends a notification to the relevant users of the courseware (such as the uploader and frequent visitors) that the courseware is about to expire. Furthermore, the filterExpiredCoursewares component is used to filter out courseware that has not been accessed for a period of time greater than or equal to the expiration time, and the expired components are then deleted in batches using the filterExpiredCoursewares component.
[0008] Preferably, obsolete courseware is disposed of as follows: Generate the SCORM courseware obsolescence function interface and save it to the database; Define the parameters that the SCORM courseware obsolescence function interface should receive, including the courseware unique ID, operator ID, obsolescence reason, etc. The SELECT component filters out the courseware that needs to be invalidated, and the corresponding parameters of the courseware are passed to the SCORM courseware invalidation function interface. The SCORM courseware invalidation function interface receives and verifies the parameters, including existence verification, permission verification, and reason for invalidation. Specifically, the existence check is performed by matching the received courseware ID with the courseware ID in the database. If the courseware record corresponding to the courseware ID exists in the database and the original creation status is not "invalid", the check is successful; otherwise, the check fails. Permission verification: The received operator ID is checked against a pre-defined associated user permission table to determine if it has the necessary permissions. If it does, the verification passes; otherwise, the verification fails. The associated user permission table contains the permissions possessed by each user ID; After the inspection is completed, call the SCORM courseware obsolescence function interface to delete the courseware, update the creation record in the database and add an obsolescence record; Update the creation status in the update log to "invalid"; The invalidation record includes information such as courseware ID, operator ID, reason for invalidation, operation time, and verification result, and is then stored in the database.
[0009] Compared with the prior art, the beneficial effects of the present invention are as follows: This method simplifies the creation, management, and disposal of courseware by integrating courseware in different formats (such as PPT, PDF, and video) and achieving unified management through the SCORM standard, thereby improving the continuity of instruction and training efficiency. This method provides the function of generating courseware sharing links and setting validity periods, which can avoid security risks and resource waste caused by long-term unused courseware; a longer validity period can be set according to needs to ensure the flexibility and security of courseware sharing; and the life cycle of courseware resources can be effectively controlled through automatic updates and expiration management of link validity periods.
[0010] By regularly cleaning up expired courseware, storage space is not wasted, and relevant users are reminded through the early warning notification function to ensure timely cleaning of courseware and effective management of resources; the disposal of obsolete courseware ensures the timely removal of useless data. Attached Figure Description
[0011] Figure 1 This is a flowchart illustrating the steps of using SCORM courseware for insurance companies according to the present invention. Detailed Implementation
[0012] To provide a further understanding of the purpose, structure, features, and functions of the present invention, detailed descriptions are provided below with reference to specific embodiments.
[0013] like Figure 1 As shown, a method for using SCORM courseware for insurance companies includes the following steps: S1: Generate the SCORM courseware creation function interface and save it to the database; S11: Receive parameters and encapsulate them; Based on the data model ScormMakeBean, determine the parameters that the SCORM courseware creation function interface needs to receive; The parameters include file ID, file name, file type, file path, etc. The file ID is a unique identifier, and the file type includes PPT, PDF, video, etc. The required parameters are passed to the SCORM courseware creation function interface. The SCORM courseware creation function interface receives the parameters and maps them to the ScormMakeBean instance, performing centralized encapsulation of the parameters. Each parameter corresponds to a field in the ScormMakeBean instance. S12: Verify the parameters; This includes parameter integrity verification, format validity verification, and unique constraint verification; Specifically, parameter integrity verification: The built-in verification logic of ScormMakeBean checks whether there are empty values in required fields such as file ID, file name, file type, and full file path. If they exist, the parameter integrity verification fails and the reason for failure is recorded (such as "file ID cannot be empty", "file type is required"). If they do not exist, the parameter integrity verification succeeds and the format validity is checked. Format validity check: A pre-set set of file types is used. If the received file type does not match any of the file types in the set, the format validity check is deemed to have failed and the reason for failure is recorded (such as "invalid file type"). If the file type matches, the format validity check is deemed to have succeeded and a unique constraint check is performed. Unique constraint validation: ScormMakeBean's built-in validation logic calls the database query interface to check whether the received file ID already exists in the database. If it exists, the unique constraint validation fails and the reason for failure is recorded (e.g., "file ID already exists"). If it does not exist, the unique constraint validation succeeds. S13: Initialize parameters and assign values to file types; Initialize the parameters after verification, including uniformly converting file path separators and completing file type extensions; ScormMakeBean pre-sets a mapping rule table, which contains the input file type and a unified standard format identifier. The file type and the standard format identifier correspond one-to-one. The received file type is matched with the corresponding standard format identifier in the mapping rule table, and the file type is updated to the standard format identifier to complete the file type assignment. S14: Add a new record to the database as the creation record; The production record includes information such as the courseware ID, parameter details, verification results, production status, courseware creator ID, and access time; The ID of the created courseware is unique; The parameter details are the parameters initialized in step S113; The verification result is "passed"; The production status is "pending processing"; The courseware creator ID should be filled in according to the actual production needs; By using the SCORM format, this method can easily achieve cross-platform compatibility, facilitate resource sharing and reuse, and improve resource flexibility.
[0014] S2: Prepare courseware; Sort existing or newly uploaded learning / training resources by chapter and directory, and obtain the corresponding file paths; Call the SCORM courseware creation function interface generated in step S11 to create a new temporary folder, and copy the SCORM standard template files (such as index.html and data.js) into the temporary folder; Download the files to a temporary folder based on the obtained file paths, and store them in order of chapter or table of contents; write the corresponding information such as the chapter structure in the files into the SCORM standard template file, compress the temporary folder and upload it to the file server, and delete the local temporary folder; once the courseware is completed, add a new production record in the database through the SCORM courseware production function interface; modify the file path in the production record to the path corresponding to the file server, update the production status of this courseware to "production completed", and synchronize the access time to the production completion timestamp.
[0015] Furthermore, when users discover that there are missing or redundant files in the courseware they have created, they can perform operations such as adding missing files or deleting redundant files in the courseware management interface. The front end calls the SCORM courseware creation function interface to overwrite the corresponding courseware in the file server based on the created courseware ID, and updates the creation status of this courseware in the database to "overwritten".
[0016] This method unifies the formatting of various resources in the courseware and manages them systematically by chapter and directory, enabling more efficient organization and utilization of internal learning resources and reducing resource waste and duplication of effort. Through clear steps (such as parameter encapsulation, validation, and file type assignment), this method ensures the standardization and efficiency of the courseware production process. Furthermore, it supports updating and overwriting missing or redundant files during production, allowing for flexible adjustments to the courseware content to maintain its suitability for training needs.
[0017] S3: Set up a sharing link for courseware; The courseware sharing link is generated through the generateShareLink component, and the courseware sharing link is associated with the courseware ID. The validity period of the courseware sharing link is set through the calculateDefaultExpiry component, and the validity period is converted into the corresponding expiration time based on the update time in the creation record. The expiration time is then bound to the courseware sharing link through the bindExpiryToLink component. Specifically, the expiration time is the time after the update plus the validity period; Preferably, if a longer validity period needs to be set according to actual needs, the handleLongTermSelection component receives the validity period selected by the user, converts the validity period into an expiration time, and updates the expiration time of the corresponding courseware sharing link through the updateLinkExpiry component.
[0018] S4: Regularly delete courseware; Pre-set the duration of the warning period and the expiration period; The scheduled task is set up through the scheduleCoursewareCleanupTask function and started periodically. The filterSoonToExpireCoursewares component uses a time difference algorithm to filter courseware that has not been accessed for a period of time and has a warning period remaining before its expiration. The cloud assistant sends a notification to the relevant users of the courseware (such as the uploader and frequent visitors) that the courseware is about to expire. Furthermore, the filterExpiredCoursewares component is used to filter out courseware that has not been accessed for a period of time greater than or equal to the expiration time, and the expired components are then deleted in batches using the filterExpiredCoursewares component.
[0019] Preferably, obsolete courseware is disposed of as follows: Generate the SCORM courseware obsolescence function interface and save it to the database; Define the parameters that the SCORM courseware obsolescence function interface should receive, including the courseware unique ID, operator ID, obsolescence reason, etc. The SELECT component filters out the courseware that needs to be invalidated, and the corresponding parameters of the courseware are passed to the SCORM courseware invalidation function interface. The SCORM courseware invalidation function interface receives and verifies the parameters, including existence verification, permission verification, and reason for invalidation. Specifically, the existence check is performed by matching the received courseware ID with the courseware ID in the database. If the courseware record corresponding to the courseware ID exists in the database and the original creation status is not "invalid", the check is successful; otherwise, the check fails. Permission verification: The received operator ID is checked against a pre-defined associated user permission table to determine if it has the necessary permissions. If it does, the verification passes; otherwise, the verification fails. The associated user permission table contains the permissions possessed by each user ID; After the inspection is completed, call the SCORM courseware obsolescence function interface to delete the courseware, update the creation record in the database and add an obsolescence record; Update the creation status in the update log to "invalid"; The invalidation record includes information such as courseware ID, operator ID, reason for invalidation, operation time, and verification result, and is then stored in the database.
[0020] In the courseware obsolescence function, this invention designs an access control mechanism to ensure that only authorized users can perform the obsolescence operation, effectively preventing unauthorized users from accidentally operating or maliciously tampering with the courseware and enhancing security.
[0021] The present invention has been described in the above-described embodiments; however, these embodiments are merely examples for implementing the present invention. It must be noted that the disclosed embodiments do not limit the scope of the present invention. Conversely, any modifications and refinements made without departing from the spirit and scope of the present invention are within the scope of patent protection of the present invention.
Claims
1. A method for using SCORM courseware for insurance companies, characterized in that: Includes the following steps: S1: Generate the SCORM courseware creation function interface and save it to the database; S11: Receive parameters and encapsulate them; Based on the data model ScormMakeBean, determine the parameters that the SCORM courseware creation function interface needs to receive; The required parameters are passed to the SCORM courseware creation function interface. The SCORM courseware creation function interface receives the parameters and maps them to the ScormMakeBean instance, performing centralized encapsulation of the parameters. Each parameter corresponds to a field in the ScormMakeBean instance. S12: Verify the parameters; S13: Initialize parameters and assign values to file types; S14: Add a new record to the database as the creation record; S2: Prepare courseware; Sort existing or newly uploaded learning / training resource files by chapter and directory, and obtain the corresponding file paths; Create a temporary folder by calling the SCORM courseware creation function interface, and copy the SCORM standard template file into the temporary folder; Download the files to a temporary folder based on the obtained file paths, and store them in order of chapter or directory; write the corresponding information such as the chapter structure in the files into the SCORM standard template file, compress the temporary folder and upload it to the file server, and delete the local temporary folder; once the courseware is completed, add a new production record in the database through the SCORM courseware production function interface; and modify the file path in the production record to the path corresponding to the file server, update the production status and access time; S3: Set up a sharing link for courseware; The courseware sharing link is generated through the generateShareLink component, and the courseware sharing link is associated with the courseware ID. The validity period of the courseware sharing link is set through the calculateDefaultExpiry component, and the validity period is converted into the corresponding expiration time based on the update time in the creation record. The expiration time is then bound to the courseware sharing link through the bindExpiryToLink component. S4: Regularly delete courseware; Set up a scheduled task to delete courseware periodically and notify relevant personnel.
2. The method for using SCORM courseware for insurance companies as described in claim 1, characterized in that: The specific details of step S1 are as follows: S11: Receive parameters and encapsulate them; The parameters include file ID, file name, file type, and file path; The file ID is a unique identifier, and the file type includes PPT, PDF, and video. S12: Verify the parameters; This includes parameter integrity verification, format validity verification, and unique constraint verification; S13: Initialize parameters and assign values to file types; Initialize the parameters after verification; ScormMakeBean pre-sets a mapping rule table, which contains the input file type and a unified standard format identifier. The file type and the standard format identifier correspond one-to-one. The received file type is matched with the corresponding standard format identifier in the mapping rule table, and the file type is updated to the standard format identifier to complete the file type assignment. S14: Add a new record to the database as the creation record; The production record includes the courseware ID, parameter details, verification results, production status, courseware creator ID, and access time.
3. The method for using SCORM courseware for insurance companies as described in claim 1, characterized in that: In step S2, when a user discovers that there are missing or redundant files in the courseware they have created, the missing files are added and the redundant files are deleted in the courseware management interface. The front end calls the SCORM courseware creation function interface to overwrite the corresponding courseware in the file server based on the created courseware ID, and updates the creation status of this courseware in the database to "overwritten".
4. The method for using SCORM courseware for insurance companies as described in claim 1, characterized in that: In step S3, if a longer validity period needs to be set according to actual needs, the user-selected validity period is received through the handleLongTermSelection component, and the validity period is converted into an expiration time. The expiration time of the corresponding courseware sharing link is then updated through the updateLinkExpiry component.
5. The method for using SCORM courseware for insurance companies as described in claim 1, characterized in that: The specific details of step S4 are as follows: Pre-set the duration of the warning period and the expiration period; The scheduled task is set up through the scheduleCoursewareCleanupTask function and started periodically. The filterSoonToExpireCoursewares component uses a time difference algorithm to filter courseware that has not been accessed for a period of time and has a warning period remaining before its expiration. The cloud assistant sends a notification to the relevant users of the courseware (such as the uploader and frequent visitors) that the courseware is about to expire. The filterExpiredCoursewares component filters out courseware that has not been accessed for a period of time equal to or longer than its expiration time, and then uses the filterExpiredCoursewares component to delete expired courseware in batches.