CN114707182A - Online document annotation authority control method and device - Google Patents
Online document annotation authority control method and device Download PDFInfo
- Publication number
- CN114707182A CN114707182A CN202210595505.1A CN202210595505A CN114707182A CN 114707182 A CN114707182 A CN 114707182A CN 202210595505 A CN202210595505 A CN 202210595505A CN 114707182 A CN114707182 A CN 114707182A
- Authority
- CN
- China
- Prior art keywords
- annotation
- authority
- user
- annotations
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6227—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database where protection concerns the structure of data, e.g. records, types, queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/169—Annotation, e.g. comment data or footnotes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Artificial Intelligence (AREA)
- Databases & Information Systems (AREA)
- Bioethics (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Document Processing Apparatus (AREA)
- Storage Device Security (AREA)
Abstract
The invention discloses an online document annotation authority control method and device, wherein the method comprises the following steps: detecting a preview operation; acquiring authority information of all annotations in a source file corresponding to preview operation; determining the authority of the user for the annotation according to the identity information of the user triggering the preview operation and the authority information of the annotation; and generating a preview interface according to the authority of the user for the annotation. By the online document annotation authority control method and device, when a user performs preview operation, different users have operation authorities corresponding to the user identity information on the annotations, and the user can edit the content of the annotations in a preview state, so that the problems that different previewers have the same operation authority and can only check the original annotations or add new annotations to the document, but the previewers cannot edit the existing annotations and the like are solved.
Description
Technical Field
The invention belongs to the field of document annotation control, and particularly relates to an online document annotation authority control method and device.
Background
When an operator edits a document, some annotations are added to the content of the document and then uploaded to a network disk for other users to preview, but when a shared document is previewed on the network disk in the prior art, different previewers have the same operation authority and can only view the original annotations or add new annotations to the document, but the previewers cannot edit the existing annotations.
Disclosure of Invention
According to the method and the device for managing and controlling the authority of the online document annotation, different users have operation authority corresponding to the identity information of the users for the annotation.
One aspect of the present invention provides a method for managing and controlling authority of online document annotation, including:
detecting a preview operation;
acquiring authority information of all annotations in a source file corresponding to the preview operation;
determining the authority of the user for the annotation according to the identity information of the user triggering the preview operation and the authority information of the annotation;
and generating a preview interface according to the authority of the user for the annotation.
In an implementation manner, the obtaining of the authority information of all annotations in the source file corresponding to the preview operation includes:
and if the source file is associated with an annotation file which comprises annotation identification codes and corresponding authority information of all annotations in the source file, acquiring the annotation identification codes and the corresponding authority information of all the annotations from the annotation file.
In an implementation manner, the obtaining right information of all annotations in a source file corresponding to the preview operation includes:
and one annotation file comprises an annotation identification code of an annotation and corresponding authority information, and the corresponding annotation identification code and the corresponding authority information are obtained from each annotation file when the source file is associated with the annotation file corresponding to each annotation.
In an implementation manner, the identity information of the user comprises a role of the user, and the authority information comprises a mapping relation between the role and the authority.
In an implementation manner, determining, according to identity information of a user who triggers the preview operation and authority information of the annotation, authority that the user has for the annotation includes:
traversing the annotation identification codes of all annotations;
and inquiring the mapping relation between the role and the authority in the authority information according to the role of the user aiming at the traversed current annotation identification code, and determining the authority of the user on the annotation corresponding to the current annotation identification code.
In an implementation manner, the generating a preview interface according to the authority that the user has for the annotation includes:
for any one annotation:
if the fact that the user does not have visible permission on the annotation is determined, the annotation is not displayed in the preview interface;
and if the user is determined to have visible authority to the annotation, displaying the annotation in the preview interface.
In one embodiment, when it is determined that the user has visible rights to the annotation, the method further comprises:
and if the user is determined to have editable and/or printable authority on the annotation, displaying the annotation in the preview interface and simultaneously displaying an editable button and/or a printable button of the annotation.
Another aspect of the present invention provides an online document annotation permission management and control apparatus, including:
the detection module is used for detecting preview operation;
the acquisition module is used for acquiring the authority information of all annotations in the source file corresponding to the preview operation;
the matching module is used for determining the authority of the user for the annotation according to the identity information of the user triggering the preview operation and the authority information of the annotation;
a generation module; and the preview interface is generated according to the authority of the user for the annotation.
In an implementation manner, if the source file is associated with an annotation file, where the annotation file includes annotation identification codes of all annotations in the source file and corresponding permission information, the obtaining module is configured to obtain the annotation identification codes of all annotations and corresponding permission information from the annotation file;
if one annotation file comprises an annotation identification code of an annotation and corresponding authority information, and the source file is associated with the annotation file corresponding to each annotation, the obtaining module is configured to obtain the corresponding annotation identification code and the corresponding authority information from each annotation file.
In an implementation manner, the matching module is configured to traverse annotation identification codes of all annotations, and for a current traversed annotation identification code, the matching module is configured to query a mapping relationship between a role and an authority in the authority information according to a role of a user, and determine an authority that the user has for an annotation corresponding to the current annotation identification code;
if the fact that the user does not have visible permission on the annotation is determined, the annotation is not displayed in a preview interface generated by the generation module;
if the user is determined to have visible authority to the annotation, the annotation is displayed in a preview interface generated by the generation module;
and if the user is determined to have editable and/or printable authority on the annotation, displaying the editable button and/or printable button of the annotation in the preview interface generated by the generation module.
Based on the above, by the method and the device for managing and controlling the authority of the online document annotation, when the user performs the preview operation, different users have the operation authority corresponding to the identity information of the user on the annotation, and the user can perform operations such as editing the content of the annotation in a preview state.
Drawings
FIG. 1 is a schematic flow chart of adding annotations provided by an embodiment of the present invention;
FIG. 2 is a flowchart illustrating an online document annotation authority control method according to an embodiment of the present invention;
FIG. 3 is a flowchart of an online document annotation authority control apparatus according to an embodiment of the present invention;
wherein the reference numbers are as follows:
001. a detection module; 002. an acquisition module; 003. a matching module; 004. and generating a module.
Detailed Description
In order to make the objects, features and advantages of the present invention more obvious and understandable, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
As shown in fig. 1, adding annotations to a source file by an editor specifically includes the following steps:
step 101, adding an annotation file, wherein the annotation file comprises one or more annotation identification codes of the annotations, and annotation information and authority information associated with the annotation identification codes.
In a cloud disk or other APP, under a source document editable mode, adding annotations to a source document to form an annotation file. The annotation information in the annotation file includes the content of the annotation, the position information of the annotation, the color and size of the font, and the like.
After the annotations are added, a generator in the server generates an annotation identification code, wherein the annotation identification code is used for uniquely identifying one annotation, further, the annotation identification code can be a bar code, and the corresponding generator can be a bar code generator; the annotation identification code may also be a number and the corresponding generator may be a random number generator.
And generating corresponding authority information aiming at the annotation, wherein the authority information comprises a user role and whether the user role has operation authority of visibility, editability, printing and the like for the annotation. Roles include individuals, organizations, teams, groups of users, and the like.
The server can store the annotation information, the annotation identification code and the authority information through a special annotation storage module, and the source file is stored in a file storage module of the server, so that the source file and the annotation file can be isolated.
In one embodiment, an annotation file is generated for each annotation, and the annotation file only includes annotation information, annotation identification codes and permission information corresponding to the annotation. Each annotation file is independent of each other, and the annotation files are stored separately from the source files.
In another embodiment, one annotation file is generated for all the annotations, the annotation file includes annotation information, annotation identification codes and authority information corresponding to each annotation, the annotation file is fragmented to form a plurality of independent annotation sub-files, and one annotation sub-file corresponds to one annotation. The fragmentation of the annotation file may be: the server identifies each annotation in the annotation files and generates annotation sub-files corresponding to each annotation. Each annotation subfile is stored separately, with the annotation subfile and the source file being stored separately.
And 102, sharing the source file added with the annotation file to one or more target users.
As shown in fig. 2, when one or more users preview a source file added with an annotation file, the method specifically includes the following steps:
step 201, detecting a preview operation;
when the user logs in the cloud disk or the app, the identity information of the user can be acquired, after the user logs in, the user can preview by clicking a preview button, and at the moment, the preview operation can be detected.
Step 202, acquiring authority information of all annotations in a source file corresponding to preview operation;
the acquiring of the authority information of all annotations in the source file corresponding to the preview operation includes the following two embodiments.
One embodiment is as follows: and if the source file is associated with an annotation file, and one annotation file comprises annotation identification codes and corresponding authority information of all the annotations in the source file, acquiring the annotation identification codes and the corresponding authority information of all the annotations from one annotation file.
The second embodiment: if one annotation file comprises an annotation identification code and corresponding authority information of one annotation, and the source file is associated with the annotation file corresponding to each annotation, the corresponding annotation identification code and the corresponding authority information are obtained from each annotation file, so that the annotation identification codes and the corresponding authority information of all the annotations can be obtained.
Step 203, determining the authority of the user for the annotation according to the identity information of the user triggering the preview operation and the authority information of the annotation;
the identity information of the user comprises the role of the user, and the role comprises an individual, an organization, a team, a user group and the like. The authority information includes a mapping relationship of roles and authorities.
Specifically, traversing all the annotation identification codes of the annotations based on the acquired annotation identification codes of all the annotations and the corresponding permission information; and inquiring the mapping relation between the role and the authority in the authority information corresponding to the current annotation identification code according to the role of the user aiming at the traversed current annotation identification code, and determining the authority of the user on the annotation corresponding to the current annotation identification code.
And step 204, generating a preview interface according to the authority of the user for the annotation.
For any one annotation:
if the fact that the user does not have visible permission on the annotation is determined, the annotation is not displayed in the preview interface;
and if the user is determined to have visible authority to the annotation, displaying the annotation in the preview interface.
If the user is determined to have editable and/or printable rights to the annotation, the annotation is displayed in the preview interface along with an editable button and/or a printable button of the annotation.
The annotation has editable authority for indicating editing of the content of the annotation, changing of the color and the size of the font and the like.
In generating the preview interface, the user may select, for any one of the annotations, specifically,
first embodiment
Step 214, determining whether the user has a visible right for the annotation, and if so, continuing to execute step 224; if the judgment result is negative, the annotation is not displayed in the preview interface;
step 224, judging whether the user has an editable right for the annotation, and if so, displaying the editable button of the annotation in a preview interface while displaying the annotation; and if the judgment result is negative, only displaying the annotation in the preview interface.
The editable button displaying the annotation is used for indicating that the editable button can be clicked to trigger editable operation, and the editable button not displaying the annotation is used for indicating that the editable button cannot be clicked and cannot trigger editable operation.
Second embodiment
Step 214, determining whether the user has a visible right for the annotation, and if so, continuing to execute step 234; if the judgment result is negative, the annotation is not displayed in the preview interface;
step 234, judging whether the user has a printable authority for the annotation, if so, displaying the annotation in a preview interface and displaying a printable button of the annotation; and if the judgment result is negative, only displaying the annotation in the preview interface.
The printable button displaying the endorsement is used for indicating that the printable button can be clicked to trigger the printable operation, and the printable button not displaying the endorsement is used for indicating that the printable button cannot be clicked to trigger the printable operation.
Third embodiment
Step 214, determining whether the user has a visible right for the annotation, and if so, continuing to execute step 244; if the judgment result is negative, the annotation is not displayed in the preview interface;
step 244, determine if the user has editable and printable rights to the annotation,
if the annotation has editable authority but does not have printable authority, only displaying an editable button of the annotation while displaying the annotation in a preview interface;
if the annotation has the editable right and the printable right, displaying the editable button and the printable button of the annotation in the preview interface at the same time.
If the annotation has the printable right but does not have the editable right, only displaying the printable button of the annotation while displaying the annotation in the preview interface;
if the annotation does not have printable or editable rights, the annotation is only displayed on the preview interface.
In order to implement the foregoing method, an embodiment of the present disclosure further provides an online document annotation permission management and control apparatus, please refer to fig. 3, including:
the detection module 001 is used for detecting preview operation;
when the user clicks the "preview" button, the detection module 001 detects a preview operation.
The obtaining module 002 is configured to obtain authority information of all annotations in the source file corresponding to the preview operation;
on one hand, if the source file is associated with an annotation file, and one annotation file includes annotation identification codes and corresponding authority information of all annotations in the source file, the obtaining module 002 obtains the annotation identification codes and corresponding authority information of all the annotations from one annotation file;
on the other hand, if one annotation file includes an annotation identification code and corresponding authority information of one annotation, and the source file is associated with the annotation file corresponding to each annotation, the obtaining module 002 obtains the corresponding annotation identification code and the corresponding authority information from each annotation file.
The matching module 003 is configured to determine, according to the identity information of the user who triggers the preview operation and the authority information of the annotation, the authority that the user has for the annotation;
the matching module 003 is configured to traverse annotation identification codes of all annotations, and for a current traversed annotation identification code, the matching module 003 queries a mapping relationship between a role and an authority in the authority information according to the role of the user, and determines an authority that the user has for an annotation corresponding to the current annotation identification code;
the identity information of the user comprises the role of the user, and the role comprises an individual, an organization, a team, a user group and the like. The authority information includes a mapping relationship of roles and authorities.
A generation module 004; and the preview interface is generated according to the authority of the user on the annotation.
If it is determined that the user does not have visible permission for the annotation, the generation module 004 does not display the annotation in the preview interface generated;
if the user is determined to have visible permission for the annotation, the generating module 004 generates a preview interface to display the annotation;
if it is determined that the user has editable and/or printable rights to the annotation, the editable button and/or printable button of the annotation is displayed at the same time the annotation is displayed in the preview interface generated by the generation module 004.
The editable button displaying the annotation is used for indicating that the editable button can be clicked to trigger editable operation, and the editable button not displaying the annotation is used for indicating that the editable button cannot be clicked and cannot trigger editable operation.
The printable button displaying the endorsement is used for indicating that the printable button can be clicked to trigger the printable operation, and the printable button not displaying the endorsement is used for indicating that the printable button cannot be clicked to trigger the printable operation.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present invention, "a plurality" means two or more unless specifically defined otherwise.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. An online document annotation authority control method is characterized by comprising the following steps:
detecting a preview operation;
acquiring authority information of all annotations in a source file corresponding to the preview operation;
determining the authority of the user for the annotation according to the identity information of the user triggering the preview operation and the authority information of the annotation;
and generating a preview interface according to the authority of the user for the annotation.
2. The method according to claim 1, wherein the obtaining of the authority information of all annotations in the source file corresponding to the preview operation includes:
and if the source file is associated with an annotation file which comprises annotation identification codes and corresponding authority information of all annotations in the source file, acquiring the annotation identification codes and the corresponding authority information of all the annotations from the annotation file.
3. The method according to claim 1, wherein the obtaining rights information of all annotations in a source file corresponding to the preview operation includes:
and one annotation file comprises an annotation identification code of an annotation and corresponding authority information, and the corresponding annotation identification code and the corresponding authority information are obtained from each annotation file when the source file is associated with the annotation file corresponding to each annotation.
4. The method according to claim 2 or 3,
the identity information of the user comprises the role of the user, and the authority information comprises the mapping relation between the role and the authority.
5. The method of claim 4, wherein determining the authority the user has for the annotation according to the identity information of the user triggering the preview operation and the authority information of the annotation comprises:
traversing the annotation identification codes of all annotations;
and inquiring the mapping relation between the role and the authority in the authority information according to the role of the user aiming at the traversed current annotation identification code, and determining the authority of the user on the annotation corresponding to the current annotation identification code.
6. The method of claim 5, wherein the generating a preview interface according to the authority the user has for the annotation comprises:
for any one annotation:
if the fact that the user does not have visible permission on the annotation is determined, the annotation is not displayed in the preview interface;
and if the user is determined to have visible authority to the annotation, displaying the annotation in the preview interface.
7. The method of claim 6, wherein determining that the user has visible rights to the annotation further comprises:
and if the user is determined to have editable and/or printable authority on the annotation, displaying the annotation in the preview interface and simultaneously displaying an editable button and/or a printable button of the annotation.
8. An online document annotation authority management and control device, comprising:
the detection module is used for detecting preview operation;
the acquisition module is used for acquiring the authority information of all annotations in the source file corresponding to the preview operation;
the matching module is used for determining the authority of the user for the annotation according to the identity information of the user triggering the preview operation and the authority information of the annotation;
a generation module; and the preview interface is generated according to the authority of the user on the annotation.
9. The apparatus according to claim 8, wherein if the source file is associated with an annotation file, the annotation file includes annotation identification codes and corresponding permission information of all annotations in the source file, the obtaining module is configured to obtain the annotation identification codes and corresponding permission information of all annotations from the annotation file;
if one annotation file comprises an annotation identification code of an annotation and corresponding authority information, and the source file is associated with the annotation file corresponding to each annotation, the obtaining module is configured to obtain the corresponding annotation identification code and the corresponding authority information from each annotation file.
10. The apparatus of claim 8,
the matching module is used for traversing the annotation identification codes of all the annotations, and for the traversed current annotation identification code, the matching module is used for inquiring the mapping relation between the role and the authority in the authority information according to the role of the user and determining the authority of the user on the annotation corresponding to the current annotation identification code;
if the fact that the user does not have visible permission on the annotation is determined, the annotation is not displayed in a preview interface generated by the generation module;
if the user is determined to have visible authority to the annotation, the annotation is displayed in a preview interface generated by the generation module;
and if the user is determined to have editable and/or printable authority on the annotation, displaying the editable button and/or printable button of the annotation in the preview interface generated by the generation module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210595505.1A CN114707182A (en) | 2022-05-30 | 2022-05-30 | Online document annotation authority control method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210595505.1A CN114707182A (en) | 2022-05-30 | 2022-05-30 | Online document annotation authority control method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114707182A true CN114707182A (en) | 2022-07-05 |
Family
ID=82176573
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210595505.1A Pending CN114707182A (en) | 2022-05-30 | 2022-05-30 | Online document annotation authority control method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114707182A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115859909A (en) * | 2023-02-23 | 2023-03-28 | 天津联想协同科技有限公司 | Method, device, server and storage medium for displaying comments of collaborative documents |
| CN116011415A (en) * | 2023-03-27 | 2023-04-25 | 天津联想协同科技有限公司 | Document annotation generation method and device, network disk and storage medium |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1731733A (en) * | 2005-09-02 | 2006-02-08 | 清华大学 | Method for model postil and operation transmission in universal type synergic communion system |
| CN1841421A (en) * | 2004-11-08 | 2006-10-04 | 国际商业机器公司 | Method and system for multi-user, multi-timed collaborative annotation |
| CN103107979A (en) * | 2011-11-10 | 2013-05-15 | 北大方正集团有限公司 | Processing method and processing device for notes of layout files |
| CN103309879A (en) * | 2012-03-12 | 2013-09-18 | 汉王科技股份有限公司 | Method and device for managing marks in WORD document |
| CN103617155A (en) * | 2013-12-13 | 2014-03-05 | 苏州利驰电子商务有限公司 | On-line commenting method and system for DWG file under WEB |
| CN104484320A (en) * | 2014-12-26 | 2015-04-01 | 语联网（武汉）信息技术有限公司 | Method and system for commenting and editing document contents |
| CN109064129A (en) * | 2018-07-19 | 2018-12-21 | 平安科技（深圳）有限公司 | Processing method, device, computer equipment and the storage medium of file endorsement information |
| US20190050420A1 (en) * | 2017-08-10 | 2019-02-14 | Microsoft Technology Licensing, Llc | Edit and share unsupported files through instantly generated preview |
| CN110290218A (en) * | 2019-07-05 | 2019-09-27 | 永中软件股份有限公司 | File annotation method and system, computer-readable medium |
| CN111008520A (en) * | 2016-12-15 | 2020-04-14 | 广州视源电子科技股份有限公司 | Annotating method and device, terminal equipment and storage medium |
| CN111177698A (en) * | 2019-12-13 | 2020-05-19 | 平安医疗健康管理股份有限公司 | Processing method and device of portal system and computer equipment |
| CN111523294A (en) * | 2020-04-23 | 2020-08-11 | 苏州云注软件技术有限公司 | PDF file-based comment separation processing method and device |
| CN113705181A (en) * | 2020-05-21 | 2021-11-26 | 永中软件股份有限公司 | Method for annotating files in browser |
-
2022
- 2022-05-30 CN CN202210595505.1A patent/CN114707182A/en active Pending
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1841421A (en) * | 2004-11-08 | 2006-10-04 | 国际商业机器公司 | Method and system for multi-user, multi-timed collaborative annotation |
| CN1731733A (en) * | 2005-09-02 | 2006-02-08 | 清华大学 | Method for model postil and operation transmission in universal type synergic communion system |
| CN103107979A (en) * | 2011-11-10 | 2013-05-15 | 北大方正集团有限公司 | Processing method and processing device for notes of layout files |
| CN103309879A (en) * | 2012-03-12 | 2013-09-18 | 汉王科技股份有限公司 | Method and device for managing marks in WORD document |
| CN103617155A (en) * | 2013-12-13 | 2014-03-05 | 苏州利驰电子商务有限公司 | On-line commenting method and system for DWG file under WEB |
| CN104484320A (en) * | 2014-12-26 | 2015-04-01 | 语联网（武汉）信息技术有限公司 | Method and system for commenting and editing document contents |
| CN111008520A (en) * | 2016-12-15 | 2020-04-14 | 广州视源电子科技股份有限公司 | Annotating method and device, terminal equipment and storage medium |
| US20190050420A1 (en) * | 2017-08-10 | 2019-02-14 | Microsoft Technology Licensing, Llc | Edit and share unsupported files through instantly generated preview |
| CN109064129A (en) * | 2018-07-19 | 2018-12-21 | 平安科技（深圳）有限公司 | Processing method, device, computer equipment and the storage medium of file endorsement information |
| CN110290218A (en) * | 2019-07-05 | 2019-09-27 | 永中软件股份有限公司 | File annotation method and system, computer-readable medium |
| CN111177698A (en) * | 2019-12-13 | 2020-05-19 | 平安医疗健康管理股份有限公司 | Processing method and device of portal system and computer equipment |
| CN111523294A (en) * | 2020-04-23 | 2020-08-11 | 苏州云注软件技术有限公司 | PDF file-based comment separation processing method and device |
| CN113705181A (en) * | 2020-05-21 | 2021-11-26 | 永中软件股份有限公司 | Method for annotating files in browser |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115859909A (en) * | 2023-02-23 | 2023-03-28 | 天津联想协同科技有限公司 | Method, device, server and storage medium for displaying comments of collaborative documents |
| CN115859909B (en) * | 2023-02-23 | 2023-10-20 | 天津联想协同科技有限公司 | Collaborative document annotation display method, collaborative document annotation display device, server and storage medium |
| CN116011415A (en) * | 2023-03-27 | 2023-04-25 | 天津联想协同科技有限公司 | Document annotation generation method and device, network disk and storage medium |
| CN116011415B (en) * | 2023-03-27 | 2023-08-04 | 天津联想协同科技有限公司 | Document annotation generation method and device, network disk and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114707182A (en) | Online document annotation authority control method and device | |
| US7958147B1 (en) | Method for providing customized and automated security assistance, a document marking regime, and central tracking and control for sensitive or classified documents in electronic format | |
| US9135312B2 (en) | Timeslider | |
| CN112134785B (en) | Information processing method, client and system in network security level protection | |
| JP5319133B2 (en) | Document management system, document management method and program | |
| US20170324691A1 (en) | Electronic mail data management systems and methods for generating a dataset for such systems | |
| US20030220838A1 (en) | Cut-list creation system, center server, advertisement creation terminals, computer programs, storage media and cut-list creation method of center server | |
| CN107408242B (en) | Providing interactive previews of content within communications | |
| JP4660341B2 (en) | Intellectual property management system, intellectual property management method and program thereof | |
| CN111090620A (en) | File storage method, device, equipment and readable storage medium | |
| CN112307145A (en) | Batch updating method, device, medium and equipment for historical map data | |
| JP2007034983A (en) | Information processor, control method thereof, computer program, computer readable storage medium and retrieval system | |
| WO2015113568A1 (en) | Construction site image management system and method | |
| JP4682549B2 (en) | Classification guidance device | |
| US20070067348A1 (en) | Repeated Segment Manager | |
| CN104268244A (en) | Method and device for processing form | |
| WO2007005607A2 (en) | Contact information managing apparatus and method | |
| US20160210468A1 (en) | Method to customize and automate a classification block for information contained in an electronic document | |
| CN114866434B (en) | Network asset security assessment method and application | |
| US20080178303A1 (en) | Information-processing apparatus, information-processing system, information-processing method, computer-readable medium, and computer data signal | |
| US20060085379A1 (en) | Automatic subscriptions to documents based on user navigation behavior | |
| CN109063175A (en) | A kind of data entry method and device | |
| JP2016051383A (en) | Document data management program, document data management method, and information processing device | |
| US20200293496A1 (en) | Information processing apparatus and non-transitory computer readable medium | |
| US10726392B2 (en) | Email file-and-refer system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220705 |
|
| RJ01 | Rejection of invention patent application after publication |