JP7537458B2 - Information processing device, information processing system, information processing method, and program - Google Patents

Description

This invention relates to an information processing device, an information processing system, an information processing method, and a program.

Document management systems are being used to digitize and manage documents such as forms used in commercial transactions. For example, Patent Literature 1 discloses a technology that reduces the costs associated with sending forms by uploading digitized forms such as invoices and delivery notes to a form management server and enabling business partners to download the forms.

For example, in a document management system, the document management server may use different management methods depending on the format of the documents to be managed. In such cases, the document management server manages the documents by associating the format of the documents with the electronic data representing the documents.

However, conventional technology has an issue in that it is time-consuming to input the document transfer format. For example, electronic data representing a document usually does not hold information indicating the transfer format of the document. As a result, users have had to manually input the document transfer format, for example, after uploading the electronic data representing the document to a document management server.

In view of the above technical problems, one embodiment of the present invention is to determine the document exchange format from electronic data representing the document.

In order to solve the above problem, an information processing device according to an embodiment of the present invention includes an input unit that accepts input of electronic data representing a document, and a discrimination unit that discriminates the format of the document based on attribute information of the electronic data.

According to one embodiment of the invention, the format of document transfer can be determined from electronic data representing the document.

1 is a diagram illustrating an example of an overall configuration of an information processing system according to an embodiment. FIG. 2 illustrates an example of a hardware configuration of an information processing device according to an embodiment. FIG. 2 is a diagram illustrating an example of a functional configuration of an information processing system according to a first embodiment. FIG. 4 is a diagram showing an example of a processing procedure of an information processing method according to the first embodiment. FIG. 4 is a diagram illustrating an example of a tenant information management table according to the first embodiment. FIG. 4 is a diagram illustrating an example of a script according to the first embodiment. FIG. 11 is a diagram showing an example of an upload screen in the first embodiment. 11A and 11B are diagrams illustrating an example of a transfer type determination process in the first embodiment. FIG. 4 is a diagram illustrating an example of a document information management table in the first embodiment. FIG. 11 is a diagram showing an example of an upload screen in the first embodiment. FIG. 4 is a diagram showing an example of a processing procedure of an information processing method according to the first embodiment. FIG. 4 is a diagram showing an example of a document list screen in the first embodiment. FIG. 13 is a diagram showing an example of a document details screen in the first embodiment. FIG. 4 is a diagram showing an example of a processing procedure of an information processing method according to the first embodiment. FIG. 4 is a diagram illustrating an example of a document information management table in the first embodiment. FIG. 11 is a diagram illustrating an example of a functional configuration of an information processing system according to a second embodiment. FIG. 11 is a diagram illustrating an example of a registration process in the second embodiment.

The following describes in detail an embodiment of the present invention with reference to the drawings. Note that components having the same functions in the drawings are given the same numbers, and duplicate explanations will be omitted.

[First embodiment]
A first embodiment of the present invention is an information processing system for electronically managing documents. The information processing system in this embodiment accepts input of electronic data representing a document (hereinafter also referred to as "document data") in response to a user's operation, and determines the document transfer format represented in the document data. The information processing system in this embodiment also associates the transfer format with the document data and stores it.

In this embodiment, documents are, for example, forms such as invoices or quotations used in commercial transactions. Forms in this embodiment include, for example, at least one of forms issued by a user to a business partner and forms received by a user from a business partner. Forms include, for example, vouchers and the like created as evidence of a commercial transaction.

The document data managed by the information processing system in this embodiment includes data that has different management methods depending on the document transfer format. For example, the so-called Electronic Bookkeeping Act applies to electronic data obtained by digitizing forms. The Electronic Bookkeeping Act requires that different management methods be followed depending on the form transfer format. Therefore, when the information processing system manages electronic data obtained by digitizing forms, it is necessary to associate the electronic data with the form transfer format and store it.

In this embodiment, the transfer format is information indicating the medium or means used when transferring a document. In this embodiment, the transfer format includes "paper" or "electronic". The "paper" transfer format indicates that a document written on paper is physically transferred by hand or by mail. The "electronic" transfer format indicates that a computerized document is electronically transferred via a network such as email or cloud service.

A document that is received in paper format is digitized as an image file using a scanner or the like. A document that is received in electronic format is generated using a document creation application such as a word processor or spreadsheet software, and converted into an electronic file in PDF (Portable Document Format) or other format.

[Overall configuration of information processing system]
The overall configuration of an information processing system according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the overall configuration of an information processing system according to this embodiment.

As shown in FIG. 1, the information processing system 1 in this embodiment includes a document management server 10 and one or more user terminals 30. The document management server 10 and the user terminals 30 are each connected to a communication network N1.

Hereinafter, when distinguishing between two or more user terminals 30, they will be referred to using sub-numbers such as "user terminal 30-1," "user terminal 30-2," etc.

The communication network N1 is configured so that the connected devices can communicate with each other. The communication network N1 is constructed by a wired communication network such as the Internet, a LAN (Local Area Network), or a WAN (Wide Area Network).

The communication network N1 may include not only wired communication, but also wireless communication such as wireless LAN or short-range wireless communication, or a network using mobile communication such as WiMAX (Worldwide Interoperability for Microwave Access), LTE (Long Term Evolution), or 5G (5th Generation).

The document management server 10 provides a document management service to the user terminal 30 via the communication network N1. The document management service in this embodiment is a service that stores document data representing forms used in commercial transactions together with the information represented on the forms, and outputs the data in response to a user request.

In this embodiment, an entity that uses the services provided by the document management server is called a tenant. That is, in this embodiment, a tenant is a business entity, an organization, an individual, etc.

The user terminal 30-1 is an information processing device used by a user belonging to a tenant. In response to operations by the user, the user terminal 30-1 uses the document management service provided by the document management server 10 via the communication network N1.

The user terminal 30-2 is an information processing device used by the input agent. In response to the input agent's operation, the user terminal 30-2 inputs information representing the contents of the document data to the document management server 10 via the communication network N1.

An input agent is a user who performs tasks (operations) related to input delegation at the request of a tenant or a user belonging to the tenant. Input delegation is, for example, a setting in which the input agent displays information about the contents of a document on the user terminal 30-2 and accepts various operations related to the document.

In addition, whether or not to enable delegation of input in the document management service can be selected at will. If delegation of input is not enabled, the information processing system 1 does not include the user terminal 30-2.

The user terminal 30 is not limited to an information processing device, so long as it is a device equipped with a communication function. The user terminal 30 may be, for example, a PJ (Projector), an IWB (Interactive White Board: a white board with an electronic blackboard function that allows mutual communication), an output device such as a digital signage, a HUD (Head Up Display) device, industrial machinery, an imaging device, a sound collection device, medical equipment, a network home appliance, an automobile (Connected Car), a notebook PC (Personal Computer), a mobile phone, a smartphone, a tablet terminal, a game console, a PDA (Personal Digital Assistant), a digital camera, a wearable PC, or a desktop PC.

[Hardware configuration of information processing system]
The hardware configuration of the information processing system in this embodiment will be described with reference to Fig. 2. Fig. 2 is a diagram showing an example of a hardware configuration in which the document management server 10 and the user terminal 30 are realized by a computer.

As shown in FIG. 2, the computer in this embodiment includes a CPU (Central Processing Unit) 501, a ROM (Read Only Memory) 502, a RAM (Random Access Memory) 503, a HD (Hard Disk) 504, a HDD (Hard Disk Drive) controller 505, a display 506, an external device connection I/F (Interface) 508, a network I/F 509, a bus line 510, a keyboard 511, a pointing device 512, a DVD-RW (Digital Versatile Disk Rewritable) drive 514, and a media I/F 516.

Of these, CPU 501 controls the operation of the entire computer. ROM 502 stores programs used to drive CPU 501, such as IPL. RAM 503 is used as a work area for CPU 501. HD 504 stores various data such as programs. HDD controller 505 controls the reading and writing of various data from HD 504 under the control of CPU 501.

The display 506 displays various information such as a cursor, a menu, a window, characters, or an image. The external device connection I/F 508 is an interface for connecting various external devices. In this case, the external devices are, for example, a USB (Universal Serial Bus) memory or a printer. The network I/F 509 is an interface for data communication using the communication network N1. The bus line 510 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 501 shown in FIG. 2.

The keyboard 511 is a type of input means equipped with multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 512 is a type of input means for selecting and executing various instructions, selecting a processing target, moving the cursor, etc. The DVD-RW drive 514 controls the reading and writing of various data from the DVD-RW 513, which is an example of a removable recording medium. Note that this is not limited to a DVD-RW, and may be a DVD-R, etc. The media I/F 516 controls the reading and writing (storing) of data from the recording medium 515, such as a flash memory.

[Functional configuration of information processing system]
The functional configuration of the information processing system in this embodiment will be described with reference to Fig. 3. Fig. 3 is a block diagram showing an example of the functional configuration of the information processing system in this embodiment.

<Functional configuration of document management server>
As shown in FIG. 3, the document management server 10 in this embodiment includes a transmission/reception unit 11, a screen generation unit 12, a storage control unit 19, and a storage unit 100.

The transmission/reception unit 11 transmits and receives various data (or information) to and from the user terminal 30 via the communication network N1. The transmission/reception unit 11 is realized by commands from the CPU 501 and the network I/F 509 shown in FIG. 2.

The screen generation unit 12 generates screen data representing a specific screen in response to a request from the user terminal 30. Each piece of screen data generated by the screen generation unit 12 is, for example, screen data written in HTML (HyperText Markup Language) or the like, and may include an application written in JavaScript (registered trademark) or the like. The screen generation unit 12 is realized by commands from the CPU 501 shown in FIG. 2.

The storage control unit 19 performs processes such as storing various data in the storage unit 100 and reading out various data stored in the storage unit 100. The storage control unit 19 is realized by instructions from the CPU 501 and the HDD controller 505 shown in FIG. 2.

The memory unit 100 includes a tenant information management DB 110 and a document information management DB 120. The memory unit 100 is realized by the HD 504 shown in FIG. 2.

The tenant information management DB 110 is composed of a tenant information management table. The tenant information management table stores information about the tenants of the document management server 10. Details of the tenant information management table will be described later.

The document information management DB120 is composed of a document information management table for each tenant. The document information management table stores document information related to at least one of the forms issued by the user to a business partner and the forms received by the user from a business partner. Details of the document information management table will be described later.

<Functional configuration of user terminal>
3, the user terminal 30 in this embodiment includes a transmission/reception unit 31, a browser 32, a storage control unit 39, and a storage unit 300. The browser 32 includes an input unit 321 and a determination unit 322. The input unit 321 and the determination unit 322 are realized by the browser 32 executing a script embedded in the screen data.

The transmission/reception unit 31 transmits and receives various data (or information) to and from the document management server 10 via the communication network N1. The transmission/reception unit 31 is realized by commands from the CPU 501 and the network I/F 509 shown in FIG. 2.

The browser 32 outputs various screens to the display 506 or an external display connected to the external device connection I/F 508 based on the screen data received from the document management server 10. The browser 32 is mainly realized by commands from the CPU 501 shown in FIG. 2.

The input unit 321 accepts the input of document data in response to user operation. The document data is electronic data representing a form issued by the user to a business partner or a form received by the user from a business partner. The input unit 321 reads the document data specified by the user from the memory unit 300 via the memory control unit 39.

The discrimination unit 322 discriminates the document transfer format represented in the document data based on the attribute information of the document data received by the input unit 321. The discrimination unit 322 also transmits a registration request including the document data and the transfer format to the document management server 10 via the transmission/reception unit 31.

The storage control unit 39 performs processes such as storing various data in the storage unit 300 and reading various data stored in the storage unit 300. The storage control unit 39 is realized mainly by instructions from the CPU 501 and the HDD controller 505 shown in FIG. 2.

The storage unit 300 prestores at least one of document data that is electronic version of a form issued by the user to a business partner or a form received by the user from a business partner. The storage unit 300 is realized by the HD 504 shown in FIG. 2.

[Processing procedure of information processing system]
The processing procedure of the information processing method executed by the information processing system in this embodiment will be described with reference to Fig. 4 to Fig. 15. Fig. 4, Fig. 11 and Fig. 14 are sequence diagrams showing an example of the processing procedure of the information processing method in this embodiment.

In step S1, the browser 32 provided in the user terminal 30-1 accepts an operation by the user to display an upload screen. When accepting an operation by the user to display the upload screen, the browser 32 may also accept an operation to select the type of document to be uploaded.

Before accepting the display operation of the upload screen, the browser 32 accepts authentication information entered by the user. The authentication information is, for example, a user ID and a password. Next, the transmission/reception unit 31 transmits the accepted authentication information to the document management server 10.

In the document management server 10, the transmission/reception unit 11 receives authentication information from the user terminal 30-1. Next, the screen generation unit 12 performs a predetermined authentication process using the received authentication information. The authentication process is performed by checking the received authentication information against the tenant information registered in the tenant information management DB 110. Therefore, the browser 32 can accept the user's operation to display the upload screen only if the user is authenticated by the document management server 10.

(Tenant Information Management Table)
Details of the tenant information management table will now be described with reference to Fig. 5. Fig. 5 is a conceptual diagram illustrating an example of the tenant information management table in this embodiment.

As shown in FIG. 5, in the tenant information management table of this embodiment, identification information (tenant ID) that identifies a tenant, information that represents the tenant (company name, etc.), authentication information (user ID and password, etc.), and contact information (email address, address, etc.) are associated and managed.

Returning to FIG. 4, in step S2, the transmission/reception unit 31 of the user terminal 30-1 transmits a request to acquire an upload screen to the document management server 10. The request includes a tenant ID. In the document management server 10, the transmission/reception unit 11 receives the request to acquire an upload screen from the user terminal 30-1.

In step S3, the screen generation unit 12 of the document management server 10 generates screen data for the upload screen. The screen generation unit 12 embeds a predetermined script in the screen data for the upload screen.

Here, the script in this embodiment will be described with reference to FIG. 6. FIG. 6 is a diagram showing an example of a script in this embodiment.

As shown in Figure 6, a URL indicating the location of the script is embedded in the screen data of the upload screen. The example in Figure 6 shows that the script "https://.../program.js" implemented in JavaScript (registered trademark) is embedded in the header of the HTML format upload screen.

The browser 32 of the user terminal 30-1 reads the screen data shown in FIG. 6 and executes the script "https://.../program.js", thereby realizing the input unit 321 and the determination unit 322.

Returning to FIG. 4, in step S4, the transmitting/receiving unit 11 included in the document management server 10 transmits screen data of the upload screen generated by the screen generating unit 12 to the user terminal 30-1. In the user terminal 30-1, the transmitting/receiving unit 31 receives the screen data of the upload screen from the document management server 10.

In step S5, the browser 32 of the user terminal 30-1 displays the upload screen on the display 506 based on the screen data of the upload screen.

(Upload screen)
The upload screen in this embodiment will now be described with reference to Fig. 7. Fig. 7 is a conceptual diagram showing an example of the upload screen in this embodiment.

As shown in FIG. 7, the upload screen 200 in this embodiment has an input proxy setting field 201 and a file selection field 202.

In the input proxy setting field 201, the user sets whether or not to use input proxy. In the file selection field 202, the user inputs information indicating the location of the document data to be uploaded. The file selection field 202 may be configured to allow the user to input information about multiple document data.

If the document management server 10 is not set to allow input delegation, the upload screen 200 is configured not to have the input delegation setting field 201.

Returning to FIG. 4, in step S6, the browser 32 provided on the user terminal 30-1 accepts an upload operation by the user. Specifically, the user sets whether or not to use the input delegation in the input delegation setting field 201, and inputs information indicating the location of the document data in the file selection field 202. This causes the input unit 321 to accept the input of the document data. The input unit 321 retrieves the accepted document data from the storage unit 300, and sends it to the discrimination unit 322.

If input delegation is not enabled on the document management server 10, the user only needs to input information indicating the location of the document data in the file selection field 202.

In step S7, the discrimination unit 322 of the user terminal 30-1 discriminates the document transfer format represented in the document data based on the attribute information of the document data received by the input unit 321.

<Transfer format determination process>
Here, the details of the transfer type determination process (step S7 in FIG. 4) in this embodiment will be described with reference to Fig. 8. Fig. 8 is a flow chart showing an example of the transfer type determination process in this embodiment.

The transfer format determination process shown in FIG. 8 is executed for the document data that has been accepted as input. If multiple pieces of document data have been accepted as input, the process is executed for each piece of document data.

In step S7-1, the discrimination unit 322 determines whether or not attribute information can be acquired from the document data. If attribute information can be acquired (YES), the discrimination unit 322 proceeds to step S7-2. If attribute information cannot be acquired (NO), the discrimination unit 322 proceeds to step S7-8.

The attribute information in this embodiment is attribute information that can be obtained by referencing the contents of the document data. For example, the attribute information in this embodiment is format information of an image included in the document data, or property information set in a file that represents the document data.

For example, if document data is encrypted with a password or the like, the attribute information of the document data cannot be obtained unless the password is entered. Also, if the format of the document data is damaged, the attribute information of the document data cannot be obtained.

In step S7-2, the discrimination unit 322 initializes a variable n to 1. The variable n is a variable that represents the page number in the document data.

In step S7-3, the discrimination unit 322 obtains the page size of the nth page of the document data. The page size is expressed as the number of pixels in both the longitudinal and lateral directions of the page.

In step S7-4, the discrimination unit 322 obtains the drawing size of each image included in the nth page of the document data. The drawing size is expressed as the number of pixels in both the long and short sides of the image.

In step S7-5, the discrimination unit 322 compares the page size acquired in step S7-3 with the drawing size acquired in step S7-4. Next, the discrimination unit 322 determines whether the drawing sizes of all images are less than the page size. If the drawing sizes of all images are less than the page size (YES), the discrimination unit 322 proceeds to step S7-8. If there is an image whose drawing size is equal to or larger than the page size (NO), the discrimination unit 322 proceeds to step S7-6.

In step S7-6, the discrimination unit 322 determines whether or not the document data contains a next page (i.e., page n+1). If the next page exists (YES), the discrimination unit 322 proceeds to step S7-7. If the next page does not exist (NO), the discrimination unit 322 proceeds to step S7-9.

In step S7-7, the discrimination unit 322 increments the variable n. Next, the discrimination unit 322 returns the process to step S7-3. In this manner, the discrimination unit 322 repeatedly executes the processes of steps S7-3 to S7-5 for each page included in the document data.

In step S7-8, the discrimination unit 322 determines that the document transfer format represented in the document data is "electronic."

In step S7-9, the discrimination unit 322 determines that the document format represented in the document data is "paper."

The determination process executed in step S7-1 will be explained in more detail. If the document data has been encrypted with a password or the like, the attribute information cannot be obtained unless the password is entered. When a paper document is digitized using a scanner, the document data is considered to be used within the company. Therefore, it is unlikely that a password will be set for the document data. Therefore, if attribute information cannot be obtained from the document data, the determination unit 322 determines that the transfer format is "electronic."

The determination process performed in step S7-5 will now be explained in more detail. When a paper document is digitized using a scanner, the scanner expands the scanned image so that it matches the page size of the document data. As a result, the drawing size of the image roughly matches the page size.

On the other hand, when digitization is performed using the functions of a document creation application, text and margins on the page are not converted into images. Therefore, even if the page contains images, the drawing size of all images will be smaller than the page size. Therefore, if the drawing size of the images contained in the page is smaller than the page size, the discrimination unit 322 determines that the transfer format is "electronic."

Returning to FIG. 4, in step S8, the transmitting/receiving unit 31 of the user terminal 30-1 transmits a request to register document data to the document management server 10. The registration request includes the document data accepted by the input unit 321 and the document transfer format determined by the determination unit 322. In the document management server 10, the transmitting/receiving unit 11 receives the request to register document data from the user terminal 30-1.

In step S9, the storage control unit 19 of the document management server 10 stores the document data included in the document data registration request in a specified storage location in the storage unit 100.

In step S10, the storage control unit 19 of the document management server 10 generates document information based on the document data registration request. The storage control unit 19 then stores the generated document information in the document information management table.

(Document Information Management Table)
Here, the document information management table in this embodiment will be described with reference to Fig. 9. Fig. 9 is a conceptual diagram showing an example of the document information management table in this embodiment.

As shown in FIG. 9, in the document information management table of this embodiment, identification information (document ID) that identifies the document, the file name on the user terminal 30, the document type, the transfer format, the document contents (business year, client name, transaction date, total amount, etc.), whether or not a proxy was entered, the status (unconfirmed or confirmed), the registration date and time, the file path on the document management server 10, etc. are stored in association with each other.

If the document management server 10 is not set to allow input delegation, the document information management table will not include an item for whether or not delegated input is available.

Figure 9 shows an example of document information immediately after registration. In the document information immediately after registration, the document ID, transfer format, whether or not proxy input is used, etc. are set. On the other hand, in the document information immediately after registration, the document content is left blank. Also, in the document information immediately after registration, the status is "unconfirmed."

Referring back to FIG. 4, in step S11, the transmitting/receiving unit 11 included in the document management server 10 transmits a notification of the upload result to the user terminal 30-1. The notification includes the document information stored in the document information management table. In the user terminal 30-1, the transmitting/receiving unit 31 receives the notification of the upload result from the document management server 10.

In step S12, the browser 32 of the user terminal 30-1 displays the upload results on the upload screen 200 based on the notification of the upload results.

Figure 10 is a diagram showing an example of an upload screen that displays the upload results. As shown in Figure 10, the upload screen 200 that displays the upload results has an upload result display section 203.

The upload result display field 203 displays information based on the document information for each document data item that the input unit 321 accepts as input. This information includes, for example, the registration date, status, whether input was performed on behalf of the user (input on behalf of the user or input on behalf of the user skipped), and the document transfer format (paper or electronic). Therefore, the user can check the automatically determined document transfer format by referring to the upload results displayed in the upload result display field 203.

If input delegation is not set to be available on the document management server 10, the upload result display field 203 will not display information regarding whether or not input delegation is available.

Let us now turn to Figure 11 for further explanation. In step S21, the browser 32 of the user terminal 30-1 accepts an operation to display the document list screen. The operation to display the document list screen is performed on a main menu screen or the like provided by the document management server 10.

In step S22, the transmission/reception unit 31 of the user terminal 30-1 transmits a request to acquire the document list screen to the document management server 10. The request includes the tenant ID associated with the user. In the document management server 10, the transmission/reception unit 11 receives the request to acquire the document list screen from the user terminal 30-1.

In step S23, the storage control unit 19 of the document management server 10 extracts document information of the tenant from the document information management DB 120 based on the tenant ID included in the request to obtain the document list screen. Specifically, the storage control unit 19 extracts document information stored in the document information management table related to the tenant.

In step S24, the screen generation unit 12 of the document management server 10 generates screen data for the document list screen. The screen generation unit 12 embeds the document information extracted by the memory control unit 19 in the screen data for the document list screen.

In step S25, the transmission/reception unit 11 of the document management server 10 transmits the screen data of the document list screen generated by the screen generation unit 12 to the user terminal 30. In the user terminal 30-1, the transmission/reception unit 31 receives the screen data of the document list screen from the document management server 10.

In step S26, the browser 32 of the user terminal 30-1 displays the document list screen on the display 506 based on the screen data of the document list screen.

(Document list screen)
The document list screen in this embodiment will now be described with reference to Fig. 12. Fig. 12 is a conceptual diagram showing an example of the document list screen in this embodiment.

As shown in FIG. 12, the document list screen 210 in this embodiment has a search condition area 211, a search button 212, and a document list area 213.

The search condition area 211 displays items that can be specified as document search conditions. Search items include, for example, the name of the business partner, a range of transaction dates, a range of total amounts, status (unconfirmed or confirmed, etc.), and the delivery format (electronic or paper), etc.

In the example of the document list screen 210 shown in FIG. 12, the status shows whether or not delegation is available. However, if delegation is not set to be available on the document management server 10, information regarding whether or not delegation is available will not be displayed.

The document list area 213 displays a list of document information. In the initial state, the document list area 213 displays a list of document information for the tenant to which the user belongs.

When the user presses the search button 212, the browser 32 accepts a search operation for document information. When the user performs a search operation, document information that matches the search conditions entered in the search condition area 211 is displayed in a list in the document list area 213. Details of the search operation will be described later.

Returning to FIG. 11, in step S27, the browser 32 of the user terminal 30-1 accepts a display operation for the document details screen. The display operation for the document details screen is performed on the document list screen 210. Specifically, the display operation for the document details screen is performed when the user performs an operation to select one of the document information displayed in the document list area 213 of the document list screen 210. This operation is, for example, an operation of double-clicking the document information displayed in the document list area 213.

In step S28, the transmission/reception unit 31 of the user terminal 30-1 transmits a request to acquire the document details screen to the document management server 10. The request includes the document ID of the document information to be displayed. In the document management server 10, the transmission/reception unit 11 receives the request to acquire the document details screen from the user terminal 30-1.

In step S29, the storage control unit 19 of the document management server 10 reads the document information to be displayed from the document information management DB 120 based on the document ID included in the request to obtain the document details screen. Next, the storage control unit 19 reads the document data from the storage unit 100 based on the file path included in the read document information.

In step S30, the screen generation unit 12 of the document management server 10 generates screen data for the document details screen. The screen generation unit 12 embeds the document information and document data read by the storage control unit 19 in the screen data for the document details screen.

In step S31, the transmission/reception unit 11 of the document management server 10 transmits screen data of the document details screen generated by the screen generation unit 12 to the user terminal 30-1. In the user terminal 30-1, the transmission/reception unit 31 receives the screen data of the document details screen from the document management server 10.

In step S32, the browser 32 of the user terminal 30-1 displays the document details screen on the display 506 based on the screen data of the document details screen.

(Document details screen)
Here, the document details screen in this embodiment will be described with reference to Fig. 13. Fig. 13 is a conceptual diagram showing an example of the document details screen in this embodiment.

As shown in FIG. 13, the document details screen 220 in this embodiment has a document image area 221, a document information area 222, a save button 223, and a confirm button 224.

The document image area 221 displays a preview of the document data. The document information area 222 displays information about the document (document type, delivery format, fiscal year, client name, transaction date, total amount, document ID, memos, etc.) in an editable format. Therefore, if there is an error in the document delivery format determined by the determination unit 322 of the user terminal 30-1, the user can correct it to the correct delivery format.

When the user presses the save button 223, the browser 32 temporarily stores the document information entered in the document information area 222 in the storage unit 300, etc. If there is document information temporarily stored in the storage unit 300, etc., the document details screen 220 displays the contents of the document information stored in the storage unit 300, etc., in the document information area 222 when displaying the same document information.

When the user presses the confirmation button 224, the browser 32 accepts the input operation of the document information. When the user performs the input operation, the document information stored in the document information management table is updated with the document information input in the document information area 222. Details of the input operation will be described later.

When the document management server 10 is set to allow input delegation and the document information input delegation availability is set to input delegation, the document details screen 220 is displayed on the user terminal 30-2 used by the input delegator. In this case, the document details screen 220 limits the items displayed in the document information area 222. Specifically, the document information area 222 displays only the client name, transaction date, and total amount, for example, as information related to the document.

Now let us turn to FIG. 14 for further explanation. In step S41, the browser 32 of the user terminal 30-1 accepts the user's input operation of document information. The input operation of document information is performed on the document details screen 220. Specifically, the user inputs or edits each piece of information in the document information area 222 of the document details screen 220, and then presses the confirmation button 224, thereby inputting document information.

In step S42, the transmission/reception unit 31 of the user terminal 30-1 transmits a document information update request to the document management server 10. The update request includes the document ID and the updated document information. In the document management server 10, the transmission/reception unit 11 receives the document information update request from the user terminal 30-1.

In step S43, the storage control unit 19 provided in the document management server 10 identifies the document information to be updated from the document information management DB 120 based on the document ID included in the document information update request. Next, the storage control unit 19 updates the identified document information based on the updated document information included in the document information update request. At this time, the status of the updated document information is updated to "confirmed."

In step S44, the transmission/reception unit 11 of the document management server 10 transmits a notification of the document information update result to the user terminal 30-1. The notification includes the updated document information. In the user terminal 30-1, the transmission/reception unit 31 receives the notification of the document information update result from the document management server 10.

In step S45, the browser 32 of the user terminal 30-1 displays the updated document information in the document information area 222 of the document details screen 220 based on the notification of the document information update results.

Figure 15 is a conceptual diagram showing an example of a document information management table after updating. As shown in Figure 15, in the document information management table after updating, values are set for the document contents (business year, client name, transaction date, total amount, etc.). In addition, in the document information management table after updating, the status has been updated to "Confirmed."

Returning to FIG. 14, in step S46, the browser 32 of the user terminal 30-1 accepts a document information search operation by the user. The document information search operation is performed on the document list screen 210. Specifically, the document information search operation is performed when the user inputs the desired search items in the search condition area 211 of the document list screen 210 and then presses the search button 212.

In step S47, the transmission/reception unit 31 of the user terminal 30-1 transmits a search request for document information to the document management server 10. The search request includes search conditions. In the document management server 10, the transmission/reception unit 11 receives the search request for document information from the user terminal 30-1.

In step S48, the storage control unit 19 of the document management server 10 extracts document information that matches the search conditions from the document information management DB 120 based on the search conditions included in the document information search request.

In step S49, the transmission/reception unit 11 of the document management server 10 transmits the search results for the document information to the user terminal 30-1. In the user terminal 30-1, the transmission/reception unit 31 receives the search results for the document information from the document management server 10.

In step S50, the browser 32 of the user terminal 30-1 displays the search results of the document information in the document list area 213 of the document list screen 210 based on the search results of the document information.

[Major Effects of the First Embodiment]
The user terminal in this embodiment determines the document transfer format represented in the document data based on the attribute information of the document data input by the user. The user terminal in this embodiment then transmits a registration request including the document data and the transfer format to the document management server. Therefore, the document management server can automatically associate and register the document data with the transfer format. This saves the user the trouble of manually inputting the transfer format for uploaded document data.

[Modification 1]
In the first embodiment, an example of determining the document transfer format by the transfer format determination process shown in Fig. 8 has been described. That is, in the transfer format determination process in the first embodiment, whether the transfer format is "paper" or "electronic" is determined based on whether attribute information can be acquired and on the result of comparing the page size with the image drawing size. In the first modified example, an example of determining the transfer format by the determination unit 322 based on property information of a file representing document data will be described.

When a file created with a word processing application is converted to PDF format, information indicating the type or manufacturer of the application may be set in the file's property information. Also, when a printed document is converted into an electronic file using a scanner, information indicating the model or manufacturer of the scanner may be set in the file's property information. When this information is known in advance, the transfer format can be determined based on the property information of the document data.

When determining the transfer format based on the file property information, the amount of calculation is less than in the first embodiment. Therefore, if the environment in which the document will be digitized is known in advance, the transfer format determination process in this modified example can be executed to determine the transfer format with less calculation.

If the document data is encrypted with a password or the like, the property information cannot be obtained unless the password is entered. Therefore, it is possible to use both the determination based on whether attribute information can be obtained and the determination based on property information.

[Second embodiment]
In the first embodiment, the document transfer format is determined by a script executed by the browser 32 of the user terminal 30-1. In the second embodiment, the document management server 10 receives document data from the user terminal 30-1 and determines the document transfer format based on attribute information of the document data.

The information processing system in the second embodiment will be described below with reference to Figs. 16 and 17. The following description will focus on the differences from the first embodiment.

[Functional configuration of information processing system]
The functional configuration of the information processing system in this embodiment will be described with reference to Fig. 16. Fig. 16 is a block diagram showing an example of the functional configuration of the information processing system in this embodiment.

<Functional configuration of document management server>
16, the document management server 10 in this embodiment includes, similarly to the first embodiment, a transmission/reception unit 11, a screen generation unit 12, a storage control unit 19, and a storage unit 100. The document management server 10 in this embodiment further includes a discrimination unit 13.

The discrimination unit 13 discriminates the document transfer format represented in the document data in response to a request from the user terminal 30-1. The discrimination unit 13 is realized by commands from the CPU 501 shown in FIG. 2.

<Functional configuration of user terminal>
16, the user terminal 30 in this embodiment includes, similarly to the first embodiment, a transmission/reception unit 31, a browser 32, a storage control unit 39, and a storage unit 300. The user terminal 30 in this embodiment differs from the first embodiment in that the browser 32 does not include a discrimination unit 322.

[Processing procedure of information processing system]
The processing procedure of the information processing method executed by the information processing system in this embodiment will be described with reference to Fig. 17. Fig. 17 is a sequence diagram showing an example of the processing procedure of the information processing method in this embodiment.

In step S6, the browser 32 of the user terminal 30-1 accepts an upload operation by the user. This causes the input unit 321 to accept the input of document data.

In step S7, the transmission/reception unit 31 of the user terminal 30-1 transmits a request to register document data to the document management server 10. The registration request includes the document data accepted by the input unit 321. In the document management server 10, the transmission/reception unit 11 receives the request to register document data from the user terminal 30-1.

In step S8, the determination unit 13 of the document management server 10 determines the document transfer format represented in the document data received from the user terminal 30-1 based on the attribute information of the document data. The method of determining the document transfer format is the same as in the first embodiment or modification example 1.

In step S9, the storage control unit 19 of the document management server 10 stores the document data included in the document data registration request in a specified storage location in the storage unit 100.

In step S10, the storage control unit 19 of the document management server 10 generates document information based on the document data registration request and the transfer format determined by the determination unit 13. Next, the storage control unit 19 stores the generated document information in the document information management table.

[Main Effects of the Second Embodiment]
The document management server in this embodiment determines the document transfer format represented in the document data based on the attribute information of the document data received from the user terminal. After that, the document management server in this embodiment stores document information that associates the document data with the transfer format in a storage unit. This saves the user the trouble of manually inputting the transfer format for uploaded document data.

[supplement]
In the above embodiment, the document management server 10 and the user terminal 30 are an example of an information processing device. The document data is an example of electronic data. The transmitting/receiving unit 31 is an example of a transmitting unit.

Each function of the embodiments described above can be realized by one or more processing circuits. In this specification, the term "processing circuit" includes a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, and devices such as an ASIC (Application Specific Integrated Circuit), DSP (Digital Signal Processor), FPGA (Field Programmable Gate Array), and conventional circuit modules designed to execute each function described above.

The devices described in the examples are merely illustrative of one of several computing environments for implementing the embodiments disclosed herein. In one embodiment, the document management server 10 includes multiple computing devices, such as a server cluster. The multiple computing devices are configured to communicate with each other over any type of communication link, including a network, shared memory, etc., and perform the processes disclosed herein.

Although the embodiments of the present invention have been described in detail above, the present invention is not limited to these embodiments, and various modifications and changes are possible within the scope of the gist of the present invention described in the claims.

Reference Signs List 1 Information processing system 10 Document management server 11, 31 Transmission/reception unit 12 Screen generation unit 19, 39 Storage control unit 30 User terminal 32 Browser 321 Input unit 322 Discrimination unit 100, 300 Storage unit

JP 2014-137773 A

Claims (11)

an input unit that accepts input of electronic data representing a document that a user has received or exchanged in paper form or a document that the user has received or exchanged electronically ;
a determination unit that determines whether the document is in paper or electronic format based on attribute information of the electronic data;
Equipped with
the determining unit determines that the transfer format is electronic when there is a page in which the drawing sizes of all images included in the electronic data are smaller than the page size of the page;
Information processing device. 2. The information processing device according to claim 1 ,
the determination unit determines that the format of the data transfer is electronic when the attribute information cannot be acquired from the electronic data;
Information processing device. 2. The information processing device according to claim 1 ,
The determination unit determines that the format of the data is electronic when the electronic data is encrypted.
Information processing device. 2. The information processing device according to claim 1 ,
the attribute information is property information of a file representing the electronic data;
The determination unit determines whether or not a predetermined character string is included in the property information to determine the transfer format.
Information processing device. 5. An information processing device according to claim 1,
the input unit accepts an input of the electronic data in response to an operation of a user to select the electronic data;
a transmission unit that transmits a registration request including the electronic data and the transfer format to another information processing device,
Information processing device. 6. The information processing device according to claim 5 ,
a receiving unit that receives screen data for displaying the electronic data in association with the transfer format from the other information processing device,
Information processing device. 5. An information processing device according to claim 1,
the input unit accepts input of the electronic data in response to receiving the electronic data from a user terminal;
a storage control unit that stores the electronic data and the transfer format in a storage unit in association with each other;
Information processing device. The information processing device according to claim 7 ,
a transmission unit that transmits screen data for displaying the electronic data in association with the transfer format to the user terminal;
Information processing device. An information processing system including a user terminal and an information processing device,
an input unit that accepts input of electronic data representing a document that a user has received or exchanged in paper form or a document that the user has received or exchanged electronically ;
a determination unit that determines whether the document is in paper or electronic format based on attribute information of the electronic data;
Including,
the determining unit determines that the transfer format is electronic when there is a page in which the drawing sizes of all images included in the electronic data are smaller than the page size of the page;
Information processing system. The computer
an input step of accepting input of electronic data representing a document received by a user on paper or a document received by the user electronically ;
a determination step of determining whether the document is in paper or electronic format based on attribute information of the electronic data;
Run
the determining step includes determining that the transfer format is electronic when there is a page, among the pages included in the electronic data, in which the drawing sizes of all images included in the page are smaller than the page size of the page;
Information processing methods. On the computer,
an input step of accepting input of electronic data representing a document received by a user on paper or a document received by the user electronically ;
a determination step of determining whether the document is in paper or electronic format based on attribute information of the electronic data;
Run the command,
the determining step includes determining that the transfer format is electronic when there is a page, among the pages included in the electronic data, in which the drawing sizes of all images included in the page are smaller than the page size of the page;
program.

Images