JP2011186768A - File management system, information processor, and information processing method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To facilitate unified management of data stored in a folder. <P>SOLUTION: The data management system managing files includes: a definition control means for defining each layer in a folder hierarchy for managing files and defining metadata added to a folder; a first storage means storing one or more pieces of folder definition data including the layer definition showing the definition of each defined layer and the metadata definition showing the definition of the defined metadata; a second storage means storing one or more pieces of folder data including data corresponding to the folder definition above the folder layer and metadata meeting the metadata definition added to the folder for each folder in the folder hierarchy; and a third storage means storing a file associated with the layer of the folder in the folder hierarchy and metadata added to the folder. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a file management system, an information processing apparatus, and an information processing method for managing files.

  Conventionally, various methods for assigning metadata to a file and managing the file based on the metadata have been proposed. For example, Patent Document 1 discloses that files are efficiently classified and a folder generated when performing automatic classification of files based on metadata is disclosed in order for a user to quickly reach a target file.

  Japanese Patent Application Laid-Open No. 2004-228561 discloses a technique of filtering and displaying as a virtual folder in accordance with file content metadata in a system using a virtual folder.

  However, in business, when managing a file and information related to the file (for example, metadata) together, it takes time to allocate the file and the information related to the file. Further, since file management is ultimately left to the user's operation, there is a problem that data is distributed to a plurality of locations (for example, folders) and related information cannot be managed. Also, for example, for a backbone system that can handle a large amount of data in a short time and can be accessed by a large number of users, it is difficult to manage folders and files.

  Even in the above-described prior art, since the end user has to learn the association method and apply it to the file management system, the regulation may not be effective if the number of end users increases. In other words, in a management system using metadata, file storage locations may be dispersed, making file management difficult. Moreover, there is a possibility that metadata having the same meaning may be dispersed, and data consistency may not be maintained.

  Further, when searching for files stored in a folder, since it is difficult to search across folders, there are cases where operations separately managed using Excel or the like are generally performed.

  Accordingly, the present invention has been made in view of the above problems, and an object thereof is to provide a file management system, an information processing apparatus, and an information processing method that facilitate centralized management of data stored in a folder. To do.

  A file management system according to an aspect of the present invention is a file management system that manages files, and defines a folder hierarchy for managing files for each folder hierarchy and is assigned to a folder in the hierarchy. A definition control means for defining metadata related to the definition of the hierarchy, a hierarchy definition indicating a definition for each defined hierarchy, and folder definition data including a metadata definition indicating a definition of the defined metadata. One or more first storage means for storing, for each folder in the folder hierarchy, data corresponding to a folder definition above the hierarchy of the folder, and metadata corresponding to a metadata definition assigned to the folder A second storage means for storing one or a plurality of folder data; a hierarchy of folders in the folder hierarchy; When creating a new folder and the third storage means for storing the file associated with the specified metadata, the folder definition data and the hierarchy are specified, and the hierarchy definition above the hierarchy in the specified folder definition data and the hierarchy definition are supported. And a folder control means for generating a registration form having a data input area corresponding to the hierarchy definition of the hierarchy in the designated folder definition data.

  An information processing apparatus according to another aspect of the present invention defines a folder hierarchy for managing files for each folder hierarchy, and is assigned to a folder in the hierarchy, and relates to the definition of the hierarchy. Definition control means for defining metadata, and when receiving a display request for the folder, the folder based on at least one of the folder designation, the hierarchy designation, and the metadata designation given to the folder Folder control means for searching a folder in a hierarchy and at the time of receiving the file display request, at least one of the designation of the folder, designation of the hierarchy, designation of metadata assigned to the folder, designation of the file name A file control means for searching for a file contained in a folder in the folder hierarchy based on one specification, and a new folder. Folder definition data and hierarchy are specified, the hierarchy definition higher than the hierarchy in the specified folder definition data, the data display area corresponding to the hierarchy definition, and the hierarchy definition of the hierarchy in the specified folder definition data And a folder control means for generating a registration form having a data input area corresponding to.

  An information processing method according to another aspect of the present invention is an information processing method in an information processing apparatus, wherein a folder hierarchy for managing files is defined for each folder hierarchy, and folders in the hierarchy Definition control step for defining metadata related to the definition of the hierarchy, and when creating a new folder, the folder definition data and the hierarchy are specified, and the hierarchy definition higher than the hierarchy in the specified folder definition data And a generation step of generating a registration form having a data display area corresponding to the hierarchy definition and a data input area corresponding to the hierarchy definition of the hierarchy in the specified folder definition data, and the data input to the registration form When creating a folder based on the creation step and a request to display the created folder A folder control step of searching for a folder in the folder hierarchy based on at least one of the designation of the folder, the designation of the hierarchy, and the designation of metadata assigned to the folder; and the created file in the folder Is included in a folder in the folder hierarchy based on at least one of the designation of the folder, the designation of the hierarchy, the designation of metadata assigned to the folder, and the designation of the file name. And a file control step for searching for the file.

  According to the present invention, it is possible to provide a file management system, an information processing apparatus, and an information processing method that facilitate centralized management of data stored in a folder.

The figure which shows an example of the file management system in an Example. The block diagram which shows an example of the hardware constitutions of the server 107 in an Example. The block diagram which shows an example of the function of the file management system in an Example. The figure which shows an example of the data structure of each data. The figure which shows an example of the data model used in an Example. The figure which shows an example of metadata. The figure which shows an example of a folder structure view. The figure which shows an example of a folder list view. The figure which shows an example of the folder registration form of a 2nd hierarchy. The figure which shows an example of the folder registration form of the 3rd hierarchy. The figure which shows an example of the result of a folder search. The sequence diagram which shows an example of the registration process of a folder. The sequence diagram which shows an example of the display process of a folder. The sequence diagram which shows an example of the display process of a file. The figure which shows an example of search UI using metadata. The figure which shows the example of API used with the server 107. FIG.

  Embodiments of a file management system, an information processing apparatus (server), and an information processing method according to the present invention will be described below in detail with reference to the accompanying drawings.

  In the following embodiment, as an example of an image input device for inputting image data, an information processing device or a multifunction device having a printer function, a scanner function, a copy function, and a facsimile function mounted in one housing is taken as an example. explain. However, the present invention is not limited to these, and can be applied to any of a scanner device, a facsimile device, a copy device, an information processing device and the like as long as image data can be input.

[Example]
<System and hardware>
FIG. 1 is a diagram illustrating an example of a file management system in the embodiment. As shown in FIG. 1, a file management system 100 includes a client (client device) 101, a load balancer (hereinafter also referred to as LB) 103, servers 105, 107, and 109, a database (hereinafter also referred to as DB) 111, and a file management server. 113.

  The client 101 is, for example, an information processing apparatus or an MFP (Multifunction Peripheral), and issues an instruction to manage files such as an image file, a document file, a moving image file, and a music file on the server side.

  The LB 103 is also a firewall for detecting unauthorized access from a client, and further performs load distribution and performs request distribution processing. The LB 103 has a function of centrally managing requests from an external network and transferring the requests to a plurality of servers having equivalent functions.

  The server 105 manages user information and provides a service for managing user information. The user information includes organization information, a login name and a password used for user authentication.

  The server 107 manages folders and files. The server 107 performs definition for each level of the folder hierarchy, and defines metadata assigned to the folder. The server 107 searches for folders and files. The server 107 also performs view customization and the like.

  The server 109 has a storage unit and provides a simple file storage service. The server 109 manages the file ID, the URL of the file storage location, the file expiration date, and the like.

  The database 111 manages files in a folder hierarchy in which folders are hierarchized. The DB 111 may be a file management server 113 that stores files.

  The client 101 uses a browser to connect to the file management server 113 using, for example, a JavaScript (registered trademark) program such as “jQuery.js” or “Ajax framework” or “jsonAPI” to search and register a file. Further, the client 101 uses the explorer to connect to the file management server 113 by WebDAV (Web-based Distributed Authoring and Versioning) for accessing a network folder, for example. Each server shown in FIG. 1 may be configured by arbitrarily combining a plurality of servers, or may be configured as one server.

  The content management system 100 is more suitable for a backbone system that handles a large amount of data in a short time. For example, this is a case where the server 107 is connected to a DB or the like of a basic system that handles a large amount of documents. In the backbone system, it is necessary to process a large amount of data in a short time. Therefore, it is necessary to reduce the processing load in the system while realizing appropriate folder management. By appropriately registering and searching for a folder, which will be described later, for this basic system, access to unnecessary data inside the system can be reduced, and the processing load associated with registration and search can be reduced.

  Next, the hardware configuration of the server in the embodiment will be described. FIG. 2 is a block diagram illustrating an example of a hardware configuration of the server 107 in the embodiment. As illustrated in FIG. 2, the server 107 includes a control unit 201, a main storage unit 203, an auxiliary storage unit 205, an external storage device I / F unit 207, and a network I / F unit 211.

  The control unit 201 is a CPU that controls each device, calculates data, and processes in a computer. The control unit 201 is an arithmetic device that executes a program stored in the main storage unit 203, receives data from the input device or the storage device, calculates and processes the data, and outputs the data to the output device or the storage device.

  The main storage unit 203 is a ROM (Read Only Memory), a RAM (Random Access Memory), or the like, and a storage device that stores or temporarily stores programs and data such as an OS and application software that are basic software executed by the control unit 201 It is.

  The auxiliary storage unit 205 is an HDD (Hard Disk Drive) or the like, and is a storage device that stores data related to application software and the like. The auxiliary storage unit 205 stores a predetermined program via the Internet. The predetermined program can be installed and executed.

  The external storage device I / F unit 207 is an interface between the server 107 and a storage medium 209 (for example, a flash memory or an SD card) connected via a data transmission path such as a USB (Universal Serial Bus).

  Further, a predetermined program is stored in the storage medium 209, and the program stored in the storage medium 209 is installed in the server 107 via the external storage device I / F unit 207, and the installed predetermined program is stored in the server 107. Can be executed.

  The network I / F unit 211 has a communication function connected via a network such as a LAN (Local Area Network) or a WAN (Wide Area Network) constructed by a data transmission path such as a wired and / or wireless line. This is an interface between the device and the server 107.

  The server 107 may include an input unit and a display unit. The input unit includes a keyboard having cursor keys, numeric input, various function keys, and the like, and a mouse and a slice pad for selecting keys on the display screen of the display unit. The input unit is a user interface for a user to give an operation instruction to the control unit 201 or input data.

  The display unit is configured with a CRT, LCD, or the like, and displays according to display data input from the control unit 201.

<Function>
FIG. 3 is a block diagram illustrating an example of functions of the file management system in the embodiment. In the example illustrated in FIG. 3, the file management system 100 includes a client 101, a server 107, and a DB 111. The client 101 defines a folder hierarchy for managing files, searches for, references, registers, or modifies folders, searches for, references, registers, or modifies files.

  The server 107 includes a folder definition control unit 301, a folder control unit 303, and a file control unit 305. The folder definition control unit 301, the folder control unit 303, and the file control unit 305 can be realized by the control unit 201, for example.

  The folder definition control unit 301 has a function of defining meaning for each layer of the folder hierarchy. In the embodiment, the fact that the hierarchical structure of the folder hierarchy is generally meaningful is used. The folder definition control unit 301 defines, for example, “country” for the first hierarchy, “year” for the second hierarchy, “person in charge” for the second hierarchy, and the like. The folder definition control unit 301 also defines metadata given to the folder. As a result, the DB 111 can manage folder hierarchies and folder metadata that are meaningful in the hierarchical structure of folders. The definition is performed by the user using a display unit or an input unit.

  The folder control unit 303 performs folder search, folder reference, registration, or correction based on the folder definition data 307 and the folder data 309. Regarding the folder search, the folder control unit 303 can search for a folder in the folder hierarchy by designating a folder hierarchy, folder metadata, or a combination of the hierarchy and metadata. When registering a folder, for example, when a parent folder is designated, the folder control unit 303 defines the hierarchy of the parent folder (eg, “country”) and data corresponding to the definition of the hierarchy of the parent folder (eg, “JAPAN”). A registration form is generated that displays the definition of the hierarchy one level below the parent folder (for example, “year”) and the definition of the metadata of the folder one level below the parent folder. The user can easily manage metadata and files by inputting data according to the registration form.

  The file control unit 305 performs file definition, file reference, file registration, or correction based on the file data 311, folder data 309, and folder definition data 307. For file search, the file control unit 305 designates a folder name, a hierarchy of the folder hierarchy, metadata assigned to the folder, file metadata, a file name, or any combination thereof, and a folder in the folder hierarchy You can search for files included in.

  The DB 111 stores folder definition data 307, folder data 309, and file data 311. FIG. 4 is a diagram illustrating an example of the data structure of each data. In the example shown in FIG. 4, the folder definition data 307 is given to the folder definition data identifier, organization ID, folder hierarchy title, folder hierarchy definition, folder hierarchy folder, and related to the hierarchy definition. Includes metadata definitions.

  In the example shown in FIG. 4, an organization ID is assigned to manage data of a plurality of organizations. However, when there is one organization, the organization ID may not be provided. The metadata includes metadata “stag (string-tag)” indicating a character string and metadata “dtag (data-tag)” indicating a date. In “layer_0_tags” 401, metadata of the 0th layer is defined. In “stag — 0” 403, for example, character sequence metadata “Country” is defined. Other metadata may include “ntag (number tag)” and “btag (boolean tag)”.

  The folder data 309 includes, for each folder, a folder ID, organization ID, folder definition data identifier, parent folder identifier, level indicating which hierarchy, data corresponding to the definition of each hierarchy, and metadata assigned to the folder. Includes metadata corresponding to the definition. In addition, each hierarchy of folder data may hold not only the own hierarchy but also data corresponding to the folder definition of the hierarchy higher than the own hierarchy. For example, “JP” of “layer_0”, “2009.01” of “layer_1”, and “0000001234900” of “layer_2” are held as folder data of “2”. As a result, when acquiring data corresponding to the definition of the upper-level folder, it is possible to acquire it easily and at high speed without following the parent folder. Further, data corresponding to the definition of the hierarchy may be the name of the folder of the hierarchy.

  The file data 311 includes a file ID, an organization ID, a folder ID indicating in which folder the file is stored, a file title, a URL indicating the location where the file is stored, a file size, file metadata, and the like. Note that file metadata can be identified from folder metadata. For example, “e_” indicating the file metadata is added to the file metadata, such as “e_stag”. This makes it possible to manage and search the folder metadata and the file metadata separately. Note that metadata assigned to a folder is associated with a file stored in the folder.

  FIG. 5 is a diagram illustrating an example of a data model used in the embodiment. FIG. 5 shows the class relationship of each model. The “Organization” class 501 is a class having an organization ID “rs_organization_id (or simply organization_id)”.

  A “Cabinets” class 509, a “Folder” class 511, an “Entry” (file) class 513, a “Tag” class 515, and a “Doctype” class 517 are classes of files and folders actually used by the user.

  The “ContentFilter” class 519 and the “ViewFiler” class 521 are classes for setting access rights for files and views. The “SmartView” class 523 and the “ViewSet” class 525 are classes for setting a UI for displaying a folder or content in a format close to business contents. The “User” class 527 is a class for setting user information. The double enclosed class is a class that can be set by the user administrator.

(Metadata)
Next, an example of metadata will be described. FIG. 6 is a diagram illustrating an example of metadata. FIG. 6A shows the definition of the hierarchy. In the example shown in FIG. 6A, the 0th hierarchy is defined as “year”, the 1st hierarchy is “in charge”, the 2nd hierarchy is “customer”, and the 3rd hierarchy “case number” is defined as a hierarchy. FIG. 6B is a diagram illustrating the definition of metadata assigned to folders in each hierarchy. In the example shown in FIG. 6B, “project”, “finished date”, “order received”, “estimate”, and “billing” are defined as metadata in the folder of the third hierarchy. It should be noted that metadata such as “year of employment” may be defined in the first layer folder, and “business type” may be defined in the second layer folder.

(View)
Next, an example of a view (display screen) based on the data structure shown in FIG. 6 will be described. FIG. 7 is a diagram illustrating an example of the folder structure view. As shown in FIG. 7, the folder structure view displays data corresponding to the definition of the hierarchy for each hierarchy. FIG. 7 shows an example in which data corresponding to the definition of the hierarchy is a folder name.

  For example, “2002” and “2003” corresponding to “Year” are displayed on the right side of the folder in the 0th hierarchy, and “AAA” and “BBB” corresponding to “in charge” are displayed in the 1st hierarchy. In the second hierarchy, “aaa”, “bbb” and the like corresponding to “customer” are displayed, and in the third hierarchy, “595”, “697” and the like corresponding to “case number” are displayed. “AAA” and “BBB” indicate a person name, and “aaa” and “bbb” indicate a company name. The personal name is data corresponding to “in charge”, and the company name is data corresponding to “customer”.

  The folder control unit 303 generates a view according to the hierarchical structure shown in FIG. 6A, so that the folder structure view shown in FIG. 7 can be displayed on the display screen of the client.

  FIG. 8 is a diagram illustrating an example of a folder list view. The folder list view is provided to the client 101 by the server 107 in “jsonAPI”, “xml”, “csv” format, etc., which will be described later. As shown in FIG. 8, the folder list view displays data corresponding to the definition of each hierarchy, and also displays metadata assigned to the folder. Folder metadata is not necessarily displayed.

  In the example shown in FIG. 8, a folder in the third hierarchy is displayed, and metadata is assigned to this folder. For example, the folder of the case number “2174” is “2002” in the 0th hierarchy, “AAA” in the 1st hierarchy, and “(aaa)” in the 2nd hierarchy for the upper layer folder. In addition, the folder of the project number “2174” has metadata such as “Chapter about human beings” for the project, “Order received” for the order received, and “Not yet received” for the estimate.

(Register)
Next, an example of folder registration based on the data structure shown in FIG. 6 will be described. FIG. 9 is a diagram showing an example of a second-level folder registration form. The example shown in FIG. 9 shows a registration form in which a parent folder is designated as “AAA” (first layer) and a folder is created. As shown in FIG. 9, when the parent folder “AAA” (first hierarchy) is designated, the folder control unit 303 refers to the folder data 309, data corresponding to the definition of the hierarchy above the parent folder, If necessary, get the metadata of the folder one level below the parent folder. The folder control unit 303 refers to the folder definition data 307 and acquires the definition of the hierarchy higher than the hierarchy immediately below the parent folder, and if necessary, the definition of the metadata.

  For example, the folder control unit 303 refers to the folder data 309 and acquires “2002” for data corresponding to the 0th hierarchy and “AAA” for data corresponding to the 1st hierarchy. Further, the folder control unit 303 refers to the folder definition data 307 to obtain the definition “year” of the 0th hierarchy, the definition “in charge” of the 1st hierarchy, and the definition “customer” of the 2nd hierarchy.

  As a result, the folder control unit 303 can generate the second-level folder registration form shown in FIG. The user can easily generate a folder according to the folder hierarchy simply by inputting information to “customer”.

  FIG. 10 is a diagram showing an example of a third-level folder registration form. The example shown in FIG. 10 shows a registration form in which a parent folder is designated as “(stock) aaa” (second layer) and a folder is created. As shown in FIG. 10, when the parent folder “(stock) aaa” (second hierarchy) is designated, the folder control unit 303 refers to the folder data 309 and corresponds to the definition of the hierarchy higher than the parent folder. Acquire data, and if necessary, metadata of the folder one level below the parent folder. The folder control unit 303 refers to the folder definition data 307 and acquires the definition of the hierarchy higher than the hierarchy immediately below the parent folder, and if necessary, the definition of the metadata.

  For example, the folder control unit 303 refers to the folder data 309, the data corresponding to the 0th hierarchy is “2002”, the data corresponding to the 1st hierarchy is “AAA”, the data corresponding to the 2nd hierarchy “(stock) ) Aaa ”. Further, the folder control unit 303 refers to the folder definition data 307 and defines the definition “year” of the 0th hierarchy, the definition “in charge” of the 1st hierarchy, the definition “customer” of the 2nd hierarchy, and the definition “3” of the 3rd hierarchy. Acquires the item number. At this time, the folder control unit 303 acquires “project”, “order”, “estimate”, “billing”, and “finished date”, which are metadata definitions corresponding to the third hierarchy.

  As a result, the folder control unit 303 can generate the third-level folder registration form shown in FIG. The user can easily set metadata corresponding to the definition of the metadata. Note that the folder registration form shown in FIG. 10 may be displayed after “(aaa) aaa” is input to the customer of the folder registration form shown in FIG. 9 and the creation button is pressed. Thereby, since folders are continuously created according to the defined folder hierarchy, folders can be quickly created without placing a burden on the user.

  In addition, when creating a new folder, the folder control unit 303 can specify folder definition data (cabinet) and hierarchy instead of specifying a parent folder. In this case, the folder control unit 303 also inputs data corresponding to a hierarchy higher than the designated hierarchy. If there is no upper folder, it is possible to create not only the registered folder but also the upper folder. For example, in FIG. 10, “year” is a text box, and “in charge” and “customer” are input from the list of registered folder names so that the user can create an annual folder after creating a year folder. Can be omitted. That is, not only can a folder be created from the upper layer to the lower layer, but a folder can be created from the lower layer to the upper layer.

  By having the data structure as shown in FIG. 6, in the embodiment, as shown in FIGS. 9 and 10, according to the definition of the folder hierarchy, the folder definition is displayed at the time of creating the folder, and the metadata is input. Can also be encouraged.

(Search)
Next, an example of search by the folder control unit 303 will be described. FIG. 11 is a diagram illustrating an example of a folder search result. FIG. 11 shows a result when a search is performed using “level = 2” or “layer = layer_2” to specify a folder hierarchy. As shown in FIG. 11, a list of folders up to the second hierarchy is displayed. Further, when “level = 2” or “layer = layer_2” is searched as a search expression, a folder list as shown in FIG. 8 is displayed as a result.

  The folder control unit 303 can also search by combining the hierarchy and the metadata. For example, if “layer = layer_3 && dtag_estimation =“ done ”” is used as a search expression, folders having metadata “estimate” “done” can be searched from the folders in the third layer. As a result, even if the root folder (the 0th hierarchy) is different, the folder can be searched across the folders in the 3rd hierarchy, or search can be performed using the metadata of the folder. Is also possible.

  The file control unit 305 can also search using metadata attached to the file and metadata attached to the folder. This is because in the embodiment, the metadata attached to the file and the metadata attached to the folder are identified and retained.

<Operation>
Next, the operation of the file management system in the embodiment will be described. Hereinafter, operations of folder registration, folder display, and file display will be described in order.

(Folder registration)
FIG. 12 is a sequence diagram illustrating an example of a folder registration process. In step S101 shown in FIG. 12, the user requests the server 107 from the client 101 or the like to specify a parent folder, for example, and register a folder.

  In steps S102 and S103, upon receiving a registration request, the folder control unit 303 identifies the folder definition data to which the parent folder belongs from the parent folder. With the data structure shown in FIG. 4, the folder definition data can be specified by “cabinet_id”. Further, when “cabinet_id” is specified in the requested URL, the folder control unit 303 may acquire “cabinet_id” therefrom. When searching for the parent folder, the folder control unit 303 may specify not only the “id” of the folder but also “cabinet_id” so that the parent folder cannot be searched if the specification of “cabinet_id” is different. The folder control unit 303 acquires folder definition data corresponding to the identified “cabinet_id” from the folder definition data 307.

  In steps S <b> 104 and S <b> 105, the folder control unit 303 acquires the folder data of the parent folder from the folder data 309 using “id” of the designated parent folder. At this time, the folder data of the parent folder holds data corresponding to the folder definition in the layer above the parent folder. The folder control unit 303 generates a registration form based on the acquired folder definition data and folder data (see FIGS. 9 and 10).

In step S <b> 106, the folder control unit 303 transmits a registration form to the client 101. The registration form includes folder hierarchy definitions and metadata fields. As for metadata, it is also possible to specify a selection box in advance for the tag data and display a select box. Examples of tag data are as follows.
| cabinet_id | tag_type | value |
| 1 | Estimate | Done |
| 1 | Estimate | Not |
| 1 | Order received | Completed |
| 1 | Orders | Not |
Accordingly, it is possible to display a select box in which “done” or “not yet” can be selected instead of the “estimate” text field shown in FIG.

  In step S <b> 107, the client 101 transmits the new folder data to the server 107 together with the data input by the user.

  In steps S108 and S109, upon receiving the new folder data, the folder control unit 303 acquires “cabinet_id” of the new folder data, and acquires folder definition data corresponding to the acquired “cabinet_id” from the folder definition data 307.

  In steps S110 and S111, the folder control unit 303 acquires the folder data of the parent folder from the folder data 309 using “id” of the acquired new folder data. At this time, the folder control unit 303 checks whether the data format of the metadata is correct. For example, whether date is not included in the metadata of the character string.

  In steps S112 and S113, the folder control unit 303 registers the new folder data in the folder data 309 when the confirmation of the new folder data is completed.

  In step S <b> 114, the folder control unit 303 transmits a registration completion notification to the client 101. Thereby, the user can recognize that the registration of the new folder data is completed.

  If the parent folder is not designated in step S101, the folder control unit 303 can determine that a parent folder is to be created, and can also acquire the 0th layer folder data and create the parent folder.

(Folder display)
FIG. 13 is a sequence diagram illustrating an example of a folder display process. In step S <b> 201, the client 101 transmits a folder display request requested by the user to the server 107. At this time, as a specification method at the time of folder request, for example,
・ Specify the folder ・ Specify the folder hierarchy and metadata values (multiple combinations are possible)
There is.

  In steps S202 and S203, upon receiving a folder display request, the folder control unit 303 acquires “cabinet_id” if the folder is included in the contents specified at the time of the folder request. The folder control unit 303 acquires folder definition data corresponding to the acquired “cabinet_id” from the folder definition data 307.

  In steps S <b> 204 and S <b> 205, the folder control unit 303 acquires folder data corresponding to the folder and metadata designated by the user from the folder data 309. The folder specified by the user is, for example, a folder whose level is “second level”, and the metadata specified by the user is, for example, metadata whose “estimation” is “not yet”.

  In step S206, the folder control unit 303 generates a folder list based on the acquired folder definition data and folder data (see FIG. 8 and the like), and transmits the folder list to the client 101. Thereby, the user can see a desired folder list.

(File display)
FIG. 14 is a sequence diagram illustrating an example of a file display process. In step S <b> 301, the client 101 transmits a file display request requested by the user to the server 107. At this time, as a specification method at the time of file request, for example,
・ Specify folder ・ Specify folder hierarchy, folder metadata value, file metadata value, or file name (multiple combinations are possible)
There is.

  In step S302 and S303, when the file control unit 305 receives a file display request, the file control unit 305 acquires “cabinet_id” if the content specified at the time of the file request includes a folder, and the folder corresponding to the acquired “cabinet_id” Definition data is acquired from the folder definition data 307.

  In steps S304, S305, and S306, the file control unit 305 acquires folder data corresponding to the folder and metadata designated by the user from the folder data 309. The folder specified by the user is, for example, a folder whose level is “second level”, and the metadata specified by the user is, for example, metadata whose “estimation” is “not yet”.

  In addition, the file control unit 305 acquires a file stored in the acquired folder from the file data 311. When the file metadata and file name are specified, the file control unit 305 searches based on the file metadata value and file name regardless of the folder hierarchy, and the search result (file data with folder information). ) To get.

  In step S <b> 307, the file control unit 305 generates a file list based on the acquired folder definition data, folder data, and file, and transmits the file list to the client 101. Thereby, the user can see a desired file list.

  FIG. 15 is a diagram illustrating an example of a search UI using metadata. A search UI 1501 illustrated in FIG. 15 illustrates an example in which time, a case number, a country, and the like are assigned to a folder as metadata. A search UI 1503 shown in FIG. 15 shows an example when a search is performed using the metadata item number “* 01234 *”.

  Since “*” represents an arbitrary zero or more characters, the search keyword “* 01234 *” searches for a case including 01234. In the folder list 1504 of the search UI 1503, folders to which metadata of case numbers including “01234” is added are displayed. A search UI 1505 shown in FIG. 15 shows an example when a search is made in the metadata country “JAPAN”. In the folder list 1506 of the search UI 1505, folders to which metadata of the country “JAPAN” is assigned are displayed.

  FIG. 16 is a diagram illustrating an example of an API (Application Program Interface) used in the server 107. The client 101 can call these APIs by the JavaScript (registered trademark) program of the browser and dynamically configure the screen according to the request. A path 1601 “cabinets / {id} /folders.json” illustrated in FIG. 16 is an API for acquiring a folder list. An example 1602 is an example of an API that acquires a folder list whose data corresponding to the definition of the layer “2” (second layer) and the layer “0” is “JP”. At this time, the data corresponding to the definition of the hierarchy of layer 2 or higher is displayed in the folder list.

  A path 1603 “cabinets / {id} /layers.json” is an API for acquiring a list of folder names of a specified layer. An example 1604 is an example of an API that acquires a list of folder names of folders of the layer “1” (first layer). At this time, for example, “2007.01” and “2007.02” are displayed in the folder name list.

  A path 1605 “cabinets / {id} /entries.json” is an API for acquiring a file list. Example 1606 is an example of an API for acquiring a file list stored in a folder whose layer name is “00000012344891” of the layer “2” (second layer), and is stored in the folder whose folder ID is “2108”. It is an example of API which acquires the list of files that are stored. At this time, for example, the file ID, position, size, title, and the like are displayed in the file list.

  A path 1607 “cabinets / {id} /tags.json” is an API for obtaining a list of tag candidates. An example 1608 is an example of an API that acquires a list of tags that are candidates for “stag_2”. At this time, the cabinet ID, folder ID, tag name, tag type, and the like are displayed.

  As described above, according to the embodiment, centralized management and search of data stored in a folder can be facilitated. If the file management system in the embodiment is applied to a backbone system that handles a large amount of data, the object of the present invention can be achieved more.

  The program executed by the server according to the embodiment has a module configuration including the above-described units. As actual hardware, the CPU (processor) reads the program from the storage medium and executes the program. Are loaded on the main memory, and the above-mentioned means are generated on the main memory.

  In addition, this invention is not limited to the said Example as it is, A component can be deform | transformed and embodied in the range which does not deviate from the summary in an implementation stage. Moreover, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the above embodiments. For example, some components may be deleted from all the components shown in the embodiments.

101 Client 103, 113 LB
105, 107, 109 Server 111 DB
113 File management server 201 Control unit 301 Folder definition control unit 303 Folder control unit 305 File control unit 307 Folder definition data 309 Folder data 311 File data

JP 2008-310450 A JP 2006-526182 A

Claims (8)

A file management system for managing files,
A definition control means for defining a folder hierarchy for managing files, defining each folder hierarchy, and defining a metadata associated with the definition of the hierarchy assigned to the folder in the hierarchy;
First storage means for storing one or a plurality of folder definition data including a hierarchy definition indicating a definition for each defined hierarchy and a metadata definition indicating a definition of metadata to be given;
For each folder in the folder hierarchy, one or a plurality of folder data including the data corresponding to the folder definition of the folder or higher than the hierarchy of the folder and the metadata corresponding to the metadata definition assigned to the folder are stored. A second storage means;
Third storage means for storing a file associated with a hierarchy of folders in the folder hierarchy and metadata attached to the folder;
When creating a new folder, the folder definition data and the hierarchy are specified, the hierarchy definition higher than the hierarchy in the specified folder definition data, the data display area corresponding to the hierarchy definition, and the hierarchy of the specified folder definition data And a folder control means for generating a registration form having a data input area corresponding to the hierarchy definition. The second storage means stores an identifier of the folder definition data for each folder,
The file management system according to claim 1, wherein the third storage unit stores an identifier of the folder data for each file.   3. The file management system according to claim 1, wherein the third storage unit stores the metadata of the file so as to be distinguishable from the metadata of the folder. The folder control means further includes
When creating a new folder, specify the parent folder, and correspond to the hierarchy definition above the specified parent folder hierarchy, the data display area corresponding to the hierarchy definition, and the hierarchy definition one level below the parent folder The file management system according to claim 1, wherein a registration form having an input area for data to be generated is generated. The folder control means further includes
The folder in the folder hierarchy is searched based on at least one of the designation of the folder, the designation of the hierarchy, and the designation of metadata assigned to the folder when receiving the display request of the folder. 4. The file management system according to any one of 4.   When receiving a display request for the file, based on at least one of the designation of the folder, the designation of the hierarchy, the designation of metadata assigned to the folder, the designation of the metadata of the file, and the designation of the file name The file management system according to any one of claims 1 to 5, further comprising file control means for searching for a file contained in a folder in the folder hierarchy. A definition control means for defining a folder hierarchy for managing files, defining each folder hierarchy, and defining a metadata associated with the definition of the hierarchy assigned to the folder in the hierarchy;
A folder control means for searching for a folder in the folder hierarchy based on at least one of the designation of the folder, the designation of the hierarchy, and the designation of metadata assigned to the folder when receiving a display request for the folder; ,
When receiving a display request for the file, a folder in the folder hierarchy is specified based on at least one of the designation of the folder, the designation of the hierarchy, the designation of metadata assigned to the folder, and the designation of the file name. A file control means for searching for included files,
The folder control means includes
When creating a new folder, the folder definition data and the hierarchy are specified, the hierarchy definition higher than the hierarchy in the specified folder definition data, the data display area corresponding to the hierarchy definition, and the hierarchy of the specified folder definition data An information processing apparatus for generating a registration form having a data input area corresponding to a hierarchy definition. An information processing method in an information processing apparatus,
A definition control step for defining a folder hierarchy for managing files, defining each folder hierarchy, and defining metadata related to the definition of the hierarchy assigned to a folder in the hierarchy;
When creating a new folder, the folder definition data and the hierarchy are specified, the hierarchy definition higher than the hierarchy in the specified folder definition data, the data display area corresponding to the hierarchy definition, and the hierarchy of the specified folder definition data A generation step for generating a registration form having a data input area corresponding to the hierarchy definition;
A creation step of creating a folder based on the data entered in the registration form;
A folder that searches for a folder in the folder hierarchy based on at least one of the designation of the folder, the designation of the hierarchy, and the designation of metadata assigned to the folder when receiving a display request for the created folder Control steps;
When receiving a display request for a file in the created folder, the specification is based on at least one of the designation of the folder, the designation of the hierarchy, the designation of metadata assigned to the folder, and the designation of the file name. An information processing method comprising: a file control step of searching for a file included in a folder in a folder hierarchy.

Images