A general college information collection platform of multi-level report model
The general-purpose university information collection platform with a multi-level reporting model solves the problems of high communication costs, poor data security and flexibility in university information collection, and achieves rapid response and secure and reliable data collection, supporting data sharing and expansion among multiple business systems.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- PEKING UNIV
- Filing Date
- 2022-06-21
- Publication Date
- 2026-07-31
AI Technical Summary
Existing technologies for information collection in universities suffer from problems such as high communication costs, large workload for data processing, low data reliability, information security issues, and poor flexibility and adaptability, making it difficult to quickly respond to ever-changing information collection needs.
The general-purpose information collection platform for universities adopts a multi-level report model, including an identity authentication system, an information collection platform, data entry services, and other services. Through modules such as report model customization, access control, and data distribution rules, it achieves flexible configuration and secure and reliable data collection.
It enables users to adapt to changes in information collection needs without secondary development, ensures data security and reliability, supports rapid response to data entry requirements, and its functions can be expanded to provide service access and data output for other business systems.
Smart Images

Figure CN114970478B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of information collection technology, specifically to a general information collection platform for universities with a multi-level report model. Background Technology
[0002] The possibility of new problems and difficulties arising at any time means that new information collection needs will be generated at any time. These needs need to meet four requirements: rapid report development, accurate delivery to the person filling out the report, monitorable information collection progress, and real-time summary and statistics of collected data.
[0003] In traditional information collection scenarios within schools, units requiring information collection typically use methods such as email, instant messaging software, third-party data entry apps, and custom-developed data entry systems to collect information based on their business needs. These traditional methods have the following drawbacks: 1. Collecting and summarizing electronic documents via email or instant messaging software results in high communication costs, a large workload for data processing, low data reliability, difficulty in data reuse, and challenges in subsequent querying and statistical work. 2. Data entry via third-party online data entry apps has also become a common method in recent years. However, the data entry entry point cannot accurately target the reporting audience, and the data collection exit point is prone to information leakage and other information security issues, making it unsuitable for data entry needs with high confidentiality requirements or involving large amounts of personal information. 3. Over the years of IT development, the applicant has custom-developed several information collection systems tailored to the specific needs of various departments within the school. While these custom-developed systems can achieve information collection with high security and data exchange capabilities, they are limited to specific scenarios and generally come with complex approval processes established by the departments, lacking the flexibility and adaptability for widespread deployment.
[0004] The "Data Rate Limiting System Based on Custom Reports" with the publication number "CN114357960A" has a report template configuration module, but the report configuration is not flexible enough. When the requirements change, it needs to be reconfigured, which is difficult to cope with changing situations. It does not have the function of automatically initiating periodic reporting. It cannot accurately initiate reporting for user groups. Summary of the Invention
[0005] The purpose of this invention is to provide a general information collection platform for universities with a multi-level report model. Based on the general multi-level report model of this invention, a construction scheme for the information collection platform for universities is provided. This scheme does not require secondary development for new information collection needs. The report configuration is simple and can be completed without technical knowledge. During the collection process, the identities of the monitoring administrator and the person filling in the data ensure the security and reliability of the collected data. The platform functions can be expanded to provide service access and data output support for other business systems. The collected data is centrally managed and supports reuse and sharing.
[0006] This invention has already been put into practical use within the applicant's organization, where an integrated information collection platform has been designed and developed, encompassing information collection initiation, submission, review, and data analysis. The platform can be applied not only to urgent and non-routine information collection tasks but also to routine tasks such as energy consumption information collection.
[0007] When the faculty and staff information collection system runs on the information collection platform, the data model configuration can be completed in just one day. User groups are divided according to departments, information submission is initiated, and the data collection portal is sent to the submitters via WeChat messages. As for the daily work of energy information collection, since the data model configuration was completed in February 2021, energy consumption information is automatically initiated quarterly among submitters in relevant logistics departments. The platform's secure, stable, convenient, and flexible features have earned it a good reputation.
[0008] To address the aforementioned technical problems, this invention adopts the following technical solution: a general-purpose university information collection platform with a multi-level report model, comprising an identity authentication system, an information collection platform, data entry services, and other services. The identity authentication system includes CARSI identity authentication and unified identity authentication. The information collection platform services include an access control system, a report model customization service, and a report export service. The data entry service requires the support of the information collection platform and includes generating a report model entry page. The data entry service is associated with the access control system of the information collection platform, and the report model generation page of the data entry service is associated with the report model customization service of the information collection platform. Other services include a university-wide data platform, a WeChat information service public account, a campus information portal, and email services.
[0009] The aforementioned multi-level report model of the general university information collection platform includes a report model customization service that comprises report information management, report project management, report information-project relationship management, user group management, data filler management, and data distribution rule management. The report information management uses a report information model; the report project management uses a report project model; the report information-project relationship management uses a report project relationship model; the user group management uses a user group model; the data filler management uses a data filler model and a user group role model; and the data distribution rule management uses a report distribution rule model.
[0010] The aforementioned multi-level report model of the general university information collection platform defines the basic information of the data collection reports in the report information model. The data table fields of the report information model include report UID, report name, and relational model UID. The report UID field is the primary key and serves as a unique identifier; the report name field records basic project information; the relational model UID is a foreign key and is associated with the report project relational model; the report information model also plays an important role in linking other modules in the multi-level report model. When a reporting requirement occurs, the report project relational model is linked through the relational model UID field, and the report distribution rule model is linked to the user group model to generate report records.
[0011] The aforementioned multi-level report model in the general university information collection platform defines the compositional relationship between the report information model and the report project model in the report project relationship model. The data table fields of the report project relationship model have relationship UID and project UID, with the relationship UID field being the primary key and serving as a unique identifier. The project UID field records information about all associated project UIDs. When the specific information collection items for the reporting requirements change, the project UID field in the report project relationship model is modified according to the specific changes, or a new report project relationship model is created and the project UID is updated. Dynamic association is achieved through the update project UID operation of the report project relationship model, which can flexibly and quickly respond to changes in reporting requirements, satisfying the generation of new report records while not losing the old report records.
[0012] The aforementioned multi-level report model in the general university information collection platform defines the specific data entry items that make up a report, the basic attributes of the items, and the data entry rules. The data table fields of the report item model include: Item UID, Item Name, Item Type, List Item, Default Value, Required, Validation Condition, Sub-item UID, Duplicate Table, and Item Filling Condition. The Item UID field is the primary key, serving as a unique identifier. The Item Name field records the title of the data item in the form. The Item Type field records information including characters, numbers, dates, and list options. The List Item field records the list of candidate items for the list options. The Default Value field can be empty or have a custom default value. The Required Field determines whether submission is possible; all required fields must be filled before submission. The Validation Condition field records various valid validations. The Sub-item UID field records the UIDs of all related items. The Duplicate Table field determines whether a lower-level item should be repeated. The Item Filling Condition field records the trigger conditions for whether a lower-level item should be filled.
[0013] In the aforementioned multi-level report model of the general university information collection platform, the project UID field of the report project relationship model records the project UID as the first-level report project, which is used to generate the main report form. Then, combined with the lower-level project UID field and the duplicate table field in the report project model data table, the next-level project of the corresponding project UID is associated, and finally a complete multi-level report form is generated. The multi-level report form provides existing report visualization services through the filling platform, and finally becomes a filling project that users see on the WEB filling page.
[0014] The aforementioned multi-level report model of the general information collection platform for universities defines a user group model as the basic unit for information collection, which is a division of units or individuals according to certain rules. The data table fields of the user group model include user group UID, user group name, division rule UID, and division rule. The user group UID field is the primary key and serves as a unique identifier; the user group name field records the user group name; the division rule UID field records the user group under the same division rule; and the division rule field records the rules for generating user groups. The customized user group model relies on the basic data support provided by the existing unified data exchange platform. When a reporting requirement occurs, the corresponding report information model is associated through the report distribution rule model, and report records are generated based on the user group model. During the information collection process, the user group is collected as a whole unit, corresponding to one information collection report. A unit or individual can belong to at most one user group under a division rule to ensure that data collection is not duplicated. Under different division rules, since a user may belong to a user group under each division rule, a user may belong to multiple user groups or not belong to any user group.
[0015] The aforementioned multi-level report model in the general university information collection platform defines the data permissions of users when filling out reports through a user group role model. Users with the same data permissions collaborate, jointly viewing, filling out, and maintaining the same report record. Reports within the same user group require different users to fill out their respective reports, achieved by setting different user group role models for users. The data table fields of the user group role model include user group role UID, role name, and user group UID. The user group role UID field is the primary key, serving as a unique identifier; the role name field records the user's custom role; and the user group UID... The ID field is defined as the primary key index; the data table fields for the submitter model include submitter UID, submitter information, user group UID, and user group role UID. The submitter UID field is the primary key and can be a student ID or employee ID, serving as a unique identifier; the submitter information field records the submitter's name, contact information, and other basic information; the user group UID field is defined as the primary key index; the user group role UID records the submitter's user group role; a user group can have any user group role, a role can have any submitter, and a user group role belongs to one user group; a submitter can belong to multiple user group roles, requiring multiple records to be defined.
[0016] The aforementioned multi-level report model in the general university information collection platform defines information for automatically generated reports and information for manually generated reports. The data table fields of the report distribution rule model include distribution rule UID, report UID, user group division rule UID, whether to initiate reporting periodically, periodic initiation interval, and administrator. The distribution rule UID field is the primary key, serving as a unique identifier. The report UID field is associated with the report UID in the report information model; the user group division rule UID field is associated with the division rule UID in the user group model; the reporting start time field records when the report is generated; the whether to initiate reporting periodically field records whether to automatically initiate reporting periodically; the periodic initiation interval field records the time interval between automatically initiated reporting periods; and the administrator field is associated with the role name field in the user group role model.
[0017] The aforementioned fields for report start time, whether to initiate report periodically, and periodic initiation interval are used to automatically generate reports. If these fields are not assigned values, they need to be manually initiated when submitting reports. Administrators can customize report services through the information collection platform. As the request initiator, they will be recorded in the report distribution rule model, and can then view, statistically analyze, and export the data from the multi-level report models they have created and the report records collected based on the multi-level report models.
[0018] The aforementioned multi-level report model in the general university information collection platform includes an identity authentication system that supports both a unified identity authentication platform and CARSI federated identity authentication to determine the legitimacy of users entering the system. Simultaneously, the system obtains relevant basic user information to perform user authentication and authorization. The access control system includes functional permissions and data permissions. Functional permissions are managed by a unified identity authentication role, restricting users to viewing and operating only authorized modules. Data permissions are defined by the platform's report administrator, who defines user groups and user group roles and authorizes report fillers within those groups, ensuring users can only operate reports within their authorized scope. The process of generating the report model and filling out the form is as follows: the report administrator customizes the multi-level report model according to the page prompts through the information collection platform's management page; at the start of the form filling process, the platform... The platform generates a form record for each user group based on a customized multi-level report model. After identity authentication and access control, the user enters the data entry service and reads the form data from the database. The data is then processed by a report visualization algorithm to convert the read JSON data into HTML format, dynamically generating multi-level entry pages. The report export service can export and store data in various text formats. The information collection platform provides the ability to summarize and analyze the collected data. Administrators can view the report collection data with authorized access on the information collection platform and export and store it in various file formats. The report export service can export a single report filled out by a user at one time, a summary report of all user groups in a single report information collection, and a comprehensive analysis report customized based on all collected data.
[0019] The aforementioned multi-level report model of the general university information collection platform includes various access methods, which can be customized according to specific business and administrator needs. Specifically, it can be deployed separately for projects, with a custom independent entry point; access can be through the campus information service hall microservice; after creating a report model and initiating the form filling, the entry point can be sent to the designated person through a WeChat information service public account push message or email.
[0020] Compared with existing technologies, the advantages of this invention are that its three modules—report, user group, and report distribution rules—of the general multi-level report model can adapt to changes in the specific information collection items required for data entry. This allows for modification of the project fields in the report project relationship model or the creation of a new report project relationship model with updated fields, eliminating the need for secondary development for new information collection requirements and providing flexible customization of information collection reports. Report configuration is simple and requires no technical knowledge. Monitoring the identities of administrators and data entry personnel during the collection process ensures the security and reliability of the collected data. The platform's functionality is expandable to provide service access and data output support to other business systems, and the centralized management of collected data supports reuse and sharing. Attached Figure Description
[0021] Figure 1 This is a structural diagram of the present invention;
[0022] Figure 2 This is a diagram showing the relationship between the report model of this invention;
[0023] Figure 3 This is a diagram showing the relationship between the user group model and the data entry person model of this invention;
[0024] Figure 4 These are the report distribution rules of this invention;
[0025] Figure 5 This invention relates to the report model customization and data entry process.
[0026] The present invention will be further described below with reference to the accompanying drawings and specific embodiments. Detailed Implementation
[0027] Embodiment 1 of the present invention: A general-purpose university information platform with a multi-level report model, comprising an identity authentication system, an information collection platform, a data entry service, and other services. The identity authentication system includes CARSI identity authentication and unified identity authentication. The information collection platform services include an access control system, a report model customization service, and a report export service. The data entry service requires the support of the information collection platform and includes generating a data entry page from a report model. The data entry service is associated with the access control system of the information collection platform, and the data entry service's report model generation page is associated with the report model customization service of the information collection platform. Other services include a university-wide data platform, a WeChat information service public account, a campus information portal, and email services. For details on the collection platform structure, see [link to documentation]. Figure 1 .
[0028] Embodiment 2 of the present invention: A general information collection platform for higher education institutions with a multi-level reporting model, including an identity authentication system, an information collection platform, data entry services, and other services;
[0029] The identity authentication system can support a unified identity authentication platform and CARSI federated identity authentication to determine the legitimacy of users entering the system. At the same time, the system obtains relevant basic information about users to perform identity authentication and authorization.
[0030] The information collection platform's services include an access control system, report model customization services, and report export services. The access control system includes functional permissions and data permissions. Functional permissions are managed by a unified identity authentication role, restricting users to only viewing and operating modules with which they have permission. Data permissions are defined by the platform's report administrator, who defines user groups and user group roles and authorizes the data entry personnel within each user group, ensuring that users can only operate reports within their own permission scope.
[0031] The report model customization service of the information collection platform includes report information management, report project management, report information-project relationship management, user group management, data filler management, and data distribution rule management. The report information management uses a report information model; the report project management uses a report project model; the report information-project relationship management uses a report project relationship model; the user group management uses a user group model; the data filler management uses a data filler model and a user group role model; and the data distribution rule management uses a report distribution rule model. For details on the report model relationships, see [link to details]. Figure 2 ;
[0032] The report information model defines the basic information of the data collection report. The data table fields of the report information model include report UID, report name, and relational model UID. The report UID field is the primary key, serving as a unique identifier; the report name field records basic project information; the relational model UID is a foreign key and is associated with the report project relational model. In multi-level report models, the report information model also plays a crucial role in linking other modules. When a reporting requirement occurs, the relational model UID field is used to link the reporting project relational model, and the report distribution rule model is linked to the user group model to generate report records. The basic information defined in the report information model is detailed in Table 1 below:
[0033] The report item relationship model defines the compositional relationship between the report information model and the report item model. The data table fields of the report item relationship model include a relationship UID and an item UID. The relationship UID field is the primary key, serving as a unique identifier; the item UID field records the UIDs of all associated items. Detailed information about the basic definition of the report item relationship model is shown in Table 2 below:
[0034]
[0035] When the specific information collection items for the reporting requirements change, the project UID field in the report project relationship model is modified according to the specific circumstances of the change, or a new report project relationship model is created and the project UID is updated. Dynamic association is completed through the update project UID operation of the report project relationship model, which can flexibly and quickly respond to changes in reporting requirements. It can not only meet the requirements of generating new report records, but also ensure that the old report records that have been generated are not lost.
[0036] The report project model defines the specific data entry items that make up a report, the basic attributes of each item, and the data entry rules. The data table fields of the report project model include: Project UID, Project Name, Project Type, List Item, Default Value, Required, Validation Condition, Sub-project UID, Duplicate Table, and Item Filling Condition. The Project UID field is the primary key, serving as a unique identifier. The Project Name field records the title of the data item in the form. The Project Type field records character, number, date, and list options. The List Item field records the list of candidate items for the list options. The Default Value field can be empty or have a custom default value. The Required Field field determines whether submission is possible; all required fields must be filled before submission. The Validation Condition field records various valid validations. The Sub-project UID field records the UIDs of all related projects. The Duplicate Table field determines whether a sub-project should be repeated. The Item Filling Condition field records the trigger conditions for whether a sub-project should be filled. Detailed information about the basic information defined in the report project model is shown in Table 3 below.
[0037]
[0038] The project UID field in Table 3 of the report project relationship model records the project UID as the first-level report project, which is used to generate the main report form. Then, combined with the lower-level project UID field and the duplicate table field in the report project model data table, the next-level project of the corresponding project UID is associated, and finally a complete multi-level report form is generated. The multi-level report form provides the existing report visualization service through the filling platform, and finally becomes a filling project that users see on the WEB filling page.
[0039] The user group model defines the basic unit for information collection, which is the division of units or individuals according to certain rules. The data table of the user group model includes fields such as user group UID, user group name, division rule UID, and division rule. The user group UID field is the primary key and serves as a unique identifier; the user group name field records the user group name; the division rule UID field records the user group under the same division rule; and the division rule field records the rules for generating user groups. The basic information of the user group model definition is detailed in Table 4 below:
[0040]
[0041] The customized user group model relies on the basic data support provided by the existing unified data exchange platform. When a data entry requirement occurs, the corresponding report information model is associated with the report distribution rule model, and report records are generated based on the user group model. During the information collection process, user groups are collected as a whole unit, corresponding to one information collection report. Under a certain classification rule, a unit or individual can belong to at most one user group to ensure that data collection is not duplicated. Under different classification rules, since a user may belong to a user group under each classification rule, a user may belong to multiple user groups or not belong to any user group. For details on the relationship between the user group model and the data entry model, please refer to [link to relevant documentation]. Figure 3 ;
[0042] The data entry model defines the data permissions of users when entering data through a user group role model. Data entry users with the same data permissions have a collaborative relationship, jointly viewing, entering, and maintaining the same report record. Reports within the same user group require different data entry users to enter their respective reports. This is achieved by setting different user group role models for data entry users. The data table fields of the user group role model include user group role UID, role name, and user group UID. The user group role UID field is the primary key, serving as a unique identifier; the role name field records the user's custom role; and the user group UID field is defined as the primary key index. The basic information of the user group role model definition is detailed in Table 5 below:
[0043]
[0044] The data table fields for the submitter model include Submitter UID, Submitter Information, User Group UID, and User Group Role UID. The Submitter UID field is the primary key and can be either a student ID or an employee ID, serving as a unique identifier. The Submitter Information field records the submitter's name, contact information, and other basic information. The User Group UID field is defined as a primary key index. The User Group Role UID records the submitter's user group role. Details of the basic information defined in the submitter model are shown in Table 6 below.
[0045]
[0046] A user group can have any number of user group roles, a role can have any number of people filling out forms, and a user group role belongs to a user group; a person filling out forms can belong to multiple user group roles, and multiple records need to be defined.
[0047] The report distribution rule model defines information for automatically generated reports and manually generated reports. The data table fields of the report distribution rule model include distribution rule UID, report UID, user group division rule UID, whether to initiate reporting periodically, periodic initiation interval, and administrator. The distribution rule UID field is the primary key, serving as a unique identifier. The report UID field is associated with the report UID in the report information model; the user group division rule UID field is associated with the division rule UID in the user group model; the reporting start time field records when the report is generated; the whether to initiate reporting periodically field records whether to automatically initiate reporting periodically; the periodic initiation interval field records the time interval for automatically initiating reporting periodically; the administrator field is associated with the role name field in the user group role model. Detailed information about the basic information defined in the report distribution rule model is shown in Table 7 below.
[0048]
[0049] Table 7 lists the start time, whether the submission is initiated periodically, and the interval between periodic submissions for information used in automatic report generation. If these parameters are not assigned, manual initiation is required. Administrators customize report models through the information collection platform. As the request initiator, they are recorded in the report distribution rule model and can then view, statistically analyze, and export data from their created report models and report records collected based on those models. The report model customization and data entry process is as follows: Administrators log in and pass unified identity authentication to access the information collection platform management page. They customize multi-level report models on the visualization page according to their needs and write the generated templates and rules into the database. When a form needs to be submitted, it can be initiated manually by the administrator in the backend or automatically according to the customized rules. After submission, the report distribution rules and the multi-level report templates in the database generate the form to be filled. The report visualization algorithm converts the read JSON data into HTML format, dynamically generating multi-level submission pages. Once the submitter completes the submission and submits, their information is stored in the information collection platform database. For details on the report model customization and data entry process, please refer to [link to relevant documentation]. Figure 5 ;
[0050] The report export service of the information collection platform can export and save data in various text formats. The information collection platform can summarize and analyze the collected data. Administrators can view the report collection data with permissions on the information collection platform and export and save it in various file formats. The report export service can export a single report filled out by a reporter at one time, a summary report of all user groups in a report information collection, and a comprehensive analysis report customized based on all collected data. The multi-level report model itself can be connected to existing data report export services, such as POI toolkits and third-party platforms such as FineReport.
[0051] The data entry service requires the support of the information collection platform. The data entry service includes a corresponding access control system and report model generation and entry page. The access control system includes functional permissions and data permissions. Functional permissions are managed by a unified identity authentication role, which restricts users to only viewing and operating the modules they have permission to access. Data permissions are defined by the platform's report administrator, who defines user groups and user group roles and authorizes users in the user groups to enter data, ensuring that users can only operate reports within their own permission scope.
[0052] The process of generating the data entry page from the report model of the data entry service is as follows: The report administrator customizes a multi-level report model according to the page prompts through the management page of the information collection platform; when the data entry begins, the platform generates a form record to be filled for each user group based on the customized multi-level report model; after identity authentication and access control, the data entry user enters the data entry service and reads the form data to be filled from the database. The data is then converted from the read JSON data into HTML format by the report visualization algorithm, and a multi-level data entry page is dynamically generated.
[0053] Other services include multiple access methods, which can be customized according to specific business and administrator needs. Specifically, they can be deployed separately for projects with a custom independent entry point; accessed through the Campus Information Service Hall microservice; or, after creating a report model and initiating the form submission, the entry point can be sent to the designated submitter via WeChat information service official account push message or email.
[0054] The working principle of one embodiment of the present invention is as follows: The administrator logs in and enters the information collection platform management page, and customizes a multi-level report model on the visualization page as needed; when the data entry begins, the information collection platform generates a form record to be filled for each user group based on the multi-level report model customized by the administrator; after identity authentication and access control, the user in the user group enters the data entry service and reads the form data to be filled from the information collection platform database. The data is converted from the read JSON data into HTML format by the report visualization algorithm, and a multi-level data entry page is dynamically generated; the user begins to fill in the data, and after the information is submitted, the user's information is stored in the information collection platform database. The information collection platform summarizes and analyzes the collected data. The administrator can view the report collection data that they have permission to access on the information collection platform. The platform can export a single report filled in by a user at one time, a summary report of all user groups in a single report information collection, and a comprehensive analysis report customized based on all collected data. The exported data can be stored in various file formats.
Claims
1. A general college information collection platform of a multi-level report model, characterized in that, This includes an identity authentication system, an information collection platform, data entry services, and other services. The identity authentication system includes CARSI identity authentication and unified identity authentication. The information collection platform provides services including an access control system, report model customization services, and report export services. The data entry service requires the service support of the information collection platform. The data entry service includes generating a report model and a data entry page, as well as the data entry service's permission control system associated with the information collection platform, and the data entry service's report model generation and data entry page's report model customization service associated with the information collection platform. Other services include a campus-wide data platform, a WeChat information service account, a campus information portal, and email services; The report model customization service of the information collection platform includes report information management, report project management, report information-project relationship management, user group management, data filler management, and data distribution rule management. The report information management uses a report information model; the report project management uses a report project model; the report information-project relationship management uses a report project relationship model; the user group management uses a user group model; the data filler management uses a data filler model and a user group role model; and the data distribution rule management uses a report distribution rule model. The report item relationship model defines the compositional relationship between the report information model and the report item model. The data table fields of the report item relationship model have relationship UID and item UID. The relationship UID field is the primary key and serves as a unique identifier. The item UID field records the associated item UID. When the specific information collection items of the reporting requirements change, the item UID field in the report item relationship model is modified according to the specific changes, or a new report item relationship model is created and the item UID is updated. Dynamic association is completed through the update item UID operation of the report item relationship model, which can flexibly and quickly respond to changes in reporting requirements. It can not only meet the requirements of generating new report records, but also ensure that the old report records are not lost. The project UID field in the report project relationship model records the project UID as the first-level report project, which is used to generate the main report form. Then, combined with the lower-level project UID field and the duplicate status field in the report project model data table, the next-level project of the corresponding project UID is associated, and finally a complete multi-level report form is generated. The multi-level report form provides existing report visualization services through the filling platform, and finally becomes a filling project that users see on the WEB filling page.
2. The general college information collection platform of a multi-level report model according to claim 1, characterized in that, The report information model defines the basic information of the data collection report. The data table fields of the report information model include report UID, report name, and relational model UID. The report UID field is the primary key and serves as a unique identifier; the report name field records basic project information; the relational model UID is a foreign key and is associated with the report project relational model; the report information model also plays an important role in linking other modules in the multi-level report model. When a reporting requirement occurs, the report project relational model is linked through the relational model UID field, and the report distribution rule model is linked to the user group model to generate report records.
3. The universal college information collection platform of a multi-level report model according to claim 2, characterized in that, The report project model defines the specific data entry items that make up a report, the basic attributes of each item, and the data entry rules. The data table fields of the report project model include: Project UID, Project Name, Project Type, List Items, Default Value, Required, Validation Conditions, Sub-project UID, Duplicate Table, and Item Filling Conditions. The Project UID field is the primary key, serving as a unique identifier. The Project Name field records the title of the data item in the form. The Project Type field records information including characters, numbers, dates, and list options. The List Items field records the list of candidate items for the list options. The Default Value field can be empty or contain a custom default value. The Required field determines whether submission is possible; all required fields must be filled before submission. The Validation Conditions field records various valid validation methods. The Sub-project UID field records the UIDs of all related projects. The "Whether it is a Duplicate" field determines whether the next level item should be repeated; the "Item Fill Condition" field records information about whether the next level item should be filled in.
4. The general-purpose university information collection platform with a multi-level report model according to claim 1, characterized in that, The user group model defines the basic unit for information collection, which is the division of units or individuals according to certain rules. The data table fields of the user group model include user group UID, user group name, division rule UID, and division rule. The user group UID field is the primary key and serves as a unique identifier; the user group name field records the user group name; the division rule UID field records the user group under the same division rule; and the division rule field records the rules that generate the user group. The customized user group model relies on the basic data support provided by the existing unified data exchange platform. When a reporting requirement occurs, the corresponding report information model is associated through the report distribution rule model, and report records are generated based on the user group model. During the information collection process, the user group is collected as a whole unit, corresponding to one information collection report. A unit or individual can belong to at most one user group under a division rule to ensure that data collection is not duplicated. Under different division rules, since a user may belong to a user group under each division rule, a user may belong to multiple user groups or not belong to any user group.
5. The universal college information collection platform of a multi-level report model according to claim 1, characterized in that, The data entry model defines the data permissions of users when entering data through a user group role model. Data entry users with the same data permissions have a collaborative relationship, jointly viewing, entering, and maintaining the same report record. Reports within the same user group require different data entry users to enter their respective reports. This is achieved by setting different user group role models for data entry users. The data table fields of the user group role model include user group role UID, role name, and user group UID. The user group role UID field is the primary key, serving as a unique identifier; the role name field records the user's custom role; and the user group UID field is defined as the primary key index. The data table fields of the data filler model include data filler UID, data filler information, user group UID, and user group role UID. The data filler UID field is the primary key and can be a student ID or employee ID, serving as a unique identifier. The data filler information field records the data filler's name, contact information, and other basic information. The user group role UID field records the data filler's user group role. A user group can have any number of user group roles, a role can have any number of people filling out forms, and a user group role belongs to a user group; a person filling out forms can belong to multiple user group roles, and multiple records need to be defined.
6. The general higher education information collection platform of a multi-level report model according to claim 5, characterized in that, The report distribution rule model defines information for automatically generated reports and information for manually generated reports. The data table fields of the report distribution rule model include distribution rule UID, report UID, user group division rule UID, whether to initiate reporting periodically, periodic initiation interval, and administrator. The distribution rule UID field is the primary key and serves as a unique identifier; the report UID field is associated with the report UID of the report information model; the user group division rule UID field is associated with the division rule UID of the user group model; and the reporting start time field records when the report is generated. The "Whether to initiate data entry periodically" field records information to determine whether data entry is automatically initiated periodically; the "Periodic Initiation Interval" field records information at what time intervals data entry is automatically initiated periodically. The administrator field is associated with the role name field in the user group role model; The fields for "start time of reporting", "whether to initiate reporting periodically", and "interval of initiation periodically" are used to automatically generate reports. If these fields are not assigned values, they need to be manually initiated when reporting. Administrators customize report services through the information collection platform. As the request initiator, they will be recorded in the report distribution rule model, and can then view, statistically analyze, and export the data from their own multi-level report models and the report records collected based on the multi-level report models.
7. The universal college information collection platform of a multi-level report model according to claim 1, characterized in that, The identity authentication system supports a unified identity authentication platform and CARSI federated identity authentication to determine the legitimacy of users entering the system. Simultaneously, the system obtains relevant basic user information to perform identity authentication and authorization. The access control system includes functional permissions and data permissions. Functional permissions are managed by a unified identity authentication role, restricting users to viewing and operating only authorized modules. Data permissions are defined by the platform's report administrator, who defines user groups and user group roles and authorizes report fillers within those groups, ensuring users can only operate reports within their authorized scope. The process of generating the report model and filling out the form is as follows: the report administrator customizes a multi-level report model through the information collection platform's management page, following the page prompts; at the start of the form filling process, the platform generates a form record for each user group based on the customized multi-level report model. After identity authentication and access control, the user enters the data entry service and reads the form data to be filled from the database. The data is then processed by a report visualization algorithm to convert the read JSON data into HTML format, dynamically generating multi-level entry pages. The report export service can export and store data in various text formats. The information collection platform can summarize and analyze the collected data. Administrators can view the report collection data with permissions on the information collection platform and export and store it in various file formats. The report export service can export a single report filled out by a user at one time, a summary report of all user groups in a single report information collection, and a comprehensive analysis report customized based on all collected data.