File management device and program
The file management device and program enhance file positioning in predefined systems by adding configuration information to file names, enabling efficient identification and access of unassociated files through hierarchical archive files with integrated access information.
Patent Information
- Application Number
- JP2020167460
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-10-02
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2040-10-02
AI Technical Summary
In predefined file management systems, it is challenging to determine the positions of content files that are not yet associated with configuration information when managing multiple files for a specific purpose, leading to difficulties in locating and accessing these files efficiently.
A file management device and program that adds configuration information to the file names of registered content files, creating an archive file with configuration information files arranged in a hierarchy, allowing users to identify unassociated positions and access files more easily by including access information in the file names.
Enables users to grasp unassociated file positions directly from the archive file, simplifying the search for storage locations and access paths, and facilitating easier management and retrieval of content files.
Smart Images

Figure 0007593036000001 
Figure 0007593036000002 
Figure 0007593036000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a file management device and a program. [Background technology]
[0002] 2. Description of the Related Art There is a known technique for making a plurality of electronic files stored in a storage device of a computer into an archive file and reading the files all at once.
[0003] Patent document 1 describes a technology for downloading multiple content documents together as an archive file, in which if there are content documents with the same name stored in different locations on the server, those content documents are stored in different folders within the archive file, thereby preventing content documents with the same name from appearing in the same folder at the download destination.
[0004] Patent Document 2 describes how, with regard to copying a document file, the file name of the destination document file includes path information indicating the memory location from which the document file is copied (see paragraph 0080 and FIG. 13 of the same document). [Prior art documents] [Patent documents]
[0005] [Patent Document 1] Patent No. 5889009 [Patent Document 2] JP 2019-86864 A Summary of the Invention [Problem to be solved by the invention]
[0006] In some systems, folders are prepared in advance as storage destinations for multiple electronic files (hereinafter referred to as content files) for a certain purpose, and each content file is stored in the corresponding folder for management. In other systems, classifications such as the role of each content file for a certain purpose are predefined, and as each content file is registered, each content file is associated with the corresponding classification and managed in a database. In these file management systems, the storage destination or classification of a content file can be said to be the positioning of the content file. Hereinafter, this type of file management will be referred to as file positioning predefined type file management, or predefined type file management.
[0007] When managing multiple content files for a specific purpose using predefined file management, it is desirable to archive content files that have already been associated with positions, and when the content files are read out all at once, to be able to determine from the readout results the positions to which content files have not yet been associated.
[0008] The object of the present invention is to enable, when managing multiple content files for a specific purpose using predefined file management, to understand a positioning to which a content file has not yet been associated from the result of reading a content file that has already been associated with a positioning. [Means for solving the problem]
[0009] The invention according to claim 1 includes a processor, the processor being configured such that configuration information indicating the respective positions of a plurality of content files for a specific purpose is defined in advance, and the processor is configured to: and The configuration information; of Mapping hand management Configuration A read request is issued to read all registered content files that are already associated with the configuration information at once. From the clientBased on the read request, Each of the above Registered Content Files is already associated with The configuration information Each of the above The name of the registered content file is added to the file name. 、 A configuration information file having the configuration information added to the file name is created for each of the configuration information including the configuration information to which a content file has not yet been associated, and the plurality of registered content files and providing an archive file in which the configuration information file for each of the configuration information is arranged at the same hierarchical level to the client; The file management device is characterized in that:
[0010] The invention according to claim 2 is the file management device according to claim 1, wherein the configuration information file is The client operated by a configuration information file for storing a content file corresponding to the configuration information file in the file management device, the configuration information file including access information to the file management device for storing a content file corresponding to the configuration information file in the file management device.
[0011] The invention according to claim 3 is the file management device according to claim 1 or 2, wherein the configuration information file is The client operated by the configuration information file includes access information to the file management device for reading out a content file corresponding to the configuration information file from the file management device.
[0012] The invention according to claim 4 is the file management device according to any one of claims 1 to 3, wherein the configuration information file is The client operated by includes access information to the file management device for displaying a management screen of a plurality of content files for the specific purpose.
[0013] The invention according to claim 5 is the file management device according to claim 1, wherein the configuration information includes a plurality of components, and the processor is configured to add the configuration information to the original file name of the registered content file to generate a new file name upon receiving the read request, and to add the original file name and the new file name to the configuration information. Each of the above Specify the order of components From the client The file management device is characterized in that it accepts
[0014] The invention according to claim 6 is the file management device according to claim 1 or 5, wherein the configuration information includes a plurality of components, and the processor is configured to add the configuration information to the file name of the configuration information file upon receiving the read request, Each of the above Specify the order of components From the client The file management device is characterized in that it accepts
[0015] The invention according to claim 7 is the file management device according to claim 1, 5 or 6, wherein when the processor receives the read request and generates the configuration information file, the processor reads configuration information corresponding to the configuration information file. and indicates the attributes of the configuration information Attribute information and This file management device is characterized in that it adds the above to the file name of the configuration information file.
[0016] The invention according to claim 8 is the file management device according to claim 7, wherein the processor specifies a type of the attribute information to be added to a file name of the configuration information file. From the client The file management device is characterized in that it accepts
[0017] The invention of claim 9 is a file management device as described in claim 8, characterized in that when the processor accepts a specification of the type of attribute information to be added to the file name of the configuration information file, if the specified attribute information does not exist, it adds a predetermined character string to the file name of the configuration information file instead of the attribute information.
[0018] The invention according to claim 10 relates to a method for storing a plurality of content files for a specific purpose. 、 Each position The configuration information indicating the attachment of the content file is defined in advance, and the content file is and The configuration information; ofMapping hand management Configuration A read request is issued to read all registered content files that are already associated with the configuration information at once. From the client Based on the read request, Each of the above Registered Content Files is already associated with The configuration information Each of the above The name of the registered content file is added to the file name. 、 A configuration information file having the configuration information added to the file name is created for each of the configuration information including the configuration information to which a content file has not yet been associated, and the plurality of registered content files and providing the client with an archive file in which the configuration information file for each of the configuration information is arranged at the same level; computer To execute It is a program. Effect of the Invention
[0019] According to the invention as set forth in claims 1 and 10, the positioning (configuration information) to which no content file has yet been associated is grasped from the correspondence between the registered content files and the configuration information file in the archive file.
[0020] According to the invention as set forth in claim 2, the user does not need to search for a storage location of the content file within the file management device.
[0021] According to the invention as defined in claim 3, the user does not need to search for the source of the content file in the file management device.
[0022] According to the invention as defined in claim 4, the management screen can be displayed more easily than when the user accesses the file management device and then instructs the display of the management screen.
[0023] According to the invention of claim 5, a new file name of a registered content file can be obtained in which the original file name and each component are arranged in a desired order.
[0024] According to the invention as defined in claim 6, a file name of a configuration information file in which each component is arranged in a desired order can be obtained.
[0025] According to the invention as defined in claim 7, attribute information of the configuration information corresponding to the configuration information file can be obtained from the file name of the configuration information file.
[0026] According to the invention as defined in claim 8, desired attribute information is added to the file name of the configuration information file.
[0027] According to the invention of claim 9, it is possible to know from the file name of a configuration information file that the specified attribute information of the configuration information corresponding to that configuration information file does not exist. [Brief description of the drawings]
[0028] [Figure 1] FIG. 1 is a schematic configuration diagram of a file management system. [Diagram 2] FIG. 11 is a diagram for explaining predefined file management. [Diagram 3] FIG. 2 is a functional block diagram of a file management system. [Figure 4] 13A and 13B are diagrams illustrating an example of a management screen and a window for specifying a save destination of an archive file. [Diagram 5] 13 is a flowchart showing the flow of an archive file creation process. [Figure 6] FIG. 2 is a diagram illustrating an example of a configuration of an archive file. [Figure 7] 13A and 13B are diagrams showing examples of windows that are displayed based on the contents of a configuration information file and the access information contained therein. [Figure 8] 13A and 13B are diagrams showing an example of a screen for specifying the order of elements in a document file name and a configuration information file name. [Figure 9] 9 is a diagram showing an example of the structure of an archive file created based on the specification of the sorting order shown in FIG. 8. FIG. [Figure 10]FIG. 13 is a diagram showing another example of a screen for specifying the order of elements in a document file name and a configuration information file name. [Figure 11] 11 is a diagram showing an example of the structure of an archive file created based on the specification of the sorting order shown in FIG. 10. FIG. [Figure 12] 11 is a diagram showing another example of the configuration of an archive file created based on the sorting order designation shown in FIG. 10. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0029] Each embodiment of the present invention will be described in detail below with reference to the accompanying drawings. The configurations described below are illustrative examples and can be modified as appropriate to suit the specifications of the system or device. In addition, when multiple embodiments or modifications are included below, it is assumed from the beginning that the characteristic parts of these embodiments and modifications will be used in appropriate combination. The same elements in all drawings are given the same reference numerals, and duplicated descriptions will be omitted.
[0030] <Outline of file management system configuration> 1 is a schematic diagram of a file management system 10. The file management system 10 includes a server 12 and a plurality of clients 14 communicatively connected to the server 12 via a network 18 such as the Internet. The network 18 is not limited to the Internet, and various forms such as an intranet or a dedicated line can be adopted. The server 12 functions as a file management device 12. Hereinafter, the server 12 will be referred to as the file management device 12.
[0031] The file management device 12 is a computer that manages a plurality of content files, accepts the registration of content files in response to requests from clients 14, and provides registered content files to clients 14. Here, content files include electronic files of various formats, such as image files and document files. In the following explanation, content files are referred to as document files. Note that a "content file" refers to an individual electronic file that is the subject of management in the file management device, and is distinguished from an "archive file" and a "configuration information file" (details of which will be described later) that are created based on a request to read a content file.
[0032] The file management device 12 includes a processor 20 and a storage device 22. The processor 20 includes a CPU, and executes information processing according to a program installed in the file management device 12. The processor 20 can be defined as a computer in the narrow sense. The storage device 22 is a ROM, RAM, flash memory, hard disk, etc., and stores the program executed by the processor 20. The file management device 12 functions as a WEB server.
[0033] In addition, the program executed by the processor 20 of the file management device 12 can be provided via a network such as the Internet, and can also be provided by storing it on a computer-readable recording medium such as an optical disc or a USB memory.
[0034] The client 14 is a personal computer (PC), a tablet terminal, a smartphone, or the like operated by a user. A web browser is installed in the client 14. The user uses the web browser to display a screen (including a window) provided by the file management device 12 on the display of the client 14, and performs operations on that screen. Note that a dedicated application may be used in the client 14 instead of the web browser.
[0035] <Predefined file management> Here, the predefined file management performed by the file management device 12 will be described. The file management device 12 manages a plurality of document files 28 for an instance ("Project A" in FIG. 2), for example. An instance is a task (including a business) that includes a plurality of processes. FIG. 2 shows a document file management example 26 in which the instance "Project A" includes the processes "Task 1", "Task 2", and "Task 3", and a "plan" and a "report" are required in each process. In FIG. 2, "Plan1.pdf", "Report1.pdf", and another "Plan1.pdf" are registered document files 28.
[0036] First, before registering the document file 28 (e.g., at the stage of considering the schedule of the case), the user specifies to the file management device what documents are to be registered in the file management device 12 for the case, that is, what documents are to be managed by the file management device 12. In the example of Fig. 2, the user specifies that a "plan" and a "report" are to be registered for each of the processes of "Task 1", "Task 2", and "Task 3" in "Project A".
[0037] Then, the file management device 12 generates a folder for storing the document file of the specified document. At this time, as shown in FIG. 2, the file management device 12 generates folders hierarchically, such that the case is an upper folder, the process belonging to the case is an intermediate folder, and the documents belonging to each process are lower folders. In FIG. 2, the case name, process name, and document name shown in a square are folders to which the names are given. The storage destination (folder) of each document file generated in this way can be said to be the positioning of each document file. In this way, file management in which the positioning of the document file 28 is specified (including "the storage destination is prepared") before the document file 28 is registered is called pre-defined file management. The document file 28 (for example, "Plan 1.pdf" in FIG. 2) is stored in a folder corresponding to the document file 28 (for example, "Project A"-"Task 1"-"Plan" in FIG. 2) from the client, and the document file 28 is registered.
[0038] As shown in FIG. 2, the folder path name indicating the storage destination of the document file (for example, "Project A"-"Task 1"-"Plan" in FIG. 2) indicates the classification of the document file (for example, "Plan1.pdf" in FIG. 2), such as the role of the document file. In this way, preparing a storage destination (folder) for the document file in advance predefines the classification of the document file. Here, the classification of the document file can also be said to be the positioning of the document file. In the example of FIG. 2, the positioning of the document file is predefined both in terms of the storage destination of the document file and in terms of classification. Depending on how the folder name is assigned, the folder path name may not indicate the classification of the document file, but even in that case, the positioning of the document file is predefined in terms of the storage destination of the document file (the fact that a storage destination has been prepared).
[0039] In the above description, the document files are managed by folders, but the document files may be managed by a database. In the above description, the case name, process name, and document name enclosed in a square in FIG. 2 are each described as a folder, but from here on, they will be described as elements indicating the classification of the document file. When managing document files by a database, before the document file is registered, a designation of what document is to be registered in the file management device 12 is accepted from the user, and the classification (positioning) of the document is defined in the database. In the example of FIG. 2, the classification is defined hierarchically, with the case being the upper element, the process belonging to the case being the middle element, and the documents belonging to each process being the lower element. In FIG. 2, for example, ("Project A"-"Task 1"-"Plan"), ("Project A"-"Task 1"-"Report"), ... are each a classification. Then, in the database, the document file 28 (for example, "Plan1.pdf" in FIG. 2) is associated with the classification (for example, "Project A"-"Task 1"-"Plan" in FIG. 2) corresponding to the document file 28, thereby registering the document file 28. This is a predefined file management using a database.
[0040] The predefined file management may be realized by using a folder, a database, or a similar means, but as will be described below, in this embodiment, a database is used as an example.
[0041] Here, information indicating the positioning of each content file (here, document file) is called configuration information. In FIG. 2, for example, ("Project A"-"Task 1"-"Plan"), ("Project A"-"Task 1"-"Report"), ... are each configuration information. Configuration information can be defined hierarchically by components. That is, when configuration information is defined hierarchically, each of the layers becomes a component of configuration information. In FIG. 2, the matter (Project A) is a component of a higher layer, a process (e.g., Task 1) is a component of a middle layer, and a document required in the process (e.g., Plan) is a component of a lower layer. Note that the component of the highest layer corresponding to the root element (the matter (Project A) in FIG. 2) indicates the purpose of each document file to be managed, and is included in all configuration information and does not have the ability to identify each configuration information, so it may be omitted from the configuration information. In the following explanation, the configuration information is a form of configuration information in which the component of the highest layer indicating the purpose of each document file to be managed is omitted.
[0042] Although an example of managing content files related to a case has been described above, content files managed by the predefined file management method are not limited to those related to a case.
[0043] <Features of the file management device> The file management device 12 manages a plurality of document files for a specific purpose by predefined file management. The processor 20 of the file management device 12 receives a read request from the client 14 to read all registered document files that have already been associated with configuration information at once. Here, the registered document files that have already been associated with configuration information are document files that have already been stored in a folder as a storage destination (positioning) upon registration of the document files, or document files that have already been associated with a classification (positioning) in a database or the like.
[0044] Then, based on the received read request, the processor 20 of the file management device 12 provides the client 14 with an archive file 70 in which the registered document files 74 are arranged in the same hierarchy after adding the configuration information of each registered document file 74 to the file name of each registered document file 74, as shown in Fig. 6. Note that Fig. 6 shows the contents of the archive file 70 corresponding to the management example 26 of Fig. 2. At this time, the processor 20 of the file management device 12 creates a configuration information file 72 in which the configuration information is added to the file name for each piece of configuration information, including configuration information to which a document file has not yet been associated, and includes the file in the archive file 70. Note that the notation method of the configuration information included in the file name here does not need to be exactly the same as the notation method of the configuration information 40 (described later) stored in the document database 38, and the notation may be changed to the extent that the user of the client 14 who sees the file name including the configuration information can understand the position.
[0045] As a result, the client 14 can determine from the contents of the archive file 70 which document file 74 is not associated with, i.e., which position (configuration information) in which document file 74 is not registered. Specifically, if there is a pair of document file 74 and configuration information file 72 whose file names contain the same configuration information, then the document file is registered in that configuration information, and if there is no pair and only configuration information file 72, then the document file is not registered in the configuration information corresponding to that configuration information file 72.
[0046] <Functional configuration of the file management system> From here, the file management system 10 of this embodiment will be specifically described. Fig. 3 is a functional block diagram of the file management system 10 of this embodiment. The processor 20 of the file management device 12 operates according to a program (not shown) stored in the storage device 22, thereby functioning as a management screen providing unit 30, an archive creating unit 32, a registration processing unit 34, and a read processing unit 36. The management screen providing unit 30 provides the client 14 with a management screen (see Fig. 4), the archive creating unit 32 performs processing to create an archive file 70 and provide it to the client 14, the registration processing unit 34 performs processing to register document files in a document database, and the read processing unit 36 performs processing to individually read document files from the document database and provide them to the client 14.
[0047] A document database 38 (hereinafter referred to as document DB 38) is stored in the storage device 22 of the file management device 12. The document DB 38 includes configuration information 40, attribute information 42, association information 44, and a registered document file group 46.
[0048] The configuration information 40 of the document DB 38 has been described with reference to FIG. 2. Hereinafter, the configuration information 40 of the document DB 38 will be described as the management example 26 of FIG. 2. The attribute information 42 of the document DB 38 is the attribute information 42 of each configuration information 40 designated by the user when defining each configuration information 40, such as the planned start date of creation of the document (position), the person in charge of creation, and the creation deadline. The registered document file group 46 of the document DB 38 is a collection of document files 48 (referred to as registered document files) registered in the document DB 38 by the client 14. The correspondence information 44 of the document DB 38 is information created when the document file is registered from the client 14 in association with the configuration information, and is information indicating which configuration information corresponds to which document file that is part of the registered document file group 46.
[0049] The client 14 includes a processor 50, a storage device 52, an input device 53, and a display device 54. The processor 50 of the client 14 includes a CPU, and operates according to a program (not shown) stored in the storage device 52. The storage device 52 of the client 14 is a ROM, a RAM, a flash memory, a hard disk, or the like. The storage device 52 stores a program (not shown), an archive file 70 read from the file management device 12, a document file 55 individually read from the file management device 12, and a document file 56 to be registered in the file management device 12. The input device 53 is, for example, a keyboard, a mouse, or the like. The display device 54 is a display.
[0050] <Management screen> Next, a management screen provided by the file management device 12 will be described. An example of a management screen 58 is shown at the top of Fig. 4. The management screen 58 is a screen corresponding to the management example 26 of Fig. 2. The management screen 58 includes a managed document display section 60 showing documents managed in the document DB 38, and a download button 62.
[0051] When a user issues a display request for a management screen 58 from the client 14 to the file management device 12 using a WEB browser or the like, the management screen providing unit 30 of the file management device 12 receives the request and generates the management screen 58. The generated management screen 58 is provided from the file management device 12 to the client 14 and displayed on the display device 54 of the client 14. The management screen providing unit 30 generates a management document display unit 60 of the management screen 58 based on the configuration information 40 and the association information 44 of the document DB 38. The association information 44 of the document DB 38 indicates the configuration information to which the document file is associated, and by comparing the association information 44 of the document DB 38 with the configuration information (all configuration information) of the document DB, the configuration information to which the document file is not yet associated (not yet registered) can be determined. Therefore, the management screen providing unit 30 can generate the management document display unit 60 so that the difference between a document to which a document file is already associated (already registered) and a document to which a document file is not yet associated (not yet registered) can be determined, as in the management document display unit 60 of FIG. 4. In the managed document display section 60 in FIG. 4, registered documents are indicated with solid borders, and unregistered documents are indicated with dashed borders.
[0052] The download button 62 on the management screen 58 is a button for collectively reading out the document files registered in the document DB 38 as an archive file. When the user operates the input device 53 of the client 14 to press the download button 62, for example with the mouse cursor, a save destination designation window 64 (lower part of FIG. 4) is provided from the file management device 12 to the client 14 and displayed on the display device 54 of the client 14. When the user designates the save destination of the archive file on the storage device 52 of the client 14 and the file name of the archive file ("Project A.zip" in the example of FIG. 4) in the save destination designation window 64 and presses the save button 66, a request for collectively reading out the registered document files is issued to the file management device 12.
[0053] <Creating an archive file> When the processor 20 of the file management device 12 receives a bulk read request from the client 14, it functions as the archive creation unit 32 and creates an archive file. Fig. 5 is a flowchart showing the flow of the archive file creation process. Fig. 6 is an example of an archive file 70 created by the process of Fig. 5 when the configuration information 40 of the document DB 38 is the same as the management example 26 of Fig. 2.
[0054] The flowchart in Fig. 5 will be described with reference to the management example 26 in Fig. 2. Note that in the management example 26 in Fig. 2, there are six pieces of configuration information: (Work 1-plan), (Work 1-report), (Work 2-plan), (Work 2-report), (Work 3-plan), and (Work 3-report).
[0055] 5, the archive creation unit 32 sets the variable i to 1. Next, in S102, the archive creation unit 32 acquires the i-th configuration information (configuration information i) from the configuration information 40 of the document DB 38. Here, since i=1, (Work 1-Plan) in FIG. 2 is acquired as the first configuration information.
[0056] Next, in S104, the archive creation unit 32 creates a configuration information file (hereinafter referred to as the i-th configuration information file) corresponding to the ith configuration information (configuration information i) as one file in the archive file. At this time, the corresponding configuration information is given to the file name of the configuration information file. Here, since i=1, the first configuration information file is created. FIG. 6 shows "001_task1_plan.txt", which is the first configuration information file 72. This file name has the first configuration information (task1-plan) given to it. Note that "001" included in the file name is a consecutive number given consecutively to files in the archive file. Note that the consecutive number may be omitted as appropriate.
[0057] The contents (contents) of configuration information file 72 are not limited. For example, the contents of the configuration information file may be empty. In this embodiment, the contents of the configuration information file include access information to file management device 12 (see contents 73 of configuration information file in FIG. 7). The format of configuration information file 72 is also not limited, but in this embodiment, it is in text format.
[0058] Next, in S106, the archive creation unit 32 checks whether a document file corresponding to the ith configuration information (configuration information i) is registered in the document DB 38. Here, since i=1, the first configuration information is checked. In the management example 26 of FIG. 2, the document file 28 (plan1.pdf) corresponding to the first configuration information (task 1-plan) has already been registered in the document DB 38, so S106 becomes Yes and the process proceeds to S108.
[0059] Next, in S108, the archive creation unit 32 reads out the registered document file 48 corresponding to the i-th configuration information (configuration information i) from the registered document file group 46 of the document DB 38, and adds it to the archive file 70. At this time, the corresponding configuration information is added to the file name of the document file. Here, since i=1, this is done for the first configuration information. FIG. 6 shows a document file 74 "002_task1_plan__plan1.pdf" corresponding to the first configuration information. This file name is obtained by adding the first configuration information (task1-plan) to the original file name "plan1.pdf" of the document file. In this file name, two underscores are inserted between the original file name "plan1.pdf" and the added sequential number and the configuration information "002_task1_plan" so that the original file name and the configuration information can be distinguished in the new file name.
[0060] In addition, in S106, if the document file corresponding to the i-th configuration information (configuration information i) is not registered in the document DB 38 (S106: No), S108 is skipped.
[0061] Next, in S110, the archive creation unit 32 adds 1 to the variable i. Here, 1 is added to i=1, so that i=2. Next, in S112, the archive creation unit 32 checks whether the variable i is greater than the total number of configuration information 40 in the document DB 38. In the management example 26 of FIG. 2, the total number of configuration information is 6, and here, i=2, so the answer in S112 is No. If the answer in S112 is No, the process returns to S102 and processing is performed on the next configuration information.
[0062] Since i=2 here, the archive creation unit 32 performs the same processes as S102 to S108 described above for the second configuration information. Specifically, in S102, the archive creation unit 32 acquires (Task 1-Report) in Fig. 2 as the second configuration information, and performs the processes of S104 to S108 to add the configuration information file 72 "003_Task 1_Report.txt" and the document file 74 "004_Task 1_Report_Report 1.pdf" for the second configuration information to the archive file 70.
[0063] In this way, the variable i is incremented, and when processing is completed for all configuration information, S112 becomes Yes, and the flow in Fig. 5 ends. In management example 26 in Fig. 2, document files are associated with the first to third configuration information, so those document files exist in a form in which the file names have been changed in archive file 70 in Fig. 6. On the other hand, in management example 26 in Fig. 2, no document files are associated with the fourth to sixth configuration information, so those document files do not exist in archive file 70 in Fig. 6.
[0064] The file management device 12 sends the created archive file 70 to the client 14 that issued the bulk read request. The client 14 that issued the bulk read request receives the archive file 70 from the file management device 12 and stores it in the save destination in the storage device 52 specified in the save destination specification window 64 in FIG.
[0065] <Major effects> According to the embodiment described above, the user can grasp from the contents of the archive file 70 at the client 14 the position (configuration information) of the document file not associated, that is, the document file not registered in the document DB 38. Specifically, if there is a pair of the document file 74 and the configuration information file 72 whose file names contain the same configuration information, the document file is registered in the configuration information, and if there is no pair and only the configuration information file 72, the document file is not registered in the configuration information corresponding to the configuration information file. Although such information can be confirmed by the user from the management screen 58, there is an advantage in that the user can grasp whether each document is registered or not from the contents of the archive file 70 without accessing the file management device 12 again to display the management screen 58 after reading out the archive file 70 and closing the management screen 58.
[0066] According to the embodiment described above, since the document files are arranged in the same hierarchy, the user who has acquired the archive file 70 can easily reach the target document file 74 compared to when the document files are in different folders. Also, when multiple document files with the same file name are registered, such as "Plan 1.pdf" in FIG. 2, and the document files are read all at once without changing the file names, the document files generally cannot be made to exist in the same hierarchy. However, according to the embodiment described above, even if the document files have the same file names, their positioning (configuration information) is different, and by adding the different configuration information to the file names, the document files can be made to exist in the same hierarchy.
[0067] <Contents of the configuration file> Next, the contents of the configuration information file 72 stored in the archive file 70 will be described. Fig. 7 is a diagram showing the contents 73 of the configuration information file and examples of windows 76, 80 that are displayed based on the access information contained therein. The contents 73 of the configuration information file in Fig. 7 are the contents of the configuration information file "001_task1_plan.txt" shown in Fig. 6.
[0068] As shown in FIG. 7, the contents 73 of the configuration information file include access information to the file management device 12. Here, the access information to the file management device is an address for accessing a screen (page) or folder provided by the file management device. In the example of FIG. 7, the contents 73 of the configuration information file include a management screen URL, a download URL, and a registration URL. The management screen URL is access information for displaying the above-mentioned management screen 58 on the display device of the client. The user inputs the management screen URL into a WEB browser or the like of the client to display the management screen 58 on the display device 54 of the client 14. In this way, since the contents 73 of the configuration information file include access information to the management screen 58, the management screen 58 can be easily displayed on the display device 54 of the client 14 compared to the case where the user accesses the file management device 12 and further issues an instruction to display the management screen 58.
[0069] The download URL is access information for individually reading out the document file corresponding to the configuration information file in which it is written from the file management device 12 to the client 14. The download URL is different for each configuration information file 72, and in the example of FIG. 7, it is an access URL for reading out the document file ("Plan 1.pdf" at the top of FIG. 2) in the configuration information (Work 1-Plan) corresponding to the configuration information file "001_Work 1_Plan.txt". When the user inputs the download URL into the WEB browser of the client 14, a save destination designation window 76 (see FIG. 7) is displayed on the display device 54 of the client 14. In the save destination designation window 76, the user designates the save destination of the document file and the file name of the document file ("Plan 1.pdf" in the example of FIG. 7), and presses the save button 78. As a result, the document file associated with the configuration information of (Work 1-Plan) registered in the document DB 38 is saved in the save destination designated in the save destination designation window 76. At this time, the processor 20 of the file management device 12 functions as the read processing unit 36 to perform processing. This access information is effective in that, for example, when a document file in the document DB 38 is updated, the document file can be read out individually. In addition, since the contents 73 of the configuration information file include access information to the read source of the document file, the user does not need to search for the read source of the document file in the file management device 12.
[0070] The registration URL is access information for specifying a document file to be associated with the configuration information corresponding to the configuration information file in which the registration URL is written, and registering the document file in the document DB 38. The registration URL is different for each configuration information file 72, and in the example of FIG. 7, it is an access URL for registering a document file in the configuration information (Work 1-Plan). When the user inputs the registration URL into the WEB browser of the client, a file specification window 80 (see FIG. 7) is displayed on the display device 54 of the client 14. The user specifies the document file to be registered in the file specification window 80 and presses the registration button 82. Thereby, the document file specified in the file specification window 80 is registered in the document DB 38 as a document file corresponding to the configuration information of (Work 1-Plan). At this time, the processor 20 of the file management device 12 functions as the registration processing unit 34 and performs processing. In this way, the configuration information file includes access information to the registration destination of the document file, so that the user does not need to search for the registration destination of the document file in the file management device 12.
[0071] <Specifying the order of file name elements> Next, a description will be given of a mode for specifying the order of each element in the file names of the document files 74 and the configuration information file 72 in the archive file 70. When reading all registered document files at once using the archive file 70, the user presses the detailed settings button 68 provided in the save destination designation window 64 in Fig. 4. This causes a setting screen for designating the order of each element in the file names to be displayed on the display device 54 of the client 14. Fig. 8 shows an example of this setting screen 84.
[0072] 8, the setting screen 84 includes a number of pull-down menus 86 for specifying each element of the file names of the document files and the configuration information files in the archive file. The user specifies the first through fourth elements of the document file name in the pull-down menu 86, and specifies the first through third elements of the structure information file name in the pull-down menu. Note that, although the number of elements in the document file name is four and the number of elements in the structure information file name is three here, the number of elements may be changed as appropriate.
[0073] As shown in the opened pull-down menu 86 at the top of Fig. 8, the types of elements that can be specified by the document file name are the original file name of the document file, each component of the configuration information (process or document type), sequence number, and attribute information (scheduled creation start date, person in charge of creation, or creation due date). Note that the attribute information is information that is specified by the user in association with each piece of configuration information before the document file is registered, and is stored in the document DB 38 (attribute information 42 of the document DB 38 shown in Fig. 3). Also, as shown in the opened pull-down menu 86 at the bottom of Fig. 8, the types of elements that can be specified by the configuration information file name are each component of the configuration information (process or document type), sequence number, and attribute information (scheduled creation start date, person in charge of creation, or creation due date).
[0074] On the setting screen 84, the user specifies each element of the document file name and the configuration information file name, and then presses the Set button 88 to complete the setting of the sort order. Thereafter, the user presses the Save button 66 in the save destination specification window 64 of FIG. 4, and the archive file 70 is stored in the storage device 52 of the client 14.
[0075] FIG. 9 is a diagram showing the configuration of an archive file 70A generated by specifying elements of each pull-down menu 86 of the setting screen 84 shown in FIG. 8. In FIG. 8, the first element of the document file name is the original file name, so the file name of each document file 74 in FIG. 9 begins with the original file name. In the embodiment of the present invention, since configuration information is added to the file name of the document file, the file name may become very long. Depending on the system, there is a limit to the number of characters in the file name, and the latter part of the file name may be omitted. However, by placing the original file name at the beginning of the file name as shown in FIG. 9, the original file name is prevented from being omitted. In this way, a new file name of the document file is obtained in which the original file name and each component are arranged in a desired order. Also, a file name of the configuration information file is obtained in which each component is arranged in a desired order.
[0076] FIG. 10 shows a setting screen 84A similar to FIG. 8, but the elements of the pull-down menus 86 have been changed from those of the setting screen 84 of FIG. 8. In FIG. 10, the creator, which is one of the attribute information, is specified as the first element of each of the document file name and the configuration information file name. FIG. 11 shows the configuration of an archive file 70B generated by specifying the elements of the pull-down menus 86 of the setting screen 84A shown in FIG. 10. As shown in FIG. 11, the name of the creator appears in the file names of the document file 74 and the configuration information file 72. In this way, by including the attribute information in the file name, the attribute information of the configuration information corresponding to that file can be obtained from the file name.
[0077] In addition, some or all of the attribute information 42 of the document DB 38 may not exist because it is not specified by the user. For example, the above-mentioned creator does not exist in the document DB 38 as attribute information 42, but may be specified as an element of the document file name or the configuration information file name as in the setting screen 84A of FIG. 10. In that case, as an archive file to be created, it is preferable to add a predetermined character string to the file name of the configuration information file 72 or the document file 74 instead of the non-existent attribute information (creator), as in the archive file 70C shown in FIG. 12. In FIG. 12, "****" is used as the predetermined character string. In this way, it is possible to know from the file name of the document file 74 or the configuration information file 72 that the specified attribute information of the configuration information corresponding to the file does not exist.
[0078] In each of the above embodiments, the term "processor" refers to a processor in a broad sense, including general-purpose processors (e.g., CPU: Central Processing Unit, etc.) and dedicated processors (e.g., GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, programmable logic device, etc.).
[0079] In addition, the operations of the processor in each of the above embodiments may be performed not only by one processor, but also by multiple processors located at physically separate locations working together. Furthermore, the order of the operations of the processor is not limited to the order described in each of the above embodiments, and may be changed as appropriate. [Explanation of symbols]
[0080] 10 file management system, 12 file management device (server), 14 client, 18 network, 20 processor, 22 storage device, 26 management example, 28 document file, 30 management screen providing unit, 32 archive creation unit, 34 registration processing unit, 36 read processing unit, 38 document database (document DB), 40 configuration information, 42 attribute information, 44 correspondence information, 46 registered document file group, 48 registered document file, 50 processor, 52 storage device, 53 input device, 54 display device, 55 read document file, 56 document file to be registered, 58 management screen, 60 managed document display unit, 62 download button, 64 save destination designation window, 66 save button, 68 detailed setting button, 70, 70A, 70B, 70C archive file, 72 configuration information file, 73 contents of configuration information file, 74 document file (registered content file), 76 Save destination selection window, 78 Save button, 80 File selection window, 82 Register button, 84, 84A Settings screen, 86 Pull-down menu, 88 Settings button.
Claims
1. A processor is included. The processor, In a configuration in which configuration information indicating the respective positions of a plurality of content files for a specific purpose is predefined, and the content files are managed in association with the configuration information upon registration of the content files, a read request is received from a client for collectively reading the registered content files that have already been associated with the configuration information; based on the read request, adding the configuration information already associated with each of the registered content files to a file name of each of the registered content files; creating a configuration information file with the configuration information added to the file name for each of the configuration information, including the configuration information to which a content file has not yet been associated; providing the client with an archive file in which the plurality of registered content files and the configuration information file for each of the configuration information are arranged in the same hierarchy; A file management device comprising:
2. 2. The file management device according to claim 1, the configuration information file includes access information to the file management device for the client operated by a user to store a content file corresponding to the configuration information file in the file management device; 2. A file management device comprising:
3. 3. The file management device according to claim 1, the configuration information file includes access information to the file management device for the client operated by a user to read a content file corresponding to the configuration information file from the file management device; A file management device comprising:
4. 4. A file management device according to claim 1, the configuration information file includes access information to the file management device for the client operated by a user to display a management screen of a plurality of content files for the specific purpose; 2. A file management device comprising:
5. 2. The file management device according to claim 1, The configuration information includes a plurality of components, The processor, receiving, from the client, a specification of the original file name and the order of the components in the new file name when receiving the read request and adding the configuration information to the original file name of the registered content file to generate a new file name; 2. A file management device comprising:
6. 6. A file management device according to claim 1, The configuration information includes a plurality of components, The processor, receiving, from the client, a specification of an order of arrangement of the components in a file name when the configuration information is to be assigned to a file name of the configuration information file in response to the read request; 2. A file management device comprising:
7. 7. A file management device according to claim 1, 5 or 6, The processor, when the read request is accepted and the configuration information file is generated, the configuration information corresponding to the configuration information file and attribute information indicating attributes of the configuration information are added to a file name of the configuration information file.
2. A file management device comprising:
8. 8. The file management device according to claim 7, The processor, receiving, from the client, a designation of a type of the attribute information to be added to a file name of the configuration information file; 2. A file management device comprising:
9. 9. A file management device according to claim 8, The processor, when a specification of the type of attribute information to be added to the file name of the configuration information file is accepted, if the specified attribute information does not exist, a predetermined character string is added to the file name of the configuration information file in place of the specified attribute information.
2. A file management device comprising:
10. In a configuration in which configuration information indicating the respective positions of a plurality of content files for a specific purpose is predefined, and the content files are managed in association with the configuration information upon registration of the content files, a read request is received from a client for collectively reading the registered content files that have already been associated with the configuration information; based on the read request, adding the configuration information already associated with each of the registered content files to a file name of each of the registered content files; creating a configuration information file with the configuration information added to the file name for each of the configuration information, including the configuration information to which a content file has not yet been associated; providing the client with an archive file in which the plurality of registered content files and the configuration information file for each of the configuration information are arranged in the same hierarchy; A program that makes a computer do something.
Citation Information
Patent Citations
Mobile sub station
JP1983089009A
Album preparing program
JP2003223347A
Document transfer support system, monitoring device, document transfer support device, method, and program
JP2009129017A
Information processing apparatus, electronic delivery product production business support method and program
JP2009175872A
Image data management system, image data management method and program
JP2017022523A
