Server device, information processing method, and information processing program

Abstract

To properly manage accumulated data sizes in a solution for searching for a document in a cross-sectional manner from various cloud storage services.SOLUTION: A server device includes an index information acquisition unit which sets a first acquisition level for acquiring first index information or a second acquisition level for acquiring second index information larger in size than the first index information, regarding acquisition levels for acquiring multiple pieces of index information for multiple files stored in a plurality of cloud storage services, calculates an estimated total size of the multiple pieces of index information to be acquired, based on the set acquisition level, acquires, when the estimated total size is equal to or smaller than an upper limit value, the multiple pieces of index information based on the set acquisition level, and accumulates the index information in an index information storage.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a server device, an information processing method, and an information processing program that obtain index information of files recorded in cloud storage and present it to a user via a terminal device. [Background technology]

[0002] A variety of providers offer cloud storage services. As a solution for searching documents across a variety of cloud storage services, a technique for saving index information of documents obtained from each cloud service is known. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2001-306371 A [Patent Document 2] JP 2009-134627 A [Patent Document 3] JP 2008-158685 A Summary of the Invention [Problem to be solved by the invention]

[0004] Depending on the number of files stored in cloud storage, storage capacity and processing performance may increase, and operational costs may also increase.

[0005] According to Patent Document 1, the data capacity of an index is estimated based on the number of records and the number of indexes. According to Patent Document 2, the data size of the index is estimated and the priority order of index creation is determined taking into account the free storage capacity. However, these methods do not take into account calculation methods according to document types or index methods according to storage upper limits.

[0006] According to Patent Document 3, when performing a full-text search, the search time for the text scan method and the search time for the index scan method are predicted, and the search process is performed using the shorter search method. However, there is no mechanism for index capacity, and the index cannot be stopped or resumed depending on the index capacity.

[0007] In view of the above circumstances, an object of the present disclosure is to appropriately manage the size of accumulated data in a solution for searching documents across various cloud storage services. [Means for solving the problem]

[0008] A server device according to an embodiment of the present disclosure includes: Regarding an acquisition level when acquiring a plurality of pieces of index information for each of a plurality of files stored in a plurality of cloud storages, either a first acquisition level for acquiring a first piece of index information or a second acquisition level for acquiring a second piece of index information having a size larger than that of the first piece of index information is set; Calculating a predicted total size of the plurality of index information to be acquired based on the set acquisition level; If the predicted total size is equal to or smaller than an upper limit value, the plurality of index information are acquired based on the set acquisition level, and are stored in an index information storage. An index information acquisition unit; an index information presenting unit that presents the plurality of pieces of index information related to the plurality of files to a user via a terminal device, without distinguishing in which of the plurality of cloud storages the plurality of files are stored; Equipped with:

[0009] According to this embodiment, by setting an upper limit on the index size, it is possible to prevent an increase in cloud storage costs. By calculating the predicted total size of the index information in advance and notifying the user, the user can know whether or not the index information can be used within the upper limit. If there is a possibility that the predicted total size of the index information will exceed the upper limit, the search range and acquisition level of the index information can be adjusted so that the size falls within the range.

[0010] An information processing method according to an embodiment of the present disclosure includes: Regarding an acquisition level when acquiring a plurality of pieces of index information for each of a plurality of files stored in a plurality of cloud storages, either a first acquisition level for acquiring a first piece of index information or a second acquisition level for acquiring a second piece of index information having a size larger than that of the first piece of index information is set; Calculating a predicted total size of the plurality of index information to be acquired based on the set acquisition level; If the predicted total size is equal to or smaller than an upper limit value, acquire the plurality of index information based on the set acquisition level, and store the plurality of index information in an index information storage; The plurality of pieces of index information relating to the plurality of files are presented to a user via a terminal device, without distinguishing in which of the plurality of cloud storages the plurality of files are stored.

[0011] An information processing program according to an embodiment of the present disclosure includes: The processor of the server device, Regarding an acquisition level when acquiring a plurality of pieces of index information for each of a plurality of files stored in a plurality of cloud storages, either a first acquisition level for acquiring a first piece of index information or a second acquisition level for acquiring a second piece of index information having a size larger than that of the first piece of index information is set; Calculating a predicted total size of the plurality of index information to be acquired based on the set acquisition level; If the predicted total size is equal to or smaller than an upper limit value, the plurality of index information are acquired based on the set acquisition level, and are stored in an index information storage. An index information acquisition unit; an index information presenting section that presents the plurality of pieces of index information relating to the plurality of files to a user via a terminal device, without distinguishing in which of the plurality of cloud storages the plurality of files are stored; Operate as. Effect of the Invention

[0012] According to the present disclosure, in a solution for searching documents across various cloud storage services, it is possible to appropriately manage the size of accumulated data.

[0013] Note that the effects described herein are not necessarily limited to those described herein, and may be any of the effects described in this disclosure. [Brief description of the drawings]

[0014] [Figure 1] 1 illustrates a network system according to an embodiment of the present disclosure. [Diagram 2] 2 shows the functional configuration of the server device. [Diagram 3] 13 shows an operation flow of an index information acquisition unit of the server device. [Figure 4] 11 shows a connection destination information setting screen. [Diagram 5] 13 shows a search query and acquisition level setting screen. [Figure 6] 13 is an example of a predicted total size display screen. [Figure 7] 13 is an example of an index information list display screen. [Figure 8] 13 is another example of the index information list display screen. [Figure 9] 13 shows an operation flow of an acquisition level changing unit of the server device. [Figure 10]13 is an example of a screen displaying the total size of index information. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.

[0016] 1. Network System

[0017] FIG. 1 illustrates a network system according to an embodiment of the present disclosure.

[0018] The network system 1 includes a server device 10, a plurality of cloud storages 20, an index information storage 30, and a terminal device 40. The server device 10, the plurality of cloud storages 20, the index information storage 30, and the terminal device 40 are connected via a network such as the Internet. The terminal device 40 is a personal computer or the like used by a user.

[0019] Each of the multiple cloud storages 20 is typically a cloud storage 20A provided by a third party. The multiple cloud storages 20 may further include a cloud storage 20B provided by the provider of the server device 10. In the multiple cloud storages 20, a user can store a large number of various files 201, such as documents and images, via a cloud storage service.

[0020] The server device 10 acquires index information for each of the many files 201 stored in the multiple cloud storages 20, and accumulates the information in the index information storage 30. The index information is information that an end user refers to in order to select a file 201 to be used from the many files 201 stored in the multiple cloud storages 20.

[0021] The server device 10 and the terminal device 40 are in a server-client system relationship via a web browser. The server device 10 presents the index information accumulated in the index information storage 30 to the user via the terminal device 40 so that the index information can be searched across the board, without distinguishing in which cloud storage 20 the numerous files 201 are stored. When the user searches for index information via the terminal device 40, the server device 10 retrieves the file 201 indicated by the index information from the cloud storage 20 in which the file 201 is stored, and outputs the file 201 to the terminal device 40.

[0022] 2. Functional configuration of the server device

[0023] FIG. 2 shows the functional configuration of the server device.

[0024] The server device 10 operates as an index information acquisition unit 101, an index information presentation unit 102, and an acquisition level change unit 103 by the CPU loading an information processing program recorded in the ROM into the RAM and executing it.

[0025] 3. Operation of the server device

[0026] 3-1. Index information acquisition section

[0027] FIG. 3 shows the operation flow of the index information acquisition unit of the server device.

[0028] The operation flow of the index information acquisition unit 101 is an operation flow when starting to collect index information 202 during initial setup of the service provided by the server device 10. As a premise, a large number of files 201 are stored in each of the multiple cloud storages 20.

[0029] FIG. 4 shows the connection destination information setting screen.

[0030] The index information acquisition unit 101 displays a connection destination information setting screen 200 for each cloud storage 20 on the browser of the terminal device 40. The user sets connection destination information such as a label, a graph ID, a graph secret, a tenant, and a host name on the connection destination information setting screen 200 (step S101).

[0031] FIG. 5 shows a search query and acquisition level setting screen.

[0032] The index information acquisition unit 101 then displays a search query and acquisition level setting screen 300 on the browser of the terminal device 40. The search query and acquisition level setting screen 300 is a screen for setting a search query and an acquisition level for each cloud storage 20, or for each group (e.g., for each folder) of multiple files 201 stored in the cloud storage 20. The user sets a search query and an acquisition level via the search query and acquisition level setting screen 300 (step S102).

[0033] The acquisition level is an acquisition level when acquiring index information 202 of each of a plurality of files 201 stored in the cloud storage 20. There are a first acquisition level 301 and a second acquisition level 302. The first acquisition level 301 is an acquisition level for acquiring only property information (first index information) of the file 201, i.e., only metadata. The property information includes, for example, a file name, an update date and time, a file size, and other property data. The second acquisition level 302 is an acquisition level for acquiring text information (second index information) included in the file 201 in addition to the property information of the file 201, i.e., metadata. The text information is substantial data such as text information in searchable PDF data and text information in the document file 201. For this reason, the second index information acquired when the second acquisition level 302 is set is larger in size than the first index information acquired when the first acquisition level 301 is set.

[0034] The search query is used by the index information acquisition unit 101 to execute the search query and acquire index information 202 from the cloud storage 20. The search query can be set uniquely for each cloud storage 20, or for each group (e.g., for each folder) of multiple files 201 stored in the cloud storage 20. The search query defines the search range. The search range is, for example, the target cloud storage 20, the range of folders in the cloud storage 20, the update date and time period (the most recent six months, etc.), etc. The search query further defines at which acquisition level (first acquisition level or second acquisition level) the index information 202 is acquired for that search range.

[0035] The index information acquisition unit 101 displays the connection destination information setting screen 200 and the search query and acquisition level setting screen 300 for all cloud storages 20 on the browser of the terminal device 40, and accepts the user's settings (step S103).

[0036] Before actually executing a query to acquire all index information 202 from all cloud storages 20, the index information acquisition unit 101 calculates the predicted total size of all the index information 202 to be acquired and presents it to the user via the terminal device 40 (step S104).

[0037] Specifically, the index information acquisition unit 101 calculates the predicted total size of all the index information 202 to be acquired based on the number of index information 202 to be acquired and the acquisition level (first acquisition level or second acquisition level) set for each of the index information 202 to be acquired.

[0038] More specifically, the index information acquisition unit 101 assumes the size of the first index information to be a uniform value (for example, 10 KB) regardless of the type or size of the file 201. The index information acquisition unit 101 assumes the size of the second index information of the file 201 not including text information (for example, an image file, a video file, an image PDF, etc.) to be a uniform value (for example, 10 KB) regardless of the size of the file. The index information acquisition unit 101 calculates the size of the second index information of the file including text information (for example, a searchable PDF, a document file, a spreadsheet file, a presentation file, etc.) based on the size of the file 201 (for example, file size x 1 / 10). The index information acquisition unit 101 calculates the predicted total size as (the number of files 201 to which the first acquisition level is set x uniform value) + (the value calculated for each file 201 including text information to which the second acquisition level is set) + (the number of files 201 not including text information to which the second acquisition level is set x uniform value).

[0039] The index information acquisition unit 101 further indicates to the user via the terminal device 40 whether the calculated predicted total size is equal to or smaller than the upper limit (step S105). The upper limit is the value of the storage capacity contracted between the user and the provider of the server device 10 (purchased by the user).

[0040] FIG. 6 is an example of a predicted total size display screen.

[0041] The predicted total size display screen 400 displays the total number 401 of files 201 for which index information 202 should be obtained, the total number 402 of files 201 for which first index information should be obtained, the total number 403 of files 201 for which second index information should be obtained, the predicted size 404 of the first index information, and the predicted size 405 of the second index information. As in this example, the predicted size 404 of the first index information and the predicted size 405 of the second index information may be displayed as a colored portion of the entire bar with a total length of 1 / 2 the upper limit value. This allows the user to visually understand the ratio of the predicted total size (the total of the colored predicted size 404 of the first index information and the predicted size 405 of the second index information) to the upper limit value (the total of the two bars). Alternatively, the predicted size 404 of the first index information and the predicted size 405 of the second index information may not be distinguished into two bars, but the upper limit value may be one bar, and the predicted total size of that bar may be colored (not shown). In addition, an expected time 406 required to acquire all the index information 202 and a warning 407 may be further displayed.

[0042] As a result of comparing the predicted total size with the upper limit, the user can return to the acquisition level setting screen 300 and reset the search query, thereby changing the range and / or acquisition level of the multiple index information 202 to be acquired via the terminal device 40 (step S106). For example, if the predicted total size exceeds the upper limit, the user may change the setting to reduce the predicted total size, such as narrowing the search range (shortening the period, etc.) or resetting a search query set with the second acquisition level to the first acquisition level. Conversely, if the predicted total size is less than the upper limit, the user may change the setting to increase the predicted total size, such as widening the search range (lengthening the period, etc.) or resetting a search query set with the first acquisition level to the second acquisition level.

[0043] When the predicted total size becomes equal to or less than the upper limit, the index information acquisition unit 101 acquires index information 202 (first index information and second index information) from multiple cloud storages 20 based on a search query based on a set acquisition level (first acquisition level or second acquisition level). The index information acquisition unit 101 accumulates the acquired index information 202 (first index information and second index information) in the index information storage 30 (step S107).

[0044] Thereafter, the index information acquisition unit 101 acquires index information 202 (first index information and second index information) from the multiple cloud storages 20 in response to a predetermined trigger, and accumulates the index information 202 in the index information storage 30. The predetermined trigger may be, for example, receiving information indicating that a file 201 stored in the cloud storage 20 has been updated, detecting the addition of a file 201 stored in the cloud storage 20, etc.

[0045] 3-2. Index information presentation section

[0046] FIG. 7 is an example of an index information list display screen.

[0047] The index information presenting unit 102 cross-sectionally searches a large number of index information 202 stored in the index information storage 30. The index information presenting unit 102 can present a plurality of pieces of index information 202 relating to a plurality of files 201 stored in the index information storage 30 to a user via the terminal device 40, without distinguishing in which of a plurality of cloud storages 20 the plurality of files 201 are stored. As a result, the index information presenting unit 102 can cross-sectionally search not only the files 201 stored in the cloud storage 20 provided by the provider of the server device 10, but also the files 201 stored in a plurality of cloud storages 20 provided by third parties.

[0048] The index information presenting unit 102 displays the searched index information 202 as a list 510 on the index information list display screen 500 in descending order of hit rate score (antenna bar) 501 according to the search results of the file name and text information, regardless of which cloud storage 20 is the storage location. For example, the hit rate score (antenna bar) 501, check boxes 507, and file names 502 and folder paths 503 included in the index information 202 may be displayed as a list 510 on the index information list display screen 500. When a user selects a certain index information 202 with the check boxes 507, the index information presenting unit 102 may display the name 522 of the cloud storage 20 which is the storage location of the file 201 specified by the selected index information 521, and may display a tree 523 indicating the folder path of the cloud storage 20. In addition, when a user selects a certain index information 202 using the check box 507, the index information presenting unit 102 may display the text information acquired as the second index information on the browser of the terminal device 40, if there is such text information.

[0049] FIG. 8 shows another example of the index information list display screen.

[0050] On the index information list display screen 500, for example, a hit rate score (antenna bar) 501, check boxes 507, file names 502 included in the index information 202, folder paths 503, update dates and times 504, creators 505, and file sizes 506 may be displayed as a list 510. When the user selects the searched index information 202 (for example, file names 502), a preview can be displayed on the browser of the terminal device 40, or the terminal device 40 where the information is saved can be accessed.

[0051] 3-3. Acquisition level change section

[0052] FIG. 9 shows the operation flow of the acquisition level changing unit of the server device.

[0053] As described above, the index information acquisition unit 101 acquires index information 202 (first index information and second index information) from multiple cloud storages 20 in response to a specific trigger, and accumulates the information in the index information storage 30. The operation flow of the index information acquisition unit 101 is an operation flow when a long time has passed and the total size of the index information 202 accumulated in the index information storage 30 has increased.

[0054] The acquisition level change unit 103 judges that the total size of the plurality of index information 202 stored in the index information storage 30 exceeds a threshold (step S201). The threshold may be equal to or less than an upper limit value (the value of the storage capacity contracted (purchased by the user) between the user and the provider of the server device 10). When the total size of the plurality of index information 202 stored in the index information storage 30 exceeds the threshold, the acquisition level change unit 103 stops acquiring the second index information. When the acquisition level change unit 103 stops acquiring the second index information, it changes (switches) the setting of the second acquisition level to the first acquisition level (step S202). As a result, the index information acquisition unit 101 acquires the first index information even for a file for which the second acquisition level is set by the user.

[0055] FIG. 10 is an example of a screen displaying the total size of index information.

[0056] The acquisition level change unit 103 may present a total size display screen 600 of the index information 202 to the user via the terminal device 40. The total size display screen 600 displays the total size of the multiple index information 202 stored in the index information storage 30. In this example, the total size display screen 600 displays a size 601 of the first index information, a size 602 of the second index information, and a total size 603 of these. Furthermore, the total size display screen 600 may display that the total size 603 exceeds a threshold. The total size display screen 600 may present to the user via the terminal device 40 whether or not the total size of the multiple index information 202 stored in the index information storage 30 is equal to or smaller than an upper limit value. As in FIG. 6, the ratio of the total size 603 to the threshold value or the upper limit value may be displayed so that the user can visually understand it. The acquisition level change unit 103 may present to the user via the terminal device 40 that the setting of the second acquisition level is changed to the first acquisition level and the first index information is acquired.

[0057] After changing (switching) the setting of the second acquisition level to the first acquisition level, the acquisition level change unit 103 determines that the total size of the index information is reduced (is likely to be reduced) due to the occurrence of a predetermined condition (step S203). The total size of the index information is reduced when, for example, the following two conditions occur:

[0058] First, the acquisition level change unit 103 receives explicit information from the cloud storage 20 side indicating that the file 201 stored in the cloud storage 20 has been updated. Detailed change information cannot be obtained from the cloud storage 20 side. For this reason, the acquisition level change unit 103 judges whether the update of this file 201 corresponds to the deletion of the file 201, the reduction in the size of the file 201, or the deletion of the folder in which the file 201 is saved. If the update of this file 201 corresponds to any of these, the acquisition level change unit 103 judges that the total size of the second index information will decrease. On the other hand, if the update of this file 201 does not correspond to any of these, the acquisition level change unit 103 judges that the total size of the second index information will not decrease (i.e., there is no change or increases).

[0059] Secondly, when the user changes the range (period, folder, etc.) and / or acquisition level of the multiple index information 202 to be acquired, i.e., the search query, via the terminal device 40, the acquisition level change unit 103 determines that the total size of the second index information will decrease depending on the changes.

[0060] When the acquisition level change unit 103 determines that the total size of the index information will decrease (step S203), it calculates a predicted amount of the total size after the decrease (step S204). When calculating the predicted amount of the total size after the decrease, the acquisition level change unit 103 assumes the size of the first index information to be a uniform value (e.g., 10 KB) as in the above, assumes the size of the second index information of the file 201 not including text information to be a uniform value, and calculates the size of the second index information of the file including text information based on the size of the file 201 (e.g., file size x 1 / 10).

[0061] When the predicted amount after the reduction of the total size of the index information is equal to or less than the threshold (step S205), the acquisition level change unit 103 changes (switches again) the setting so as to return the first acquisition level to the second acquisition level (step S206). Here, the threshold may be equal to or less than the upper limit value (the value of the storage capacity contracted (purchased by the user) between the user and the provider of the server device 10).

[0062] This causes the index information acquisition unit 101 to resume acquisition of the second index information. That is, the index information acquisition unit 101 acquires the second index information for the file whose setting has been changed to the first acquisition level, according to the user's initial setting.

[0063] 4. Conclusion

[0064] By setting an upper limit on the index size in the index information acquisition unit 101, it is possible to prevent an increase in the cost of the cloud storage 20. By calculating the predicted total size of the index information 202 in advance and notifying the user, the user can know whether or not the information can be used within the upper limit. If there is a possibility that the predicted total size of the index information 202 will exceed the upper limit, the search range and acquisition level of the index information can be adjusted so that the size falls within the range.

[0065] In the acquisition level change unit 103, by setting an upper limit value for the index size, it is possible to stop or resume acquisition of the second index including text information according to the size of index information already acquired. If the search range of the files to be indexed is reduced, etc., and the predicted amount after the reduction in the total size of the index information falls within the upper limit, acquisition of the second index is automatically resumed, thereby increasing the number of files for which text information can be searched, and the user can perform a text search from the browser of the terminal device 40.

[0066] Although the embodiments and modified examples of the present technology have been described above, the present technology is not limited to the above-described embodiments, and it goes without saying that various modifications can be made within the scope of the gist of the present technology. [Explanation of symbols]

[0067] Network System 1 Server device 10 Cloud Storage 20 Index Information Storage 30 Terminal device 40 Index information acquisition unit 101 Index information presentation unit 102 Acquisition level change unit 103 File 201 Index Information 202

Claims

1. Regarding an acquisition level when acquiring a plurality of pieces of index information for each of a plurality of files stored in a plurality of cloud storages, either a first acquisition level for acquiring a first piece of index information or a second acquisition level for acquiring a second piece of index information having a size larger than that of the first piece of index information is set; Calculating a predicted total size of the plurality of index information to be acquired based on the set acquisition level; If the predicted total size is equal to or smaller than an upper limit value, the plurality of index information are acquired based on the set acquisition level, and are stored in an index information storage. An index information acquisition unit; an index information presenting unit that presents the plurality of pieces of index information related to the plurality of files to a user via a terminal device, without distinguishing in which of the plurality of cloud storages the plurality of files are stored; A server device comprising:

2. 2. The server device according to claim 1, When calculating the predicted total size, the index information acquisition unit Calculating a size of the second index information of a file including text information based on a size of the file; The size of the second index information of a file that does not contain text information is assumed to be a uniform value. Server device.

3. 3. The server device according to claim 1, The index information acquisition unit before acquiring the plurality of pieces of index information, presenting to a user via the terminal device whether or not the predicted total size is equal to or smaller than the upper limit value; The range and / or acquisition level of the plurality of index information to be acquired can be changed by the user via the terminal device. Server device.

4. 3. The server device according to claim 1, The index information acquisition unit generating a query for acquiring a plurality of pieces of index information at any acquisition level for each of the cloud storages and / or for each group of the plurality of files stored in each of the cloud storages, and acquiring the plurality of pieces of index information from the plurality of cloud storages based on the query; Server device.

5. 3. The server device according to claim 1, the first index information is property information of a file, The second index information is property information of a file and text information contained in the file. Server device.

6. Regarding an acquisition level when acquiring a plurality of pieces of index information for each of a plurality of files stored in a plurality of cloud storages, either a first acquisition level for acquiring a first piece of index information or a second acquisition level for acquiring a second piece of index information having a size larger than that of the first piece of index information is set; Calculating a predicted total size of the plurality of index information to be acquired based on the set acquisition level; If the predicted total size is equal to or smaller than an upper limit value, acquire the plurality of index information based on the set acquisition level, and store the plurality of index information in an index information storage; The plurality of pieces of index information relating to the plurality of files are presented to a user via a terminal device, without distinguishing in which of the plurality of cloud storages the plurality of files are stored. Information processing methods.

7. The processor of the server device, Regarding an acquisition level when acquiring a plurality of pieces of index information for each of a plurality of files stored in a plurality of cloud storages, either a first acquisition level for acquiring a first piece of index information or a second acquisition level for acquiring a second piece of index information having a size larger than that of the first piece of index information is set; Calculating a predicted total size of the plurality of index information to be acquired based on the set acquisition level; If the predicted total size is equal to or smaller than an upper limit value, the plurality of index information are acquired based on the set acquisition level, and are stored in an index information storage. An index information acquisition unit; an index information presenting section that presents the plurality of pieces of index information relating to the plurality of files to a user via a terminal device, without distinguishing in which of the plurality of cloud storages the plurality of files are stored; An information processing program that operates as

Images