JP2014016873A - Document data management device, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a document data management device in which information security of document data is secured, and besides browsing of document data can be performed.SOLUTION: A document data management device according to the present invention has means for: previously collecting document data as a target of a browsing request from a server device such as a document file server; dividing document data by the document constituent element of a document; endowing each document constituent element with a hash value so as to hold it; extracting, in response to a browsing request from a document browsing client as an information terminal, only a document constituent element in response to the request; and transmitting it to the document browsing client.

Description

  The present invention relates to a document data management device and a program thereof, and more particularly to a technique for managing document data in a structured manner and browsing the document data using a network.

  In recent years, a large amount of structured document data represented by XML (Extensible Markup Language) has been used as a document data storage format for reasons such as easy handling of data, high compatibility with networks, and high reusability. It has been. In structured document data, a sentence is structured by decorating the document with tags. Then, paragraphs and appearance can be set for each element of the sentence structure. Furthermore, if an attribute is defined in tag information, it is possible to give meaning to what element each element has.

  Document data created in a company is mainly data such as reports, estimates, and invoices. In many cases, the document data created in the company has a predetermined format. In the case of such document data, a sentence format can be created in a structured form by defining a sentence format in XML format in advance and creating document data.

  For example, in OfficeOpenXML (Standard ECMA-376 Office Open XML File Formats), which is one of the document formats of XML data, a custom definition tag is used, and attribute information is given to the tag. Meaning can be made.

  By creating document data as XML data, any application can handle the data as XML data. Since XML data is structured text data composed of text data, there is a merit that data is highly versatile and can be easily reused. There are some known methods of utilizing XML data that take advantage of the characteristic that XML data is structured text data.

  In Japanese Patent Laid-Open No. 2004-126804, a large amount of XML data is centrally managed by decomposing XML data into components based on the hierarchical structure and tag information, mapping the components to a database table, and storing them. The handling of XML data is made efficient. Furthermore, Japanese Patent Application Laid-Open No. 2002-297601 has known a technique for managing documents having different sentence structures while maintaining the same document structure by taking advantage of the fact that XML data is structured sentences. .

JP 2004-126804 A JP 2002-297601 A

Standard ECMA-376 Office Open XML File Formats [Search May 9, 2012], <URL: http://www.ecma-international.org/publications/standards/Ecma-376.htm>

  In recent years, due to the widespread use of network devices, there are many usage scenes in which a sales person connects to an internal network from a remote location and refers to document data from a file server in the internal network. In such a case, by creating the document data as XML data, taking advantage of the characteristic that the XML data is structured text data, a required part of the required document data from among a large number of document data. It is also possible to extract and acquire only.

  For example, according to the methods disclosed in Patent Documents 1 and 2, XML data can be stored while maintaining the sentence structure. As a result, it is possible to efficiently extract and refer to only the document data required by the user from the large amount of XML data using the structured information of the text.

  However, in general, access is restricted for each document data from the viewpoint of security. Specifically, in order to ensure information security of document data, even for users in the same company, document data created by users in different departments have access restrictions in document data units that cannot be referenced. Operation such as setting is performed. Therefore, even if the document data is stored as XML data, it may be difficult to freely extract and use information required by the user from the document data.

  Normally, an operation is performed so that the user can refer to the document data required by the user by setting the reference authority for each document data and setting the permission of reference for each user. In such an operation, it is necessary to set a reference authority for each document data, and the operation is complicated. In addition, there is a problem that the reference authority is set incorrectly.

  The present invention solves such a problem. Document data stored in an in-company network is stored in a form that can be easily referred to, and document data information can be stored without complicated settings. The purpose is to enable browsing of document data while ensuring security.

  In order to solve the above-described problems, the document data management apparatus according to the present invention collects document data to be browsed in advance from a server apparatus such as a document file server, and divides the document data for each document component of the document. Then, a hash value is assigned to each document component and held, and by means of a browsing request from the document browsing client that is an information terminal, only the document component corresponding to the request is extracted and transmitted to the document browsing client have. The outline of this document data management apparatus is as follows.

  (1) A document data browsing apparatus includes a document collection setting storage unit that stores document collection settings that define how to collect document data that can be referred to by a document browsing client from which document file server. , A document collection unit that collects document data from the document file server defined in the document collection settings, and a document division unit that divides the document data collected by the document collection unit into document components and records them in the document data holding unit And a document search accepting unit that accepts document search conditions from the document browsing client, and a document data holding unit that performs document search according to the search conditions accepted by the document search accepting unit. A document search result generation unit that generates a document component by searching a document component, adds a document name and a hash value to the retrieved document component, and stores the result in a document data holding unit, and a document name as a document search result And a document search result providing unit for transmitting the hash value to the document browsing client.

  As a result, document data referred to by the document browsing client is held in the document data management apparatus, so that the document browsing client can browse the document data without directly accessing the document file server. Furthermore, document data is recorded as data that does not make sense even if only the document components that are divided are referred to by being divided and recorded in the document document structure, thereby ensuring reference security. Can do.

  When the divided document component is held in the document dividing unit, a hash value may be added to the divided document component and recorded. This makes it possible to restore meaningful document data by combining the divided data using the hash value as a key.

  Further, according to the document management apparatus, the document components recorded in the document data holding unit can be extracted according to the search condition input from the document browsing client. The extracted document constituent element is added with a document name and a hash value, and recorded again in the document data holding unit.

  The added document name and hash value are transmitted from the document search result providing unit to the document browsing client. As a result, the document browsing client can browse the document using the document name and the hash value.

Here, the document name is an arbitrary arbitrary document name given by the document search result generation unit corresponding to the search result. For example, it is given by a rule such as ““ search result ”+ serial number”. The hash value is a hash value that is unique corresponding to a search result generated by an MD5 (MessageDigestAlgorithm5) algorithm or the like based on data obtained by combining searched document components.

  (2) Furthermore, the document data browsing device searches the document browsing element from the document browsing client according to the document browsing condition and the document browsing receiving unit that receives the document browsing condition from the document browsing client. A document generation unit that generates document data by combining, a hash value verification unit that verifies whether the hash value of the document component constituting the generated document data is equal to the hash value of the viewing condition, and the generated document A document providing unit that transmits data to the document browsing client is provided.

  As a result, it is possible to generate document data from the divided document components by inputting browsing conditions from the document browsing client. Furthermore, by verifying the hash value, if the correct hash value is input, the document data corresponding to the hash value can be browsed. If the hash value is not input or incorrect, it is generated by the search result. The security of the document data can be ensured by being able to browse the document data.

  (3) The document collection unit of the document browsing device collects document data by converting the document data into structured document data when the document data collected from the document file server is not structured document data, and divides the document. The unit may take a configuration in which the document data is divided into document constituent elements based on the tag information of the structured document data.

  Thus, when the document data is structured text data such as XML data, the document data is divided into document components based on the tag information of the XML data, and when the document data is not structured text data, Based on the page information of the document data and the information of the document data, the document data can be divided into document components after being converted into structured text data.

(4) The document browsing accepting unit can also accept the document name added by the document search result generating unit as the browsing condition as the browsing condition. (5) Document configuration stored in the document data holding unit in advance You can also accept element item names as browsing conditions.

As a result, when browsing document data that combines specific document components based on conditions such as document name and item name, the document data cannot be browsed unless the correct hash value is passed. Even if it is unknown, document data can be provided in units of document components, and only part of the document data can be provided while ensuring document security.

  According to the present invention, the document data management device divides document data into sentence document components and stores them, thereby making the data of the document components meaningless, thereby improving the security of the entire document data. Can be secured.

  Further, even if the document data is meaningless as a single document component, it is possible to refer to the required document data by generating the document data by combining the document components using the hash value as a key. When the correct hash value is input, the correct document data can be referred to, and even if the hash value is not input or not correct, some document data is displayed. The security of document data can be ensured while ensuring the performance.

  In addition, since it is possible to refer to data in units of document components and to display a combination of document components according to conditions, the security of the original document data itself is guaranteed and It is possible to refer to the document component of the document data required by the.

1 is an overall configuration diagram of a system in which a document data management apparatus is used. It is a processing flowchart of document data collection. It is a figure which shows the example of document data collection setting. It is a processing flowchart of document data division. It is a process flowchart of a document data search process. It is a process flowchart of a document data browsing process. It is a process flowchart of a document data browsing process. It is a figure which shows the example of document data. It is a figure which shows the example of the document data of structured document data. It is a figure which shows the example of a division | segmentation of structured document data. It is a figure which shows the example of a division | segmentation of structured document data. It is a figure which shows the example of a preservation | save of a document component. It is a figure which shows the example of preservation | save of the document component of a document data search result. It is a figure which shows the example of the document search condition input screen in a document browsing client. It is a figure which shows the example of the document search result display screen in a document browsing client. It is a figure which shows the example of the document content display screen in a document browsing client. It is a figure which shows the example of the document content display screen in a document browsing client.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is an overall configuration diagram of a system in which a document data management apparatus is used. As shown in FIG. 1, a document data management apparatus 1 is connected to a document file server 3 and a document browsing client 2 via a network, collects document data stored in the document file server 3, and collects the document browsing client 2 Provide document data to In the document data management apparatus 1, the connection between the document file server 3 and the document browsing client 2 may be an internal network such as an intranet or a connection via an external network using the Internet.

  The document file server 3 is a server device in which document data is stored, such as a file server in an enterprise, an FTP (File Transfer Protocol) server, a WWW (Word Wide Web) server, and the document browsing client 2 is, for example, a mobile phone It is an information terminal such as a portable information terminal such as a telephone or a smartphone or a document browsing client that operates on a PC (Personal Computer) or the like.

  The document data management apparatus 1 includes a document search reception unit 101, a document search result generation unit 102, a document search result provision unit 103, a document provision unit 104, a hash value verification unit 105, a document generation unit 106, a document browsing reception unit 107, The document dividing unit 108, the document collecting unit 109, the document data holding unit 110, and the document collection setting storage unit 120 are included.

  Hereinafter, each part of the document data management apparatus 1 will be described.

  The document collection setting storage unit 120 stores a document collection setting that sets how to collect document data from which of the plurality of document file servers 3. The document collection setting is a setting item shown in FIG. The contents of the document collection setting will be described later.

  The document collection unit 109 refers to the document collection setting stored in the document collection setting storage unit 120 and collects document data from the document file server 3 according to the setting contents of the document collection setting.

  The document dividing unit 108 divides the document data collected from the document file server 3 by the document collecting unit 109 into document constituent elements and records them in the document data holding unit 110.

  The document data holding unit 110 holds the document components divided by the document dividing unit 108, the document components searched by the document search result generating unit 102, and the like. The contents of the document components held in the document data holding unit 108 are the contents shown in FIGS. The contents of the document component held in the document data holding unit will be described later.

  The document search reception unit 101 is connected from the document browsing client 2, receives the document search condition from the document browsing client 2, and delivers the received search condition to the document search result generation unit 102.

  The document search result generation unit 102 searches for document components from the document data holding unit 110 based on the search conditions of the delivered document search conditions. The same hash value is assigned to the document component of the search result. Combining document components results in one document data. The hash value and the document name are added to the document component of the search result, and are recorded in the document data holding unit 110 as the document component of the search result.

  The document search result providing unit 103 provides the document browsing client 3 with the document name and hash value generated by the document search result generating unit 102. The document browsing client 2 displays the provided document name and hash value.

  The document browsing reception unit 107 is connected from the document browsing client 2, receives a document browsing request, and delivers the content of the received browsing request to the document generation unit 106.

  The document generation unit 106 extracts document components from the document data holding unit 110 according to the request content of the browsing request delivered from the document browsing reception unit 107, and creates document data by combining the extracted document components. .

  The hash value verification unit 105 verifies whether the hash value of the document data created by the document generation unit 106 is correct. If the hash value is correct, the generated document is provided to the document browsing client 2 from the document providing unit 104, and the document browsing client 2 displays the document.

  Next, a specific example of processing executed by the document data management apparatus 1 will be described.

[Collecting and dividing document data]
2 is a process flowchart of the document collection unit 109, and FIG. 4 is a process flowchart of the document dividing unit 108. The document collection unit 109 collects document data from the document file server in accordance with the document collection setting stored in the document collection setting storage unit 120, and the collected document data is decomposed into document components by the document dividing unit 108. , Stored in the document data holding unit 110. The document data acquisition process is performed at regular time intervals in accordance with, for example, a predetermined collection cycle setting.

  FIG. 3 shows an example of document collection settings stored in the document collection setting storage unit 120. The document collection setting information shown in FIG. 3 includes setting items “setting name”, “server”, “server type”, “data acquisition method”, and “server connection setting”. The meaning of each setting item will be described below.

  “Setting name” is the name of the document collection setting. This setting name is used to identify what kind of document is collected. “Server” indicates the address of the server where the document is stored. “Server type” indicates the type of server as to what function the server has. For example, when “FILE” is set, it indicates a file server, and when “WEB” is set, it indicates a WWW (WordWideWeb) server, and “FTP” is set. If it is, it represents an FTP (File Transfer Protocol) server. “Data acquisition method” indicates a protocol used for data acquisition. For example, when “SMB” is set, it means that it is necessary to connect and acquire data using the Samba protocol, and when “HTTP” is set, it is necessary to connect and acquire data using the HTTP (HyperTextTransfer Protocol) protocol. When “FTP” is set, it indicates that it is necessary to acquire data by connecting with the FTP protocol. “Server connection setting” sets authentication conditions (connection ID and password), connection setting (connection character string), and the like for connecting to the server. For example, in the case of a server with a protocol that requires authentication by ID and password for server connection, the setting is made as “ID: XXXX, PWD: YYYYY”, and authentication is performed using XXXX as the ID and YYYYY as the password. A connection to the server is made.

  Here, the details of document data collection and conversion processing will be described based on the processing flowcharts of FIGS.

  FIG. 2 shows a document data collection process flow. In step S 101 shown in FIG. 2, first, the document collection unit 109 acquires a list of document collection settings as shown in FIG. 3 from the document collection setting storage unit 120. Next, in step S102, the processing from step S103 to step S105 is repeated for each document collection setting for the number of acquired document collection settings. For example, in the document collection setting example of FIG. 3, since three document collection settings are set, the processing from step S103 to step S105 is repeated three times.

  In the next step S103, the server is connected to the server set in the “server” of the document collection setting. Connection to the server is made based on information set in “server type”, “data acquisition method”, and “server connection setting”. For example, in FIG. 3, the document collection settings defined as “data collection settings from file server” in “setting name” are “server”, “server type”, “data acquisition method”, and “server connection setting”, respectively, and “groupFileServer”. ”,“ FILE ”,“ SMB ”,“ ID: XXXXXX, PWD: YYYYY ”. When set in this way, the connection is made to the FILE server groupFileServer using the Samba protocol with IDXXXX as the ID and YYYYY as the password.

  When the connection to the server is made, in step S104, the document data stored in the connected server is acquired. Acquisition of document data is performed based on information set in the “data acquisition method” of the document collection setting. For example, when “FTP” is set in the “data acquisition method”, document data acquisition processing is performed using the FTP protocol. The document data may be acquired by acquiring all the document data stored in the server, or by separately setting an acquisition rule and acquiring the document data according to the acquisition setting rule.

  When the document data is acquired from the server, in step S105, the acquired document data is divided and the divided document data is stored in the document data holding unit 110. Document data division processing and storage processing are performed on all the document data acquired in step S104. Details of document data division processing and storage processing will be described later based on the document data division processing flow shown in FIG.

  After the processing has been completed for all the acquired document data, in step S106, it is confirmed whether or not all the document collection settings have been processed. If it is determined that the processing has not been completed for all the document collection settings (No in step S106), the process returns to step S102, and the next document collection setting process is performed. If it is determined that the processing has been completed for all the document collection settings (step S106, Yes), the document data collection and conversion processing is terminated.

  Next, details of document data division processing and storage processing will be described based on the processing flow of FIG. This document data dividing process flow details the document dividing process in step S105 described above.

  The document division processing is processed by the document division processing unit 108. First, in step S201, information of document data to be divided is acquired from the document collection unit 109 as structured document data. The document data to be converted is, for example, text data as shown in FIG. 8. When text data is stored as structured document data, it is acquired as text-structured structured document data as shown in FIG. The Here, when the data format of the document data is not stored as structured text data, the data format is converted into structured document data such as an XML data format. The conversion to structured text data is performed to structured text data based on document data property information such as document data file information and page information, and the meaning of data included in the document data. For example, if the document data is tabular data, the columns of the table can be converted as a component of the document data, and even if the document data is composed of only sentences, It can be converted into structured text data based on the title information. If the file format is already structured text data, the conversion process is not performed.

  When the document data is acquired, the structured document data is divided into document components in step S202. In general, structured document data includes tags and attributes. For example, in a data line described as <DATA NAME = “product description”>, DATA is a tag name and NAME is an attribute name. In the attribute, an attribute representing the type of the data is defined. Here, it can be seen that “product description” is defined as the NAME attribute in the DATA tag.

  As an example of the document data dividing process, data is divided based on tag attribute information. FIG. 10 shows an example in which structured text data is divided based on tag attribute information. In this example, structured text data is divided in units of NAME attributes of DATA tags. The structured text data divided based on the tag attribute information is further divided by internal tags. FIG. 11 shows an example in which document data divided by attribute information is further divided by internal tags. As shown in FIG. 11, the hierarchical structure of the document data divided by the attribute information is divided to the minimum unit by an internal tag.

  A unit obtained by dividing document data as structured document data into a minimum unit by a hierarchical internal tag is a document constituent element. When the document composition summary is divided, the document composition elements divided in step S203 are classified for each attribute. The attribute to be classified is classified according to the attribute of the tag used when dividing the document data in step S202. In step S204, the same hash value is associated with the document components divided from the same document data. The hash value is, for example, a unique hash value generated from document data by a known MD5 algorithm or the like.

  When the document data is divided into document constituent elements and the hash value is set, the document constituent element and the hash value divided in step S205 are recorded in the document data holding unit 110. FIG. 12 shows an example in which the document data in the structured text data format shown in FIG. 9 is divided and recorded in the document data holding unit 110. In FIG. 12, “document name” represents the document name of the document data from which the document is divided, “attribute” represents the attribute information name when divided in step S202 and classified in step 203, and “tag” represents the step. The tag name of the document component divided to the minimum unit in S202 is represented, the “value” represents the value of the document component divided to the minimum unit in step S202, and the “hash value” is assigned in step S204. Represents a hash value.

  The above is the details about the collection and division processing of document data. As described above, since the document data divided into document components is related by the hash value, it is restored to one document data by combining the document components divided using the hash value as a related key. Is possible.

  Next, a document component search and browsing method in the document browsing client 2 will be described in detail.

[Document data search processing]
The search for the document component is performed by transmitting a search keyword from the document browsing client 2 to the document search receiving unit 101. FIG. 14 shows an example of a search condition input screen displayed on the document browsing client 2. In FIG. 14, a keyword character string serving as a search condition is input in the search keyword input field, and when the search button is pressed, the search keyword is transmitted from the document browsing client 2 to the document search reception unit 101 as a search condition.

  FIG. 5 is a process flowchart of the document search process. In step S <b> 301, the document search reception unit 101 acquires the search condition transmitted from the document browsing client 2. In step S302, the document search result generation unit 102 searches the document component from the document data holding unit 110 based on the search condition acquired by the document search reception unit 101, and generates a combination of document components. In step S303, a hash value is generated from the combination of document components, the same hash value is assigned to each retrieved document component, and the retrieved document component and hash value provided in step S304. Is assigned a document name and recorded in the document data holding unit 110. The document name may be given a name generated from the search condition, or a fixed character string may be given a name generated by a combination of sequential numbers, or any document name can be assigned. Also good.

  For example, when document components are recorded in the document data holding unit 110 as shown in FIG. 12, if “product name = ice making machine” is input from the document browsing client 2 as a search keyword, The search receiving unit 101 acquires the search keyword “product name = ice machine” as a search condition, and the document search result generation unit 102 determines that the “tag name” is “product” from the document components recorded in the document data holding unit 110. A search is made for the classification of document components whose “value” is “ice machine” in “value”, and a combination of document components as shown in FIG. 13 is generated. Then, in order to identify the combination of document components generated by the same search condition, the same hash value is set for each document component, and the document name is set to the document name. “Search result 01” is set, and the document component combination shown in FIG. 13 is recorded in the document data holding unit 110 by the document search result generation unit 102.

  When the document component of the search result is recorded in the document data holding unit 110, the document name and hash value are transmitted as the search result from the document search result providing unit 103 to the document browsing client 2 in the next step S305. FIG. 15 shows an example of a screen on which a document name and a hash value are displayed as a search result in the document browsing client 2.

  As described above, the search keyword input and search method may be a search by inputting a tag name and its value, a free word search, or any search method used in a normal text search. It may be a method. Further, a combination of document constituent elements and a hash value as search results may be arbitrarily generated in advance and recorded in the document data holding unit 110. By doing so, it is possible to create a combination of frequently referred document components in advance, and it is possible to easily refer to document data simply by inputting a search condition and a hash value.

  Next, a process for browsing the document components recorded in the document data holding unit 110 by the document data search process will be described in detail.

[Document data browsing process]
Browsing of the document components recorded in the document data holding unit 110 is performed by the document browsing client 2, and the browsing method is to select a combination of document components continuously searched from the document search result display screen in FIG. There are cases of browsing and cases of browsing by inputting a search keyword and a hash value on the search condition input screen in FIG.

  FIG. 6 shows a processing flow in the case of browsing a combination of document components that are continuously searched from the document search result, and FIG. 7 shows a processing flow in the case of browsing a combination of document components from a search keyword and a hash value. Represent.

  First, based on FIG. 6, a process in the case of browsing a combination of document constituent elements that are continuously searched from the document search result will be described in detail. When the search result screen as shown in FIG. 15 is displayed in the document browsing client 2, when the browse button is pressed, the document browsing client 2 sends the document name and the hash value to the document browsing receiving unit 107. In step S401, the document browsing receiving unit 107 receives the sent document name and hash value. In step S <b> 402, the document generation unit 106 searches the document component from the document data holding unit 110 based on the document name acquired by the document browsing reception unit 107. Here, the document component whose item “document name” recorded in the document data providing unit 110 matches the document name acquired by the document browsing receiving unit 107 is searched. In step S403, document data is generated by combining the retrieved document components. Next, in step S404, it is verified whether or not the hash value acquired by the document browsing acceptance unit 107 is included in the hash value assigned to the retrieved document component.

  In step S405, if the hash value verified in step S404 is included (S405, YES), the process proceeds to step S406, and the document corresponding to the verified hash value from the document data generated by the document providing unit 104 in step S403. Only the document data composed of the components is returned to the document browsing client 2. In step S405, if the hash value verified in step S404 is not included (S405, No), the process proceeds to step S407, and the document providing unit 104 sends all of the document data generated in step S403 to the document browsing client 2. return.

  In this way, even when document data is displayed from the search result, by controlling the display by verifying the hash value, for example, when there is an illegal screen transition, the document search result is transferred to other users. Since it is possible to control the display of the document data generated by the document search when the user does not want to browse the document data, the security of the document data can be ensured. In other words, if the hash value generated from the search result is sent correctly, the document data of the search result corresponding to the hash value is displayed, and it is sent even if the hash value is not correct. Some document data corresponding to the retrieved result is displayed. Therefore, since the person who performed the search can browse some document data, even if the document data is illegally browsed, it is possible to misunderstand that the incorrect document data is the correct document data. , The concealment of document data can be improved.

  Next, based on FIG. 7, a process in the case where document data is browsed by inputting a search keyword and a hash value from the document search condition input screen will be described in detail. When a document search condition input screen as shown in FIG. 14 is displayed in the document browsing client 2, when the search keyword and hash value are input and the browse button is pressed, the document browsing reception unit 107 receives the document browsing client 2. Search keyword and hash value are sent to.

  In step S501, the document browsing receiving unit 107 receives the sent search keyword and hash value as browsing conditions. In step S <b> 502, the document generation unit 106 searches the document component from the document data holding unit 110 based on the search keyword acquired by the document browsing reception unit 107. For example, when a document name is specified as a search keyword, the “document name” item of the sentence structure data recorded in the document data providing unit 110 is the document name of the search condition acquired by the document browsing receiving unit 107. A matching document component is searched. In step S504, it is checked whether the hash value is sent from the document browsing client 2 to the document browsing receiving unit 107. If the hash value is not sent (S504, No), the process proceeds to step S508, and the document providing unit 104 returns all the document data generated in step S503 to the document browsing client 2. If the hash value has been sent (S504, Yes), the process proceeds to step S505 in order to verify whether the sent hash value is correct.

  In step S505, it is verified whether or not the hash value assigned to the document component searched in step S503 includes the hash value acquired by the document browsing reception unit 107. In step S506, if the hash value verified in step S505 is included (S506, Yes), the process proceeds to step S507, and the document providing unit 104 generates the verified hash value from the document data generated in step S503. Only the document data composed of the corresponding document components is returned to the document browsing client 2. In step S506, if the hash value verified in step S505 is not included (S506, No), the process proceeds to step S508, and the document providing unit 104 sends all of the document data generated in step S403 to the document browsing client 2. return.

  In this way, by inputting the search keyword and the hash value so that the document data can be displayed, the document data generated by the past document search process can be displayed or arbitrarily created in the document data holding unit 110. It is possible to display the document data recorded at any time. Furthermore, by verifying the hash value and controlling the display, even if the document name and other conditions are known as search conditions for the document data to be displayed, the document data cannot be browsed unless the correct hash value is entered. Therefore, the security of the document data can be ensured. Even if the hash value is incorrect or not entered, some document data is displayed instead of making the browsing error. As a result, even if the document data is illegally browsed, the viewer can be mistaken as if the target document data was displayed, so that the unauthorized browsing process can be prevented again. Can do.

  Individual data of the document constituent elements that are divided and recorded in the document data holding unit 110 can be used as document data that can be used as data alone, but by combining them, the entire document data has value. This is document data. According to the method of the present invention, document data having a specific value can be generated by combining document components if the hash value is known, and the document data is kept secret to those who do not know the hash value. Can do. On the other hand, even if the hash value is not known, document data can be newly generated and browsed by a search keyword, so that the divided document components can be used effectively.

  FIG. 16 shows a display example of generated document data in the document browsing client 2. Since the generated document data is displayed as structured text data as shown in FIG. 16, it can be reprocessed into an arbitrary format and used. For example, it is also possible to display a generated document in a table form as shown in FIG. 17 by performing browsing definition of structured text data.

  The document data collection and division process, the document data search process, and the document data browsing process performed in the document data management apparatus have been described in detail. The apparatus for managing the document data includes a computer and a software program. The program can be realized, and the program can be recorded on a computer-readable recording medium or provided through a network.

DESCRIPTION OF SYMBOLS 1 Document data management apparatus 2 Document browsing client 3 Document file server 101 Document search reception part 102 Document search result generation part 103 Document search result provision part 104 Document provision part 105 Hash value verification part 106 Document generation part 107 Document browsing reception part 108 Document Division unit 109 Document collection unit 110 Document data holding unit 120 Document collection setting storage unit

Claims (6)

A document collection setting storage unit that stores document collection settings that define how to collect document data from a server device connected to the network;
A document collection unit for collecting document data stored in the server defined in the document collection setting;
A document data dividing unit for dividing the document data collected by the document collecting unit into document components;
A document data holding unit for holding document components divided by the document data dividing unit;
A document search receiving unit for receiving a search condition for searching for a document component stored in the document data holding unit from an information terminal connected to a network;
Searching document components from the document data holding unit based on the search condition received by the document search receiving unit, adding a document name and hash value to the document component of the search result, and holding the document component in the document holding unit A document search result generation unit for generating document components by means of
A document data management apparatus comprising: a document search result providing unit that provides a document name and a hash value added by the document search generation unit to the information terminal. The document data management apparatus according to claim 1, wherein
The document collection unit is a document collection unit that collects document data by converting the collected document data into a structured document data format when the collected document data is not in a structured document data format;
The document dividing unit is a document dividing unit that divides document data into document components based on tag information of structured text data. In the document data management device according to claim 1 or 2,
A document browsing receiving unit that receives browsing conditions including at least a hash value from the information terminal;
A document generation unit that searches the document data holding unit based on the browsing conditions received by the document browsing reception unit and generates document data by combining the searched document components;
A hash value verification unit that verifies whether the hash value included in the viewing condition is included in the hash value of the document component searched in the document generation unit;
A document providing unit that provides document data corresponding to a hash value from the document data generated by the document generation unit to the information terminal when the hash value verification unit determines that a hash value is included; A document data management apparatus comprising: In the document data management apparatus according to claim 3,
The document browsing receiving unit is a document browsing receiving unit that receives, as a browsing condition, a document name added by the document search result generation unit as a browsing condition. In the document data management device according to claim 3 or 4,
The document browsing receiving unit is a document browsing receiving unit that receives, as browsing conditions, item names of document components recorded in the document data storage unit as browsing conditions.   A document data providing program for causing a computer to function as each processing unit provided in the document data management device according to any one of claims 1 to 5.