JP2000339299A - Document managing device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a document managing device capable of adding a marker or note to an electronic document on a server without affecting another user. SOLUTION: Concerning the document managing device having a server part 112 and a terminal part 101 connected on a network 111, the terminal part is provided with a display part 102 for document reference, an input part 103 for inputting a user ID or document ID, a user ID holding part 104 for holding the user ID, which is inputted by a user at the time of log-in, until log-out, a document data holding part 106 for holding the text data of a document, an attached information holding part 107 for holding the link information of the marker or note personally attached to the document, a compound data holding part 105 for holding compound data reflecting the text data of the document with the link information, a version number holding part 108 for holding the version number of the document and a terminal control part 110. Thus, since the shared document can be managed separately from the personal marker or note, the other user is not affected at all in the case of referring to the shared document.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a document management apparatus for managing an electronic document, and more particularly to a document management apparatus for individually managing a marker, a memo, and the like added by a user to the electronic document. .

[0002]

2. Description of the Related Art In recent years, PCs have penetrated offices, and with the spread of the Internet and intranets, electronic documents managed by a server have been connected to a network connected to a PC.
System software such as groupware that is shared, referenced, and reused by C terminals is used.

Conventionally, like a marker or memo added to a paper document, a character string in an electronic document can be marked with a marker or a text can be added as a memo to an electronic document. There is a document management device provided with reference software.

In this conventional electronic document editing / referencing software, added markers and memo data are embedded and managed in an electronic document to be added.

[0005]

However, in this conventional document management apparatus, markers and memo data are embedded in the electronic document. Therefore, when the electronic document is shared on a network, another user adds the data. When a marker or a memo is displayed or a large number of users add a marker or a memo, there is a possibility that the data size of the electronic document itself is enlarged and a trouble occurs in network transfer.

The present invention solves such a conventional problem, and adds a marker and a memo to an electronic document shared on a server via a network without affecting other users. It is an object of the present invention to provide a document management apparatus capable of performing the above-mentioned operations.

[0007]

Therefore, according to the present invention, in a document management apparatus having a server unit and a terminal unit connected by a network, a terminal unit has a display unit for document reference, a user ID and a password. Input unit for inputting a document ID of a document to be referred to, a user ID storage unit for storing a user ID input by a user at the time of login until the user logs out, and a document data storage unit for storing text data of the document And an attached information holding unit that holds link information of markers and memos that are individually attached to the document, a compound data holding unit that holds compound data reflecting the link information in the text data of the document, and a display unit. A version number holding unit for holding a version number of a document in the terminal, a terminal I / O unit for performing I / O with a network, and a terminal control unit for controlling processing of the terminal unit A is provided.

[0008] Further, the server unit has an I / O with the network.
/ O server I / O unit, user ID / password storage unit for storing a set of user ID and password of a user who can use this apparatus, and document data storage unit for storing registered document data as text A link information storage unit for storing information relating a marker or a memo personally attached by the user to the document stored in the document data storage unit; and a content of the marker or memo individually attached to the document by the user. And a server control unit for controlling processing in the server unit.

Therefore, the shared document text and the personal markers and memos can be managed separately, and even if the markers and memos are individually added to the shared document, the shared document can be managed by other users. Has no effect when referencing.

[0010]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS According to a first aspect of the present invention, in a document management apparatus having a server unit and a terminal unit connected by a network, a terminal unit has a display unit for referring to a document, An input unit for inputting a set of a user ID and a password, a document ID of a document to be referred to, a user ID holding unit for holding a user ID input by a user at the time of login until the user logs out, and holding text data of the document A document data holding unit, an attached information holding unit for holding link information of a marker or a memo individually attached to the document, and a compound data holding unit for holding compound data in which link information is reflected in text data of the document; A version number holding unit for holding a version number of the document being displayed on the display unit, a terminal I / O unit for performing I / O with the network, and a terminal system for controlling processing of the terminal unit Are those provided with parts, can be given personally markers and notes for a shared document, even such a case, no influence at all when other users to see shared document.

According to a second aspect of the present invention, a server I / O section for performing I / O with a network and a user ID for storing a set of a user ID and a password of a user who can use the apparatus are provided in the server section. / Password storage unit, a document data storage unit that stores registered document data in text, and link information that stores information that associates a marker or a memo personally attached by a user to a document stored in the document data storage unit. It is provided with a storage unit, an attached information storage unit for storing the contents of a marker or a memo personally attached to the document by the user, and a server control unit for controlling processing in the server unit. The document actual text and personal markers and memos can be managed separately.

According to a third aspect of the present invention, in the link information storage unit, a user ID table having a user ID as an element, a start position and an end position indicating a position where a marker or a memo is attached to a document, corresponding to each document. A server control unit stores a position, a version of a document, and a link table each of which is an element of a link ID, and the server control unit operates the data of the user ID table and the link table. It is possible to search for a marker or a memo related to the user who made the search.

According to a fourth aspect of the present invention, the link information storage unit stores, in correspondence with each document, a user ID, a start position and an end position indicating a position where a marker or a memo is attached to the document, a document version, and a link. A link table having each ID as an element is stored, and the server control unit operates data of the link table.
Markers and memos can be attached without limitation.

According to a fifth aspect of the present invention, a link information storage unit stores a user ID having a link value to one or a plurality of rows of a link table described later and a user ID corresponding to each document as elements. A table and a link table having a start position and an end position indicating a position where a marker or a memo is attached to the document, a version of the document, and a link ID as elements are stored, and the server control unit stores the user ID table and the link. The table data is manipulated. Many markers and memos can be attached to each document, and link information can be extracted at high speed.

According to a sixth aspect of the present invention, a link information storage unit stores a user ID table having a link value to one row of a link table described later and a user ID as elements corresponding to each document. , A start position and an end position indicating a position where a marker or a memo is attached to a document, a version of the document, a link ID, and a link table having elements of a value indicating a line to be positioned next as elements. But this user I
The data in the D table and the link table are manipulated. Markers and memos can be attached to each document without limitation, and link information can be extracted at high speed.

According to a seventh aspect of the present invention, the server control section searches information stored in the link information storage section to detect a document to which a specific marker or memo is attached and its attached position. It is possible to designate a marker or a memo, and present a document to which the marker or the memo is attached or an attached portion thereof.

According to the invention described in claim 8, the document data storage unit holds text data of different versions of the document, and the server control unit searches the information stored in the link information storage unit and specifies the specified data. A marker or a memo attached by a user designated to a designated version of the document is detected, and the document data can be managed by the version. According to a ninth aspect of the present invention, the server control unit searches the information stored in the link information storage unit and relates to the attachment positions of all markers or memos attached to the specified version of the specified document. The information is extracted, the terminal unit edits the version of the document data, re-detects the attachment positions of all markers or memos at the end of the editing, and the server control unit stores the re-detected attachment positions in the link information storage unit. In this case, even if the position of a marker or a memo attached so far is shifted, the attached position can be updated.

According to a tenth aspect of the present invention, the attached information storage unit is omitted, and the link information storage unit stores
A user ID table having a user ID as an element, a start position and an end position indicating a position where a marker or memo is attached to a document, a document version, a link ID, a marker or memo type,
And a link table having each of the contents of the marker or the memo as an element, and the server control unit operates data of the user ID table and the link table.
Since it is not necessary to follow the link of the data to obtain the contents of the marker or the memo, the attached information can be quickly presented.

According to an eleventh aspect of the present invention, the terminal control unit responds to the user's addition or deletion of a marker or memo, a change in the attachment position, or a correction of the marker color or the substantive text.
The information stored in the attached information storage unit or the composite data stored in the composite data storage unit is sequentially changed. The user can add a marker or memo while referring to the document on the display unit of the terminal. Can be modified, deleted, etc.

According to a twelfth aspect of the present invention, the server control unit searches the attached information storage unit and specifies the designated user ID.
A marker or memo corresponding to the document data is extracted, and a marker or a memo attached by the user to the document data can be obtained.

According to a thirteenth aspect of the present invention, the server control unit searches the link information storage unit of the tenth aspect and extracts a marker or a memo corresponding to the designated user ID. Since the link table stored in the link information storage unit includes the type of the marker or the memo and the contents of the marker or the memo as elements, the marker or the memo corresponding to the user ID can be extracted.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.

(First Embodiment) As shown in FIG. 1, a document management apparatus according to an embodiment includes a terminal unit 101 and a server unit 112 connected by a network unit 111.

A terminal unit 101 includes a display unit 102 for referring to a document.
An input unit 103 for inputting a set of a user ID and a password at the time of login and a document ID of a document to be referred to; a user ID holding unit 104 for holding a user ID of a logged-in user until logout of the user; A document data holding unit 106 for holding text data, an attached information holding unit 107 for holding link information of a marker or a memo individually added to the document, and a data in which the link information is reflected in the text data of the document. A composite data holding unit 105 for holding, a version number holding unit 108 for holding a version number of the document being displayed on the display unit 102, a terminal I / O unit 109 for performing I / O with the network unit 111, and a terminal unit A terminal control unit 110 for controlling the processing in 101 is provided.

The server unit 112 includes a network unit 111
A server I / O unit 113 for performing I / O with the user, a user ID / password storage unit 114 for storing a set of a user ID and a password of a user who can use the present apparatus, and text data registered in the present apparatus as text. And an attached information storage unit 117 for storing the contents of a marker or a memo personally added to the document by the user.
A link information storage unit 116 for storing information relating a marker or a memo stored in the attached information storage unit 117 to a document stored in the document data storage unit 115;
And a server control unit 118 for controlling the processing in.

An example of the operation of the document management apparatus configured as described above will be described.

Prior to use, the user first inputs a set of a user ID and a password to the input unit 103. The terminal control unit 110, which has detected the input of the user ID and the password to the input unit 103, receives the user ID and the password from the input unit 103, and sends them to the server unit 112 through the terminal I / O unit 109 and the network unit 111. Send. Server section 112
Then, the set of the user ID and the password is stored in the server I /
The server control unit 118 receives the user ID and password at the server I / O unit 113, and receives the user ID and password stored in the user ID / password storage unit 114 in advance. Check if there is a match in the password pair.

FIG. 2 shows data stored in the user ID / password storage unit 114 of the first embodiment. If there is a match, the server control unit 118 determines that the user who has input the user ID and password to the input unit 103 of the terminal unit 101 is a user who can use the present apparatus, and the server I / O unit 113 and the network The device use permission information is sent through the unit 111.

In the terminal unit 101, the information of the device use permission is received by the terminal I / O unit 109, and subsequently, the terminal control unit 110, which detects the reception of the device use permission information, inputs the information to the input unit 103 by the user. The user ID is stored in the user ID holding unit 104.

The user permitted to use the apparatus as described above inputs the document ID and the version number of the document to be subsequently referred to into the input unit 103. The terminal control unit 110 transmits the document I
When the input of D and the version number is detected, the input version number is stored in the version number holding unit 108, and the user ID stored in the user ID holding unit 104, the document ID, and the version number are grouped. , To the server unit 112 via the terminal I / O unit 109 and the network unit 111.

Upon detecting the user ID, the document ID, and the version number via the server I / O unit 113, the server control unit 118 stores the document data indicated by the document ID and the version number from the document data storage unit 115, The link information indicated by the user ID and the version number corresponding to the document indicated by the document ID is acquired from the link information storage unit 116.

FIG. 3 is a diagram showing data held by the document data storage unit 115 according to the first embodiment. As shown in FIG. 3, since the text data as the document entity is stored as a set with the document ID and the version number, an entry that matches the set of the document ID and the version number received by the server I / O unit 113 is detected. By doing so, the text data of the document can be obtained.

According to such a procedure, the server control unit 118 stores the document data indicated by the document ID and the version number in the document data storage unit 11
Explore and get 5

FIG. 4 is a diagram showing data held by the link information storage unit 116 according to the first embodiment. In the link information storage unit 116, a set of a user ID table and a link table is created for each document ID stored in the document data storage unit 115. This user ID table stores the user ID of the user who has individually added a marker or a memo to the corresponding document. In the first embodiment, the upper limit of the total number of markers and memos that can be added to a document by a user is defined as N. Each time a new user ID is added to the end of the user ID table, an empty area consisting of N lines is added to the end of the link table, and the area is kept until the user no longer adds a personal marker or memo to the document. , And is used as an area dedicated to the user. As described above, the block consisting of N rows in the link table and the user in the user ID table have a one-to-one correspondence.

The subsequent rows are represented by offsets from the first row of the link table, and the offset is represented by “L offset (≧
0) ”, and the subsequent rows are represented by offsets from the first row of the user ID table. When the offset is referred to as“ U offset (≧ 0) ”, the offset is located at the position of the U offset in the user ID table. The link information of a certain user is stored from a row in the link table indicated by “L offset = N * U offset” to a maximum of N rows.

In the link table, the leading character position of the partial character string in the document data designated by the user as a marker or memo addition destination is “start position” (≧ 1), and the end character position is “end position” (≧ 1). ≧ 1), the version number of the document in which the link information is set is stored as “version”, and the ID for distinguishing the link information across different versions of the document is stored as “link ID”. .

As shown in FIG. 5, information on a marker and a memo is stored in the attached information
D, and stored in combination with the link ID. In the figure, "type" indicates the type of the attached information as a marker or a memo, and "entity" indicates the color if the "type" of the line is a marker, and indicates the actual text if the memo is a memo. ing. In response to the above information, the server control unit 118
User ID based on document ID obtained from / O unit 113
One set of a table and a link table is determined, and from this set of determined tables, the version number obtained from the server I / O unit 113, the link information corresponding to the user ID, and the L offset value thereof are obtained. The attached information indicated by the link ID of the link information is acquired from the attached information storage unit 117.

In this way, the server control unit 118
When the document data corresponding to the document ID and the version number, the link information corresponding to the document ID, the version number and the user ID, the L offset value and the attached information are acquired, these are acquired by the server I / O
It is sent to the terminal unit 101 through the O unit 113 and the network unit 111.

Upon detecting the arrival of the information at the terminal I / O unit 109, the terminal control unit 110 stores the document data in the document data holding unit 106 in combination with the document ID as shown in FIG. Also, the link information, its L offset value, and the attached information are stored in the attached information holding unit 107 in the data format shown in FIG. In FIG. 7, the user ID is pana
9 shows an example of the attached information when the user logs in by using.

Subsequently, the terminal control unit 110 converts the data held in the document data holding unit 106 and the data held in the attached information holding unit 107 into data obtained by inserting the attached data into the actual document as shown in FIG. (Hereafter referred to as "composite data")
Is created and stored in the composite data holding unit 105.

This composite data is created as follows.
In the attached information in FIG. 7, a blue marker is added from the second character to the third character in the link information of L0001.
The link information indicates that a memo is added from the fifth character to the seventh character. In the text stored in the document data holding unit 106, the character string corresponding to the marker addition position is “say”, and the memo addition position is “okaki”. The terminal control unit 110 includes the document data holding unit 106
By applying the information held by the attached information holding unit 107 to the text held by, the two link source character strings are detected, and these character strings are surrounded by a start mark character "(" and a end mark character ")". For the start mark character and the end mark character, composite data is created with the corresponding L offset value, and stored in the composite data holding unit 105.

Subsequently, the terminal control unit 110 creates image data for screen display on the display unit 102 based on the composite data held by the composite data holding unit 105, and presents it to the user via the display unit 102. . At this time, the terminal control unit 110 does not include the start and end mark characters in the display data. FIG.
FIG. 9 is a view showing a document displayed on the display unit 102 when the document is referred to.
A blue rectangle that is visually recognized as a blue marker is displayed at the part of the character string “say” specified as the marker attachment part,
The character string "okaki" designated as the memo attachment portion is a notation in which the color of the character is changed and the character string is underlined to notify the user that the memo is added.

When the user clicks the memo attachment location, display unit 102 informs terminal control unit 109 of the L offset value corresponding to the clicked character string. Upon receiving the L offset value, the terminal control unit 110
The line corresponding to this L offset value is detected from the information held in the memo, and the memo entity text held in the “attached data” of the line is acquired, and this is displayed on the display unit 102 as shown in FIG. Display as memo information above.

Subsequently, the user designates a marker or a memo displayed on the display unit 102, and inputs a request for referring to the relevant part in the same document or another document to which the designated marker or memo is added. When input to the terminal 103, the terminal control unit 110 detects this, and the “L offset value” of the designated memo, the “document ID” held in the document data holding unit 106, and “reference to other link locations” Request ”through the terminal I / O unit 109 and the network unit 111.
Send to 2.

Upon detecting the reception of the “L offset value”, “document ID”, and “other link location reference request” to server I / O section 113, server control section 118 detects link information storage section 1
In the link table corresponding to the 16 document IDs, the line indicated by the L offset value is detected to acquire the link ID, and then all the link tables in the link information storage unit 116 are searched to find the same as the link ID. A link table including the link IDs of the documents and a group of the document IDs corresponding to the link table, the corresponding line and the L offset value thereof are obtained, and further, the start character position and the end character position which are the link positions in each document And the “group of document IDs”, the “group of L offset values for each document ID”, and the “group of link locations corresponding to the rows of the L offset values” are stored in the server I / O unit 113 and the network unit 111. To the terminal unit 101 through

The terminal I / O unit 109 executes the “group of document IDs”
“Group of L offset values for each document ID” and “This L
When receiving the “group of link locations corresponding to the row of the offset value”, the terminal control unit 110 that has detected the
Display at 02. In this way, a reference location in the same document or another document that refers to the memo specified by the user can be presented to the user.

After the authentication of the use of the apparatus by inputting the user ID and the password, the user can also obtain a list of memos created by the user. In this case, after authentication, the user inputs a reference request for the created memo list to the input unit 103. When detecting the input of the memo list reference request, the terminal control unit 110 transmits the user ID and the memo list reference request stored in the user ID holding unit 104 to the server via the terminal I / O unit 109 and the network unit 111. It is sent to the unit 112.

When the server control unit 118 detects that the server I / O unit 113 has received the user ID and the memo list reference request, the server control unit 118 stores the user ID and the memo list from the memo data of the attached information storage unit 117 in a pair with the user ID. Group of memo entity texts
The information is obtained by distinguishing it from the marker using the “type” in the table, and transmitted to the terminal unit 101 via the server I / O unit 113 and the network unit 111.

Terminal control unit 11 which has detected that terminal I / O unit 109 has received a group of memo entity texts from server unit 112
0 displays this group of memo entity texts on the display unit 102. In this way, the user can see a list of notes created by him.

Further, the user can newly add a marker or memo information to the document being displayed on the display unit 102. When the user specifies a character string to add a marker through the input unit 103 as shown in FIG.
Updates the content of the composite data holding unit 105 to the content shown in FIG. The updating of the content of the composite data by the terminal control unit 110 is sequentially performed in response to the addition or deletion of the marker or the memo by the user, or the change of the position of the attachment destination.

Since the L offset value is not yet determined for the green marker for the character string “Keko” added this time, the character “X” is included in the composite data instead of the character string indicating the L offset value. ". The terminal control unit 110 also performs, as shown in FIG.
With the same change as above, the character "X" is added to the L offset value.
Is added.

Subsequently, the user inputs the current memo,
When a request to save the marker status is input, the terminal control unit
110 detects this and stores “all data stored in the attached information storage unit 107”, “document ID” stored in the document data storage unit 106, and “user ID storage unit 104”. The “user ID” and the “version number” held in the version number holding unit 108 are paired, and these are set to the terminal I / O unit 10.
9 and to the server unit 112 via the network unit 111.

When the server I / O unit 113 receives the set of information, the server control unit 118 which has detected the set of information receives the information of each row indicated by the L offset value held in the attached information holding unit 107, and The contents of the corresponding row of the link table corresponding to the document ID stored in the link information storage unit 116 are compared.

The contents of each element of the line are equal, and the contents of each element of the line in the attached information storage unit 117 indicated by the link ID of the line are equal to the corresponding line of the information held in the attached information holding unit 107. It is assumed that there is no change from the already registered contents, and if a difference is detected, the information held in the attached information holding unit 107 is reflected as the changed contents. Further, the line of the information held in the attached information holding unit 107 that includes the character “X” in the L offset value is determined to be the marker or memo added by the user of the received user ID this time, and the document ID is A line that does not hold valid contents, such as being cleared from a block consisting of a maximum of N lines corresponding to the user ID in the link table to be pointed out, is detected, and the line is held in the attached information holding unit 107. In the information line, the contents of the line including the character "X" in the L offset value are reflected, and an unused link ID is given by the server unit 112 instead of the "X". Further, the information of “type” and “attached data” of the line of the information held in the attached information holding unit 107 is stored in the attached information storage unit 117 in combination with the link ID and the user ID.

The unused link ID is stored in the link information storage unit.
It can be easily obtained by searching the attached information storage unit 117 that manages the attached data of all the links existing in the 116.
FIG. 13 is a diagram of the edited data held by the link information storage unit 116 according to the first embodiment. The row where the L offset value is “X” in FIG.
L0003, which has not been used in step 6, is added and stored in the link table.

Subsequently, the server control unit 118 determines the “version” of the link table indicated by the document ID received from the terminal unit 101 from the maximum N rows corresponding to the user ID received from the terminal unit 101. A line equal to the version number received from the unit 101 is extracted, and it is searched whether the line having the L offset value of the line is included in the information held in the attached information holding unit 107 received from the terminal unit 101. . If a line that is not included is detected, the link is assumed to have been deleted by the user this time, and the “version” of the line is the same as the version number received from the terminal unit 101, and only the version number is the “version”. Is deleted from the link information storage unit 116. If "version" contains multiple version numbers,
The version number received from the terminal unit 101 is deleted from the plurality of version numbers, and the line is not deleted. Note that the case where a plurality of version numbers are stored in the “version” means that the link ID is referred to by a different version of the document indicating the link table.

FIG. 14 shows a link L0007 of the user ID “tsuru” held by the link information storage unit 116 of the first embodiment.
It is a figure of the data after deleting. When a row is deleted, all the valid contents of each element held by the row are cleared, and the row becomes a reusable row when a link is added next time.

"All data stored in the attached information storage unit 107" sent to the server I / O unit 113
In the set of “document ID”, “user ID”, and “version number”, “all data held in the attached information holding unit 107” may not have a valid element. This is a case where the user does not attach any marker or memo to the document being referred to.

The server control unit 118 includes the “attached information holding unit 107
When it is detected that there is no valid element as "all data held in", the user I corresponding to the "document ID" received from the terminal unit 101 of the link information storage unit 116
A search is performed to determine whether the “user ID” received from the terminal unit 101 exists in the D table. If it does not exist, nothing is performed, but if it does exist, a block consisting of a maximum of N rows in the link table corresponding to the user ID is detected from the U offset value, and a row in the block is received from the terminal unit 101. Search for the existence of a "version" element in the "version" element. If it does not exist, nothing is done, but if it does exist, the version number is deleted from the "version" element or the line is deleted according to the link deletion procedure.

As a result of the above-described processing relating to link deletion, there is a case where no valid line remains from the block consisting of a maximum of N lines corresponding to the user ID received from the terminal unit 101. In this case, it is assumed that the user of the user ID has not attached a marker or a memo through all versions of the document, and the user ID is cleared from the row of the user ID table including the user ID, and the next user is added. Make a row reusable when

FIG. 15 is a diagram of data after deleting the user ID “tsuru” held by the link information storage unit 116 according to the first embodiment.

Next, an operation when the user edits a document displayed on the display unit 102 will be described. If the document itself is edited, the markers and memos added to the document up to that point may be misaligned. The location needs to be updated.

Therefore, when the user inputs a request for editing the document displayed on the display unit 102 from the input unit 103, the terminal control unit 110 which has detected the request inputs the request to the document data holding unit 106. The “document ID” held, the “version number” held in the version number holding unit 108, and the user ID
The “user ID” and “edit request” held in the holding unit 104 are sent to the server unit 112 via the terminal I / O unit 109 and the network unit 111 as a set.

When the server control unit 118 detects the reception of the set of “document ID”, “version number”, “user ID” and “edit request” to the server I / O unit 113, the server control unit 118 Information is extracted from the contents of the link table indicated by the document ID in the following procedure.

If one row of the link table is a row corresponding to the “user ID” and has the “version number”, the server control unit 118
The “end position” and the L offset value are obtained, and the line corresponding to the link ID of the line is detected from the attached information storage unit 117, and the element “type” and “substance” are obtained. In the other rows having the “version number”, the elements “start position”, “end position”, and L offset value are obtained. Ignore lines that do not fit any of the above.

The server control unit 118 sends the information obtained from all the rows of the link table in the above procedure to the terminal unit 101 through the server I / O unit 113 and the network unit 111 in the format shown in FIG. .

In the “attached data” of FIG. 16, data stored in the “entity” acquired from the attached information storage unit 117 is stored. Note that the L offset value in FIG.
The types and attached data are not entered in the rows 1 and 2N. Since these are attached information corresponding to different user IDs, the data of the start position and the end position are necessary for updating, but the type and attached data are not required.

The terminal control unit 110 which has detected the reception of the information in the format shown in FIG. 16 in the terminal I / O unit 109 stores the received information in the attached information holding unit 107, and further holds the received information in the attached information holding unit 107. The composite data is created using the information and the text data stored in the document data storage unit 106 and stored in the composite data storage unit 105. The terminal control unit 110 creates information to be displayed on the display unit 102 according to the content of the composite data in the composite data holding unit 105, and the “type” in FIG.
Is not used to create the information to be displayed. As a result, the information displayed on the display unit 102 includes only the information of the marker and the memo corresponding to the user using the terminal, and the display state is the same as the state of FIG.

Next, a case will be described in which the user edits the part that was previously “ok” to “o α or β”. The display on the display unit 102 is as shown in FIG.

As a result of this editing, the data held by the composite data holding unit 105 becomes the state shown in FIG.

When the editing work by the user is completed, the input unit 10
When a request to save the edited result is input to 3, the terminal control unit 110
Responds to this by extracting the text data of the edited document from the contents of the composite data
Stored in 106, and the starting point “(” in the composite data holding unit 105
And the end “)” is searched, and the values of “start position” and “end position” of the attached information holding unit 107 are updated to match the edited state. At this time, if the link deleted due to the deletion of the character string by the editing operation, that is, if the attached information holding unit 107 has a line but the composite data holding unit 105 has no start or end, the attached information holding unit Clear the 107 line.

FIG. 19 is a diagram of data after document editing held by the attached information holding unit 107.

Next, the terminal control unit 110 sends the “text data” and “document ID” of the document data holding unit 106, the “link information” of the attached information holding unit 107, the “version number” of the version number holding unit 108, and the user The “user ID” of the ID holding unit 104 is sent as a set to the server unit 112 via the terminal I / O unit 109 and the network unit 111.

When the server I / O unit 113 confirms reception of the “document ID”, the “text data” of the document, the “version number” of the document, the “link information” and the “user ID”, the server control unit 118 The version number is updated, and the text data and the document ID are paired and additionally registered in the document data storage unit 115. Further, the server control unit 118 controls the link information storage unit 1
The row of the link table corresponding to the document ID in
Reference is made to the L offset value of each line of the link information received from 1 to compare whether the "start position" and "end position" match between the line in the link table and the line in the link information. If they match, the server control unit 118 adds the updated version number to the element “version” of the row in the link table. If they do not match, the server control unit 118
One new row in the link table or one row from reusable rows is secured, and the “start position” and “end position” in the link information are added to the elements “start position” and “end position” of the obtained row. The end position is stored, the updated version number is stored in the element "version", and each element of the line used for comparison with the line in the link information is copied and stored in other elements.

FIG. 20 is a diagram of the edited data held by the link information storage unit 116. FIG. 21 is a diagram of the edited data held by the document data storage unit 115.

As is clear from the above description, the document management apparatus of this embodiment manages the shared document entity text and personal markers and memo data separately, so that the shared document has markers and memo data. A personal marker or memo data can be attached to a shared document without directly adding memo data. Further, since no information is added to the shared document for adding a marker or memo data, reference to the shared document by another user is not affected at all. Also,
When a marker or a memo attached to a document is designated, another part of the same document that refers to the same marker or memo or an attached part of another document can be presented to the user. In addition, version management of document data is possible, and markers and memo attachment points of all users set in the document when another user updates the version of the document are updated.

(Second Embodiment) In the document management apparatus of the second embodiment, the user can set the number of markers and memos without an upper limit.

This document management device is different from the device of the first embodiment (FIG. 1) in that the link information storage 1
The data structure of the data held by 16 differs, and accordingly, the processing performed by the server control unit 118 on the link information storage unit 116 differs. In other respects, there is no difference from the first embodiment.

FIG. 22 shows a diagram of data held by the link information storage unit 116 according to the second embodiment. The link information storage unit 116 holds, for each document, only a link table having the user ID, the start position, the end position, the version, and the link ID as shown in FIG. In this table, link information of markers and memos set by the user is endlessly entered.

The operation of the document management device will be described.

First, information exchanged between the terminal unit 101 and the server unit 112 via the network unit 111 is the same as in the first embodiment. Here, the processing performed by the server control unit 118 on the link information storage unit 116 will be described with emphasis on the point that the link information stored by the link information storage unit 116 is different from the first embodiment. The processing in each unit not appearing in the description here is the same as in the first embodiment.

In the first embodiment, as shown in FIG.
Although a user ID table and a link table are paired and prepared for each document held by the document data storage unit 115, in the second embodiment, as shown in FIG. A table is prepared for each of the documents held by the document data storage unit 115.

When the user requests the server unit 112 to refer to the document from the terminal unit 101, the server control unit 118 transmits the "user ID", "document ID", and "document ID" of the user, as in the first embodiment. Version number ". Subsequently, the server control unit 118 controls the link information storage unit 116 corresponding to the document ID.
The link table is searched, and the user ID matches the user ID received from the terminal unit 101, and the version number is changed to the terminal unit 101.
Extracts the line that matches the version number received from, removes the user ID from the extracted line, and stores the marker or memo information stored in the attached information storage unit 117 corresponding to the link ID included in the extracted line. To create link information in the format shown in FIG.

When the user adds, deletes, or changes a marker or memo data to the document displayed on the display unit 102,
As in the first embodiment, the server control unit 118 includes “all data held in the attached information holding unit 107”, “document ID held in the document data holding unit 106”, “user ID”
The user ID held in the holding unit 104 and the version number held in the version number holding unit 108 are grouped into a terminal unit 101.
Receive from

Subsequently, the server control unit 118 compares the link table in the link information storage unit 116 corresponding to the document ID received from the terminal unit 101 with the data stored in the attached information storage unit 107. Similar to the first embodiment, the comparison is performed between the row of data held in the attached information holding unit 107 and the row of the link table indicated by the L offset value of the row, and the elements “start position” and “end” Check if the values of "position" are equal.

If they are the same, nothing is done, but if they are different, the "start position" and "end position" of the data held in the attached information holding unit 107 are overwritten on the elements of the line in the link table. Those in which the L offset value of the row in the data held in the attached information holding unit 107 is described as “X” are assumed to be newly added this time as in the first embodiment,
One new row in the link table or one row from reusable rows is secured, and the secured row includes “start position”, “end position” of data held in the attached information holding unit 107, “User ID”, “version number” received from the terminal unit 101,
"New link ID" is stored.

Subsequently, the server control unit 118 extracts a row including the user ID and the version number obtained from the terminal unit 101 from the link table corresponding to the document ID obtained from the terminal unit 101 in the link information storage unit 116. Then, an L offset value corresponding to each of the extracted rows is obtained, and whether or not the row including the L offset value is included in the data held in the attached information holding unit 107 is searched. If a line that does not include the corresponding line is detected in the data held in the attached information holding unit 107, the line is assumed to be deleted this time, and the version number is deleted from the element “version” of the line. I do. If the version number stored in the “version” of the line becomes empty as a result of deleting the version number, all elements of the line are cleared to make the line reusable.

FIG. 23 shows a link L0003 of the user ID “tsuru” held by the link information storage unit 116 according to the second embodiment.
Is a diagram of data after the line has been deleted, and shows a state where the line has been cleared as a reusable line.

In this embodiment, the link information storage unit 116
Does not have a user ID table, as in the first embodiment,
The process of clearing the user ID from the row of the user ID table does not occur. An equivalent state is a state shown in FIG. 24 in which a line including the user ID of the user no longer exists as a result of clearing the elements of the link table accompanying the deletion of the marker or the memo.

As is clear from the above description, in the document management apparatus of this embodiment, for each document, the user
The number of markers and memos can be set without an upper limit.

(Third Embodiment) In a document management apparatus according to a third embodiment, in a method of managing link information using a user ID table and a link table, a user It is possible to set many markers and notes.

This document management device is different from the device of the first embodiment (FIG. 1) in that the link information storage 1
The data structure of the data held by 16 differs, and accordingly, the processing performed by the server control unit 118 on the link information storage unit 116 differs. In other respects, there is no difference from the first embodiment.

FIG. 25 shows a diagram of data held by the link information storage unit 116 according to the third embodiment. The link information storage unit 116 includes, for each document, a user ID table including a user ID and an L offset group as shown in FIG.
A link table having a start position, an end position, a version, and a link ID as elements is held.

The operation of the document management device will be described.

First, information exchanged between the terminal unit 101 and the server unit 112 via the network unit 111 is the same as in the first embodiment. Here, the processing performed by the server control unit 118 on the link information storage unit 116 will be described with emphasis on the point that the link information stored by the link information storage unit 116 is different from the first embodiment. The processing in each unit not appearing in the description here is the same as in the first embodiment.

In the first embodiment, as shown in FIG.
The set of the user ID table and the link table is stored in the document data storage 11
5 was prepared for each of the documents held, but the third
In the second embodiment, as shown in FIG. 25, the structure of the user ID table is different from that of the first embodiment. The preparation of a set of a user ID table and a link table for each of the documents held by the document data storage unit 115 is the same as in the first embodiment.

The user ID table according to the third embodiment has a row L of a link table in which link information of a user is stored for each user.
The offset values are collected and managed in pairs with the user ID. For example, in FIG. 25, the link information of the user with the user ID of pana is the row with the L offset of 0, 1, 2 in the link table, that is, the row with the link ID of L0001, L0002, and L0003. The ID table stores the user ID pana and the L offset values 0, 1, and 2 in pairs.

When the user requests the server unit 112 to refer to a document from the terminal unit 101, the server control unit 118, as in the first embodiment, transmits the "user ID", "document ID", and "document ID" of the user. Version number ". Subsequently, the server control unit 118 controls the link information storage unit 116 corresponding to the document ID.
In the link table, the user ID table is searched, and one or more L offset values of a row in which the link information of the user is stored are obtained, and a version number is further obtained from a row of the link table corresponding to the obtained L offset value. Extracts the same line as the version number received from the terminal unit 101, adds the marker or memo information stored in the attached information storage unit 117 corresponding to the link ID included in the extracted line, and adds the information to FIG. The link information in the format shown is created and sent to the terminal unit 101.

When the user adds, deletes, or changes a marker or memo data to the document displayed on the display unit 102,
As in the first embodiment, the server control unit 118 includes “all data held in the attached information holding unit 107”, “document ID held in the document data holding unit 106”, and “user ID held The user ID stored in the unit 104 and the version number stored in the version number storage unit 108 are paired and received from the terminal unit 101.

Subsequently, server control section 118 compares the link table in link information storage section 116 corresponding to the document ID received from terminal section 101 with the data held in attached information holding section 107. Similar to the first embodiment, the comparison is performed between the row of data held in the attached information holding unit 107 and the row of the link table indicated by the L offset value of the row, and the elements “start position” and “end position” To see if the values are equal.

If they are equal, nothing is done, but if they are different, the "start position" and "end position" of the data held in the attached information holding unit 107 are overwritten on the elements of the corresponding row in the link table. When the L offset value of the row in the data held in the attached information holding unit 107 is described as “X”,
In the same manner as in the embodiment, it is assumed that a new row is added this time, and one new row in the link table is secured or one row is secured from reusable rows. The "start position" and "end position" of the stored data, the terminal
The “user ID”, “version number”, and “new link ID” received from 101 are stored, and the L offset value of the row is set to the “L offset group” of the row including the user ID in the user ID table. to add.

Subsequently, the server control unit 118, based on the link table corresponding to the document ID acquired from the terminal unit 101 in the link information storage unit 116, corresponds to the user ID acquired from the terminal unit 101, and A line including the obtained version number is extracted, an L offset value corresponding to each extracted line is obtained, and the line including the obtained L offset value is stored in the attached information holding unit.
Search whether it is included in the data held in 107. If a line that does not include the corresponding line is detected in the data held in the attached information holding unit 107, the line is assumed to be deleted this time, and the version number is deleted from the element “version” of the line. I do. When the version number stored in the “version” of the line becomes empty as a result of deleting the version number, all the elements of the line are cleared to make the line reusable, and the L offset value of the line is set to the user ID. Delete from the “L offset group” of the row including the user in the table.

FIG. 26 is a diagram of data after deleting the link L0006 of the user ID “tsuru” held in the link information storage unit of the third embodiment, and the line has been cleared as a reusable line. Indicates the status.

As a result of deleting the L offset value from the “L offset group”, “L offset” in the row including the user in the user ID table is displayed.
When the "offset group" becomes empty, all the elements of the row in the user ID table are cleared to make the row reusable. FIG.
FIG. 14 is a diagram of data after deleting a user ID “tsuru” held by a link information storage unit according to the third embodiment.

As is apparent from the above description, in the document management apparatus according to the third embodiment, the user is allowed to write the value of the L offset in the L offset group column of the user ID table until there is no room for writing. Many markers and memos can be set. Further, at the time of document reference, since only the row corresponding to the user who has issued the reference request can be referenced from the link table, link information can be extracted at high speed.

(Fourth Embodiment) In a document management apparatus according to a fourth embodiment, in a method of managing link information using a user ID table and a link table, the number of markers and memos set by the user is reduced. The upper limit can be eliminated.

This document management apparatus differs from the first embodiment (FIG. 1) in the data structure of the data held by the link information storage unit 116. Accordingly, the server control unit 11
8 is different from the link information storage unit 116 in processing. Other points are the same as those of the first embodiment.

FIG. 28 shows the data structure of the data held by the link information storage unit 116. As shown in FIG. 28, the link information storage unit 116 stores, for each document, a user ID table including a user ID and a minimum value of an L offset value corresponding to the user ID, a start position, and an end position. In addition to the position, version, and link ID, a link table having "Next" as an element for displaying the next line in which link information of the same user is described, and a deleted link table for displaying the L offset value of the deleted line It has.

The operation of the document management device will be described.

First, information exchanged between the terminal unit 101 and the server unit 112 via the network unit 111 is the same as in the first embodiment. Here, the processing performed by the server control unit 118 on the link information storage unit 116 will be described with emphasis on the point that the link information stored by the link information storage unit 116 is different from the first embodiment. The processing in each unit not appearing in the description here is the same as in the first embodiment.

In the first embodiment, as shown in FIG. 4, a user ID table and a link table are paired and prepared for each document held by the document data storage unit 115. In the fourth embodiment, as shown in FIG. 28, the structures of the user ID table and the link table are different from those of the first embodiment, and a deleted link table is newly provided.

As in the first embodiment, a set of a user ID table, a link table, and a deleted link table is prepared for each document held by the document data storage unit 115. The user ID table according to the fourth embodiment includes, among one or more rows in a link table storing link information corresponding to each user ID,
The L offset value of one row is managed in combination with the user ID. For example, in FIG. 28, the link information of the user whose user ID is pana is the row with the L offset of 0, 1, 2 in the link table, that is, the row with the link ID of L0001, L0002, and L0003. Is the user ID pa
na and one of the L offset values 0, 1, 2 are stored as a set.

In the fourth embodiment, a series of rows in a link table corresponding to a certain user ID is managed as a ring. In the example where the user ID is pana, the L of the row in the corresponding link table
The offset values were 0, 1, and 2, which were managed as a circular chain with 0 next to 1, 1 next to 1, 2 next to 0, and so on. In order to realize this ring, a “Next” element is newly added to the link table of the fourth embodiment. The “Next” element stores an L offset value of a row positioned as “next” of the row. In FIG. 28, “1” is stored in the “Next” element of the row with the link ID L0001, which is the “next” of the row with the link ID L0001, ie, the row with the L offset value of 0, and the L offset value is 1 Means that the row is positioned.

As described above, the row next to the row with the L offset value of 0 is the row with the L offset value of 1, the row next to the row with the L offset value of 1 is the row with the L offset value of 2, The row following the row with the offset value of 2 manages all the rows in the link table corresponding to the user ID of pana as a circular chain with the row with the L offset value of 0.

When the user requests the server unit 112 to refer to a document from the terminal unit 101, the server control unit 118 transmits the "user ID", "document ID", and "document ID" of the user, as in the first embodiment. Version number ". Subsequently, the server control unit 118 controls the link information storage unit 116 corresponding to the document ID.
The user ID table in the link table is searched, one L offset value of the row storing the link information of the user in the link table is obtained, and the row in the link table indicated by the obtained L offset value is referred to and referred to. All the link information stored in the link table and corresponding to the user ID was extracted and extracted by successively referring to the next row indicated by the Next element of the row in the link table until the circle went around. From the link information, a line having the same version number as the version number received from the terminal unit 101 is further extracted, and the information of the marker or the memo stored in the attached information storage unit 117 corresponding to the link ID included in the extracted line is extracted. In addition, it creates link information in the format shown in FIG. 7 and sends it to the terminal unit 101.

For example, if the user ID obtained from the terminal unit 101 is t
If the suru and the version number are 1, it can be seen from the user ID table that the L offset value indicating the row of the link table to be referred to is 3, and the “Nex” of the row having the L offset value of 3 is 3
It can be seen from the “t” element that the next row is a row with an L offset value of 4, and that the next row from the “Next” element of the row with an L offset value of 4 is a row with an L offset value of 6 It turns out that the link ID is L0004, L0005, L000 without referring to any other row of the link table while comparing the value of the "version" element of the row with the version number obtained from the terminal unit 101.
Extract the contents of row 7.

[0117] In addition, each row in the link table in which the contents stored up to that point have been cleared and which can be reused is managed by connecting them with a circular chain. The deleted link table stores the L offset value of one row in the reusable row group.

When the number of elements in the circular chain becomes one, the L offset value of the row is stored in the “Next” element of the row.

When the user adds, deletes, or changes a marker or memo data to the document displayed on the display unit 102,
As in the first embodiment, the server control unit 118 includes “all data held in the attached information holding unit 107”, “document ID held in the document data holding unit 106”, and “user ID held The user ID stored in the unit 104 and the version number stored in the version number storage unit 108 are paired and received from the terminal unit 101.

Subsequently, server control section 118 compares the link table in link information storage section 116 corresponding to the document ID received from terminal section 101 with the data held in attached information holding section 107. Similar to the first embodiment, the comparison is performed between the row of the data held in the attached information holding unit 107 and the row of the link table indicated by the L offset value of the row, and the elements “start position” and “end” Check if the values of "position" are equal.

If they are equal, nothing is done, but if they are different, the "start position" and "end position" of the data held in the attached information holding unit 107 are overwritten on the elements of the corresponding row in the link table. Those in which the L offset value of the row in the data held in the attached information holding unit 107 is described as “X” are assumed to be newly added this time as in the first embodiment, and are described in the link table. One new line is reserved or one line is reserved from reusable lines.
The “start position” and “end position” of the data held in 7,
The “user ID”, “version number”, and “new link ID” received from the terminal unit 101 are stored, respectively, and any of the circular chains of the row indicated by the L offset value of the row of the user ID in the user ID table The value of the “Next” element of the line located before and after the location is added to the location by operating the value. For example, when the L offset value is connected by a ring of 3 → 4 → 6 → 3, and a row of L offset value 11 is added between 4 and 6, the “Next” element of the row of L offset value 4 Is set to 11 and 6 is set to the “Next” element of the row with the L offset value 11.

Detection of a reusable row is performed by examining a deleted link table. As shown in FIG. 28, when a valid L offset value is not set in the deletion link table, it is determined that there is no reusable row. When an L offset value is set, the set L offset value is One line is obtained from the line group of the circular chain to be pointed and used.

The consumption of reusable rows reduces one row from the circular chain of reusable rows. For example, when the L offset value of a reusable row is managed in a circular chain of 21 → 22 → 23 → 24 → 21, and the row having an L offset value of 22 is removed from this chain for reuse, the L offset The value of the “Next” element in the row with the value 21 is set to 23.

Subsequently, the server control unit 118 checks the document ID acquired from the terminal unit 101 in the link table in the link information storage unit 116.
From the link table corresponding to, the line corresponding to the user ID obtained from the terminal unit 101 and including the version number obtained from the terminal unit 101 is extracted, and the L offset value corresponding to each extracted line is obtained and obtained. A search is performed to determine whether a row including the L offset value is included in the data held in the attached information holding unit 107. If a line that does not include the corresponding line is detected in the data held in the attached information holding unit 107, the line is assumed to be deleted this time, and the version number is deleted from the element “version” of the line . If the version number stored in the “version” of the row becomes empty as a result of deleting the version number, all the elements of the row are cleared to make the row reusable, and the link table corresponding to the user ID is deleted. Is removed from the circular chain of the row, and this is added to the circular chain of the row indicated by the deleted link table, and if necessary, the L offset value of the deleted link table is set.

FIG. 29 is a diagram of data after deleting the link L0004 of the user ID “tsuru” held in the link information storage unit of the fourth embodiment, and shows a state where the line is cleared as a reusable line. . In the row of L0004, all elements other than L0004 of the link ID are cleared to be empty, and are off the ring chain of the row in the link table corresponding to tsuru. Further, upon deletion from the chain, since the row to be deleted was set as the L offset value of the chain corresponding to tsuru in the user ID table, an L offset value 4 indicating another row in the chain was set. ing. L of the row deleted this time is displayed in the deletion link table.
The offset value 3 is set, and the row is reusable. Further, assuming that the reusable row is only the row of L0004, the value of the “Next” element of the row is set to 3 which is the L offset value of the row.

FIG. 30 is a diagram of data after deleting the link L0003 of the user ID “pana” held in the link information storage unit of the fourth embodiment. This deletion is assumed to have been performed after the state shown in FIG. The processing when the row with the link ID L0003 is deleted from the annular chain of the row in the link table corresponding to pana is as described above. Here, the deleted row having the link ID L0003, that is, the row having the L offset value of 2, forms a ring with the row having the L offset value of 3 which is a reusable row in FIG.

If the row of the row in the link table corresponding to the user becomes empty as a result of deleting the row in the link table, all elements of the row in the user ID table can be cleared and reused. Line. FIG. 31 is a diagram of data after deleting the user ID “pana” held by the link information storage unit.

As is clear from the above description, in the document management apparatus of this embodiment, there is no specified upper limit on the number of markers and memos that can be set by the user for each document. Also, when referring to a document, it is possible to extract link information at high speed by referring to only the row in the link table corresponding to the user who has issued the reference request. In addition, reusable rows in the link table can be obtained without searching the link table.

(Fifth Embodiment) The document management apparatus of the fifth embodiment manages link information and actual state information together.

This document management apparatus does not include the attached information storage unit 117 as compared with the first embodiment (FIG. 1).
The data structure of the data held by the link information storage unit 116 is different. Along with that, the server control unit 118
Perform a different process on the link information storage unit 116. Other points are the same as those of the first embodiment.

FIG. 32 shows a diagram of data held by the link information storage unit 116 according to the fifth embodiment. This data is
This is a structure having both information held by the link information storage unit 116 and the attached information storage unit 117 of the first embodiment. That is, in the first embodiment, each marker or memo entity added to the document is managed in each line of the attached information storage unit 117. However, in this embodiment, each marker or memo entity is It is stored in the line having the link ID in the link information storage unit 116. As a result, if the row has the same link ID, the contents of the element “type” and the element “substance” are stored in the row in an overlapping manner. In this embodiment, such data having the structure shown in FIG.
Prepare for each of the documents held by 5.

When the user requests the server unit 112 to refer to a document from the terminal unit 101, the server control unit 118 transmits the "user ID", "document ID", and "document ID" of the user, as in the first embodiment. Version number ". Subsequently, the server control unit 118 controls the link information storage unit 116 corresponding to the document ID.
The link table in the form shown in FIG. 7 is extracted by searching the inside link table and extracting the same row as the user ID whose user ID is received from the terminal unit 101 and the version number which is the same as the version number received from the terminal unit 101. Information is created and sent to the terminal unit 101.

When the user adds, deletes, or changes a marker or memo data to the document displayed on the display unit 102,
As in the first embodiment, the server control unit 118 includes “all data held in the attached information holding unit 107”, “document ID held in the document data holding unit 106”, and “user ID held The user ID stored in the unit 104 and the version number stored in the version number storage unit 108 are paired and received from the terminal unit 101.

Subsequently, the server control unit 118 compares the link table in the link information storage unit 116 corresponding to the document ID received from the terminal unit 101 with the data stored in the attached information storage unit 107. The comparison is similar to the first embodiment,
Performed by the row of the data held in the attached information holding unit 107 and the row of the link table indicated by the L offset value of the row,
It is checked whether the values of the elements "start position" and "end position" are equal.

If they are equal, nothing is done. If they are different, the “start position”, “end position”, “type” and “attached data” of the data held in the attached information
Overwrites the element of the corresponding row in the link table. Those in which the L offset value of the row in the data held in the attached information holding unit 107 is described as “X” are assumed to be newly added this time as in the first embodiment, and are described in the link table. New line of 1
A row is secured or one row is re-usable from the reusable row. The “start position”, “end position”, “type”, and “attached data” of the data held in the attached information holding unit 107 are stored in the secured row. "User ID", "version number",
"Newly generated link ID" is stored.

Subsequently, the server control unit 118 extracts a line including the user ID and the version number obtained from the terminal unit 101 from the link table corresponding to the document ID obtained from the terminal unit 101 in the link information storage unit 116. Then, an L offset value corresponding to each extracted row is obtained, and it is searched whether a row including the obtained L offset value is included in the data held in the attached information holding unit 107. If a line that does not include the corresponding line is detected in the data held in the attached information holding unit 107, the line is assumed to be deleted this time, and the version number is deleted from the element “version” of the line. I do. When the version number stored in the “version” of the line becomes empty as a result of deleting the version number, all the elements of the line are cleared to make the line reusable. When the line in the link table corresponding to the user becomes empty as a result of the clearing, the line including the user ID is cleared from the user ID table.

As is clear from the above description, in the document management apparatus according to this embodiment, the attached information can be obtained immediately without tracing from the link information. Can be presented.

[0138]

As is apparent from the above description, the document management apparatus of the present invention separately manages a shared document entity text and personal markers and memo data.
It is possible to attach a personal marker or memo data to a shared document without any influence when another user refers to the shared document.

Further, by specifying a marker or a memo attached to a document, it is possible to present to the user another portion of the same document which refers to the same marker or memo or an attached portion of another document. Further, it is possible to manage the version of the document data, and when the version of the document is revised by another user, the markers and memo attachment points of all the users set in the document are also updated. In a device that manages link information with the above data, the user can set the number of markers and memos for each document without specifying an upper limit.

The apparatus for managing link information by using the data having the structure shown in FIG. 25 allows a user to set a large number of markers and memos for each document. Can be extracted at high speed.

The apparatus for managing link information using the data having the structure shown in FIG. 28 allows a user to set the number of markers and memos without specifying an upper limit for each document. When referring to a document, link information can be extracted at high speed.

In the apparatus for managing the link information and the attached information by using the data having the structure shown in FIG. 32, it is not necessary to obtain the attached information by tracing the data. be able to.

[Brief description of the drawings]

FIG. 1 is a functional block diagram illustrating a document management apparatus according to a first embodiment;

FIG. 2 is a diagram of data held by a user ID / password storage unit according to the first embodiment;

FIG. 3 is a diagram of data held by a document data storage unit according to the first embodiment;

FIG. 4 is a diagram of data held by a link information storage unit according to the first embodiment;

FIG. 5 is a diagram illustrating data held by an attached information storage unit according to the first embodiment;

FIG. 6 is a diagram illustrating data held by a document data holding unit according to the first embodiment;

FIG. 7 is a diagram of data held by an attached information holding unit according to the first embodiment;

FIG. 8 is a diagram of data held by a composite data holding unit according to the first embodiment;

FIG. 9 is a view showing a document display when referring to a document on the display unit according to the first embodiment;

FIG. 10 is a diagram illustrating a marker addition when referring to a document on the display unit according to the first embodiment;

FIG. 11 is a diagram of data after addition of a marker held by the composite data holding unit according to the first embodiment;

FIG. 12 is a diagram of data after addition of a marker held by an attached information holding unit according to the first embodiment;

FIG. 13 is a diagram of edited data held by a link information storage unit according to the first embodiment;

FIG. 14 is a diagram of data after deleting a link L0007 of a user ID “tsuru” held by a link information storage unit according to the first embodiment;

FIG. 15 is a diagram of data after deleting a user ID “tsuru” held by a link information storage unit according to the first embodiment;

FIG. 16 is a diagram of data at the start of document editing held by the attached information holding unit according to the first embodiment;

FIG. 17 is a diagram showing a document display after editing the document on the display unit according to the first embodiment;

FIG. 18 is a diagram of data after document editing held by the composite data holding unit according to the first embodiment;

FIG. 19 is a diagram of data after document editing held by the attached information holding unit according to the first embodiment;

FIG. 20 is a diagram of edited data held by the link information storage unit according to the first embodiment;

FIG. 21 is a diagram of edited data held by the document data storage unit according to the first embodiment;

FIG. 22 is a diagram of data held by a link information storage unit according to the second embodiment;

FIG. 23 is a diagram of data after deleting the link L0003 of the user ID “tsuru” held by the link information storage unit according to the second embodiment;

FIG. 24 is a diagram of data after deleting a user ID “tsuru” held by a link information storage unit according to the second embodiment;

FIG. 25 is a diagram of data held by a link information storage unit according to the third embodiment;

FIG. 26 is a diagram of data after deleting the link L0006 of the user ID “tsuru” held by the link information storage unit according to the third embodiment;

FIG. 27 is a diagram of data after deleting a user ID “tsuru” held by a link information storage unit according to the third embodiment;

FIG. 28 is a diagram of data held by a link information storage unit according to the fourth embodiment;

FIG. 29 is a diagram of data after deleting the link L0004 of the user ID “tsuru” held by the link information storage unit according to the fourth embodiment;

FIG. 30 is a diagram of data after deleting a link L0003 of a user ID “pana” held by a link information storage unit according to the fourth embodiment;

FIG. 31 is a diagram of data after deleting a user ID “pana” held by a link information storage unit according to the fourth embodiment;

FIG. 32 is a diagram of data held by a link information storage unit according to the fifth embodiment.

[Explanation of symbols]

 101 terminal unit 102 display unit 103 input unit 104 user ID storage unit 105 composite data storage unit 106 document data storage unit 107 attached information storage unit 108 version number storage unit 109 terminal I / O unit 110 terminal control unit 111 network unit 112 server unit 113 Server I / O Unit 114 User ID / Password Storage Unit 115 Document Data Storage Unit 116 Link Information Storage Unit 117 Attached Information Storage Unit 118 Server Control Unit

 ──────────────────────────────────────────────────の Continuing on the front page (72) Inventor Chuichi Kikuchi 1006 Kazuma Kadoma, Osaka Pref. Matsushita Electric Industrial Co., Ltd. F-term (reference) 5B009 QB11 SA03 SA14 TB13 VA02 5B075 KK07 KK43 KK54 KK63 KK64 KK65 KK66 KK67 KK68 ND03 ND36 NK02 NK07 NK08 NK14 NS10 PR01

Claims (13)

[Claims] 1. A document management device having a server unit and a terminal unit connected by a network, wherein the terminal unit includes a display unit for referring to a document, and a user ID.
And an input unit for inputting a set of passwords and a document ID of a document to be referred to, and a user I for holding the user ID input by the user at the time of login until the user logs out
D holding unit, a document data holding unit for holding text data of a document, an attached information holding unit for holding link information of a marker or a memo individually attached to the document, and the link information in the text data of the document. A composite data storage unit for storing the reflected composite data, a version number storage unit for storing the version number of the document being displayed on the display unit,
A document management apparatus, comprising: a terminal I / O section for performing / O; and a terminal control section for controlling processing of the terminal section. 2. A document management device having a server unit and a terminal unit connected by a network, wherein the server unit performs a server I / O unit for performing I / O with a network, and uses the device. User ID of appropriate user
And a user ID / password storage unit for storing a set of passwords, a document data storage unit for storing registered document data in text, and a marker personally attached by a user to a document stored in the document data storage unit. Or a link information storage unit for storing information relating a memo, an attached information storage unit for storing the contents of a marker or a memo personally attached to a document by a user, and a server control unit for controlling processing in a server unit. A document management device comprising: 3. The link information storage unit stores, for each document, a user ID table having a user ID as an element, a start position and an end position indicating a position where a marker or a memo is attached to the document, a version of the document, The document management apparatus according to claim 2, wherein the server control unit stores data of the user ID table and the link table, and a link table including each of the link IDs as elements. 4. The link information storage unit includes, for each document, a user ID, a start position and an end position indicating a position where a marker or a memo is attached to the document, a document version, and a link ID as elements. The document management apparatus according to claim 2, wherein a link table to be stored is stored, and the server control unit operates data of the link table. 5. A user ID table having a link value to one or more rows of a link table described later and a user ID corresponding to each document as an element,
A start position and an end position indicating a position where a marker or a memo is attached to a document, a version of the document, and a link table including each of link IDs as elements, and the server control unit stores
3. The document management apparatus according to claim 2, wherein data of the user ID table and the link table are operated. 6. The link information accumulating unit stores, for each document, a user ID table having a link value to one row of a link table and a user ID as elements, and a marker or memo for the document. And a link table including, as elements, values of a start position and an end position indicating an attachment position, a document version, a link ID, and a value indicating a line positioned next, and the server control unit stores the user ID. 3. The document management apparatus according to claim 2, wherein data of the table and the link table are operated. 7. The server control unit according to claim 1, wherein the server control unit searches for information stored in the link information storage unit, and detects a document to which a specific marker or memo is attached and an attachment position thereof. 3. The document management device according to 2. 8. The document data storage unit holds text data of different versions of a document, and the server control unit searches information stored in the link information storage unit to specify a designated document. 7. The document management apparatus according to claim 3, wherein a marker or a memo attached by a user specified to the specified version is detected. 9. The server control unit searches information stored in the link information storage unit, and obtains information on attachment positions of all markers or memos attached to a specified version of a specified document. Extract, the terminal unit edits the version of the document data, re-detects the attached positions of all the markers or memos at the end of editing, the server control unit,
7. The re-detected attachment position is reflected in information stored in the link information storage unit.
The document management device according to any one of the above. 10. Omitting the attachment information storage unit, the link information storage unit starts a user ID table having a user ID as an element and a marker or memo attachment position for the document for each document. Position and end position, document version,
A server storing a link ID, a type of a marker or a memo, and a link table having elements of the contents of the marker or the memo as elements, and wherein the server control unit operates data of the user ID table and the link table. 3. The document management device according to claim 2, wherein 11. The information stored in the attached information storage unit or the composite information according to a user's addition or deletion of a marker or memo, a change of an attachment position, or a correction of a marker color or a substantial text by the user. 2. The composite data stored in the data storage unit is sequentially changed.
Document management device according to the item. 12. The document management apparatus according to claim 2, wherein the server control unit searches the attached information storage unit and extracts a marker or a memo corresponding to a designated user ID. 13. The server control unit according to claim 10, wherein the server control unit searches the link information storage unit and extracts a marker or a memo corresponding to a designated user ID.
Document management device according to the item.