Label assignment system, label generation system, label assignment method, label generation method, label assignment program, and label generation program
The labeling system simplifies the management of transaction-related documents in cloud storage by automating the assignment of search labels, addressing the complexity of managing documents in general-purpose storage systems and ensuring compliance with regulatory standards.
Patent Information
- Application Number
- JP2024138462
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-08-20
- Publication Date
- 2024-11-19
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Small and medium-sized enterprises do not use dedicated portal sites for contract management, instead relying on general-purpose storage like cloud storage, which requires complex settings for content-based searches and file overview management, complicating the process.
A labeling system and method that adds search labels to transaction-related document files in cloud storage, utilizing file identification and label identification data, along with label setting condition data, to facilitate easy management and search functionality without manual configuration.
Enables efficient management of transaction-related documents in cloud storage by automating the assignment of search labels, allowing users to perform content-based searches easily and ensuring compliance with regulatory requirements, such as the Electronic Bookkeeping Law, while reducing the effort required for manual data registration.
Smart Images

Figure 2024161534000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a label assignment system, a label generation system, a label assignment method, a label generation method, a label assignment program, and a label generation program. [Background technology]
[0002] As a method for managing transaction-related document files such as digitized contracts, for example, Patent Document 1 has been proposed. Patent Document 1 discloses an electronic contract system that can centrally manage the status of contracts and the like through a dedicated portal site. In the electronic contract system of Patent Document 1, when search conditions are input and a search is performed, a list of extracted contracts is displayed, and the contents and status of the contracts can be confirmed. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Patent Publication No. 2021-05360 Summary of the Invention [Problem to be solved by the invention]
[0004] However, small and medium-sized enterprises and the like may store and manage contracts in general-purpose storage such as cloud storage in a cloud workspace, rather than storing and managing contracts in a dedicated portal site or dedicated application for contract management as in Patent Document 1. Here, when managing transaction-related document files such as contracts on general-purpose storage, the user needs to perform cumbersome setting work, etc., in order to facilitate management, such as enabling the user to perform searches based on content or easily grasp the file overview. Therefore, there is a demand for a system that can facilitate management when using general-purpose storage such as cloud storage without the user having to perform cumbersome setting work.
[0005] The present disclosure provides a label assignment system, a label generation system, a label assignment method, a label generation method, a label assignment program, and a label generation program that enable easy management of transaction-related document files when using general-purpose storage. [Means for solving the problem]
[0006] A labeling system proposed in the present disclosure is a labeling system that assigns search labels to transaction-related document files stored in a cloud storage, and includes: a file reading means that reads out from the cloud storage the transaction-related document file together with file identification data that identifies the transaction-related document file and label identification data that identifies the search label, which are associated with the transaction-related document file; a label setting condition data reading means that reads out label setting condition data that indicates setting conditions for the search label and is stored in the cloud storage in association with the label identification data read from the cloud storage; a transmitting means that transmits the read transaction-related document file, the file identification data, the label setting condition data, and the label identification data to a label generating system; a receiving means that receives data related to the search label generated by the label generating system in accordance with the label setting condition data, together with the file identification data and the label identification data; and a label registration means that stores the data related to the search label in the cloud storage in association with the file identification data and the label identification data.
[0007] The label generation system proposed in the present disclosure includes a receiving means for receiving from a labeling system a transaction-related document file stored in cloud storage, file identification data identifying the transaction-related document file, label identification data identifying a search label to be assigned to the transaction-related document file, and label setting condition data indicating setting conditions for the search label, a label means for generating data related to the search label that satisfies the setting conditions indicated in the label setting condition data based on the transaction-related document file, and a transmitting means for transmitting the generated data related to the search label together with the file identification data and the label identification data to the labeling system.
[0008] A labeling method proposed in the present disclosure is a labeling method for assigning search labels to transaction-related document files stored in a cloud storage, the labeling method including: a file reading step of reading the transaction-related document file from the cloud storage together with file identification data for identifying the transaction-related document file and label identification data for identifying the search label, which are associated with the transaction-related document file; a label setting condition data reading step of reading label setting condition data indicating setting conditions for the search label, which is stored in the cloud storage in association with the label identification data read from the cloud storage; a transmitting step of transmitting the read transaction-related document file, the file identification data, the label setting condition data, and the label identification data to a label generating system; a receiving step of receiving data related to the search label generated by the label generating system in accordance with the label setting condition data, together with the file identification data and the label identification data; and a label registration step of storing the data related to the search label in the cloud storage in association with the file identification data and the label identification data.
[0009] The label generation method proposed in the present disclosure includes a receiving step of receiving from a labeling system a transaction-related document file stored in a cloud storage, file identification data identifying the transaction-related document file, label identification data identifying a search label to be assigned to the transaction-related document file, and label setting condition data indicating setting conditions for the search label; a label generating step of generating data related to the search label that satisfies the setting conditions indicated in the label setting condition data based on the transaction-related document file; and a transmitting step of transmitting the generated data related to the search label together with the file identification data and the label identification data to the labeling system.
[0010] A labeling program proposed in the present disclosure is a labeling program for assigning search labels to transaction-related document files stored in cloud storage, and causes a computer to function as: file reading means for reading from the cloud storage the transaction-related document file together with file identification data for identifying the transaction-related document and label identification data for identifying the search label, which are associated with the transaction-related document file; label setting condition data reading means for reading label setting condition data indicating setting conditions for the search label, which is stored in the cloud storage in association with the label identification data read from the cloud storage; transmitting means for transmitting the read transaction-related document file, the file identification data, the label setting condition data, and the label identification data to a label generating system; receiving means for receiving data related to the search label generated by the label generating system in accordance with the label setting condition data, together with the file identification data and the label identification data; and label registration means for storing the data related to the search label in the cloud storage in association with the file identification data and the label identification data.
[0011] The label generation program proposed in the present disclosure causes a computer to function as a receiving means for receiving from a labeling system a transaction-related document file stored in cloud storage, file identification data identifying the transaction-related document file, label identification data identifying a search label to be assigned to the transaction-related document file, and label setting condition data indicating setting conditions for the search label, a label generating means for generating data relating to the search label that satisfies the setting conditions indicated in the label setting condition data, based on the transaction-related document file, and a transmitting means for transmitting the generated data relating to the search label together with the file identification data and the label identification data to the labeling system. Effect of the Invention
[0012] It is possible to provide a system and a program that make it possible to easily manage transaction-related document files when using general-purpose storage. [Brief description of the drawings]
[0013] [Figure 1] 1 is a diagram illustrating an example of an overall configuration of a document management system according to an embodiment of the present invention. [Figure 2A] FIG. 13 is a diagram showing an example of a screen before a search label is added to a contract file selected by a user. [Figure 2B] FIG. 13 is a diagram showing an example of a screen after a search label has been added to a contract file selected by a user. [Figure 2C] FIG. 13 is a diagram showing an example of a search screen for searching for a contract file. [Diagram 3] FIG. 2 is a functional block diagram showing an example of functions realized by the document management system according to the embodiment. [Figure 4A] FIG. 13 is a diagram showing label setting condition data associated with a label ID. [Figure 4B] FIG. 13 is a diagram showing an example of the configuration of a search label in which attributes are input in label setting condition data. [Diagram 5]FIG. 13 is a diagram showing an example of an employee ID associated with a company ID. [Figure 6A] 10 is a sequence diagram illustrating the flow of a process for creating label setting condition data in the present embodiment. FIG. [Figure 6B] FIG. 11 is a sequence diagram illustrating a process flow relating to label assignment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0014] An example of the document management system S proposed in this disclosure will be described below.
[0015] [Detailed Background] In managing transaction-related document files such as electronic contracts, it is preferable to make efforts to facilitate management, such as by allowing users to perform searches based on the content or easily grasp the overview. One of the reasons for this is that it is required to manage while satisfying certain management requirements required by laws and regulations. For example, the amendment of the "Act on Special Provisions Concerning the Preservation Method of National Tax-Related Books and Documents Prepared Using Electronic Computers (Electronic Book Preservation Act)" (enforced in Japan on January 1, 2022) requires that when storing electronic transaction-related document files, management requirements (storage requirements) including search requirements that make transaction-related document files searchable based on record items such as transaction dates are met. For example, in order to facilitate management by satisfying management requirements when managing transaction-related document files when using cloud storage, the user must operate and input data for each transaction-related document file stored in the cloud storage, which creates the trouble of registering data to satisfy the management requirements for each transaction-related document file. In the cloud workspace, a label (metadata) including the file contents is assigned to a file stored in cloud storage, making it possible to search based on the label or to understand the file contents by accessing the label, but it is necessary to set a label including appropriate content for each transaction-related document file, and registration is time-consuming. Therefore, by using the document management system S proposed in this disclosure, a system is provided that makes it possible to easily manage transaction-related document files when using general-purpose storage such as cloud storage. Below, an example is described in which a cloud workspace, which is an application executed on a cloud server, and cloud storage on the cloud server are used as general-purpose storage.
[0016] [Overview of Document Management System S] The document management system S according to the present embodiment is a system that assigns search labels to contract files stored in cloud storage based on label setting condition data, which is data related to setting conditions (label definition templates) for search labels. Contract files to which search labels are assigned and stored in cloud storage can be searched on a cloud workspace including the cloud storage based on the attributes of the contract file. The assignment of search labels may be performed by an add-on program installed in the cloud workspace. The add-on program is a program that is added to a program that provides the cloud workspace. As long as search labels can be assigned to files in the cloud storage, a program provided in a form different from the add-on program may be used. For example, the program may be executed on a user terminal. The program executed on the user terminal may be, for example, an extension program of a file management program of an OS (Operating System).
[0017] In this embodiment, an example of assigning a search label to a contract file will be described, but the subject to which the search label is assigned is not limited to this. For example, the search label may be assigned to various electronic transaction-related document files used in business transactions, such as quotation files and purchase order files.
[0018] A search label is metadata that makes a contract file searchable on a cloud workspace. A search label includes at least one or more fields. A field is an area in which an attribute indicating specific information contained in a contract file should be set. Each field includes a field ID for identifying the field, attribute type data indicating the type of attribute of the contract file to be entered into the field, and an attribute field in which an attribute corresponding to the attribute type data is entered.
[0019] The types of attributes of a contract file may be, for example, "transaction partner (e.g., "transaction name")," "contract type," "transaction amount," "transaction date" (e.g., "contract conclusion date," "contract start date," "contract end date," etc.), "whether or not the contract is automatically renewed," "contract language," "alert date," etc. For example, when searching for a contract whose attribute corresponding to the contract type is a confidentiality agreement, a specific label (e.g., contract label) attached to the contract file is selected on the search screen on the cloud workspace, and the search word "confidentiality agreement" is entered in the search field for the field whose attribute type is defined as contract type, thereby making it possible to extract a contract file whose attribute is a confidentiality agreement from among a large number of contract files attached with a contract label stored in the cloud storage. In the following, "affixing a search label" means that a search label in which an attribute based on a contract file is input in an attribute field is stored in association with the contract file. Also, "affixing a setting condition for a search label" means that a label in which an attribute based on a contract file is not input in an attribute field is stored in association with the contract file.
[0020] The types of attributes of a contract file should include at least the "transaction partner," "transaction amount," and "transaction date" for transaction-related document files such as contract files. This is to meet the storage requirements for electronic files in the above-mentioned amendment to the Electronic Bookkeeping Act.
[0021] In this embodiment, a user has an account for using the cloud workspace. The user's account is set in the cloud workspace so as to belong to the account (organization account) of the cloud workspace of the organization to which the user belongs. The contract file may be shared by multiple users belonging to the same organization account via cloud storage on the cloud workspace. In addition, only users of accounts (administrator accounts) authorized by the organization's representative or administrator (hereinafter, administrator, etc.) may be able to view the contract file on the cloud workspace. The label setting conditions (label definition template) of the search label are set for each organization account, and users belonging to the organization account can use the same label setting conditions. Note that the organization is not limited to a company unit, and may be a department unit or group unit of the same company.
[0022] In this embodiment, the add-on program and an attribute generation system 30 described below are available only to users of organizations that have signed a contract with a company (hereinafter, provider company) that provides the add-on program and the attribute generation system 30. The organization is, for example, a company having legal personality. The process performed by the provider company for a contracted company will be described below. The provider company assigns company identification data (hereinafter, company ID) that identifies the company and employee identification data (hereinafter, employee ID) that identifies an employee belonging to the company, and stores them in the attribute generation system 30. Here, FIG. 5 shows an example of an employee ID associated with a company ID.
[0023] The company ID or employee ID is used for authentication when accessing the add-on program or the attribute generation system 30. In this case, it is preferable that the employee ID is stored in association with an account in the cloud workspace. In this case, a configuration may be adopted in which access to the add-on program or the attribute generation system 30 is automatically authenticated when a user logs in to the cloud workspace with his or her own account. In addition, the employee ID of a user who has an account such as an administrator in the cloud workspace may be stored in the attribute generation system 30 as an administrator ID.
[0024] [Overall configuration of document management system] Fig. 1 is a diagram showing an example of the overall configuration of a document management system according to this embodiment. As shown in Fig. 1, the document management system S includes a user terminal 10, a document management server 20 which is a label assignment system, and an attribute generation system 30 which is a label generation system. These may be connected to each other via a network N such as the Internet.
[0025] The user terminal 10 is a personal computer. However, the present invention is not limited to this, and the user terminal 10 may be a mobile phone (including a smartphone), a mobile information terminal (including a tablet computer or a wearable terminal), or the like.
[0026] The document management server 20 is a computer that provides cloud storage, which is storage on a cloud server, and a cloud workspace, which is an application executed on the cloud server. Although the document management server 20 configured with one computer is shown in Fig. 1, the document management server 20 may be configured with multiple computers connected to each other via the network N or different networks. The cloud storage is an example of a storage device.
[0027] The attribute generation system 30 is a computer that generates attributes of a contract file, which is data related to a search label, based on the contract file. The attribute generation system 30 may convert the contract file into data (text data, etc.) in an analyzable format using a technology such as OCR (Optical Character Recognition), and then perform text analysis of the data to generate attributes of the contract file. If the contract file is in an analyzable format, OCR may not be performed. Furthermore, the text analysis of the data may be analysis based on a predetermined rule for a character string, or may be analysis using machine learning. The machine learning model is, for example, a Transformer model. Furthermore, the attribute generation system 30 may perform user authentication using an employee ID, issue and manage authentication information that proves that the user is an authenticated user, or determine whether or not the contract file selected by the user is an analyzable file (for example, whether a password is set and the file cannot be opened, whether the file size is too large, etc.) before performing OCR or text analysis. If the attribute generation system 30 determines that the file is not analyzable, it may perform processing to display to the user on the user terminal that the file is not analyzable. Furthermore, the attribute generation system 30 may be configured such that only a user with an administrator ID can perform the process of creating label setting condition data, which will be described later.
[0028] The user may input account information (including an employee ID and password, etc.) on the cloud workspace in which the add-on program is installed, and the user may be authenticated in the attribute generation system 30 based on the input account information. The employee ID may be any ID that can identify the user, and may be an email address, etc. The issuance and management of authentication information is not limited to being performed by the attribute generation system 30, and may be performed by another computer. For example, if the employee ID is an account for the cloud workspace, the attribute generation system 30 may obtain login information for the cloud workspace and authenticate the user.
[0029] Although FIG. 1 shows the attribute generation system 30 configured with one computer, the attribute generation system 30 may be configured with multiple computers connected to each other via the network N or different networks.
[0030] [Hardware configuration of user terminal 10] As shown in FIG. 1, the user terminal 10 includes a control unit 11, a storage unit 12, a communication unit 13, a display unit 14, and an input unit 15. The control unit 11 includes at least one processor. The control unit 11 executes processing according to programs and data stored in the storage unit 12. The storage unit 12 includes a main storage unit and an auxiliary storage unit. For example, the main storage unit is a volatile memory such as a RAM (Random Access Memory), and the auxiliary storage unit is a non-volatile memory such as a ROM (Read Only Memory), an EEPROM (Electrically Erasable and Programmable Read Only Memory), a flash memory, or a hard disk. The communication unit 13 is a communication interface for wired or wireless communication, and performs data communication via a network N.
[0031] The display unit 14 is, for example, a liquid crystal display unit or an organic EL display unit. The display unit 14 displays an image according to an instruction from the control unit 11. The input unit 15 is a pointing device such as a touch panel or a mouse. The input unit 15 may include a keyboard, buttons, etc. The input unit 15 inputs a signal to the control unit 11 in response to an operation by a user.
[0032] [Hardware configuration of document management server 20] 1, the document management server 20 includes a control unit 21, a storage unit 22, and a communication unit 23. The control unit 21 includes at least one processor. The control unit 21 executes processing according to programs and data stored in the storage unit 22. The storage unit 22 includes a main storage unit and an auxiliary storage unit. For example, the main storage unit is a volatile memory such as a RAM, and the auxiliary storage unit is a non-volatile memory such as a ROM, an EEPROM, a flash memory, or a hard disk. The communication unit 23 is a communication interface for wired or wireless communication, and performs data communication via a network N.
[0033] [Hardware configuration of attribute generation system 30] As shown in FIG. 1, the attribute generation system 30 includes a control unit 31, a storage unit 32, and a communication unit 33. The control unit 31 includes at least one processor. The control unit 31 executes processing according to programs and data stored in the storage unit 32. The storage unit 32 includes a main storage unit and an auxiliary storage unit. For example, the main storage unit is a volatile memory such as a RAM, and the auxiliary storage unit is a non-volatile memory such as a ROM, an EEPROM, a flash memory, or a hard disk. The communication unit 33 is a communication interface for wired or wireless communication, and performs data communication via a network N.
[0034] [Example of screen displayed on user terminal 10] 2A to 2C show examples of screens displayed on a user terminal. Fig. 2A is a diagram showing an example of the screen before a search label is assigned to a contract file selected by a user. Fig. 2B is a diagram showing an example of the screen after a search label is assigned to a contract file selected by a user. Fig. 2C is a diagram showing an example of a search screen for searching for a contract file.
[0035] Here, an example will be described in which the screens shown in Figures 2A to 2C are displayed on the display unit 14 by the user terminal 10 accessing the document management server 20 through a web browser. However, the present invention is not limited to this, and these screens may be displayed as a result of processing in which the control unit 11 executes dedicated application software installed in the user terminal 10. Note that the configurations of the screens shown in Figures 2A to 2C are merely examples and may be changed as appropriate.
[0036] The screens shown in Figures 2A to 2C are screens that are displayed as a result of processing executed by the control unit 21 of the document management server 20 of a program that executes the functions of the cloud workspace in which the add-on program has been installed. Also, the "add-on menu" on the right side of the screens shown in Figures 2A to 2C is a screen that is displayed as a result of processing executed by the control unit 21 of the document management server 20 of an add-on program that executes an additional function. Hereinafter, the screen displayed on the right side of the screens shown in Figures 2A to 2C will be referred to as the add-on menu screen. "Customer name," "contract type," and so on displayed on the add-on menu screen indicate the types of attributes of the contract file.
[0037] FIG. 2A shows a list of information related to contract files stored in the document management server 20. Specifically, the file names of contract files are shown in a list. FIG. 2A also shows a contract file with the file name "Confidentiality Agreement (Company X)" being selected. The add-on menu screen in FIG. 2A also shows a state before search labels are added. Since search labels have not been added, each attribute type is set to "Not set." Note that "Not set" may be displayed when a search label setting condition is added to the contract file (when no attribute is input), or "Not set" may be displayed when it is determined that a search label has not been added.
[0038] "Execute Analysis" in Fig. 2A is a button for executing analysis of the contract file in order to assign a search label to the contract file. The user operates the user terminal 10 to click or tap (hereinafter, referred to as "click") on "Execute Analysis" displayed on the screen, thereby executing analysis of the contract file. In other words, processing for assigning a search label to the contract file is executed.
[0039] By executing the analysis of the contract file, attributes corresponding to the attribute type data included in the label setting condition data are assigned to the contract file. FIG. 2B shows an example in which the attribute "Company X" is assigned to "client name". Similarly, FIG. 2B shows an example in which "confidentiality" is assigned to "contract type", "1 million yen" is assigned to "transaction amount", "March 20, 2023" is assigned to "contract conclusion date", "April 1, 2023" is assigned to "contract start date", "March 31, 2024" is assigned to "contract end date", "none" is assigned to "automatic contract renewal", and "Japanese" is assigned to "contract language".
[0040] Although the attributes are generated and automatically set by the attribute generation system 30, they may be editable by a user's input operation. For example, if there is an error in the attribute generated by the attribute generation system 30 or if the attribute is not generated by the attribute generation system 30, the attribute may be corrected or added by a user's input operation. For example, by clicking the "Edit directly" button displayed in FIG. 2B or the like, the attribute becomes editable mode, and the attribute assigned to the label can be corrected or added according to the user's input operation on the user terminal 10.
[0041] FIG. 2C shows an example of a search screen. "Search by label" in FIG. 2C is a button for executing a search. FIG. 2C shows a screen for searching for contract files using the search conditions that the attribute type "client name" includes "Company X" as a keyword indicating the attribute, and the attribute type "contract conclusion date" includes "April 1, 2023" as a keyword indicating the attribute. With the search conditions set in this way, contract files that meet the search conditions can be extracted by clicking "Search by label" or the like.
[0042] The type of attribute may be selected by the user using a pull-down menu, and the type of attribute selected using the pull-down menu is set according to label setting condition data preset by a company administrator or the like.
[0043] FIG. 2C also shows an example in which "List of files being analyzed" and "List of alert files" are displayed on the add-on menu screen. By clicking "List of files being analyzed", a list of contract files for which analysis has not yet been completed after analysis execution has started may be displayed. By clicking "List of alert files", a list of contract files for which the alert date is within a specified period may be displayed. This makes it easier for users to notice the existence of contract files for which renewal should be considered, for example, by setting the alert date three months before the contract expiration date for a contract with automatic renewal.
[0044] [Functions realized by the document management system S] Fig. 3 is a functional block diagram showing an example of functions realized by the document management system according to the present embodiment. Each function shown in Fig. 3 is realized by a computer executing a program stored in a storage unit of each computer. The program may be stored in a computer-readable information storage medium.
[0045] [Functions realized by the document management server 20] The document management server 20 implements a basic function unit 201 that executes basic functions of the document management server 20, and an additional function unit 202 that executes additional functions added to the basic functions. The basic function unit 201 includes a file storage unit 201a and a label setting condition data storage unit 201b that are cloud storage, and a basic control unit 201c. The additional function unit 202 includes a file reading unit 202a, a label setting condition data reading unit 202b, a transmission unit 202c, a display control unit 202d, an attribute receiving unit 202e, and an attribute registration unit 202f. Note that the additional function unit 202 may include some or all of the functions of the basic control unit 201c.
[0046] The file storage unit 201a and the label setting condition data storage unit 201b are realized mainly by the storage unit 22. The basic control unit 201c is realized mainly by the control unit 21. The file reading unit 202a, the label setting condition data reading unit 202b, the display control unit 202d, and the attribute registration unit 202f are realized mainly by the control unit 21. The transmission unit 202c and the attribute reception unit 202e are realized mainly by the communication unit 23.
[0047] The file storage unit 201a stores a contract file, file identification data (hereinafter referred to as a file ID) for identifying the contract file, and label identification data (hereinafter referred to as a label ID) for identifying a search label, in association with each other. The file storage unit 201a preferably stores the contract file in a manner accessible by a uniform resource locator (URL) that identifies the location on the Internet.
[0048] The label setting condition data storage unit 201b stores label setting condition data relating to the setting conditions of the search label and the label ID in association with each other.
[0049] The label setting condition data and the search label will now be described with reference to Figures 4A and 4B. Figure 4A is a diagram showing the label setting condition data associated with a label ID.
[0050] The label setting condition data is data indicating the setting conditions of the search label. In this embodiment, the label setting condition data is data including, for each of one or more fields included in the search label, field identification data (hereinafter, field ID) that identifies the field, attribute type data that indicates the type of attribute of the contract file to be set in the field, and an attribute field.
[0051] 4A shows an example in which label IDs "L001" to "L00N" are associated with an organization ID (organization identification data that identifies the organization to which a user belongs), which is an organization account in a cloud workspace. In addition, the label setting condition data associated with the label ID shown in FIG. 4A includes attribute type data 01 to 10, and for example, the attribute type data 01 to 10 of the label ID "L001" are associated with field IDs "L001F01" to "L001F10", respectively. For example, if the label ID "L001" is a label for a contract, the attribute type data 01 is the client name.
[0052] The number, contents, order, etc. of attribute type data included in the label setting condition data may be arbitrarily set by a company administrator, etc.
[0053] The number of label IDs associated with one contract file is not limited to one, and two or more label IDs may be associated with one contract file. The user may be able to select which label ID is associated with the label setting condition data to assign a search label to the contract file. The attribute may be generated based on the label setting condition data associated with the label ID selected by the user.
[0054] Also, one label ID may be associated with multiple contract files. By using a common label ID associated with an organization ID within the same organization, a unified search label can be assigned to multiple contract files managed in cloud storage. This makes it possible to search for contract files that have been assigned labels based on common label setting conditions (e.g., contract label setting conditions) based on attributes assigned to the labels in the cloud workspace.
[0055] FIG. 4B is a diagram showing an example of the configuration of a search label in which attributes are input to the label setting condition data. The "field item" shown in FIG. 4B corresponds to the "attribute type data" of the label setting condition data, and the "field information" shown in FIG. 4B is an area corresponding to the "belonging field" of the label setting condition data. FIG. 4B shows 10 fields included in the search label. For example, FIG. 4B shows a search label in which the attribute "Company A" is input in the attribute field corresponding to the attribute type data "client name" associated with the field ID "L001F01" in the first field. The label setting condition data may include information regarding the sorting order of the field IDs for each label ID. Then, as shown in FIG. 2B, each field may be displayed in order from the top based on the information regarding the sorting order.
[0056] The label setting condition data may include attribute type data indicating the type of attribute generated by selecting one of two or more options, and option identification data (hereinafter, option ID) for identifying the option. The attribute generated corresponding to the attribute type data indicating the type of attribute generated by selecting one of two or more options may be, for example, the presence or absence of automatic contract renewal. In FIG. 4B, a search label in which the attribute "Yes" is input is shown in the label setting condition data including option IDs "L001F08C01" and "L001F08C02" associated with the field ID "L001F08" (field item "automatic contract renewal"). The two or more options may be set in advance. The number of options may be three or more. The option ID, the label ID, and the field ID described above may be composed of an irregular character string (hash value) generated by a specific algorithm. For example, each ID may be a 32-digit hexadecimal number. It is preferable that each ID is a value that is uniquely determined in all organizations to which the cloud workspace is provided. Since each ID is generated by the cloud workspace, it is preferable to obtain a target ID from the cloud workspace and send the target ID to the cloud workspace when executing an instruction regarding the label.
[0057] Returning to FIG. 3, among the functions realized by the document management server 20, the functions realized by the additional function unit 202 will be described.
[0058] The file reading unit 202a reads out a contract file selected by a user operating the user terminal 10 from the file storage unit 201a together with the file ID and label ID associated with the contract file. Note that the functions executed by the file reading unit 202a are commands to the basic control unit 201c, and it is preferable that the reading control of the contract file and the like executed in response to commands from the file reading unit 202a be performed by the basic control unit 201c.
[0059] The label setting condition data reading unit 202b reads out the label setting condition data stored in the label setting condition data storage unit 201b in association with the label ID read out from the file storage unit 201a. Note that the functions executed by the label setting condition data reading unit 202b are commands to the basic control unit 201c, and the reading control of the label setting conditions executed in response to commands from the label setting condition data reading unit 202b is preferably performed by the basic control unit 201c.
[0060] The transmission unit 202c transmits the contract file, file ID, label setting condition data, and label ID read by the file reading unit 202a and the label setting condition data reading unit 202b to the attribute generation system 30. Note that the functions executed by the transmission unit 202c are commands to the basic control unit 201c, and the transmission control of the contract file and the like executed by commands from the transmission unit 202c is preferably performed by the basic control unit 201c. In other words, the basic control unit 201c may read the contract file and label setting condition data in response to commands from the file reading unit 202a and the label setting condition data reading unit 202b, and transmit the contract file and label setting condition data read in response to commands from the transmission unit 202c to the attribute generation system 30.
[0061] The display control unit 202d displays various screens on the user terminal 10. The display control unit 202d transmits display data of a screen to be displayed to the user terminal 10, thereby displaying the screen on the display unit 14 of the user terminal 10. The display data may be in any data format, and may be, for example, HTML (Hyper Text Markup Language) data.
[0062] In this embodiment, the display control unit 202d may transmit display data for displaying an add-on menu screen among the screens shown in Figures 2A to 2C to the user terminal 10, thereby causing the screen to be displayed on the display unit 14 of the user terminal 10. Note that the functions executed by the display control unit 202d are instructions to the basic control unit 201c, and the display control executed in response to instructions from the display control unit 202d may be performed by the basic control unit 201c.
[0063] The attribute receiving unit 202e receives each attribute of the contract file generated by the attribute generation system 30, and the field ID, file ID, and label ID associated with each attribute from the attribute generation system 30. Note that the functions executed by the attribute receiving unit 202e are commands to the basic control unit 201c, and the reception control of attributes and the like executed by commands from the attribute receiving unit 202e may be performed by the basic control unit 201c.
[0064] The attribute registration unit 202f stores each attribute in the file storage unit 201a in association with the file ID, label ID, and field ID. The attribute registration unit 202f may store each attribute according to the structure of the label setting condition data. This results in the attributes being registered in the contract file stored in the file storage unit 201a. Note that the functions executed by the attribute registration unit 202f are commands to the basic control unit 201c, and attribute registration control executed in response to commands from the attribute registration unit 202f may be performed by the basic control unit 201c.
[0065] After the attribute receiving unit 202e receives the attributes, the display control unit 202d may display a confirmation screen on the display unit 14 of the user terminal 10 together with the received attributes. In the confirmation screen, for example, a sentence such as "Are these the attributes to be entered?" may be displayed. Then, the attribute registration unit 202f may register attributes in each attribute field in response to an input operation of the user terminal 10 by a user who has confirmed the confirmation screen. In the confirmation screen, it is preferable that attributes can be changed or added in response to an input operation of the user terminal 10 by a user. In addition, in the confirmation screen, an alert date may be set in response to an input operation of the user terminal 10 by a user. In the above-mentioned FIG. 4B, an example is shown in which "September 1, 2023" is registered in the field item "alert date" associated with the field ID "L001F10". Since a corresponding attribute is not generated in the attribute generation system 30 for this field item, it is preferable that the user can arbitrarily set it.
[0066] [Functions realized by the attribute generation system 30] In the attribute generation system 30, a receiving unit 301, an attribute generation unit 302, an attribute storage unit 303, and an attribute transmission unit 304 are realized. The receiving unit 301 and the attribute transmission unit 304 are realized mainly by the communication unit 33. The attribute generation unit 302 is realized mainly by the control unit 31. The attribute storage unit 303 is realized mainly by the storage unit 32.
[0067] The receiving unit 301 receives the contract file, the file ID, the label setting condition data, and the label ID transmitted from the transmitting unit 202c.
[0068] The attribute generation unit 302 generates attributes corresponding to attribute type data of each field included in the label setting condition data based on the contract file. For example, when the label setting condition data has the data structure shown in Fig. 4A, the attribute generation unit 302 may generate attributes corresponding to attribute type data 1 to 10 based on the contract file. Note that when the label setting condition data includes attribute type data indicating the type of attribute to be generated by selecting one of two or more options, the attribute generation unit 302 may select an attribute corresponding to the attribute type data from the options and generate it.
[0069] The attribute generating unit 302 may analyze the contract file by an analysis method according to the type of attribute and generate the attribute. Therefore, the attribute generating unit 302 may include a plurality of generating units with different analysis methods. For example, the first generating unit 302a may generate attributes related to the date. For example, the first generating unit 302a may generate attributes corresponding to the contract conclusion date, the contract start date, and the contract end date based on the contract file. Specifically, for example, the first generating unit 302a may generate the "date" written near the term "conclusion" as an attribute of the "contract conclusion date". In addition, for example, the second generating unit 302b may generate attributes related to the type of the contract using a trained model. In this case, the trained model may be a model generated by learning from training data including a contract file with which the type is associated. Note that the analysis method described here is an example, and the attribute generating unit 302 may include a generating unit that employs another analysis method. Furthermore, the attribute may be data indicating the extracted wording, or may be data corresponding to the extracted wording.
[0070] The data format of the contract file analyzed by the attribute generation unit 302 is preferably PDF (Portable Document Format) or the like, but is not limited to this. Also, the contract file may or may not include text data.
[0071] The attribute storage unit 303 stores each attribute generated by the attribute generation unit 302 in association with the file ID, the label ID, and the field ID. When the label setting condition data includes attribute type data indicating the type of attribute to be generated by selecting one of two or more options and an option ID corresponding to the attribute type data, the attribute storage unit 303 may store the attribute generated by selecting one of the options in association with the option ID.
[0072] When a predetermined action is performed by a user in the cloud workspace, the attribute transmission unit 304 transmits each attribute stored in the attribute storage unit 303 together with the field ID, file ID, and label ID associated with the attribute to the document management server 20. The predetermined action may be, for example, a login by an authenticated user terminal 10, an operation being performed on the cloud workspace, or the selection of an analyzed contract file.
[0073] [Sequence diagram] Next, the flow of processing in this embodiment will be described with reference to Fig. 6A and Fig. 6B. Fig. 6A is a sequence diagram for explaining the flow of processing for creating label setting condition data in this embodiment. Fig. 6B is a sequence diagram for explaining the flow of processing related to label attachment.
[0074] First, an administrator of a company installs an add-on program for executing the additional function unit 202. Thereafter, as shown in FIG. 6A, a process for creating label setting condition data is executed in response to an input operation of the administrator on the user terminal 10. Specifically, first, the administrator performs an input operation to command the document management server 20 to execute the creation of label setting condition data associated with an organization ID (S1). For example, the execution of the creation of label setting condition data may be commanded by clicking a "label creation" button displayed on the user terminal 10 by the function of the add-on program. In the document management server 20 that receives the command, the function of the add-on program creates label setting condition data associated with the organization ID (S2). That is, label setting condition data as shown in FIG. 4A is generated. The created label setting condition data is stored in the label setting condition data storage unit 201b in association with the label ID (S3). Thereafter, a display is displayed on the user terminal 10 to report the completion of the creation of the label setting condition data (S4). With the above, the process for creating label setting condition data, which is a pre-processing of the process related to labeling, is completed. It is preferable that the basic control unit 201c controls the creation, storage, and display of the label setting condition data.
[0075] In addition, by an administrator or the like installing the add-on program, an employee who has an account belonging to an organization ID in the cloud workspace and has been assigned an employee ID associated with the company ID may be able to use the functions of the add-on program (i.e., the additional functions executed by the additional function unit 202) on his / her own user terminal 10. Alternatively, after an administrator or the like installs the add-on program, each employee may individually install the add-on program on his / her own user terminal 10, thereby enabling the functions of the add-on program to be used on his / her own user terminal 10.
[0076] 6B, the document management server 20 accepts the selection of a contract file in response to an employee's operation of the user terminal 10 (S101). In the document management server 20, the file reading unit 202a reads the selected contract file from the file storage unit 201a together with the file ID and label ID associated with the contract file (S102). Also, in the document management server 20, the label setting condition data reading unit 202b reads the label setting condition data stored in the label setting condition data storage unit 201b in association with the label ID read from the file storage unit 201a (S103).
[0077] Furthermore, in the document management server 20, the transmitting unit 202c transmits the read contract file, file ID, label setting condition data, and label ID to the attribute generation system 30 (S104).
[0078] In the attribute generation system 30, the receiving unit 301 receives the contract file, the file ID, the label setting condition data, and the label ID. After that, the attribute generation system 30 transmits an instruction to the document management server 20 to cause the user terminal 10 to display a message indicating that analysis is in progress (S105).
[0079] In the document management server 20, the display control unit 202d causes the display unit 14 of the user terminal 10 to display, via the web browser, a message indicating that analysis is in progress (S106).
[0080] In the attribute generation system 30, the attribute generation unit 302 generates attributes corresponding to the attribute type data of each field included in the label setting condition data based on the contract file (S107). In the attribute generation system 30, the attribute storage unit 303 stores each attribute generated by the attribute generation unit 302 in association with the file ID, label ID, and field ID (S108).
[0081] Furthermore, the document management server 20 accepts the selection of the contract file in response to the employee's operation of the user terminal 10 (S109). The document management server 20 requests the attribute generation system 30 to transmit the attributes of the selected contract file (S110).
[0082] In the attribute creation system 30 that has received the request, the attribute sending unit 304 sends each attribute stored in the attribute memory unit 303 to the document management server 20 together with the field ID, file ID, and label ID associated with that attribute (S111).
[0083] In the document management server 20, the attribute receiving unit 202e receives each attribute and the field ID, file ID, and label ID associated with each attribute. Then, in the document management server 20, the attribute registration unit 202f stores each attribute in the file storage unit 201a in association with the file ID, label ID, and field ID (S112). In other words, each attribute is registered in the contract file.
[0084] [summary] In the document management system S according to the present embodiment described above, when using general-purpose storage such as cloud storage, the user can easily assign search labels to transaction-related document files without performing complicated settings related to the search labels. This makes it easier to manage transaction-related document files, such as by allowing transaction-related document files to be stored in cloud storage while satisfying certain management requirements. By operating and inputting data in a cloud workspace or the like, the user can eliminate the need to register attributes, etc., for each of a number of contract files.
[0085] In addition, by assigning search labels to contract files based on search label setting conditions preset by a company administrator or the like, uniformity of search label setting conditions is ensured for contract files shared in cloud storage by employees belonging to the same company. This makes it possible to improve the efficiency of contract file management and prevent search omissions, etc. For example, in a cloud workspace, users belonging to a specific organizational account can search for transaction-related document files labeled with a common search label by label field.
[0086] [others] In the present embodiment, the attribute generation system 30 has been described as an example of a label generation system, but the present invention is not limited to this. The label generation system may be any system that generates data related to search labels that satisfy the setting conditions indicated in the label setting condition data based on a transaction-related document file.
[0087] 6, the transmitting unit 202c may also transmit the company ID in association with the label setting condition data. When an error occurs in the generation of an attribute, the attribute generation system 30 may store information about the error in association with the company ID.
[0088] In addition, the types of attributes of the contract file are not limited to those shown in FIG. 2B, and may include, for example, the relationship between the transaction-related document file to which the search label is added and other transaction-related document files related thereto. That is, the correspondence between contract files may be set as an attribute. Specifically, for example, a file ID associated with a contract file before the contract is concluded may be set as an attribute of a contract file for which a contract has been concluded. In this case, for example, the attribute generation system 30 may store contract files analyzed in the past and determine whether the contract file analyzed in the past is similar to the contract file currently being analyzed. If it is determined that they are similar, the file ID of the contract file analyzed in the past may be set as an attribute.
[0089] In the present embodiment, an example has been described in which the label setting condition data includes a field ID and attribute type data as shown in Fig. 4A, but the present invention is not limited to this, and the label setting condition data may be data including only a label ID, or the label ID itself. In this case, in the attribute generation system 30, the receiving unit 301 may receive the label ID, and the attribute generating unit 302 may generate an attribute corresponding to the attribute type data pre-stored in the attribute generation system 30. Then, the attribute transmitting unit 304 may transmit the generated attribute to the document management server 20 in association with the label ID. In this case, in the attribute generation system 30, a plurality of attribute type data may be pre-stored in association with information regarding the order so as to correspond to the display order in the search label.
[0090] In the present embodiment, an example in which one label setting condition data is used has been described, but a configuration may be adopted in which a program can create a plurality of different label setting condition data, and the attribute generation system 30 receives the label setting condition data selected by the user. The attribute generation system 30 may further include a plurality of attribute generation units, and the attribute generation unit to be used may be different depending on the selected label setting condition data. For example, when the attribute generation system 30 determines that a label for a contract has been received, it may perform analysis using an attribute generation unit for contract analysis, and when it determines that a label for an invoice has been received, it may perform analysis using an attribute generation unit for invoice analysis. In addition, a configuration may be adopted in which an external attribute generation unit is used for some of the label setting condition data. In addition, labels may be assigned to transaction-related document files in local storage, not to transaction-related document files in cloud storage. In addition, labels may be assigned using an extension program of a file management program of the OS. For example, a file management program of the OS may function as a basic function unit, and an extension program for the file management program may function as an additional function unit, and label setting condition data may be sent to an attribute generation system on the cloud through operation of the extension program, attributes generated by the attribute generation system may be received, and labels may be assigned to transaction-related document files in general-purpose storage such as cloud storage that can be accessed via the OS.
[0091] [Note] For example, the label assignment system, the label generation system, the label assignment method, the label generation method, the label assignment program, and the label generation program may be configured as follows. (1) A labeling system that assigns search labels to transaction-related document files stored in a cloud storage device, comprising: a file reading means for reading the transaction-related document file from the cloud storage together with file identification data for identifying the transaction-related document file and label identification data for identifying the search label, the file identification data being associated with the transaction-related document file; a label setting condition data reading means for reading label setting condition data indicating setting conditions of the search label, the label setting condition data being stored in the cloud storage in association with the label identification data read from the cloud storage; a transmitting means for transmitting the read transaction related document file, the file identification data, the label setting condition data, and the label identification data to a label production system; a receiving means for receiving data relating to the search label generated by the label generating system in accordance with the label setting condition data, together with the file identification data and the label identification data; a label registration means for storing data relating to the search label in association with the file identification data and the label identification data in the cloud storage; A labeling system including: (2) In paragraph (1), the label setting condition data includes, for each of one or more fields included in the search label, field identification data for identifying the field, and attribute type data indicating the type of attribute of the transaction-related document file to be set in the field; the receiving means receives the attributes, which are data related to the search label and correspond to the attribute type data of each of the fields included in the label setting condition data, generated by the label generating system; the label registration means causes the cloud storage to store the attribute in association with the file identification data and the label identification data; Labeling system. (3) a receiving means for receiving from a labeling system a transaction-related document file stored in a cloud storage, file identification data for identifying the transaction-related document file, label identification data for identifying a search label to be assigned to the transaction-related document file, and label setting condition data indicating setting conditions for the search label; a label generating means for generating data relating to the search label that satisfies the setting conditions indicated in the label setting condition data based on the transaction related document file; a transmitting means for transmitting data relating to the generated search label together with the file identification data and the label identification data to the labeling system; A label generation system including: (4) In paragraph (3), the label setting condition data includes, for each of one or more fields included in the search label, field identification data for identifying the field, and attribute type data indicating the type of attribute of the transaction-related document file to be set in the field; the label generating means generates the attribute, which is data related to the search label, corresponding to the attribute type data of each of the fields included in the label setting condition data; the transmitting means transmits the attribute together with the file identification data and the label identification data to the labeling system; Label generation system. (5) In paragraph (4), the attribute storage means for storing the attributes in association with the file identification data, the label identification data, and the field identification data; the transmitting means transmits each of the attributes stored in the attribute storage means to the labeling system together with the field identification data, the file identification data, and the label identification data associated with the attribute; Label generation system. (6) In paragraph (4) or (5), the label generating means analyzes the transaction related document file using an analysis method corresponding to the type of the attribute to generate the attribute; Label generation system. (7) In any of (4) to (6), the transaction-related document file is stored in the cloud storage in association with at least first label identification data for identifying a first search label and second label identification data for identifying a second search label; the label generating means generates the attribute corresponding to the attribute type data included in label setting condition data indicating setting conditions of a search label selected by a user from the first search label and the second search label, based on the transaction related document file; Label generation system. (8) In any of (4) to (7), The types of attributes include at least the transaction counterparty, transaction amount, and transaction date related to the transaction related document file; Label generation system. (9) In any of (4) to (8), the type of attribute includes a relationship between the transaction related document file to which the search label is assigned and other transaction related document files; Label generation system. (10) In any of (4) to (9), The label setting condition data is associated with organization identification data that identifies an organization to which a user belongs in a cloud workspace that includes the cloud storage. Label generation system. (11)(5) In paragraph (5), the label setting condition data includes the attribute type data indicating a type of the attribute selected from two or more options, and option identification data identifying the option, the label generating means generates the attribute corresponding to the attribute type data by selecting one of the options; the attribute storage means stores the attribute generated by selecting one of the options in association with the option identification data; Label generation system. (12) A labeling method for assigning search labels to transaction-related document files stored in a cloud storage, comprising the steps of: a file reading step of reading the transaction related document file from the cloud storage together with file identification data associated with the transaction related document file, the file identification data identifying the transaction related document file, and label identification data identifying the search label; a label setting condition data reading step of reading label setting condition data indicating setting conditions of the search label, the label setting condition data being stored in the cloud storage in association with the label identification data read from the cloud storage; a transmitting step of transmitting the read transaction related document file, the file identification data, the label setting condition data, and the label identification data to a label production system; a receiving step of receiving data relating to the search label generated by the label generating system in accordance with the label setting condition data, together with the file identification data and the label identification data; a label registration step of storing data related to the search label in association with the file identification data and the label identification data in the cloud storage; A labeling method including: (13) a receiving step of receiving from a labeling system a transaction-related document file stored in a storage device, file identification data for identifying the transaction-related document file, label identification data for identifying a search label to be assigned to the transaction-related document file, and label setting condition data indicating setting conditions for the search label; a label generating step of generating data relating to the search label that satisfies the setting conditions indicated in the label setting condition data based on the transaction related document file; a transmitting step of transmitting data relating to the generated search label together with the file identification data and the label identification data to the labeling system; A label generation method including: (14) A labeling program for assigning search labels to transaction-related document files stored in a cloud storage, comprising: a file reading means for reading the transaction-related document file from the cloud storage together with file identification data for identifying the transaction-related document and label identification data for identifying the search label, the file identification data being associated with the transaction-related document file; a label setting condition data reading means for reading label setting condition data indicating setting conditions of the search label, the label setting condition data being stored in the cloud storage in association with the label identification data read from the cloud storage; a transmitting means for transmitting the read transaction related document file, the file identification data, the label setting condition data, and the label identification data to a label production system; a receiving means for receiving data relating to the search label generated by the label generating system in accordance with the label setting condition data, together with the file identification data and the label identification data; a label registration means for storing data relating to the search label in association with the file identification data and the label identification data in the cloud storage; A labeling program that enables a computer to function as a (15) a receiving means for receiving from a labeling system a transaction-related document file stored in a storage device, file identification data for identifying the transaction-related document file, label identification data for identifying a search label to be assigned to the transaction-related document file, and label setting condition data indicating setting conditions for the search label; a label generating means for generating data relating to the search label that satisfies the setting conditions indicated in the label setting condition data based on the transaction related document file; a transmitting means for transmitting data relating to the generated search label together with the file identification data and the label identification data to the labeling system; A label generation program that allows a computer to function as a [Explanation of symbols]
[0092] 10 user terminal, 11 control unit, 12 memory unit, 13 communication unit, 14 display unit, 15 input unit, 20 document management server, 21 control unit, 22 memory unit, 23 communication unit, 30 attribute generation system, 31 control unit, 32 memory unit, 33 communication unit, 201 basic function unit, 201a file memory unit, 201b label setting condition data memory unit, 201c basic control unit, 202 additional function unit, 202a file reading unit, 202b label setting condition data reading unit, 202c transmission unit, 202d display control unit, 202e attribute receiving unit, 202f attribute registration unit, 301 receiving unit, 302 attribute generation unit, 303 attribute memory unit, 304 attribute transmission unit, S document management system.
Claims
1. A labeling system that assigns search labels to transaction-related document files stored in a cloud storage, comprising: a file reading means for reading the transaction-related document file from the cloud storage together with file identification data for identifying the transaction-related document file and label identification data for identifying the search label, the file identification data being associated with the transaction-related document file; a label setting condition data reading means for reading label setting condition data indicating setting conditions of the search label, the label setting condition data being stored in the cloud storage in association with the label identification data read from the cloud storage; a transmitting means for transmitting the read transaction related document file, the file identification data, the label setting condition data, and the label identification data to a label production system; a receiving means for receiving data relating to the search label generated by the label generating system in accordance with the label setting condition data, together with the file identification data and the label identification data; a label registration means for storing data relating to the search label in association with the file identification data and the label identification data in the cloud storage; A labeling system including:
2. 2. The labeling system of claim 1, the label setting condition data includes, for each of one or more fields included in the search label, field identification data for identifying the field, and attribute type data indicating a type of attribute of the transaction-related document file to be set in the field; the receiving means receives the attributes, which are data related to the search label and correspond to the attribute type data of each of the fields included in the label setting condition data, generated by the label generating system; the label registration means causes the cloud storage to store the attribute in association with the file identification data and the label identification data; Labeling system.
3. a receiving means for receiving from a labeling system a transaction-related document file stored in a cloud storage, file identification data for identifying the transaction-related document file, label identification data for identifying a search label to be assigned to the transaction-related document file, and label setting condition data indicating setting conditions for the search label; a label generating means for generating data relating to the search label that satisfies the setting conditions indicated in the label setting condition data based on the transaction related document file; a transmitting means for transmitting data relating to the generated search label together with the file identification data and the label identification data to the labeling system; A label generation system including:
4. 4. The label generating system according to claim 3, the label setting condition data includes, for each of one or more fields included in the search label, field identification data for identifying the field, and attribute type data indicating a type of attribute of the transaction-related document file to be set in the field; the label generating means generates the attribute, which is data related to the search label, corresponding to the attribute type data of each of the fields included in the label setting condition data; the transmitting means transmits the attribute together with the file identification data and the label identification data to the labeling system; Label generation system.
5. 5. The label generating system according to claim 4, the attribute storage means for storing the attributes in association with the file identification data, the label identification data, and the field identification data; the transmitting means transmits each of the attributes stored in the attribute storage means to the labeling system together with the field identification data, the file identification data, and the label identification data associated with the attribute; Label generation system.
6. 5. The label generating system according to claim 4, the label generating means analyzes the transaction related document file using an analysis method corresponding to the type of the attribute to generate the attribute; Label generation system.
7. 5. The label generating system according to claim 4, the transaction-related document file is stored in the cloud storage in association with at least first label identification data for identifying a first search label and second label identification data for identifying a second search label; the label generating means generates the attribute corresponding to the attribute type data included in label setting condition data indicating setting conditions of a search label selected by a user from the first search label and the second search label, based on the transaction related document file; Label generation system.
8. 5. The label generating system according to claim 4, The types of attributes include at least the transaction counterparty, transaction amount, and transaction date related to the transaction related document file; Label generation system.
9. 5. The label generating system according to claim 4, the type of attribute includes a relationship between the transaction related document file to which the search label is assigned and other transaction related document files; Label generation system.
10. 5. The label generating system according to claim 4, The label setting condition data is associated with organization identification data that identifies an organization to which a user belongs in a cloud workspace that includes the cloud storage. Label generation system.
11. 6. The label generating system according to claim 5, the label setting condition data includes the attribute type data indicating a type of the attribute selected from two or more options, and option identification data identifying the option, the label generating means generates the attribute corresponding to the attribute type data by selecting one of the options; the attribute storage means stores the attribute generated by selecting one of the options in association with the option identification data; Label generation system.
12. A labeling method for assigning search labels to transaction-related document files stored in a cloud storage, comprising the steps of: a file reading step of reading the transaction related document file from the cloud storage together with file identification data associated with the transaction related document file, the file identification data identifying the transaction related document file, and label identification data identifying the search label; a label setting condition data reading step of reading label setting condition data indicating setting conditions of the search label, the label setting condition data being stored in the cloud storage in association with the label identification data read from the cloud storage; a transmitting step of transmitting the read transaction related document file, the file identification data, the label setting condition data, and the label identification data to a label production system; a receiving step of receiving data relating to the search label generated by the label generating system in accordance with the label setting condition data, together with the file identification data and the label identification data; a label registration step of storing data related to the search label in association with the file identification data and the label identification data in the cloud storage; A labeling method including:
13. a receiving step of receiving from a labeling system a transaction-related document file stored in a storage device, file identification data for identifying the transaction-related document file, label identification data for identifying a search label to be assigned to the transaction-related document file, and label setting condition data indicating setting conditions for the search label; a label generating step of generating data relating to the search label that satisfies the setting conditions indicated in the label setting condition data based on the transaction related document file; a transmitting step of transmitting data relating to the generated search label together with the file identification data and the label identification data to the labeling system; A label generation method including:
14. A labeling program for assigning search labels to transaction-related document files stored in a cloud storage, comprising: a file reading means for reading the transaction-related document file from the cloud storage together with file identification data for identifying the transaction-related document and label identification data for identifying the search label, the file identification data being associated with the transaction-related document file; a label setting condition data reading means for reading label setting condition data indicating setting conditions of the search label, the label setting condition data being stored in the cloud storage in association with the label identification data read from the cloud storage; a transmitting means for transmitting the read transaction related document file, the file identification data, the label setting condition data, and the label identification data to a label production system; a receiving means for receiving data relating to the search label generated by the label generating system in accordance with the label setting condition data, together with the file identification data and the label identification data; a label registration means for storing data relating to the search label in association with the file identification data and the label identification data in the cloud storage; A labeling program that enables a computer to function as a
15. a receiving means for receiving from a labeling system a transaction-related document file stored in a storage device, file identification data for identifying said transaction-related document file, label identification data for identifying a search label to be assigned to said transaction-related document file, and label setting condition data indicating setting conditions for said search label; a label generating means for generating data relating to the search label that satisfies the setting conditions indicated in the label setting condition data based on the transaction related document file; a transmitting means for transmitting data relating to the generated search label together with the file identification data and the label identification data to the labeling system; A label generation program that allows a computer to function as a
Citation Information
Patent Citations
Electronic contract system, electronic contract method, and server device
JP2021005360A
