US20020120613A1 - Document management system - Google Patents

Abstract

The present intervention wherein a document referencing computer applies relationships between documents that are documents managed by a document managing computer, and a knowledge managing computer manages these relationship, or links. The display of the links is controlled according to a variety of conditions. The display of these links between documents can be controlled by either the user who set the link (the link setting user) or by a user using the system to reference documents, or a referencing user, thereby enabling related documents to be referenced easily.

Description

BACKGROUND OF THE INVENTION
• This invention relates to a document management system that includes a document referencing system for retrieving a desired document from a document database in which electronic documents are stored and more specifically, a technology for defining the relationship between documents and a technology for referencing related documents.[0001]
• A document referencing system may be used to search for other documents related to a particular document. A conventional technology for searching for a related document employs a referencing method described following, that utilizes information on the history of past referencing operations.[0002]
• The invention of JP-A-3-22084 records referenced history information consisting of the frequency of access and the time of access by an information user for each option on each menu and a priority for isolating for example, those options which have a high access frequency. This helps to improve operability.[0003]
• The invention of JP-A-10-111876 assesses a referencing user according to assessment standards based on the results of the referencing operations of that user. Assessment standards are used in case of referencing a patent, to assess points that include the importance and the novelty of as well as the means pertaining to, that patent. Such assessments can be applied to an individual or a group and enable a subsequent referencing user to assess the results of referencing operations.[0004]
• The invention of JP-A-11-39320 has a method for searching for related documents. This method records a “job name” and a “job handler” associated with the making of a document and times at which it is referenced, and automatically records a history of operations performed on that document including such things as the performance of, references and alterations to, the document. By doing this, links are created between the document and each “job name” and “job handler.” Usage of these links enables a user to successively extract documents related to a particular document so the user can reference a document worked on for a job, to reference other jobs worked on for that referenced document and further, to reference documents worked on for that other jobs.[0005]
SUMMARY OF THE INVENTION
• The conventional art as described has problems however. To shorten the time required for referencing for each individual user and to improve operability, the invention of JP-A-3-22084 does not allow sharing of history information by multiple people. In the invention of JP-A-10-111876 if an assessment is conducted by an individual, the system applies the assessment without regard to the level of skill of the person performing the assessment. This means that if there are differing points of focus for a referencing operation the assessment applied to a particular document may differ between different people. With technology of the conventional art as described, an assessment is applied to the actual target document itself but any relation that document has to an original document that would provide a good starting point to reference other related documents, is not revealed.[0006]
• The invention of JP-A-11-39320 is a system which only associates a job and a document, however this is an inadequate degree of association for document referencing purposes. Creating an association between a job and a document in the case of for example the job of “creating a report” involves collecting data to produce the document, allowing the person concerned to reference other reports they produced themselves in the past and referencing documents for citation. It is therefore necessary for the various work objectives required for the job involved to be managed as linked attribute information. There is also the problem of cases in which links are formed to all documents that are worked on many of which have actually no relationship to a job. This leads for example to situations where certain documents are referenced in relation to a certain job that have no relationship to that job. The existence of such meaningless links complicates the work of referencing documents that are related to each other.[0007]
• The problems with methodology used for referencing related documents using the prior art as described above is that the links between related documents all appear the same to everybody. To achieve a more effective and flexible document referencing methodology requires that the display of links be restricted according to conditions such as the objective of the referencing user's referencing operation, the group to which referencing a user belongs and the existence of access levels to links.[0008]
• An objective of the present invention is to control the display of links between related documents to reflect the wishes of a referencing user and a link setting user.[0009]
• To fulfill the above objective in the present invention restricts the display of links so as to coordinate them with the settings—the input—applied by the link setting user and to allow the referencing user to control the display of links based on information about the link setting user who input the link.[0010]
BRIEF DESCRIPTION OF THE DRAWINGS
• FIG. 1 shows the system structure according to an embodiment of the present invention.[0011]
• FIG. 2 shows a document index table.[0012]
• FIG. 3 shows a link information table.[0013]
• FIG. 4 shows a user information table.[0014]
• FIG. 5 shows an expertise table.[0015]
• FIG. 6 shows a link source document ID table.[0016]
• FIG. 7 shows the flow of processing operations that occur when a document is registered.[0017]
• FIG. 8 shows the flow of processing operations that occur when a link is set.[0018]
• FIG. 9 shows the flow of operations that occurs when a document is referenced using a link.[0019]
• FIG. 10 shows in detail, the flow of operations that occur when a link is displayed.[0020]
• FIG. 11 shows an example of a link referencing screen.[0021]
DESCRIPTION OF THE EMBODIMENTS
• A specific embodiment of an information referencing system according to the present invention will now be described with reference to FIGS. 1 through 11. The first description is of the overall structure of an information referencing system according to this embodiment.[0022]
• A[0023]document managing computer1 is a computer for managing documents to which is connected anarchive database2. The processings of data will be executed structured as an integrated whole. Whereas the following description envisages a configuration in which these three computers exist separately from each other as in FIG. 1, the description would still largely apply were these three computers to be each a single part or concentrated together.
• The[0024]archive database2 includes, as shown in FIG. 2, a document index table 20 and the document itself. Each document is identified by a document ID and is associated to each item in the document index table. At the very least the identifying document ID of a document must exist in the document index table and each ID should correspond to its respective document.
• The[0025]knowledge database6 of the form of this embodiment includes a link information table 30 shown in FIG. 3, a user information table 40 shown in FIG. 4, an expertise table 50 shown in FIG. 5 and a link source document ID table 60 shown in FIG. 6.
• Certain settings must be applied before document referencing can commence.[0026]
• User information defining users of the system is defined first. FIG. 4 shows the user information table 40. User information is information about a user who registers a document, references or sets links between documents.[0027]
• Items in user information are a user ID, the user's name, the group to which he belongs and his access level. The user ID is the identifier which specifies a user in the system. The user's name is the user's real name. The user's group is the name of the group to which the user belongs e.g. a group such as the name of a department in an organization. Access level is a label that shows the scope of access that user has to a document or links between documents. 1 is the lowest level and the scope of access increases as the number of the level rises to 2 or 3.[0028]
• FIG. 4 shows an example of user information. The user ID of this user is Tanaka, his user name is Ichiro Tanaka, his user group is Gr 1 and his access level is 1.[0029]
• Next, expertise information is defined. FIG. 5 shows an expertise table 50. Expertise information is information that shows what expertise is held by which user.[0030]
• FIG. 5 shows an example of expertise information. User Tanaka's expertise is in databases. It is possible to register multiple fields of expertise for one user. No registration is made for a user with no expertise.[0031]
• The workings of the[0032]document referencing computer4, thedocument managing computer1 and theknowledge managing computer5 when a user uses thedocument referencing computer4 to reference a document in thearchive database2 will now be described. The conditions extant in each table are as shown in FIGS.4 and5.
• The flow of processing operations when a document is registered, when a link is set between documents and when a document is referenced using a link will be described with reference to FIGS. 7 through 10. Firstly, the flow of operations for registering a document will be described with reference to FIG. 7.[0033]
• (S01) In response to input from a user a message requesting login is sent from the[0034]document referencing computer4 to thedocument managing computer1. User ID=Tanaka for example is included in the message. A password may also be included.
• (S02) In response to the user login request the[0035]document managing computer1 looks up the user information table 40 and confirms that there is a record saying that that user ID is Tanaka and a login authorization message is delivered to the document referencing computer. If the login request message includes a password, although not illustrated in the drawings, the login password must be registered in advance in the user information table 40. Login authorization is based on the matching of a user ID and password.
• (S03) The[0036]document referencing computer4 sends a message requesting registration of a document to thedocument managing computer1. This message could include for example document data, the document ID, the document name, a user ID, a user group and keywords. Document data includes at least one of text data, document data created by the application software used to create document, drawing data, image data, audio data and moving image data. The document ID is an identifier allocated to uniquely determine a document inside the system. The user ID and document user group are information about the user who registered the document. The user ID identifies the user. The user group identifies the group to which that user belongs. Keywords are words applied to assist in referencing the document.
• (S04) The[0037]document managing computer1 holds the document data included in the document registration request received in thearchive database2 and the information about the document is held in the document index table 20. FIG. 2 shows a document index table 20. The document index table holds this information so that information concerning the document stored in thearchive database2 can be referenced subsequently. FIG. 2 shows that the user Tanaka registered a document with the document name “x report” on Apr. 15, 2000. FIG. 2 also shows that the document ID for the document is DOC 001, that the user group of Tanaka isGr 1 and that reference keywords for this document are A and B.
• A system design in which this document ID is automatically allocated from the[0038]document managing computer1 would work well. In this case the numbers could conform to the order of registration. Having information concerning the document such as the document name, user ID and user group automatically registered as keywords may also be appropriate. An appropriate word from automatic analysis of data included in the document could also be registered.
• This completes the description of the flow chart in FIG. 7. Here follows a description with reference to FIG. 8 of the flow of processing operations when a link between documents is established.[0039]
• (S11) and (S12) are processes concerned with a user logging into the[0040]knowledge management computer5 but further explanation has been omitted because they simply follow the processes of (S01) and (S02) respectively in respect of thedocument managing computer1 except that theknowledge managing computer5 should be read in place of thedocument managing computer1.
• (S13) The[0041]document referencing computer4 delivers the document reference request message to thedocument managing computer1. This message could for example be structured of referencing conditions including the document ID, document name, document creation date, user ID, user group and keywords.
• (S14) The[0042]document managing computer1 searches in the document index table 20 for documents that match the referencing conditions included in the document reference request message received and returns a document information list to thedocument referencing computer4. The document information is constructed of the document ID, document name, document creation date, creating user ID and user group for example.
• (S15) The[0043]document referencing computer4 selects one document from the document information list received and delivers a message to thedocument managing computer1 requesting that the data in the document be displayed. This message contains the document ID for example.
• (S16) The[0044]document managing computer1 pulls the document data specified in the document display request message out from thearchive database2 and delivers that document data to thedocument referencing computer4.
• (S17) The[0045]document referencing computer4 displays the document data received. Next, if the user wants to set links between this document and another document a message requesting that this document be a link source document is delivered to theknowledge managing computer5. This message could include for example the document ID and user ID. The link source document is one document amongst documents between which links are set. These processes may be performed after one document is selected from amongst multiple documents at (S13), dispensing with (S15) and (S16)
• (S18) The[0046]knowledge managing computer5 holds the document ID and user ID included in the link source specification request message received in the link source document ID table 60. If data from the same user ID already exists there that data is overwritten. FIG. 6 shows a link source document ID table 60. FIG. 6 shows that a user Tanaka has specified document DOC 001 as a link source document.
• From (S19) to (S22) the user references another document and displays it. The processes involved here are each the same as those occurring between (S13) through (S16) and thus are not described here. The processes occurring between (S19) through (S22) may be repeated over again many times while (S17) may be executed at some stage within that sequence, in other words, link source documents may be reset multiple times.[0047]
• (S23) The[0048]document referencing computer4 specifies a particular document and delivers to theknowledge managing computer5, a message requesting a linkage to a previously registered link source document. Items contained in this message include for example the document ID, the user ID of the user, the user's group of the user, the job, the objective, comments, access enabled groups, and access levels. The job shows information describing what work the document referencing operation the user is presently executing is part of. This could be for example creating a report or producing specifications. The objective shows the kind of objective that the links between the documents were set based on. When the job is creating a report for example, the objective will differ according to each operation comprising that job. This could include for example researching prior art, researching past reports of a similar type, researching trends in other companies, research about a specific technology, researching relevant laws or researching relevant drawings. The link setting user specifies what meaning the link he is about to set will have based on the setting for the objective. Comments are information that provides a supplementary explanation for the link and can be freely recorded at the discretion of the user. Access enabled groups are specified to control the users who are enabled access to the display of the links. At least one group must be specified for the user group of the user. To allow display to everybody, specify nothing. Access levels also are specified to control users who are enabled access to the display of links. Access levels specified in the users information table 40 are specified at this point.
• (S24) The[0049]knowledge management computer5 uses the user ID included in the set link request message received to acquire a link source document ID from the link source document ID table 60, which is stored in the link information table 30 together with other information included in the set link request message. FIG. 3 shows a link information table 30. The link information table 30 stores information about relationships between documents and relationship disclosure standards.
• The relationships between documents shows for what purpose the relationship was set and by whom. The relationship disclosure standards show the scope of users to whom the relationship may be disclosed. The link source document ID and link recipient document ID of link information table 30 show the respective sides to the document linkage relationship. The link set date carries a value allocated automatically on the date the link is set. The user ID and user group of the user who set the link are information concerning the link setting user. The job, objective, comments, access enabled groups, and access levels are set in the set link request message. The reference frequency is set at 0 when the link is set. FIG. 3 shows a link set between documents, one with the document ID “DOC001” and the other “DR002.” The link set date in that table is Jun. 5, 2000 and the link setting user was “Tanaka,” whose group is “[0050]Gr 1.” The job at the time the link was set was “create report” and the objective was “research prior art.” A comment about the link is “a picture of market information.” Access enabled levels include “Gr 1” and “Gr 2” while the access level is “1.”
• This completes a description of the flowchart appearing in FIG. 8. Here follows a description with reference to FIG. 9, of the flow of processing operations when a document is referenced using a link.[0051]
• (S30) and (S31) are processes involved when a user logs in, however no description is provided here because they are the same processes as (S11) and (S12) respectively.[0052]
• (S32) through (S35) are the steps involved when a document is referenced in relation to input from a user and displayed. Because these steps involve the same processes as (S13) through (S16) respectively no description is provided of them here.[0053]
• (S36) The[0054]document referencing computer4 specifies a particular document and sends to theknowledge managing computer5, a message requesting display of a list of links for other documents related to that document. This message includes information concerning the user and referencing conditions for the link.
• (S37) The[0055]knowledge managing computer5 returns to thedocument referencing computer4, a list of information on links that match the link referencing conditions included in the display link list request message.
• (S38) The[0056]document referencing computer5 pulls the document data specified in the display document request message out from thearchive database2 and delivers this to thedocument referencing computer4.
• This completes a description of the flowchart appearing in FIG. 9. Here follows a description, with reference to FIG. 10, of the detailed flow of processes in (S36) and (S37) concerned with the display of link information. (S36) and (S37) are constructed in detail through the exchange of messages two times.[0057]
• (S50) The[0058]document referencing computer4 specifies a particular document and delivers to theknowledge managing computer5, a message requesting information on links to documents related to that document. The user ID and document ID are included in this message.
• (S51) The[0059]knowledge managing computer5 utilizes the user ID included in this request link information message to acquire from the user information table 40, the user group and access level of the user who originally created the document. Next, the system acquires for the link source document ID of the link information table 30, an equivalent record to the document ID included in the message. From among these records the system selects only the user of the user group and access level that fulfill the conditions for the requisite access enabled group and access levels. For example when “user ID”=“Tanaka” AND “document ID”=“DOC001” are included in the request link information message, the facts that the user group of the user Tanaka is “Gr 1” and the access level is “1” are known from the information recorded in the user information table 40. Next, the information for this link is selected because this user fulfills the conditions for the access enabled group and the access level for the document DOC001 as described in the link information table 30.
• (S52) The[0060]knowledge managing computer5 delivers to thedocument referencing computer4, the link selected, information on the name of the user that corresponds to the user ID and an expertise list from the expertise table 50. If there is no such link information the system returns “no link.”
• (S53) Based on the information thus received the[0061]document referencing computer4 creates a referencing screen which is displayed to the user. In this referencing screen the user is prompted to input referencing conditions for working in a link. FIG. 11 shows an example of a referencing screen.
• (S54) The user inputs the referencing conditions for the link and the[0062]document referencing computer4 sends these referencing conditions to theknowledge managing computer5. The referencing conditions concerned are the link set date, the link setting user, the user group of the link setting user, the job, objective, comments and reference frequency. At this time, in addition to the name of the link setting user, the link setting user may include as optional items, his field of expertise as databases or networks. This means that if a subsequent user wishes only to see links set by a database expert that user can select “databases” for the link setting user. In the referencingscreen70 of FIG. 11 the referencing conditions set include “databases” set for the link setting user, the user group of the link setting user is not required, the job involved was “create report”, and the objective was “research prior art.”
• (S55) The[0063]knowledge managing computer5 performs a comparison between the referencing conditions received and the link information table 30 and acquires the appropriate link information.
• (S56) The[0064]knowledge managing computer5 sends to thedocument referencing computer4 the link information thus acquired and information on the name of the user corresponding to the appropriate user ID.
• (S57) The[0065]document referencing computer4 displays the link information thus received. This completes a description of the flow chart of FIG. 10.
• According to the configuration of the present invention, when the relationships between documents are established in a document referencing system, a variety of conditions may be used to control the display of relationships as manipulated by the user who sets the relationships and a referencing user.[0066]

Claims (22)

1. A document management system for referencing document data from among multiple document data gathered in response to a referencing request from a document referencing part connected via a network, said system comprising:

a storing part for storing said multiple document data;

a receiver part for receiving from said document referencing part, transmission of identifying information that identifies a first document data included amongst said multiple document data, transmission of a request to perform a referencing operation for document data with the appropriate relationship to said first document data and transmission of referencing conditions that provide the conditions for said referencing operation;

a processing part that is connected to said receiving part and to said storing part that, in accordance with a previously stored program and based on said request for performance of a referencing operation, utilizes said identifying information and executes a referencing operation for document data having the appropriate restricted relationship with said first document data in accordance with information defining the appropriate relationship to said first document data, which processing part selects as a result of its referencing operations and from among said document data referenced for having said appropriate relationship, that document data which fulfills said referencing conditions for said information defining the appropriate relationship; and

an output part that is connected to said processing part and to said network that outputs to said network said selected results of referencing operations.

2. A document management system according toclaim 1 wherein said information defining the appropriate relationship shows a restriction applied to either the user requesting the reference operation or said referencing part.

3. A document management system according toclaim 2 wherein said referencing condition includes either of said information identifying the reference requesting user or said information identifying the referencing part.

4. A document management system according toclaim 2 wherein the restrictions concerning said reference requesting user apply to either of said reference requesting user himself or the organization to which said referencing requesting user belongs.

5. A document management system according toclaim 4 wherein the information identifying said reference requesting user is either of information identifying the relevant reference requesting user himself or information identifying the organization to which said reference requesting user belongs.

6. A document management system according toclaim 1 wherein:

said network is connected to a knowledge management part that stores said information defining the appropriate relationship;

said receiver part receives information defining the appropriate relationship for said first document data from said knowledge management part via said network; and

said processing part performs said referencing and selection based on said received information defining the appropriate relationship.

7. A document management system according toclaim 1 wherein

said appropriate relationship is a link between different document data; and

said information defining the appropriate relationship is information showing whether or not such link is applied in accordance with conditions.

8. A document management method for a document management system that manages multiple document data and references from said multiple document data that document data which conforms to a referencing request coming from a document referencing part connected via a network, which methodology includes the following steps:

a step for receiving from said document referencing part via said network, transmission of identifying information that identifies a first document data included amongst said multiple document data, transmitting a request to perform a referencing operation for document data with the appropriate relationship to said first document data and transmitting referencing conditions that provide the conditions for said referencing operation;

a step that operates based on said request for performance of a referencing operation and utilizes said identifying information for executing a referencing operation for document data having the appropriate restricted relationship with said first document data in accordance with information defining the appropriate relationship to said first document data; and

a step for selecting as a result of referencing operations conducted among said document data referenced for having said appropriate relationship, that document data which fulfills said referencing conditions for said information defining the appropriate relationship.

9. A document management method according toclaim 8 wherein said document management system provides a storage means for storing said multiple document data.

10. A document management method according toclaim 8 wherein said information defining the appropriate relationship shows a restriction applied to either the reference requesting user or said referencing part.

11. A document management method according toclaim 10 wherein said referencing condition includes either of said information identifying the reference requesting user or said information identifying the referencing part.

12. A document management method according toclaim 10 wherein the restrictions concerning said reference requesting user are applied to either of the said reference requesting user himself or the organization to which said referencing requesting user belongs.

13. A document management method according toclaim 12 wherein said information identifying the reference requesting user is either of information identifying the relevant reference requesting user himself or information identifying the organization to which said reference requesting user belongs.

14. A document management method according toclaim 8 wherein said document management system connects via a network to said knowledge management part storing information identifying the appropriate relationship and wherein the referencing operation for said document data and the output of said referencing results are executed utilizing the information defining the appropriate relationship stored in said knowledge management part.

15. A document management method according toclaim 8 wherein said appropriate relationship is a link between different document data and wherein said information defining the appropriate relationship is information showing whether or not such link is applied in accordance with conditions.

16. A program loadable in a storage medium from which a computer can retrieve data, which program manages multiple document data, and which program initiates performance of the following steps in a document management part that references from said multiple document data, that document data corresponding to the referencing request coming from a document referencing part connected via a network:

a step for storing said multiple document data;

a step for receiving from said document referencing part via said network, transmitting identifying information that identifies a first document data included amongst said multiple document data, transmitting a request to perform a referencing operation for document data with the appropriate relationship to said first document data and transmitting referencing conditions that provide the conditions for said referencing operation;

a step for performing, based on said request for performance of a referencing operation and utilizing said identifying information, a referencing operation for document data having the appropriate restricted relationship with said first document data; and

a step for selecting as a result of its referencing operations and from among said document data referenced for having said appropriate relationship, that document data which fulfills said referencing conditions for said information defining the appropriate relationship.

17. A program according toclaim 16 wherein said information defining the appropriate relationship shows a restriction applied to either a reference requesting user or said referencing part.

18. A program according toclaim 17 wherein said referencing condition includes either of said information identifying the reference requesting user or said information identifying the referencing part.

19. A program according toclaim 17 wherein the restrictions concerning said reference requesting user are applied to either of said reference requesting user himself or the organization to which said reference requesting user belongs.

20. A program according toclaim 19 wherein the information identifying said reference requesting user is either of information identifying the relevant reference requesting user himself or information identifying the organization to which said reference requesting user belongs.

21. A program according toclaim 16 executing in said document management system, connection via a network to said knowledge management part storing information identifying the appropriate relationship.

22. A program according toclaim 16 wherein said appropriate relationship is a link between different document data and wherein said information defining the appropriate relationship is information showing whether or not such link is applied in accordance with conditions.

Images