WO2024089910A1 - 情報処理方法、情報処理プログラム、情報処理システム - Google Patents

情報処理方法、情報処理プログラム、情報処理システム Download PDF

Info

Publication number
WO2024089910A1
WO2024089910A1 PCT/JP2023/011828 JP2023011828W WO2024089910A1 WO 2024089910 A1 WO2024089910 A1 WO 2024089910A1 JP 2023011828 W JP2023011828 W JP 2023011828W WO 2024089910 A1 WO2024089910 A1 WO 2024089910A1
Authority
WO
WIPO (PCT)
Prior art keywords
document
contract
information processing
information
contracts
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2023/011828
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
瑛美子 乾
究吾 勝田
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LegalOn Technologies Inc
Original Assignee
LegalOn Technologies Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LegalOn Technologies Inc filed Critical LegalOn Technologies Inc
Publication of WO2024089910A1 publication Critical patent/WO2024089910A1/ja
Priority to US19/189,599 priority Critical patent/US20250252129A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/38—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • G06F16/383—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using metadata automatically derived from the content
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/34—Browsing; Visualisation therefor
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/38—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/93—Document management systems

Definitions

  • This disclosure relates to an information processing method, an information processing program, and an information processing system.
  • the document processing server device described in Patent Document 1 searches for document information using search criteria specified by the user among the selected contract type, the search keyword selected from the search keyword display area, and the search keyword entered in the search keyword input field, depending on the user's operation, and displays the search results on the display unit of the terminal.
  • An object of one aspect of the present invention is to provide an information processing method, an information processing program, and an information processing system that make it possible to more easily grasp the existence of related documents.
  • a processor displays a first document stored in a memory unit on a document viewing screen, searches the memory unit for a second document that is separate from the first document and contains information corresponding to attribute information obtained from the first document, displays the second document on the document viewing screen as a candidate document related to the first document, and registers the first document and the second document as related documents based on a user operation.
  • the information processing method, information processing program, and information processing system of the present invention make it easier to determine the existence of related documents.
  • FIG. 1 is a block diagram showing a schematic configuration of an information processing system according to a first embodiment.
  • FIG. 2 is a block diagram showing a schematic configuration of a document management server device according to the first embodiment.
  • 4 is a table showing an example of information stored in a document database according to the first embodiment; 4A and 4B are diagrams showing an example of metadata according to the first embodiment.
  • FIG. 4 is a diagram showing an example of a screen displayed on the terminal device according to the first embodiment.
  • FIG. 4 is a diagram showing an example of a screen displayed on the terminal device according to the first embodiment.
  • FIG. 4 is a diagram showing an example of a screen displayed on the terminal device according to the first embodiment.
  • FIG. 4 is a diagram showing an example of a screen displayed on the terminal device according to the first embodiment.
  • FIG. 4 is a diagram showing an example of a screen displayed on the terminal device according to the first embodiment.
  • FIG. 4 is a diagram showing an example of a screen displayed on the terminal device according to
  • FIG. 4 is a diagram showing an example of a screen displayed on the terminal device according to the first embodiment.
  • 4 is a sequence chart showing an example of the operation of the information processing system according to the first embodiment;
  • 4 is a sequence chart showing an example of the operation of the information processing system according to the first embodiment;
  • FIG. 2 is a block diagram showing an example of a hardware configuration of a document management server device according to the first embodiment.
  • FIG. 13 is a diagram showing an example of data included in a list file of contracts according to the second embodiment.
  • 13A and 13B are diagrams showing a schematic diagram of a linking mode of a contract.
  • the information processing system 10 of this embodiment shown in FIG. 1 is a system that manages documents created by a user.
  • a document is information that is recorded on the premise that it will be referenced.
  • the document includes, for example, official documents, contracts, minutes, rules, notices, regulations, and rules.
  • the document may be in any language, including those written in Japanese, English, Chinese, and the like.
  • the format of the information of each document is not particularly limited, but may be, for example, a data file created by a specific word processing software or the like, or text data extracted from the data file. In the following, a contract will be described as an example of a "document”.
  • an information processing system 10 of the present embodiment includes a document management server device 20 and a terminal device 30.
  • the document management server device 20 and the terminal device 30 are connected to each other via a network line N so as to be able to communicate with each other.
  • the document management server device 20 of this embodiment is a server-type information processing device, and operates in response to a request from the terminal device 30.
  • the document management server device 20 includes electronic components such as a CPU (Central Processing Unit, an example of a processor) having a function for processing information within the main body, a HDD (Hard Disk Drive), and a flash memory (an example of a storage unit).
  • a CPU Central Processing Unit, an example of a processor
  • HDD Hard Disk Drive
  • flash memory an example of a storage unit
  • the document management server device 20 does not necessarily have to be configured as a single information processing device, and may be a device in which multiple information processing devices work together, or may be a device that works by any cloud service.
  • the functions of the document management server device 20 may be realized within the terminal device 30.
  • the processor and storage unit may be any of the multiple information processing devices, and processing may be shared.
  • the terminal device 30 of this embodiment is an information processing device such as a PC (Personal Computer) or a tablet terminal, and is equipped with electronic components such as a CPU (an example of a processor) that has the function of processing information within the main body, and a flash memory (an example of a memory unit).
  • the network line N is a communication network capable of high-speed communication, such as the Internet, an intranet, or a LAN (Local Area Network), or other wired or wireless communication network.
  • each user is assigned account information.
  • the account information includes an identification number and a password.
  • This account information is transmitted from the terminal device 30 to the document management server device 20 when logging in to the system of the document management server device 20, and is used for user authentication in the document management server device 20. Once this authentication is established, the user can use various services provided by the document management server device 20 by operating the terminal device 30. For example, the user can upload and store data of a contract that he or she created to the document management server device 20.
  • the document management server device 20 may also store data of a contract transmitted from any electronic conclusion service.
  • the contract data stored in the document management server device 20 is, for example, data of a contract after it has been concluded.
  • the user can view contracts that he or she created in the past or search for a desired contract from among multiple contracts by operating the terminal device 30 to access the database of the document management server device 20.
  • the document management server device 20 of the present embodiment includes a storage unit 21, a communication unit 22, and a control unit 23.
  • the storage unit 21 is configured with a non-volatile memory such as a HDD or a flash memory.
  • the storage unit 21 is electrically connected to the communication unit 22 and the control unit 23.
  • the storage unit 21 stores a document processing program 210 and a document database 211.
  • the document processing program 210 of this embodiment is executed by the control unit 23.
  • the control unit 23 functions as, for example, various functional units 230 to 235 shown in FIG.
  • the contract body data is electronic data of a contract created or uploaded by a user.
  • the contract electronic data is the content of the contract body converted into electronic data.
  • the electronic data of the contract body may be image information such as PDF, or may be a text file or Word file containing text data.
  • the contract is an example of a first document.
  • the contract identification number is a number assigned individually to each contract.
  • the contract metadata is, for example, data indicating the characteristics of the contract, and includes characteristic words contained in the contents of the contract and data entered separately from the contents of the contract. For example, data such as the title of the contract, the names of the parties to the contract, and the contract date.
  • a related contract is another contract related to the target contract. For example, if the target contract is a service contract, a memorandum concluded to change the contents of the service contract corresponds to a related contract.
  • contract A11 corresponds to a related contract with contract A10
  • the identification number of contract A11 is registered in the related contract identification number field of contract A10
  • the identification number of contract A10 is registered in the related contract identification number field of contract A11, as shown in FIG. 3.
  • the related contract is an example of a second document and corresponds to a related document.
  • the communication unit 22 of this embodiment shown in FIG. 2 functions as a communication interface for communicating with the outside via the network line N shown in FIG. 1.
  • the communication unit 22 is connected to the storage unit 21 and the control unit 23.
  • the communication unit 22 performs various communications with the terminal device 30.
  • the communication unit 22 receives contract text data transmitted from the terminal device 30.
  • the communication unit 22 transmits contract text data stored in the document database 220 to the terminal device 30 in response to a request from the terminal device 30.
  • the control unit 23 of this embodiment is composed of a processor such as a CPU.
  • the control unit 23 is connected to the storage unit 21 and the communication unit 22.
  • the control unit 23 has a document acquisition means 230, a metadata acquisition unit 231, a search term creation unit 232, a candidate document search unit 233, a linking unit 234, and an output control unit 235 as functional components realized by executing the document processing program 210 stored in the storage unit 21.
  • the document acquisition means 230 of this embodiment stores the contract text data in the document database 220.
  • the document acquisition means 230 may convert it into text using OCR (Optical Character Recognition) or the like.
  • the metadata acquisition unit 231 of this embodiment extracts metadata from the contract text data when the contract text data is uploaded from the terminal device 30. Specifically, the metadata acquisition unit 231 executes the first document analysis program to extract information on multiple pre-set target items, such as the contract title, the names of the parties to the contract, and the contract date, from the contract text data as metadata, for example, as shown in FIG. 4(A). Note that FIG. 4(A) illustrates an example in which the metadata acquisition unit 231 extracts "Service Outsourcing Contract” as the contract title, "X Co., Ltd.” and “Y Co., Ltd.” as the names of the parties, and "2022/07/06" as the contract date. The metadata acquisition unit 231 links the extracted metadata to the contract text data and stores it in the document database 220.
  • the metadata acquisition unit 231 may store the unacquired items as blank data in the document database 220. For example, when storing the body data of a contract in the document database 220, if the metadata acquisition unit 231 is able to acquire the title of the contract and the contract date from the body data of the contract as shown in FIG. 4(B), but is unable to extract the names of the parties to the contract, the metadata acquisition unit 231 will keep the field for the names of the parties to the contract as blank data.
  • the metadata acquisition unit 231 may execute a second document analysis program to extract the extraction target items after extracting the information of the extraction target items once. This allows the extraction target items to be acquired more accurately. For example, information on the extraction target items that are null data may be extracted again from the contract body data. For example, when the contract body data stored in the document database 220 is displayed on the terminal device 30, information on the names of the parties to the contract is extracted again from the contract body data. This allows the metadata acquisition unit 231 to acquire information on the items more reliably, even if the items for the names of the parties to the contract are null data as shown in FIG. 4B, that is, even if an item of null data exists in the metadata of the contract. Note that the metadata acquisition unit 231 may execute the process of extracting information on the extraction target items multiple times, regardless of whether the extraction target items include null data or not.
  • the second document analysis program may be the same program as the first document analysis program, or may be a different program, for example, using a different algorithm that can extract metadata with higher accuracy than the first document analysis program.
  • a document analysis program based on named entity extraction can be used as the second document analysis program.
  • the metadata of the contract acquired by the metadata acquisition unit 231 corresponds to the document information acquired from the first document.
  • the metadata of the contract stored in the document database 220 may be manually added or changed by an administrator of the document management server device 20 or on the terminal device 30.
  • the search term creation unit 232 creates search terms based on the metadata of the contract acquired by the metadata acquisition unit 231, for example, when displaying the text data of the contract stored in the document database 220 on the terminal device 30. Search terms are terms used when searching the document database 220 for candidates for related contracts corresponding to the contract displayed on the terminal device 30, and correspond to so-called search queries.
  • the search term creation unit 232 is an example of a search query creation unit.
  • the candidate document search unit 233 searches the document database 220 for candidates for related contracts that correspond to the search terms created by the search term creation unit 232 using a specified search engine.
  • the candidate document search unit 233 calculates the degree of relevance with the search terms for each of the body data of a single or multiple contracts stored in the document database 220 by converting it into a numerical value, and extracts the body data of contracts whose calculated relevance is equal to or greater than a specified value as candidates for related contracts.
  • related contracts or contracts extracted as candidates for related contracts for a certain contract are examples of second documents.
  • the text of the related contract especially the heading, often contains the date of execution of the original contract, the name of the contract, etc., in a way that makes it possible to identify the original contract. Therefore, by extracting such data from the original contract as metadata and using it to perform a full-text search of contracts in the database, it is possible to efficiently present candidates for related contracts.
  • the candidate document search unit 233 may extract candidates for related contracts by using the metadata of each contract stored in the document database 200.
  • the document database 200 stores the text data of two contracts ⁇ and ⁇ that are not linked to each other.
  • the company and the other party described in the text data of contract ⁇ are the same as the company and the other party described in the text data of contract ⁇ , that is, if the parties to contract ⁇ and the parties to contract ⁇ are the same, then those contracts ⁇ and ⁇ are highly likely to be related.
  • cases where the parties to contracts are the same also include cases where they are the same after name matching.
  • candidates for related contracts may be extracted and presented based on that.
  • the items of the metadata for the related contracts may be the same as those for the original contract.
  • the candidate document search unit 233 may not only extract contracts that contain all of the search terms as candidates for related contracts, but may also extract contracts that contain part of the search terms as candidates for related contracts. For example, if the search terms contain the names of three companies as the parties, the candidate document search unit 233 may extract contracts that contain the names of at least two of the three companies as candidates for related contracts. Also, if the search terms contain the title of the contract, the names of the parties to the contract, the contract date, etc., the candidate document search unit 233 may extract contracts that contain at least two of these as candidates for related contracts. It is possible to appropriately adjust the degree of match that a searched contract must have with such search terms to be extracted as a candidate for related contracts.
  • the linking unit 234 registers the information in the document database 220. For example, when the data of contract A10 is displayed on the terminal device 30 and contract A11 is displayed as a candidate related contract corresponding to contract A10, the user performs an operation on the terminal device 30 to link contract A11 to the contract A10 being viewed. In this case, the linking unit 234 adds the identification number of contract A11 to the related contract item in the information of contract A10 registered in the document database 220. Also, the linking unit 234 adds, for example, the identification number of contract A10 to the related contract item in the information of contract A11 registered in the document database 220. As a result, in the document database 220, contract A10 and contract A11 are linked as related contracts.
  • the output control unit 235 displays, for example, information such as the contract text data stored in the document database 220 and related contract candidates extracted by the candidate document search unit 233 on the terminal device 30. As a result, the information transmitted from the output control unit 235 is displayed on the display unit of the terminal device 30.
  • the output control unit 235 reads the body data of the contract from the document database 220 and displays the body data of the contract on the display unit of the terminal device 30.
  • the request to view sent from the terminal device 30 includes, for example, an identification number of the contract to be viewed.
  • Figure 5 shows an example of a document viewing screen 40 on which the body data of the contract is displayed.
  • the document viewing screen 40 is provided with, for example, a document display area 400, a related information display area 401, a first selection button 402, and a second selection button 403.
  • the document display area 400 displays, for example, the contents of the main text of the contract 50 that the user has requested to view.
  • the related information display area 401 displays various information related to the contract 50 being viewed. In this embodiment, the information displayed in the related information display area 401 can be switched by operating a first selection button 402 and a second selection button 403.
  • the metadata of the contract 50 being viewed is displayed in the related information display area 401, for example as shown in FIG. 5.
  • the user can confirm the metadata extracted from the contract 50 being viewed.
  • the metadata is an example of various information related to the contract 50.
  • the related information display area 401 displays, for example, a related contract display area 401a and a candidate contract display area 401b as shown in FIG. 6.
  • the candidate contract display area 401b corresponds to the first display area
  • the related contract display area 401a corresponds to the second display area.
  • the candidate contract display area 401b displays information on candidate related contracts extracted by the candidate document search unit 233.
  • FIG. 6 illustrates an example in which a contract 51 titled "Memorandum of Change of Business Conditions" and a contract 52 titled “Confidentiality Agreement" are extracted as candidates for related contracts.
  • the display area for each contract 51 and 52 displays the names of the parties and the contract date along with the contract title.
  • the metadata information for each contract 51 and 52 stored in the document database 220 is used as information on the title, names of the parties, and contract date of contracts 51 and 52.
  • contract 51 is displayed in priority over contract 52 in the candidate contract display area 401b as shown in FIG. 6. In the user interface of this embodiment, it is displayed at the top. This allows the user to recognize that contract 51 is a contract that is more relevant to contract 50 being viewed than contract 52 when looking at the candidate contract display area 401b.
  • the order in which contracts are displayed may also be determined taking into consideration factors other than relevance. For example, displaying contracts in order of oldest contract conclusion date (the order in which the contracts were concluded) can help users understand the relationships between contracts. This makes it possible to more appropriately link related contracts.
  • the display order may also be determined according to the type of contract. For example, in joint development, contracts are often concluded in the following order: non-disclosure agreement, PoC contract, joint research and development contract, and joint application contract. In other words, there are cases where contracts of a certain type are concluded in a more or less fixed order. By displaying the contracts in an order according to their type, it becomes possible to more appropriately link related contracts.
  • the contents of the contracts 51 and 52 can be displayed by clicking on the titles of the contracts 51 and 52.
  • another document viewing screen 41 shown in FIG. 7 is displayed.
  • the document viewing screen 41 is provided with a document display area 410, a related information display area 411, a first selection button 412, and a second selection button 413, similar to the document viewing screen 40 shown in FIG. 6.
  • the related information display area 411 displays, for example, a related contract display area 411a and a candidate contract display area 411b.
  • the document display area 410 displays the contents of the contract 51.
  • the candidate contract display area 411b displays the contracts 50 and 52 as candidates for related contracts for the contract 51.
  • link buttons 414, 415 are displayed to the left of the portion displaying information on each contract 50, 52.
  • the link buttons 414, 415 are buttons operated when linking the contract 51 being viewed with a candidate related contract.
  • the link buttons are an example of a display for linking contracts. For example, if the user checks the contents of contract 51 on the screen shown in Fig. 7, determines that contract 51 being viewed is a related contract to contract 50, and clicks on link button 414 displayed to the left of contract 50, the contract 51 being viewed and contract 50 are linked to each other. In this case, information on contract 50 is displayed in related contract display area 411a as shown in Fig. 8.
  • the linking operation may be performed by clicking the link button, or may be performed by right-clicking on the contract data to display a menu, or by overlaying the display of the related contract on the display of the original contract and dragging and dropping it, or the like.
  • the output control unit 235 does not display information about contract 51 in the candidate contract display area 411b even if contract 51 is extracted by the candidate document search unit 233 as a candidate for the related contract.
  • an unlink button 416 is displayed on the left side of the contract 50 in the candidate contract display area 401b. This allows the user to easily unlink the contract 51 being viewed from another contract 50 by operating the unlink button 416. Similarly, on the document viewing screen 40 shown in FIG. 9, it is possible to unlink the contract 50 being viewed from another contract 51 by operating the unlink button 406.
  • the unlink button is an example of a display for the operation of unlinking contracts.
  • the operation of unlinking a contract is not limited to clicking the unlink button.
  • a display may be provided to confirm to the user whether or not the user really wants to link or unlink the contract in order to reduce the risk of an erroneous operation.
  • link button 407 shown in Figures 7 to 9 has a similar function to the link button 407 shown in Figure 6.
  • link buttons 404 and 405 shown in Figure 6 and the link button 405 in Figure 9 have a similar function to the link buttons 414 and 415 in Figure 7.
  • the contract viewed by the user on the terminal device 30 will be referred to as the first contract
  • the contract related to the first contract will be referred to as the second contract.
  • the first contract is, for example, a service contract
  • the second contract is, for example, a memorandum of the service contract.
  • the body data of the first contract is stored in the document database 211 of the document management server device 20 (step S20).
  • this first contract corresponds to the first document.
  • the metadata acquisition unit 231 extracts metadata from the body data of the first contract (step S21), and stores the extracted metadata in the document database 211 in association with the body data of the first contract (step S22).
  • the output control unit 235 of the document management server device 20 reads the body data of the first contract requested by the terminal device 30 from the document database 220 (step S23) and transmits it to the terminal device 30 (step S24).
  • the terminal device 30 receives the body data of the first contract transmitted from the document management server device 20 (step S12), it displays the body data of the first contract on the display unit (step S13). This allows the user to view the body data of the first contract.
  • the document management server device 20 transmits the body data of the first contract to the terminal device 30 while searching for related contracts. Specifically, as shown by the dashed line in FIG. 11, if the metadata corresponding to the first contract contains null data, the metadata acquisition unit 231 extracts metadata from the body data of the first contract (step S25) to complement the metadata. Next, the search term creation unit 232 creates a search term based on the metadata extracted by the metadata acquisition unit 231 (step S26). Then, the candidate document search unit 233 searches the document database 220 for candidates for related contracts corresponding to the search term (step S27).
  • the output control unit 235 of the document management server device 20 transmits information on the candidate related contract extracted by the candidate document search unit 233 to the terminal device 30 (step S28).
  • the display unit of the terminal device 30 displays the candidate contracts related to the first contract being viewed (step S15).
  • the linking unit 234 of the document management server device 20 links the first contract being viewed to the second contract (step S29).
  • this second contract corresponds to the second document.
  • a computer 100 includes, for example, a processor 101, a memory 102, a storage device 103, and a communication interface (I/F) unit 104.
  • Computer 100 may be, for example, a cloud computer, a server computer, a personal computer (e.g., desktop, laptop, tablet, etc.), a media computing platform (e.g., cable, satellite set-top box, digital video recorder, etc.), a handheld computing device (e.g., PDA, email client, etc.), or some other type of computer or communications platform.
  • the processor 101 is a control unit that controls various processes in the computer 100 by executing programs stored in the memory 102 .
  • the memory 102 is a storage medium such as a RAM (Random Access Memory), etc.
  • the memory 102 temporarily stores the code of the program executed by the processor 101 and data required when the program is executed.
  • the storage device 103 is a non-volatile storage medium such as a hard disk drive (HDD), a flash memory, etc.
  • the storage device 103 stores an operating system and various programs for implementing the above-mentioned components.
  • the communication interface unit 104 is a device for performing data communication via a network such as the Internet, either wired or wirelessly, with an external device of the computer 100.
  • the communication interface unit 104 may be provided outside the computer 100. When the communication interface unit 104 is provided outside the computer 100, the communication interface unit 104 is connected to the computer 100 via an interface such as a USB.
  • the control unit 23 of the document management server device 20 displays the first contract stored in the document database 211 on the document viewing screen 40 based on user operation, searches the document database 211 for a second contract containing information corresponding to the metadata acquired from the first contract, and displays the second contract on the document viewing screen 40 as a candidate for a related contract related to the first contract.
  • the second contract is displayed on the document viewing screen 40 as a candidate for the corresponding related contract. Therefore, the user can become aware of the existence of related contracts without having to perform a search or the like by himself/herself. This makes it easier to grasp the existence of related contracts.
  • the control unit 23 of the document management server device 20 acquires attribute information corresponding to each of a plurality of target items set in advance as metadata from the first contract.
  • the attribute information is acquired, for example, as text information.
  • the plurality of target items include at least one of the title of the first contract, the parties to the first contract, and the contract date of the first contract.
  • the second contract is searched for based on at least one of the title of the first contract, the parties to the first contract, and the contract date of the first contract, making it easier to search for a second contract related to a first contract.
  • the control unit 23 of the document management server device 20 calculates the degree of relevance between the contents of the second contract and the metadata of the first contract when searching for a second contract related to the first contract from the document database 211.
  • the control unit 23 displays the multiple second contracts in the related contract display area 401a in descending order of relevance. According to this configuration, it is possible to easily recognize that the first second contract displayed among the multiple second contracts displayed in the related contract display area 401a is the contract most related to the first contract, thereby improving user convenience.
  • the control unit 23 of the document management server device 20 acquires metadata from the first contract when storing the first contract in the document database 211. In addition, the control unit 23 acquires metadata from the first contract when displaying the first contract on the document viewing screen 40. With this configuration, metadata can be easily obtained from the first contract.
  • the control unit 23 of the document management server device 20 links the first contract with the second contract. According to this configuration, the first contract and the second contract can be easily linked, thereby improving convenience for the user.
  • the document viewing screen 40 is provided with a candidate contract display area 401b in which a contract 52 that is a candidate for a related contract is displayed, and a related contract display area 401a in which a contract 51 linked to a first contract is displayed.
  • the contract 52 corresponds to the second document
  • the contract 51 corresponds to the third document. According to this configuration, the user can easily check contract 52, which is a candidate contract related to contract 50 being viewed, and contract 51 that is actually linked to contract 50, thereby improving user convenience.
  • control unit 23 of this embodiment further includes a list data output unit 236 as a functional configuration realized by executing the document processing program 210 stored in the memory unit 21.
  • the list data output unit 236 extracts information on all contracts corresponding to the identification number of the user of the terminal device 30 from the document database 220, displays a list display screen on the terminal device 30 on which the extracted contracts can be confirmed in a list, and creates a list file that can display the extracted contracts in a list.
  • this contract list file contains, for each contract, the contract title, the names of the parties, the contract date, the upload date, and a URL (Uniform Resource Locator) that can access the target contract using Web software or the like.
  • this contract list file also contains, for each contract, the title of the related contract linked by the linking unit 234, and a URL that can access the related contract using Web software or the like.
  • the list data output unit 236 transmits the created list file to the terminal device 30. The user can download the list file to the user's terminal and process it using a spreadsheet software or the like.
  • the control unit 23 of the document management server device 20 extracts information on the user's contract or contracts stored in the document database 220, displays a list display screen on which the extracted contract or contracts information can be viewed in a list, and creates a list file that the user can download, including information on other contracts associated with the contract.
  • the user can easily check all of the contracts managed by the document management server device 20.
  • the contract list also displays information about other contracts that are associated with the specified contract, so the user can easily understand the existence of related contracts.
  • FIG. 14(A) is a schematic diagram showing the relationship between the first contract 50 and the second contract 51 and the relationship between the first contract 50 and the third contract 53 shown in FIG. 7. Note that the solid line connecting the first contract 50 and the third contract 53 in FIG. 14(A) indicates that they are linked. In such a case, for example, when the user moves the mouse pointer to the title of the contract 50 in the candidate contract display area 411b shown in FIG.
  • a pop-up or the like may be displayed on the document viewing screen 41 to the effect that another contract 53 is already linked to the contract 50.
  • This configuration makes it easier for the user to recognize that another contract 53 is already linked to the contract 50.
  • it is preferable to display it in a graph so that the relationship between multiple contracts can be easily understood visually.
  • the text of contract 50 may be displayed as a pop-up or the like. This allows the user to easily compare the text of contract 51 displayed in document display area 410 of document viewing screen 41 with the text of contract 50, making it easy to determine whether contract 50 and contract 51 are related.
  • the linking unit 234 may automatically link contract 53 to contract 51 as shown by a dashed line in FIG. 14(B).
  • the document database 211 has been illustrated as a configuration in which various data are managed for each user as shown in FIG. 3, but the method of managing data in the document database 211 is not limited to this.
  • the document database 211 may manage various data for each organization to which multiple users belong. In this case, if there are multiple contract data linked to a specific organization, it is effective to selectively set whether or not to grant access rights to the contract data to each of the multiple users belonging to the specific organization. This makes it possible to prevent unintended users from viewing the contract data.
  • contract B10 and contract B11 are linked in a situation in which a certain user has access rights to contract B10 but does not have access rights to contract B11.
  • contract B10 when the user views the body data of contract B10 on the document viewing screen, text information saying "There is a related contract that you do not have permission to view” may be displayed on the document viewing screen. Furthermore, in such a case, contract B11 may not be displayed as a candidate for a related contract in the candidate contract display area on the document viewing screen.
  • the candidate document search unit 233 can use any extraction method to extract candidates for related contracts, not limited to extraction methods using search terms.
  • the control unit 23 of the document management server device 20 may be equipped with a search query creation unit that constructs a vector (sequence) from the metadata of the contract.
  • the candidate document search unit 233 searches the document database 220 for candidates for related contracts based on the vector constructed by the search query creation unit.
  • the vector corresponds to the search query.
  • the candidate document search unit 233 can extract candidates for related contracts using any method of comparing the characteristics of documents.
  • Processes and procedures described herein as being performed by a single device, software, component, and/or module may be performed by multiple devices, multiple software, multiple components, and/or multiple modules.
  • various information described herein as being stored in a single memory and storage device may be stored in multiple memories included in a single device or in multiple memories distributed across multiple devices.
  • multiple software and hardware described herein may be realized by integrating them into fewer components or by decomposing them into more components.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Library & Information Science (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
PCT/JP2023/011828 2022-10-26 2023-03-24 情報処理方法、情報処理プログラム、情報処理システム Ceased WO2024089910A1 (ja)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US19/189,599 US20250252129A1 (en) 2022-10-26 2025-04-25 Computer-implemented method and information processing system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2022-171072 2022-10-26
JP2022171072A JP2024063280A (ja) 2022-10-26 2022-10-26 情報処理方法、情報処理プログラム、情報処理システム、

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US19/189,599 Continuation US20250252129A1 (en) 2022-10-26 2025-04-25 Computer-implemented method and information processing system

Publications (1)

Publication Number Publication Date
WO2024089910A1 true WO2024089910A1 (ja) 2024-05-02

Family

ID=90830445

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/011828 Ceased WO2024089910A1 (ja) 2022-10-26 2023-03-24 情報処理方法、情報処理プログラム、情報処理システム

Country Status (3)

Country Link
US (1) US20250252129A1 (enExample)
JP (1) JP2024063280A (enExample)
WO (1) WO2024089910A1 (enExample)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090089315A1 (en) * 2007-09-28 2009-04-02 Tractmanager, Inc. System and method for associating metadata with electronic documents
JP2012038333A (ja) * 2005-09-07 2012-02-23 Ricoh Co Ltd 情報処理装置
WO2021038887A1 (ja) * 2019-08-30 2021-03-04 富士通株式会社 類似文書検索方法、類似文書検索プログラム、類似文書検索装置、索引情報作成方法、索引情報作成プログラムおよび索引情報作成装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012038333A (ja) * 2005-09-07 2012-02-23 Ricoh Co Ltd 情報処理装置
US20090089315A1 (en) * 2007-09-28 2009-04-02 Tractmanager, Inc. System and method for associating metadata with electronic documents
WO2021038887A1 (ja) * 2019-08-30 2021-03-04 富士通株式会社 類似文書検索方法、類似文書検索プログラム、類似文書検索装置、索引情報作成方法、索引情報作成プログラムおよび索引情報作成装置

Also Published As

Publication number Publication date
JP2024063280A (ja) 2024-05-13
US20250252129A1 (en) 2025-08-07

Similar Documents

Publication Publication Date Title
US7962464B1 (en) Federated search
US6957384B2 (en) Document management system
US7680856B2 (en) Storing searches in an e-mail folder
US7930301B2 (en) System and method for searching computer files and returning identified files and associated files
US8539334B2 (en) Document management system having automatic notifications
CN102483765B (zh) 文件搜索系统和程序
US9614933B2 (en) Method and system of cloud-computing based content management and collaboration platform with content blocks
US7693866B1 (en) Network-based system and method for accessing and processing legal documents
US11030697B2 (en) Secure document exchange portal system with efficient user access
US20130036348A1 (en) Systems and Methods for Identifying a Standard Document Component in a Community and Generating a Document Containing the Standard Document Component
US20090171961A1 (en) Workflow collaboration in a forensic investigations system
US8589433B2 (en) Dynamic tagging
US7599929B2 (en) Document use tracking system, method, computer readable medium, and computer data signal
Khan et al. Key features of digital library management system (DLMS) for developing digital libraries: An investigation from LIS practitioners in Pakistan
US20110004819A1 (en) Systems and methods for user-driven document assembly
US9824155B2 (en) Automated electronic discovery collections and preservations
US20180232487A1 (en) Document classification tool for large electronic files
US20100325101A1 (en) Marketing asset exchange
US20230143597A1 (en) Methods to infer content relationships from user actions and system automations
US11657228B2 (en) Recording and analyzing user interactions for collaboration and consumption
US7792857B1 (en) Migration of content when accessed using federated search
US20070185832A1 (en) Managing tasks for multiple file types
WO2024089910A1 (ja) 情報処理方法、情報処理プログラム、情報処理システム
Sathiadas et al. Document management techniques and technologies
CN118861295B (zh) 针对超短文本的数据分类分级系统、方法以及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23882128

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 23882128

Country of ref document: EP

Kind code of ref document: A1