A state change data package generation and permission control method and system for a chemistry research project

Abstract

The embodiment of the application relates to a state change data package generation and permission control method and system for a chemical research project, and the method comprises the following steps: receiving a project state change instruction of a target chemical research project; acquiring project performance association data based on a project identifier of the target chemical research project; freezing the project performance association data to generate a project state snapshot; performing consistency checking on current actual data based on the project state snapshot, and organizing the data passing the checking into a project life cycle data package according to a preset directory structure; generating partial settlement data objects based on the project state snapshot and the project life cycle data package, and performing hash two-way binding on the partial settlement data objects and the project life cycle data package; generating a state change event object according to the project state change instruction; and generating a field-level permission label according to a preset permission isolation strategy and the state change event object, and performing access permission configuration.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a method and system for generating and controlling access permissions for status change data packages for chemical research projects. Background Technology

[0002] In drug development, chemical synthesis, natural product separation, new material development, contract research organization / contract research and development organization (CRO / CDMO) services, custom non-standard compounds, impurity reference standard preparation, quality control testing and technical services projects, project transactions are often not simple transactions of standard commodities, but rather involve needs confirmation, technical route communication, quotation, phased execution, weekly reports, phase reports, quality documents, sample delivery, customer feedback, project completion report, handling of anomalies and possible project termination.

[0003] Existing e-commerce systems or general project management systems can typically record orders, payments, shipments, or simple statuses, but they are ill-suited to the following characteristics of chemical research projects: Project outcomes involve technical uncertainties and may be suspended or terminated due to route infeasibility, unavailable raw materials, uncontrollable impurities, substandard test results, or regulatory reasons; Project deliverables include not only samples or goods but also weekly reports, interim project reports, project completion reports, failed project reports, Certificates of Analysis (COA), Material Safety Data Sheets (MSDS), and quality documents such as high-performance liquid chromatography / liquid chromatography-mass spectrometry / nuclear magnetic resonance (HPLC / LCMS / NMR); For Customer-Factory Services (FFS), Full-Time Equivalent Services (FTE), milestone-based, custom synthesis, and quality control services, completed work, incurred costs, submitted reports, and sample status require structured confirmation; After project termination, partial settlement and wind-down procedures may be required between the parties. Cost confirmation, document archiving, dispute tracking, or project transfer; if a project is transferred to another supplier or re-initiated after adjustments, the technical communications, reasons for failure, quality documents, reports, and sample information from the original project need to be transferred or anonymized and shared within the authorized scope; ordinary order systems cannot link project termination reasons, report delivery status, quality anomalies, transferred documents, and subsequent projects to form a traceable data chain.

[0004] Therefore, when project status changes, how to achieve structured archiving, status migration, access control isolation, and audit trail recording of project performance data becomes an urgent problem to be solved. Summary of the Invention

[0005] Based on the above-mentioned situation of the prior art, the purpose of the embodiments of the present invention is to provide a method, system, electronic device, computer-readable storage medium and computer program product for generating and controlling the status change data package of chemical research projects, so as to realize the generation, termination settlement and project transfer processing of project life cycle data package, especially chemical research project transactions, so as to enable the structured archiving, status migration, access control and auditing of project performance data when the project is suspended, terminated, partially completed, disputed, transferred or re-initiated.

[0006] To achieve the above objectives, according to one aspect of the present invention, a method for generating and controlling access to status change data packages for chemical research projects is provided, the method comprising: Receive a project status change instruction for the target chemical research project; the project status change instruction includes at least one of the following: project suspension, project termination, partial completion, dispute resolution, project transfer, or re-initiation; Based on the project identifier of the target chemical research project, obtain project performance-related data; the project performance-related data includes at least two of the following: demand records, quotation records, supplier response records, project reports, quality documents, sample status, raw material status, cost records, communication confirmation records, and abnormal event records; The project performance-related data is frozen in status, and the unique identifier, key status summary and file storage information of each data record are extracted to generate a project status snapshot; the file storage information includes the file storage path and file hash value. Based on the project status snapshot, the current actual data is checked for consistency, and the data that passes the check is organized into a project lifecycle data package according to a preset directory structure; a partial settlement data object is generated based on the project status snapshot and the project lifecycle data package, and the partial settlement data object is hashed and bound to the project lifecycle data package in a two-way manner. A status change event object is generated based on the project status change instruction; the status change event object includes at least one of the following: termination event object, paused event object, partially completed event object, disputed event object, transferred event object, or re-initiated event object; Based on the preset permission isolation strategy, state change event objects, and sensitivity information of each data record in the project lifecycle data package, field-level permission tags are generated, and access permissions are configured for project data in the project lifecycle data package based on the field-level permission tags.

[0007] Furthermore, the method also includes: When the project status change instruction includes project transfer or re-initiation, a transfer data package and a new project association object are generated, and the transfer data package is anonymized. The new project association object includes the original project identifier, the new project identifier, the association type, the association reason, the authorization scope, the referenced data package identifier, and the timestamp, which are used to form a traceable project family tree. The status change event object, partial settlement data object, transfer data package, and new project associated object are written into the audit trail record. The audit trail record is used to record the creation, modification, access, confirmation, download, de-identification, and permission change events of the status change event object, partial settlement data object, transfer data package, and new project associated object.

[0008] Furthermore, the project performance-related data is frozen in state, and the unique identifier, key state summary and file storage information of each data record are extracted to generate a project state snapshot, including: traversing the project performance-related data, and for each data record, extracting the unique identifier, key state summary and file storage information of that data record; The unique identifier, key status summary, and file storage information are combined into a structured index object according to the original data structure of the project. This structured index object constitutes the project status snapshot.

[0009] Furthermore, based on the project status snapshot, a consistency check is performed on the current actual data, and the data that passes the check is organized into a project lifecycle data package according to a preset directory structure, including: Based on the unique identifier of the data record in the project status snapshot, locate and obtain the current actual data of the data record; Verify that the current actual data is consistent with the data at the time the project status snapshot was generated; Data that shows consistent verification results are organized according to a preset directory structure to generate a project lifecycle data package.

[0010] Furthermore, based on the project status snapshot and project lifecycle data package, a partial settlement data object is generated, including: Extract key status summaries from project status snapshots that fall within the scope of fulfilled obligations to form a list of settlementable records; the list of settlementable records includes at least one of the following: completed experimental rounds, submitted weekly reports, phase reports, quality documents, sample preparation status, incurred expenses, and wind-down costs; For each data record in the list of settleable records, set two confirmation status bits: buyer confirmation status bit and supplier confirmation status bit; The list of settlement records and the corresponding confirmation status bits of the data records are encapsulated into a partial settlement data object.

[0011] Furthermore, the partial settlement data object is hash-bound two-way with the project lifecycle data package, including: Write the unique identifier of the source project lifecycle data package and the overall hash value of the project lifecycle data package into the aforementioned partial settlement data object; Write the overall hash value of the partial settlement data object into the directory index of the project lifecycle data package to establish a two-way hash binding between the project lifecycle data package and the partial settlement data object.

[0012] Furthermore, the directory index includes a file list, storage location, source project status snapshot identifier, status summary verification result, hash verification result, sensitivity information, and field-level permission tags.

[0013] Furthermore, the transferred data package undergoes desensitization processing, including: Based on the scope of authorization from the purchaser, field-level permission tags, and desensitization rules, extract the data subset that can be transferred from the project lifecycle data package, and perform masking, replacement, deletion, or summarization processing on the restricted fields.

[0014] Furthermore, the project status change instructions can originate from the project details page, order page, quality control page, supplier workbench, purchaser workbench, API, message queue, ELN / LIMS, instrument system, or platform automatic rules.

[0015] According to a second aspect of the present invention, a system for generating and controlling access to state change data packages for chemical research projects is provided, the system comprising: The project status change receiving module is used to receive project status change instructions for the target chemical research project; the project status change instructions include at least one of the following: project suspension, project termination, partial completion, dispute resolution, project transfer, or re-initiation; The project performance data acquisition module is used to acquire project performance-related data based on the project identifier of the target chemical research project; the project performance-related data includes at least two of the following: demand records, quotation records, supplier response records, project reports, quality documents, sample status, raw material status, cost records, communication confirmation records, and abnormal event records; The status snapshot generation module is used to freeze the status of the project performance-related data, extract the unique identifier, key status summary and file storage information of each data record, and generate a project status snapshot; the file storage information includes the file storage path and file hash value. The lifecycle data package generation module is used to perform consistency verification on the current actual data based on the project status snapshot, and organize the data that passes the verification into a project lifecycle data package according to a preset directory structure. A partial settlement data object generation module is used to generate partial settlement data objects based on project status snapshots and project lifecycle data packages, and to perform a two-way hash binding between the partial settlement data objects and the project lifecycle data packages. The status change event object generation module is used to generate status change event objects according to the project status change instruction; the status change event object includes at least one of the following: termination event object, pause event object, partially completed event object, disputed event object, transfer event object, or re-initiated event object; The permission isolation module is used to generate field-level permission tags based on preset permission isolation policies, state change event objects, and sensitivity information of each data record in the project lifecycle data package, and to configure access permissions for project data in the project lifecycle data package based on the field-level permission tags.

[0016] According to a third aspect of the present invention, an electronic device is provided, including a memory, a processor, and executable instructions stored in the memory and executable on the processor, wherein the processor, when executing the executable instructions, implements the method as described in the first aspect of the present invention.

[0017] According to a fourth aspect of the present invention, a computer-readable storage medium is provided having computer-executable instructions stored thereon, which, when executed by a processor, implement the method as described in the first aspect of the present invention.

[0018] According to a fifth aspect of the present invention, a computer program product is provided, comprising a computer program / instructions that, when executed by a processor, implement the method as described in the first aspect of the present invention.

[0019] In summary, the embodiments of the present invention provide a method, system, electronic device, computer-readable storage medium, and computer program product for generating and controlling the status change data package of a chemical research project. The method includes: receiving a project status change instruction for a target chemical research project; obtaining project performance-related data based on the project identifier of the target chemical research project; freezing the status of the project performance-related data, extracting the unique identifier, key status summary, and file storage information of each data record, and generating a project status snapshot; performing consistency verification on the current actual data based on the project status snapshot, and organizing the verified data into a project lifecycle data package according to a preset directory structure; generating a partial settlement data object based on the project status snapshot and the project lifecycle data package, and performing a hash-based two-way binding between the partial settlement data object and the project lifecycle data package; generating a status change event object according to the project status change instruction; generating field-level permission tags according to a preset permission isolation strategy and the status change event object, and configuring access permissions for project data in the project lifecycle data package based on the field-level permission tags. The technical solution provided by the embodiments of the present invention integrates data freezing, verification, encapsulation and dynamic access control before the project status changes into an integrated automated processing flow, fundamentally solving the problem of data fragmentation and lack of credibility caused by termination or transfer in scientific research project transactions, and ensuring the integrity, traceability and compliance security of data throughout the project process. Attached Figure Description

[0020] Figure 1 This is a flowchart of the method for generating and controlling access permissions for status change data packages for chemical research projects provided by an embodiment of the present invention; Figure 2 This is an overall structural block diagram of the status change data package generation and access control system for chemical research projects provided by the embodiments of the present invention. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to specific embodiments and the accompanying drawings. It should be understood that these descriptions are merely exemplary and not intended to limit the scope of the invention. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concept of the invention.

[0022] It should be noted that, unless otherwise defined, the technical or scientific terms used in one or more embodiments of the present invention should have the ordinary meaning understood by one of ordinary skill in the art to which this invention pertains. The terms "first," "second," and similar terms used in one or more embodiments of the present invention do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Terms such as "comprising" or "including" mean that the element or object preceding the word encompasses the element or object listed following the word and its equivalents, without excluding other elements or objects. Terms such as "connected" or "linked" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect.

[0023] The technical solution of the present invention will be described in detail below with reference to the accompanying drawings. The embodiments of the present invention provide a method for generating and controlling access permissions for status change data packages in chemical research projects. Figure 1 The flowchart illustrates the method for generating and controlling access to status change data packages for chemical research projects. Figure 1 As shown, the method includes the following steps: S202, Receive the project status change instruction for the target chemical research project.

[0024] According to embodiments of the present invention, a project status change instruction refers to a computer-executable instruction or signal received by the system to trigger a target project to migrate from its current state to another state. The project status change instruction includes at least one of the following: project pause, project termination, partial completion, dispute resolution, project transfer, or re-initiation. This project status change instruction can be generated based on user operations or automatically triggered based on pre-set logical rules of the system. The project status change instruction contains at least one identifier to indicate the type of target state to be changed, such as project pause, project termination, partial completion, transfer, or re-initiation. The project status change instruction can be a structured API request, a data object event in a message queue, or a signal triggered by a user interface control. It can originate from project details pages, order pages, quality control pages, supplier workbench, buyer workbench, APIs, message queues, ELN / LIMS, instrument systems, or platform automatic rules; the present invention does not impose specific limitations on these.

[0025] A project status change instruction is a prerequisite for triggering the entire processing flow. This instruction must include at least a unique identifier for the target project and the type of status change. Project status change instructions can originate from two main sources: first, explicit user actions via the system interface (e.g., webpages, clients), such as clicking the "Terminate Project" or "Initiate Transfer" button on the project details page, which generates and sends the instruction; second, automatic triggering by internal system logic based on preset rules, such as when a project fails to respond within the specified timeframe or when the cumulative number of failed quality document parsing attempts reaches a certain threshold.

[0026] In one alternative implementation, a project status change instruction may include a metadata field carrying contextual information that triggered the instruction, such as a negotiation number, the reviewer's employee ID, or an internal work order ID. This metadata field can be passed to downstream steps to record the decision context in audit logs.

[0027] S204. Based on the project identifier of the target chemical research project, obtain project performance-related data.

[0028] According to an embodiment of the present invention, project performance-related data refers to a collection of computer data stored in a structured database or file storage system that is related to the entire lifecycle of the target project execution. This data collection, i.e., project performance-related data, includes project performance records, requirement records, quotation records, project reports, supplier response records, report deliverables, quality documents, sample status, raw material status, cost records, communication confirmation records, and abnormal event records.

[0029] The acquisition of this data set relies on the system identifying the unique identifier of the target project and querying and aggregating it from the associated data tables. Specifically, based on the unique identifier of the target project in the project status change instruction in step S202, a query request is initiated to the database to obtain project performance-related data associated with the execution phase.

[0030] In one optional implementation, the acquisition of project performance-related data can employ a step-by-step query or parallel query strategy to improve processing efficiency. For example, if project performance records and expense records come from different data tables, they can be queried in parallel using two database connections and finally aggregated in main memory. This invention does not limit the specific query strategy or database type, as long as the key project performance data can be obtained. This step aggregates data fragments scattered across different database tables and different file systems based on the unique identifier of the target project, providing a data foundation for the subsequent generation of a unified data package.

[0031] S206. Freeze the status of project performance-related data, extract the unique identifier, key status summary and file storage information of each data record, and generate a project status snapshot.

[0032] S208. Based on the project status snapshot, perform consistency verification on the current actual data, and organize the data that passes the verification into a project lifecycle data package according to the preset directory structure.

[0033] A project lifecycle data package refers to a structured collection of data generated by the system after receiving a status change instruction, based on project performance-related data throughout the entire project lifecycle. This data package contains snapshots of all key information about the target project from its creation to the moment of status change. Its data structure is a composite object containing multiple fields and sub-data sets, such as a JSON object or an XML document.

[0034] This step begins by "freezing" the project performance-related data at the current moment, generating an immutable project state snapshot. This snapshot is a full copy of the project's current state, recording all critical data at the instant the instruction arrives. By locking the target project's actual state before the state change, inconsistencies caused by concurrent data modifications during the generation of the project lifecycle data package can be prevented. The project state snapshot can be an independent dataset stored in a temporary table or in memory, decoupled from the real-time database. Then, based on this project state snapshot, a structured project lifecycle data package is generated.

[0035] In one optional implementation, the project lifecycle data package can be a compressed file containing a directory index, such as a ZIP format, or a structured JSON data object containing an index and summary information of all key data. The project lifecycle data package can assetize project data, forming a complete data block that can exist independently of the original operating environment, providing a unified data foundation for subsequent long-term preservation, auditing, or transfer. The above-described implementation method provided by this invention, which generates a project status snapshot and a project lifecycle data package based on project performance-related data when a project is abnormally terminated, can reduce the risk of losing project process information.

[0036] This invention is not limited to a single project management page, a unified transaction page, or a fixed front-end entry point. Project status change instructions and project lifecycle data packages can be generated from project pages, order pages, quality control pages, supplier workbench, purchaser workbench, APIs, message queues, ELN / LIMS, instrument systems, or platform automatic rules.

[0037] In one alternative implementation, project status snapshots and project lifecycle data packages can be generated based on the following steps: S2061. Traverse the project performance-related data. For each data record, extract its unique identifier, key status summary, and file storage information, including the file's storage path and file hash value. When a data record points to a file, such as a PDF report, it is necessary to extract the storage path and file hash value of the file that the data record points to.

[0038] S2062. The above unique identifier, key status summary, and file storage information are combined into a structured index object according to the original data structure of the project. This structured index object constitutes a project status snapshot. The project status snapshot itself does not contain any large file content and is extremely small in size. The generation process does not require moving large files, so it can be generated in milliseconds, greatly shortening the lock-in time for real-time business.

[0039] S2063. Based on the unique identifier of the data record in the above project status snapshot, locate and obtain the current actual data of the data record.

[0040] S2064. Verify whether the current actual data is consistent with the data at the time the project status snapshot was generated. This verification includes verifying whether the currently acquired actual data is consistent with the data in the key status summary of the project status snapshot; and for data records pointing to files, after reading the file content, recalculating the hash value of the file and comparing it with the file hash value recorded in the project status snapshot. If the verification results are consistent, it means that the data has not changed after the project status snapshot was generated; if the verification results are inconsistent, it means that the data has changed or the file has been modified after the project status snapshot was generated. At this time, according to the preset processing strategy, the system can prompt that the data is inconsistent, select a certain version to generate the project lifecycle data package, or terminate the generation of the project lifecycle data package.

[0041] S2065. Organize the data with consistent verification results according to a preset directory structure to generate a project lifecycle data package. Simultaneously, generate a directory index for the project lifecycle data package. This directory index includes a list and storage location of all files within the project lifecycle data package, a unique identifier for the source project status snapshot, and whether each data record passed dual verification of the status digest and hash value during the generation process, as well as the verification result. According to some optional embodiments, this directory index also includes sensitivity information and field-level permission tags for each data record. Field-level permission tags include visible, de-identified visible, read-only, downloadable, and access prohibited, etc., which can generate different access views for buyers, original suppliers, new suppliers, platform administrators, and auditors. Each field in the access view is labeled with a field-level permission tag. Sensitivity information can specifically be represented as a sensitivity score, which is generated, for example, through the following steps: S2065a. Based on the content type of the data record in the project lifecycle data package, obtain the type dimension score for that data record. The content type of the data record can be obtained from the file extension, metadata tags, or database field values, etc. The type dimension score can be obtained by referring to the content type and a preset type dimension score lookup table. For example, the score is 0.9 for the quotation details type; 0.8 for the supplier's internal remarks type; and 0.7 for unpublished experimental raw data types, etc. The type dimension score ranges from (0,1).

[0042] S2065b. Based on the uploader identifier of the data record, set a source coefficient for the data record. The uploader may be a buyer, supplier, or system, etc. For data uploaded by a supplier (such as quotations, internal notes, etc.), the source coefficient is 1; for data uploaded by a buyer, the source coefficient is 0.5; and for status records automatically generated by the system, the source coefficient is 0.2.

[0043] S2065c: If the contract records for the target project contain confidentiality clauses, add a fixed offset to the corresponding data records, for example, a value of 0.15.

[0044] S2065d. Based on the above-mentioned type dimension scores, source coefficients, and fixed offsets, calculate the sensitivity score for this data record. The sensitivity score can be calculated using the following formula:

[0045] Where S represents the sensitivity score, C represents the type dimension score, and K represents the source coefficient. This indicates a fixed offset. A lower sensitivity score indicates a lower level of confidentiality for that type of data record or file.

[0046] When a project terminates abnormally, generating a project status snapshot and a project lifecycle data package can reduce the risk of information loss. The generation process of the project status snapshot and project lifecycle data package provided in the above embodiments of the present invention uses the status digest and hash value in the project status snapshot to perform dual verification on the generation process of the project lifecycle data package. This ensures that the project lifecycle data package truly reflects the complete state of the project at the time of the status change, enabling both the detection of subsequent status changes and the detection of file tampering, providing objective and reliable evidence for settlement negotiation and dispute resolution. The project status snapshot only records the identifier, status digest, and hash value without transferring the file body, resulting in extremely fast generation speed and significantly reducing the time required to lock real-time business data. The project lifecycle data package can be packaged asynchronously, achieving separate storage of data credentials and data entities through decoupling, balancing data consistency and system response efficiency.

[0047] S210. Generate a partial settlement data object based on the project status snapshot and the project lifecycle data package, and perform a hash-based two-way binding between the partial settlement data object and the project lifecycle data package.

[0048] Partial settlement data objects refer to data objects used to record completed work, delivered goods, incurred costs, pending costs, and confirmation status by both parties. Based on project performance records and the confirmation status by both parties, a traceable data basis can be generated for settlement negotiations. Specifically, this step can be achieved through the following steps: S2101. Extract key status summaries from the project status snapshot that fall under the "fulfilled" category of data records to form a settlement record list. This list may include completed experimental rounds, submitted weekly reports, progress reports, quality documents, sample preparation status, and incurred costs. The "fulfilled" category includes, but is not limited to, statuses such as "completed," "submitted," "occurred," and "confirmed." The settlement record list may also include wind-down costs incurred after project termination, i.e., expenses incurred for project closure, sample disposal, data processing, and raw material handling after project termination. These costs can be included as part of the settlement data objects.

[0049] S2102. For each data record in the list of settleable records, set two confirmation status bits: buyer confirmation status bit and supplier confirmation status bit. The initial status of these two confirmation status bits can be extracted from the project lifecycle data package. These two confirmation status bits are stored independently of the project lifecycle data package and can be modified according to changes in the actual status. Modification records are written to the audit log.

[0050] S2103. Encapsulate the above-mentioned list of settlementable records and the corresponding confirmation status bits of the data records into a partial settlement data object. At the same time, write the unique identifier of the source project lifecycle data package and the overall hash value of the project lifecycle data package into this partial settlement data object.

[0051] S2104. Write the overall hash value of the aforementioned partial settlement data objects into the directory index of the project lifecycle data package, thereby establishing a two-way hash binding between the project lifecycle data package and the partial settlement data objects. The project lifecycle data package can clearly identify which partial settlement data object it was used to generate, and the partial settlement data object can also clearly identify which project lifecycle data package it was generated from. Any tampering with a partial settlement data object (such as modifying the fee amount) will cause its hash to change, thus resulting in a mismatch with the hash recorded in the project lifecycle data package.

[0052] The steps described above in this invention improve the traceability of completed work, costs, and deliverables confirmation through partial settlement data objects, achieving decoupling between the immutable project lifecycle data package and the variable settlement confirmation status. The project lifecycle data package maintains its integrity as solidified evidence at the moment of project status change, while the confirmation status bits are stored independently and support dynamic updates. The two are cryptographically bound through hash values, ensuring the traceability and integrity of the partial settlement data objects. Simultaneously, each data record includes a precise reference to the original evidence in the project lifecycle data package, ensuring that every cost in the settlement negotiation is supported by independently verifiable evidence. This effectively avoids disputes arising from subsequent data modification or loss of evidence, balancing the seriousness of data archiving with the flexibility of the settlement process.

[0053] S212. Generate a status change event object based on the above project status change instructions.

[0054] A status change event object is a data object generated by the system when a project is suspended, terminated, partially completed, or cannot continue. It records the termination type, reason, triggering party, trigger time, scope of impact, and subsequent actions. Status change event objects include at least one of the following: termination event object, suspension event object, partial completion event object, dispute event object, transfer event object, or re-initiation event object. This step is triggered if the project status change instruction in step S202 indicates that the project is terminated, suspended, or partially completed. An empty status change event object can be created, and its attributes can be populated based on the parameters in the project status change instruction and the data obtained in step S204. For example, the status change type (e.g., technically infeasible termination, budget adjustment termination, etc.) can be extracted from the project status change instruction as the "termination type"; if the data contains a text description of the termination reason, the system can encode it as a preset enumeration value and fill it into the "termination reason code" field. This status change event object is also used to record the triggering party (buyer, supplier, or system), trigger time, scope of impact, and subsequent actions.

[0055] S214. Based on the preset permission isolation strategy, state change event objects, and sensitivity information of each data record in the project lifecycle data package, generate field-level permission tags, and configure access permissions for project data in the project lifecycle data package based on the field-level permission tags.

[0056] After the project lifecycle data package is generated, not all data is visible to all roles. Access permissions for the project data in the project lifecycle data package are configured according to a preset permission isolation policy. This permission isolation policy defines the access permissions for different roles (buyer, original supplier, new supplier, platform administrator, auditor) for different fields, file types, or report types. Field-level permission tags are generated based on the preset permission isolation policy, state change event objects, and sensitivity information of each data record in the project lifecycle data package. Field-level permission tags include visible, anonymized visible, read-only, downloadable, and access prohibited. Different access views can be generated for the buyer, original supplier, new supplier, platform administrator, and auditor. Each field in the access view is labeled with a field-level permission tag based on sensitivity information. When a user accesses the data, the corresponding access view is loaded according to their role's access permissions, and access control is executed according to the field-level permission tags.

[0057] The above-described embodiments of the present invention, through a unified data processing flow, transform the processes of termination, partial completion, data archiving, and transfer of chemical research projects from manual email / form processing to a structured data processing flow. When abnormal termination occurs, the scattered performance data, reports, and quality information in the project are automatically transformed into several structured data objects with clear technical definitions. This can elevate data management in abnormal project completion scenarios from a discrete state to a system-automated structured data processing flow.

[0058] According to certain optional implementations, the method may further include the following steps: S216. When a project status change instruction includes project handover or re-initiation, a handover data package and a new project association object are generated, and the handover data package is anonymized.

[0059] A transfer data package refers to a collection of data generated within the authorized scope when a project is transferred to another supplier or re-initiated. It is a subset of project data that has undergone access control and anonymization. When the original project needs to be transferred to another supplier for execution, or is re-initiated for any reason, necessary information is extracted from the original project lifecycle data package according to the preset authorization scope. Certain sensitive fields may be automatically masked or replaced, generating a data package for use by the new participant. A new project association object is a data object used to record the relationship between the original project, the transferred project, and the re-initiated project. It includes the original project identifier, the new project identifier, the association type, the association reason, the authorization scope, the referenced data package identifier, and a timestamp, used to form a traceable project family tree. This object typically contains the original project identifier, the new project identifier, the association type, and the association timestamp, thus establishing a traceable project family tree in the system database. Anonymization of the transfer data package can be performed by extracting a subset of data that is allowed to be transferred from the project lifecycle data package based on the purchaser's authorization scope, field-level permission tags, and anonymization rules, and performing masking, replacement, deletion, or summarization on restricted fields.

[0060] S218. Write the status change event object, partial settlement data object, transferred data package and new project related object into the audit log.

[0061] In this step, status change event objects, partial settlement data objects, transfer data packages, and new project-related objects are written into the audit trail, thereby constructing a complete data traceability chain. The audit trail is used to record the creation, modification, access, confirmation, download, anonymization, and permission change events of status change event objects, partial settlement data objects, transfer data packages, and new project-related objects. When any core data object is created or updated in steps S208 to S214, the audit trail module is triggered and captures event details. These event details include at least the precise time of the operation, the user or system module identifier that performed the operation, the unique identifier of the operated object (e.g., status change event object ID), the operation type (create, modify, confirm, read), and a snapshot or difference of the content before and after the modification. This information is serialized and appended to an immutable audit log file or a dedicated audit database table. The establishment of this audit trail ensures that any creation and modification of project termination, settlement, and transfer data is traceable, providing reliable technical evidence for handling potential disputes and conducting compliance audits.

[0062] The following specific embodiments illustrate the technical solution of the present invention.

[0063] Example 1: The non-standard compound FFS project was terminated due to route infeasibility. The buyer initiates a custom non-standard compound project through the platform. The supplier submits a quotation, technical route, and milestones. During project execution, the supplier submits weekly reports and uploads intermediate detection data and HPLC chromatograms. After the third week, the supplier determines that the target route is not feasible under the current conditions and submits a project failure report through the platform. Upon receiving the project status change instruction to terminate the project, the system performs the following operations: 1. Based on the project's unique identifier in the project status change instruction, obtain project performance-related data, including project requirements, quotation version chain, weekly report list, monitoring graph, failed project report, and communication confirmation records.

[0064] 2. "Freeze" the current performance-related data to generate an immutable project status snapshot. This project status snapshot includes a unique identifier for each data record, a key status summary (such as "Report uploaded" or "Milestone partially completed"), and the file storage path and hash value.

[0065] 3. Based on the project status snapshot, a project lifecycle data package is generated after double verification (status digest comparison and file hash value comparison). This project lifecycle data package includes a directory index, all actual files, and a sensitivity score for each data record (automatically calculated based on content type, source, and confidentiality clause). Failed project reports are fully archived in the data package.

[0066] 4. Generate a status change event object based on the project status change instruction, where the termination reason code is mapped to "technical route is not feasible", and record information such as the triggering party, triggering time, and affected milestones.

[0067] 5. Extract data records from the project status snapshot whose key status summary is "Completed" or "Submitted" to form a list of settlementable records (including completed experimental rounds, submitted weekly reports, confirmed test documents, etc.). Assign independent buyer confirmation status bits and supplier confirmation status bits to each record, and encapsulate them into a partial settlement data object. This object simultaneously writes the source data package identifier and the overall hash value of the data package, and writes its own overall hash value back to the data package directory index, achieving two-way binding.

[0068] 6. With the buyer's authorization, mark the reasons for failure, structured route information, and key experimental conditions as negative samples for subsequent model training or project risk warning data, and write them into the audit log.

[0069] Example 2: The FTE project was terminated early due to budget adjustments, and a wind-down cost record was generated. The buyer and supplier conduct FTE-type projects through the platform. During the project, the system records personnel input, progress reports, sample preparation, and quality documentation. If the buyer requests early termination due to budget adjustments, the system receives the termination instruction and executes the following process: 1. Obtain project performance-related data, including personnel input time records, phase report lists, sample status, quality document lists, etc.

[0070] 2. Generate project status snapshots and project lifecycle data packages. The snapshots record the "occurred" status of each work record and the "submitted" status of each phase report, etc.

[0071] 3. Generate a status change event object, with the termination reason code being "budget adjustment" and the triggering party being the buyer.

[0072] 4. Extract the list of settlementable records: The system will automatically identify the wind-down costs (sample disposal fees, raw material processing fees, data processing fees, etc.) after the project is terminated, based on the "occurred" work hours records, submitted stage reports, and completed sample preparation items in the project status snapshot, along with the corresponding evidence references (pointing to specific documents in the data package) and include these cost items in the list of settlementable records.

[0073] 5. Set a confirmation status bit for each record (the initial status is extracted from the data package), encapsulate it into a partial settlement data object, and perform a two-way hash binding with the project lifecycle data package.

[0074] 6. The system does not automatically determine the final settlement amount, but only provides structured fee-evidence association entries and confirmation status bits for both parties to negotiate and confirm on the platform. All modifications to the confirmation status are recorded in the audit log.

[0075] Example 3: After the quality control service project is terminated, it is transferred to a third-party testing agency. The buyer commissioned the supplier to conduct quality control testing. Due to instrument malfunction, the supplier was unable to complete the test on schedule. The buyer decided to transfer the project to another third-party testing agency and issued a project status change instruction containing the "transfer" type through the platform. The system executed the following operations: 1. Obtain the performance-related data of the original project, including sample information, testing requirements, completed test results, uncompleted test items, quality document list, supplier internal notes, commercial quotations, etc.

[0076] 2. Generate a snapshot of the original project's status and a project lifecycle data package, and generate a status change event object. The termination reason is "insufficient supplier capabilities".

[0077] 3. Based on the preset permission isolation strategy and the termination reason in the state change event object (here, "Supplier Default" with an adjustment factor of -0.4), calculate the access score for each data block in the project lifecycle data package: Access Score = Sensitivity Score + Adjustment Factor. Then compare it with the basic permission threshold for each role to determine the access permissions.

[0078] 4. Due to the negative adjustment factor, highly sensitive data blocks such as supplier internal notes and commercial quotations are deemed "prohibited" from access; while less sensitive data blocks such as sample information, testing requirements, completed test results, incomplete test items, and quality document lists can still be "read-only" or "downloaded" for new supplier roles (with lower basic thresholds).

[0079] 5. Based on the above permission determination results, the system extracts a subset of data within the authorized scope from the original project lifecycle data package and generates a transfer data package. This data package does not contain any prohibited sensitive information.

[0080] 6. At the same time, generate a new project association object, record the original project identifier, the new project identifier, and the association type as "transfer to", and write it into the audit log.

[0081] Example 4: Re-initiating a terminated project after adjustments After a project is terminated, the buyer adjusts the target purity, delivery quantity, or route conditions based on the failure report and supplier recommendations, and then initiates a new project through the platform. The system executes the following process: 1. When the original project was terminated, a project lifecycle data package and a status change event object were generated. After the new project is created, the system generates a new project association object, which includes the original project identifier, the new project identifier, the association type ("derived from"), the association reason ("adjusted conditions based on failure report"), and a timestamp.

[0082] 2. The related objects of the new project are written into the audit record, establishing a traceable family tree between projects.

[0083] 3. Based on the buyer's authorization (such as checking "Allow reference to original project technical data" when re-initiating), the system extracts data within the authorized scope from the original project's data package based on the permission isolation policy, including the termination reasons, failure reports, confirmed quality documents, and buyer-authorized technical communication records in the status change event object.

[0084] 4. This data is linked to the context of the new project in read-only mode. After logging into the platform, the new supplier (or the original supplier) can view the relevant information within the authorized scope without having to repeat communication about technical background and lessons learned.

[0085] In addition, embodiments of the present invention provide a system for generating and controlling access permissions for status change data packages in chemical research projects. Figure 2 The overall structural block diagram of the system is shown in the figure, such as Figure 2 As shown, the status change data package generation and access control system 300 for chemical research projects includes: The project status change receiving module 301 is used to receive project status change instructions for the target chemical research project; the project status change instructions include at least one of the following: project suspension, project termination, partial completion, dispute resolution, project transfer, or re-initiation.

[0086] The project performance data acquisition module 302 is used to acquire project performance-related data based on the project identifier of the target chemical research project. The project performance-related data includes at least two of the following: demand records, quotation records, supplier response records, project reports, quality documents, sample status, raw material status, cost records, communication confirmation records, and abnormal event records.

[0087] The status snapshot generation module 303 is used to freeze the status of project performance-related data, extract the unique identifier, key status summary and file storage information of each data record, and generate a project status snapshot.

[0088] The lifecycle data package generation module 304 is used to perform consistency verification on the current actual data based on the project status snapshot, and organize the data that passes the verification into a project lifecycle data package according to a preset directory structure.

[0089] The partial settlement data object generation module 305 is used to generate partial settlement data objects based on project status snapshots and project lifecycle data packages, and to perform a hash-based two-way binding between the partial settlement data objects and the project lifecycle data packages.

[0090] The status change event object generation module 306 is used to generate status change event objects according to the project status change instruction; the status change event object includes at least one of the following: termination event object, pause event object, partially completed event object, disputed event object, transfer event object, or re-initiated event object.

[0091] The permission isolation module 307 is used to generate field-level permission tags based on the preset permission isolation strategy, state change event objects and sensitivity information of each data record in the project lifecycle data package, and to configure access permissions for project data in the project lifecycle data package based on the field-level permission tags.

[0092] According to certain optional implementations, the system may further include: The transfer data package generation module is used to generate a transfer data package when the project status change instruction includes project transfer or re-initiation, and to perform anonymization processing on the transfer data package.

[0093] The new project association module is used to generate new project association objects when the project status change instruction includes transfer or re-initiation. The new project association object includes the original project identifier, new project identifier, association type, association reason, authorization scope, referenced data package identifier and timestamp, which are used to form a traceable project family tree. The audit trail module is used to write status change event objects, partial settlement data objects, transferred data packages, and new project associated objects into audit trail records. Audit trail records are used to record the creation, modification, access, confirmation, download, de-identification, and permission change events of status change event objects, partial settlement data objects, transferred data packages, and new project associated objects.

[0094] The specific functions and operations of each module in the aforementioned state change data package generation and access control system for chemical research projects have been described in detail in the above-described method for state change data package generation and access control for chemical research projects. Therefore, their repeated description will be omitted here.

[0095] According to embodiments of the present invention, an electronic device is also provided, including a memory, a processor, and executable instructions stored in the memory and executable on the processor. When the processor executes the executable instructions, it implements the method described in the above embodiments of the present invention. The electronic device includes: one or more processors and a memory; and computer-executable instructions stored in the memory, which, when executed by the processor, cause the processor to perform the method described in the above embodiments of the present invention. The processor may be a central processing unit (CPU) or other processing unit having data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device to perform desired functions. The memory may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor may execute the program instructions to implement the steps in the method of the above embodiments of the present invention and / or other desired functions.

[0096] Embodiments of the present invention also provide a computer-readable storage medium storing computer-executable instructions thereon, which, when executed by a processor, implement the method described in the above embodiments of the present invention. The computer-readable storage medium may be any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may, for example, include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. It should be understood that the processor in embodiments of the present invention can be a central processing unit (CPU), which can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc.

[0097] In an embodiment of the present invention, a computer program product is also provided, including a computer program / instructions, which, when executed by a processor, implement the method described in the above embodiments of the present invention.

[0098] In summary, the embodiments of the present invention relate to a method, system, electronic device, computer-readable storage medium, and computer program product for generating and controlling the status change data package of a chemical research project. The method includes: receiving a project status change instruction for a target chemical research project; obtaining project performance-related data based on the project identifier of the target chemical research project; freezing the status of the project performance-related data, extracting the unique identifier, key status summary, and file storage information of each data record, and generating a project status snapshot; performing consistency verification on the current actual data based on the project status snapshot, and organizing the verified data into a project lifecycle data package according to a preset directory structure; generating a partial settlement data object based on the project status snapshot and the project lifecycle data package, and performing a hash-based two-way binding between the partial settlement data object and the project lifecycle data package; generating a status change event object according to the project status change instruction; generating field-level permission tags according to a preset permission isolation strategy and the status change event object, and configuring access permissions for project data in the project lifecycle data package based on the field-level permission tags. The technical solution provided by the embodiments of the present invention integrates data freezing, verification, encapsulation and dynamic access control before the project status changes into an integrated automated processing flow, fundamentally solving the problem of data fragmentation and lack of credibility caused by termination or transfer in scientific research project transactions, and ensuring the integrity, traceability and compliance security of data throughout the project process.

[0099] It should be understood that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of the invention (including the claims) is limited to these examples. Within the framework of this invention, technical features of the above embodiments or different embodiments can also be combined, steps can be implemented in any order, and many other variations exist regarding different aspects of one or more embodiments of the invention as described above; for the sake of brevity, they are not provided in the details. The specific embodiments described above are merely illustrative or explanatory of the principles of the invention and do not constitute a limitation thereof. Therefore, any modifications, equivalent substitutions, improvements, etc., made without departing from the spirit and scope of the invention should be included within the protection scope of the invention. Furthermore, the appended claims are intended to cover all variations and modifications falling within the scope and boundaries of the appended claims, or equivalent forms of such scope and boundaries.

Claims

1. A method for generating and controlling access to state change data packages for chemical research projects, characterized in that, The method includes: Receive a project status change instruction for the target chemical research project; the project status change instruction includes at least one of the following: project suspension, project termination, partial completion, dispute resolution, project transfer, or re-initiation; Based on the project identifier of the target chemical research project, obtain project performance-related data; the project performance-related data includes at least two of the following: demand records, quotation records, supplier response records, project reports, quality documents, sample status, raw material status, cost records, communication confirmation records, and abnormal event records; The project performance-related data is frozen in status, and the unique identifier, key status summary and file storage information of each data record are extracted to generate a project status snapshot; the file storage information includes the file storage path and file hash value. Based on the project status snapshot, the current actual data is checked for consistency, and the data that passes the check is organized into a project lifecycle data package according to a preset directory structure; a partial settlement data object is generated based on the project status snapshot and the project lifecycle data package, and the partial settlement data object is hashed and bound to the project lifecycle data package in a two-way manner. A status change event object is generated based on the project status change instruction; the status change event object includes at least one of the following: termination event object, paused event object, partially completed event object, disputed event object, transferred event object, or re-initiated event object; Based on the preset permission isolation strategy, state change event objects, and sensitivity information of each data record in the project lifecycle data package, field-level permission tags are generated, and access permissions are configured for project data in the project lifecycle data package based on the field-level permission tags.

2. The method according to claim 1, characterized in that, The method further includes: When the project status change instruction includes project transfer or re-initiation, a transfer data package and a new project association object are generated, and the transfer data package is anonymized. The new project association object includes the original project identifier, the new project identifier, the association type, the association reason, the authorization scope, the referenced data package identifier, and the timestamp, which are used to form a traceable project family tree. The status change event object, partial settlement data object, transfer data package, and new project associated object are written into the audit trail record. The audit trail record is used to record the creation, modification, access, confirmation, download, de-identification, and permission change events of the status change event object, partial settlement data object, transfer data package, and new project associated object.

3. The method according to claim 2, characterized in that, The project performance-related data is frozen in status, and the unique identifier, key status summary, and file storage information of each data record are extracted to generate a project status snapshot, including: Traverse the project performance-related data, and for each data record, extract its unique identifier, key status summary, and file storage information; The unique identifier, key status summary, and file storage information are combined into a structured index object according to the original data structure of the project. This structured index object constitutes the project status snapshot.

4. The method according to claim 3, characterized in that, Based on the project status snapshot, the current actual data is checked for consistency, and the data that passes the check is organized into a project lifecycle data package according to a preset directory structure, including: Based on the unique identifier of the data record in the project status snapshot, locate and obtain the current actual data of the data record; Verify that the current actual data is consistent with the data at the time the project status snapshot was generated; Data that shows consistent verification results are organized according to a preset directory structure to generate a project lifecycle data package.

5. The method according to claim 4, characterized in that, Based on the project status snapshot and project lifecycle data package, a partial settlement data object is generated, including: Extract key status summaries from project status snapshots that fall within the scope of fulfilled obligations to form a list of settlementable records; the list of settlementable records includes at least one of the following: completed experimental rounds, submitted weekly reports, phase reports, quality documents, sample preparation status, incurred expenses, and wind-down costs; For each data record in the list of settleable records, set two confirmation status bits: buyer confirmation status bit and supplier confirmation status bit; The list of settlement records and the corresponding confirmation status bits of the data records are encapsulated into a partial settlement data object.

6. The method according to claim 5, characterized in that, The partial settlement data object is hash-bound to the project lifecycle data package, including: Write the unique identifier of the source project lifecycle data package and the overall hash value of the project lifecycle data package into the aforementioned partial settlement data object; Write the overall hash value of the partial settlement data object into the directory index of the project lifecycle data package to establish a two-way hash binding between the project lifecycle data package and the partial settlement data object.

7. The method according to claim 6, characterized in that, The directory index includes a file list, storage location, source project status snapshot identifier, status summary verification result, hash verification result, sensitivity information, and field-level permission tags.

8. The method according to claim 7, characterized in that, The data package being transferred is anonymized, including: Based on the scope of authorization from the purchaser, field-level permission tags, and desensitization rules, extract the data subset that can be transferred from the project lifecycle data package, and perform masking, replacement, deletion, or summarization processing on the restricted fields.

9. The method according to claim 8, characterized in that, The project status change instructions come from the project details page, order page, quality control page, supplier workbench, purchaser workbench, API, message queue, ELN / LIMS, instrument system, or platform automatic rules.

10. A state change data package generation and access control system for chemical research projects, characterized in that, The system includes: The project status change receiving module is used to receive project status change instructions for the target chemical research project; the project status change instructions include at least one of the following: project suspension, project termination, partial completion, dispute resolution, project transfer, or re-initiation; The project performance data acquisition module is used to acquire project performance-related data based on the project identifier of the target chemical research project; the project performance-related data includes at least two of the following: demand records, quotation records, supplier response records, project reports, quality documents, sample status, raw material status, cost records, communication confirmation records, and abnormal event records; The status snapshot generation module is used to freeze the status of the project performance-related data, extract the unique identifier, key status summary and file storage information of each data record, and generate a project status snapshot; the file storage information includes the file storage path and file hash value. The lifecycle data package generation module is used to perform consistency verification on the current actual data based on the project status snapshot, and organize the data that passes the verification into a project lifecycle data package according to a preset directory structure. A partial settlement data object generation module is used to generate partial settlement data objects based on project status snapshots and project lifecycle data packages, and to perform a two-way hash binding between the partial settlement data objects and the project lifecycle data packages. The status change event object generation module is used to generate status change event objects according to the project status change instruction; the status change event object includes at least one of the following: termination event object, pause event object, partially completed event object, disputed event object, transfer event object, or re-initiated event object; The permission isolation module is used to generate field-level permission tags based on preset permission isolation policies, state change event objects, and sensitivity information of each data record in the project lifecycle data package, and to configure access permissions for project data in the project lifecycle data package based on the field-level permission tags.

11. An electronic device comprising a memory, a processor, and executable instructions stored in the memory and executable on the processor, characterized in that, When the processor executes the executable instructions, it implements the method as described in any one of claims 1-9.

12. A computer-readable storage medium having computer-executable instructions stored thereon, characterized in that, When the executable instructions are executed by the processor, they implement the method as described in any one of claims 1-9.

13. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the method as described in any one of claims 1-9.

Images