A DOCUWORKS format file mark sharing method
Patent Information
- Application Number
- CN202611191569.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-07
- Publication Date
- 2026-11-03
AI Technical Summary
Existing DOCCUWORKS format files cannot be shared across terminals/users, tag data is not stored uniformly, version information is missing, historical tags cannot be traced, query efficiency is low, and it is difficult to meet the document tag management needs of multi-user collaborative office scenarios.
By performing structured parsing on DOCUWORKS format files, basic file information and taggable region data are extracted. Tag data is read and associated with version information, and stored in a database to achieve cross-user and cross-terminal tag sharing. Data protection is achieved using the AES-256 encryption algorithm, supporting multi-node redundant backup and off-site disaster recovery. Combined with hierarchical access control and multi-dimensional queries, the security and traceability of tag data are ensured.
It enables cross-user and cross-terminal sharing of DOCUWORKS file tags, meeting the needs of collaborative office work. Tag data is bound to version information to achieve version traceability. Tag data is stored uniformly and supports fast and accurate querying, improving the efficiency of document tag management.
Smart Images
Figure CN123030558A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the technical field of document processing, and in particular to a method for sharing tags in DOCUWORKS format files. Background Technology
[0002] DOCUWORKS is a commonly used electronic document format, widely used in document viewing, annotation, and archiving scenarios. Current technologies for marking DOCUWORKS files are mostly processed locally on a single machine, resulting in technical shortcomings such as the inability to share marks across terminals / users, lack of unified storage of marked data, missing version information, inability to trace historical marks, and low query efficiency. These limitations make it difficult to meet the document marking management needs of multi-user collaborative work scenarios. Summary of the Invention
[0003] To overcome the problems of existing DOCUWORKS file tags not being shareable, lacking version management, and being inconvenient to query, this application provides a method for sharing DOCUWORKS format file tags.
[0004] This application provides a method for sharing DOCUWORKS format files using tagging, which employs the following technical solution: A method for tagging and sharing DOCUWORKS format files includes the following steps: Step 1: Perform structured parsing on the DOCUWORKS format file to extract basic file information and taggable region data; Step 2: Read the user's tagging data for the DOCUWORKS file; Step 3: Associate the marked data with the version information and store it in the database; Step 4: Based on the tag data in the database, perform tag sharing operations for authorized users; Step 5: Perform version management on the tagged data and record version iteration information; Step 6: Based on the query criteria, retrieve the marked data and version information from the database.
[0005] Preferably, the structured parsing in step one further includes: The file is checked for encryption. If the file uses the built-in encryption mechanism of DocuWORKS, it is decrypted using the preset decryption key and then parsed. Extract the page structure data of the file, including page number, page size, page margin, layer hierarchy, and text flow coordinate information; Perform validity checks on the tagged areas and filter out non-editable locked areas or areas with restricted permissions.
[0006] Preferably, the marking data in step two includes marking location, marking type, marking content, operation time, operation user information, marking style parameters, associated object identifier, and marking status identifier; the marking style parameters include color value, line thickness value, fill transparency value, and font attribute; the associated object identifier is used to associate specific text paragraphs, images, tables, or formulas in the file; the marking status identifier includes draft status, confirmed status, archived status, and voided status.
[0007] Preferably, in step three, the version information is automatically generated by the system with a unique version number based on the operation time or number of modifications, supporting user-defined version names or version tags, and the version information and the tag data form a one-to-one correspondence; the storage operation further includes: The marked data is encrypted using the AES-256 symmetric encryption algorithm before being stored. The database is deployed using a distributed architecture, supporting multi-node redundant backup and off-site disaster recovery of tagged data; Establish an index linking the tagged data to the source files, with index fields including the source file ID, file version number, and tag creation time.
[0008] Preferably, the tag sharing operation in step four further includes: Role-based hierarchical access control includes read-only access to view tags, tag editing access to modify tags created by the user, tag management access to modify all tags, and access allocation access to authorize other users. Supports multiple sharing methods: real-time push to authorized users' interfaces, generation of shared links with expiration dates, and notification via email or system messages; Record shared access logs, including the accessing user ID, access time, access operation, and access duration.
[0009] Preferably, the version management in step five supports historical tag retrospection, operation log retention, version difference visualization comparison, automatic cleanup of redundant versions, and conflict resolution mechanism; the operation log includes operation user ID, operation type, operation time, and snapshots before and after data changes; the conflict resolution mechanism is as follows: when multiple people edit the same tag or the associated tag of the same file at the same time, conflict resolution is performed based on the operation timestamp priority and user permission level, with high-priority operations overriding low-priority operations, or merging non-conflicting tag attributes.
[0010] Preferably, the query operation described in step six supports: Multi-dimensional query conditions: tag type, user, time range, tag status, file page number, associated object type, keyword tag content or version tag; It combines fuzzy and precise queries, and supports the configuration, saving, and reuse of combined query conditions; The query results export function can export to Excel, PDF, or CSV format. The exported content includes the full data with tags and associated version information.
[0011] Preferably, it also includes step seven: real-time verification of the validity of the marked data. When the page structure of the DOCCUWORKS format file is modified, such as text deletion, image replacement, or page addition or deletion, the validity of the marked position is automatically detected, and the coordinate parameters of the invalid marked are adjusted through the page mapping algorithm to ensure that the correspondence between the marked and the original associated object is not interrupted.
[0012] Preferably, it also includes step eight: offline tag synchronization. Tag data created by the user while offline is stored in a local cache. After connecting to the network, the data is automatically compared with the database to synchronize the newly added or modified tag data, and data conflicts during the synchronization process are resolved based on version management rules.
[0013] Preferably, it also includes step nine: batch operation of tags, which supports batch editing, batch deletion, batch status update and batch permission adjustment operations on tags that meet preset conditions, including tag type, creation time, operating user and tag status.
[0014] In summary, this application includes at least one of the following beneficial technical effects: Enables cross-user and cross-terminal sharing of DocuWORKS file tags to meet collaborative office needs; tags are bound to version information to ensure traceability and management, preventing tag loss or confusion; tags are uniformly stored in the database, supporting fast and accurate queries and improving document tag management efficiency; the process is complete and highly adaptable, and can be widely applied to various DocuWORKS document processing scenarios. Attached Figure Description
[0015] Figure 1 This is a flowchart of a method for tagging and sharing DOCUWORKS format files. Detailed Implementation
[0016] The following provides a further detailed description of this application.
[0017] This application discloses a method for tagging and sharing DOCCUWORKS format files, referring to... Figure 1 The details are as follows: First, a structured parsing operation is performed on the DOCUWORKS format file. Before parsing, the file's encryption status is checked. If the file uses DOCUWORKS' built-in encryption mechanism, it is decrypted using a preset decryption key before parsing. During the parsing process, basic file information and markable area data are extracted. Page structure data such as page numbers, page size, margins, layer hierarchy, and text flow coordinates are also obtained. The markable areas are validated for validity, filtering out uneditable locked or restricted areas to ensure the feasibility of subsequent marking operations. Next, the user's marking data for the DOCUWORKS file is read. This marking data specifically includes marking position, marking type, marking content, operation time, user information, marking style parameters, associated object identifiers, and marking status identifiers. The marking style parameters include color values, line thickness values, fill transparency values, and font attributes. The associated object identifier is used to associate specific text paragraphs, images, tables, or formulas in the file. The marking status identifiers are divided into four categories: draft, confirmed, archived, and void. Subsequently, a one-to-one correspondence is established between the tagging data and version information. The version information is automatically generated by the system with a unique version number based on the operation time or number of modifications. User-defined version names or version tags are also supported. During storage, the tagging data is encrypted using the AES-256 symmetric encryption algorithm and then stored in a distributed database. This database supports multi-node redundant backup and off-site disaster recovery of the tagging data. A correlation index containing the source file ID, file version number, and tag creation time is established to enable fast lookup and association between tagging data and source files. When authorized users perform tag sharing operations based on the tagging data stored in the database, a role-based hierarchical permission control mechanism is adopted. Specific permission levels include read-only permission (allowing only viewing tags), tag editing permission (allowing only modification of tags created by the user), tag management permission (allowing modification of all tags), and permission allocation permission (allowing only authorization of other users). Multiple sharing methods are supported: real-time push to the authorized user's interface, generation of shared links with expiration dates, and notification via email or system messages. During the sharing process, a sharing access log is recorded, including the accessing user ID, access time, access operation, and access duration. When performing version management on tagged data, it supports historical tag backtracking, operation log retention, visual comparison of version differences, automatic cleanup of redundant versions, and conflict resolution mechanisms. The operation log includes the user ID, operation type, operation time, and snapshots before and after data changes. The conflict resolution mechanism works as follows: when multiple users simultaneously edit the same tag or associated tags of the same file, conflict resolution is performed based on operation timestamp priority and user permission levels, with higher-priority operations overriding lower-priority operations, or merging conflict-free tag attributes. Users can query tagged data and version information from the database based on query conditions. The query operation supports multi-dimensional query conditions including tag type, user, operation time range, tag status, file page number, associated object type, keyword tag content, or version tag. It uses a combination of fuzzy and precise queries, supports combined configuration and saving of query conditions for reuse, and can export query results to Excel, PDF, or CSV formats, including the full tag data and associated version information. To ensure the continuity and availability of the tag data, this embodiment also includes a real-time tag data validity verification step: when the page structure of the DOCUWORKS format file is modified, such as text deletion, image replacement, or page addition / deletion, the system automatically detects the validity of the tag position and adjusts the coordinate parameters of invalid tags through a page mapping algorithm to ensure that the correspondence between the tags and the original associated objects is not interrupted. For offline scenarios, an offline tag synchronization function is set up. Tag data created by the user offline is stored in a local cache. After connecting to the network, it automatically compares the data with the database, synchronizes newly added or modified tag data, and resolves data conflicts during the synchronization process based on version management rules. Furthermore, this embodiment also supports batch tag operations. Users can perform batch editing, batch deletion, batch status updates, and batch permission adjustments on tags that meet preset conditions, including tag type, creation time, operating user, and tag status.
[0018] The above are all preferred embodiments of this application, and are not intended to limit the scope of protection of this application. Therefore, all equivalent changes made in accordance with the structure, shape and principle of this application should be covered within the scope of protection of this application.
Claims
1. A method for tagging and sharing DOCCUWORKS format files, characterized in that: Includes the following steps: Step 1: Perform structured parsing on the DOCUWORKS format file to extract basic file information and taggable region data; Step 2: Read the user's tagging data for the DOCUWORKS file; Step 3: Associate the marked data with the version information and store it in the database; Step 4: Based on the tag data in the database, perform tag sharing operations for authorized users; Step 5: Perform version management on the tagged data and record version iteration information; Step 6: Based on the query criteria, retrieve the marked data and version information from the database.
2. The method for tagging and sharing DOCCUWORKS format files according to claim 1, characterized in that: The structured parsing described in step one also includes: The file is checked for encryption. If the file uses the built-in encryption mechanism of DocuWORKS, it is decrypted using the preset decryption key and then parsed. Extract the page structure data of the file, including page number, page size, page margin, layer hierarchy, and text flow coordinate information; Perform validity checks on the tagged areas and filter out non-editable locked areas or areas with restricted permissions.
3. The method for tagging and sharing DOCCUWORKS format files according to claim 1, characterized in that: The tagging data mentioned in step two includes tag location, tag type, tag content, operation time, operation user information, tag style parameters, associated object identifier, and tag status identifier; the tag style parameters include color value, line thickness value, fill transparency value, and font attributes; The associated object identifier is used to associate specific text paragraphs, images, tables, or formulas in the associated file; the marked status identifier includes draft status, confirmed status, archived status, and voided status.
4. The method for tagging and sharing DOCCUWORKS format files according to claim 1, characterized in that: The version information mentioned in step three is automatically generated by the system with a unique version number based on the operation time or number of modifications. Users can also customize version names or version tags, and there is a one-to-one correspondence between the version information and the tag data. The storage operation also includes: The marked data is encrypted using the AES-256 symmetric encryption algorithm before being stored. The database is deployed using a distributed architecture, supporting multi-node redundant backup and off-site disaster recovery of tagged data; Establish an index linking the tagged data to the source files, with index fields including the source file ID, file version number, and tag creation time.
5. A method for tagging and sharing DOCCUWORKS format files according to claim 1, characterized in that: The tag sharing operation described in step four also includes: Role-based hierarchical access control includes read-only access to view tags, tag editing access to modify tags created by the user, tag management access to modify all tags, and access allocation access to authorize other users. Supports multiple sharing methods: real-time push to authorized users' interfaces, generation of shared links with expiration dates, and notification via email or system messages; Record shared access logs, including the accessing user ID, access time, access operation, and access duration.
6. A method for tagging and sharing DOCCUWORKS format files according to claim 1, characterized in that, The version management described in step five supports historical tag retrospection, operation log retention, version difference visualization and comparison, automatic cleanup of redundant versions, and conflict resolution mechanism. The operation log includes the operation user ID, operation type, operation time, and snapshots before and after data changes. The conflict resolution mechanism is as follows: when multiple people edit the same tag or the associated tag of the same file at the same time, conflict resolution is performed based on the operation timestamp priority and user permission level. High-priority operations override low-priority operations, or non-conflicting tag attributes are merged.
7. A method for tagging and sharing DOCCUWORKS format files according to claim 1, characterized in that, The query operation described in step six supports: Multi-dimensional query conditions: tag type, user, time range, tag status, file page number, associated object type, keyword tag content or version tag; It combines fuzzy and precise queries, and supports the configuration and saving of combined query conditions for reuse. The query results export function can export to Excel, PDF, or CSV format. The exported content includes the full data with tags and associated version information.
8. A method for tagging and sharing DOCCUWORKS format files according to claim 1, characterized in that, It also includes step seven: real-time verification of the validity of the marked data. When the page structure of the DOCCUWORKS format file is modified, such as text deletion, image replacement, or page addition or deletion, the validity of the marked position is automatically detected, and the coordinate parameters of the invalid marked are adjusted through the page mapping algorithm to ensure that the correspondence between the marked and the original associated object is not interrupted.
9. A method for tagging and sharing DOCCUWORKS format files according to claim 8, characterized in that, It also includes step eight: offline tag synchronization. Tag data created by the user while offline is stored in the local cache. After connecting to the network, the data is automatically compared with the database to synchronize the newly added or modified tag data, and data conflicts during the synchronization process are resolved based on version management rules.
10. A method for tagging and sharing DOCCUWORKS format files according to claim 9, characterized in that, It also includes step nine: batch operation of tags, which supports batch editing, batch deletion, batch status update and batch permission adjustment operations on tags that meet preset conditions. The preset conditions include tag type, creation time, operation user and tag status.