KR101075023B1 - Method for Managing history of document using Link Document and System thereof - Google Patents

Abstract

The present invention, unlike the conventional document file, a method that can manage the history of the document by using a connection document added to the header to add information that can indicate the link relationship whenever the document is modified and a system using the same The invention relates to.

Document history management system using a connection document according to the present invention for achieving the above object is a system consisting of one or more terminals connected to the server and the network, when the terminal receives a save command, the connection document to the terminal A storing module for storing the connection information and the document contents of the connection document at the same time as the storing; A import module for downloading the connection information and the document contents of the connection document from the server when an import command is received; And a display module configured to display the downloaded creation information and document content.

The server is a communication module for transmitting and receiving the creation information and document content of the connection document from the terminal; And a database module for storing the creation information and the document content.

Linked document, preparation information, document editing, latest document, history, document history

Description

Method for managing history of document using linked document and system using same {Method for Managing history of document using Link Document and System about}

The present invention, unlike the conventional document file, using a connection document that adds information that can indicate a connection relationship to the header, a method for managing the history of the document every time the document is modified and a system using the same The invention relates to.

According to the present invention, when more than one user is working while receiving one document file, the user can manage the history of the document so that the user can check the version of the document he or she is currently working with and when the document was modified by whom. The present invention relates to a history management system of a document and a method therefor.

When many people collaborate on a single document file, they send and receive these documents using e-mail attachments or storage media such as USB drivers. If the user changes the copied document file, the management is very difficult and the final document cannot be managed.

For example, suppose three people, A, B, and C, work together to produce a report. If A writes the first report and sends it to B, B adds his work here, sends the document to C, and C adds his work.

At this time, the most popular way to send and receive documents among workers is email. In other words, A attaches the document he worked on and sends it to B, and B sends the document that he worked on to C. This allows users to open and work with the document attached to the received email.

The problem is that if you work this way, you will have a document on each of A, B, and C's terminals. For convenience of explanation, it is assumed that the first document A worked on is version 1, the document B modified later on is version 2, and the last document C worked on is version 3. As a result, even though the same document has the same file name, a document of version 1 is stored in terminal A, a document of version 2 in terminal B, and a document of version 3 in terminal C.

Then, if A wants to revise the document again, he needs to request and receive a version 3 document from C and work on it. If A opens the document on his terminal and then works, the modifications of B and C are not reflected at all.

As a result, each user has to work with the latest version of the work, which is not easy if the document is moved between multiple collaborators and there are many copies.

Therefore, when a document is modified by several users, a method of managing the history of the document is needed.

The present invention has been made to solve the above problems, and the object of the present invention is that even if a number of copies are generated by various people sending and receiving documents through an attachment of an e-mail, a storage medium such as a USB memory, and any other means. The present invention provides a system and method for managing the change history history of such a document.

It also provides the user with the ability to view the full history of the copy document he received, to see what other participants are doing, to check which version of the file I have, or to restore a previous version. .

Document history management system using a connection document according to the present invention for achieving the above object is a system consisting of one or more terminals connected to the server and the network, when the terminal receives a save command, the connection document to the terminal A storing module for storing the connection information and the document contents of the connection document at the same time as the storing; A import module for downloading the connection information and the document contents of the connection document from the server when an import command is received; And a display module configured to display the downloaded creation information and document content.

The server is a communication module for transmitting and receiving the creation information and document content of the connection document from the terminal; And a database module for storing the creation information and document contents. .

The display module lists and displays the downloaded creation information, and further includes a function selected for any one of the creation information.

The display module further includes a function of listing and downloading the downloaded writing history, and selecting any version from the writing history.

Preferably, the retrieval module downloads and retrieves document contents corresponding to the selected creation information.

In addition, the storing module further includes a function for receiving whether to save in the form of a connection document when receiving a save command, and, if received in the form of a connection document, uploading the creation information and document content to the server, In other cases, it is desirable to store only in the terminal.

In addition, when the network connection with the server is not possible, the retrieval module preferably retrieves the document contents from the connection document file itself in the terminal.

In addition, the database module checks whether the connection document is pre-stored when the creation information and the document content of the connection document are received, and stores all the document contents when the connection document is not already stored. It is advisable to save only the changes.

The preparation information preferably includes a document ID generated one by one for each linked document and a version ID newly generated each time the storage is performed.

In addition, the connection document header unit that includes the document ID and address information of the server; And a content unit in which the contents of the document are stored.

The creation information may further include an author ID indicating a terminal storing the document, a modification date indicating the time of storing the document, and a previous LINK indicating the previous document before storage.

It is also preferable that the display module graphically displays whether the document is modified by whom and at what time by using the author ID, modification date, and previous LINK included in the creation information.

The storing module further includes a function of encrypting before uploading to the server, and the retrieving module further includes a function of decrypting after downloading from the server.

On the other hand, a terminal capable of document history management using a linked document according to another embodiment of the present invention, in a terminal capable of editing a document, receives a command to store a document, and stores the connected document in the terminal and at the same time through a network. A storage module for uploading creation information and document contents of the connection document to a server; A import module for downloading the connection information and the document contents of the connection document from the server when an import command is received; And a display module configured to display the downloaded creation information and document content.

On the other hand, a server for enabling document history management using a connection document according to another embodiment of the present invention includes a communication module for transmitting and receiving information on the connection document from an external terminal; And a database module for storing the creation information and the document content.

On the other hand, a document history management method using a link document according to another embodiment of the present invention in a system consisting of a plurality of user terminals connected to a server and a network, after creating a document file in the terminal after creating a document file and a storage command from the user A document creation step of uploading the creation information and the created document contents to the server when the input is received; A document display step of downloading the creation information and the document contents of the document from the server and displaying the creation information and the document contents when the terminal receives the open command of the document file; And a document modification step of uploading the correction information and the modified document contents to the server when the terminal receives the storage command from the user after modifying the document file.

And selecting, by the terminal, one of the pieces of writing information among the downloaded pieces of writing information; And downloading a document content corresponding to the selected creation information.

In addition, when storing the connection document, further comprising the step of receiving whether to save in the form of the connection document, if received in the form of the connection document uploads the information and document content to the server, otherwise the terminal only It is desirable to store.

In the storing step, the server checks whether the connection document is pre-stored. If not, the server stores all of the document contents.

In addition, the connection document header unit that includes the document ID and address information of the server; And a content unit in which the contents of the document are stored.

The creation information may further include an author ID indicating a terminal storing the document, a modification date indicating the time of storing the document, and a previous LINK indicating the previous document before storage.

The method may further include graphically displaying whether the document is modified by whom and at what time by using the author ID, the modification date, and the previous LINK included in the creation information.

On the other hand, the computer-readable recording medium according to the present invention, when receiving a storage command, and stores the connection document in the terminal and at the same time uploads the information and the document content of the connection document to the server, , When receiving a load command, performs a function of downloading the creation information and document content of the connection document from a server from an external network based on the header information included in the connection document, and downloading the created information and document content. The program that performs the function of displaying is recorded.

As described above, by using the system or method of the present invention, even if multiple documents are exchanged by multiple people, the change history history of the corresponding document can be managed.

It also allows the user to see the full history of the copy document they received, to see what other participants are doing, to see which version of the file I have, or to restore a previous version.

Hereinafter, with reference to the drawings will be described the present invention in more detail.

1 is a diagram illustrating a system in a general network including a plurality of terminals and servers.

As shown in FIG. 1, a case in which a document is stored in the terminal A 110, the document thus created is stored in the USB memory 140, and copied to the terminal B 120 is described as an example.

In this case, when the button for storing the document is pressed in the terminal A 110, the document is stored in the terminal A, and the document creation information and the document content are also uploaded to the server 130. On the other hand, the document file stored in the terminal A includes a content unit in which the document content is stored, and a header unit including a document ID, a version ID, and a server address.

Hereinafter, the document will be referred to as a link document. Copy the link document stored in terminal A to the USB device and transfer it to terminal B again. Of course, not only can it be transmitted through a storage medium such as USB, but also can be copied and transmitted by email or any other means.

When the link document is called by the B terminal 120 which has received the link document, the server 130 is first connected to the server 130 using the address of the server included in the header of the link document. And history information of this document is read using document ID and version ID included in header part. Such history information is information accumulated by the created information uploaded when stored in the terminal A (110).

Through this, the terminal B knows that the link document was previously created by the terminal A.

This process will be described in detail later with reference to FIG. 2.

2 is a flowchart illustrating a document history management method using a link document according to an embodiment of the present invention.

First, a document is created in the A terminal 110 (S210). Thereafter, the stored document is stored in the terminal A 110 (S220). When performing the save, the user is asked whether to set as a link document (S230). If it is not set as a link document (S230-N), then the document is used as a document we usually use, and if it is set as a link document (S230-Y), the document is uploaded to the server (S235). At this time, upload the written information as well as the document contents. The server 130 manages the uploaded creation information and document content as a database. Here, all of the document contents may be managed by the server, or only the version in which the document is first created may be stored in the entire document, and thereafter, only the changed part of the document may be stored.

Meanwhile, an embodiment of the link document is shown in FIG. 3. As shown in Fig. 3, a header portion exists separately from the document contents, and includes the document ID, the version ID, and the server location URL information. Through this header part information, other users can later use the document as a link document.

Here, the creation information is a basic information for storing a history when the document is created in the terminal A 110, for example, a document ID specifying the document, an author ID indicating a created terminal (or creator), and a storage time point. The date of modification is included.

The document ID is assigned to each document. The document ID is assigned when the first document is created and is maintained even if it is continuously modified. If the document is modified, the document ID existing in the header of the link document may be used as it is. If the document is newly generated, the terminal may generate a new document ID and upload it to the server. Alternatively, when the terminal uploads the information indicating that the document is newly generated to the server, the server may assign a new document ID to the server, and the terminal may receive this information and write it in the link document.

In addition, the creator ID refers to information that can be used to know who has been modified or newly created by utilizing the pre-stored ID for each terminal.

Returning to Figure 2 again, handing over the document stored in terminal A 110 to terminal B 120. As mentioned above, the present invention may be applied in any way.

Thereafter, the B terminal 120 loads (opens) the received document. In this case, the B terminal 120 refers to the address of the server in the header of the document, accesses the corresponding server, and downloads necessary information belonging to the document ID of the document (S250).

Then you can see the document ID, ie how and when the document was modified. In this case, the user may view the history of the document as graphic contents, which will be described later in detail with reference to FIGS. 4A and 4B.

If the B terminal 120 modifies the document (S255), the B terminal 120 determines whether the document is a linked document (S260). If the document is set as the link document in the terminal A at the time of initial writing (S230-Y), the document is the current link document (S260-Y), and thus, the step of uploading to the server is performed similarly to step S235 described above (S265). ).

Of course, it is also possible for the user of the terminal B 120 to convert the linked document into a general document as needed, in which case it is stored only inside the terminal B 120.

On the other hand, in the present embodiment, for example, each terminal sets the link document at the time of creating and storing the first document, but this is only one embodiment. According to the intention of the system implementer, it is possible for a user to set the document as a link document or a general document by using an option or the like when creating a document.

In addition, in the present embodiment, it has been described that the document is uploaded to the server after determining whether the document is set as a link document at the time of storing the document, but this is also only an embodiment. Therefore, not only when saving, but also when the application is terminated or uploaded to the server at a certain interval, it is of course possible.

4A is an example of creation information stored in a server according to an embodiment of the present invention.

The content of FIG. 4a shows a case in which a document named aa is first created by a terminal named AA (or a user named AA) on August 5, 2008, and then modified while working with people named BB and CC.

FIG. 4B is an example of a graphic screen showing history information of the document, that is, the linked document, when a user who receives a document last modified by CC on September 4, 2008 is called through the terminal.

In the case of the link document, which is a link document modified by the CC on September 4, 2008, the header part includes information such as document ID aa, version ID 04, and creator ID CC.

In this case, when the document is retrieved, the terminal first retrieves all the information whose document ID is aa, downloads it, and displays it graphically as shown in FIG. 4B.

As shown in FIG. 4B, the user corresponds to the user ID after the file he received is managed by another user, that is, BB (the ID may be displayed directly, or the user name and database corresponding to the ID are separately managed). It is also possible to display the name of the lamp.) You can see the newly revised on September 6, 2008. Therefore, instead of directly editing the document that he received, the user clicks 05 and then downloads the new version of the new work done by BB on September 6, 2008 to work with this document. It may be.

FIG. 5A illustrates a case in which AA is newly modified on September 10, 2008 in document No. 05, that is, September 6, 2008 after 4b.

The previous link field is used to indicate in which document this link document has been modified. Therefore, in 5a, the document revised by AA on September 10, 2008 was modified from information 05, which was modified by BB on September 6, 2008. If in the description of Figure 4b, the user just clicked 05 and did not work as the final version, the previous link field was recorded as 04 instead of 05, and in Figure 5b described below, Figure 06 was connected with 04. will be.

FIG. 5B is a screen when the server creates and opens a file modified on September 4 by the CC, not the final version, in the same situation as in FIG. 5A. Thus, the user can see that the linked document is not the final version but the document edited on September 4th, and has been modified twice since. Therefore, the user can click the most recent version to download it and create a document, and of course, the previous version can be downloaded and written.

 While the above has been shown and described with respect to preferred embodiments of the present invention, the present invention is not limited to the specific embodiments described above, it is usually in the technical field to which the invention belongs without departing from the spirit of the invention claimed in the claims. Various modifications can be made by those skilled in the art, and these modifications should not be individually understood from the technical spirit or the prospect of the present invention.

1 is a diagram showing a state of a system on a network for explaining the present invention.

2 is a flowchart illustrating a document history management method using a link document according to an embodiment of the present invention;

3 is a view showing the structure of a link document according to an embodiment of the present invention;

4A and 4B illustrate screens of creation information stored in a server and history information displayed on a terminal according to an embodiment of the present invention;

5A and 5B are diagrams illustrating screens of creation information and history information when the modifications are made once more in FIGS. 4A and 4B.

Claims (20)

In the system consisting of a terminal capable of editing one or more documents connected to the network by the server, The terminal is A storing module for storing the document in the form of a connection document in the terminal, and uploading the creation information and the document content of the connection document to the server; A retrieval module for determining whether the document is in the form of a connection document when receiving a document retrieval command, and downloading information and document contents of the connection document from the server when the document is in the form of a connection document; And And a display module configured to display the downloaded creation information and document content. The server is Communication module for transmitting and receiving the creation information and document content of the connection document from the terminal; And And a database module for storing the creation information and document contents. The display module And listing and displaying the downloaded creation information, and selecting any one of the creation information. The import module Document history management system using a connection document, characterized in that for downloading and retrieving the document content corresponding to the selected creation information. delete The method of claim 1, The saving module Determine whether the document is set as a linked document, The document history management system using the linked document, wherein the function of uploading the creation information and the document contents of the linked document to the server is performed when the document is set as the linked document. The method of claim 1, The import module If network connection with the server is not possible, Document history management system using a connection document, characterized in that the document content is retrieved from the connection document file itself in the terminal. The method of claim 1, The database module When the information and content of the linked documents are received, After checking whether the linked document is already stored, If not already saved, save the entire document. Document history management system using a linked document, characterized in that if the previously stored only the changes in the document content. The method of claim 1, The filling information is Document history management system using a linked document, characterized in that it comprises a document ID is generated one by one for each linked document and a version ID newly generated each time the storage is performed. The method of claim 6, The linked document is A header unit including the document ID and address information of the server; And Document history management system using a connection document comprising a; content unit for storing the content of the document. The method of claim 6, In the above preparation information A document history management system using a linked document, characterized in that it further comprises an author ID indicating the terminal storing the document, a modification date indicating the time when the document is stored, and a previous LINK indicating the previous document before storing. The method of claim 8, The display module Included in the above written information By using author ID, date modified, and previous LINK And documenting whether the document is modified by whom and at what time. The method of claim 1, The saving module And further encrypting before uploading to the server, The import module Document history management system using a connection document, characterized in that it further comprises a function for decrypting after downloading from the server. In a terminal that can edit documents, A storing module for storing a document in the form of a connection document and uploading information and content of the connection document to an external server through a network; And A retrieval module for downloading the connection information and the document content of the connected document from the server when a document retrieval command is received; And And a display module configured to display the downloaded creation information and document content. The display module And listing and displaying the downloaded creation information, and selecting any one of the creation information. The import module And a document content corresponding to the selected creation information is downloaded and retrieved. delete In a system consisting of a plurality of user terminals connected to a server and a network, A local storage step of storing, by the terminal, a document in the terminal when the terminal receives a command to store a document; A connection document setting step of setting, by the terminal, the document in the form of a connection document; A document creation step of uploading, by the terminal, creation information of the connection document and contents of the created document to a server; When the terminal receives a document import command, when the document is in the form of a linked document, the terminal downloads the creation information and document content of the connection document from the server, and displays the document information and display the document content step; And And a document modification step of modifying the downloaded connection document by the terminal, storing the connection document in the terminal, and uploading creation information and document contents of the connection document to a server. Selecting, by the terminal, any one of the downloaded creation information; And The document history management method using the link document, characterized in that it further comprises the step of downloading the document content corresponding to the selected creation information. delete The method of claim 13, The document editing step Further comprising a linked document determination step of determining whether the linked document is a linked document type, Uploading the creation information and the document content of the linked document to the server is a document history management method using a linked document, characterized in that is performed when the linked document is determined in the form of a linked document in the connection document determination step. The method of claim 13, The step of storing by the server After checking whether the linked document is already stored, If not already saved, save the entire document. If the document is already stored, the document history management method using a linked document, characterized in that only changes are stored among the document contents. The method of claim 13, The linked document is A header unit including document IDs and server address information, which are generated one by one for each connection document; And Document history management method using a linked document comprising a; content unit for storing the content of the document. The method of claim 17, In the above preparation information A document history management method using a linked document further comprising a creator ID indicating a terminal storing a document, a modification date indicating a time of storing the document, and a previous link indicating a previous document before storing. The method of claim 18, Included in the above written information By using author ID, date modified, and previous LINK And displaying graphically whether the linked document is modified by whom at any point in time. delete

Images